[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lemonade] WGLC streaming

Dave Cridland wrote:

2). In Section 2.2:

The first example:

  C: a122 UID FETCH 24356 BODY[1.2.MIME]
  S: * 26 FETCH (BODY[1.2.MIME] {127}
  S: Content-Transfer-Encoding: base64
  S: Content-Type: video/mpeg;
  S: UID 24356 FLAGS (\Seen))


Should be:

  C: a122 UID FETCH 24356 BODY[1.2.MIME]
  S: * 26 FETCH (BODY[1.2.MIME] {62}
  S: Content-Transfer-Encoding: base64
  S: Content-Type: video/mpeg;
  S:  UID 24356 FLAGS (\Seen))

(i.e. an extra space before "UID" and change "{127}" to "{62}"

Actually, no... It *should* be using BODYSTRUCTURE to find the media type - by the time you know that section 1.2 (or 1.2.MIME) exists, you already know the media type of the part, and its encoding.

I thought about this too. But at least the current example needs to be fixed.
[...]

9). In section 5: 

I think this should be:

  ms-tuple = host ":" port [":" "authuser"]

as the last component is optional.

I'm concerned with IPv6 behaviour with this production. 

Good point.

I'm also thinking that perhaps a URI form would be more suitable, as it allows for more expansion capability. Assuming, that is, that these media services have URIs to them.

That would be fine with me, however this would require some changes to how ms-tuples are delimited.
Also this would mean that the username is explicit, which might be a good thing anyway


_______________________________________________
lemonade mailing list
lemonade at ietf.org
https://www1.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade