1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
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
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
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
445
|
<pre>Network Working Group H. Schulzrinne
Request for Comments: 5223 Columbia University
Category: Standards Track J. Polk
Cisco
H. Tschofenig
Nokia Siemens Networks
August 2008
<span class="h1">Discovering Location-to-Service Translation (LoST) Servers Using the</span>
<span class="h1">Dynamic Host Configuration Protocol (DHCP)</span>
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Abstract
The Location-to-Service Translation (LoST) Protocol describes an XML-
based protocol for mapping service identifiers and geospatial or
civic location information to service contact Uniform Resource
Locators (URLs). LoST servers can be located anywhere, but a
placement closer to the end host, e.g., in the access network, is
desirable. In disaster situations with intermittent network
connectivity, such a LoST server placement provides benefits
regarding the resiliency of emergency service communication.
This document describes how a LoST client can discover a LoST server
using the Dynamic Host Configuration Protocol (DHCP).
<span class="grey">Schulzrinne, et al. Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc5223">RFC 5223</a> DHCP-Based LoST Discovery August 2008</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-3">3</a>. Domain Name Encoding . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4">4</a>. LoST Server DHCPv4 Option . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-5">5</a>. LoST Server DHCPv6 Option . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-6">6</a>. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-7">7</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-7.1">7.1</a>. DHCPv4 Option . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-7.2">7.2</a>. DHCPv6 Option . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-8">8</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-9">9</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-10">10</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-10.1">10.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-10.2">10.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Location-to-Service Translation (LoST) Protocol [<a href="./rfc5222" title=""LoST: A Location-to-Service Translation Protocol"">RFC5222</a>]
describes an XML-based protocol for mapping service identifiers and
geospatial or civic location information to service contact Uniform
Resource Locators (URLs).
In order to interact with a LoST server, the LoST client needs to
discover the server's IP address. Several mechanisms can be used to
learn this address, including manual configuration. In environments
where the access network itself either deploys a LoST server or knows
a third party that operates a LoST server, DHCP can provide the end
host with a domain name. This domain name is then used as input to
the DNS-based resolution mechanism described in LoST [<a href="./rfc5222" title=""LoST: A Location-to-Service Translation Protocol"">RFC5222</a>] that
reuses the URI-enabled NAPTR specification (see [<a href="./rfc4848" title=""Domain-Based Application Service Location Using URIs and the Dynamic Delegation Discovery Service (DDDS)"">RFC4848</a>]).
This document specifies a DHCPv4 and a DHCPv6 option that allows LoST
clients to discover local LoST servers.
<a href="#section-2">Section 2</a> provides terminology. <a href="#section-3">Section 3</a> shows the encoding of the
domain name. <a href="#section-4">Section 4</a> describes the DHCPv4 option while <a href="#section-5">Section 5</a>
describes the DHCPv6 option, with the same functionality. IANA and
Security Considerations complete the document in Sections <a href="#section-7">7</a> and <a href="#section-8">8</a>.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
In this document, the key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" are to be interpreted as described in <a href="./rfc2119">RFC 2119</a>
[<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="grey">Schulzrinne, et al. Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc5223">RFC 5223</a> DHCP-Based LoST Discovery August 2008</span>
Within this document, we use terminology from [<a href="./rfc5012" title=""Requirements for Emergency Context Resolution with Internet Technologies"">RFC5012</a>] and
[<a href="./rfc5222" title=""LoST: A Location-to-Service Translation Protocol"">RFC5222</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Domain Name Encoding</span>
This section describes the encoding of the domain name used in the
DHCPv4 option shown in <a href="#section-4">Section 4</a> and also used in the DHCPv6 option
shown in <a href="#section-5">Section 5</a>.
The domain name is encoded according to <a href="./rfc1035#section-3.1">Section 3.1 of RFC 1035</a>
[<a href="./rfc1035" title=""Domain names - implementation and specification"">RFC1035</a>] whereby each label is represented as a one-octet length
field followed by that number of octets. Since every domain name
ends with the null label of the root, a domain name is terminated by
a length byte of zero. The high-order two bits of every length octet
MUST be zero, and the remaining six bits of the length field limit
the label to 63 octets or less. To simplify implementations, the
total length of a domain name (i.e., label octets and label length
octets) is restricted to 255 octets or less.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. LoST Server DHCPv4 Option</span>
The LoST server DHCPv4 option carries a DNS (<a href="./rfc1035">RFC 1035</a> [<a href="./rfc1035" title=""Domain names - implementation and specification"">RFC1035</a>])
fully-qualified domain name (FQDN) to be used by the LoST client to
locate a LoST server.
The DHCP option for this encoding has the following format:
Code Len LoST Server Domain Name
+-----+-----+-----+-----+-----+-----+-----+----
| 137 | n | s1 | s2 | s3 | s4 | s5 | ...
+-----+-----+-----+-----+-----+-----+-----+----
Figure 1: LoST FQDN DHCPv4 Option
The values s1, s2, s3, etc. represent the domain name labels in the
domain name encoding. Note that the length field in the DHCPv4
option represents the length of the entire domain name encoding,
whereas the length fields in the domain name encoding (see <a href="#section-3">Section 3</a>)
is the length of a single domain name label.
Code: OPTION_V4_LOST (137)
Len: Length of the 'LoST Server Domain Name' field
in octets; variable.
LoST Server Domain Name: The domain name of the LoST
server for the client to use.
<span class="grey">Schulzrinne, et al. Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc5223">RFC 5223</a> DHCP-Based LoST Discovery August 2008</span>
A DHCPv4 client MAY request a LoST server domain name in a Parameter
Request List option, as described in [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>].
The encoding of the domain name is described in <a href="#section-3">Section 3</a>.
This option contains a single domain name and, as such, MUST contain
precisely one root label.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. LoST Server DHCPv6 Option</span>
This section defines a DHCPv6 option to carry a domain name.
The DHCPv6 option has the format shown in Figure 2.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_V6_LOST | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LoST Server Domain Name |
| ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: OPTION_V6_LOST (51)
option-length: Length of the 'LoST Server Domain Name' field
in octets; variable.
LoST Server Domain Name: The domain name of the LoST
server for the client to use.
Figure 2: DHCPv6 Option for LoST Server Domain Name List
A DHCPv6 client MAY request a LoST server domain name in an Options
Request Option (ORO), as described in [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>].
The encoding of the domain name is described in <a href="#section-3">Section 3</a>.
This option contains a single domain name and, as such, MUST contain
precisely one root label.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Example</span>
This section shows an example of a DHCPv4 option where the DHCP
server wants to offer the "example.com" domain name to the client as
input to the U-NAPTR LoST discovery procedure. This domain name
would be encoded as follows:
<span class="grey">Schulzrinne, et al. Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc5223">RFC 5223</a> DHCP-Based LoST Discovery August 2008</span>
+----+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
|137 |13 | 7 | e | x | a | m | p | l | e | 3 | c | o | m | 0 |
+----+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
Figure 3: Example for a LoST FQDN DHCPv4 Option
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. DHCPv4 Option</span>
The following DHCPv4 option code for the Location-to-Service
Translation (LoST) Protocol server option has been assigned by IANA:
Option Name Value Described in
-----------------------------------------------
OPTION_V4_LOST 137 <a href="#section-4">Section 4</a>
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. DHCPv6 Option</span>
IANA has assigned the following DHCPv6 option code for the Location-
to-Service Translation (LoST) Protocol option:
Option Name Value Described in
------------------------------------------------
OPTION_V6_LOST 51 <a href="#section-5">Section 5</a>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
If an adversary manages to modify the response from a DHCP server or
insert its own response, a LoST client could be led to contact a
rogue LoST server under the control of the adversary or be given an
invalid address. These threats are documented in [<a href="./rfc5069" title=""Security Threats and Requirements for Emergency Call Marking and Mapping"">RFC5069</a>]. The
security considerations in [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>], [<a href="./rfc2132" title=""DHCP Options and BOOTP Vendor Extensions"">RFC2132</a>], and [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>] are
applicable to this document.
[<a id="ref-RFC5222">RFC5222</a>] enumerates the LoST security mechanisms.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgements</span>
Andrew Newton reviewed the document and helped simplify the
mechanism. Other helpful input was provided by Jari Arkko, Leslie
Daigle, Vijay K. Gurbani (Gen-ART Review), David W. Hankins, Russ
Housley, Tim Polk, Mark Stapp, and Christian Vogt.
<span class="grey">Schulzrinne, et al. Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc5223">RFC 5223</a> DHCP-Based LoST Discovery August 2008</span>
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span>
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span>
[<a id="ref-RFC1035">RFC1035</a>] Mockapetris, P., "Domain names - implementation and
specification", STD 13, <a href="./rfc1035">RFC 1035</a>, November 1987.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="./rfc2119">RFC 2119</a>, <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, March 1997.
[<a id="ref-RFC2131">RFC2131</a>] Droms, R., "Dynamic Host Configuration Protocol",
<a href="./rfc2131">RFC 2131</a>, March 1997.
[<a id="ref-RFC2132">RFC2132</a>] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
Extensions", <a href="./rfc2132">RFC 2132</a>, March 1997.
[<a id="ref-RFC3315">RFC3315</a>] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", <a href="./rfc3315">RFC 3315</a>, July 2003.
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span>
[<a id="ref-RFC4848">RFC4848</a>] Daigle, L., "Domain-Based Application Service Location
Using URIs and the Dynamic Delegation Discovery Service
(DDDS)", <a href="./rfc4848">RFC 4848</a>, April 2007.
[<a id="ref-RFC5012">RFC5012</a>] Schulzrinne, H. and R. Marshall, "Requirements for
Emergency Context Resolution with Internet Technologies",
<a href="./rfc5012">RFC 5012</a>, January 2008.
[<a id="ref-RFC5069">RFC5069</a>] Taylor, T., Tschofenig, H., Schulzrinne, H., and M.
Shanmugam, "Security Threats and Requirements for
Emergency Call Marking and Mapping", <a href="./rfc5069">RFC 5069</a>,
January 2008.
[<a id="ref-RFC5222">RFC5222</a>] Hardie, T., Newton, A., Schulzrinne, H., and H.
Tschofenig, "LoST: A Location-to-Service Translation
Protocol", <a href="./rfc5222">RFC 5222</a>, August 2008.
<span class="grey">Schulzrinne, et al. Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc5223">RFC 5223</a> DHCP-Based LoST Discovery August 2008</span>
Authors' Addresses
Henning Schulzrinne
Columbia University
Department of Computer Science
450 Computer Science Building
New York, NY 10027
US
EMail: hgs+ecrit@cs.columbia.edu
URI: <a href="http://www.cs.columbia.edu">http://www.cs.columbia.edu</a>
James Polk
Cisco
2200 East President George Bush Turnpike
Richardson, TX 75082
US
EMail: jmpolk@cisco.com
Hannes Tschofenig
Nokia Siemens Networks
Linnoitustie 6
Espoo 02600
Finland
Phone: +358 (50) 4871445
EMail: Hannes.Tschofenig@nsn.com
URI: <a href="http://www.tschofenig.priv.at">http://www.tschofenig.priv.at</a>
<span class="grey">Schulzrinne, et al. Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc5223">RFC 5223</a> DHCP-Based LoST Discovery August 2008</span>
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
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>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Schulzrinne, et al. Standards Track [Page 8]
</pre>
|
