draft-ietf-dhc-relay-id-suboption-09.txt   draft-ietf-dhc-relay-id-suboption-10.txt 
DHC B. Joshi DHC B. Joshi
Internet-Draft R. Rao Internet-Draft D. Ramakrishna Rao
Intended status: Standards Track Infosys Ltd. Intended status: Standards Track Infosys Ltd.
Expires: December 22, 2011 M. Stapp Expires: July 13, 2012 M. Stapp
Cisco Systems, Inc. Cisco Systems, Inc.
June 20, 2011 January 10, 2012
The DHCPv4 Relay Agent Identifier Suboption The DHCPv4 Relay Agent Identifier Suboption
draft-ietf-dhc-relay-id-suboption-09.txt draft-ietf-dhc-relay-id-suboption-10.txt
Abstract Abstract
This draft defines a new Relay Agent Identifier suboption for the This draft 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 within the administrative domain. The value is relay agent device within the administrative domain. The value is
normally administratively-configured in the relay agent. The normally administratively-configured in the relay agent. The
suboption allows a DHCP relay agent to include the identifier in the suboption allows a DHCP relay agent to include the identifier in the
DHCP messages it sends. DHCP messages it sends.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on December 22, 2011. This Internet-Draft will expire on July 13, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 38 skipping to change at page 3, line 38
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]. Agent Information Option in [RFC3046].
3. Example Use-Cases 3. Example Use-Cases
3.1. Bulk Leasequery 3.1. 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 accommodate some additional Leasequery protocol [RFC4388] to accommodate some additional
situations. There is a recent draft situations. There is a recent draft
([I-D.ietf-dhc-dhcpv4-bulk-leasequery]) proposing a variety of ([I-D.ietf-dhc-dhcpv4-bulk-leasequery] proposing a variety of
enhancements to the existing Leasequery protocol. The draft enhancements to the existing Leasequery protocol. The draft
describes a use-case where a relay agent queries DHCP servers using describes a use-case where a relay agent queries DHCP servers using
the Relay Identifier to retrieve all the leases allocated through the the Relay Identifier to retrieve all the leases allocated through the
relay agent. relay agent.
3.2. Industrial Ethernet 3.2. Industrial Ethernet
DHCP typically identifies clients based on information in their DHCP DHCP typically identifies clients based on information in their DHCP
messages - such as the Client-Identifier option, or the value of the messages - such as the Client-Identifier option, or the value of the
chaddr field. In some networks, however, the location of a client - chaddr field. In some networks, however, the location of a client -
skipping to change at page 4, line 21 skipping to change at page 4, line 21
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.
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 | | |SUBOPT_RELAY_ID| length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
. . . .
. identifier (variable) . . identifier (variable) .
. . . .
+---------------------------------------------------------------+ +---------------------------------------------------------------+
Where: Where:
SUBOPT_RELAY_ID [TBA] SUBOPT_RELAY_ID [TBA]
length the number of octets in the suboption length the number of octets in the suboption
(excluding the suboption ID and length fields); (excluding the suboption ID and length fields);
the minimum length is one. the minimum length is one.
identifier the identifying data. identifier the identifying data.
5. Identifier Stability 5. Identifier Stability
If the relay identifier is to be meaningful it has to be stable. A If the relay identifier is to be meaningful it has to be stable. A
relay agent SHOULD use a single identifier value consistently. The relay agent SHOULD use a single identifier value consistently. The
identifier used by a relay device SHOULD be committed to stable identifier used by a relay device SHOULD be committed to stable
storage, unless the relay device can regenerate the value upon storage, unless the relay device can regenerate the value upon
reboot. reboot.
Administrators MUST make sure that the relay-id configured in a relay Administrators MUST make sure that the relay-id configured in a relay
skipping to change at page 6, line 37 skipping to change at page 6, line 39
9.2. Informative References 9.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.
[I-D.ietf-dhc-dhcpv4-bulk-leasequery] [I-D.ietf-dhc-dhcpv4-bulk-leasequery]
Kinnear, K., Volz, B., Russell, N., Stapp, M., Rao, D., Kinnear, K., Volz, B., Stapp, M., Joshi, B., Russell, N.,
Joshi, B., and P. Kurapati, "Bulk DHCPv4 Lease Query", and P. Kurapati, "Bulk DHCPv4 Lease Query",
draft-ietf-dhc-dhcpv4-bulk-leasequery-04 (work in draft-ietf-dhc-dhcpv4-bulk-leasequery-05 (work in
progress), May 2011. progress), November 2011.
Authors' Addresses Authors' Addresses
Bharat Joshi Bharat Joshi
Infosys Ltd. Infosys Ltd.
44 Electronics City, Hosur Road 44 Electronics City, Hosur Road
Bangalore 560 100 Bangalore 560 100
India India
Email: bharat_joshi@infosys.com Email: bharat_joshi@infosys.com
 End of changes. 13 change blocks. 
26 lines changed or deleted 26 lines changed or added

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