draft-ietf-radext-delegated-prefix-03.txt   draft-ietf-radext-delegated-prefix-04.txt 
Network Working Group J. Salowey Network Working Group J. Salowey
Internet-Draft R. Droms Internet-Draft R. Droms
Intended status: Standards Track Cisco Systems, Inc. Intended status: Standards Track Cisco Systems, Inc.
Expires: March 9, 2007 September 5, 2006 Expires: April 13, 2007 October 10, 2006
RADIUS Delegated-IPv6-Prefix Attribute RADIUS Delegated-IPv6-Prefix Attribute
draft-ietf-radext-delegated-prefix-03.txt draft-ietf-radext-delegated-prefix-04.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 34 skipping to change at page 1, line 34
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on March 9, 2007. This Internet-Draft will expire on April 13, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document defines a RADIUS (Remote Authentication Dial In User This document defines a RADIUS (Remote Authentication Dial In User
Service) attribute that carries an IPv6 prefix that is to be Service) attribute that carries an IPv6 prefix that is to be
delegated to the user. This attribute is usable within either RADIUS delegated to the user. This attribute is usable within either RADIUS
or Diameter. or Diameter.
1. Introduction 1. Introduction
The Delegated-IPv6-Prefix is a RADIUS attribute [1] that carries an This document defines the Delegated-IPv6-Prefix attribute as a RADIUS
IPv6 prefix to be delegated to the user, for use in the user's [1] attribute that carries an IPv6 prefix to be delegated to the
network. For example, the prefix in a Delegated-IPv6-Prefix user, for use in the user's network. For example, the prefix in a
attribute can be delegated to another node through DHCP Prefix Delegated-IPv6-Prefix attribute can be delegated to another node
Delegation [2]. through DHCP Prefix Delegation [2].
The Framed-IPv6-Prefix attribute [4] is not designed to carry an IPv6 The Delegated-IPv6-Prefix attribute can be used in DHCP Prefix
prefix to be used in the user's network, and therefore Framed-IPv6- Delegation between the delegating router and a RADIUS server, as
Prefix and Delegated-IPv6-Prefix attributes may be included in the illustrated in the following message sequence.
same RADIUS packet.
Requeting Router Delegating Router RADIUS Server
| | |
|-Solicit------------>| |
| |-Request------------------------>|
| |<--Accept(Delegated-IPv6-Prefix)-|
|<--Advertise(Prefix)-| |
|-Request(Prefix)---->| |
|<--Reply(Prefix)-----| |
| | |
DHCP PD RADIUS
The Framed-IPv6-Prefix attribute [4] is not designed to support
delegation of IPv6 prefixes 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 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [3]. document are to be interpreted as described in RFC 2119 [3].
3. Attribute format 3. Attribute format
The format of the Delegated-IPv6-Prefix is: The format of the Delegated-IPv6-Prefix is:
skipping to change at page 4, line 43 skipping to change at page 5, line 12
The text in this specification describing the applicability of the The text in this specification describing the applicability of the
Delegated-IPv6-Prefix attribute for RADIUS Accounting-Request applies Delegated-IPv6-Prefix attribute for RADIUS Accounting-Request applies
to Diameter Accounting-Request [6] as well. to Diameter Accounting-Request [6] as well.
The AVP flag rules [5] for the Delegate-IPv6-Prefix attribute are: The AVP flag rules [5] for the Delegate-IPv6-Prefix attribute are:
+---------------------+ +---------------------+
| AVP Flag rules | | AVP Flag rules |
|----+-----+----+-----|----+ |----+-----+----+-----|----+
AVP Section | | |SHLD| MUST| | AVP | | |SHLD| MUST| |
Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr| Attribute Name Code Value Type |MUST| MAY | NOT| NOT|Encr|
-----------------------------------------|----+-----+----+-----|----| ---------------------------------|----+-----+----+-----|----|
Framed-IPv6- 97 6.11.6 OctetString| M | P | | V | Y | Delegated-IPv6- TBD OctetString| M | P | | V | Y |
Prefix | | | | | | Prefix | | | | | |
---------------------------------|----+-----+----+-----|----|
6. IANA Considerations 6. IANA Considerations
IANA is requested to assign a Type value, TBD, for this attribute IANA is requested to assign a Type value, TBD, for this attribute
from the RADIUS Attribute Types registry. from the RADIUS Attribute Types registry.
7. Security Considerations 7. Security Considerations
Known security vulnerabilities of the RADIUS protocol are discussed Known security vulnerabilities of the RADIUS protocol are discussed
in RFC 2607 [8], RFC 2865 [1] and RFC 2869 [9]. Use of IPsec [10] in RFC 2607 [8], RFC 2865 [1] and RFC 2869 [9]. Use of IPsec [10]
skipping to change at page 6, line 4 skipping to change at page 6, line 21
Framed-IPv6-Prefix attribute Framed-IPv6-Prefix attribute
o Improved description of attribute fields in section 3 o Improved description of attribute fields in section 3
o Added border to table in section 3 o Added border to table in section 3
o Updated Section 4, Diameter Considerations, to describe how this o Updated Section 4, Diameter Considerations, to describe how this
attribute would be used in Diameter. attribute would be used in Diameter.
o Added reference to RFC 3588 in Section 6, Security Considerations. o Added reference to RFC 3588 in Section 6, Security Considerations.
The following changes, based on Issues 201 and 204 on the RADEXT WG The following changes, based on Issues 201 and 204 on the RADEXT WG
Issues list: http://www.drizzle.com/~aboba/RADEXT/, were made in Issues list: http://www.drizzle.com/~aboba/RADEXT/, were made in
revision -03 of this document: revision -03 of this document:
o Updated Section 5, Diameter Considerations, to describe the AVP
o Updated Section 4, Diameter Considerations, to describe the AVP
flag rules for this attribute. flag rules for this attribute.
o Edited Section 1, to clarify the relationship between the o Edited Section 1, to clarify the relationship between the
Delegated-IPv6-Prefix and Framed-IPv6-Prefix attributes. Delegated-IPv6-Prefix and Framed-IPv6-Prefix attributes.
o Edited table of attributes and moved to a separate section. o Edited table of attributes and moved to a separate section.
Revision -04 includes the following changes:
o Editorial changes in the AVP flag rules table
o Editorial changes in the description of the relationship between
the Delegated-IPv6-Prefix and Framed-IPv6-Prefix attributes (last
paragraph of section 1)
o Editorical changes in the first paragraph of section 1 to clarify
that this document defines a new attribute not already defined in
RFC 2865
o Added a text and a diagram to section 1 to illustrate the use of
the Delegated-IPv6-Prefix attribute
9. References 9. References
9.1. Normative References 9.1. Normative References
[1] Rigney, C., Willens, S., Rubens, A., and W. Simpson, "Remote [1] Rigney, C., Willens, S., Rubens, A., and W. Simpson, "Remote
Authentication Dial In User Service (RADIUS)", RFC 2865, Authentication Dial In User Service (RADIUS)", RFC 2865,
June 2000. June 2000.
[2] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host [2] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host
Configuration Protocol (DHCP) version 6", RFC 3633, Configuration Protocol (DHCP) version 6", RFC 3633,
 End of changes. 9 change blocks. 
18 lines changed or deleted 44 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/