Session Description Protocol (SDP) Attributes for Open Mobile Alliance (OMA) Broadcast (BCAST) Service and Content Protection
draft-dondeti-oma-mmusic-sdp-attrs-00

[Ballot comment]
The document should be either re-classified as PS (and go through the appropriate IETF LC) or it should include text in the Introduction to explain why Informational is enough. Both paths are OK with me.

[Ballot comment]
Comments from Al Morton, OPS-DIR:


Since the Intro says:
  OMA BCAST specifications are expected to be used by 3GPP MBMS, 3GPP2
  BCMCS and DVB-H based broadcast wireless systems.

this seems to satisfy the criteria for a Standards Track Specification,
according to RFC4566:
  ...Attributes that are
  expected to see widespread use and interoperability SHOULD be
  documented with a standards-track RFC that specifies the attribute
  more precisely.

1,$s/identifyer/identifier/g


Section 3  New SDP Attributes

The 193 page OMA Reference Document gives many examples where
the identifier for a stream is specified by attribute "streamid".
Two of the new attributes also specify ids:
  o  a=stkmstream:
  o  a=SRTPAuthentication:
Suggest it would be more exact to name these attributes:
  o  a=stkmstreamid:
  o  a=SRTPAuthenticationid:
(Naming is kind of an OPS issue)

Section 4 Security Considerations

The paragraphs describing the reasons to protect bcastversion and
stkmstream(id) could be included in the Purpose section of the
corresponding attribute specification in Section 5.


Section 5  IANA Considerations

S 5.1.3  SRTPAuthentication:

[Ballot discuss]
Section 1 says:
  >
  > Section 8.2.4 of RFC 4566 [1] requires that new SDP attributes are
  > registered through IANA with name, contact information and
  > description (and other similar parameters).  A standards track
  > specification is RECOMMENDED if the new attribute(s) will have
  > widespread use and interoperability considerations.
  >
  This begs for another sentence telling why this document is not on
  the standards track.

[Ballot discuss]
Section 1 says:
  >
  > Section 8.2.4 of RFC 4566 [1] requires that new SDP attributes are
  > registered through IANA with name, contact information and
  > description (and other similar parameters).  A standards track
  > specification is RECOMMENDED if the new attribute(s) will have
  > widespread use and interoperability considerations.
  >
  This begs for another sentence telling why this document is not on
  the standards track.

[Ballot discuss]
Section 1 says:
  >
  > Section 8.2.4 of RFC 4566 [1] requires that new SDP attributes are
  registered through IANA with name, contact information and
  > description (and other similar parameters).  A standards track
  > specification is RECOMMENDED if the new attribute(s) will have
  > widespread use and interoperability considerations.
  >
  This begs for another sentence telling why this document is not on
  the standards track.