Debian Codegraph @

rfc5107.html

raw
1 <pre>Network Working Group R. Johnson
2 Request for Comments: 5107 J. Jumarasamy
3 Category: Standards Track K. Kinnear
4 M. Stapp
5 Cisco Systems, Inc.
6 February 2008
7
8
9 <span class="h1">DHCP Server Identifier Override Suboption</span>
10
11 Status of This Memo
12
13 This document specifies an Internet standards track protocol for the
14 Internet community, and requests discussion and suggestions for
15 improvements. Please refer to the current edition of the "Internet
16 Official Protocol Standards" (STD 1) for the standardization state
17 and status of this protocol. Distribution of this memo is unlimited.
18
19 Abstract
20
21 This memo defines a new suboption of the DHCP relay information
22 option that allows the DHCP relay to specify a new value for the
23 Server Identifier option, which is inserted by the DHCP Server. This
24 allows the DHCP relay to act as the actual DHCP server such that
25 RENEW DHCPREQUESTs will come to the relay instead of going to the
26 server directly. This gives the relay the opportunity to include the
27 Relay Agent option with appropriate suboptions even on DHCP RENEW
28 messages.
29
30 Table of Contents
31
32 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
33 <a href="#section-2">2</a>. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
34 <a href="#section-3">3</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
35 <a href="#section-4">4</a>. Server Identifier Override Suboption Definition . . . . . . . . <a href="#page-3">3</a>
36 <a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
37 <a href="#section-6">6</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
38 <a href="#section-7">7</a>. Intellectual Property Rights and Copyright . . . . . . . . . . <a href="#page-5">5</a>
39 <a href="#section-8">8</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
40 <a href="#section-8.1">8.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
41 <a href="#section-8.2">8.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Johnson, 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="./rfc5107">RFC 5107</a> Server ID Override Suboption February 2008</span>
55
56
57 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
58
59 There are many situations where a DHCP relay agent is involved, and
60 it can easily insert a Relay Agent Information option [<a href="#ref-3" title="&quot;DHCP Relay Agent Information Option&quot;">3</a>] with
61 appropriate suboptions into DHCPDISCOVER messages. Once the lease
62 has been granted, however, future DHCPREQUEST messages sent by a
63 client in RENEWING state are sent directly to the DHCP server, as
64 specified in the Server Identifier option. In this case, the relay
65 may not see these DHCPREQUEST messages (depending upon network
66 topology) and thus cannot insert the Relay Agent Information option
67 in the DHCPREQUEST messages.
68
69 This DHCP relay agent suboption, Server Identifier Override, allows
70 the relay agent to tell the DHCP server what value to place into the
71 Server Identifier option [<a href="#ref-5" title="&quot;DHCP Options and BOOTP Vendor Extensions&quot;">5</a>]. Using this, the relay agent can force
72 a host in RENEWING state to send DHCPREQUEST messages to the relay
73 agent instead of directly to the server. The relay agent then has
74 the opportunity to insert the Relay Agent Information option with
75 appropriate suboptions and relay the DHCPREQUEST to the actual
76 server. In this fashion, the DHCP server will be provided with the
77 same relay agent information upon renewals (such as Circuit-ID,
78 Remote-ID, Device Class, etc.) as was provided in the initial
79 DHCPDISCOVER message.
80
81 In short, this new suboption allows the DHCPv4 relay to function in
82 the same fashion as the DHCPv6 relay [<a href="#ref-7" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">7</a>] currently does.
83
84 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions</span>
85
86 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
87 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this
88 document are to be interpreted as described in [<a href="#ref-1" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">1</a>].
89
90 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Terminology</span>
91
92 This document uses DHCP terminology as defined in section 1.5 of <a href="./rfc2131">RFC</a>
93 <a href="./rfc2131">2131</a> [<a href="#ref-2" title="&quot;Dynamic Host Configuration Protocol&quot;">2</a>], with the exception of the term "DHCP relay agent" replacing
94 "BOOTP relay agent".
95
96 Other terms used in this document:
97
98 o RENEW DHCPREQUEST - a DHCPREQUEST message sent by a client in
99 RENEWING state
100
101
102
103
104
105
106
107
108 <span class="grey">Johnson, 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="./rfc5107">RFC 5107</a> Server ID Override Suboption February 2008</span>
111
112
113 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Server Identifier Override Suboption Definition</span>
114
115 The format of the suboption is:
116
117 Code Len Overriding Server Identifier Address
118 +-----+-----+-----+-----+-----+-----+
119 | 11 | n | a1 | a2 | a3 | a4 |
120 +-----+-----+-----+-----+-----+-----+
121
122
123 Figure 1
124
125 The option length (n) is 4. The octets "a1" through "a4" specify the
126 value that MUST be inserted into the Server Identifier option by the
127 DHCP Server upon reply.
128
129 DHCP servers that implement this Relay Agent Information suboption
130 MUST use this value, if present in a DHCP message received from a
131 client, as the value to insert into the Server Identifier option in
132 the corresponding response. The DHCP server must also record the
133 address in the suboption for use in subsequent messages to the DHCP
134 client until the next DHCP message is received from the DHCP relay
135 agent.
136
137 If a DHCP server does not understand/implement this Relay Information
138 suboption, it will ignore the suboption, and thus it will insert its
139 own appropriate interface address in the Server Identifier option.
140 In this case, the DHCP Relay will not receive RENEW DHCPREQUEST
141 messages from the client. When configuring a DHCP relay agent to use
142 this suboption, the administrator of the relay agent should take into
143 account whether or not the DHCP server to which the message will be
144 relayed will correctly understand this suboption.
145
146 When servicing a DHCPREQUEST message, the DHCP server would normally
147 look at the Server Identifier option for verification that the
148 address specified there is one of the addresses associated with the
149 DHCP server, silently ignoring the DHCPREQUEST if it does not match a
150 configured DHCP server interface address. If the DHCPREQUEST message
151 contains a Server Identifier Override suboption, however, comparison
152 should be made between the address in this suboption and the Server
153 Identifier option. If both the Server Identifier Override suboption
154 and the Server Identifier option specify the same address, then the
155 server should accept the DHCPREQUEST message for processing,
156 regardless of whether or not the Server Identifier option matches a
157 DHCP server interface.
158
159 The DHCP relay agent should fill in the giaddr field when relaying
160 the message, just as it normally would do.
161
162
163
164 <span class="grey">Johnson, 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="./rfc5107">RFC 5107</a> Server ID Override Suboption February 2008</span>
167
168
169 In a situation where the DHCP relay agent is configured to forward
170 messages to more than one server, the DHCP relay agent SHOULD forward
171 all DHCP messages to all servers. This applies to RENEW DHCPREQUEST
172 messages as well. The intent is that the DHCP relay agent should not
173 need to maintain state information about the DHCP lease.
174
175 DHCP relay agents implementing this suboption SHOULD also implement
176 and use the DHCPv4 Relay Agent Flags Suboption [<a href="#ref-4" title="&quot;The Dynamic Host Configuration Protocol Version 4 (DHCPv4) Relay Agent Flags Suboption&quot;">4</a>] in order to
177 specify whether the DHCP relay agent received the original message as
178 a broadcast or unicast. The DHCP server receiving a message
179 containing the Server Identifier Override Suboption may use this
180 additional information in processing the message.
181
182 Note that if the DHCP relay agent becomes inaccessible by the DHCP
183 client or loses network access to the DHCP server, further RENEW
184 DHCPREQUEST messages from the DHCP client may not be properly
185 processed and the DHCP client's lease may time out.
186
187 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
188
189 Message authentication in DHCP for intradomain use where the out-of-
190 band exchange of a shared secret is feasible is defined in [<a href="#ref-6" title="&quot;Authentication for DHCP Messages&quot;">6</a>].
191 Potential exposures to attack are discussed in <a href="#section-7">Section 7</a> of the DHCP
192 protocol specification in [<a href="#ref-2" title="&quot;Dynamic Host Configuration Protocol&quot;">2</a>].
193
194 The DHCP Relay Agent Information option depends on a trusted
195 relationship between the DHCP relay agent and the DHCP server, as
196 described in <a href="./rfc3046#section-5">Section&nbsp;5 of RFC 3046</a>. While the introduction of
197 fraudulent DHCP relay agent information options can be prevented by a
198 perimeter defense that blocks these options unless the DHCP relay
199 agent is trusted, a deeper defense using the authentication suboption
200 for DHCP relay agent information option [<a href="#ref-8" title="&quot;The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option&quot;">8</a>] SHOULD be deployed as
201 well.
202
203 If a rogue DHCP relay agent were inserted between the DHCP client and
204 the DHCP server, it could redirect clients to itself using this
205 suboption. This would allow such a system to later deny RENEW
206 DHCPREQUESTs and thus force clients to discontinue use of their
207 allocated addresses. It could also allow the rogue relay to change,
208 insert, or delete DHCP options in DHCPACK messages and extend leases
209 beyond what the server has allowed. DHCP authentication [<a href="#ref-6" title="&quot;Authentication for DHCP Messages&quot;">6</a>] and/or
210 DHCP Relay Agent Information option authentication [<a href="#ref-8" title="&quot;The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option&quot;">8</a>] would address
211 this case. (Note that, as is always the case, lack of DHCP
212 authentication would allow a rogue DHCP relay agent to change the
213 Server Identifier Override option in the DHCPOFFER and DHCPACK
214 messages without detection. This threat is not new to the Server
215 Identifier Override suboption.)
216
217
218
219
220 <span class="grey">Johnson, 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="./rfc5107">RFC 5107</a> Server ID Override Suboption February 2008</span>
223
224
225 This document does not add any new vulnerabilities that were not
226 already present, except in the case where DHCP authentication is
227 already in place, and DHCP clients require its use. It is suggested
228 that DHCP Authentication and DHCP Relay Agent Option Authentication
229 SHOULD be deployed when this option is used, or protection should be
230 provided against the insertion of rogue DHCP relay agents between the
231 client and server.
232
233 This relay suboption is not intended, by itself, to provide any
234 additional security benefits.
235
236 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
237
238 IANA has assigned a suboption number (11) for the Server Identifier
239 Override Suboption from the DHCP Relay Agent Information Option [<a href="#ref-3" title="&quot;DHCP Relay Agent Information Option&quot;">3</a>]
240 suboption number space.
241
242 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Intellectual Property Rights and Copyright</span>
243
244 The IETF has been notified of intellectual property rights claimed in
245 regard to some or all of the specification contained in this
246 document. For more information consult the online list of claimed
247 rights.
248
249 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
250
251 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
252
253 [<a id="ref-1">1</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
254 Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
255
256 [<a id="ref-2">2</a>] Droms, R., "Dynamic Host Configuration Protocol", <a href="./rfc2131">RFC 2131</a>,
257 March 1997.
258
259 [<a id="ref-3">3</a>] Patrick, M., "DHCP Relay Agent Information Option", <a href="./rfc3046">RFC 3046</a>,
260 January 2001.
261
262 [<a id="ref-4">4</a>] Kinnear, K., Normoyle, M., and M. Stapp, "The Dynamic Host
263 Configuration Protocol Version 4 (DHCPv4) Relay Agent Flags
264 Suboption", <a href="./rfc5010">RFC 5010</a>, September 2007.
265
266 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
267
268 [<a id="ref-5">5</a>] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
269 Extensions", <a href="./rfc2132">RFC 2132</a>, March 1997.
270
271 [<a id="ref-6">6</a>] Droms, R. and W. Arbaugh, "Authentication for DHCP Messages",
272 <a href="./rfc3118">RFC 3118</a>, June 2001.
273
274
275
276 <span class="grey">Johnson, 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="./rfc5107">RFC 5107</a> Server ID Override Suboption February 2008</span>
279
280
281 [<a id="ref-7">7</a>] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M.
282 Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",
283 <a href="./rfc3315">RFC 3315</a>, July 2003.
284
285 [<a id="ref-8">8</a>] Stapp, M. and T. Lemon, "The Authentication Suboption for the
286 Dynamic Host Configuration Protocol (DHCP) Relay Agent Option",
287 <a href="./rfc4030">RFC 4030</a>, March 2005.
288
289 Authors' Addresses
290
291 Richard A. Johnson
292 Cisco Systems, Inc.
293 170 W. Tasman Dr.
294 San Jose, CA 95134
295 US
296
297 Phone: +1 408 526 4000
298 EMail: [email protected]
299
300
301 Jay Kumarasamy
302 Cisco Systems, Inc.
303 170 W. Tasman Dr.
304 San Jose, CA 95134
305 US
306
307 Phone: +1 408 526 4000
308 EMail: [email protected]
309
310
311 Kim Kinnear
312 Cisco Systems, Inc.
313 170 W. Tasman Dr.
314 San Jose, CA 95134
315 US
316
317 Phone: +1 408 526 4000
318 EMail: [email protected]
319
320
321 Mark Stapp
322 Cisco Systems, Inc.
323 170 W. Tasman Dr.
324 San Jose, CA 95134
325 US
326
327 Phone: +1 408 526 4000
328 EMail: [email protected]
329
330
331
332 <span class="grey">Johnson, 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="./rfc5107">RFC 5107</a> Server ID Override Suboption February 2008</span>
335
336
337 Full Copyright Statement
338
339 Copyright (C) The IETF Trust (2008).
340
341 This document is subject to the rights, licenses and restrictions
342 contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
343 retain all their rights.
344
345 This document and the information contained herein are provided on an
346 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
347 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
348 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
349 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
350 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
351 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
352
353 Intellectual Property
354
355 The IETF takes no position regarding the validity or scope of any
356 Intellectual Property Rights or other rights that might be claimed to
357 pertain to the implementation or use of the technology described in
358 this document or the extent to which any license under such rights
359 might or might not be available; nor does it represent that it has
360 made any independent effort to identify any such rights. Information
361 on the procedures with respect to rights in RFC documents can be
362 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>.
363
364 Copies of IPR disclosures made to the IETF Secretariat and any
365 assurances of licenses to be made available, or the result of an
366 attempt made to obtain a general license or permission for the use of
367 such proprietary rights by implementers or users of this
368 specification can be obtained from the IETF on-line IPR repository at
369 <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
370
371 The IETF invites any interested party to bring to its attention any
372 copyrights, patents or patent applications, or other proprietary
373 rights that may cover technology that may be required to implement
374 this standard. Please address the information to the IETF at
375 [email protected].
376
377
378
379
380
381
382
383
384
385
386
387
388 Johnson, et al. Standards Track [Page 7]
389 </pre>