draft-ietf-dhc-relay-id-suboption-03.txt   draft-ietf-dhc-relay-id-suboption-04.txt 
DHC M. Stapp DHC M. Stapp
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: April 2, 2009 September 29, 2008 Expires: April 3, 2009 September 30, 2008
The DHCPv4 Relay Agent Identifier Suboption The DHCPv4 Relay Agent Identifier Suboption
draft-ietf-dhc-relay-id-suboption-03.txt draft-ietf-dhc-relay-id-suboption-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 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 April 2, 2009. This Internet-Draft will expire on April 3, 2009.
Abstract Abstract
This memo defines a new Relay Agent Identifier suboption for the This memo defines a new Relay Agent Identifier suboption for the
Dynamic Host Configuration Protocol's (DHCP) Relay Agent Information Dynamic Host Configuration Protocol's (DHCP) Relay Agent Information
option. The suboption carries a value that uniquely identifies the option. The suboption carries a value that uniquely identifies the
relay agent device. The value may be administratively-configured or relay agent device. The value may be administratively-configured or
may be generated by the relay agent. The suboption allows a DHCP may be generated by the relay agent. The suboption allows a DHCP
relay agent to include the identifier in the DHCP messages it sends. relay agent to include the identifier in the DHCP messages it sends.
skipping to change at page 3, line 23 skipping to change at page 3, line 23
using the Relay Agent Information option [RFC3046]. Servers that using the Relay Agent Information option [RFC3046]. Servers that
recognize the relay information option echo it back in their replies. recognize the relay information option echo it back in their replies.
This specification introduces a Relay Agent Identifier suboption for This specification introduces a Relay Agent Identifier suboption for
the Relay Information option. The Relay-Id suboption carries a the Relay Information option. The Relay-Id suboption carries a
sequence of octets that is intended to identify the relay agent sequence of octets that is intended to identify the relay agent
uniquely within the administrative domain. The identifier may be uniquely within the administrative domain. The identifier may be
administratively configured: in some networks it may be adequate to administratively configured: in some networks it may be adequate to
assign ASCII strings such as "switch1" and "switch2". Alternatively, assign ASCII strings such as "switch1" and "switch2". Alternatively,
the identifier may be generated by the relay agent itself, and we the identifier may be generated by the relay agent itself, and we
specify use of [RFC3315] DUIDs for this purpose. specify use of DUIDs [RFC3315] for this purpose.
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 [RFC2119]. document are to be interpreted as described in [RFC2119].
DHCPv4 terminology is defined in [RFC2131], and the DHCPv4 Relay DHCPv4 terminology is defined in [RFC2131], and the DHCPv4 Relay
Agent Information Option in [RFC3046]. DUID terminology is in Agent Information Option in [RFC3046]. DUID terminology is in
[RFC3315]. [RFC3315].
skipping to change at page 4, line 13 skipping to change at page 4, line 13
networks is to have the network elements acting as DHCP relay agents networks is to have the network elements acting as DHCP relay agents
supply information that a DHCP server could use as a client supply information that a DHCP server could use as a client
identifier. A straightforward way to form identifier information is identifier. A straightforward way to form identifier information is
to combine something that is unique within the scope of the network to combine something that is unique within the scope of the network
element, such as a port/slot value, with something that uniquely element, such as a port/slot value, with something that uniquely
identifies that network element, such as a Relay Agent Identifier. identifies that network element, such as a Relay Agent Identifier.
3.2. Bulk Leasequery 3.2. Bulk Leasequery
There has been quite a bit of recent interest in extending the DHCP There has been quite a bit of recent interest in extending the DHCP
Leasequery protocol [RFC4388] to accomodate some additional Leasequery protocol [RFC4388] to accommodate some additional
situations. There are two recent drafts ([draft-kinnear] and situations. There are two recent drafts ([draft-kinnear] and
[draft-dtv]) proposing a variety of enhancements to the existing [draft-dtv]) proposing a variety of enhancements to the existing
Leasequery protocol. draft-dtv describes a use-case where a relay Leasequery protocol. [draft-dtv] describes a use-case where a relay
agent queries DHCP servers using the Relay Identifier to retrieve all agent queries DHCP servers using the Relay Identifier to retrieve all
the leases allocated through the relay device. the leases allocated through the relay device.
4. Suboption Format 4. Suboption Format
Format of the Relay Agent Identifier suboption: Format of the Relay Agent Identifier suboption:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|SUBOPT_RELAY_ID| length | type | | |SUBOPT_RELAY_ID| length | type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
. . . .
. identifier (variable) . . identifier (variable) .
. . . .
+---------------------------------------------------------------+ +---------------------------------------------------------------+
Where: Where:
SUBOPT_RELAY_ID [TBD] SUBOPT_RELAY_ID [TBA]
length the number of octets in the suboption; the length the number of octets in the suboption
minimum length is two. (excluding the suboption ID and length fields);
the minimum length is two.
type a single octet describing the type of type a single octet describing the type of
identifier that is present. identifier that is present.
identifier the identifying data. identifier the identifying data.
5. Relay Identifier Types 5. Relay Identifier Types
For clarity, the suboption specified here includes a type octet that For clarity, the suboption specified here includes a type octet that
describes the data used in the identifier field. The type value zero describes the data used in the identifier field. The type value zero
skipping to change at page 6, line 14 skipping to change at page 6, line 14
[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.
9. 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 [TBA]
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 Review, as defined in [RFC5226].
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[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
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
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.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
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
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.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
10.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, [RFC5107] Johnson, R., Kumarasamy, J., Kinnear, K., and M. Stapp,
"DHCP Server Identifier Override Suboption", RFC 5107, "DHCP Server Identifier Override Suboption", RFC 5107,
February 2008. February 2008.
[draft-kinnear] [draft-kinnear]
 End of changes. 14 change blocks. 
18 lines changed or deleted 19 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/