| TOC |
|
This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
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 September 4, 2009.
Copyright (c) 2009 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 in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
This document specifies new IPv6 attributes for RADIUS that complement [RFC3162]. Its goal is to offer more IPv6 deployment options when StateLess Address Auto Configuration (SLAAC) or DHCP are involved.
1.
Requirements Language
2.
Introduction
3.
Attributes
3.1.
IPv6-Address Attribute
3.2.
IPv6-DNS-Server-Address
3.3.
IPv6-Prefix-Information
3.4.
Table of attributes
4.
Diameter Considerations
5.
Security Considerations
6.
IANA Considerations
7.
Acknowledgements
8.
References
8.1.
Normative References
8.2.
Informative References
§
Authors' Addresses
| TOC |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.).
| TOC |
This document specifies new IPv6 RADIUS attributes used to support IPv6 network access. As IPv6 specifies two configuration mechanisms (DHCP and SLAAC), the new attributes are targeted at both protocols when it makes sense.
| TOC |
As usual, the fields shown in the diagrams below are transmitted from left to right.
| TOC |
This Attribute indicates an IPv6 Address that is assigned to the uplink of the user equipment. It MAY be used in Access-Accept packets, and can appear multiple times. It MAY be used in an Access-Request packet as a hint by the NAS to the server that it would prefer these IPv6 address(es), but the server is not required to honor the hint. Since it is assumed that the NAS, when necessary will add a route corresponding to the address, it is not necessary for the server to also send a host Framed-IPv6-Route attribute for the same address.
This Attribute can be used by DHCPv6 to offer a unique IPv6 address or can be used for a-posteriori validation of an autoconfigured address.
A summary of the IPv6-Address Attribute format is shown below.
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Address |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- Type
TBA1 for IPv6-Address- Length
18- Address
The Address field contains a 128-bit IPv6 address.
| TOC |
The IPv6-DNS-Server-Address Attribute contains the IPv6 address of a DNS server. This attribute MAY be included multiple times in Access-Accept.
The contnet of this attribute can be inserted in a Router Advertisemnt as specified in RFc5006 or mapped to the matching DHCPv6 option.
A summary of the IPv6-DNS-Server-Address Attribute format is given below.
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Address |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- Type
TBA2 for IPv6-DNS-Server-Address- Length
18- Address
The 128-bit IPv6 address of a DNS server.
| TOC |
This Attribute provides more specific prefix information to be advertised to the user by the NAS, with the NAS interface as the intended next-hop. It is used in the Access-Accept packet and can appear multiple times.
A summary of the IPv6-Prefix-Information Attribute format is shown below.
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved | Prefix-Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. Prefix (variable) .
. .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- Type
TBA3 for IPv6-Prefix-Information- Length
At least 4 and no larger than 20; typically 12 or less.- Prefix Length
The length of the prefix, in bits; at least 0 and no more than 128; typically 64 or less.- Prefix
Variable-length field containing an IP address or a prefix of an IP address. The Prefix Length field contains the number of valid leading bits in the prefix. The bits in the prefix after the prefix length (if any) are reserved and MUST be initialized to zero by the sender and ignored by the receiver.
| TOC |
The following table provides a guide to which attributes may be found in which kinds of packets, and in what quantity.
Request Accept Reject Challenge Accounting # Attribute
Request
0+ 0+ 0 0 0+ TBA1 IPv6-Address
0+ 0+ 0 0 0+ TBA2 IPv6-DNS-Server-Address
0 0+ 0 0 0+ TBA3 IPv6-Prefix-Information
| TOC |
Since the Attributes defined in this document are allocated from the standard RADIUS type space (see Section 6 (IANA Considerations)), no special handling is required by Diameter entities.
| TOC |
TBD
| TOC |
This document requires the assignment of three new RADIUS Attribute Types in the "Radius Types" registry (currently located at http://www.iana.org/assignments/radius-types for the following attributes:
IANA should allocate these numbers from the standard RADIUS Attributes space using the "IETF Review" policy [RFC5226] (Narten, T. and H. Alvestrand, “Guidelines for Writing an IANA Considerations Section in RFCs,” May 2008.).
| TOC |
The authors would like to thank Alfred HÎnes and TBD for their contributions and comments to this document.
| TOC |
| TOC |
| [RFC2865] | Rigney, C., Willens, S., Rubens, A., and W. Simpson, “Remote Authentication Dial In User Service (RADIUS),” RFC 2865, June 2000 (TXT). |
| TOC |
| TOC |
| Benoit Lourdelet | |
| Cisco Systems, Inc. | |
| Village ent. GreenSide, Bat T3, | |
| 400, Av de Roumanille, | |
| 06410 BIOT - Sophia-Antipolis Cedex | |
| France | |
| Phone: | +33 4 97 23 26 23 |
| Email: | blourdel@cisco.com |
| Wojciech Dec | |
| Cisco Systems, Inc. | |
| Haarlerbergweg 13-19 | |
| 400, Av de Roumanille, | |
| Amsterdam , NOORD-HOLLAND 1101 CH | |
| Netherlands | |
| Phone: | +31 20 357 3034 |
| Email: | wdec@cisco.com |
| Glen Zorn | |
| Network Zen | |
| 1310 East Thomas Street | |
| Seattle, WA | |
| US | |
| Email: | gwz@net-zen.net |