AVT Working Group D. Wing Internet-Draft Cisco Updates: 4568, 3711 April 20, 2010 (if approved) Intended status: Standards Track Expires: October 22, 2010 Policy for Registering SRTP Transforms draft-ietf-avt-register-srtp-02 Abstract IETF procedure requires country-specific cryptographic transforms to be Informational RFCs. This document allows such Informational RFCs to be used by SRTP and SRTP Security Descriptions. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on October 22, 2010. Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of Wing Expires October 22, 2010 [Page 1]
Internet-Draft Policy for Registering SRTP Transforms April 2010 publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Update to RFC3711 . . . . . . . . . . . . . . . . . . . . . . . 3 3. Update to RFC4568 . . . . . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 7.1. Normative References . . . . . . . . . . . . . . . . . . . 4 7.2. Informative References . . . . . . . . . . . . . . . . . . 4 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4 Wing Expires October 22, 2010 [Page 2]
Internet-Draft Policy for Registering SRTP Transforms April 2010 1. Introduction It is desirable to extend Secure Real-time Transport Protocol (SRTP [RFC3711]) and its keying mechanisms to support country-specific cryptographic transforms. This document resolves a clash between IETF procedure and existing RFCs. IETF procedure requires that cryptographic transforms not intended for deployment on the Internet be published as Informational RFCs (Section 4.2 of [RFC2026]). However, existing documents require extensions to SRTP and extensions to SRTP keying to be published as Standards-Track RFCs. This document resolves this clash by allowing Informational RFCs to register new cryptographic transforms. 2. Update to RFC3711 This document updates Section 6 and Section 12 of [RFC3711], which currently require a standards track RFC to define a new SRTP transform. After publication of this document, new SRTP transforms can be defined using "IETF Review" policy of [RFC5226]. 3. Update to RFC4568 This document updates Section 10.3.2.1 of [RFC4568] to change the requirements to add a new crypto suite to the IANA registry "SRTP Crypto Suite Registrations" which currently requires Standards Action. After publication of this document, new SRTP crypto suite registrations are allocated using the "IETF Review" policy of [RFC5226], and the "SRTP Crypto Suite Registrations" table should also reference [RFCXXXX]. [RFC Editor, IANA: RFCXXXX should be replaced by the number for this RFC.] 4. Security Considerations This specification makes it easier for new cryptographic transforms to be used with SRTP. However, this specification does not lift the requirement that cryptographic transforms are subject to IETF Review [RFC5226]. 5. IANA Considerations Please see Section 3. Wing Expires October 22, 2010 [Page 3]
Internet-Draft Policy for Registering SRTP Transforms April 2010 6. Acknowledgements Thanks to Roni Even for guidance on this document. Thanks to Carlos Pignataro and Brian Weis and for their review comments. This document was produced using version e1-dwing of XML2RFC. 7. References 7.1. Normative References [RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, "The Secure Real-time Transport Protocol (SRTP)", RFC 3711, March 2004. [RFC4568] Andreasen, F., Baugher, M., and D. Wing, "Session Description Protocol (SDP) Security Descriptions for Media Streams", RFC 4568, July 2006. [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. 7.2. Informative References [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. Author's Address Dan Wing Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134 USA Email: dwing@cisco.com Wing Expires October 22, 2010 [Page 4]
