| 1 |
<pre>Internet Engineering Task Force (IETF) K. Kinnear |
| 2 |
Request for Comments: 6926 M. Stapp |
| 3 |
Category: Standards Track Cisco Systems, Inc. |
| 4 |
ISSN: 2070-1721 R. Desetti |
| 5 |
B. Joshi |
| 6 |
Infosys Ltd. |
| 7 |
N. Russell |
| 8 |
Sea Street Technologies Inc. |
| 9 |
P. Kurapati |
| 10 |
Juniper Networks |
| 11 |
B. Volz |
| 12 |
Cisco Systems, Inc. |
| 13 |
April 2013 |
| 14 |
|
| 15 |
|
| 16 |
<span class="h1">DHCPv4 Bulk Leasequery</span> |
| 17 |
|
| 18 |
Abstract |
| 19 |
|
| 20 |
The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) Leasequery |
| 21 |
protocol allows a requestor to request information about DHCPv4 |
| 22 |
bindings. This protocol is limited to queries for individual |
| 23 |
bindings. In some situations, individual binding queries may not be |
| 24 |
efficient or even possible. This document extends the DHCPv4 |
| 25 |
Leasequery protocol to allow for bulk transfer of DHCPv4 address |
| 26 |
binding data via TCP. |
| 27 |
|
| 28 |
Status of This Memo |
| 29 |
|
| 30 |
This is an Internet Standards Track document. |
| 31 |
|
| 32 |
This document is a product of the Internet Engineering Task Force |
| 33 |
(IETF). It represents the consensus of the IETF community. It has |
| 34 |
received public review and has been approved for publication by the |
| 35 |
Internet Engineering Steering Group (IESG). Further information on |
| 36 |
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 37 |
|
| 38 |
Information about the current status of this document, any errata, |
| 39 |
and how to provide feedback on it may be obtained at |
| 40 |
<a href="http://www.rfc-editor.org/info/rfc6926">http://www.rfc-editor.org/info/rfc6926</a>. |
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Kinnear, 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="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 55 |
|
| 56 |
|
| 57 |
Copyright Notice |
| 58 |
|
| 59 |
Copyright (c) 2013 IETF Trust and the persons identified as the |
| 60 |
document authors. All rights reserved. |
| 61 |
|
| 62 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 63 |
Provisions Relating to IETF Documents |
| 64 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 65 |
publication of this document. Please review these documents |
| 66 |
carefully, as they describe your rights and restrictions with respect |
| 67 |
to this document. Code Components extracted from this document must |
| 68 |
include Simplified BSD License text as described in Section 4.e of |
| 69 |
the Trust Legal Provisions and are provided without warranty as |
| 70 |
described in the Simplified BSD License. |
| 71 |
|
| 72 |
|
| 73 |
|
| 74 |
|
| 75 |
|
| 76 |
|
| 77 |
|
| 78 |
|
| 79 |
|
| 80 |
|
| 81 |
|
| 82 |
|
| 83 |
|
| 84 |
|
| 85 |
|
| 86 |
|
| 87 |
|
| 88 |
|
| 89 |
|
| 90 |
|
| 91 |
|
| 92 |
|
| 93 |
|
| 94 |
|
| 95 |
|
| 96 |
|
| 97 |
|
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Kinnear, 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="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 111 |
|
| 112 |
|
| 113 |
Table of Contents |
| 114 |
|
| 115 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-4">4</a> |
| 116 |
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-5">5</a> |
| 117 |
<a href="#section-3">3</a>. Design Goals ....................................................<a href="#page-8">8</a> |
| 118 |
<a href="#section-3.1">3.1</a>. Information Acquisition before Data Starts .................<a href="#page-8">8</a> |
| 119 |
<a href="#section-3.2">3.2</a>. Lessen Need for Caching and Negative Caching ...............<a href="#page-8">8</a> |
| 120 |
<a href="#section-3.3">3.3</a>. Antispoofing in 'Fast Path' ................................<a href="#page-8">8</a> |
| 121 |
<a href="#section-3.4">3.4</a>. Minimize Data Transmission .................................<a href="#page-9">9</a> |
| 122 |
<a href="#section-4">4</a>. Protocol Overview ...............................................<a href="#page-9">9</a> |
| 123 |
<a href="#section-5">5</a>. Interaction between UDP Leasequery and Bulk Leasequery .........<a href="#page-11">11</a> |
| 124 |
<a href="#section-6">6</a>. Message and Option Definitions .................................<a href="#page-12">12</a> |
| 125 |
<a href="#section-6.1">6.1</a>. Message Framing for TCP ...................................<a href="#page-12">12</a> |
| 126 |
<a href="#section-6.2">6.2</a>. New or Changed Options ....................................<a href="#page-13">13</a> |
| 127 |
<a href="#section-6.3">6.3</a>. Connection and Transmission Parameters ....................<a href="#page-20">20</a> |
| 128 |
<a href="#section-7">7</a>. Requestor Behavior .............................................<a href="#page-21">21</a> |
| 129 |
<a href="#section-7.1">7.1</a>. Connecting and General Processing .........................<a href="#page-21">21</a> |
| 130 |
<a href="#section-7.2">7.2</a>. Forming a Bulk Leasequery .................................<a href="#page-21">21</a> |
| 131 |
<a href="#section-7.3">7.3</a>. Processing Bulk Replies ...................................<a href="#page-23">23</a> |
| 132 |
<a href="#section-7.4">7.4</a>. Processing Time Values in Leasequery Messages .............<a href="#page-25">25</a> |
| 133 |
<a href="#section-7.5">7.5</a>. Querying Multiple Servers .................................<a href="#page-26">26</a> |
| 134 |
7.6. Making Sense out of Multiple Responses concerning |
| 135 |
a Single IPv4 Address .....................................<a href="#page-26">26</a> |
| 136 |
<a href="#section-7.7">7.7</a>. Multiple Queries to a Single Server over One Connection ...<a href="#page-27">27</a> |
| 137 |
<a href="#section-7.8">7.8</a>. Closing Connections .......................................<a href="#page-28">28</a> |
| 138 |
<a href="#section-8">8</a>. Server Behavior ................................................<a href="#page-29">29</a> |
| 139 |
<a href="#section-8.1">8.1</a>. Accepting Connections .....................................<a href="#page-29">29</a> |
| 140 |
<a href="#section-8.2">8.2</a>. Replying to a Bulk Leasequery .............................<a href="#page-29">29</a> |
| 141 |
<a href="#section-8.3">8.3</a>. Building a Single Reply for Bulk Leasequery ...............<a href="#page-33">33</a> |
| 142 |
<a href="#section-8.4">8.4</a>. Multiple or Parallel Queries ..............................<a href="#page-34">34</a> |
| 143 |
<a href="#section-8.5">8.5</a>. Closing Connections .......................................<a href="#page-35">35</a> |
| 144 |
<a href="#section-9">9</a>. Security Considerations ........................................<a href="#page-35">35</a> |
| 145 |
<a href="#section-10">10</a>. IANA Considerations ...........................................<a href="#page-37">37</a> |
| 146 |
<a href="#section-11">11</a>. Acknowledgements ..............................................<a href="#page-38">38</a> |
| 147 |
<a href="#section-12">12</a>. References ....................................................<a href="#page-38">38</a> |
| 148 |
<a href="#section-12.1">12.1</a>. Normative References .....................................<a href="#page-38">38</a> |
| 149 |
<a href="#section-12.2">12.2</a>. Informative References ...................................<a href="#page-39">39</a> |
| 150 |
|
| 151 |
|
| 152 |
|
| 153 |
|
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Kinnear, 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="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 170 |
|
| 171 |
DHCPv4 [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>] [<a href="./rfc2132" title=""DHCP Options and BOOTP Vendor Extensions"">RFC2132</a>] specifies a protocol for the assignment of |
| 172 |
IPv4 address and configuration information to IPv4 nodes. DHCPv4 |
| 173 |
servers maintain authoritative binding information. |
| 174 |
|
| 175 |
+--------+ |
| 176 |
| DHCPv4 | +--------------+ |
| 177 |
| Server |-...-| DHCP | |
| 178 |
| | | Relay Agent | |
| 179 |
+--------+ +--------------+ |
| 180 |
| | |
| 181 |
+------+ +------+ |
| 182 |
|Modem1| |Modem2| |
| 183 |
+------+ +------+ |
| 184 |
| | | |
| 185 |
+-----+ +-----+ +-----+ |
| 186 |
|Node1| |Node2| |Node3| |
| 187 |
+-----+ +-----+ +-----+ |
| 188 |
|
| 189 |
Figure 1: Example DHCPv4 Configuration |
| 190 |
|
| 191 |
DHCPv4 relay agents receive DHCPv4 messages and frequently append a |
| 192 |
Relay Agent Information option [<a href="./rfc3046" title=""DHCP Relay Agent Information Option"">RFC3046</a>] before relaying them to the |
| 193 |
configured DHCPv4 servers (see Figure 1). In this process, some |
| 194 |
relay agents also glean lease information sent by the server and |
| 195 |
cache it locally. This information is used for a variety of |
| 196 |
purposes. Two examples are prevention of spoofing attempts from the |
| 197 |
DHCPv4 clients and installation of routes. When a relay agent |
| 198 |
reboots, this information is frequently lost. |
| 199 |
|
| 200 |
The DHCPv4 Leasequery capability [<a href="./rfc4388" title=""Dynamic Host Configuration Protocol (DHCP) Leasequery"">RFC4388</a>] extends the basic DHCPv4 |
| 201 |
capability to allow an external entity, such as a relay agent, to |
| 202 |
query a DHCPv4 server to rapidly recover lease state information |
| 203 |
about a particular IP address or client. |
| 204 |
|
| 205 |
The existing query types in Leasequery are typically data driven; the |
| 206 |
relay agent initiates the Leasequery when it receives data traffic |
| 207 |
from or to the client. This approach may not scale well when there |
| 208 |
are thousands of clients connected to the relay agent or when the |
| 209 |
relay agent has a need to rebuild its internal data store prior to |
| 210 |
processing traffic in one direction or another. |
| 211 |
|
| 212 |
Some applications require the ability to query the server without |
| 213 |
waiting for traffic from or to clients. This query capability, in |
| 214 |
turn, requires an underlying transport more suitable to the bulk |
| 215 |
transmission of data. |
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Kinnear, 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="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 223 |
|
| 224 |
|
| 225 |
This document extends the DHCPv4 Leasequery protocol [<a href="./rfc4388" title=""Dynamic Host Configuration Protocol (DHCP) Leasequery"">RFC4388</a>] to add |
| 226 |
support for queries that address these additional requirements. |
| 227 |
There may be many thousands of DHCPv4 bindings returned as the result |
| 228 |
of a single request, so TCP [<a href="./rfc4614" title=""A Roadmap for Transmission Control Protocol (TCP) Specification Documents"">RFC4614</a>] is specified for efficiency of |
| 229 |
data transfer. We define several additional query types, each of |
| 230 |
which can return multiple responses, in order to meet a variety of |
| 231 |
requirements. |
| 232 |
|
| 233 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span> |
| 234 |
|
| 235 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 236 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and |
| 237 |
"OPTIONAL" in this document are to be interpreted as described in <a href="./rfc2119">RFC</a> |
| 238 |
<a href="./rfc2119">2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 239 |
|
| 240 |
This document uses the following terms: |
| 241 |
|
| 242 |
o "absolute time" |
| 243 |
|
| 244 |
Absolute time is a 32-bit quantity containing the number of |
| 245 |
seconds since January 1, 1970. |
| 246 |
|
| 247 |
o "access concentrator" |
| 248 |
|
| 249 |
An access concentrator is a router or switch at the broadband |
| 250 |
access provider's edge of a public broadband access network. This |
| 251 |
document assumes that the access concentrator includes the DHCPv4 |
| 252 |
relay agent functionality, for example, a CMTS (Cable Modem |
| 253 |
Termination System) in a cable environment or a DSLAM (Digital |
| 254 |
Subscriber Line Access Multiplexer) in a DSL environment. |
| 255 |
|
| 256 |
o "active binding" |
| 257 |
|
| 258 |
An IP address with an active binding refers to an IP address that |
| 259 |
is currently associated with a DHCPv4 client where that DHCPv4 |
| 260 |
client has the right to use the IP address. |
| 261 |
|
| 262 |
o "Bulk Leasequery" |
| 263 |
|
| 264 |
Bulk Leasequery involves requesting and receiving the existing |
| 265 |
DHCPv4 address binding information in an efficient manner. |
| 266 |
|
| 267 |
o "clock skew" |
| 268 |
|
| 269 |
The clock skew for a Bulk Leasequery connection is the difference |
| 270 |
between the absolute time on a DHCPv4 server and the absolute time |
| 271 |
on the system where a requestor of a Bulk Leasequery is executing. |
| 272 |
It is not absolutely constant but is likely to vary only slowly. |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Kinnear, 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="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 279 |
|
| 280 |
|
| 281 |
It is possible that, when both systems run NTP, the clock skew is |
| 282 |
negligible; this is not only acceptable but desired. |
| 283 |
|
| 284 |
While it is easy to think that this can be calculated precisely |
| 285 |
after one message is received by a requestor from a DHCPv4 server, |
| 286 |
a more accurate value is derived from continuously examining the |
| 287 |
instantaneous value developed from each message received from a |
| 288 |
DHCPv4 server and using it to make small adjustments to the |
| 289 |
existing value held in the requestor. |
| 290 |
|
| 291 |
o "Default VPN" |
| 292 |
|
| 293 |
A default VPN indicates that the address being described belongs |
| 294 |
to the set of addresses not part of any VPN (in other words, the |
| 295 |
normal address space operated on by DHCP). This includes Special |
| 296 |
Use IPv4 Addresses as defined in [<a href="./rfc5735" title=""Special Use IPv4 Addresses"">RFC5735</a>]. |
| 297 |
|
| 298 |
o "DHCPv4 client" |
| 299 |
|
| 300 |
A DHCPv4 client is an Internet node using DHCPv4 to obtain |
| 301 |
configuration parameters such as a network address. |
| 302 |
|
| 303 |
o "DHCPv4 relay agent" |
| 304 |
|
| 305 |
A DHCPv4 relay agent is an agent that is neither a DHCPv4 client |
| 306 |
nor a DHCP server that transfers BOOTP and DHCPv4 messages between |
| 307 |
clients and servers residing on different subnets, per [<a href="./rfc951" title=""Bootstrap Protocol"">RFC951</a>] |
| 308 |
and [<a href="./rfc1542" title=""Clarifications and Extensions for the Bootstrap Protocol"">RFC1542</a>]. |
| 309 |
|
| 310 |
o "DHCPv4 server" |
| 311 |
|
| 312 |
A DHCPv4 server is an Internet node that returns configuration |
| 313 |
parameters to DHCPv4 clients. |
| 314 |
|
| 315 |
o "DSLAM" |
| 316 |
|
| 317 |
DSLAM stands for Digital Subscriber Line Access Multiplexer. |
| 318 |
|
| 319 |
o "downstream" |
| 320 |
|
| 321 |
Downstream refers to a direction away from the central part of a |
| 322 |
network and toward the edge. In a DHCPv4 context, this typically |
| 323 |
refers to a network direction that is away from the DHCPv4 server |
| 324 |
and toward the DHCPv4 client. |
| 325 |
|
| 326 |
o "Global VPN" |
| 327 |
|
| 328 |
Global VPN is another name for the default VPN. |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Kinnear, 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="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 335 |
|
| 336 |
|
| 337 |
o "IP address" |
| 338 |
|
| 339 |
In this document, the term "IP address" refers to an IPv4 IP |
| 340 |
address. |
| 341 |
|
| 342 |
o "IP address binding" |
| 343 |
|
| 344 |
An IP address binding is the information that a DHCPv4 server |
| 345 |
keeps regarding the relationship between a DHCPv4 client and an IP |
| 346 |
address. This includes the identity of the DHCPv4 client and the |
| 347 |
expiration time, if any, of any lease that client has on a |
| 348 |
particular IP address. In some contexts, this may include |
| 349 |
information on IP addresses that are currently associated with |
| 350 |
DHCPv4 clients, and in others, it may also include IP addresses |
| 351 |
with no current association to a DHCPv4 client. |
| 352 |
|
| 353 |
o "MAC address" |
| 354 |
|
| 355 |
In the context of a DHCPv4 message, a Media Access Control (MAC) |
| 356 |
address consists of the fields: hardware type "htype", hardware |
| 357 |
length "hlen", and client hardware address "chaddr". |
| 358 |
|
| 359 |
o "upstream" |
| 360 |
|
| 361 |
Upstream refers to a direction toward the central part of a |
| 362 |
network and away from the edge. In a DHCPv4 context, this |
| 363 |
typically refers to a network direction that is away from the |
| 364 |
DHCPv4 client and toward the DHCPv4 server. |
| 365 |
|
| 366 |
o "stable storage" |
| 367 |
|
| 368 |
Stable storage is used to hold information concerning IP address |
| 369 |
bindings (among other things) so that this information is not lost |
| 370 |
in the event of a failure that requires restart of the network |
| 371 |
element. DHCPv4 servers are typically expected to have high-speed |
| 372 |
access to stable storage, while relay agents and access |
| 373 |
concentrators usually do not have access to stable storage, |
| 374 |
although they may have periodic access to such storage. |
| 375 |
|
| 376 |
o "xid" |
| 377 |
|
| 378 |
Transaction-id. The term "xid" refers to the DHCPv4 field |
| 379 |
containing the transaction-id of the message. |
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Kinnear, 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="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Design Goals</span> |
| 394 |
|
| 395 |
The goal of this document is to provide a lightweight protocol for an |
| 396 |
access concentrator or other network element (such as a DHCP relay |
| 397 |
agent) to retrieve IP address binding information available in the |
| 398 |
DHCPv4 server. The protocol should also allow an access concentrator |
| 399 |
or DHCP relay agent to retrieve consolidated IP address binding |
| 400 |
information for either the entire access concentrator or a single |
| 401 |
connection/circuit. Throughout the discussion below, everything that |
| 402 |
applies to an access concentrator also applies to a DHCP relay agent. |
| 403 |
|
| 404 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Information Acquisition before Data Starts</span> |
| 405 |
|
| 406 |
The existing data-driven approach required by [<a href="./rfc4388" title=""Dynamic Host Configuration Protocol (DHCP) Leasequery"">RFC4388</a>] means that |
| 407 |
the Leasequeries can only be performed after an access concentrator |
| 408 |
receives data. To implement antispoofing, the concentrator must drop |
| 409 |
messages for each client until it gets lease information from the |
| 410 |
DHCPv4 server for that client. If an access concentrator finishes |
| 411 |
the Leasequeries before it starts receiving data, then there is no |
| 412 |
need to drop legitimate messages. In this way, outage time may be |
| 413 |
reduced. |
| 414 |
|
| 415 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Lessen Need for Caching and Negative Caching</span> |
| 416 |
|
| 417 |
The result of a single Leasequery should be cached, whether that |
| 418 |
results in a positive or negative cache, in order to remember that |
| 419 |
the Leasequery was performed. This caching is required to limit the |
| 420 |
traffic imposed upon a DHCPv4 server by Leasequeries for information |
| 421 |
already received. |
| 422 |
|
| 423 |
These caches not only consume precious resources, they also need to |
| 424 |
be managed. Hence, they should be avoided as much as possible. One |
| 425 |
of the goals of the DHCPv4 Bulk Leasequery is to reduce the need for |
| 426 |
this sort of caching. |
| 427 |
|
| 428 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Antispoofing in 'Fast Path'</span> |
| 429 |
|
| 430 |
If antispoofing is not done in the fast path, it will become a |
| 431 |
bottleneck and may lead to denial of service of the access |
| 432 |
concentrator. The Leasequeries should make it possible to do |
| 433 |
antispoofing in the fast path. |
| 434 |
|
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Kinnear, et al. Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 447 |
|
| 448 |
|
| 449 |
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Minimize Data Transmission</span> |
| 450 |
|
| 451 |
It may be that a network element is able to periodically save its |
| 452 |
entire list of assigned IP addresses to some form of stable storage. |
| 453 |
In this case, it will wish to recover all of the updates to this |
| 454 |
information without duplicating the information it has recovered from |
| 455 |
its own stable storage. |
| 456 |
|
| 457 |
Bulk Leasequery allows the specification of a query-start-time as |
| 458 |
well as a query-end-time. Use of query times allows a network |
| 459 |
element that periodically commits information to stable storage to |
| 460 |
recover just what it lost since the last commit. |
| 461 |
|
| 462 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Protocol Overview</span> |
| 463 |
|
| 464 |
The DHCPv4 Bulk Leasequery protocol is modeled on the existing |
| 465 |
individual DHCPv4 Leasequery protocol in [<a href="./rfc4388" title=""Dynamic Host Configuration Protocol (DHCP) Leasequery"">RFC4388</a>] as well as related |
| 466 |
work on DHCPv6 Bulk Leasequery [<a href="./rfc5460" title=""DHCPv6 Bulk Leasequery"">RFC5460</a>]. A Bulk Leasequery |
| 467 |
requestor opens a TCP connection to a DHCPv4 server using the DHCPv4 |
| 468 |
port 67. Note that this implies that the Leasequery requestor has |
| 469 |
server IP address(es) available via configuration or some other means |
| 470 |
and that it has unicast IP reachability to the DHCPv4 server. No |
| 471 |
relaying of Bulk Leasequery messages is specified. |
| 472 |
|
| 473 |
After establishing a connection, the requestor sends a |
| 474 |
DHCPBULKLEASEQUERY message over the connection. |
| 475 |
|
| 476 |
The server uses the message type and additional data in the DHCPv4 |
| 477 |
DHCPBULKLEASEQUERY message to identify any relevant bindings. |
| 478 |
|
| 479 |
In order to support some query types, servers may have to maintain |
| 480 |
additional data structures or otherwise be able to locate bindings |
| 481 |
that have been requested by the Leasequery requestor. |
| 482 |
|
| 483 |
Relevant bindings are returned in DHCPv4 messages with either the |
| 484 |
DHCPLEASEACTIVE message type for an IP address with a currently |
| 485 |
active lease or, in some situations, a DHCPLEASEUNASSIGNED message |
| 486 |
type for an IP address that is controlled by the DHCPv4 server but is |
| 487 |
not actively leased by a DHCPv4 client at the present time. |
| 488 |
|
| 489 |
The Bulk Leasequery protocol is designed to provide an external |
| 490 |
entity with information concerning existing DHCPv4 IPv4 address |
| 491 |
bindings managed by the DHCPv4 server. When complete, the DHCPv4 |
| 492 |
server will send a DHCPLEASEQUERYDONE message. If a connection is |
| 493 |
lost while processing a Bulk Leasequery, the Bulk Leasequery must be |
| 494 |
retried as there is no provision for determining the extent of data |
| 495 |
already received by the requestor for a Bulk Leasequery. |
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Kinnear, et al. Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 503 |
|
| 504 |
|
| 505 |
Bulk Leasequery supports queries by MAC address and by Client |
| 506 |
Identifier in a way similar to [<a href="./rfc4388" title=""Dynamic Host Configuration Protocol (DHCP) Leasequery"">RFC4388</a>]. The Bulk Leasequery |
| 507 |
protocol also adds several new queries. |
| 508 |
|
| 509 |
o Query by Relay Identifier |
| 510 |
|
| 511 |
This query asks a server for the bindings associated with a |
| 512 |
specific relay agent; the relay agent is identified by a Relay |
| 513 |
Agent Identifier carried in a Relay-ID sub-option [<a href="./rfc6925" title=""The DHCPv4 Relay Agent Identifier Sub-Option"">RFC6925</a>]. |
| 514 |
Relay agents can include this sub-option while relaying messages |
| 515 |
to DHCPv4 servers. Servers can retain the Relay-ID and associate |
| 516 |
it with bindings made on behalf of the relay agent's clients. The |
| 517 |
bindings returned are only those for DHCPv4 clients with a |
| 518 |
currently active binding. |
| 519 |
|
| 520 |
o Query by Remote ID |
| 521 |
|
| 522 |
This query asks a server for the bindings associated with a relay |
| 523 |
agent Remote ID sub-option [<a href="./rfc3046" title=""DHCP Relay Agent Information Option"">RFC3046</a>] value. The bindings returned |
| 524 |
are only those for DHCPv4 clients with a currently active binding. |
| 525 |
|
| 526 |
o Query for All Configured IP Addresses |
| 527 |
|
| 528 |
This query asks a server for information concerning all IP |
| 529 |
addresses configured in that DHCPv4 server by specifying no other |
| 530 |
type of query. In this case, the bindings returned are for all |
| 531 |
configured IP addresses, whether or not they contain a currently |
| 532 |
active binding to a DHCPv4 client, since one point of this type of |
| 533 |
query is to update an existing database with changes after a |
| 534 |
particular point in time. |
| 535 |
|
| 536 |
Any of the above queries can be qualified by the specification of a |
| 537 |
query-start-time or a query-end-time (or both). When these timers |
| 538 |
are used as qualifiers, they indicate that a binding should be |
| 539 |
included if it changed on or after the query-start-time and on or |
| 540 |
before the query-end-time. |
| 541 |
|
| 542 |
In addition, any of the above queries can be qualified by the |
| 543 |
specification of a VPN-ID option [<a href="./rfc6607" title=""Virtual Subnet Selection Options for DHCPv4 and DHCPv6"">RFC6607</a>] to select the VPN on which |
| 544 |
the query should be processed. The VPN-ID option is also extended to |
| 545 |
allow queries across all available VPNs. In the absence of any VPN- |
| 546 |
ID option, only the default (global) VPN is used to satisfy the |
| 547 |
query. |
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Kinnear, et al. Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 559 |
|
| 560 |
|
| 561 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Interaction between UDP Leasequery and Bulk Leasequery</span> |
| 562 |
|
| 563 |
Bulk Leasequery can be seen as an extension of the existing UDP |
| 564 |
Leasequery protocol [<a href="./rfc4388" title=""Dynamic Host Configuration Protocol (DHCP) Leasequery"">RFC4388</a>]. This section clarifies the |
| 565 |
relationship between the two protocols. |
| 566 |
|
| 567 |
The Bulk Leasequery TCP connection is only designed to handle the |
| 568 |
DHCPBULKLEASEQUERY request. It is not intended as an alternative |
| 569 |
DHCPv4 communication option for clients seeking other DHCPv4 |
| 570 |
services. DHCPv4 address allocation could not be performed over a |
| 571 |
TCP connection in any case, as a TCP connection requires an IP |
| 572 |
address and no IPv4 address exists prior to a successful DHCPv4 |
| 573 |
address allocation exchange. In addition, the existing DHCPv4 UDP |
| 574 |
transmission regime is implemented in untold millions of devices |
| 575 |
deployed worldwide, and complicating DHCPv4 services with alternative |
| 576 |
transmission approaches (even if it were possible) would be worse |
| 577 |
than any perceived benefit to doing so. |
| 578 |
|
| 579 |
Two of the query types introduced in the UDP Leasequery protocol can |
| 580 |
be used in the Bulk Leasequery protocol -- Query by MAC address and |
| 581 |
Query by Client-identifier. |
| 582 |
|
| 583 |
The contents of the reply messages are similar between the existing |
| 584 |
UDP Leasequery protocol and the Bulk Leasequery protocol, though more |
| 585 |
information is returned in the Bulk Leasequery messages. |
| 586 |
|
| 587 |
One change in behavior for these existing queries is required when |
| 588 |
Bulk Leasequery is used. Sections <a href="#section-6.1">6.1</a>, <a href="#section-6.4.1">6.4.1</a>, and <a href="#section-6.4.2">6.4.2</a> of [<a href="./rfc4388" title=""Dynamic Host Configuration Protocol (DHCP) Leasequery"">RFC4388</a>] |
| 589 |
specify the use of an associated-ip option in DHCPLEASEACTIVE |
| 590 |
messages in cases where multiple bindings were found. When Bulk |
| 591 |
Leasequery is used, this mechanism is not necessary; a server |
| 592 |
returning multiple bindings simply does so directly as specified in |
| 593 |
this document. The associated-ip option MUST NOT appear in Bulk |
| 594 |
Leasequery replies. |
| 595 |
|
| 596 |
Implementors should note that the TCP message framing defined in |
| 597 |
<a href="#section-6.1">Section 6.1</a> is not compatible with the UDP message format. If a TCP- |
| 598 |
framed request is sent as a UDP message, it may not be valid, because |
| 599 |
protocol fields will be offset by the message-size prefix. |
| 600 |
|
| 601 |
|
| 602 |
|
| 603 |
|
| 604 |
|
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Kinnear, et al. Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 615 |
|
| 616 |
|
| 617 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Message and Option Definitions</span> |
| 618 |
|
| 619 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Message Framing for TCP</span> |
| 620 |
|
| 621 |
The use of TCP for the Bulk Leasequery protocol permits multiple |
| 622 |
messages to be sent from one end of the connection to the other |
| 623 |
without requiring a request/response paradigm as does UDP DHCPv4 |
| 624 |
[<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>]. The receiver needs to be able to determine the size of |
| 625 |
each message it receives. Two octets containing the message size in |
| 626 |
network byte order are prepended to each DHCPv4 message sent on a |
| 627 |
Bulk Leasequery TCP connection. The two message-size octets 'frame' |
| 628 |
each DHCPv4 message. |
| 629 |
|
| 630 |
The maximum message size is 65535 octets. |
| 631 |
|
| 632 |
0 1 2 3 |
| 633 |
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 |
| 634 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 635 |
| message-size | op (1) | htype (1) | |
| 636 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 637 |
| hlen (1) | hops (1) | .... | |
| 638 |
+---------------+---------------+ + |
| 639 |
| | |
| 640 |
. remainder of DHCPv4 message, |
| 641 |
. from Figure 1 of [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>] . |
| 642 |
. . |
| 643 |
. (variable) . |
| 644 |
| | |
| 645 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 646 |
|
| 647 |
message-size the number of octets in the message that |
| 648 |
follows, as a 16-bit unsigned integer in |
| 649 |
network byte order. |
| 650 |
|
| 651 |
All other fields are as specified in DHCPv4 [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>]. |
| 652 |
|
| 653 |
Figure 2: Format of a DHCPv4 Message in TCP |
| 654 |
|
| 655 |
The intent in using this format is that code that currently knows how |
| 656 |
to deal with sending or receiving a message in [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>] format will |
| 657 |
easily be able to deal with the message contained in the TCP framing. |
| 658 |
|
| 659 |
|
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Kinnear, et al. Standards Track [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 671 |
|
| 672 |
|
| 673 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. New or Changed Options</span> |
| 674 |
|
| 675 |
The existing messages DHCPLEASEUNASSIGNED and DHCPLEASEACTIVE are |
| 676 |
used as the value of the dhcp-message-type option to indicate an IP |
| 677 |
address that is currently not leased or currently leased to a DHCPv4 |
| 678 |
client, respectively [<a href="./rfc4388" title=""Dynamic Host Configuration Protocol (DHCP) Leasequery"">RFC4388</a>]. |
| 679 |
|
| 680 |
Additional options have also been defined to enable the Bulk |
| 681 |
Leasequery protocol to communicate useful information to the |
| 682 |
requestor. |
| 683 |
|
| 684 |
<span class="h4"><a class="selflink" id="section-6.2.1" href="#section-6.2.1">6.2.1</a>. dhcp-message-type</span> |
| 685 |
|
| 686 |
The dhcp-message-type option (option 53) from <a href="./rfc2132#section-9.6">Section 9.6 of |
| 687 |
[RFC2132]</a> requires new values. The values of these message types are |
| 688 |
shown below in an extension of the table from <a href="./rfc2132#section-9.6">Section 9.6 of |
| 689 |
[RFC2132]</a>: |
| 690 |
|
| 691 |
Value Message Type |
| 692 |
----- ------------ |
| 693 |
14 DHCPBULKLEASEQUERY |
| 694 |
15 DHCPLEASEQUERYDONE |
| 695 |
|
| 696 |
<span class="h4"><a class="selflink" id="section-6.2.2" href="#section-6.2.2">6.2.2</a>. status-code</span> |
| 697 |
|
| 698 |
The status-code option allows a machine-readable value to be returned |
| 699 |
regarding the status of a DHCPBULKLEASEQUERY request. |
| 700 |
|
| 701 |
This option has two possible scopes when used with Bulk Leasequery, |
| 702 |
depending on the context in which it appears. It refers to the |
| 703 |
information in a single Leasequery reply if the value of the dhcp- |
| 704 |
message-type is DHCPLEASEACTIVE or DHCPLEASEUNASSIGNED. It refers to |
| 705 |
the message stream related to an entire request if the value of the |
| 706 |
dhcp-message-type is DHCPLEASEQUERYDONE. |
| 707 |
|
| 708 |
The code for this option is 151. The length of this option is a |
| 709 |
minimum of 1 octet. |
| 710 |
|
| 711 |
Status Status |
| 712 |
Code Len Code Message |
| 713 |
+------+------+------+------+------+-- --+-----+ |
| 714 |
| 151 | n+1 |status| s1 | s2 | ... | sn | |
| 715 |
+------+------+------+------+------+-- --+-----+ |
| 716 |
|
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Kinnear, et al. Standards Track [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 727 |
|
| 728 |
|
| 729 |
The status-code is indicated in one octet as defined in the table |
| 730 |
below. The Status Message is an optional UTF-8-encoded text string |
| 731 |
suitable for display to an end user. This text string MUST NOT |
| 732 |
contain a termination character (e.g., a null). The Len field |
| 733 |
describes the length of the Status Message without any terminator |
| 734 |
character. Null characters MUST NOT appear in the Status Message |
| 735 |
string, and it is a protocol violation for them to appear in any |
| 736 |
position in the Status Message, including at the end. |
| 737 |
|
| 738 |
Name Status Code Description |
| 739 |
---- ----------- ----------- |
| 740 |
Success 000 Success. Also signaled by absence of |
| 741 |
a status-code option. |
| 742 |
|
| 743 |
UnspecFail 001 Failure, reason unspecified. |
| 744 |
|
| 745 |
QueryTerminated 002 Indicates that the server is unable to |
| 746 |
perform a query or has prematurely terminated |
| 747 |
the query for some reason (which should be |
| 748 |
communicated in the text message). |
| 749 |
|
| 750 |
MalformedQuery 003 The query was not understood. |
| 751 |
|
| 752 |
NotAllowed 004 The query or request was understood but was |
| 753 |
not allowed in this context. |
| 754 |
|
| 755 |
A status-code option MAY appear in the options field of a DHCPv4 |
| 756 |
message. If the status-code option does not appear, it is assumed |
| 757 |
that the operation was successful. The status-code option SHOULD NOT |
| 758 |
appear in a message that is successful unless there is some text |
| 759 |
string that needs to be communicated to the requestor. |
| 760 |
|
| 761 |
<span class="h4"><a class="selflink" id="section-6.2.3" href="#section-6.2.3">6.2.3</a>. base-time</span> |
| 762 |
|
| 763 |
The base-time option is the current time the message was created to |
| 764 |
be sent by the DHCPv4 server to the requestor of the Bulk Leasequery. |
| 765 |
This MUST be an absolute time. All of the other time-based options |
| 766 |
in the reply message are relative to this time, including the dhcp- |
| 767 |
lease-time [<a href="./rfc2132" title=""DHCP Options and BOOTP Vendor Extensions"">RFC2132</a>] and client-last-transaction-time [<a href="./rfc4388" title=""Dynamic Host Configuration Protocol (DHCP) Leasequery"">RFC4388</a>]. |
| 768 |
This time is in the context of the DHCPv4 server that placed this |
| 769 |
option in a message. |
| 770 |
|
| 771 |
This is an unsigned integer in network byte order. |
| 772 |
|
| 773 |
|
| 774 |
|
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Kinnear, et al. Standards Track [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 783 |
|
| 784 |
|
| 785 |
The code for this option is 152. The length of this option is 4 |
| 786 |
octets. |
| 787 |
|
| 788 |
DHCPv4 Server |
| 789 |
Code Len base-time |
| 790 |
+-----+-----+-----+-----+-----+-----+ |
| 791 |
| 152 | 4 | t1 | t2 | t3 | t4 | |
| 792 |
+-----+-----+-----+-----+-----+-----+ |
| 793 |
|
| 794 |
<span class="h4"><a class="selflink" id="section-6.2.4" href="#section-6.2.4">6.2.4</a>. start-time-of-state</span> |
| 795 |
|
| 796 |
The start-time-of-state option allows the receiver to determine the |
| 797 |
time at which the IP address made the transition into its current |
| 798 |
state. |
| 799 |
|
| 800 |
This MUST NOT be an absolute time, which is equivalent to saying that |
| 801 |
this MUST NOT be an absolute number of seconds since January 1, 1970. |
| 802 |
Instead, this MUST be the unsigned integer number of seconds from the |
| 803 |
time the IP address transitioned its current state to the time |
| 804 |
specified in the base-time option in the same message. |
| 805 |
|
| 806 |
This is an unsigned integer in network byte order. |
| 807 |
|
| 808 |
The code for this option is 153. The length of this option is 4 |
| 809 |
octets. |
| 810 |
|
| 811 |
Seconds in the past |
| 812 |
Code Len from base-time |
| 813 |
+-----+-----+-----+-----+-----+-----+ |
| 814 |
| 153 | 4 | t1 | t2 | t3 | t4 | |
| 815 |
+-----+-----+-----+-----+-----+-----+ |
| 816 |
|
| 817 |
<span class="h4"><a class="selflink" id="section-6.2.5" href="#section-6.2.5">6.2.5</a>. query-start-time</span> |
| 818 |
|
| 819 |
The query-start-time option specifies a start query time to the |
| 820 |
DHCPv4 server. If specified, only bindings that have changed on or |
| 821 |
after the query-start-time should be included in the response to the |
| 822 |
query. |
| 823 |
|
| 824 |
The requestor MUST determine the query-start-time using lease |
| 825 |
information it has received from the DHCPv4 server. This MUST be an |
| 826 |
absolute time in the DHCPv4 server's context (see <a href="#section-7.4">Section 7.4</a>). |
| 827 |
|
| 828 |
Typically (though this is not a requirement), the query-start-time |
| 829 |
option will contain the value most recently received in a base-time |
| 830 |
option by the requestor, as this will indicate the last successful |
| 831 |
communication with the DHCP server. |
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Kinnear, et al. Standards Track [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 839 |
|
| 840 |
|
| 841 |
This MUST be an absolute time. |
| 842 |
|
| 843 |
This is an unsigned integer in network byte order. |
| 844 |
|
| 845 |
The code for this option is 154. The length of this option is 4 |
| 846 |
octets. |
| 847 |
|
| 848 |
DHCPv4 Server |
| 849 |
Code Len query-start-time |
| 850 |
+-----+-----+-----+-----+-----+-----+ |
| 851 |
| 154 | 4 | t1 | t2 | t3 | t4 | |
| 852 |
+-----+-----+-----+-----+-----+-----+ |
| 853 |
|
| 854 |
<span class="h4"><a class="selflink" id="section-6.2.6" href="#section-6.2.6">6.2.6</a>. query-end-time</span> |
| 855 |
|
| 856 |
The query-end-time option specifies an end query time to the DHCPv4 |
| 857 |
server. If specified, only bindings that have changed on or before |
| 858 |
the query-end-time should be included in the response to the query. |
| 859 |
|
| 860 |
The requestor MUST determine the query-end-time based on lease |
| 861 |
information it has received from the DHCPv4 server. This MUST be an |
| 862 |
absolute time in the context of the DHCPv4 server. |
| 863 |
|
| 864 |
In the absence of information to the contrary, the requestor SHOULD |
| 865 |
assume that the time context of the DHCPv4 server is identical to the |
| 866 |
time context of the requestor (see <a href="#section-7.4">Section 7.4</a>). |
| 867 |
|
| 868 |
This is an unsigned integer in network byte order. |
| 869 |
|
| 870 |
The code for this option is 155. The length of this option is 4 |
| 871 |
octets. |
| 872 |
|
| 873 |
DHCPv4 Server |
| 874 |
Code Len query-end-time |
| 875 |
+-----+-----+-----+-----+-----+-----+ |
| 876 |
| 155 | 4 | t1 | t2 | t3 | t4 | |
| 877 |
+-----+-----+-----+-----+-----+-----+ |
| 878 |
|
| 879 |
|
| 880 |
|
| 881 |
|
| 882 |
|
| 883 |
|
| 884 |
|
| 885 |
|
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Kinnear, et al. Standards Track [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 895 |
|
| 896 |
|
| 897 |
<span class="h4"><a class="selflink" id="section-6.2.7" href="#section-6.2.7">6.2.7</a>. dhcp-state</span> |
| 898 |
|
| 899 |
The dhcp-state option allows greater detail to be returned than |
| 900 |
allowed by the DHCPLEASEACTIVE and DHCPLEASEUNASSIGNED message types. |
| 901 |
|
| 902 |
The code for this option is 156. The length of this option is 1 |
| 903 |
octet. |
| 904 |
|
| 905 |
0 1 2 |
| 906 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 |
| 907 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 908 |
| 156 | Length | State | |
| 909 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 910 |
|
| 911 |
156 The option code. |
| 912 |
|
| 913 |
Length The option length, 1 octet. |
| 914 |
|
| 915 |
State The state of the IP address. |
| 916 |
|
| 917 |
Value State |
| 918 |
----- ----- |
| 919 |
1 AVAILABLE Address is available to local DHCPv4 server |
| 920 |
2 ACTIVE Address is assigned to a DHCPv4 client |
| 921 |
3 EXPIRED Lease has expired |
| 922 |
4 RELEASED Lease has been released by DHCPv4 client |
| 923 |
5 ABANDONED Server or client flagged address as unusable |
| 924 |
6 RESET Lease was freed by some external agent |
| 925 |
7 REMOTE Address is available to a remote DHCPv4 server |
| 926 |
8 TRANSITIONING Address is moving between states |
| 927 |
|
| 928 |
Note that some of these states may be transient and may not appear in |
| 929 |
normal use. A DHCPv4 server MUST implement at least the AVAILABLE |
| 930 |
and ACTIVE states and SHOULD implement at least the ABANDONED and |
| 931 |
RESET states. |
| 932 |
|
| 933 |
Note the states AVAILABLE and REMOTE are relative to the current |
| 934 |
server. An address that is available to the current server should |
| 935 |
show AVAILABLE on that server, and if another server is involved with |
| 936 |
that address as well, it should show as REMOTE on that other server. |
| 937 |
|
| 938 |
The dhcp-state option SHOULD contain ACTIVE when it appears in a |
| 939 |
DHCPLEASEACTIVE message. A DHCPv4 server MAY choose to not send a |
| 940 |
dhcp-state option in a DHCPLEASEACTIVE message, and a requestor |
| 941 |
SHOULD assume that the dhcp-state is ACTIVE if no dhcp-state option |
| 942 |
appears in a DHCPLEASEACTIVE message. |
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Kinnear, et al. Standards Track [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 951 |
|
| 952 |
|
| 953 |
The reference to local and remote relate to possible use in an |
| 954 |
environment that includes multiple servers cooperating to provide an |
| 955 |
increased availability solution. In this case, an IP address with |
| 956 |
the state of AVAILABLE is available to the local server, while one |
| 957 |
with the state of REMOTE is available to a remote server. Usually, |
| 958 |
an IP address that is AVAILABLE on one server would be REMOTE on any |
| 959 |
remote server. The TRANSITIONING state is also likely to be useful |
| 960 |
in multiple server deployments, where sometimes one server must |
| 961 |
interlock a state change with one or more other servers. Should a |
| 962 |
Bulk Leasequery need to send information concerning the state of the |
| 963 |
IP address during this period, it SHOULD use the TRANSITIONING state, |
| 964 |
since the IP address is likely to be neither ACTIVE or AVAILABLE. |
| 965 |
|
| 966 |
There is no requirement for the state of an IP address to transition |
| 967 |
in a well-defined way from state to state. To put this another way, |
| 968 |
you cannot draw a simple state transition graph for the states of an |
| 969 |
IP address, and the requestor of a Leasequery MUST NOT depend on one |
| 970 |
certain state always following a particular previous state. While a |
| 971 |
state transition diagram can be drawn, it would be fully connected |
| 972 |
and therefore conveys no useful information. Every state can (at |
| 973 |
times) follow every other state. |
| 974 |
|
| 975 |
<span class="h4"><a class="selflink" id="section-6.2.8" href="#section-6.2.8">6.2.8</a>. data-source</span> |
| 976 |
|
| 977 |
The data-source option contains information about the source of the |
| 978 |
data in a DHCPLEASEACTIVE or a DHCPLEASEUNASSIGNED message. It |
| 979 |
SHOULD be used when there are two or more servers that might have |
| 980 |
information about a particular IP address binding. Frequently, two |
| 981 |
servers work together to provide an increased availability solution |
| 982 |
for the DHCPv4 service, and in these cases, both servers will respond |
| 983 |
to Bulk Leasequery requests for the same IP address. When one server |
| 984 |
is working with another server and both may respond with information |
| 985 |
about the same IP address, each server SHOULD return the data-source |
| 986 |
option with the other information provided about the IP address. |
| 987 |
|
| 988 |
The data contained in this option will allow an external process to |
| 989 |
better discriminate between the information provided by each of the |
| 990 |
servers servicing this IPv4 address. |
| 991 |
|
| 992 |
|
| 993 |
|
| 994 |
|
| 995 |
|
| 996 |
|
| 997 |
|
| 998 |
|
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Kinnear, et al. Standards Track [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
The code for this option is 157. The length of this option is 1 |
| 1010 |
octet. |
| 1011 |
|
| 1012 |
0 1 2 |
| 1013 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 |
| 1014 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1015 |
| 157 | Length | Flags | |
| 1016 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1017 |
|
| 1018 |
157 The option code. |
| 1019 |
|
| 1020 |
Length The option length, 1 octet. |
| 1021 |
|
| 1022 |
Flags The source information for this message. |
| 1023 |
|
| 1024 |
0 1 2 3 4 5 6 7 |
| 1025 |
+-+-+-+-+-+-+-+-+ |
| 1026 |
| UNA |R| |
| 1027 |
+-+-+-+-+-+-+-+-+ |
| 1028 |
|
| 1029 |
R: REMOTE flag |
| 1030 |
|
| 1031 |
remote = 1 |
| 1032 |
local = 0 |
| 1033 |
|
| 1034 |
UNA: UNASSIGNED |
| 1035 |
|
| 1036 |
The REMOTE flag is used to indicate where the most recent change of |
| 1037 |
state (or other interesting change) concerning this IPv4 address took |
| 1038 |
place. If the value is local, then the change took place on the |
| 1039 |
server from which this message was transmitted. If the value is |
| 1040 |
remote, then the change took place on some other server and was made |
| 1041 |
known to the server from which this message was transmitted. |
| 1042 |
|
| 1043 |
If this option was requested and it doesn't appear, the requestor |
| 1044 |
MUST consider that the data-source was local. |
| 1045 |
|
| 1046 |
Unassigned bits MUST be ignored. |
| 1047 |
|
| 1048 |
|
| 1049 |
|
| 1050 |
|
| 1051 |
|
| 1052 |
|
| 1053 |
|
| 1054 |
|
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Kinnear, et al. Standards Track [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
<span class="h4"><a class="selflink" id="section-6.2.9" href="#section-6.2.9">6.2.9</a>. Virtual Subnet Selection Type and Information</span> |
| 1066 |
|
| 1067 |
All of the (sub-)options defined in [<a href="./rfc6607" title=""Virtual Subnet Selection Options for DHCPv4 and DHCPv6"">RFC6607</a>] carry identical |
| 1068 |
payloads, consisting of a type and additional VSS (Virtual Subnet |
| 1069 |
Selection) information. The existing table is extended (see below) |
| 1070 |
with a new type 254 to allow specification of a type code that |
| 1071 |
indicates that all VPNs are to be used to process the Bulk |
| 1072 |
Leasequery. |
| 1073 |
|
| 1074 |
Type VSS Information Format |
| 1075 |
---------------------------------------------------------- |
| 1076 |
0 Network Virtual Terminal (NVT) ASCII VPN identifier |
| 1077 |
1 <a href="./rfc2685">RFC 2685</a> VPN-ID |
| 1078 |
CHANGED -> 2-253 Unassigned |
| 1079 |
NEW -> 254 All VPNs (wildcard) |
| 1080 |
255 Global, default VPN |
| 1081 |
|
| 1082 |
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Connection and Transmission Parameters</span> |
| 1083 |
|
| 1084 |
DHCPv4 servers that support Bulk Leasequery SHOULD listen for |
| 1085 |
incoming TCP connections on the DHCPv4 server port 67. |
| 1086 |
Implementations MAY offer to make the incoming port configurable, but |
| 1087 |
port 67 MUST be the default. Requestors SHOULD make TCP connections |
| 1088 |
to port 67 and MAY offer to make the destination server port |
| 1089 |
configurable. |
| 1090 |
|
| 1091 |
This section presents a table of values used to control Bulk |
| 1092 |
Leasequery behavior, including recommended defaults. Implementations |
| 1093 |
MAY make these values configurable. However, configuring too-small |
| 1094 |
timeout values may lead to harmful behavior both to this application |
| 1095 |
as well as to other traffic in the network. As a result, timeout |
| 1096 |
values smaller than the default values are NOT RECOMMENDED. |
| 1097 |
|
| 1098 |
Parameter Default Description |
| 1099 |
-------------------------------------------------------------------- |
| 1100 |
BULK_LQ_DATA_TIMEOUT 300 secs Bulk Leasequery data timeout |
| 1101 |
for both client and server |
| 1102 |
(see Sections <a href="#section-7">7</a> and <a href="#section-8">8</a>) |
| 1103 |
BULK_LQ_MAX_CONNS 10 Max Bulk Leasequery TCP connections |
| 1104 |
at the server side (see <a href="#section-8.1">Section 8.1</a>) |
| 1105 |
|
| 1106 |
|
| 1107 |
|
| 1108 |
|
| 1109 |
|
| 1110 |
|
| 1111 |
|
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Kinnear, et al. Standards Track [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Requestor Behavior</span> |
| 1122 |
|
| 1123 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Connecting and General Processing</span> |
| 1124 |
|
| 1125 |
A requestor attempts to establish a TCP connection to a DHCPv4 server |
| 1126 |
in order to initiate a Leasequery exchange. If the attempt fails, |
| 1127 |
the requestor MAY retry. |
| 1128 |
|
| 1129 |
If Bulk Leasequery is terminated prematurely by a DHCPLEASEQUERYDONE |
| 1130 |
with a status-code option with a status code of QueryTerminated or by |
| 1131 |
the failure of the connection over which it was being submitted, the |
| 1132 |
requestor MAY retry the request after the creation of a new |
| 1133 |
connection. |
| 1134 |
|
| 1135 |
Messages from the DHCPv4 server come as multiple responses to a |
| 1136 |
single DHCPBULKLEASEQUERY message. Thus, each DHCPBULKLEASEQUERY |
| 1137 |
request MUST have an xid (transaction-id) unique on the connection on |
| 1138 |
which it is sent. All of the messages that come as a response to |
| 1139 |
that message will contain the same xid as the request. The xid |
| 1140 |
allows the data-streams of two different DHCPBULKLEASEQUERY requests |
| 1141 |
to be demultiplexed by the requestor. |
| 1142 |
|
| 1143 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Forming a Bulk Leasequery</span> |
| 1144 |
|
| 1145 |
Bulk Leasequery is designed to create a connection that will transfer |
| 1146 |
the state of some subset (or possibly all) of the IP address bindings |
| 1147 |
from the DHCPv4 server to the requestor. The DHCPv4 server will send |
| 1148 |
all of the requested IPv4 address bindings across this connection |
| 1149 |
with minimal delay after it receives the request. In this context, |
| 1150 |
"all IP address binding information" means information about all IPv4 |
| 1151 |
addresses configured within the DHCPv4 server that meet the specified |
| 1152 |
query criteria. For some query criteria, this may include IP address |
| 1153 |
binding information for IP addresses that may not now have or ever |
| 1154 |
have had an association with a specific DHCPv4 client. |
| 1155 |
|
| 1156 |
To form the Bulk query, a DHCPv4 request is constructed with a dhcp- |
| 1157 |
message-type of DHCPBULKLEASEQUERY. The query SHOULD have a dhcp- |
| 1158 |
parameter-request-list to inform the DHCPv4 server which DHCPv4 |
| 1159 |
options are of interest to the requestor sending the |
| 1160 |
DHCPBULKLEASEQUERY message. The dhcp-parameter-request-list in a |
| 1161 |
DHCPBULKLEASEQUERY message SHOULD contain the codes for base-time, |
| 1162 |
dhcp-lease-time, start-time-of-state, and client-last-transaction- |
| 1163 |
time. |
| 1164 |
|
| 1165 |
A DHCPBULKLEASEQUERY request is constructed of one primary query and |
| 1166 |
optionally one or more qualifiers for it. |
| 1167 |
|
| 1168 |
|
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Kinnear, et al. Standards Track [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
The possible primary queries are listed below. Each |
| 1178 |
DHCPBULKLEASEQUERY request MUST contain only one of these primary |
| 1179 |
queries. |
| 1180 |
|
| 1181 |
o Query by MAC address |
| 1182 |
|
| 1183 |
In a Query by MAC address, the chaddr, htype, and hlen of the |
| 1184 |
DHCPv4 packet are filled in with the values requested. |
| 1185 |
|
| 1186 |
o Query by Client-identifier |
| 1187 |
|
| 1188 |
In a Query by Client-identifier, a Client-identifier option |
| 1189 |
containing the requested value is included in the |
| 1190 |
DHCPBULKLEASEQUERY request. |
| 1191 |
|
| 1192 |
o Query by Remote ID |
| 1193 |
|
| 1194 |
In a Query by Remote ID, a Remote ID sub-option containing the |
| 1195 |
requested value is included in the relay-agent-information option |
| 1196 |
of the DHCPBULKLEASEQUERY request. |
| 1197 |
|
| 1198 |
o Query by Relay-ID |
| 1199 |
|
| 1200 |
In a Query by Relay-ID, a Relay-ID sub-option [<a href="./rfc6925" title=""The DHCPv4 Relay Agent Identifier Sub-Option"">RFC6925</a>] containing |
| 1201 |
the requested value is included in the relay-agent-information |
| 1202 |
option of the DHCPBULKLEASEQUERY request. |
| 1203 |
|
| 1204 |
o Query for All Configured IP Addresses |
| 1205 |
|
| 1206 |
A Query for All Configured IP addresses is signaled by the absence |
| 1207 |
of any other primary query. |
| 1208 |
|
| 1209 |
There are three qualifiers that can be applied to any of the above |
| 1210 |
primary queries. These qualifiers can appear individually or |
| 1211 |
together in any combination, but only one of each can appear. |
| 1212 |
|
| 1213 |
o Query Start Time |
| 1214 |
|
| 1215 |
Inclusion of a query-start-time option specifies that only IP |
| 1216 |
address bindings that have changed on or after the time specified |
| 1217 |
in the query-start-time option should be returned. |
| 1218 |
|
| 1219 |
o Query End Time |
| 1220 |
|
| 1221 |
Inclusion of a query-end-time option specifies that only IP |
| 1222 |
address bindings that have changed on or before the time specified |
| 1223 |
in the query-end-time option should be returned. |
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Kinnear, et al. Standards Track [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
o VPN-ID |
| 1234 |
|
| 1235 |
If no VPN-ID option appears in the DHCPBULKLEASEQUERY, the default |
| 1236 |
(global) VPN is searched to satisfy the query specified by the |
| 1237 |
DHCPBULKLEASEQUERY. Using the VPN-ID option [<a href="./rfc6607" title=""Virtual Subnet Selection Options for DHCPv4 and DHCPv6"">RFC6607</a>] allows the |
| 1238 |
requestor to specify a single VPN other than the default VPN. In |
| 1239 |
addition, the VPN-ID option has been extended as part of this |
| 1240 |
document to allow specification that all configured VPNs be |
| 1241 |
searched in order to satisfy the query specified in the |
| 1242 |
DHCPBULKLEASEQUERY. |
| 1243 |
|
| 1244 |
In all cases, any message returned from a DHCPBULKLEASEQUERY |
| 1245 |
request containing information about an IP address for other than |
| 1246 |
the default (global) VPN MUST contain a VPN-ID option in the |
| 1247 |
message. |
| 1248 |
|
| 1249 |
Use of the query-start-time or the query-end-time options or both can |
| 1250 |
serve to reduce the amount of data transferred over the TCP |
| 1251 |
connection by a considerable amount. Note that the times specified |
| 1252 |
in the query-start-time or query-end-time options are absolute times, |
| 1253 |
not durations offset from "now". |
| 1254 |
|
| 1255 |
The TCP connection may become blocked or stop being writable while |
| 1256 |
the requestor is sending its query. Should this happen, the |
| 1257 |
implementation's behavior is controlled by the current value of |
| 1258 |
BULK_LQ_DATA_TIMEOUT. The default value is given elsewhere in this |
| 1259 |
document, and this value may be overridden by local configuration of |
| 1260 |
the operator. |
| 1261 |
|
| 1262 |
If this situation is detected, the requestor SHOULD start a timer |
| 1263 |
using the current value of BULK_LQ_DATA_TIMEOUT. If that timer |
| 1264 |
expires, the requestor SHOULD terminate the connection. This timer |
| 1265 |
is completely independent of any TCP timeout established by the TCP |
| 1266 |
protocol connection. |
| 1267 |
|
| 1268 |
<span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. Processing Bulk Replies</span> |
| 1269 |
|
| 1270 |
The requestor attempts to read a DHCPv4 Leasequery reply message from |
| 1271 |
the TCP connection. |
| 1272 |
|
| 1273 |
The TCP connection may stop delivering reply data (i.e., the |
| 1274 |
connection stops being readable). Should this happen, the |
| 1275 |
implementation's behavior is controlled by the current value of |
| 1276 |
BULK_LQ_DATA_TIMEOUT. The default value is given elsewhere in this |
| 1277 |
document, and this value may be overridden by local configuration of |
| 1278 |
the operator. |
| 1279 |
|
| 1280 |
|
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Kinnear, et al. Standards Track [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
If this situation is detected, the requestor SHOULD start a timer |
| 1290 |
using the current value of BULK_LQ_DATA_TIMEOUT. If that timer |
| 1291 |
expires, the requestor SHOULD terminate the connection. |
| 1292 |
|
| 1293 |
A single Bulk Leasequery can, and usually will, result in a large |
| 1294 |
number of replies. The requestor MUST be prepared to receive more |
| 1295 |
than one reply with an xid matching a single DHCPBULKLEASEQUERY |
| 1296 |
message from a single DHCPv4 server. If the xid in the received |
| 1297 |
message does not match an outstanding DHCPBULKLEASEQUERY message, the |
| 1298 |
requestor MUST close the TCP connection. |
| 1299 |
|
| 1300 |
If the requestor receives more data than it can process, it can |
| 1301 |
simply abort the connection and try again with a more specific |
| 1302 |
request. It can also simply read the TCP connection more slowly and |
| 1303 |
match the rate at which it can digest the information returned in the |
| 1304 |
Bulk Leasequery packets with the rate at which it reads those packets |
| 1305 |
from the TCP connection. |
| 1306 |
|
| 1307 |
The DHCPv4 server MUST send a server-identifier option (option 54) in |
| 1308 |
the first response to any DHCPBULKLEASEQUERY message. The DHCPv4 |
| 1309 |
server SHOULD NOT send server-identifier options in subsequent |
| 1310 |
responses to that DHCPBULKLEASEQUERY message. The requestor MUST |
| 1311 |
cache the server-identifier option from the first response and apply |
| 1312 |
it to any subsequent responses. |
| 1313 |
|
| 1314 |
The response messages generated by a DHCPBULKLEASEQUERY request are: |
| 1315 |
|
| 1316 |
o DHCPLEASEACTIVE |
| 1317 |
|
| 1318 |
A Bulk Leasequery will generate DHCPLEASEACTIVE messages |
| 1319 |
containing binding data for bound IP addresses that match the |
| 1320 |
specified query criteria. The IP address that is bound to a |
| 1321 |
DHCPv4 client will appear in the ciaddr field of the |
| 1322 |
DHCPLEASEACTIVE message. The message may contain a non-zero |
| 1323 |
chaddr, htype, hlen, and possibly additional options. |
| 1324 |
|
| 1325 |
o DHCPLEASEUNASSIGNED |
| 1326 |
|
| 1327 |
Some queries will also generate DHCPLEASEUNASSIGNED messages for |
| 1328 |
IP addresses that match the query criteria. These messages |
| 1329 |
indicate that the IP address is managed by the DHCPv4 server but |
| 1330 |
is not currently bound to any DHCPv4 client. The IP address to |
| 1331 |
which this message refers will appear in the ciaddr field of the |
| 1332 |
DHCPLEASEUNASSIGNED message. A DHCPLEASEUNASSGINED message MAY |
| 1333 |
also contain information about the last DHCPv4 client that was |
| 1334 |
bound to this IP address. The message may contain a non-zero |
| 1335 |
chaddr, htype, hlen, and possibly additional options in this case. |
| 1336 |
|
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Kinnear, et al. Standards Track [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
o DHCPLEASEQUERYDONE |
| 1346 |
|
| 1347 |
A response of DHCPLEASEQUERYDONE indicates that the server has |
| 1348 |
completed its response to the query and that no more messages will |
| 1349 |
be sent in response to the DHCPBULKLEASEQUERY. More details will |
| 1350 |
sometimes be available in the received status-code option in the |
| 1351 |
DHCPLEASEQUERYDONE message. If there is no status-code option in |
| 1352 |
the DHCPLEASEQUERYDONE message, then the query completed |
| 1353 |
successfully. |
| 1354 |
|
| 1355 |
Note that a query that returned no data, that is, a |
| 1356 |
DHCPBULKLEASEQUERY request followed by a DHCPLEASEQUERYDONE |
| 1357 |
response, is considered a successful query in that no errors |
| 1358 |
occurred during the processing. It is not considered an error to |
| 1359 |
have no information to return to a DHCPBULKLEASEQUERY request. |
| 1360 |
|
| 1361 |
The DHCPLEASEUNKNOWN message MUST NOT appear in a response to a Bulk |
| 1362 |
Leasequery. |
| 1363 |
|
| 1364 |
The requestor MUST NOT assume that there is any inherent order in the |
| 1365 |
IP address binding information that is sent in response to a |
| 1366 |
DHCPBULKLEASEQUERY. While the base-time will tend to increase |
| 1367 |
monotonically (as it is the current time on the DHCPv4 server), the |
| 1368 |
actual time that any IP address binding information changed is |
| 1369 |
unrelated to the base-time. |
| 1370 |
|
| 1371 |
The DHCPLEASEQUERYDONE message always ends a successful |
| 1372 |
DHCPBULKLEASEQUERY request and any unsuccessful DHCPBULKLEASEQUERY |
| 1373 |
requests not terminated by a dropped connection. After receiving a |
| 1374 |
DHCPLEASEQUERYDONE from a server, the requestor MAY close the TCP |
| 1375 |
connection to that server if no other DHCPBULKLEASEQUERY is |
| 1376 |
outstanding on that TCP connection. |
| 1377 |
|
| 1378 |
The DHCPv4 Leasequery protocol [<a href="./rfc4388" title=""Dynamic Host Configuration Protocol (DHCP) Leasequery"">RFC4388</a>] uses the associated-ip |
| 1379 |
option as an indicator that multiple bindings were present in |
| 1380 |
response to a single DHCPv4 client-based query. For Bulk Leasequery, |
| 1381 |
a separate message is returned for each binding, so the associated-ip |
| 1382 |
option is not used. |
| 1383 |
|
| 1384 |
<span class="h3"><a class="selflink" id="section-7.4" href="#section-7.4">7.4</a>. Processing Time Values in Leasequery Messages</span> |
| 1385 |
|
| 1386 |
Bulk Leasequery requests may be made to a DHCPv4 server whose |
| 1387 |
absolute time may not be synchronized with the local time of the |
| 1388 |
requestor. Thus, there are at least two time contexts in even the |
| 1389 |
simplest Bulk Leasequery response, and in the situation where |
| 1390 |
multiple DHCPv4 servers are queried, the situation becomes even more |
| 1391 |
complex. |
| 1392 |
|
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Kinnear, et al. Standards Track [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
If the requestor of a Bulk Leasequery is saving the data returned in |
| 1402 |
some form, it has a requirement to store a variety of time values; |
| 1403 |
some of these will be time in the context of the requestor, and some |
| 1404 |
will be time in the context of the DHCPv4 server. |
| 1405 |
|
| 1406 |
When receiving a DHCPLEASEACTIVE or DHCPLEASEUNASSIGNED message from |
| 1407 |
the DHCPv4 server, the message will contain a base-time option. The |
| 1408 |
time contained in this base-time option is in the context of the |
| 1409 |
DHCPv4 server. As such, it is an ideal time to save and use as input |
| 1410 |
to a DHCPBULKLEASEQUERY in the query-start-time or query-end-time |
| 1411 |
options, should the requestor ever need to issue a DHCPBULKLEASEQUERY |
| 1412 |
message using those options as part of a later query, since those |
| 1413 |
options require a time in the context of the DHCPv4 server. |
| 1414 |
|
| 1415 |
In addition to saving the base-time for possible future use in a |
| 1416 |
query-start-time or query-end-time option, the base-time is used as |
| 1417 |
part of the conversion of the other times in the Leasequery message |
| 1418 |
to values that are meaningful in the context of the requestor. These |
| 1419 |
other time values are specified as a offset (duration) from the base- |
| 1420 |
time value and not as an absolute time. |
| 1421 |
|
| 1422 |
In systems whose clocks are synchronized, perhaps using NTP, the |
| 1423 |
clock skew will usually be zero. |
| 1424 |
|
| 1425 |
<span class="h3"><a class="selflink" id="section-7.5" href="#section-7.5">7.5</a>. Querying Multiple Servers</span> |
| 1426 |
|
| 1427 |
A Bulk Leasequery requestor MAY be configured to attempt to connect |
| 1428 |
to and query from multiple DHCPv4 servers in parallel. The DHCPv4 |
| 1429 |
Leasequery specification [<a href="./rfc4388" title=""Dynamic Host Configuration Protocol (DHCP) Leasequery"">RFC4388</a>] includes a discussion about |
| 1430 |
reconciling binding data received from multiple DHCPv4 servers. |
| 1431 |
|
| 1432 |
In addition, the algorithm in <a href="#section-7.6">Section 7.6</a> should be used. |
| 1433 |
|
| 1434 |
<span class="h3"><a class="selflink" id="section-7.6" href="#section-7.6">7.6</a>. Making Sense out of Multiple Responses concerning a Single IPv4</span> |
| 1435 |
<span class="h3"> Address</span> |
| 1436 |
|
| 1437 |
Any requestor of an Bulk Leasequery MUST be prepared for multiple |
| 1438 |
responses to arrive for a particular IPv4 address from multiple |
| 1439 |
different DHCPv4 servers. The following algorithm SHOULD be used to |
| 1440 |
decide if the information just received is more up to date (i.e., |
| 1441 |
better) than the best existing information. In the discussion below, |
| 1442 |
the information that is received from a DHCPv4 server about a |
| 1443 |
particular IPv4 address is termed a "record". The times used in the |
| 1444 |
algorithm below SHOULD have been converted into the requestor's |
| 1445 |
context, and the time comparisons SHOULD be performed in a manner |
| 1446 |
consistent with the information in <a href="#section-7.4">Section 7.4</a>. |
| 1447 |
|
| 1448 |
|
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Kinnear, et al. Standards Track [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
o If both the existing and the new record contain client-last- |
| 1458 |
transaction-time information, the record with the later client- |
| 1459 |
last-transaction-time is considered better. |
| 1460 |
|
| 1461 |
o If one of the records contains client-last-transaction-time |
| 1462 |
information and the other one doesn't, then compare the client- |
| 1463 |
last-transaction-time in the record that contains it against the |
| 1464 |
other record's start-time-of-state. The record with the later |
| 1465 |
time is considered better. |
| 1466 |
|
| 1467 |
o If neither record contains client-last-transaction-time |
| 1468 |
information, compare their start-time-of-state information. The |
| 1469 |
record with the later start-time-of-state is considered better. |
| 1470 |
|
| 1471 |
o If none of the comparisons above yield a clear answer as to which |
| 1472 |
record is later, then compare the value of the REMOTE flag from |
| 1473 |
the data-source option for each record. If the values of the |
| 1474 |
REMOTE flag are different between the two records, the record with |
| 1475 |
the REMOTE flag value of local is considered better. |
| 1476 |
|
| 1477 |
The above algorithm does not necessarily determine which record is |
| 1478 |
better. In the event that the algorithm is inconclusive with regard |
| 1479 |
to a record that was just received by the requestor, the requestor |
| 1480 |
SHOULD use additional information in the two records to make a |
| 1481 |
determination as to which record is better. |
| 1482 |
|
| 1483 |
<span class="h3"><a class="selflink" id="section-7.7" href="#section-7.7">7.7</a>. Multiple Queries to a Single Server over One Connection</span> |
| 1484 |
|
| 1485 |
Bulk Leasequery requestors may need to make multiple queries in order |
| 1486 |
to recover binding information. A requestor MAY use a single |
| 1487 |
connection to issue multiple queries to a server willing to support |
| 1488 |
them. Each query MUST have a unique xid. |
| 1489 |
|
| 1490 |
A server SHOULD allow configuration of the number of queries that can |
| 1491 |
be processed simultaneously over a single connection. A server |
| 1492 |
SHOULD read the number of queries it is configured to process |
| 1493 |
simultaneously and only read any subsequent queries as current |
| 1494 |
queries are processed. |
| 1495 |
|
| 1496 |
A server that is processing multiple queries simultaneously MUST NOT |
| 1497 |
block sending replies on new queries until all replies for the |
| 1498 |
existing query are complete. Requestors need to be aware that |
| 1499 |
replies for multiple queries may be interleaved within the stream of |
| 1500 |
reply messages. Requestors that are not able to process interleaved |
| 1501 |
replies (based on xid) MUST NOT send more than one query over a |
| 1502 |
single connection prior to the completion of the previous query. |
| 1503 |
|
| 1504 |
|
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">Kinnear, et al. Standards Track [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
Requestors should be aware that servers are not required to process |
| 1514 |
more than one query over a connection at a time (the limiting case |
| 1515 |
for the configuration described above) and that servers are likely to |
| 1516 |
limit the rate at which they process queries from any one requestor. |
| 1517 |
|
| 1518 |
<span class="h4"><a class="selflink" id="section-7.7.1" href="#section-7.7.1">7.7.1</a>. Example</span> |
| 1519 |
|
| 1520 |
This example illustrates what a series of queries and responses might |
| 1521 |
look like. This is only an example -- there is no requirement that |
| 1522 |
this sequence must be followed or that requestors or servers must |
| 1523 |
support parallel queries. |
| 1524 |
|
| 1525 |
In the example session, the client sends four queries after |
| 1526 |
establishing a connection. Query 1 returns no results; query 2 |
| 1527 |
returns 3 messages, and the stream of replies concludes before the |
| 1528 |
client issues any new query. Query 3 and query 4 overlap, and the |
| 1529 |
server interleaves its replies to those two queries. |
| 1530 |
|
| 1531 |
Requestor Server |
| 1532 |
--------- ------ |
| 1533 |
DHCPBULKLEASEQUERY xid 1 -----> |
| 1534 |
<----- DHCPLEASEQUERYDONE xid 1 |
| 1535 |
DHCPBULKLEASEQUERY xid 2 -----> |
| 1536 |
<----- DHCPLEASEACTIVE xid 2 |
| 1537 |
<----- DHCPLEASEACTIVE xid 2 |
| 1538 |
<----- DHCPLEASEACTIVE xid 2 |
| 1539 |
<----- DHCPLEASEQUERYDONE xid 2 |
| 1540 |
DHCPBULKLEASEQUERY xid 3 -----> |
| 1541 |
DHCPBULKLEASEQUERY xid 4 -----> |
| 1542 |
<----- DHCPLEASEACTIVE xid 4 |
| 1543 |
<----- DHCPLEASEACTIVE xid 4 |
| 1544 |
<----- DHCPLEASEACTIVE xid 3 |
| 1545 |
<----- DHCPLEASEACTIVE xid 4 |
| 1546 |
<----- DHCPLEASEUNASSIGNED xid 3 |
| 1547 |
<----- DHCPLEASEACTIVE xid 4 |
| 1548 |
<----- DHCPLEASEACTIVE xid 3 |
| 1549 |
<----- DHCPLEASEQUERYDONE xid 3 |
| 1550 |
<----- DHCPLEASEACTIVE xid 4 |
| 1551 |
<----- DHCPLEASEQUERYDONE xid 4 |
| 1552 |
|
| 1553 |
<span class="h3"><a class="selflink" id="section-7.8" href="#section-7.8">7.8</a>. Closing Connections</span> |
| 1554 |
|
| 1555 |
If a requestor has no additional queries to send, or doesn't know if |
| 1556 |
it has additional queries to send or not, then it SHOULD close the |
| 1557 |
connection after receiving the DHCPLEASEQUERYDONE message for the |
| 1558 |
last outstanding query that it sent. |
| 1559 |
|
| 1560 |
|
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">Kinnear, et al. Standards Track [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
The requestor SHOULD close connections in a graceful manner and not |
| 1570 |
an abort. The requestor SHOULD NOT assume that the manner in which |
| 1571 |
the DHCP server closed a connection carries any special meaning. |
| 1572 |
|
| 1573 |
Typically, the requestor is the entity that will close the |
| 1574 |
connection, as servers will often wait with an open connection in |
| 1575 |
case the requestor has additional queries. |
| 1576 |
|
| 1577 |
If a server closes a connection with an exception condition, the |
| 1578 |
requestor SHOULD consider as valid any completely received |
| 1579 |
intermediate results, and the requestor MAY retry the Bulk Leasequery |
| 1580 |
operation. |
| 1581 |
|
| 1582 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Server Behavior</span> |
| 1583 |
|
| 1584 |
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Accepting Connections</span> |
| 1585 |
|
| 1586 |
Servers that implement DHCPv4 Bulk Leasequery listen for incoming TCP |
| 1587 |
connections. Port numbers are discussed in <a href="#section-6.3">Section 6.3</a>. Servers |
| 1588 |
MUST be able to limit the number of concurrently accepted and active |
| 1589 |
connections. The value BULK_LQ_MAX_CONNS SHOULD be the default; |
| 1590 |
implementations MAY permit the value to be configurable. Connections |
| 1591 |
SHOULD be accepted and, if the number of connections is over |
| 1592 |
BULK_LQ_MAX_CONNS, they SHOULD be closed immediately. |
| 1593 |
|
| 1594 |
Servers MAY restrict Bulk Leasequery connections and |
| 1595 |
DHCPBULKLEASEQUERY messages to certain requestors. Connections not |
| 1596 |
from permitted requestors SHOULD be closed immediately to avoid |
| 1597 |
server connection resource exhaustion. Servers MAY restrict some |
| 1598 |
requestors to certain query types. Servers MAY reply to queries that |
| 1599 |
are not permitted with the DHCPLEASEQUERYDONE message with a status- |
| 1600 |
code option status of NotAllowed or MAY simply close the connection. |
| 1601 |
|
| 1602 |
If the TCP connection becomes blocked while the server is accepting a |
| 1603 |
connection or reading a query, it SHOULD be prepared to terminate the |
| 1604 |
connection after a BULK_LQ_DATA_TIMEOUT. We make this recommendation |
| 1605 |
to allow servers to control the period of time they are willing to |
| 1606 |
wait before abandoning an inactive connection, independent of the TCP |
| 1607 |
implementations they may be using. |
| 1608 |
|
| 1609 |
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Replying to a Bulk Leasequery</span> |
| 1610 |
|
| 1611 |
If the connection becomes blocked while the server is attempting to |
| 1612 |
send reply messages, the server SHOULD be prepared to terminate the |
| 1613 |
TCP connection after a BULK_LQ_DATA_TIMEOUT. |
| 1614 |
|
| 1615 |
|
| 1616 |
|
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">Kinnear, et al. Standards Track [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
Every Bulk Leasequery request MUST be terminated by sending a final |
| 1626 |
DHCPLEASEQUERYDONE message if such a message can be sent. The |
| 1627 |
DHCPLEASEQUERYDONE message MUST have a status-code option status if |
| 1628 |
the termination was other than successful, and SHOULD NOT contain a |
| 1629 |
status-code option status if the termination was successful. |
| 1630 |
|
| 1631 |
If the DHCPv4 server encounters an error during processing of the |
| 1632 |
DHCPBULKLEASEQUERY message, either during initial processing or later |
| 1633 |
during the message processing, it SHOULD send a DHCPLEASEQUERYDONE |
| 1634 |
containing a status-code option. It MAY close the connection after |
| 1635 |
this error is signaled, but that is not required. |
| 1636 |
|
| 1637 |
If the server does not find any bindings satisfying a query, it MUST |
| 1638 |
send a DHCPLEASEQUERYDONE. It SHOULD NOT include a status-code |
| 1639 |
option with a Success status unless there is a useful string to |
| 1640 |
include in the status-code option. Otherwise, the server sends each |
| 1641 |
binding's data in a DHCPLEASEACTIVE or DHCPLEASEUNASSIGNED message. |
| 1642 |
|
| 1643 |
The response to a DHCPBULKLEASEQUERY may involve examination of |
| 1644 |
multiple DHCPv4 IP address bindings maintained by the DHCPv4 server. |
| 1645 |
The Bulk Leasequery protocol does not require any ordering of the IP |
| 1646 |
addresses returned in DHCPLEASEACTIVE or DHCPLEASEUNASSIGNED |
| 1647 |
messages. |
| 1648 |
|
| 1649 |
When responding to a DHCPBULKLEASEQUERY message, the DHCPv4 server |
| 1650 |
MUST NOT send more than one message for each applicable IP address, |
| 1651 |
even if the state of some of those IP addresses changes during the |
| 1652 |
processing of the message. Updates to such IP address state are |
| 1653 |
already handled by normal protocol processing, so no special effort |
| 1654 |
is needed here. |
| 1655 |
|
| 1656 |
If the ciaddr, yiaddr, or siaddr is non-zero in a DHCPBULKLEASEQUERY |
| 1657 |
request, the request must be terminated immediately by a |
| 1658 |
DHCPLEASEQUERYDONE message with a status-code option status of |
| 1659 |
MalformedQuery. |
| 1660 |
|
| 1661 |
Any DHCPBULKLEASEQUERY that has more than one of the following |
| 1662 |
primary query types specified MUST be terminated immediately by a |
| 1663 |
DHCPLEASEQUERYDONE message with a status-code option status code of |
| 1664 |
NotAllowed. |
| 1665 |
|
| 1666 |
The allowable queries in a DHCPBULKLEASEQUERY message are processed |
| 1667 |
as follows. Note that the descriptions of the primary queries below |
| 1668 |
must be constrained by the actions of any of the three qualifiers |
| 1669 |
described subsequently as well. |
| 1670 |
|
| 1671 |
|
| 1672 |
|
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
<span class="grey">Kinnear, et al. Standards Track [Page 30]</span></pre> |
| 1677 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1678 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
The following table discusses how to process the various queries. |
| 1682 |
For information on how to identify the query, see the information in |
| 1683 |
<a href="#section-7.2">Section 7.2</a>. |
| 1684 |
|
| 1685 |
o Query by MAC address |
| 1686 |
|
| 1687 |
Every IP address that has a current binding to a DHCPv4 client |
| 1688 |
matching the chaddr, htype, and hlen in the DHCPBULKLEASEQUERY |
| 1689 |
request MUST be returned in a DHCPLEASEACTIVE message. |
| 1690 |
|
| 1691 |
o Query by Client-identifier |
| 1692 |
|
| 1693 |
Every IP address that has a current binding to a DHCPv4 client |
| 1694 |
matching the Client-identifier option in the DHCPBULKLEASEQUERY |
| 1695 |
request MUST be returned in a DHCPLEASEACTIVE message. |
| 1696 |
|
| 1697 |
o Query by Remote ID |
| 1698 |
|
| 1699 |
Every IP address that has a current binding to a DHCPv4 client |
| 1700 |
matching the Remote ID sub-option of the relay-agent-information |
| 1701 |
option in the DHCPBULKLEASEQUERY request MUST be returned in a |
| 1702 |
DHCPLEASEACTIVE message. |
| 1703 |
|
| 1704 |
o Query by Relay-ID |
| 1705 |
|
| 1706 |
Every IP address that has a current binding to a DHCPv4 client |
| 1707 |
matching the Relay-ID sub-option of the relay-agent-information |
| 1708 |
option in the DHCPBULKLEASEQUERY request MUST be returned in a |
| 1709 |
DHCPLEASEACTIVE message. |
| 1710 |
|
| 1711 |
o Query for All Configured IP Addresses |
| 1712 |
|
| 1713 |
A Query for All Configured IP addresses is signaled by the absence |
| 1714 |
of any other primary query. That is, if there is no value in the |
| 1715 |
chaddr, hlen, htype, no Client-identifier option, and no Remote ID |
| 1716 |
sub-option or Relay-ID sub-option of the relay-agent-information |
| 1717 |
option, then the request is a query for information concerning all |
| 1718 |
configured IP addresses. In this case, every configured IP |
| 1719 |
address that has a current binding to a DHCPv4 client MUST be |
| 1720 |
returned in a DHCPLEASEACTIVE message. In addition, every |
| 1721 |
configured IP address that does not have a current binding to a |
| 1722 |
DHCPv4 client MUST be returned in a DHCPLEASEUNASSIGNED message. |
| 1723 |
|
| 1724 |
In this form of query, each configured IP address MUST be returned |
| 1725 |
at most one time. In the absence of qualifiers restricting the |
| 1726 |
number of IP addresses returned, every configured IP address MUST |
| 1727 |
be returned exactly once. |
| 1728 |
|
| 1729 |
|
| 1730 |
|
| 1731 |
|
| 1732 |
<span class="grey">Kinnear, et al. Standards Track [Page 31]</span></pre> |
| 1733 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1734 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 1735 |
|
| 1736 |
|
| 1737 |
There are three qualifiers that can be applied to any of the above |
| 1738 |
primary queries. These qualifiers can appear individually or |
| 1739 |
together in any combination, but only one of each can appear. |
| 1740 |
|
| 1741 |
o Query Start Time |
| 1742 |
|
| 1743 |
If a query-start-time option appears in the DHCPBULKLEASEQUERY |
| 1744 |
request, only IP address bindings that have changed on or after |
| 1745 |
the time specified in the query-start-time option should be |
| 1746 |
returned. |
| 1747 |
|
| 1748 |
o Query End Time |
| 1749 |
|
| 1750 |
If a query-end-time option appears in the DHCPBULKLEASEQUERY |
| 1751 |
request, only IP address bindings that have changed on or before |
| 1752 |
the time specified in the query-end-time option should be |
| 1753 |
returned. |
| 1754 |
|
| 1755 |
o VPN-ID |
| 1756 |
|
| 1757 |
If no VPN-ID option appears in the DHCPBULKLEASEQUERY, the default |
| 1758 |
(global) VPN is used to satisfy the query. A VPN-ID option |
| 1759 |
[<a href="./rfc6607" title=""Virtual Subnet Selection Options for DHCPv4 and DHCPv6"">RFC6607</a>] value other than the wildcard value (254) allows the |
| 1760 |
requestor to specify a single VPN other than the default VPN. In |
| 1761 |
addition, the VPN-ID option has been extended as part of this |
| 1762 |
document to allow specification of a type 254, which indicates |
| 1763 |
that all configured VPNs be searched in order to satisfy the |
| 1764 |
primary query. |
| 1765 |
|
| 1766 |
In all cases, if the information returned in a DHCPLEASEACTIVE or |
| 1767 |
DHCPLEASEUNASSIGNED message is for a VPN other than the default |
| 1768 |
(global) VPN, a VPN-ID option MUST appear in the packet. |
| 1769 |
|
| 1770 |
The query-start-time and query-end-time qualifiers are used to |
| 1771 |
constrain the amount of data returned by a Bulk Leasequery request by |
| 1772 |
returning only IP addresses whose address bindings have changed in |
| 1773 |
some way during the time window specified by the query-start-time and |
| 1774 |
query-end-time. |
| 1775 |
|
| 1776 |
A DHCPv4 server SHOULD consider an address binding to have changed |
| 1777 |
during a specified time window if either the client-last- |
| 1778 |
transaction-time or the start-time-of-state of the address binding |
| 1779 |
changed during that time window. |
| 1780 |
|
| 1781 |
The DHCPv4 server MAY return address binding data in any order, as |
| 1782 |
long as binding information for any given IP address is not repeated. |
| 1783 |
When all binding data for a given DHCPBULKLEASEQUERY has been sent, |
| 1784 |
the DHCPv4 server MUST send a DHCPBULKLEASEQUERYDONE message. |
| 1785 |
|
| 1786 |
|
| 1787 |
|
| 1788 |
<span class="grey">Kinnear, et al. Standards Track [Page 32]</span></pre> |
| 1789 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span> |
| 1790 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 1791 |
|
| 1792 |
|
| 1793 |
<span class="h3"><a class="selflink" id="section-8.3" href="#section-8.3">8.3</a>. Building a Single Reply for Bulk Leasequery</span> |
| 1794 |
|
| 1795 |
The DHCPv4 Leasequery specification [<a href="./rfc4388" title=""Dynamic Host Configuration Protocol (DHCP) Leasequery"">RFC4388</a>] describes the initial |
| 1796 |
construction of DHCPLEASEQUERY reply messages using the |
| 1797 |
DHCPLEASEACTIVE and DHCPLEASEUNASSIGNED message types in <a href="#section-6.4.2">Section</a> |
| 1798 |
<a href="#section-6.4.2">6.4.2</a>. All of the reply messages in Bulk Leasequery are similar to |
| 1799 |
the reply messages for an IP address query. Message transmission and |
| 1800 |
framing for TCP are described in this document in <a href="#section-6.1">Section 6.1</a>. |
| 1801 |
|
| 1802 |
[<a id="ref-RFC2131">RFC2131</a>] and [<a href="./rfc4388" title=""Dynamic Host Configuration Protocol (DHCP) Leasequery"">RFC4388</a>] specify that every response message MUST |
| 1803 |
contain the server-identifier option. However, that option will be |
| 1804 |
the same for every response from a particular DHCPBULKLEASEQUERY |
| 1805 |
request. Thus, the DHCPv4 server MUST include the server-identifier |
| 1806 |
option in the first message sent in response to a DHCPBULKLEASEQUERY. |
| 1807 |
It SHOULD NOT include the server-identifier option in later messages. |
| 1808 |
|
| 1809 |
The message type of DHCPLEASEACTIVE or DHCPLEASEUNASSIGNED is based |
| 1810 |
on the value of the dhcp-state option. If the dhcp-state option |
| 1811 |
value is ACTIVE, then the message type is DHCPLEASEACTIVE; otherwise, |
| 1812 |
the message type is DHCPLEASEUNASSIGNED. |
| 1813 |
|
| 1814 |
In addition to the basic message construction described in [<a href="./rfc4388" title=""Dynamic Host Configuration Protocol (DHCP) Leasequery"">RFC4388</a>], |
| 1815 |
the following guidelines exist: |
| 1816 |
|
| 1817 |
1. If the dhcp-state option code appears in the dhcp-parameter- |
| 1818 |
request-list, the DHCPv4 server SHOULD include a dhcp-state |
| 1819 |
option whose value corresponds most closely to the state held by |
| 1820 |
the DHCPv4 server for the IP address associated with this reply. |
| 1821 |
If the state is ACTIVE and the message being returned is |
| 1822 |
DHCPLEASEACTIVE, then the DHCPv4 server MAY choose to not send |
| 1823 |
the dhcp-state option. The requestor SHOULD assume that any |
| 1824 |
DHCPLEASEACTIVE message arriving without a requested dhcp-state |
| 1825 |
option has a dhcp-state of ACTIVE. |
| 1826 |
|
| 1827 |
2. If the base-time option code appears in the dhcp-parameter- |
| 1828 |
request-list, the DHCPv4 server MUST include a base-time option, |
| 1829 |
which is the current time in the DHCPv4 server's context and the |
| 1830 |
time from which the start-time-of-state, dhcp-lease-time, client- |
| 1831 |
last-transaction-time, and other duration-style times are based |
| 1832 |
upon. |
| 1833 |
|
| 1834 |
3. If the start-time-of-state option code appears in the dhcp- |
| 1835 |
parameter-request-list, the DHCPv4 server MUST include a start- |
| 1836 |
time-of-state option whose value represents the time at which the |
| 1837 |
dhcp-state option's state became valid. |
| 1838 |
|
| 1839 |
|
| 1840 |
|
| 1841 |
|
| 1842 |
|
| 1843 |
|
| 1844 |
<span class="grey">Kinnear, et al. Standards Track [Page 33]</span></pre> |
| 1845 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span> |
| 1846 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 1847 |
|
| 1848 |
|
| 1849 |
4. If the dhcp-lease-time option code appears in the dhcp- |
| 1850 |
parameter-request-list, the DHCPv4 server MUST include a dhcp- |
| 1851 |
lease-time option for any state that has a timeout value |
| 1852 |
associated with it. |
| 1853 |
|
| 1854 |
5. If the data-source option code appears in the dhcp-parameter- |
| 1855 |
request-list, the DHCPv4 server MUST include the data-source |
| 1856 |
option in any situation where any of the bits would be non-zero. |
| 1857 |
Thus, in the absence of the data-source option, the assumption is |
| 1858 |
that all of the flags are zero. |
| 1859 |
|
| 1860 |
6. If the client-last-transaction-time option code appears in the |
| 1861 |
dhcp-parameter-request-list, the DHCPv4 server MUST include the |
| 1862 |
client-last-transaction-time option in any situation where the |
| 1863 |
information is available. |
| 1864 |
|
| 1865 |
7. If there is a dhcp-parameter-request-list in the initial |
| 1866 |
DHCPBULKLEASEQUERY request, then it should be used for all of the |
| 1867 |
replies generated by that request. Some options can be sent from |
| 1868 |
a DHCPv4 client to the server or from the DHCPv4 server to a |
| 1869 |
DHCPv4 client. Option 125 is such an option. If the option code |
| 1870 |
for one of these options appears in the dhcp-parameter-request- |
| 1871 |
list, it SHOULD result in returning the value of the option sent |
| 1872 |
by the DHCPv4 client to the server if one exists. |
| 1873 |
|
| 1874 |
Note that there may be other requirements for a reply to a |
| 1875 |
DHCPBULKLEASEQUERY request, as discussed in <a href="#section-8.2">Section 8.2</a>. |
| 1876 |
|
| 1877 |
<span class="h3"><a class="selflink" id="section-8.4" href="#section-8.4">8.4</a>. Multiple or Parallel Queries</span> |
| 1878 |
|
| 1879 |
As discussed in <a href="#section-7.3">Section 7.3</a>, requestors may want to use a connection |
| 1880 |
that has already been established when they need to make additional |
| 1881 |
queries. Servers SHOULD support reading and processing multiple |
| 1882 |
queries from a single connection and SHOULD allow configuration of |
| 1883 |
the number of simultaneous queries it may process. A server MUST NOT |
| 1884 |
read more query messages from a connection than it is prepared to |
| 1885 |
process simultaneously. |
| 1886 |
|
| 1887 |
This SHOULD be a feature that is administratively controlled. |
| 1888 |
Servers SHOULD offer configuration that limits the number of |
| 1889 |
simultaneous queries permitted from any one requestor, in order to |
| 1890 |
control resource use if there are multiple requestors seeking |
| 1891 |
service. |
| 1892 |
|
| 1893 |
|
| 1894 |
|
| 1895 |
|
| 1896 |
|
| 1897 |
|
| 1898 |
|
| 1899 |
|
| 1900 |
<span class="grey">Kinnear, et al. Standards Track [Page 34]</span></pre> |
| 1901 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span> |
| 1902 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 1903 |
|
| 1904 |
|
| 1905 |
<span class="h3"><a class="selflink" id="section-8.5" href="#section-8.5">8.5</a>. Closing Connections</span> |
| 1906 |
|
| 1907 |
The DHCPv4 server SHOULD close connections in a graceful manner and |
| 1908 |
not abort the connection. The DHCPv4 server SHOULD NOT assume that |
| 1909 |
the manner in which the requestor closed a connection carries any |
| 1910 |
special meaning. |
| 1911 |
|
| 1912 |
Typically, the DHCPv4 server will only close the connection after |
| 1913 |
some form of an exception or a timeout on the connection. |
| 1914 |
|
| 1915 |
Using a timer to detect when a connection is idle and then closing |
| 1916 |
that connection is designed to protect the DHCPv4 server from |
| 1917 |
consuming unnecessary resources. |
| 1918 |
|
| 1919 |
The DHCPv4 server should start a timer for BULK_LQ_DATA_TIMEOUT |
| 1920 |
seconds for a particular connection after it sends a |
| 1921 |
DHCPLEASEQUERYDONE message over that connection if there is no |
| 1922 |
current query outstanding for that connection. It should restart |
| 1923 |
this timer if a query arrives over that connection. If the timer |
| 1924 |
expires, the DHCPv4 server should close the connection. |
| 1925 |
|
| 1926 |
The server MUST close its end of the TCP connection if it encounters |
| 1927 |
an error sending data on the connection. The server MUST close its |
| 1928 |
end of the TCP connection if it finds that it has to abort an in- |
| 1929 |
process request. A server aborting an in-process request SHOULD |
| 1930 |
attempt to signal that to its requestors by using the QueryTerminated |
| 1931 |
status code in the status-code option in a DHCPLEASEQUERYDONE |
| 1932 |
message, including a message string indicating details of the reason |
| 1933 |
for the abort. If the connection is closed for any reason, all of |
| 1934 |
the data flows associated with any currently outstanding |
| 1935 |
DHCPBULKLEASEQUERY messages will be terminated. |
| 1936 |
|
| 1937 |
If the server detects that the requesting end of the connection has |
| 1938 |
been closed, the server MUST close its end of the connection. |
| 1939 |
|
| 1940 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span> |
| 1941 |
|
| 1942 |
The Security Considerations section of [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>] details the general |
| 1943 |
threats to DHCPv4. The DHCPv4 Leasequery specification [<a href="./rfc4388" title=""Dynamic Host Configuration Protocol (DHCP) Leasequery"">RFC4388</a>] |
| 1944 |
describes recommendations for the Leasequery protocol, especially |
| 1945 |
with regard to authentication of LEASEQUERY messages, mitigation of |
| 1946 |
packet-flooding DoS attacks, and restriction to trusted requestors. |
| 1947 |
|
| 1948 |
The use of TCP introduces some additional concerns. Attacks that |
| 1949 |
attempt to exhaust the DHCPv4 server's available TCP connection |
| 1950 |
resources, such as SYN flooding attacks, can compromise the ability |
| 1951 |
of legitimate requestors to receive service. Malicious requestors |
| 1952 |
who succeed in establishing connections but who then send invalid |
| 1953 |
|
| 1954 |
|
| 1955 |
|
| 1956 |
<span class="grey">Kinnear, et al. Standards Track [Page 35]</span></pre> |
| 1957 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span> |
| 1958 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 1959 |
|
| 1960 |
|
| 1961 |
queries, partial queries, or no queries at all can also exhaust a |
| 1962 |
server's pool of available connections. We recommend that servers |
| 1963 |
offer configuration to limit the sources of incoming connections, |
| 1964 |
that they limit the number of accepted connections and the number of |
| 1965 |
in-process queries from any one connection, and that they limit the |
| 1966 |
period of time during which an idle connection will be left open. |
| 1967 |
|
| 1968 |
There are two specific issues regarding Bulk Leasequery security that |
| 1969 |
deserve explicit mention. The first is preventing information that |
| 1970 |
Bulk Leasequery can provide from reaching clients who are not |
| 1971 |
authorized to receive such information. The second is ensuring that |
| 1972 |
authorized clients of the Bulk Leasequery capability receive accurate |
| 1973 |
information from the server (and that this information is not |
| 1974 |
disrupted in transit). |
| 1975 |
|
| 1976 |
To prevent information leakage to unauthorized clients, servers |
| 1977 |
SHOULD restrict Bulk Leasequery connections and DHCPBULKLEASEQUERY |
| 1978 |
messages to certain requestors, either through explicit configuration |
| 1979 |
of the server itself or by employing external network elements to |
| 1980 |
provide such restrictions. In particular, the typical DHCPv4 client |
| 1981 |
SHOULD NOT be allowed to receive a response to a Bulk Leasequery |
| 1982 |
request, and some technique MUST exist to allow prevention of such |
| 1983 |
access in any environment where Bulk Leasequery is deployed. |
| 1984 |
|
| 1985 |
Connections not from permitted requestors SHOULD be closed |
| 1986 |
immediately to avoid server connection resource exhaustion or |
| 1987 |
alternatively, simply not be allowed to reach the server at all. |
| 1988 |
Servers SHOULD have the capability to restrict certain requestors to |
| 1989 |
certain query types. Servers MAY reply to queries that are not |
| 1990 |
permitted with the DHCPLEASEQUERYDONE message with a status-code |
| 1991 |
option status of NotAllowed or MAY simply close the connection. |
| 1992 |
|
| 1993 |
To prevent disruption and malicious corruption of Bulk Leasequery |
| 1994 |
data flows between the server and authorized clients, these data |
| 1995 |
flows SHOULD transit only secured networks. These data flows are |
| 1996 |
typically infrastructure oriented, and there is usually no reason to |
| 1997 |
have them flowing over networks where such attacks are likely. In |
| 1998 |
the rare cases where these data flows might need to be sent through |
| 1999 |
unsecured networks, they MUST be sent over connections secured |
| 2000 |
through means external to the DHCPv4/DHCPv6 server and its client(s) |
| 2001 |
(e.g., through VPNs). |
| 2002 |
|
| 2003 |
Authentication for DHCP messages [<a href="./rfc3118" title=""Authentication for DHCP Messages"">RFC3118</a>] MUST NOT be used to |
| 2004 |
attempt to secure transmission of the messages described in this |
| 2005 |
document. In particular, the message framing would not be protected |
| 2006 |
by using the mechanisms described in [<a href="./rfc3118" title=""Authentication for DHCP Messages"">RFC3118</a>] (which was designed |
| 2007 |
only with UDP transport in mind). |
| 2008 |
|
| 2009 |
|
| 2010 |
|
| 2011 |
|
| 2012 |
<span class="grey">Kinnear, et al. Standards Track [Page 36]</span></pre> |
| 2013 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span> |
| 2014 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 2015 |
|
| 2016 |
|
| 2017 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. IANA Considerations</span> |
| 2018 |
|
| 2019 |
IANA has assigned the following new DHCPv4 option codes from the |
| 2020 |
registry "BOOTP Vendor Extensions and DHCP Options" maintained at |
| 2021 |
<a href="http://www.iana.org/assignments/bootp-dhcp-parameters">http://www.iana.org/assignments/bootp-dhcp-parameters</a>. |
| 2022 |
|
| 2023 |
1. An option code of 151 for status-code. |
| 2024 |
|
| 2025 |
2. An option code of 152 for base-time. |
| 2026 |
|
| 2027 |
3. An option code of 153 for start-time-of-state. |
| 2028 |
|
| 2029 |
4. An option code of 154 for query-start-time. |
| 2030 |
|
| 2031 |
5. An option code of 155 for query-end-time. |
| 2032 |
|
| 2033 |
6. An option code of 156 for dhcp-state. |
| 2034 |
|
| 2035 |
7. An option code of 157 for data-source. |
| 2036 |
|
| 2037 |
IANA has assigned the following new DHCP message types from the |
| 2038 |
registry "DHCP Message Type 53 Values" maintained at |
| 2039 |
<a href="http://www.iana.org/assignments/bootp-dhcp-parameters">http://www.iana.org/assignments/bootp-dhcp-parameters</a>. |
| 2040 |
|
| 2041 |
1. A dhcp-message-type of 14 for DHCPBULKLEASEQUERY. |
| 2042 |
|
| 2043 |
2. A dhcp-message-type of 15 for DHCPLEASEQUERYDONE. |
| 2044 |
|
| 2045 |
IANA has created a new registry on the same assignments page, titled |
| 2046 |
"DHCP State 156 Values" (where 156 corresponds to the assigned value |
| 2047 |
of the dhcp-state option above). This registry has the following |
| 2048 |
initial values: |
| 2049 |
|
| 2050 |
State |
| 2051 |
----- |
| 2052 |
1 AVAILABLE |
| 2053 |
2 ACTIVE |
| 2054 |
3 EXPIRED |
| 2055 |
4 RELEASED |
| 2056 |
5 ABANDONED |
| 2057 |
6 RESET |
| 2058 |
7 REMOTE |
| 2059 |
8 TRANSITIONING |
| 2060 |
|
| 2061 |
New values for this namespace may only be defined by IETF Review, as |
| 2062 |
described in [<a href="./rfc5226" title="">RFC5226</a>]. |
| 2063 |
|
| 2064 |
|
| 2065 |
|
| 2066 |
|
| 2067 |
|
| 2068 |
<span class="grey">Kinnear, et al. Standards Track [Page 37]</span></pre> |
| 2069 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span> |
| 2070 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 2071 |
|
| 2072 |
|
| 2073 |
IANA has created a new registry on the same assignments page, titled |
| 2074 |
"DHCP Status Code 151 Values" (where 151 corresponds to the assigned |
| 2075 |
value of the status-code option above). This registry has the |
| 2076 |
following initial values: |
| 2077 |
|
| 2078 |
Name status-code |
| 2079 |
---- ----------- |
| 2080 |
Success 000 |
| 2081 |
UnspecFail 001 |
| 2082 |
QueryTerminated 002 |
| 2083 |
MalformedQuery 003 |
| 2084 |
NotAllowed 004 |
| 2085 |
|
| 2086 |
New values for this namespace may only be defined by IETF Review, as |
| 2087 |
described in [<a href="./rfc5226" title="">RFC5226</a>]. |
| 2088 |
|
| 2089 |
IANA has revised the registry "VSS Type Options" created by [<a href="./rfc6607" title=""Virtual Subnet Selection Options for DHCPv4 and DHCPv6"">RFC6607</a>] |
| 2090 |
in the overall area "Dynamic Host Configuration Protocol (DHCP) and |
| 2091 |
Bootstrap Protocol (BOOTP) Parameters". It has been revised to |
| 2092 |
appear as follows. Note that the number range for "Unassigned" has |
| 2093 |
changed, and a new line for "All VPNs (wildcard)" was added. |
| 2094 |
|
| 2095 |
Type VSS Information Format |
| 2096 |
------------------------------------------------------------ |
| 2097 |
0 Network Virtual Terminal (NVT) ASCII VPN identifier |
| 2098 |
1 <a href="./rfc2685">RFC 2685</a> VPN-ID |
| 2099 |
2-253 Unassigned |
| 2100 |
254 All VPNs (wildcard) |
| 2101 |
255 Global, default VPN |
| 2102 |
|
| 2103 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Acknowledgements</span> |
| 2104 |
|
| 2105 |
Significant text as well as important ideas were borrowed in whole or |
| 2106 |
in part from "DHCPv6 Bulk Leasequery" [<a href="./rfc5460" title=""DHCPv6 Bulk Leasequery"">RFC5460</a>], written by Mark |
| 2107 |
Stapp. Further suggestions and improvements were made by |
| 2108 |
participants in the DHC Working Group, including Alfred Hoenes. |
| 2109 |
|
| 2110 |
<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. References</span> |
| 2111 |
|
| 2112 |
<span class="h3"><a class="selflink" id="section-12.1" href="#section-12.1">12.1</a>. Normative References</span> |
| 2113 |
|
| 2114 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 2115 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 2116 |
|
| 2117 |
[<a id="ref-RFC2131">RFC2131</a>] Droms, R., "Dynamic Host Configuration Protocol", <a href="./rfc2131">RFC</a> |
| 2118 |
<a href="./rfc2131">2131</a>, March 1997. |
| 2119 |
|
| 2120 |
|
| 2121 |
|
| 2122 |
|
| 2123 |
|
| 2124 |
<span class="grey">Kinnear, et al. Standards Track [Page 38]</span></pre> |
| 2125 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span> |
| 2126 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 2127 |
|
| 2128 |
|
| 2129 |
[<a id="ref-RFC2132">RFC2132</a>] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor |
| 2130 |
Extensions", <a href="./rfc2132">RFC 2132</a>, March 1997. |
| 2131 |
|
| 2132 |
[<a id="ref-RFC3046">RFC3046</a>] Patrick, M., "DHCP Relay Agent Information Option", <a href="./rfc3046">RFC</a> |
| 2133 |
<a href="./rfc3046">3046</a>, January 2001. |
| 2134 |
|
| 2135 |
[<a id="ref-RFC3118">RFC3118</a>] Droms, R., Ed., and W. Arbaugh, Ed., "Authentication for |
| 2136 |
DHCP Messages", <a href="./rfc3118">RFC 3118</a>, June 2001. |
| 2137 |
|
| 2138 |
[<a id="ref-RFC4388">RFC4388</a>] Woundy, R. and K. Kinnear, "Dynamic Host Configuration |
| 2139 |
Protocol (DHCP) Leasequery", <a href="./rfc4388">RFC 4388</a>, February 2006. |
| 2140 |
|
| 2141 |
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an |
| 2142 |
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>, |
| 2143 |
May 2008. |
| 2144 |
|
| 2145 |
[<a id="ref-RFC5735">RFC5735</a>] Cotton, M. and L. Vegoda, "Special Use IPv4 Addresses", |
| 2146 |
<a href="https://www.rfc-editor.org/bcp/bcp153">BCP 153</a>, <a href="./rfc5735">RFC 5735</a>, January 2010. |
| 2147 |
|
| 2148 |
[<a id="ref-RFC6607">RFC6607</a>] Kinnear, K., Johnson, R., and M. Stapp, "Virtual Subnet |
| 2149 |
Selection Options for DHCPv4 and DHCPv6", <a href="./rfc6607">RFC 6607</a>, April |
| 2150 |
2012. |
| 2151 |
|
| 2152 |
[<a id="ref-RFC6925">RFC6925</a>] Joshi, B., Desetti, R., and M. Stapp, "The DHCPv4 Relay |
| 2153 |
Agent Identifier Sub-Option", <a href="./rfc6925">RFC 6925</a>, April 2013. |
| 2154 |
|
| 2155 |
<span class="h3"><a class="selflink" id="section-12.2" href="#section-12.2">12.2</a>. Informative References</span> |
| 2156 |
|
| 2157 |
[<a id="ref-RFC951">RFC951</a>] Croft, W. and J. Gilmore, "Bootstrap Protocol", <a href="./rfc951">RFC 951</a>, |
| 2158 |
September 1985. |
| 2159 |
|
| 2160 |
[<a id="ref-RFC1542">RFC1542</a>] Wimer, W., "Clarifications and Extensions for the |
| 2161 |
Bootstrap Protocol", <a href="./rfc1542">RFC 1542</a>, October 1993. |
| 2162 |
|
| 2163 |
[<a id="ref-RFC4614">RFC4614</a>] Duke, M., Braden, R., Eddy, W., and E. Blanton, "A Roadmap |
| 2164 |
for Transmission Control Protocol (TCP) Specification |
| 2165 |
Documents", <a href="./rfc4614">RFC 4614</a>, September 2006. |
| 2166 |
|
| 2167 |
[<a id="ref-RFC5460">RFC5460</a>] Stapp, M., "DHCPv6 Bulk Leasequery", <a href="./rfc5460">RFC 5460</a>, February |
| 2168 |
2009. |
| 2169 |
|
| 2170 |
|
| 2171 |
|
| 2172 |
|
| 2173 |
|
| 2174 |
|
| 2175 |
|
| 2176 |
|
| 2177 |
|
| 2178 |
|
| 2179 |
|
| 2180 |
<span class="grey">Kinnear, et al. Standards Track [Page 39]</span></pre> |
| 2181 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span> |
| 2182 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 2183 |
|
| 2184 |
|
| 2185 |
Authors' Addresses |
| 2186 |
|
| 2187 |
Kim Kinnear |
| 2188 |
Cisco Systems, Inc. |
| 2189 |
1414 Massachusetts Ave. |
| 2190 |
Boxborough, Massachusetts 01719 |
| 2191 |
USA |
| 2192 |
|
| 2193 |
Phone: (978) 936-0000 |
| 2194 |
EMail: [email protected] |
| 2195 |
|
| 2196 |
|
| 2197 |
Mark Stapp |
| 2198 |
Cisco Systems, Inc. |
| 2199 |
1414 Massachusetts Ave. |
| 2200 |
Boxborough, Massachusetts 01719 |
| 2201 |
USA |
| 2202 |
|
| 2203 |
Phone: (978) 936-0000 |
| 2204 |
EMail: [email protected] |
| 2205 |
|
| 2206 |
|
| 2207 |
D.T.V Ramakrishna Rao |
| 2208 |
Infosys Ltd. |
| 2209 |
44 Electronics City, Hosur Road |
| 2210 |
Bangalore 560 100 |
| 2211 |
India |
| 2212 |
|
| 2213 |
EMail: [email protected] |
| 2214 |
URI: <a href="http://www.infosys.com/">http://www.infosys.com/</a> |
| 2215 |
|
| 2216 |
|
| 2217 |
Bharat Joshi |
| 2218 |
Infosys Ltd. |
| 2219 |
44 Electronics City, Hosur Road |
| 2220 |
Bangalore 560 100 |
| 2221 |
India |
| 2222 |
|
| 2223 |
EMail: [email protected] |
| 2224 |
URI: <a href="http://www.infosys.com/">http://www.infosys.com/</a> |
| 2225 |
|
| 2226 |
|
| 2227 |
Neil Russell |
| 2228 |
Sea Street Technologies Inc. |
| 2229 |
|
| 2230 |
EMail: [email protected] |
| 2231 |
|
| 2232 |
|
| 2233 |
|
| 2234 |
|
| 2235 |
|
| 2236 |
<span class="grey">Kinnear, et al. Standards Track [Page 40]</span></pre> |
| 2237 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span> |
| 2238 |
<span class="grey"><a href="./rfc6926">RFC 6926</a> DHCPv4 Bulk Leasequery April 2013</span> |
| 2239 |
|
| 2240 |
|
| 2241 |
Pavan Kurapati |
| 2242 |
Juniper Networks |
| 2243 |
1194 N. Mathilda Ave. |
| 2244 |
Sunnyvale, CA 94089 |
| 2245 |
USA |
| 2246 |
|
| 2247 |
EMail: [email protected] |
| 2248 |
URI: <a href="http://www.juniper.net/">http://www.juniper.net/</a> |
| 2249 |
|
| 2250 |
|
| 2251 |
Bernie Volz |
| 2252 |
Cisco Systems, Inc. |
| 2253 |
1414 Massachusetts Ave. |
| 2254 |
Boxborough, Massachusetts 01719 |
| 2255 |
USA |
| 2256 |
|
| 2257 |
Phone: (978) 936-0000 |
| 2258 |
EMail: [email protected] |
| 2259 |
|
| 2260 |
|
| 2261 |
|
| 2262 |
|
| 2263 |
|
| 2264 |
|
| 2265 |
|
| 2266 |
|
| 2267 |
|
| 2268 |
|
| 2269 |
|
| 2270 |
|
| 2271 |
|
| 2272 |
|
| 2273 |
|
| 2274 |
|
| 2275 |
|
| 2276 |
|
| 2277 |
|
| 2278 |
|
| 2279 |
|
| 2280 |
|
| 2281 |
|
| 2282 |
|
| 2283 |
|
| 2284 |
|
| 2285 |
|
| 2286 |
|
| 2287 |
|
| 2288 |
|
| 2289 |
|
| 2290 |
|
| 2291 |
|
| 2292 |
Kinnear, et al. Standards Track [Page 41] |
| 2293 |
</pre> |