| 1 |
<pre>Network Working Group S. Park |
| 2 |
Request for Comments: 4039 P. Kim |
| 3 |
Category: Standards Track SAMSUNG Electronics |
| 4 |
B. Volz |
| 5 |
Cisco Systems |
| 6 |
March 2005 |
| 7 |
|
| 8 |
|
| 9 |
<span class="h1">Rapid Commit Option for the</span> |
| 10 |
<span class="h1">Dynamic Host Configuration Protocol version 4 (DHCPv4)</span> |
| 11 |
|
| 12 |
Status of This Memo |
| 13 |
|
| 14 |
This document specifies an Internet standards track protocol for the |
| 15 |
Internet community, and requests discussion and suggestions for |
| 16 |
improvements. Please refer to the current edition of the "Internet |
| 17 |
Official Protocol Standards" (STD 1) for the standardization state |
| 18 |
and status of this protocol. Distribution of this memo is unlimited. |
| 19 |
|
| 20 |
Copyright Notice |
| 21 |
|
| 22 |
Copyright (C) The Internet Society (2005). |
| 23 |
|
| 24 |
Abstract |
| 25 |
|
| 26 |
This document defines a new Dynamic Host Configuration Protocol |
| 27 |
version 4 (DHCPv4) option, modeled on the DHCPv6 Rapid Commit option, |
| 28 |
for obtaining IP address and configuration information using a |
| 29 |
2-message exchange rather than the usual 4-message exchange, |
| 30 |
expediting client configuration. |
| 31 |
|
| 32 |
Table of Contents |
| 33 |
|
| 34 |
<a href="#section-1">1</a>. Introduction................................................... <a href="#page-2">2</a> |
| 35 |
<a href="#section-2">2</a>. Requirements................................................... <a href="#page-2">2</a> |
| 36 |
<a href="#section-3">3</a>. Client/Server Operations....................................... <a href="#page-2">2</a> |
| 37 |
<a href="#section-3.1">3.1</a>. Detailed Flow............................................ <a href="#page-3">3</a> |
| 38 |
<a href="#section-3.2">3.2</a>. Administrative Considerations............................ <a href="#page-6">6</a> |
| 39 |
<a href="#section-4">4</a>. Rapid Commit Option Format..................................... <a href="#page-7">7</a> |
| 40 |
<a href="#section-5">5</a>. IANA Considerations............................................ <a href="#page-7">7</a> |
| 41 |
<a href="#section-6">6</a>. Security Considerations........................................ <a href="#page-7">7</a> |
| 42 |
<a href="#section-7">7</a>. References..................................................... <a href="#page-7">7</a> |
| 43 |
<a href="#section-7.1">7.1</a>. Normative References..................................... <a href="#page-7">7</a> |
| 44 |
<a href="#section-7.2">7.2</a>. Informative References................................... <a href="#page-8">8</a> |
| 45 |
<a href="#section-8">8</a>. Acknowledgements............................................... <a href="#page-8">8</a> |
| 46 |
Authors' Addresses................................................ <a href="#page-9">9</a> |
| 47 |
Full Copyright Statement.......................................... <a href="#page-10">10</a> |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Park, 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="./rfc4039">RFC 4039</a> Rapid Commit Option for DHCPv4 March 2005</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 58 |
|
| 59 |
In some environments, such as those in which high mobility occurs and |
| 60 |
the network attachment point changes frequently, it is beneficial to |
| 61 |
rapidly configure clients. And, in these environments it is possible |
| 62 |
to more quickly configure clients because the protections offered by |
| 63 |
the normal (and longer) 4-message exchange may not be needed. The |
| 64 |
4-message exchange allows for redundancy (multiple DHCP servers) |
| 65 |
without wasting addresses, as addresses are only provisionally |
| 66 |
assigned to a client until the client chooses and requests one of the |
| 67 |
provisionally assigned addresses. The 2-message exchange may |
| 68 |
therefore be used when only one server is present or when addresses |
| 69 |
are plentiful and having multiple servers commit addresses for a |
| 70 |
client is not a problem. |
| 71 |
|
| 72 |
This document defines a new Rapid Commit option for DHCPv4, modeled |
| 73 |
on the DHCPv6 Rapid Commit option [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>], which can be used to |
| 74 |
initiate a 2-message exchange to expedite client configuration in |
| 75 |
some environments. A client advertises its support of this option by |
| 76 |
sending it in DHCPDISCOVER messages. A server then determines |
| 77 |
whether to allow the 2-message exchange based on its configuration |
| 78 |
information and can either handle the DHCPDISCOVER as defined in |
| 79 |
[<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>] or commit the client's configuration information and |
| 80 |
advance to sending a DHCPACK message with the Rapid Commit option as |
| 81 |
defined herein. |
| 82 |
|
| 83 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements</span> |
| 84 |
|
| 85 |
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, |
| 86 |
SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this |
| 87 |
document, are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 88 |
|
| 89 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Client/Server Operations</span> |
| 90 |
|
| 91 |
If a client that supports the Rapid Commit option intends to use the |
| 92 |
rapid commit capability, it includes a Rapid Commit option in |
| 93 |
DHCPDISCOVER messages that it sends. The client MUST NOT include it |
| 94 |
in any other messages. A client and server only use this option when |
| 95 |
configured to do so. |
| 96 |
|
| 97 |
A client that sent a DHCPDISCOVER with Rapid Commit option processes |
| 98 |
responses as described in [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>]. However, if the client receives |
| 99 |
a DHCPACK message with a Rapid Commit option, it SHOULD process the |
| 100 |
DHCPACK immediately (without waiting for additional DHCPOFFER or |
| 101 |
DHCPACK messages) and use the address and configuration information |
| 102 |
contained therein. |
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Park, 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="./rfc4039">RFC 4039</a> Rapid Commit Option for DHCPv4 March 2005</span> |
| 111 |
|
| 112 |
|
| 113 |
A server that supports the Rapid Commit option MAY respond to a |
| 114 |
DHCPDISCOVER message that included the Rapid Commit option with a |
| 115 |
DHCPACK that includes the Rapid Commit option and fully committed |
| 116 |
address and configuration information. A server MUST NOT include the |
| 117 |
Rapid Commit option in any other messages. |
| 118 |
|
| 119 |
The Rapid Commit option MUST NOT appear in a Parameter Request List |
| 120 |
option [<a href="./rfc2132" title=""DHCP Options and BOOTP Vendor Extensions"">RFC2132</a>]. |
| 121 |
|
| 122 |
All other DHCP operations are as documented in [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>]. |
| 123 |
|
| 124 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Detailed Flow</span> |
| 125 |
|
| 126 |
The following is revised from <a href="./rfc2131#section-3.1">Section 3.1 of [RFC2131]</a>, which |
| 127 |
includes handling of the Rapid Commit option. |
| 128 |
|
| 129 |
1. The client broadcasts a DHCPDISCOVER message on its local |
| 130 |
physical subnet. If the client supports the Rapid Commit |
| 131 |
option and intends to use the rapid commit capability, it |
| 132 |
includes a Rapid Commit option in the DHCPDISCOVER message. |
| 133 |
The DHCPDISCOVER message MAY include options that suggest |
| 134 |
values for the network address and lease duration. BOOTP relay |
| 135 |
agents may pass the message on to DHCP servers not on the same |
| 136 |
physical subnet. |
| 137 |
|
| 138 |
2. Each server may respond with either a DHCPOFFER message or a |
| 139 |
DHCPACK message with the Rapid Commit option (the latter only |
| 140 |
if the DHCPDISCOVER contained a Rapid Commit option and the |
| 141 |
server's configuration policies allow use of Rapid Commit). |
| 142 |
These would include an available network address in the |
| 143 |
'yiaddr' field (and other configuration parameters in DHCP |
| 144 |
options). Servers sending a DHCPOFFER need not reserve the |
| 145 |
offered network address, although the protocol will work more |
| 146 |
efficiently if the server avoids allocating the offered network |
| 147 |
address to another client. Servers sending the DHCPACK message |
| 148 |
commit the binding for the client to persistent storage before |
| 149 |
sending the DHCPACK. The combination of 'client identifier' or |
| 150 |
'chaddr' and assigned network address constitute a unique |
| 151 |
identifier for the client's lease and are used by both the |
| 152 |
client and server to identify a lease referred to in any DHCP |
| 153 |
messages. The server transmits the DHCPOFFER or DHCPACK |
| 154 |
message to the client, if necessary by using the BOOTP relay |
| 155 |
agent. |
| 156 |
|
| 157 |
When allocating a new address, servers SHOULD check that the |
| 158 |
offered network address is not already in use; e.g., the server |
| 159 |
may probe the offered address with an ICMP Echo Request. |
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Park, 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="./rfc4039">RFC 4039</a> Rapid Commit Option for DHCPv4 March 2005</span> |
| 167 |
|
| 168 |
|
| 169 |
Servers SHOULD be implemented so that network administrators |
| 170 |
MAY choose to disable probes of newly allocated addresses. |
| 171 |
|
| 172 |
Figure 3 in [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>] shows the flow for the normal 4-message |
| 173 |
exchange. Figure 1 below shows the 2-message exchange. |
| 174 |
|
| 175 |
Server Client Server |
| 176 |
(not selected) (selected) |
| 177 |
|
| 178 |
v v v |
| 179 |
| | | |
| 180 |
| Begins initialization | |
| 181 |
| | | |
| 182 |
| _____________/|\____________ | |
| 183 |
|/DHCPDISCOVER | DHCPDISCOVER \| |
| 184 |
| w/Rapid Commit| w/Rapid Commit| |
| 185 |
| | | |
| 186 |
Determines | Determines |
| 187 |
configuration | configuration |
| 188 |
| | Commits configuration |
| 189 |
| Collects replies | |
| 190 |
|\ | ____________/| |
| 191 |
| \________ | / DHCPACK | |
| 192 |
| DHCPOFFER\ |/w/Rapid Commit| |
| 193 |
| (discarded) | | |
| 194 |
| Initialization complete | |
| 195 |
| | | |
| 196 |
. . . |
| 197 |
. . . |
| 198 |
| | | |
| 199 |
| Graceful shutdown | |
| 200 |
| | | |
| 201 |
| |\_____________ | |
| 202 |
| | DHCPRELEASE \| |
| 203 |
| | | |
| 204 |
| | Discards lease |
| 205 |
| | | |
| 206 |
v v v |
| 207 |
|
| 208 |
Figure 1 Timeline diagram when Rapid Commit is used |
| 209 |
|
| 210 |
3. The client receives one or more DHCPOFFER or DHCPACK (if the |
| 211 |
Rapid Commit option is sent in DHCPDISCOVER) messages from one |
| 212 |
or more servers. If a DHCPACK (with the Rapid Commit option) |
| 213 |
is received, the client may immediately advance to step 5 below |
| 214 |
if the offered configuration parameters are acceptable. The |
| 215 |
client may choose to wait for multiple responses. The client |
| 216 |
chooses one server from which to request or accept |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Park, 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="./rfc4039">RFC 4039</a> Rapid Commit Option for DHCPv4 March 2005</span> |
| 223 |
|
| 224 |
|
| 225 |
configuration parameters, based on the configuration parameters |
| 226 |
offered in the DHCPOFFER and DHCPACK messages. If the client |
| 227 |
chooses a DHCPACK, it advances to step 5. Otherwise, the |
| 228 |
client broadcasts a DHCPREQUEST message that MUST include the |
| 229 |
'server identifier' option to indicate which server it has |
| 230 |
selected, the message MAY include other options specifying |
| 231 |
desired configuration values. The 'requested IP address' |
| 232 |
option MUST be set to the value of 'yiaddr' in the DHCPOFFER |
| 233 |
message from the server. This DHCPREQUEST message is broadcast |
| 234 |
and relayed through DHCP/BOOTP relay agents. To help ensure |
| 235 |
that any BOOTP relay agents forward the DHCPREQUEST message to |
| 236 |
the same set of DHCP servers that received the original |
| 237 |
DHCPDISCOVER message, the DHCPREQUEST message MUST use the same |
| 238 |
value in the DHCP message header's 'secs' field and be sent to |
| 239 |
the same IP broadcast address as was the original DHCPDISCOVER |
| 240 |
message. The client times out and retransmits the DHCPDISCOVER |
| 241 |
message if the client receives no DHCPOFFER messages. |
| 242 |
|
| 243 |
4. The servers receive the DHCPREQUEST broadcast from the client. |
| 244 |
Servers not selected by the DHCPREQUEST message use the message |
| 245 |
as notification that the client has declined those servers' |
| 246 |
offers. The server selected in the DHCPREQUEST message commits |
| 247 |
the binding for the client to persistent storage and responds |
| 248 |
with a DHCPACK message containing the configuration parameters |
| 249 |
for the requesting client. The combination of 'client |
| 250 |
identifier' or 'chaddr' and assigned network address constitute |
| 251 |
a unique identifier for the client's lease and are used by both |
| 252 |
the client and server to identify a lease referred to in any |
| 253 |
DHCP messages. Any configuration parameters in the DHCPACK |
| 254 |
message SHOULD NOT conflict with those in the earlier DHCPOFFER |
| 255 |
message to which the client is responding. The server SHOULD |
| 256 |
NOT check the offered network address at this point. The |
| 257 |
'yiaddr' field in the DHCPACK messages is filled in with the |
| 258 |
selected network address. |
| 259 |
|
| 260 |
If the selected server is unable to satisfy the DHCPREQUEST |
| 261 |
message (e.g., the requested network address has been |
| 262 |
allocated), the server SHOULD respond with a DHCPNAK message. |
| 263 |
|
| 264 |
A server MAY choose to mark addresses offered to clients in |
| 265 |
DHCPOFFER messages as unavailable. The server SHOULD mark an |
| 266 |
address offered to a client in a DHCPOFFER message as available |
| 267 |
if the server receives no DHCPREQUEST message from that client. |
| 268 |
|
| 269 |
5. The client receives the DHCPACK message with configuration |
| 270 |
parameters. The client SHOULD perform a final check on the |
| 271 |
parameters (e.g., ARP for allocated network address), and it |
| 272 |
notes the duration of the lease specified in the DHCPACK |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Park, 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="./rfc4039">RFC 4039</a> Rapid Commit Option for DHCPv4 March 2005</span> |
| 279 |
|
| 280 |
|
| 281 |
message. At this point, the client is configured. If the |
| 282 |
client detects that the address is already in use (e.g., |
| 283 |
through the use of ARP), the client MUST send a DHCPDECLINE |
| 284 |
message to the server, and it restarts the configuration |
| 285 |
process. The client SHOULD wait a minimum of ten seconds |
| 286 |
before restarting the configuration process to avoid excessive |
| 287 |
network traffic in case of looping. |
| 288 |
|
| 289 |
If the client receives a DHCPNAK message, the client restarts |
| 290 |
the configuration process. |
| 291 |
|
| 292 |
The client times out and retransmits the DHCPREQUEST message if |
| 293 |
the client receives neither a DHCPACK nor a DHCPNAK message. |
| 294 |
The client retransmits the DHCPREQUEST according to the |
| 295 |
retransmission algorithm in <a href="./rfc2131#section-4.1">section 4.1 of [RFC2131]</a>. The |
| 296 |
client should choose to retransmit the DHCPREQUEST enough times |
| 297 |
to give an adequate probability of contacting the server |
| 298 |
without causing the client (and the user of that client) to |
| 299 |
wait too long before giving up; e.g., a client retransmitting |
| 300 |
as described in <a href="./rfc2131#section-4.1">section 4.1 of [RFC2131]</a> might retransmit the |
| 301 |
DHCPREQUEST message four times, for a total delay of 60 |
| 302 |
seconds, before restarting the initialization procedure. If |
| 303 |
the client receives neither a DHCPACK nor a DHCPNAK message |
| 304 |
after employing the retransmission algorithm, the client |
| 305 |
reverts to INIT state and restarts the initialization process. |
| 306 |
The client SHOULD notify the user that the initialization |
| 307 |
process has failed and is restarting. |
| 308 |
|
| 309 |
6. The client may choose to relinquish its lease on a network |
| 310 |
address by sending a DHCPRELEASE message to the server. The |
| 311 |
client identifies the lease to be released with its 'client |
| 312 |
identifier' or 'chaddr' and network address in the DHCPRELEASE |
| 313 |
message. If the client used a 'client identifier' when it |
| 314 |
obtained the lease, it MUST use the same 'client identifier' in |
| 315 |
the DHCPRELEASE message. |
| 316 |
|
| 317 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Administrative Considerations</span> |
| 318 |
|
| 319 |
Network administrators MUST only enable the use of Rapid Commit on a |
| 320 |
DHCP server if one of the following conditions is met: |
| 321 |
|
| 322 |
1. The server is the only server for the subnet. |
| 323 |
|
| 324 |
2. When multiple servers are present, they may each commit a |
| 325 |
binding for all clients, and therefore each server must have |
| 326 |
sufficient addresses available. |
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Park, 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="./rfc4039">RFC 4039</a> Rapid Commit Option for DHCPv4 March 2005</span> |
| 335 |
|
| 336 |
|
| 337 |
A server MAY allow configuration for a different (likely shorter) |
| 338 |
initial lease time for addresses assigned when Rapid Commit is used |
| 339 |
to expedite reclaiming addresses not used by clients. |
| 340 |
|
| 341 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Rapid Commit Option Format</span> |
| 342 |
|
| 343 |
The Rapid Commit option is used to indicate the use of the two- |
| 344 |
message exchange for address assignment. The code for the Rapid |
| 345 |
Commit option is 80. The format of the option is: |
| 346 |
|
| 347 |
Code Len |
| 348 |
+-----+-----+ |
| 349 |
| 80 | 0 | |
| 350 |
+-----+-----+ |
| 351 |
|
| 352 |
A client MUST include this option in a DHCPDISCOVER message if the |
| 353 |
client is prepared to perform the DHCPDISCOVER-DHCPACK message |
| 354 |
exchange described earlier. |
| 355 |
|
| 356 |
A server MUST include this option in a DHCPACK message sent in a |
| 357 |
response to a DHCPDISCOVER message when completing the DHCPDISCOVER- |
| 358 |
DHCPACK message exchange. |
| 359 |
|
| 360 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span> |
| 361 |
|
| 362 |
IANA has assigned value 80 for the Rapid Commit option code in |
| 363 |
accordance with [<a href="./rfc2939" title=""Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types"">RFC2939</a>]. |
| 364 |
|
| 365 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span> |
| 366 |
|
| 367 |
The concepts in this document do not significantly alter the security |
| 368 |
considerations for DHCP (see [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>] and [<a href="./rfc3118" title=""Authentication for DHCP Messages"">RFC3118</a>]). However, use |
| 369 |
of this option could expedite denial of service attacks by allowing a |
| 370 |
mischievous client to consume all available addresses more rapidly or |
| 371 |
to do so without requiring two-way communication (as injecting |
| 372 |
DHCPDISCOVER messages with the Rapid Commit option is sufficient to |
| 373 |
cause a server to allocate an address). |
| 374 |
|
| 375 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span> |
| 376 |
|
| 377 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span> |
| 378 |
|
| 379 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 380 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 381 |
|
| 382 |
[<a id="ref-RFC2131">RFC2131</a>] Droms, R., "Dynamic Host Configuration Protocol", <a href="./rfc2131">RFC</a> |
| 383 |
<a href="./rfc2131">2131</a>, March 1997. |
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Park, 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="./rfc4039">RFC 4039</a> Rapid Commit Option for DHCPv4 March 2005</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span> |
| 394 |
|
| 395 |
[<a id="ref-RFC2132">RFC2132</a>] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor |
| 396 |
Extensions", <a href="./rfc2132">RFC 2132</a>, March 1997. |
| 397 |
|
| 398 |
[<a id="ref-RFC2939">RFC2939</a>] Droms, R., "Procedures and IANA Guidelines for Definition |
| 399 |
of New DHCP Options and Message Types", <a href="https://www.rfc-editor.org/bcp/bcp43">BCP 43</a>, <a href="./rfc2939">RFC 2939</a>, |
| 400 |
September 2000. |
| 401 |
|
| 402 |
[<a id="ref-RFC3118">RFC3118</a>] Droms, R. and W. Arbaugh, "Authentication for DHCP |
| 403 |
Messages", <a href="./rfc3118">RFC 3118</a>, June 2001. |
| 404 |
|
| 405 |
[<a id="ref-RFC3315">RFC3315</a>] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., |
| 406 |
and M. Carney, "Dynamic Host Configuration Protocol for |
| 407 |
IPv6 (DHCPv6)", <a href="./rfc3315">RFC 3315</a>, July 2003. |
| 408 |
|
| 409 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgements</span> |
| 410 |
|
| 411 |
Special thanks to Ted Lemon and Andre Kostur for their many valuable |
| 412 |
comments. Thanks to Ralph Droms for his review comments during WGLC. |
| 413 |
Thanks to Noh-Byung Park and Youngkeun Kim for their supports on this |
| 414 |
work. |
| 415 |
|
| 416 |
Particularly, the authors would like to acknowledge the |
| 417 |
implementation contributions by Minho Lee of SAMSUNG Electronics. |
| 418 |
|
| 419 |
|
| 420 |
|
| 421 |
|
| 422 |
|
| 423 |
|
| 424 |
|
| 425 |
|
| 426 |
|
| 427 |
|
| 428 |
|
| 429 |
|
| 430 |
|
| 431 |
|
| 432 |
|
| 433 |
|
| 434 |
|
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Park, 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="./rfc4039">RFC 4039</a> Rapid Commit Option for DHCPv4 March 2005</span> |
| 447 |
|
| 448 |
|
| 449 |
Authors' Addresses |
| 450 |
|
| 451 |
Soohong Daniel Park |
| 452 |
Mobile Platform Laboratory |
| 453 |
SAMSUNG Electronics |
| 454 |
416, Maetan-3dong, Yeongtong-Gu |
| 455 |
Suwon, Korea |
| 456 |
|
| 457 |
Phone: +82-31-200-4508 |
| 458 |
EMail: [email protected] |
| 459 |
|
| 460 |
|
| 461 |
Pyungsoo Kim |
| 462 |
Mobile Platform Laboratory |
| 463 |
SAMSUNG Electronics |
| 464 |
416, Maetan-3dong, Yeongtong-Gu |
| 465 |
Suwon, Korea |
| 466 |
|
| 467 |
Phone: +82-31-200-4635 |
| 468 |
EMail: [email protected] |
| 469 |
|
| 470 |
|
| 471 |
Bernie Volz |
| 472 |
Cisco Systems, Inc. |
| 473 |
1414 Massachusetts Ave. |
| 474 |
Boxborough, MA 01719 |
| 475 |
USA |
| 476 |
|
| 477 |
Phone: +1-978-936-0382 |
| 478 |
EMail: [email protected] |
| 479 |
|
| 480 |
|
| 481 |
|
| 482 |
|
| 483 |
|
| 484 |
|
| 485 |
|
| 486 |
|
| 487 |
|
| 488 |
|
| 489 |
|
| 490 |
|
| 491 |
|
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Park, 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="./rfc4039">RFC 4039</a> Rapid Commit Option for DHCPv4 March 2005</span> |
| 503 |
|
| 504 |
|
| 505 |
Full Copyright Statement |
| 506 |
|
| 507 |
Copyright (C) The Internet Society (2005). |
| 508 |
|
| 509 |
This document is subject to the rights, licenses and restrictions |
| 510 |
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors |
| 511 |
retain all their rights. |
| 512 |
|
| 513 |
This document and the information contained herein are provided on an |
| 514 |
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS |
| 515 |
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET |
| 516 |
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, |
| 517 |
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE |
| 518 |
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED |
| 519 |
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 520 |
|
| 521 |
Intellectual Property |
| 522 |
|
| 523 |
The IETF takes no position regarding the validity or scope of any |
| 524 |
Intellectual Property Rights or other rights that might be claimed to |
| 525 |
pertain to the implementation or use of the technology described in |
| 526 |
this document or the extent to which any license under such rights |
| 527 |
might or might not be available; nor does it represent that it has |
| 528 |
made any independent effort to identify any such rights. Information |
| 529 |
on the procedures with respect to rights in RFC documents can be |
| 530 |
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>. |
| 531 |
|
| 532 |
Copies of IPR disclosures made to the IETF Secretariat and any |
| 533 |
assurances of licenses to be made available, or the result of an |
| 534 |
attempt made to obtain a general license or permission for the use of |
| 535 |
such proprietary rights by implementers or users of this |
| 536 |
specification can be obtained from the IETF on-line IPR repository at |
| 537 |
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>. |
| 538 |
|
| 539 |
The IETF invites any interested party to bring to its attention any |
| 540 |
copyrights, patents or patent applications, or other proprietary |
| 541 |
rights that may cover technology that may be required to implement |
| 542 |
this standard. Please address the information to the IETF at ietf- |
| 543 |
[email protected]. |
| 544 |
|
| 545 |
Acknowledgement |
| 546 |
|
| 547 |
Funding for the RFC Editor function is currently provided by the |
| 548 |
Internet Society. |
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
Park, et al. Standards Track [Page 10] |
| 557 |
</pre> |