draft-ietf-dhc-relay-id-suboption-01.txt   draft-ietf-dhc-relay-id-suboption-02.txt 
DHC M. Stapp DHC M. Stapp
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: March 23, 2009 September 19, 2008 Expires: March 23, 2009 September 19, 2008
The DHCPv4 Relay Agent Identifier Suboption The DHCPv4 Relay Agent Identifier Suboption
draft-ietf-dhc-relay-id-suboption-01.txt draft-ietf-dhc-relay-id-suboption-02.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 2, line 15 skipping to change at page 2, line 15
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Example Use-Cases . . . . . . . . . . . . . . . . . . . . . . . 3 3. Example Use-Cases . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Industrial Ethernet . . . . . . . . . . . . . . . . . . . . 3 3.1. Industrial Ethernet . . . . . . . . . . . . . . . . . . . . 3
3.2. Bulk Leasequery . . . . . . . . . . . . . . . . . . . . . . 4 3.2. Bulk Leasequery . . . . . . . . . . . . . . . . . . . . . . 4
4. Suboption Format . . . . . . . . . . . . . . . . . . . . . . . 4 4. Suboption Format . . . . . . . . . . . . . . . . . . . . . . . 4
5. Relay Identifier Types . . . . . . . . . . . . . . . . . . . . 5 5. Relay Identifier Types . . . . . . . . . . . . . . . . . . . . 5
6. Generating a Relay Identifier . . . . . . . . . . . . . . . . . 5 6. Generating a Relay Identifier . . . . . . . . . . . . . . . . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 7. Identifier Stability . . . . . . . . . . . . . . . . . . . . . 5
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
9.1. Normative References . . . . . . . . . . . . . . . . . . . 6 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
9.2. Informative References . . . . . . . . . . . . . . . . . . 6 10.1. Normative References . . . . . . . . . . . . . . . . . . . 6
10.2. Informative References . . . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7
Intellectual Property and Copyright Statements . . . . . . . . . . 8 Intellectual Property and Copyright Statements . . . . . . . . . . 8
1. Introduction 1. Introduction
The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) [RFC2131] The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) [RFC2131]
provides IP addresses and configuration information for IPv4 clients. provides IP addresses and configuration information for IPv4 clients.
It includes a relay agent capability, in which network elements It includes a relay agent capability, in which network elements
receive broadcast messages from clients and forward them to DHCP receive broadcast messages from clients and forward them to DHCP
servers as unicast messages. In many network environments, relay servers as unicast messages. In many network environments, relay
skipping to change at page 5, line 27 skipping to change at page 5, line 27
As described in Section 1, in some situations it may be useful for As described in Section 1, in some situations it may be useful for
network devices to generate identifiers themselves. Relay agents who network devices to generate identifiers themselves. Relay agents who
send the Relay Agent Identifier suboption using identifiers that are send the Relay Agent Identifier suboption using identifiers that are
not administratively-configured MUST be generated following the not administratively-configured MUST be generated following the
procedures in the DUID section of [RFC3315]. Relay agents who use procedures in the DUID section of [RFC3315]. Relay agents who use
generated identifiers SHOULD make the generated value visible to generated identifiers SHOULD make the generated value visible to
their administrators via their user-interface, through a log entry, their administrators via their user-interface, through a log entry,
or through some other mechanism. or through some other mechanism.
7. Security Considerations 7. Identifier Stability
If the relay identifier is to be meaningful it has to be stable. The
identifier associated with a relay device SHOULD be committed to
stable storage. This applies to all identifier types.
Implementors should note that the identifier needs to be present in
all DHCP message types where its value is being used by the DHCP
server. The relay agent may not be able to add the Relay Agent
Information option to all messages - such as RENEW messages sent as
IP unicasts. In some deployments that might mean that the server has
to be willing to continue to associate the relay-identifier it has
last seen with a lease that is being RENEWed. Other deployments may
prefer to use the Server Identifier Override suboption [RFC5107] to
permit the relay device to insert the Information option into all
relayed messages.
8. Security Considerations
Security issues with the Relay Agent Information option and its use Security issues with the Relay Agent Information option and its use
by servers in address assignment are discussed in [RFC3046] and by servers in address assignment are discussed in [RFC3046] and
[RFC4030]. Relay agents who send the Relay Agent Identifier [RFC4030]. Relay agents who send the Relay Agent Identifier
suboption SHOULD use the Relay Agent Authentication suboption suboption SHOULD use the Relay Agent Authentication suboption
[RFC4030] to provide integrity protection. [RFC4030] to provide integrity protection.
8. IANA Considerations 9. IANA Considerations
We request that IANA assign a new suboption code from the registry of We request that IANA assign a new suboption code from the registry of
DHCP Agent Sub-Option Codes maintained in DHCP Agent Sub-Option Codes maintained in
http://www.iana.org/assignments/bootp-dhcp-parameters. http://www.iana.org/assignments/bootp-dhcp-parameters.
Relay Agent Identifier Suboption [TBD] Relay Agent Identifier Suboption [TBD]
We request that IANA establish a new registry of DHCP Relay Agent We request that IANA establish a new registry of DHCP Relay Agent
Identifier Sub-Option Types, to be maintained in Identifier Sub-Option Types, to be maintained in
http://www.iana.org/assignments/bootp-dhcp-parameters. The http://www.iana.org/assignments/bootp-dhcp-parameters. The
Identifier Type is a single octet. The initial values assigned in Identifier Type is a single octet. The initial values assigned in
this document are: this document are:
RELAY_IDENTIFIER_NULL 0 RELAY_IDENTIFIER_NULL 0
RELAY_IDENTIFIER_DUID 1 RELAY_IDENTIFIER_DUID 1
RELAY_IDENTIFIER_ASCII 2 RELAY_IDENTIFIER_ASCII 2
Additional Identifier Type values will be allocated and assigned Additional Identifier Type values will be allocated and assigned
through IETF consensus, as defined in [RFC2434]. through IETF consensus, as defined in [RFC2434].
9. References 10. References
9.1. Normative References 10.1. Normative References
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", [RFC2131] Droms, R., "Dynamic Host Configuration Protocol",
RFC 2131, March 1997. RFC 2131, March 1997.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998. October 1998.
[RFC3046] Patrick, M., "DHCP Relay Agent Information Option", [RFC3046] Patrick, M., "DHCP Relay Agent Information Option",
RFC 3046, January 2001. RFC 3046, January 2001.
skipping to change at page 6, line 37 skipping to change at page 7, line 9
and M. Carney, "Dynamic Host Configuration Protocol for and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4030] Stapp, M. and T. Lemon, "The Authentication Suboption for [RFC4030] Stapp, M. and T. Lemon, "The Authentication Suboption for
the Dynamic Host Configuration Protocol (DHCP) Relay Agent the Dynamic Host Configuration Protocol (DHCP) Relay Agent
Option", RFC 4030, March 2005. Option", RFC 4030, March 2005.
9.2. Informative References 10.2. Informative References
[RFC4388] Woundy, R. and K. Kinnear, "Dynamic Host Configuration [RFC4388] Woundy, R. and K. Kinnear, "Dynamic Host Configuration
Protocol (DHCP) Leasequery", RFC 4388, February 2006. Protocol (DHCP) Leasequery", RFC 4388, February 2006.
[RFC5107] Johnson, R., Kumarasamy, J., Kinnear, K., and M. Stapp,
"DHCP Server Identifier Override Suboption", RFC 5107,
February 2008.
[draft-kinnear] [draft-kinnear]
Kinnear, K., Volz, B., Russell, N., and M. Stapp, "Bulk Kinnear, K., Volz, B., Russell, N., and M. Stapp, "Bulk
DHCPv4 Lease Query DHCPv4 Lease Query
(draft-kinnear-dhc-dhcpv4-bulk-leasequery-*)", July 2008. (draft-kinnear-dhc-dhcpv4-bulk-leasequery-*)", July 2008.
[draft-dtv] [draft-dtv]
Rao, D., Joshi, B., and P. Kurapati, "DHCPv4 bulk lease Rao, D., Joshi, B., and P. Kurapati, "DHCPv4 bulk lease
query (draft-dtv-dhc-dhcpv4-bulk-leasequery-*)", query (draft-dtv-dhc-dhcpv4-bulk-leasequery-*)",
July 2008. July 2008.
 End of changes. 8 change blocks. 
11 lines changed or deleted 33 lines changed or added

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