RFC 4566, "SDP: Session Description Protocol", July 2006

Note: This RFC has been obsoleted by RFC 8866

Errata ID: 4769
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Petr Vaněk
Date Reported: 2016-08-08
Rejected by: Ben Campbell
Date Rejected: 2016-08-08

Section 5.3. says:

5.3.  Session Name ("s=")

      s=<session name>

   The "s=" field is the textual session name.  There MUST be one and
   only one "s=" field per session description.  The "s=" field MUST NOT
   be empty and SHOULD contain ISO 10646 characters (but see also the
   "a=charset" attribute).  If a session has no meaningful name, the
   value "s= " SHOULD be used (i.e., a single space as the session
   name).

It should say:

5.3.  Session Name ("s=")

      s=<session name>

   The "s=" field is the textual session name.  There MUST be one and
   only one "s=" field per session description.  The "s=" field MUST NOT
   be empty and SHOULD contain ISO 10646 characters (but see also the
   "a=charset" attribute).  If a session has no meaningful name, the
   value "s=-" SHOULD be used (i.e., a single dash as the session
   name).

Notes:

In 3rd paragraph of section 5. is written: whitespace MUST NOT be used on either side of the "=" sign, which is incosistent with subsection 5.3. Therefore I suggest to use "-" (single dash) instead of " " (single space) for sessions without meaningful name.
--VERIFIER NOTES--
The mmusic working group is in the process of updating RFC 4566. If the issue applies to the updated text ( https://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc4566bis/ ), please send comments to mmusic@ietf.org rather than file errata reports against RFC 4566.

Report New Errata