| 1 |
<pre>Internet Engineering Task Force (IETF) B. Joshi |
| 2 |
Request for Comments: 6925 R. Desetti |
| 3 |
Category: Standards Track Infosys Ltd. |
| 4 |
ISSN: 2070-1721 M. Stapp |
| 5 |
Cisco Systems, Inc. |
| 6 |
April 2013 |
| 7 |
|
| 8 |
|
| 9 |
<span class="h1">The DHCPv4 Relay Agent Identifier Sub-Option</span> |
| 10 |
|
| 11 |
Abstract |
| 12 |
|
| 13 |
This document defines a new Relay Agent Identifier sub-option for the |
| 14 |
Dynamic Host Configuration Protocol (DHCP) Relay Agent Information |
| 15 |
option. The sub-option carries a value that uniquely identifies the |
| 16 |
relay agent device within the administrative domain. The value is |
| 17 |
normally administratively configured in the relay agent. The sub- |
| 18 |
option allows a DHCP relay agent to include the identifier in the |
| 19 |
DHCP messages it sends. |
| 20 |
|
| 21 |
Status of This Memo |
| 22 |
|
| 23 |
This is an Internet Standards Track document. |
| 24 |
|
| 25 |
This document is a product of the Internet Engineering Task Force |
| 26 |
(IETF). It represents the consensus of the IETF community. It has |
| 27 |
received public review and has been approved for publication by the |
| 28 |
Internet Engineering Steering Group (IESG). Further information on |
| 29 |
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 30 |
|
| 31 |
Information about the current status of this document, any errata, |
| 32 |
and how to provide feedback on it may be obtained at |
| 33 |
<a href="http://www.rfc-editor.org/info/rfc6925">http://www.rfc-editor.org/info/rfc6925</a>. |
| 34 |
|
| 35 |
Copyright Notice |
| 36 |
|
| 37 |
Copyright (c) 2013 IETF Trust and the persons identified as the |
| 38 |
document authors. All rights reserved. |
| 39 |
|
| 40 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 41 |
Provisions Relating to IETF Documents |
| 42 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 43 |
publication of this document. Please review these documents |
| 44 |
carefully, as they describe your rights and restrictions with respect |
| 45 |
to this document. Code Components extracted from this document must |
| 46 |
include Simplified BSD License text as described in Section 4.e of |
| 47 |
the Trust Legal Provisions and are provided without warranty as |
| 48 |
described in the Simplified BSD License. |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Joshi, et al. Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc6925">RFC 6925</a> The Relay Agent ID Sub-Option April 2013</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a> |
| 60 |
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-2">2</a> |
| 61 |
<a href="#section-3">3</a>. Example Use Cases ...............................................<a href="#page-3">3</a> |
| 62 |
<a href="#section-3.1">3.1</a>. Bulk Leasequery ............................................<a href="#page-3">3</a> |
| 63 |
<a href="#section-3.2">3.2</a>. Industrial Ethernet ........................................<a href="#page-3">3</a> |
| 64 |
<a href="#section-4">4</a>. Sub-Option Format ...............................................<a href="#page-4">4</a> |
| 65 |
<a href="#section-5">5</a>. Identifier Stability ............................................<a href="#page-4">4</a> |
| 66 |
<a href="#section-5.1">5.1</a>. Identifier Uniqueness ......................................<a href="#page-5">5</a> |
| 67 |
<a href="#section-6">6</a>. Security Considerations .........................................<a href="#page-6">6</a> |
| 68 |
<a href="#section-6.1">6.1</a>. Forged Relay ID Attacks ....................................<a href="#page-6">6</a> |
| 69 |
<a href="#section-6.2">6.2</a>. Factory-Floor Scenario .....................................<a href="#page-6">6</a> |
| 70 |
<a href="#section-7">7</a>. IANA Considerations .............................................<a href="#page-7">7</a> |
| 71 |
<a href="#section-8">8</a>. Acknowledgments .................................................<a href="#page-7">7</a> |
| 72 |
<a href="#section-9">9</a>. References ......................................................<a href="#page-7">7</a> |
| 73 |
<a href="#section-9.1">9.1</a>. Normative References .......................................<a href="#page-7">7</a> |
| 74 |
<a href="#section-9.2">9.2</a>. Informative References .....................................<a href="#page-8">8</a> |
| 75 |
|
| 76 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 77 |
|
| 78 |
The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>] |
| 79 |
provides IP addresses and configuration information for IPv4 clients. |
| 80 |
It includes a relay agent capability, in which network elements |
| 81 |
receive broadcast messages from clients and forward them to DHCP |
| 82 |
servers as unicast messages. In many network environments, relay |
| 83 |
agents add information to the DHCP messages before forwarding them, |
| 84 |
using the Relay Agent Information option [<a href="./rfc3046" title=""DHCP Relay Agent Information Option"">RFC3046</a>]. Servers that |
| 85 |
recognize the Relay Agent Information option echo it back in their |
| 86 |
replies. |
| 87 |
|
| 88 |
This specification introduces a Relay Agent Identifier (Relay-ID) |
| 89 |
sub-option for the Relay Agent Information option. The Relay-ID sub- |
| 90 |
option carries a sequence of octets that is intended to uniquely |
| 91 |
identify the relay agent within the administrative domain. In this |
| 92 |
document, an administrative domain consists of all DHCP servers and |
| 93 |
relay agents that communicate with each other. |
| 94 |
|
| 95 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span> |
| 96 |
|
| 97 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 98 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 99 |
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 100 |
|
| 101 |
DHCPv4 terminology is defined in [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>], and the DHCPv4 Relay |
| 102 |
Agent Information option is defined in [<a href="./rfc3046" title=""DHCP Relay Agent Information Option"">RFC3046</a>]. |
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Joshi, et al. Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc6925">RFC 6925</a> The Relay Agent ID Sub-Option April 2013</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Example Use Cases</span> |
| 114 |
|
| 115 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Bulk Leasequery</span> |
| 116 |
|
| 117 |
There has been quite a bit of recent interest in extending the DHCP |
| 118 |
Leasequery protocol [<a href="./rfc4388" title=""Dynamic Host Configuration Protocol (DHCP) Leasequery"">RFC4388</a>] to accommodate some additional |
| 119 |
situations. [<a href="./rfc6926" title=""DHCPv4 Bulk Leasequery"">RFC6926</a>] proposes a variety of enhancements to the |
| 120 |
existing Leasequery protocol. The document describes a use case |
| 121 |
where a relay agent queries DHCP servers using the relay identifier |
| 122 |
to retrieve all the leases allocated through the relay agent. |
| 123 |
|
| 124 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Industrial Ethernet</span> |
| 125 |
|
| 126 |
DHCP typically identifies clients based on information in their DHCP |
| 127 |
messages, such as the Client-Identifier option or the value of the |
| 128 |
chaddr field. In some networks, however, the location of a client -- |
| 129 |
its point of attachment to the network -- is a more useful |
| 130 |
identifier. In factory-floor networks (commonly called 'industrial' |
| 131 |
networks), for example, the role a device plays is often fixed and |
| 132 |
based on its location. Using manual address configuration is |
| 133 |
possible (and is common), but it would be beneficial if DHCP |
| 134 |
configuration could be applied to these networks. |
| 135 |
|
| 136 |
One way to provide connection-based identifiers for industrial |
| 137 |
networks is to have the network elements acting as DHCP relay agents |
| 138 |
supply information that a DHCP server could use as a client |
| 139 |
identifier. A straightforward way to form identifier information is |
| 140 |
to combine something that is unique within the scope of the network |
| 141 |
element, such as a port/slot value, with something that uniquely |
| 142 |
identifies that network element, such as a Relay Agent Identifier. |
| 143 |
|
| 144 |
|
| 145 |
|
| 146 |
|
| 147 |
|
| 148 |
|
| 149 |
|
| 150 |
|
| 151 |
|
| 152 |
|
| 153 |
|
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Joshi, et al. Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc6925">RFC 6925</a> The Relay Agent ID Sub-Option April 2013</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Sub-Option Format</span> |
| 170 |
|
| 171 |
Format of the Relay Agent Identifier sub-option: |
| 172 |
|
| 173 |
0 1 2 3 |
| 174 |
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 |
| 175 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 176 |
|SUBOPT_RELAY_ID| length | | |
| 177 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |
| 178 |
. . |
| 179 |
. identifier (variable) . |
| 180 |
. . |
| 181 |
+---------------------------------------------------------------+ |
| 182 |
|
| 183 |
Where: |
| 184 |
|
| 185 |
SUBOPT_RELAY_ID 12 |
| 186 |
|
| 187 |
length the number of octets in the sub-option |
| 188 |
(excluding the sub-option ID and length fields); |
| 189 |
the minimum length is one. |
| 190 |
|
| 191 |
identifier the identifying data |
| 192 |
|
| 193 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Identifier Stability</span> |
| 194 |
|
| 195 |
If the relay identifier is to be meaningful, it has to be stable. A |
| 196 |
relay agent SHOULD use a single identifier value consistently. The |
| 197 |
identifier used by a relay device SHOULD be committed to stable |
| 198 |
storage, unless the relay device can regenerate the value upon |
| 199 |
reboot. |
| 200 |
|
| 201 |
If the Relay-ID configured in a relay agent is not unique within its |
| 202 |
administrative domain, resource allocation problems may occur as the |
| 203 |
DHCP server attempts to allocate the same resource to devices behind |
| 204 |
two different relay agents. Therefore, a Relay-ID configured in a |
| 205 |
relay agent MUST be unique within its administrative domain. To aid |
| 206 |
in ensuring uniqueness of Relay-IDs, relay agents SHOULD make their |
| 207 |
relay identifiers visible to their administrators via their user |
| 208 |
interface, through a log entry, through a MIB field, or through some |
| 209 |
other mechanism. |
| 210 |
|
| 211 |
Implementors of relay agents should note that the identifier needs to |
| 212 |
be present in all DHCP message types where its value is being used by |
| 213 |
the DHCP server. The relay agent may not be able to add the Relay |
| 214 |
Agent Information option to all messages, such as RENEW messages sent |
| 215 |
as IP unicasts. In some deployments, that might mean that the server |
| 216 |
has to be willing to continue to associate the relay identifier it |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Joshi, et al. Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc6925">RFC 6925</a> The Relay Agent ID Sub-Option April 2013</span> |
| 223 |
|
| 224 |
|
| 225 |
has last seen with a lease that is being RENEWed. Other deployments |
| 226 |
may prefer to use the Server Identifier Override sub-option [<a href="./rfc5107" title=""DHCP Server Identifier Override Suboption"">RFC5107</a>] |
| 227 |
to permit the relay device to insert the Relay Agent Information |
| 228 |
option into all relayed messages. |
| 229 |
|
| 230 |
Handling situations where a relay agent device is replaced is another |
| 231 |
aspect of stability. One of the use cases for the relay identifier |
| 232 |
is to permit a server to associate clients' lease bindings with the |
| 233 |
relay device connected to the clients. If the relay device is |
| 234 |
replaced because it has failed or been upgraded, it may be desirable |
| 235 |
for the new device to continue to provide the same relay identifier |
| 236 |
as the old device. Therefore, if a relay agent supports Relay-ID, |
| 237 |
the Relay-ID should be administratively configurable. |
| 238 |
|
| 239 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Identifier Uniqueness</span> |
| 240 |
|
| 241 |
It is strongly recommended that administrators take special care to |
| 242 |
ensure that Relay-IDs configured in their relay agents are not |
| 243 |
duplicated. There are a number of strategies that may be used to |
| 244 |
achieve this. |
| 245 |
|
| 246 |
Administrators may use a strategy to configure unique Relay-IDs. One |
| 247 |
such strategy is that a Relay-ID on a relay agent may reuse an |
| 248 |
existing identifier or set of identifiers that are already guaranteed |
| 249 |
to be unique (e.g., Universally Unique Identifier (UUID) [<a href="./rfc4122" title=""A Universally Unique IDentifier (UUID) URN Namespace"">RFC4122</a>]). |
| 250 |
|
| 251 |
For administrators who are already using a provisioning system to |
| 252 |
manage their networking infrastructure, it may work to enumerate |
| 253 |
relay agents on the basis of roles and then, as a second step, assign |
| 254 |
those roles to specific relay agents or groups of relay agents. In |
| 255 |
such a scenario, when a replacement relay agent is first seen by the |
| 256 |
DHCP server, it could trigger a configuration event on the |
| 257 |
provisioning system, and the new relay agent could be assigned to the |
| 258 |
role of the relay agent it is replacing. |
| 259 |
|
| 260 |
It may be that the DHCP server has configurable event notification |
| 261 |
and that a duplicate Relay-ID would trigger this notification. |
| 262 |
Administrators can take advantage of this feature to work out whether |
| 263 |
the duplication is real and unintended or whether the original relay |
| 264 |
agent is being replaced. |
| 265 |
|
| 266 |
A network management/provisioning system may also be able to collect |
| 267 |
a full list of all relay agents on the network. It may then notice |
| 268 |
that more than one device reports the same Relay-ID. In such a case, |
| 269 |
the provisioning system could notify the administrator of the fault, |
| 270 |
which could then be corrected. |
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Joshi, et al. Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc6925">RFC 6925</a> The Relay Agent ID Sub-Option April 2013</span> |
| 279 |
|
| 280 |
|
| 281 |
This is not an exhaustive list of strategies. We suggest an |
| 282 |
additional strategy in the Security Considerations section. If none |
| 283 |
of these strategies will work, administrators are also encouraged to |
| 284 |
consider the specifics of their own network configuration to see if |
| 285 |
there is some way to detect duplicate Relay-IDs other than the ones |
| 286 |
listed here. |
| 287 |
|
| 288 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span> |
| 289 |
|
| 290 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Forged Relay ID Attacks</span> |
| 291 |
|
| 292 |
Security issues with the Relay Agent Information option and its use |
| 293 |
by servers in address assignment are discussed in [<a href="./rfc3046" title=""DHCP Relay Agent Information Option"">RFC3046</a>] and |
| 294 |
[<a href="./rfc4030" title=""The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option"">RFC4030</a>]. The DHCP Relay Agent Information option depends on a |
| 295 |
trusted relationship between the DHCP relay agent and the DHCP |
| 296 |
server, as described in <a href="./rfc3046#section-5">Section 5 of [RFC3046]</a>. While the |
| 297 |
introduction of fraudulent DHCP Relay Agent Information options can |
| 298 |
be prevented by a perimeter defense that blocks these options unless |
| 299 |
the DHCP relay agent is trusted, a deeper defense using the |
| 300 |
authentication sub-option for the DHCP Relay Agent Information option |
| 301 |
[<a href="./rfc4030" title=""The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option"">RFC4030</a>] SHOULD be deployed as well. It also helps in avoiding |
| 302 |
duplication of relay identifiers by malicious entities. However, |
| 303 |
implementation of the authentication sub-option for the DHCP Relay |
| 304 |
Agent Information option [<a href="./rfc4030" title=""The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option"">RFC4030</a>] is not a must to support the |
| 305 |
Relay-ID sub-option. |
| 306 |
|
| 307 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Factory-Floor Scenario</span> |
| 308 |
|
| 309 |
One possible use case for the Relay-ID sub-option is the automated |
| 310 |
configuration of machines on a factory floor. In this situation, |
| 311 |
various sections of the factory floor might be on their own network |
| 312 |
links with a relay agent interposed between those links and the DHCP |
| 313 |
server. The Relay-ID of each relay agent might cause special |
| 314 |
configurations to be downloaded to those devices to control their |
| 315 |
behavior. |
| 316 |
|
| 317 |
If a relay agent was deployed on the factory floor in such a |
| 318 |
situation, with an incorrect Relay-ID, there is the potential that |
| 319 |
devices could be misconfigured in a way that could produce incorrect |
| 320 |
results, cause physical damage, or even create hazardous conditions |
| 321 |
for workers. |
| 322 |
|
| 323 |
In deployment scenarios like this one, administrators must use some |
| 324 |
dependable technique to ensure that such misconfigurations do not |
| 325 |
occur. It is beyond the scope of this document to provide a complete |
| 326 |
list of such techniques. |
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Joshi, et al. Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc6925">RFC 6925</a> The Relay Agent ID Sub-Option April 2013</span> |
| 335 |
|
| 336 |
|
| 337 |
However, as an example, a relay agent device intended for use in such |
| 338 |
a scenario could require the use of a hardware token that contains a |
| 339 |
Relay-ID that is physically attached to the installation location of |
| 340 |
the relay agent device and can be connected to and disconnected from |
| 341 |
the relay agent device without the use of special tools. Such a |
| 342 |
relay agent device should not be operable when this hardware token is |
| 343 |
not connected to it: either it should fail because it presents an |
| 344 |
unknown identifier to the DHCP server, or it should simply refuse to |
| 345 |
relay DHCP packets until the token is connected to it. |
| 346 |
|
| 347 |
A relay agent device that does not provide a clear mitigation |
| 348 |
strategy for a scenario where misconfiguration could have damaging or |
| 349 |
hazardous consequences should not be deployed in such a scenario. |
| 350 |
|
| 351 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span> |
| 352 |
|
| 353 |
IANA has assigned a new sub-option code from the "DHCP Relay Agent |
| 354 |
Sub-Option Codes" registry maintained at |
| 355 |
<a href="http://www.iana.org/assignments/bootp-dhcp-parameters">http://www.iana.org/assignments/bootp-dhcp-parameters</a>. |
| 356 |
|
| 357 |
Relay Agent Identifier Sub-Option 12 |
| 358 |
|
| 359 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgments</span> |
| 360 |
|
| 361 |
Thanks to Bernie Volz, David W. Hankins, Pavan Kurapati, and Ted |
| 362 |
Lemon for providing valuable suggestions. |
| 363 |
|
| 364 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span> |
| 365 |
|
| 366 |
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span> |
| 367 |
|
| 368 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 369 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 370 |
|
| 371 |
[<a id="ref-RFC2131">RFC2131</a>] Droms, R., "Dynamic Host Configuration Protocol", <a href="./rfc2131">RFC</a> |
| 372 |
<a href="./rfc2131">2131</a>, March 1997. |
| 373 |
|
| 374 |
[<a id="ref-RFC3046">RFC3046</a>] Patrick, M., "DHCP Relay Agent Information Option", <a href="./rfc3046">RFC</a> |
| 375 |
<a href="./rfc3046">3046</a>, January 2001. |
| 376 |
|
| 377 |
[<a id="ref-RFC4030">RFC4030</a>] Stapp, M. and T. Lemon, "The Authentication Suboption for |
| 378 |
the Dynamic Host Configuration Protocol (DHCP) Relay Agent |
| 379 |
Option", <a href="./rfc4030">RFC 4030</a>, March 2005. |
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Joshi, et al. Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc6925">RFC 6925</a> The Relay Agent ID Sub-Option April 2013</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span> |
| 394 |
|
| 395 |
[<a id="ref-RFC4122">RFC4122</a>] Leach, P., Mealling, M., and R. Salz, "A Universally |
| 396 |
Unique IDentifier (UUID) URN Namespace", <a href="./rfc4122">RFC 4122</a>, July |
| 397 |
2005. |
| 398 |
|
| 399 |
[<a id="ref-RFC4388">RFC4388</a>] Woundy, R. and K. Kinnear, "Dynamic Host Configuration |
| 400 |
Protocol (DHCP) Leasequery", <a href="./rfc4388">RFC 4388</a>, February 2006. |
| 401 |
|
| 402 |
[<a id="ref-RFC5107">RFC5107</a>] Johnson, R., Kumarasamy, J., Kinnear, K., and M. Stapp, |
| 403 |
"DHCP Server Identifier Override Suboption", <a href="./rfc5107">RFC 5107</a>, |
| 404 |
February 2008. |
| 405 |
|
| 406 |
[<a id="ref-RFC6926">RFC6926</a>] Kinnear, K., Stapp, M., Desetti, R., Joshi, B., Russell, |
| 407 |
N., Kurapati, P., and B. Volz, "DHCPv4 Bulk Leasequery", |
| 408 |
<a href="./rfc6926">RFC 6926</a>, April 2013. |
| 409 |
|
| 410 |
Authors' Addresses |
| 411 |
|
| 412 |
Bharat Joshi |
| 413 |
Infosys Ltd. |
| 414 |
44 Electronics City, Hosur Road |
| 415 |
Bangalore 560 100 |
| 416 |
India |
| 417 |
|
| 418 |
EMail: [email protected] |
| 419 |
URI: <a href="http://www.infosys.com/">http://www.infosys.com/</a> |
| 420 |
|
| 421 |
|
| 422 |
D.T.V Ramakrishna Rao |
| 423 |
Infosys Ltd. |
| 424 |
44 Electronics City, Hosur Road |
| 425 |
Bangalore 560 100 |
| 426 |
India |
| 427 |
|
| 428 |
EMail: [email protected] |
| 429 |
URI: <a href="http://www.infosys.com/">http://www.infosys.com/</a> |
| 430 |
|
| 431 |
|
| 432 |
Mark Stapp |
| 433 |
Cisco Systems, Inc. |
| 434 |
1414 Massachusetts Ave. |
| 435 |
Boxborough, MA 01719 |
| 436 |
USA |
| 437 |
|
| 438 |
Phone: +1 978 936 0000 |
| 439 |
EMail: [email protected] |
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
Joshi, et al. Standards Track [Page 8] |
| 445 |
</pre> |