RTP Control Protocol (RTCP) Port for Source-Specific Multicast (SSM) Sessions
draft-ietf-avt-rtcp-port-for-ssm-04
Yes
(Robert Sparks)
No Objection
(Gonzalo Camarillo)
(Jari Arkko)
(Peter Saint-Andre)
(Ron Bonica)
(Russ Housley)
(Stewart Bryant)
(Tim Polk)
Note: This ballot was opened for revision 04 and is now closed.
Robert Sparks Former IESG member
Yes
Yes
()
Unknown
Adrian Farrel Former IESG member
No Objection
No Objection
(2011-01-05)
Unknown
As idnits points out, you can strip the RFC 2119 boilerplate and reference. I'm sure the RFC Editor can handle this.
David Harrington Former IESG member
No Objection
No Objection
(2011-01-05)
Unknown
1) in section 1, "the +1 rule" is mentioned without definition or reference.
Gonzalo Camarillo Former IESG member
No Objection
No Objection
()
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
()
Unknown
Peter Saint-Andre Former IESG member
No Objection
No Objection
()
Unknown
Ron Bonica Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
()
Unknown
Sean Turner Former IESG member
No Objection
No Objection
(2011-01-05)
Unknown
Section 5 has: This can, for example, be achieved on an end-to-end basis using S/MIME [RFC5652] when SDP is used in a signaling packet using MIME types (application/sdp). Technically, S/MIME messages aren't in [RFC5652] they're in [RFC5751]. RFC 5652 is CMS, which is profiled for email in RFC 5751. I've noted that when used with SDP S/MIME has been referred to as follows: RFC 4566 uses text that is similar, but omits a reference for S/MIME; RFC 4657 uses RFC 3851 (previous version of RFC 5751); RFC 4658 uses RFC 3851; RFC 3605 uses RFC 3852 (prior version of RFC 5652); RFC 3261 refers to both 2633 (S/MIME) and 2630 (CMS). Maybe the right approach is to point to both CMS and S/MIME.
Stewart Bryant Former IESG member
No Objection
No Objection
()
Unknown
Tim Polk Former IESG member
No Objection
No Objection
()
Unknown