SIP Interface to VoiceXML Media Services
draft-ietf-mediactrl-vxml-04
Yes
No Objection
Note: This ballot was opened for revision 04 and is now closed.
Lars Eggert No Objection
(Jon Peterson; former steering group member) Yes
(Robert Sparks; former steering group member) Yes
(Chris Newman; former steering group member) No Objection
Section 2.1, page 12, 3rd paragraph after ABNF: > Since some applications may choose to transfer confidential > information, the VoiceXML Media Server MUST support the sip: scheme > as discussed in Section 9. I believe this should say "sips:" instead of "sip:" to be consistent with Section 9.
(Cullen Jennings; former steering group member) No Objection
(Dan Romascanu; former steering group member) No Objection
The following issue was raised in the OPS-DIR review by Tina Tsou. In section 9 Security Considerations, it says SRTP should be supported to provide confidentiality, authentication, and replay protection for RTP media streams (including RTCP control traffic). However, in above use cases, all the message types are RTP/SRTP. In RTP case, how to guarantee security? So I suggest change “RTP/SRTP” to “RTP and SRTP” in all the use cases or to any other expressions to well express the problem.
(David Ward; former steering group member) No Objection
(Jari Arkko; former steering group member) No Objection
(Lisa Dusseault; former steering group member) (was Discuss) No Objection
(Magnus Westerlund; former steering group member) No Objection
(Mark Townsley; former steering group member) No Objection
(Ron Bonica; former steering group member) No Objection
(Ross Callon; former steering group member) No Objection
(Russ Housley; former steering group member) No Objection
(Tim Polk; former steering group member) No Objection