Network Working Group Abhishek Tiwari INTERNET-DRAFT Microsoft Corporation Category: Informational 24 November 2008 Expires: February 9, 2009 New Tunnel-Type Values draft-ietf-radext-tunnel-type-00.txt By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of 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 February 9, 2009. Copyright Notice Copyright (C) The IETF Trust (2008). All Rights Reserved. Abstract This document defines a set of values for the Tunnel-Type RADIUS Attribute. Tiwari Informational [Page 1] INTERNET-DRAFT New Tunnel-Type Values 28 August 2008 Table of Contents 1. Introduction .......................................... 3 2. Tunnel-Type Values .... ............................... 3 3. IANA Considerations ................................... 3 3.1 Attribute Values ...................................... 3 4. Security Considerations ............................... 4 5. References ............................................ 4 5.1 Normative References .................................. 4 5.2 Informative References ................................ 4 ACKNOWLEDGMENTS .............................................. 4 AUTHOR'S ADDRESSES ........................................... 5 Full Copyright Statement ..................................... 5 Intellectual Property ........................................ 5 Tiwari Informational [Page 2] INTERNET-DRAFT New Tunnel-Type Values 28 August 2008 1. Introduction The RADIUS protocol is defined in [RFC2865]. "RADIUS Attributes for Tunnel Protocol Support" [RFC2868] Section 3.1 defines the Tunnel- Type Attribute. This document defines a set of new values for the Tunnel-Type Attribute. In [RFC2868] Section 3.1, two values relating to IPsec Tunnel-mode are allocated, one for "IP Authentication Header in the Tunnel-mode (AH)" (6), and one for for "IP Encapsulating Security Payload in the Tunnel-mode (ESP)" (9). While the key management mechanisms are not stated, it is assumed that these include either Internet Key Exchange (IKE) [RFC2409] or manual keying via the Tunnel-Password Attribute defined in [RFC2868] Section 3.5. Since then, IKEv2 [RFC4306] has been developed, and the specification for ESP has been revised [RFC4303]. This document requests allocation of additional Tunnel-Type values for "IP Encapsulating Security Payload in the Tunnel-mode (ESP) with IKEv2", as well as for the "Secure Socket Tunneling Protocol (SSTP)" [SSTP]. 2. Tunnel-Type Values This document defines new values for the Tunnel-Type Attribute. This specification concerns the following values: 14 IP Encapsulating Security Payload (ESP) [RFC4303] in the Tunnel-mode with IKEv2 [RFC4306] 15 Microsoft Secure Socket Tunneling Protocol (SSTP) [SSTP] 3. IANA Considerations This document requests assignment of new values of the RADIUS Tunnel- Type Attribute by IANA in the appropriate registry [RADTYP]. The new values being requested are: Tunnel-Type Value ========= ==== IP Encapsulating Security Payload (ESP) in the Tunnel-mode with IKEv2 14 Microsoft Secure Socket Tunneling Protocol (SSTP) 15 Additional values of the Tunnel-Type Attribute are allocated as described in [RFC2868] Section 6.1 (IETF Consensus). Allocation of attribute values is also discussed in [RFC3575] Section 2.1. Tiwari Informational [Page 3] INTERNET-DRAFT New Tunnel-Type Values 28 August 2008 4. Security Considerations This specification neither adds to nor detracts from the security of the RADIUS protocol. 5. References 5.1. Normative references [RFC2865] Rigney, C., Rubens, A., Simpson, W. and S. Willens, "Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June 2000. [RFC2868] Zorn, G., Leifer, D., Rubens, A., Shriver, J., Holdrege, M., and I. Goyret, "RADIUS Attributes for Tunnel Protocol Support", RFC 2868, June 2000. [RFC3575] Aboba, B., "IANA Considerations for RADIUS", RFC 3575, July 2003. 5.2. Informative references [RADTYP] Internet Assigned Numbers Authority, "RADIUS TYPES", . [RFC2409] Harkins, D. and D. Carrel, "The Internet Key Exchange (IKE)", RFC 2409, November 1998. [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", RFC 4303, December 2005. [RFC4306] Kaufman, C., Ed., "Internet Key Exchange (IKEv2) Protocol", RFC 4306, December 2005. [SSTP] "[MS-SSTP]: Secure Socket Tunneling Protocol (SSTP) Specification", Microsoft Developer Network Library, http://msdn.microsoft.com/en-us/library/cc247338.aspx Acknowledgments The authors would like to acknowledge the RADEXT WG for review of this document. Tiwari Informational [Page 4] INTERNET-DRAFT New Tunnel-Type Values 28 August 2008 Authors' Addresses Abhishek Tiwari Microsoft Corporation Hyderabad, India EMail: abhisht@microsoft.com Full Copyright Statement Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Tiwari Informational [Page 5] INTERNET-DRAFT New Tunnel-Type Values 28 August 2008 Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Tiwari Informational [Page 6]