Re: [alto] ALTO Meeting Info for Dec. 18, 2019 [last meeting before Xmas break]

2019-12-18 Thread LUIS MIGUEL CONTRERAS MURILLO 
I will not be able to attend today, apologies.

Obtener Outlook para Android

From: alto-weekly-meet...@googlegroups.com 
 on behalf of Danny Alex Lachos Perez 

Sent: Tuesday, December 17, 2019 5:27:15 PM
To: IETF ALTO ; alto-weekly-meet...@googlegroups.com 

Subject: ALTO Meeting Info for Dec. 18, 2019 [last meeting before Xmas break]

Dear all,

Just a friendly reminder that we will have one more weekly meeting this 
Wednesday before the Xmas break.

Agenda*:

  *   Discuss WG rechartering
  *   Updates on existing WG documents
  *   Plan for next side meeting/workshop

*If people have other agenda items, please feel free to post.

Date/time: Dec-18 at 9:30 am US ET.
Bridge link: https://yale.zoom.us/j/8423318713

Best regards,

Danny Lachos

--
You received this message because you are subscribed to the Google Groups 
"alto-weekly-meeting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
alto-weekly-meeting+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/alto-weekly-meeting/CAEDarXLjGLbXdwrmR1P40Hx-dV4cTgL%3D%3D-8jj_bNG4mTkYrM4w%40mail.gmail.com.



Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede 
contener informaci?n privilegiada o confidencial y es para uso exclusivo de la 
persona o entidad de destino. Si no es usted. el destinatario indicado, queda 
notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin 
autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente.. Si ha 
recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente 
por esta misma v?a y proceda a su destrucci?n.

The information contained in this transmission is privileged and confidential 
information intended only for the use of the individual or entity named above. 
If the reader of this message is not the intended recipient, you are hereby 
notified that any dissemination, distribution or copying of this communication 
is strictly prohibited. If you have received this transmission in error, do not 
read it. Please immediately reply to the sender that you have received this 
communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat?rio, pode 
conter informa??o privilegiada ou confidencial e ? para uso exclusivo da pessoa 
ou entidade de destino. Se n?o ? vossa senhoria o destinat?rio indicado, fica 
notificado de que a leitura, utiliza??o, divulga??o e/ou c?pia sem autoriza??o 
pode estar proibida em virtude da legisla??o vigente. Se recebeu esta mensagem 
por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e 
proceda a sua destrui??o
___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

Re: [alto] End of WGLC for update-sse; need reviews.

2019-12-18 Thread Jensen Zhang 
Hi WG,

Sorry for my late review. This document is quite long. But I think the
overall write-up is clear enough. Please see my comments inline:

Section 6.1., paragraph 3:

>Hence, the event field of ALTO update message can include two sub-
>fields (media-type and data-id), where the two sub-fields are
>separated by a comma:
 COMMENT:
  As the SSE message can support unicode, indicating that the comma is
  (',', U+002C) may be better. This is also consistent with the
  character encoding used in other ALTO documents (e.g., Section 10.1
  of RFC7285).


Section 6.1., paragraph 5:

>To allow non-ambiguous decoding of the two sub-fields, the media-type
>name used by ALTO SSE MUST NOT contain a comma (character code 0x2c),
>and the string before the comma is the media-type name.  [To RFC
>editor: please check this conforms to Section 4.2 of [RFC6838] and
>confirms to IANA.]
 COMMENT:
  According to the ABNF of Section 4.2 of [RFC6838], the media-type
  name can never include a comma. So the "MUST NOT" requirement
  can be removed. Instead, we can emphasize there is no ambiguity,
  if necessary.


Section 6.2., paragraph 2:

>The `data-id` sub-field identifies the ALTO data to which a data
>update message applies.  For a resource containing only a single JSON
>object, the substream-id assigned by the client when requesting the
>SSE service is enough to identify the data.  In this document,
>substream-ids MUST follow the rules for ALTO ResourceIds
>(Section 10.2 of [RFC7285]).  Substream-ids MUST be unique within an
>update stream, but need not be globally unique.  For a resource using
>multipart/related, the `data-id` sub-field must include the
>substream-id, `.` and the unique Content-ID.
 COMMENT:
  "must" should be capitalized: the `data-id` sub-field must xxx ->
  MUST The description "must include substream-id, `.` and the unique
  Content-ID" is not clear for me. It seems that this document does
  not just require the `data-id` to include these three components,
  but be exactly the concatenation of them in order.

The latest revision introduces more generic `data-id` to support multipart
messages. But I do not see an example to show how to use it. We know path
vector is a potential example. Maybe authors do not want to make this
document coupled with path vector.

Cheers,
Jensen


On Fri, Dec 13, 2019 at 10:19 AM Vijay Gurbani 
wrote:

> Jensen: Excellent.  Thank you!
>
> On Fri, Dec 13, 2019 at 9:04 AM Jensen Zhang 
> wrote:
>
>> Hi Vijay and WG,
>>
>> I am reviewing the latest revision of SSE. I will post my review by
>> tonight.
>>
>> Thanks,
>> Jensen
>>
>>
>> On Fri, Dec 13, 2019 at 10:01 AM Vijay Gurbani 
>> wrote:
>>
>>> Folks: The WGLC ended for update-sse on Dec 8 [1].  However, we have had
>>> absolutely no discussion on the mailing list about this draft after it was
>>> posted for WGLC.
>>>
>>> I am shepherding this draft, and as such, I will need at least one, and
>>> perhaps two, members from the WG who are not associated with the draft to
>>> perform an indepth review of this draft.  I will review it as well as part
>>> of shepherding.
>>>
>>> Please send me an email indicating that you will like to review this
>>> draft, and please let me know when to expect the review by.
>>>
>>> Thank you.
>>>
>>> [1]
>>> https://mailarchive.ietf.org/arch/msg/alto/hHM_bC1CfwygcxTTm96zBbj7gmo
>>> ___
>>> alto mailing list
>>> alto@ietf.org
>>> https://www.ietf.org/mailman/listinfo/alto
>>>
>>
___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto