idnits 2.17.1 draft-aboba-radius-ipv6-09.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents -- however, there's a paragraph with a matching beginning. Boilerplate error? == The page length should not exceed 58 lines per page, but there was 10 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 11 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 3 instances of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 478 has weird spacing: '...>, and expir...' == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The exact meaning of the all-uppercase expression 'MAY NOT' is not defined in RFC 2119. If it is intended as a requirements expression, it should be rewritten using one of the combinations defined in RFC 2119; otherwise it should not be all-uppercase. == The expression 'MAY NOT', while looking like RFC 2119 requirements text, is not defined in RFC 2119, and should not be used. Consider using 'MUST NOT' instead (if that is what you mean). Found 'MAY NOT' in this paragraph: However, where RADIUS is run over IPSEC ESP with a non-null transform, the secret shared between the NAS and the RADIUS server MAY NOT be configured. In this case, a shared secret of zero length MUST be assumed. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '5' is defined on line 344, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 359, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2044 (ref. '2') (Obsoleted by RFC 2279) ** Downref: Normative reference to an Informational RFC: RFC 2607 (ref. '3') ** Downref: Normative reference to an Informational RFC: RFC 2866 (ref. '5') ** Downref: Normative reference to an Informational RFC: RFC 2867 (ref. '6') ** Downref: Normative reference to an Informational RFC: RFC 2868 (ref. '7') ** Downref: Normative reference to an Informational RFC: RFC 2869 (ref. '8') ** Obsolete normative reference: RFC 2401 (ref. '9') (Obsoleted by RFC 4301) ** Obsolete normative reference: RFC 2434 (ref. '10') (Obsoleted by RFC 5226) ** Obsolete normative reference: RFC 2472 (ref. '11') (Obsoleted by RFC 5072, RFC 5172) ** Obsolete normative reference: RFC 2460 (ref. '13') (Obsoleted by RFC 8200) ** Obsolete normative reference: RFC 1933 (ref. '15') (Obsoleted by RFC 2893) Summary: 17 errors (**), 0 flaws (~~), 8 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Bernard Aboba 3 INTERNET-DRAFT Microsoft 4 Category: Standards Track Glen Zorn 5 Cisco Systems 6 13 June 2001 Dave Mitton 7 Nortel Networks 9 RADIUS and IPv6 11 This document is an Internet-Draft and is in full conformance with all 12 provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering Task 15 Force (IETF), its areas, and its working groups. Note that other groups 16 may also distribute working documents as Internet- Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet-Drafts as reference material 21 or to cite them other than as "work in progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 1. Copyright Notice 31 Copyright (C) The Internet Society (2001). All Rights Reserved. 33 2. Abstract 35 This document specifies the operation of RADIUS when run over IPv6 as 36 well as the RADIUS attributes used to support IPv6 network access. 38 3. Introduction 40 This document specifies the operation of RADIUS [4]-[8] over IPv6 [13] 41 as well as the RADIUS attributes used to support IPv6 network access. 43 Note that a NAS sending a RADIUS Access-Request may not know a-priori 44 whether the host will be using IPv4, IPv6, or both. For example, within 45 PPP, IPv6CP [11] occurs after LCP, so that address assignment will not 46 occur until after RADIUS authentication and authorization has completed. 48 Therefore it is presumed that the IPv6 attributes described in this 49 document MAY be sent along with IPv4-related attributes within the same 50 RADIUS message and that the NAS will decide which attributes to use. The 51 NAS SHOULD only allocate addresses and prefixes that the client can 52 actually use, however. For example, there is no need for the NAS to 53 reserve use of an IPv4 address for a host that only supports IPv6; 54 similarly, a host only using IPv4 or 6to4 [12] does not require 55 allocation of an IPv6 prefix. 57 The NAS can provide IPv6 access natively, or alternatively, via other 58 methods such as IPv6 within IPv4 tunnels [15] or 6over4 [14]. The choice 59 of method for providing IPv6 access has no effect on RADIUS usage per 60 se, although if it is desired that an IPv6 within IPv4 tunnel be opened 61 to a particular location, then tunnel attributes should be utilized, as 62 described in [6],[7]. 64 3.1. Requirements language 66 In this document, the key words "MAY", "MUST, "MUST NOT", "optional", 67 "recommended", "SHOULD", and "SHOULD NOT", are to be interpreted as 68 described in [1]. 70 4. Attributes 72 4.1. NAS-IPv6-Address 74 Description 76 This Attribute indicates the identifying IPv6 Address of the NAS 77 which is requesting authentication of the user, and SHOULD be unique 78 to the NAS within the scope of the RADIUS server. NAS-IPv6-Address 79 is only used in Access-Request packets. NAS-IPv6-Address and/or NAS- 80 IP-Address MAY be present in an Access-Request packet; however, if 81 neither attribute is present then NAS-Identifier MUST be present. 83 A summary of the NAS-IPv6-Address Attribute format is shown below. The 84 fields are transmitted from left to right. 86 0 1 2 3 87 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 88 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 89 | Type | Length | Address 90 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 91 Address 92 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 93 Address 94 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 95 Address 96 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 97 Address | 98 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 100 Type 102 TBD for NAS-IPv6-Address 104 Length 106 18 108 Address 110 The Address field is 16 octets. 112 4.2. Framed-Interface-Id 114 Description 116 This Attribute indicates the IPv6 interface identifier to be 117 configured for the user. It MAY be used in Access-Accept packets. If 118 the Interface-Identifier IPv6CP option [11] has been successfully 119 negotiated, this Attribute MUST be included in an Access-Request 120 packet as a hint by the NAS to the server that it would prefer that 121 value. It is recommended, but not required, that the server honor the 122 hint. 124 A summary of the Framed-Interface-Id Attribute format is shown below. 125 The fields are transmitted from left to right. 127 0 1 2 3 128 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 130 | Type | Length | Interface-Id 131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 132 Interface-Id 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 Interface-Id | 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 137 Type 139 TBD for Framed-Interface-Id 141 Length 143 10 145 Interface-Id 147 The Interface-Id field is 8 octets. 149 4.3. Framed-IPv6-Prefix 151 Description 153 This Attribute indicates an IPv6 prefix (and corresponding route) to 154 be configured for the user. It MAY be used in Access-Accept packets. 155 It MAY be used in an Access-Request packet as a hint by the NAS to 156 the server that it would prefer that prefix, but the server is not 157 required to honor the hint. Since it is assumed that the NAS will 158 plumb a route corresponding to the assigned prefix, it is not 159 necessary for the server to also send a Framed-IPv6-Route attribute 160 with the same information. 162 A summary of the Framed-IPv6-Prefix Attribute format is shown below. 163 The fields are transmitted from left to right. 165 0 1 2 3 166 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 167 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 168 | Type | Length | Reserved | Prefix-Length | 169 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 170 Prefix 171 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 172 Prefix 173 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 174 Prefix 175 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 176 Prefix | 177 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 179 Type 181 TBD for Framed-IPv6-Prefix 183 Length 185 At least 3 and no larger than 20. 187 Reserved 189 This field, which is reserved and MUST be present, is always set to 190 zero. 192 Prefix-Length 194 The length of the prefix, in bits. At least 0 and no larger than 128. 196 Prefix 198 The Prefix field is up to 16 octets in length. Bits outside of the 199 Prefix-Length, if included, must be zero. 201 4.4. Login-IPv6-Host 203 Description 205 This Attribute indicates the system with which to connect the user, 206 when the Login-Service Attribute is included. It MAY be used in 207 Access-Accept packets. It MAY be used in an Access-Request packet as 208 a hint to the server that the NAS would prefer to use that host, but 209 the server is not required to honor the hint. 211 A summary of the Login-IPv6-Host Attribute format is shown below. The 212 fields are transmitted from left to right. 214 0 1 2 3 215 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 217 | Type | Length | Address 218 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 219 Address 220 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 221 Address 222 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 223 Address 224 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 225 Address | 226 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 228 Type 230 TBD for Login-IPv6-Host 232 Length 234 18. 236 Address 238 The Address field is 16 octets in length. The value 239 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF indicates that the NAS SHOULD 240 allow the user to select an address or name to be connected to. The 241 value 0 indicates that the NAS SHOULD select a host to connect the 242 user to. Other values indicate the address the NAS SHOULD connect the 243 user to. 245 4.5. Framed-IPv6-Route 247 Description 249 This Attribute provides routing information to be configured for the 250 user on the NAS. It is used in the Access-Accept packet and can 251 appear multiple times. 253 A summary of the Framed-IPv6-Route Attribute format is shown below. The 254 fields are transmitted from left to right. 256 0 1 2 257 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 258 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 259 | Type | Length | Text ... 260 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 262 Type 264 TBD for Framed-IPv6-Route 266 Length 268 >=3 270 Text 272 The Text field is one or more octets, and its contents are 273 implementation dependent. It is intended to be human readable and 274 MUST NOT affect operation of the protocol. It is recommended that 275 the message contain UTF-8 encoded 10646 [2] characters. 277 For IPv6 routes, it SHOULD contain a destination prefix optionally 278 followed by a slash and a decimal length specifier stating how many 279 high order bits of the prefix to use. That is followed by a space, a 280 gateway address, a space, and one or more metrics separated by 281 spaces. 283 Whenever the gateway address is specified as zero the IPv6 address of 284 the user SHOULD be used as the gateway address. 286 4.6. Framed-IPv6-Pool 288 Description 290 This Attribute contains the name of an assigned pool that SHOULD be 291 used to assign an IPv6 prefix for the user. If a NAS does not 292 support multiple prefix pools, the NAS MUST ignore this Attribute. 294 A summary of the Framed-IPv6-Pool Attribute format is shown below. The 295 fields are transmitted from left to right. 297 0 1 2 298 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 299 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 300 | Type | Length | String... 301 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 303 Type 305 TBD for Framed-IPv6-Pool 307 Length 309 >= 3 311 String 313 The string field contains the name of an assigned IPv6 prefix pool 314 configured on the NAS. 316 5. Table of Attributes 318 The following table provides a guide to which attributes may be found in 319 which kinds of packets, and in what quantity. 321 Request Accept Reject Challenge Accounting # Attribute 322 Request 323 0-1 0 0 0 0-1 TBD NAS-IPv6-Address 324 0-1 0-1 0 0 0-1 TBD Framed-Interface-Id 325 0+ 0+ 0 0 0+ TBD Framed-IPv6-Prefix 326 0+ 0+ 0 0 0+ TBD Login-IPv6-Host 327 0 0+ 0 0 0+ TBD Framed-IPv6-Route 328 0 0-1 0 0 0-1 TBD Framed-IPv6-Pool 330 6. References 332 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 333 Levels", RFC 2119, March, 1997. 335 [2] Yergeau, F., "UTF-8, a transformation format of Unicode and ISO 336 10646", RFC 2044, October 1996. 338 [3] Aboba, B., and Vollbrecht, J., "Proxy Chaining and Policy 339 Implementation in Roaming", RFC 2607, June 1999. 341 [4] Rigney, C., Rubens, A., Simpson, W., Willens, S., "Remote 342 Authentication Dial In User Service (RADIUS)", RFC 2865, June 2000. 344 [5] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000. 346 [6] Zorn, G., Mitton, D., Aboba, B., "RADIUS Accounting Modifications 347 for Tunnel Protocol Support", RFC 2867, June 2000. 349 [7] Zorn, G., Leifer, D., Rubens, A., Shriver, J., Holdrege, M., 350 Goyret, I., "RADIUS Attributes for Tunnel Protocol Support", RFC 351 2868, June 2000. 353 [8] Rigney, C., Willats, W., Calhoun, P., "RADIUS Extensions", RFC 354 2869, June 2000. 356 [9] Kent S., Atkinson, R., "Security Architecture for the Internet 357 Protocol", RFC 2401, November 1998. 359 [10] Alvestrand, H. and T. Narten, "Guidelines for Writing an IANA 360 Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. 362 [11] Haskin, D., and Allen, E., "IP Version 6 over PPP", RFC 2472, 363 December 1998. 365 [12] Carpenter, B., Moore, K., "Connection of IPv6 Domains via IPv4 366 Clouds", RFC 3056, February 2001. 368 [13] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) 369 Specification", RFC 2460, December 1998. 371 [14] Carpenter, B. and C. Jung, "Transmission of IPv6 over IPv4 Domains 372 without Explicit Tunnels", RFC 2529, March 1999. 374 [15] Gilligan, R. and E. Nordmark, "Transition Mechanisms for IPv6 Hosts 375 and Routers", RFC 1933, April 1996. 377 7. Security Considerations 379 This draft describes the use of RADIUS for the purposes of 380 authentication, authorization and accounting in IPv6-enabled networks. 381 In such networks, the RADIUS protocol may run either over IPv4 or over 382 IPv6. Known security vulnerabilities of the RADIUS protocol are 383 described in [3],[4] and [8]. 385 Since IPSEC [9] is mandatory to implement for IPv6, it is expected that 386 running RADIUS implementations supporting IPv6 will typically run over 387 IPSEC. Where RADIUS is run over IPSEC and where certificates are used 388 for authentication, it may be desirable to avoid management of RADIUS 389 shared secrets, so as to leverage the improved scalability of public key 390 infrastructure. 392 Within RADIUS, a shared secret is used for hiding of attributes such as 393 User-Password [4] and Tunnel-Password [7]. In addition, the shared 394 secret is used in computation of the Response Authenticator [4], as well 395 as the Message-Authenticator attribute [8]. Therefore, in RADIUS a 396 shared secret is used to provide confidentiality as well as integrity 397 protection and authentication. As a result, only use of IPSEC ESP with a 398 non-null transform can provide security services sufficient to 399 substitute for RADIUS application-layer security. Therefore, where IPSEC 400 AH or ESP null is used, it will typically still be necessary to 401 configure a RADIUS shared secret. 403 However, where RADIUS is run over IPSEC ESP with a non-null transform, 404 the secret shared between the NAS and the RADIUS server MAY NOT be 405 configured. In this case, a shared secret of zero length MUST be 406 assumed. 408 8. IANA Considerations 410 This draft requires the assignment of six new RADIUS attribute numbers 411 for the following attributes: 413 NAS-IPv6-Address 414 Framed-Interface-Id 415 Framed-IPv6-Prefix 416 Login-IPv6-Host 417 Framed-IPv6-Route 418 Framed-IPv6-Pool 420 9. Acknowledgments 422 The authors would like to acknowledge Jun-ichiro itojun Hagino of IIJ 423 Research Laboratory, Darran Potter of Cisco and Carl Rigney of Lucent 424 for contributions to this document. 426 10. Authors' Addresses 428 Bernard Aboba 429 Microsoft Corporation 430 One Microsoft Way 431 Redmond, WA 98052 433 EMail: bernarda@microsoft.com 434 Phone: +1 425 936 6605 435 Fax: +1 425 936 7329 436 Glen Zorn 437 Cisco Systems, Inc. 438 500 108th Avenue N.E., Suite 500 439 Bellevue, WA 98004 441 Phone: +1 425 468 0955 442 Email: gwz@cisco.com 444 Dave Mitton 445 Nortel Networks 446 880 Technology Park Drive 447 Billerica, MA 01821 449 Phone: +1 978 288 4570 450 Fax: +1 978 288 3030 451 EMail: dmitton@nortelnetworks.com 453 11. Full Copyright Statement 455 Copyright (C) The Internet Society (2001). All Rights Reserved. 456 This document and translations of it may be copied and furnished to 457 others, and derivative works that comment on or otherwise explain it or 458 assist in its implementation may be prepared, copied, published and 459 distributed, in whole or in part, without restriction of any kind, 460 provided that the above copyright notice and this paragraph are included 461 on all such copies and derivative works. However, this document itself 462 may not be modified in any way, such as by removing the copyright notice 463 or references to the Internet Society or other Internet organizations, 464 except as needed for the purpose of developing Internet standards in 465 which case the procedures for copyrights defined in the Internet 466 Standards process must be followed, or as required to translate it into 467 languages other than English. The limited permissions granted above are 468 perpetual and will not be revoked by the Internet Society or its 469 successors or assigns. This document and the information contained 470 herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE 471 INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 472 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 473 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 474 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." 476 12. Expiration Date 478 This memo is filed as , and expires 479 January 1, 2002.