idnits 2.17.1 draft-ietf-radext-tunnel-type-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 13. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 171. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 182. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 189. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 195. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 2 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document date (24 November 2008) is 5631 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 2409 (Obsoleted by RFC 4306) -- Obsolete informational reference (is this intentional?): RFC 4306 (Obsoleted by RFC 5996) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Abhishek Tiwari 3 INTERNET-DRAFT Microsoft Corporation 4 Category: Informational 24 November 2008 5 Expires: February 9, 2009 7 New Tunnel-Type Values 8 draft-ietf-radext-tunnel-type-00.txt 10 By submitting this Internet-Draft, each author represents that any 11 applicable patent or other IPR claims of which he or she is aware 12 have been or will be disclosed, and any of which he or she becomes 13 aware will be disclosed, in accordance with Section 6 of BCP 79. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt. 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 This Internet-Draft will expire on February 9, 2009. 33 Copyright Notice 35 Copyright (C) The IETF Trust (2008). All Rights Reserved. 37 Abstract 39 This document defines a set of values for the Tunnel-Type RADIUS 40 Attribute. 42 Table of Contents 44 1. Introduction .......................................... 3 45 2. Tunnel-Type Values .... ............................... 3 46 3. IANA Considerations ................................... 3 47 3.1 Attribute Values ...................................... 3 48 4. Security Considerations ............................... 4 49 5. References ............................................ 4 50 5.1 Normative References .................................. 4 51 5.2 Informative References ................................ 4 52 ACKNOWLEDGMENTS .............................................. 4 53 AUTHOR'S ADDRESSES ........................................... 5 54 Full Copyright Statement ..................................... 5 55 Intellectual Property ........................................ 5 56 1. Introduction 58 The RADIUS protocol is defined in [RFC2865]. "RADIUS Attributes for 59 Tunnel Protocol Support" [RFC2868] Section 3.1 defines the Tunnel- 60 Type Attribute. This document defines a set of new values for the 61 Tunnel-Type Attribute. 63 In [RFC2868] Section 3.1, two values relating to IPsec Tunnel-mode 64 are allocated, one for "IP Authentication Header in the Tunnel-mode 65 (AH)" (6), and one for for "IP Encapsulating Security Payload in the 66 Tunnel-mode (ESP)" (9). While the key management mechanisms are not 67 stated, it is assumed that these include either Internet Key Exchange 68 (IKE) [RFC2409] or manual keying via the Tunnel-Password Attribute 69 defined in [RFC2868] Section 3.5. 71 Since then, IKEv2 [RFC4306] has been developed, and the specification 72 for ESP has been revised [RFC4303]. This document requests 73 allocation of additional Tunnel-Type values for "IP Encapsulating 74 Security Payload in the Tunnel-mode (ESP) with IKEv2", as well as for 75 the "Secure Socket Tunneling Protocol (SSTP)" [SSTP]. 77 2. Tunnel-Type Values 79 This document defines new values for the Tunnel-Type Attribute. This 80 specification concerns the following values: 82 14 IP Encapsulating Security Payload (ESP) [RFC4303] in the 83 Tunnel-mode with IKEv2 [RFC4306] 85 15 Microsoft Secure Socket Tunneling Protocol (SSTP) 86 [SSTP] 88 3. IANA Considerations 90 This document requests assignment of new values of the RADIUS Tunnel- 91 Type Attribute by IANA in the appropriate registry [RADTYP]. 93 The new values being requested are: 95 Tunnel-Type Value 96 ========= ==== 97 IP Encapsulating Security Payload (ESP) in the 98 Tunnel-mode with IKEv2 14 99 Microsoft Secure Socket Tunneling Protocol 100 (SSTP) 15 102 Additional values of the Tunnel-Type Attribute are allocated as 103 described in [RFC2868] Section 6.1 (IETF Consensus). Allocation of 104 attribute values is also discussed in [RFC3575] Section 2.1. 106 4. Security Considerations 108 This specification neither adds to nor detracts from the security of 109 the RADIUS protocol. 111 5. References 113 5.1. Normative references 115 [RFC2865] Rigney, C., Rubens, A., Simpson, W. and S. Willens, "Remote 116 Authentication Dial In User Service (RADIUS)", RFC 2865, June 117 2000. 119 [RFC2868] Zorn, G., Leifer, D., Rubens, A., Shriver, J., Holdrege, M., 120 and I. Goyret, "RADIUS Attributes for Tunnel Protocol 121 Support", RFC 2868, June 2000. 123 [RFC3575] Aboba, B., "IANA Considerations for RADIUS", RFC 3575, July 124 2003. 126 5.2. Informative references 128 [RADTYP] Internet Assigned Numbers Authority, "RADIUS TYPES", 129 . 131 [RFC2409] Harkins, D. and D. Carrel, "The Internet Key Exchange (IKE)", 132 RFC 2409, November 1998. 134 [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", RFC 4303, 135 December 2005. 137 [RFC4306] Kaufman, C., Ed., "Internet Key Exchange (IKEv2) Protocol", 138 RFC 4306, December 2005. 140 [SSTP] "[MS-SSTP]: Secure Socket Tunneling Protocol (SSTP) 141 Specification", Microsoft Developer Network Library, 142 http://msdn.microsoft.com/en-us/library/cc247338.aspx 144 Acknowledgments 146 The authors would like to acknowledge the RADEXT WG for review of 147 this document. 149 Authors' Addresses 151 Abhishek Tiwari 152 Microsoft Corporation 153 Hyderabad, India 155 EMail: abhisht@microsoft.com 157 Full Copyright Statement 159 Copyright (C) The IETF Trust (2008). 161 This document is subject to the rights, licenses and restrictions 162 contained in BCP 78, and except as set forth therein, the authors 163 retain all their rights. 165 This document and the information contained herein are provided on an 166 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 167 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 168 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 169 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 170 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 171 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 173 Intellectual Property 175 The IETF takes no position regarding the validity or scope of any 176 Intellectual Property Rights or other rights that might be claimed to 177 pertain to the implementation or use of the technology described in 178 this document or the extent to which any license under such rights 179 might or might not be available; nor does it represent that it has 180 made any independent effort to identify any such rights. Information 181 on the procedures with respect to rights in RFC documents can be 182 found in BCP 78 and BCP 79. 184 Copies of IPR disclosures made to the IETF Secretariat and any 185 assurances of licenses to be made available, or the result of an 186 attempt made to obtain a general license or permission for the use of 187 such proprietary rights by implementers or users of this 188 specification can be obtained from the IETF on-line IPR repository at 189 http://www.ietf.org/ipr. 191 The IETF invites any interested party to bring to its attention any 192 copyrights, patents or patent applications, or other proprietary 193 rights that may cover technology that may be required to implement 194 this standard. Please address the information to the IETF at 195 ietf-ipr@ietf.org. 197 Acknowledgment 199 Funding for the RFC Editor function is provided by the IETF 200 Administrative Support Activity (IASA).