Re: [MMUSIC] [Technical Errata Reported] RFC4566 (5595)

[[e-mail] (Dale R. Worley)]

Paul Kyzivat <[e-mail]> writes:
> Do you have a thought about how to improve it? As it is, the text reads 
> as normative, but the ABNF should really be the formal authority, with 
> this being just a summary.

I think an adequate fix could be confined to an editorial change:

   Some lines in each description are REQUIRED and some are OPTIONAL,
   but all MUST appear in exactly the order given here (the fixed order
   greatly enhances error detection and allows for a simple parser).  In
   the following overview OPTIONAL items are marked with a "*".  (For
   details, see the formal grammar in Section 9.)

      Session description
         v=  (protocol version)
         o=  (originator and session identifier)
         s=  (session name)
         i=* (session information)
         u=* (URI of description)
         e=* (email address)
         p=* (phone number)
         c=* (connection information -- not required if included in
              all media descriptions)
         b=* (zero or more bandwidth information lines)
         One or more time descriptions:
           ("t=", "r=" and "z=" lines; see below)
         k=* (encryption key)
         a=* (zero or more session attribute lines)
         Zero or more media descriptions

+  The referenced subsections of the description have this structure:

      Time description
         t=  (time the session is active)
         r=* (zero or more repeat times)
         z=* (optional time zone offset line)

      Media description, if present
         m=  (media name and transport address)
         i=* (media title)
         c=* (connection information -- optional if included at
              session level)
         b=* (zero or more bandwidth information lines)
         k=* (encryption key)
         a=* (zero or more media attribute lines)

Inserting that one sentence tends to terminate the scope of "the
following overview".

Dale