[AVT] Re: Changes in draft-ietf-avt-2833bis-13.txt

Thank you.

On May 8, 2006, at 8:13 PM, Tom-PT Taylor wrote:

> I have submitted an update to draft-ietf-avt-2833bis. It contains  
> the following changes.
>
> Abstract
> --------
> Added sentences indicating what was done with the RFC 2833 event  
> codes, in response to Sasha Vainshtein's intervention. Reorganized  
> the existing content to flow more smoothly given this change.
>
> Second paragraph of section 1.2 "Overview"
> ------------------------------------------
> Deleted "MIME" in front of "media type registrations" in the  
> existing last sentence. Added a new sentence pointing to Appendix  
> A, which lists the changes from RFC 2833.
>
> Section 6 "Security Considerations"
> -----------------------------------
> Added the following text based on comments from Pekka Nikander and  
> Magnus Nyström, and reorganized existing text to flow more smoothly  
> into it. Added RFC 3711 as a normative reference.
>
> "The telephony-event payload defined in this specification is  
> highly compressed. An interchange of just two bits can result in a  
> major change in meaning as decoded at the receiver. Thus the  
> telephony-event payload type is in particular need of protection of  
> integrity.
>
> "To meet the need for protection both of confidentiality and  
> integrity, this specification requires that compliant  
> implementations also implement the Secure Real-time Transport  
> Protocol (SRTP) [RFC3711].
>
> "  Note that the appropriate method of key distribution for SRTP
>    may vary with the specific application."
>
> Section 9.1 "Normative References"
> ----------------------------------
> Added RFC 3711 (SRTP), as indicated above.
>
> Updated the media type registration procedure reference (was "RFC  
> TBD") to point to RFC 4288.
>
> Section 9.2 "Informative References"
> ------------------------------------
> Added references to 2833bisdata and 2833biscas as Works In Progress.
>
> Appendix A (new)
> ----------------
> Describes the differences between RFC 2833 and 2833bis. Includes a  
> table indicating what happened to the event codes defined in RFC 2833.

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt