Re: [MMUSIC] RTSP: Speed header

On 5/7/07, Magnus Westerlund <magnus.westerlund@ericsson.com> wrote:
>    There is no means to negotiate a content type for
> > GET_PARAMETER and SET_PARAMETER, so their interoperability remain
> > dubious.  (And I've already complained that there is no specification
> > for "text/parameters" despite its usage both in the field and in the
> > examples.)
>
> Yes, I agree with that this isn't complete. Are you willing to write an
> definition of text/parameters?

Yuck.  I don't even like it.  But here's a stab:

A resource of type "text/parameters" consists of either
1) a list of parameters (for a query) or
2) a list of parameters and associated values (for an update).
Each entry of the list is a single line of text.  Parameters are
separated from values by a colon.

The ABNF [RFC2234] grammar for "text/parameters" content is:

(Note: this uses the "Core Rules" from RFC2234)

file = parameter-list / parameter-value-list
parameter-list = *(parameter CRLF)
parameter-value-list = *(parameter-value CRLF)
parameter-value = parameter WSP ":" value
parameter = 1*visible-except-colon
visible-except-colon = %x21-39 / %x3B-7E	; VCHAR - ":"
value = *VCHAR

> Do I understand you correctly that you rather see the asynchronous event
> signalling, like end of stream, to be in the base spec rather than as a
> extension specification. There was
> http://tools.ietf.org/id/draft-ietf-mmusic-rtsp-announce-01.txt

I would, in fact, prefer to see async stream event signalling in the
base spec. I think it is broadly useful.  But the ANNOUNCE draft
combines stream events with session announcements, and I don't see
async session announcements as being desirable in the base spec (does
anyone use them?), nor do I think the same method should be used for
both.

And I would rather see a finished, clean, extensible spec than my
preferred feature(s).  I do worry that extensions will be less
rigorously scrutinized because they are optional.

joe

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic