--- 1/draft-ietf-radext-delegated-prefix-02.txt 2006-09-13 22:12:07.000000000 +0200 +++ 2/draft-ietf-radext-delegated-prefix-03.txt 2006-09-13 22:12:07.000000000 +0200 @@ -1,18 +1,18 @@ Network Working Group J. Salowey Internet-Draft R. Droms Intended status: Standards Track Cisco Systems, Inc. -Expires: January 11, 2007 July 10, 2006 +Expires: March 9, 2007 September 5, 2006 RADIUS Delegated-IPv6-Prefix Attribute - draft-ietf-radext-delegated-prefix-02.txt + draft-ietf-radext-delegated-prefix-03.txt Status of this Memo 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 @@ -23,46 +23,45 @@ 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 January 11, 2007. + This Internet-Draft will expire on March 9, 2007. Copyright Notice Copyright (C) The Internet Society (2006). Abstract This document defines a RADIUS (Remote Authentication Dial In User Service) attribute that carries an IPv6 prefix that is to be delegated to the user. This attribute is usable within either RADIUS or Diameter. 1. Introduction The Delegated-IPv6-Prefix is a RADIUS attribute [1] that carries an IPv6 prefix to be delegated to the user, for use in the user's network. For example, the prefix in a Delegated-IPv6-Prefix attribute can be delegated to another node through DHCP Prefix Delegation [2]. - The Framed-IPv6-Prefix attribute [4] serves a similar purpose, but - may also be used for other purposes other than delegating a prefix - for use in a user's network. Definition of the Delegated-IPv6-Prefix - allows the simultaneous use of the Framed-IPv6-Prefix for other - purposes and the Delegated-IPv6-Prefix for prefix delegation. + The Framed-IPv6-Prefix attribute [4] is not designed to carry an IPv6 + prefix to be used in the user's network, and therefore Framed-IPv6- + Prefix and Delegated-IPv6-Prefix attributes may be included in the + same RADIUS packet. 2. Terminology 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 RFC 2119 [3]. 3. Attribute format The format of the Delegated-IPv6-Prefix is: @@ -98,48 +97,51 @@ Prefix-Length The length of the prefix being delegated, in bits. At least 0 and no larger than 128 bits (identifying a single IPv6 address) Note that the prefix field is only required to be long enough to hold the prefix bits and can be shorter than 16 bytes. Any bits in the prefix field that are not part of the prefix MUST be zero. - The definition of the Delegated-IPv6-Prefix Attribute is based on the - Framed-IPv6-Prefix attribute [4]. - The Delegated-IPv6-Prefix MAY appear in an Access-Accept packet, and can appear multiple times. It MAY appear in an Access-Request packet as a hint by the NAS to the server that it would prefer these prefix(es), but the server is not required to honor the hint. The Delegated-IPv6-Prefix attribute MAY appear in an Accounting- Request packet. The Delegated-IPv6-Prefix MUST NOT appear in any other RADIUS packets. - The following table describes which messages the Delegated-IPv6- - Prefix attribute can appear in and in what quantity. +4. Table of Attributes - +------------------------------------------------------+ - | Request Accept Accounting # Attribute | + 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+ TBD Delegated-IPv6-Prefix | - +------------------------------------------------------+ +| 0+ 0+ 0 0 0+ TBD Delegated-IPv6-Prefix | ++-----------------------------------------------------------------------+ - In this table 0+ means that zero or more instances of this attribute - MAY be present in packet. This attribute MUST NOT appear in any - packet not listed in the table. + The meaning of the above table entries is as follows: + 0 This attribute MUST NOT be present. -4. Diameter Considerations + 0+ Zero or more instances of this attribute MAY be present. + 0-1 Zero or one instance of this attribute MAY be present. + 1 Exactly one instance of this attribute MUST be present. + 1+ One or more of these attributes MUST be present. + +5. Diameter Considerations When used in Diameter, the attribute defined in this specification can be used as a Diameter AVP from the Code space 1-255, i.e., RADIUS attribute compatibility space. No additional Diameter Code values are therefore allocated. The data types of the attributes are as follows: Delegated-IPv6-Prefix OctetString The attribute in this specification has no special translation @@ -153,36 +155,47 @@ Diameter to AA-Request [6] or Diameter-EAP-Request [7]. The text in this specification describing the applicability of the Delegated-IPv6-Prefix attribute for RADIUS Access-Accept applies in Diameter to AA-Answer or Diameter-EAP-Answer that indicates success. The text in this specification describing the applicability of the Delegated-IPv6-Prefix attribute for RADIUS Accounting-Request applies to Diameter Accounting-Request [6] as well. -5. IANA Considerations + The AVP flag rules [5] for the Delegate-IPv6-Prefix attribute are: + + +---------------------+ + | AVP Flag rules | + |----+-----+----+-----|----+ + AVP Section | | |SHLD| MUST| | + Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr| + -----------------------------------------|----+-----+----+-----|----| + Framed-IPv6- 97 6.11.6 OctetString| M | P | | V | Y | + Prefix | | | | | | + +6. IANA Considerations IANA is requested to assign a Type value, TBD, for this attribute from the RADIUS Attribute Types registry. -6. Security Considerations +7. Security Considerations Known security vulnerabilities of the RADIUS protocol are discussed in RFC 2607 [8], RFC 2865 [1] and RFC 2869 [9]. Use of IPsec [10] for providing security when RADIUS is carried in IPv6 is discussed in RFC 3162. Security considerations for the Diameter protocol are discussed in RFC 3588 [5]. -7. Change Log +8. Change Log This section to be removed before publication as an RFC. The following changes were made in revision -01 of this document: o Added additional details to Abstract; defined that this attribute can be used in both RADIUS and Diameter. (Issue 188) o Moved and clarified text describing which packets this attribute can appear in adjacent to table in section 3. (Issue 188) o Fixed RFC 2119 boilerplate in section 2. (Issue 185) o Fixed table in section 3 to clarify which packets this attribute @@ -195,36 +208,46 @@ The following changes were made in revision -02 of this document: o Added a second paragraph to the Introduction, referencing the Framed-IPv6-Prefix attribute o Improved description of attribute fields in section 3 o Added border to table in section 3 o Updated Section 4, Diameter Considerations, to describe how this attribute would be used in Diameter. o Added reference to RFC 3588 in Section 6, Security Considerations. -8. References + The following changes, based on Issues 201 and 204 on the RADEXT WG + Issues list: http://www.drizzle.com/~aboba/RADEXT/, were made in + revision -03 of this document: -8.1. Normative References + o Updated Section 4, Diameter Considerations, to describe the AVP + flag rules for this attribute. + o Edited Section 1, to clarify the relationship between the + Delegated-IPv6-Prefix and Framed-IPv6-Prefix attributes. + o Edited table of attributes and moved to a separate section. + +9. References + +9.1. Normative References [1] Rigney, C., Willens, S., Rubens, A., and W. Simpson, "Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June 2000. [2] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6", RFC 3633, December 2003. [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. -8.2. Non-normative References +9.2. Non-normative References [4] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", RFC 3162, August 2001. [5] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko, "Diameter Base Protocol", RFC 3588, September 2003. [6] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter Network Access Server Application", RFC 4005, August 2005.