draft-ietf-dhc-dhcpv6-subid-01.txt   rfc4580.txt 
DHC B. Volz Network Working Group B. Volz
Internet-Draft Cisco Systems, Inc. Request for Comments: 4580 Cisco Systems, Inc.
Expires: September 5, 2006 March 4, 2006
DHCPv6 Relay Agent Subscriber-ID Option
draft-ietf-dhc-dhcpv6-subid-01.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
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 Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
http://www.ietf.org/ietf/1id-abstracts.txt. Relay Agent Subscriber-ID Option
The list of Internet-Draft Shadow Directories can be accessed at Status of This Memo
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 5, 2006. This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This memo defines a new Relay Agent Subscriber-ID option for the This memo defines a new Relay Agent Subscriber-ID option for the
Dynamic Host Configuration Protocol for IPv6 (DHCPv6). The option Dynamic Host Configuration Protocol for IPv6 (DHCPv6). The option
allows a DHCPv6 relay agent to associate a stable "Subscriber-ID" allows a DHCPv6 relay agent to associate a stable "Subscriber-ID"
with DHCPv6 client messages in a way that is independent of the with DHCPv6 client messages in a way that is independent of the
client and of the underlying physical network infrastructure. client and of the underlying physical network infrastructure.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction ....................................................2
2. Requirements Terminology . . . . . . . . . . . . . . . . . . . 3 2. The Relay Agent Subscriber-ID Option ............................2
3. The Relay Agent Subscriber-ID Option . . . . . . . . . . . . . 3 3. DHCPv6 Relay Agent Behavior .....................................3
4. DHCPv6 Relay Agent Behavior . . . . . . . . . . . . . . . . . . 4 4. DHCPv6 Server Behavior ..........................................3
5. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations .........................................4
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 6. IANA Considerations .............................................4
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 7. Acknowledgements ................................................4
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 8. References ......................................................4
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 8.1. Normative References .......................................4
9.1. Normative References . . . . . . . . . . . . . . . . . . . 5 8.2. Informative References .....................................4
9.2. Informative References . . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7
Intellectual Property and Copyright Statements . . . . . . . . . . 8
1. Introduction 1. Introduction
DHCPv6 [1] provides IP addresses and configuration information for DHCPv6 [1] provides IP addresses and configuration information for
IPv6 clients. It includes a relay agent capability, in which IPv6 clients. It includes a relay agent capability, in which
processes within the network infrastructure receive multicast processes within the network infrastructure receive multicast
messages from clients and relay them to DHCPv6 servers. In some messages from clients and relay them to DHCPv6 servers. In some
network environments, it will be useful for the relay agent to add network environments, it will be useful for the relay agent to add
information to the DHCPv6 message before relaying it. information to the DHCPv6 message before relaying it.
The information that relay agents supply can also be used in the The information that relay agents supply can also be used in the
server's decision making about the addresses, delegated prefixes [3], server's decision-making about the addresses, delegated prefixes [2],
and configuration parameters that the client is to receive. and configuration parameters that the client is to receive.
In many service provider environments, it is believed to be desirable In many service-provider environments, it is believed to be desirable
to associate some provider-specific information with clients' DHCPv6 to associate some provider-specific information with clients' DHCPv6
messages that is independent of the physical network configuration messages that is independent of the physical network configuration
and which the relay agent has learned through some means which is and that the relay agent has learned through some means that is
outside the scope of this memo. outside the scope of this memo.
2. Requirements Terminology 2. The Relay Agent Subscriber-ID Option
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 [2].
3. The Relay Agent Subscriber-ID Option
In complex service provider environments, there is a need to connect In complex service provider environments, there is a need to connect
a customer's DHCPv6 configuration with the customer's administrative a customer's DHCPv6 configuration with the customer's administrative
information. The Relay Agent Subscriber-ID option carries a value information. The Relay Agent Subscriber-ID option carries a value
that can be independent of the physical network configuration through that can be independent of the physical network configuration through
which the subscriber is connected. This value complements, and might which the subscriber is connected. This value complements, and might
well be used in addition to, the network-based information. The well be used in addition to, the network-based information. The
"subscriber-id" assigned by the provider is intended to be stable as "subscriber-id" assigned by the provider is intended to be stable as
customers connect through different paths, and as network changes customers connect through different paths, and as network changes
occur. occur.
The subscriber-id information allows the service provider to assign/ The subscriber-id information allows the service provider to assign/
activate subscriber-specific actions, e.g. assignment of specific IP activate subscriber-specific actions; e.g., assignment of specific IP
addresses, prefixes, DNS configuration, trigger accounting, etc. addresses, prefixes, DNS configuration, trigger accounting, etc.
This option is de-coupled from the access network's physical This option is de-coupled from the access network's physical
structure, so subscriber moves from one access-point to another, for structure, so a subscriber that moves from one access-point to
example, would not require reconfiguration at the service provider's another, for example, would not require reconfiguration at the
DHCPv6 servers. service provider's DHCPv6 servers.
The subscriber-id information is only intended for use within a The subscriber-id information is only intended for use within a
single administrative domain and is only exchanged between the relay single administrative domain and is only exchanged between the relay
agents and DHCPv6 servers within that domain. Therefore, the format agents and DHCPv6 servers within that domain. Therefore, the format
of and encoding of the data in the option is not standardized and and encoding of the data in the option is not standardized, and this
this specification does not establish any semantic requirements on specification does not establish any semantic requirements on the
the data. This specification only defines the option for conveying data. This specification only defines the option for conveying this
this information from relay agents to DHCPv6 servers. information from relay agents to DHCPv6 servers.
However, as the DHCPv4 Subscriber-ID suboption [4] specifies NVT However, as the DHCPv4 Subscriber-ID suboption [3] specifies Network
ASCII [5] encoded data, in environments where both DHCPv4 [6] and Virtual Terminal (NVT) American Standard Code for Information
DHCPv6 are being used, it MAY be beneficial to use that encoding. Interchange (ASCII) [4] encoded data, in environments where both
DHCPv4 [5] and DHCPv6 are being used, it may be beneficial to use
that encoding.
The format of the DHCPv6 Relay Agent Subscriber-ID option is shown The format of the DHCPv6 Relay Agent Subscriber-ID option is shown
below: below:
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_SUBSCRIBER_ID | option-len | | OPTION_SUBSCRIBER_ID | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. subscriber-id . . subscriber-id .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code OPTION_SUBSCRIBER_ID (TBD) option-code OPTION_SUBSCRIBER_ID (38)
option-len length, in octets, of the subscriber-id field. option-len length, in octets, of the subscriber-id field.
The minimum length is 1 octet. The minimum length is 1 octet.
subscriber-id The subscriber's identity. subscriber-id The subscriber's identity.
4. DHCPv6 Relay Agent Behavior 3. DHCPv6 Relay Agent Behavior
DHCPv6 relay agents MAY be configured to include a Subscriber-ID DHCPv6 relay agents may be configured to include a Subscriber-ID
option in relayed (RELAY-FORW) DHCPv6 messages. How the option in relayed (RELAY-FORW) DHCPv6 messages. How the subscriber-
subscriber-id is assigned and the mechanisms used to configure it are id is assigned and the mechanisms used to configure it are outside
outside the scope of this memo. the scope of this memo.
5. DHCPv6 Server Behavior 4. DHCPv6 Server Behavior
This option provides additional information to the DHCPv6 server. This option provides additional information to the DHCPv6 server.
The DHCPv6 server MAY use this information, if available, in addition The DHCPv6 server may use this information, if available, in addition
to other relay agent option data, other options included in the to other relay agent option data, other options included in the
DHCPv6 client messages, and physical network topology information in DHCPv6 client messages, and physical network topology information in
order to assign IP addresses, delegate prefixes, and/or other order to assign IP addresses, delegate prefixes, and/or other
configuration parameters to the client. There is no special configuration parameters to the client. There is no special
additional processing for this option. additional processing for this option.
There is no requirement that a server return this option and its data There is no requirement that a server return this option and its data
in a RELAY-REPLY message. in a RELAY-REPLY message.
6. Security Considerations 5. Security Considerations
As the subscriber-id option is only exchanged between relay agents As the subscriber-id option is only exchanged between relay agents
and DHCPv6 servers, [1] section 21.1, provides details on securing and DHCPv6 servers, [1], Section 21.1, provides details on securing
DHCPv6 messages sent between servers and relay agents. And, [1] DHCPv6 messages sent between servers and relay agents. [1], Section
section 23, provides general DHCPv6 security considerations. 23, provides general DHCPv6 security considerations.
7. IANA Considerations 6. IANA Considerations
IANA is requested to assign a DHCPv6 option code for the Relay Agent IANA has assigned a DHCPv6 option code (38) for the Relay Agent
Subscriber-ID Option. Subscriber-ID Option.
8. Acknowledgements 7. Acknowledgements
Thanks to Richard Johnson, Theyn Palaniappan, and Mark Stapp as this Thanks to Richard Johnson, Theyn Palaniappan, and Mark Stapp as this
document is essentially an edited version of their memo [4]. document is essentially an edited version of their memo [3].
9. References 8. References
9.1. Normative References 8.1. Normative References
[1] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. [1] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M.
Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",
RFC 3315, July 2003. RFC 3315, July 2003.
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement 8.2. Informative References
Levels", BCP 14, RFC 2119, March 1997.
9.2. Informative References
[3] 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, December
December 2003. 2003.
[4] Johnson, R., Palaniappan, T., and M. Stapp, "Subscriber-ID [3] Johnson, R., Palaniappan, T., and M. Stapp, "Subscriber-ID
Suboption for the Dynamic Host Configuration Protocol (DHCP) Suboption for the Dynamic Host Configuration Protocol (DHCP)
Relay Agent Option", RFC 3993, March 2005. Relay Agent Option", RFC 3993, March 2005.
[5] Postel, J. and J. Reynolds, "Telnet Protocol Specification", [4] Postel, J. and J. Reynolds, "Telnet Protocol Specification", STD
STD 8, RFC 854, May 1983. 8, RFC 854, May 1983.
[6] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, [5] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131,
March 1997. March 1997.
Author's Address Author's Address
Bernard Volz Bernard Volz
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Ave. 1414 Massachusetts Ave.
Boxborough, MA 01719 Boxborough, MA 01719
USA USA
Phone: +1 978 936 0382 Phone: +1 978 936 0382
Email: volz@cisco.com EMail: volz@cisco.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 8, line 29 skipping to change at page 6, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity Acknowledgement
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 35 change blocks. 
110 lines changed or deleted 82 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/