draft-ietf-dhc-dhcpv6-subid-00.txt   draft-ietf-dhc-dhcpv6-subid-01.txt 
DHC B. Volz DHC B. Volz
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: October 9, 2005 April 07, 2005 Expires: September 5, 2006 March 4, 2006
DHCPv6 Relay Agent Subscriber-ID Option DHCPv6 Relay Agent Subscriber-ID Option
draft-ietf-dhc-dhcpv6-subid-00.txt draft-ietf-dhc-dhcpv6-subid-01.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 33 skipping to change at page 1, line 33
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 October 9, 2005. This Internet-Draft will expire on September 5, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Terminology . . . . . . . . . . . . . . . . . . . 3 2. Requirements Terminology . . . . . . . . . . . . . . . . . . . 3
3. The Relay Agent Subscriber-ID Option . . . . . . . . . . . . . 3 3. The Relay Agent Subscriber-ID Option . . . . . . . . . . . . . 3
4. DHCPv6 Relay Agent Behavior . . . . . . . . . . . . . . . . . 4 4. DHCPv6 Relay Agent Behavior . . . . . . . . . . . . . . . . . . 4
5. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . . . . 4 5. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . 4 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
9.1 Normative References . . . . . . . . . . . . . . . . . . . 5 9.1. Normative References . . . . . . . . . . . . . . . . . . . 5
9.2 Informative References . . . . . . . . . . . . . . . . . . 5 9.2. Informative References . . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7
Intellectual Property and Copyright Statements . . . . . . . . 6 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.
skipping to change at page 3, line 50 skipping to change at page 3, line 50
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 subscriber moves from one access-point to another, for
example, would not require reconfiguration at the service provider's example, would not require reconfiguration at the service provider's
DHCPv6 servers. DHCPv6 servers.
The subscriber-id is an NVT ASCII [4] string. The semantic contents The subscriber-id information is only intended for use within a
of the subscriber-id field are of course provider-specific. This single administrative domain and is only exchanged between the relay
specification does not establish any semantic requirements on the agents and DHCPv6 servers within that domain. Therefore, the format
data in the string. of and encoding of the data in the option is not standardized and
this specification does not establish any semantic requirements on
the data. This specification only defines the option for conveying
this information from relay agents to DHCPv6 servers.
However, as the DHCPv4 Subscriber-ID suboption [4] specifies NVT
ASCII [5] encoded data, in environments where both DHCPv4 [6] 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 (TBD)
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 A NVT ASCII string. It MUST NOT be null subscriber-id The subscriber's identity.
terminated.
4. DHCPv6 Relay Agent Behavior 4. 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. The subscriber-id option in relayed (RELAY-FORW) DHCPv6 messages. How the
strings themselves are assigned and configured through mechanisms subscriber-id is assigned and the mechanisms used to configure it are
that are outside the scope of this memo. outside the scope of this memo.
5. DHCPv6 Server Behavior 5. DHCPv6 Server Behavior
This option provides additional information to the DHCPv6 server. This option provides additional information to the DHCPv6 server.
The DHCPv6 server, if it is configured to support this option, MAY The DHCPv6 server MAY use this information, if available, in addition
use this information in addition to other relay agent option data, to other relay agent option data, other options included in the
other options included in the DHCPv6 client messages, and physical DHCPv6 client messages, and physical network topology information in
network topology information in order to assign IP addresses, order to assign IP addresses, delegate prefixes, and/or other
delegate prefixes, and/or other configuration parameters to the configuration parameters to the client. There is no special
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 6. Security Considerations
See [1] section 21.1, on securing DHCPv6 messages sent between As the subscriber-id option is only exchanged between relay agents
servers and relay agents, and section 23, on general DHCPv6 security and DHCPv6 servers, [1] section 21.1, provides details on securing
considerations. DHCPv6 messages sent between servers and relay agents. And, [1]
section 23, provides general DHCPv6 security considerations.
7. IANA Considerations 7. IANA Considerations
IANA is requested to assign a DHCPv6 option code for the Relay Agent IANA is requested to assign a DHCPv6 option code for the Relay Agent
Subscriber-ID Option. Subscriber-ID Option.
8. Acknowledgements 8. 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 verison of their memo [5]. document is essentially an edited version of their memo [4].
9. References 9. References
9.1 Normative References 9.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 [2] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
9.2 Informative References 9.2. Informative References
[3] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host [3] 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 2003. December 2003.
[4] Postel, J. and J. Reynolds, "Telnet Protocol Specification", [4] Johnson, R., Palaniappan, T., and M. Stapp, "Subscriber-ID
STD 8, RFC 854, May 1983.
[5] 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",
STD 8, RFC 854, May 1983.
[6] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131,
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
skipping to change at page 6, line 41 skipping to change at page 8, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 18 change blocks. 
37 lines changed or deleted 47 lines changed or added

This html diff was produced by rfcdiff 1.29, available from http://www.levkowetz.com/ietf/tools/rfcdiff/