RTP Payload Format for ITU-T Recommendation G.722.1
RFC 5577

Note: This ballot was opened for revision 09 and is now closed.

Lars Eggert Yes

(Cullen Jennings) Yes

(Jari Arkko) No Objection

(Ron Bonica) No Objection

(Ross Callon) No Objection

(Lisa Dusseault) No Objection

(Pasi Eronen) No Objection

(Russ Housley) No Objection

(Alexey Melnikov) No Objection

Comment (2009-05-27)
No email
send info
The latest version addresses my SecDir review comments.

1 small nit in Section 6:

   Note that the appropriate mechanism to provide security to RTP and
   payloads following this memo may vary.  It is dependent on the
   application, the transport, and the signaling protocol employed.
   Therefore, a single mechanism is not sufficient, although if
   suitable, usage of the Secure Real-time Transport Protocol (SRTP)
   [RFC3711] recommended.  Other mechanisms that may be used are IPsec
   [RFC4301] Transport Layer Security (TLS) [RFC5246] (RTP over TCP);

"and" or "," is missing before Transport Layer Security.

   other alternatives may exist.

(Chris Newman) No Objection

(Jon Peterson) No Objection

(Tim Polk) (was No Record, Discuss) No Objection

(Dan Romascanu) (was Discuss) No Objection

Comment (2009-05-28)
No email
send info
Section 7 still says 'The new draft obsoletes RFC3047' - this needs to change in the final published version which will no longer be a draft

(Mark Townsley) No Objection

(David Ward) No Objection

(Magnus Westerlund) No Objection