Debian Codegraph @

rfc6225.html

raw
1 <pre>Internet Engineering Task Force (IETF) J. Polk
2 Request for Comments: 6225 M. Linsner
3 Obsoletes: <a href="./rfc3825">3825</a> Cisco Systems
4 Category: Standards Track M. Thomson
5 ISSN: 2070-1721 Andrew Corporation
6 B. Aboba, Ed.
7 Microsoft Corporation
8 July 2011
9
10
11 <span class="h1">Dynamic Host Configuration Protocol Options for</span>
12 <span class="h1">Coordinate-Based Location Configuration Information</span>
13
14 Abstract
15
16 This document specifies Dynamic Host Configuration Protocol options
17 (both DHCPv4 and DHCPv6) for the coordinate-based geographic location
18 of the client. The Location Configuration Information (LCI) includes
19 Latitude, Longitude, and Altitude, with resolution or uncertainty
20 indicators for each. Separate parameters indicate the reference
21 datum for each of these values. This document obsoletes <a href="./rfc3825">RFC 3825</a>.
22
23 Status of This Memo
24
25 This is an Internet Standards Track document.
26
27 This document is a product of the Internet Engineering Task Force
28 (IETF). It represents the consensus of the IETF community. It has
29 received public review and has been approved for publication by the
30 Internet Engineering Steering Group (IESG). Further information on
31 Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
32
33 Information about the current status of this document, any errata,
34 and how to provide feedback on it may be obtained at
35 <a href="http://www.rfc-editor.org/info/rfc6225">http://www.rfc-editor.org/info/rfc6225</a>.
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2011 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 This document may contain material from IETF Documents or IETF
73 Contributions published or made publicly available before November
74 10, 2008. The person(s) controlling the copyright in some of this
75 material may not have granted the IETF Trust the right to allow
76 modifications of such material outside the IETF Standards Process.
77 Without obtaining an adequate license from the person(s) controlling
78 the copyright in such materials, this document may not be modified
79 outside the IETF Standards Process, and derivative works of it may
80 not be created outside the IETF Standards Process, except to format
81 it for publication as an RFC or to translate it into languages other
82 than English.
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">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
111
112
113 Table of Contents
114
115 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
116 <a href="#section-1.1">1.1</a>. Conventions Used in This Document ..........................<a href="#page-4">4</a>
117 <a href="#section-1.2">1.2</a>. Resolution and Uncertainty .................................<a href="#page-4">4</a>
118 <a href="#section-2">2</a>. DHCP Option Formats .............................................<a href="#page-6">6</a>
119 <a href="#section-2.1">2.1</a>. DHCPv6 GeoLoc Option .......................................<a href="#page-6">6</a>
120 <a href="#section-2.2">2.2</a>. DHCPv4 Options .............................................<a href="#page-8">8</a>
121 <a href="#section-2.3">2.3</a>. Latitude and Longitude Fields .............................<a href="#page-11">11</a>
122 <a href="#section-2.4">2.4</a>. Altitude ..................................................<a href="#page-14">14</a>
123 <a href="#section-2.5">2.5</a>. Datum .....................................................<a href="#page-16">16</a>
124 <a href="#section-3">3</a>. Security Considerations ........................................<a href="#page-17">17</a>
125 <a href="#section-4">4</a>. IANA Considerations ............................................<a href="#page-17">17</a>
126 <a href="#section-4.1">4.1</a>. DHCP Options ..............................................<a href="#page-17">17</a>
127 <a href="#section-4.2">4.2</a>. Altitude Type Registry ....................................<a href="#page-18">18</a>
128 <a href="#section-4.3">4.3</a>. Datum Registry ............................................<a href="#page-18">18</a>
129 <a href="#section-4.4">4.4</a>. GeoLoc Option Version Registry ............................<a href="#page-19">19</a>
130 <a href="#section-5">5</a>. Acknowledgments ................................................<a href="#page-20">20</a>
131 <a href="#section-6">6</a>. References .....................................................<a href="#page-20">20</a>
132 <a href="#section-6.1">6.1</a>. Normative References ......................................<a href="#page-20">20</a>
133 <a href="#section-6.2">6.2</a>. Informative References ....................................<a href="#page-21">21</a>
134 <a href="#appendix-A">Appendix A</a>. GML Mapping ...........................................<a href="#page-23">23</a>
135 <a href="#appendix-A.1">A.1</a>. GML Templates ............................................<a href="#page-23">23</a>
136 <a href="#appendix-B">Appendix B</a>. Calculations of Resolution ............................<a href="#page-27">27</a>
137 B.1. Location Configuration Information of "White House"
138 (Example 1) ..............................................<a href="#page-27">27</a>
139 B.2. Location Configuration Information of "Sears Tower"
140 (Example 2) ..............................................<a href="#page-29">29</a>
141 <a href="#appendix-C">Appendix C</a>. Calculations of Uncertainty ...........................<a href="#page-30">30</a>
142 C.1. Location Configuration Information of "Sydney Opera
143 House" (Example 3) .......................................<a href="#page-30">30</a>
144 <a href="#appendix-D">Appendix D</a>. Changes from <a href="./rfc3825">RFC 3825</a> .................................<a href="#page-34">34</a>
145
146 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
147
148 The physical location of a network device has a range of
149 applications. In particular, emergency telephony applications rely
150 on knowing the location of a caller in order to determine the correct
151 emergency center.
152
153 The location of a device can be represented either in terms of
154 geospatial (or geodetic) coordinates, or as a civic address.
155 Different applications may be more suited to one form of location
156 information; therefore, both the geodetic and civic forms may be used
157 simultaneously.
158
159
160
161
162
163
164 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
167
168
169 This document specifies Dynamic Host Configuration Protocol v4
170 (DHCPv4) [<a href="./rfc2131" title="&quot;Dynamic Host Configuration Protocol&quot;">RFC2131</a>] and DHCPv6 [<a href="./rfc3315" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3315</a>] options for the coordinate-
171 based geographic location of the client, to be provided by the
172 server. "Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6)
173 Option for Civic Addresses Configuration Information" [<a href="./rfc4776" title="&quot;Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information&quot;">RFC4776</a>]
174 specifies DHCP options for civic addresses.
175
176 The geodetic coordinate options defined in this document and the
177 civic address options defined in <a href="./rfc4776">RFC 4776</a> [<a href="./rfc4776" title="&quot;Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information&quot;">RFC4776</a>] enable a DHCP
178 client to obtain its location. For example, a wired Ethernet host
179 might use these options for location determination. In this case,
180 the location information could be derived from a wiremap by the DHCP
181 server, using the Circuit ID Relay Agent Information Option (RAIO)
182 defined (as Sub-Option 1) in <a href="./rfc3046">RFC 3046</a> [<a href="./rfc3046" title="&quot;DHCP Relay Agent Information Option&quot;">RFC3046</a>]. The DHCP server
183 could correlate the Circuit ID with the geographic location where the
184 identified circuit terminates (such as the location of the wall
185 jack).
186
187 The mechanism defined here may also be utilized to provide location
188 to wireless hosts. DHCP relay agent sub-options (RAIO) [<a href="./rfc3046" title="&quot;DHCP Relay Agent Information Option&quot;">RFC3046</a>]
189 provide one method a DHCP server might use to perform host location
190 determination. Currently, the relay agent sub-options do not include
191 data sets required for device-level location determination of
192 wireless hosts. In cases where the DHCP server uses RAIO for
193 location determination, a wireless host can use this mechanism to
194 discover the location of the radio access point, or the area of
195 coverage for the radio access point.
196
197 An important feature of this specification is that after the relevant
198 DHCP exchanges have taken place, the location information is stored
199 on the end device rather than somewhere else, where retrieving it
200 might be difficult in practice.
201
202 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Conventions Used in This Document</span>
203
204 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
205 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
206 document are to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
207
208 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Resolution and Uncertainty</span>
209
210 The DHCP options defined in this document include fields quantifying
211 the resolution or uncertainty associated with a target location. No
212 inferences relating to privacy policies can be drawn from either
213 uncertainty or resolution values.
214
215
216
217
218
219
220 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
223
224
225 As utilized in this document, resolution refers to the accuracy of a
226 reported location, as expressed by the number of valid bits in each
227 of the Latitude, Longitude, and Altitude fields.
228
229 The Latitude (LaRes), Longitude (LoRes), and Altitude (AltRes)
230 Resolution fields are encoded as 6-bit, unsigned integer values. In
231 the DHCPv4 GeoConf Option 123, the LaRes, LoRes, and AltRes fields
232 are used to encode the number of bits of resolution. The resolution
233 sub-fields accommodate the desire to easily adjust the precision of a
234 reported location. Contents beyond the claimed resolution MAY be
235 randomized to obscure greater precision that might be available.
236
237 In the context of location technology, uncertainty is a
238 quantification of errors. Any method for determining location is
239 subject to some sources of error; uncertainty describes the amount of
240 error that is present. Uncertainty might be the coverage area of a
241 wireless transmitter, the extent of a building, or a single room.
242
243 Uncertainty is usually represented as an area within which the target
244 is located. In this document, each of the three axes can be assigned
245 an uncertainty value. In effect, this describes a rectangular prism,
246 which may be used as a coarse representation of a more complex shape
247 that fits within it. See <a href="#section-2.3.2">Section 2.3.2</a> for more detail on the
248 correspondence between shapes and uncertainty.
249
250 When representing locations from sources that can quantify
251 uncertainty, the goal is to find the smallest possible rectangular
252 prism that this format can describe. This is achieved by taking the
253 minimum and maximum values on each axis and ensuring that the final
254 encoding covers these points. This increases the region of
255 uncertainty, but ensures that the region that is described
256 encompasses the target location.
257
258 The DHCPv4 option formats defined in this document support resolution
259 and uncertainty parameters. The DHCPv4 GeoConf Option 123 includes a
260 resolution parameter for each of the dimensions of location. Since
261 this resolution parameter need not apply to all dimensions equally, a
262 resolution value is included for each of the three location elements.
263 The DHCPv4 GeoLoc Option 144 as well as the DHCPv6 GeoLoc Option 63
264 format utilize an uncertainty parameter.
265
266 <a href="#appendix-A">Appendix A</a> describes the mapping of DHCP option values to the
267 Geography Markup Language (GML). <a href="#appendix-B">Appendix B</a> of this document
268 provides examples showing the calculation of resolution values.
269 <a href="#appendix-C">Appendix C</a> provides an example demonstrating calculation of
270 uncertainty values.
271
272
273
274
275
276 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
279
280
281 Since the Presence Information Data Format Location Object (PIDF-LO)
282 [<a href="./rfc4119" title="&quot;A Presence-based GEOPRIV Location Object Format&quot;">RFC4119</a>] [<a href="./rfc5491" title="&quot;GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations&quot;">RFC5491</a>] is used to convey location and the associated
283 uncertainty within an emergency call [<a href="#ref-Convey" title="&quot;Location Conveyance for the Session Initiation Protocol&quot;">Convey</a>], a mechanism is needed
284 to convert the information contained within the DHCPv4 and DHCPv6
285 options to PIDF-LO. This document describes the following
286 conversions:
287
288 o DHCPv4 GeoConf Option 123 to PIDF-LO
289
290 o DHCPv4 GeoLoc Option 144 and DHCPv6 GeoLoc Option 63 to PIDF-LO
291
292 o PIDF-LO to DHCP GeoLoc Option 144 and DHCPv6 GeoLoc Option 63
293
294 Conversion to PIDF-LO does not increase uncertainty; conversion from
295 PIDF-LO to the DHCPv4 GeoLoc Option 144 and the DHCPv6 GeoLoc Option
296 63 increases uncertainty by less than a factor of 2 in each
297 dimension. Since it is not possible to translate an arbitrary
298 PIDF-LO to the DHCP GeoConf Option 123 with a bounded increase in
299 uncertainty, the conversion is not specified.
300
301 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. DHCP Option Formats</span>
302
303 This section defines the format for the DHCPv4 and DHCPv6 options.
304 These options utilize a similar format, differing primarily in the
305 option code.
306
307 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. DHCPv6 GeoLoc Option</span>
308
309 The format of the DHCPv6 [<a href="./rfc3315" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3315</a>] GeoLoc Option is as follows:
310
311 0 1 2 3
312 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
313 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
314 | Option Code (63) | OptLen |
315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
316 | LatUnc | Latitude +
317 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
318 | Lat (cont'd) | LongUnc | Longitude +
319 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
320 | Longitude (cont'd) | AType | AltUnc | Altitude +
321 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
322 | Altitude (cont'd) |Ver| Res |Datum|
323 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
324
325 Code: 16 bits. The code for the DHCP Option Code (63).
326
327 OptLen: Option Length. For version 1, the option length is 16.
328
329
330
331
332 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
335
336
337 LatUnc: 6 bits. When the Ver field = 1, this field represents
338 latitude uncertainty. The contents of this field are
339 undefined for other values of the Ver field.
340
341 Latitude: A 34-bit fixed-point value consisting of 9 bits of
342 integer and 25 bits of fraction, interpreted as described
343 in <a href="#section-2.3">Section 2.3</a>.
344
345 LongUnc: 6 bits. When the Ver field = 1, this field represents
346 longitude uncertainty. The contents of this field are
347 undefined for other values of the Ver field.
348
349 Longitude: A 34-bit fixed-point value consisting of 9 bits of
350 integer and 25 bits of fraction, interpreted as described
351 in <a href="#section-2.3">Section 2.3</a>.
352
353 AType: 4 bits. Altitude Type, defined in <a href="#section-2.4">Section 2.4</a>.
354
355 AltUnc: 6 bits. When the Ver field = 1, this field represents
356 altitude uncertainty. The contents of this field are
357 undefined for other values of the Ver field.
358
359 Altitude: A 30-bit value defined by the AType field, described in
360 <a href="#section-2.4">Section 2.4</a>.
361
362 Ver: The Ver field is 2 bits, providing for four potential
363 versions. This specification defines the behavior of
364 version 1. The Ver field is always located at the same
365 offset from the beginning of the option, regardless of
366 the version in use. DHCPv6 clients implementing this
367 specification MUST support receiving version 1 responses.
368 DHCPv6 servers implementing this specification MUST send
369 version 1 responses.
370
371 Res: 3 bits. The Res field is reserved. These bits have been
372 used by [<a href="#ref-IEEE-802.11y">IEEE-802.11y</a>], but are not defined within this
373 specification.
374
375 Datum: 3 bits. The Map Datum used for the coordinates given in
376 this option.
377
378
379
380
381
382
383
384
385
386
387
388 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
391
392
393 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. DHCPv4 Options</span>
394
395 <span class="h4"><a class="selflink" id="section-2.2.1" href="#section-2.2.1">2.2.1</a>. DHCPv4 GeoConf Option</span>
396
397 The format of the DHCPv4 GeoConf Option is as follows:
398
399 0 1 2 3
400 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
401 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
402 | Code 123 | Length | LaRes | Latitude +
403 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
404 | Latitude (cont'd) | LoRes | +
405 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
406 | Longitude |
407 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
408 | AType | AltRes | Altitude +
409 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
410 | Alt.(cont'd) | Res |Datum|
411 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
412
413 Code: 8 bits. The code for the DHCPv4 GeoConf Option (123).
414
415 Length: 8 bits. The length of the option, in octets.
416 The option length is 16.
417
418 LaRes: 6 bits. This field represents latitude resolution.
419
420 Latitude: A 34-bit fixed-point value consisting of 9 bits of signed
421 integer and 25 bits of fraction, interpreted as described
422 in <a href="#section-2.3">Section 2.3</a>.
423
424 LoRes: 6 bits. This field represents longitude resolution.
425
426 Longitude: A 34-bit fixed-point value consisting of 9 bits of signed
427 integer and 25 bits of fraction, interpreted as described
428 in <a href="#section-2.3">Section 2.3</a>.
429
430 AType: 4 bits. Altitude Type, defined in <a href="#section-2.4">Section 2.4</a>.
431
432 AltRes: 6 bits. This field represents altitude resolution.
433
434 Altitude: A 30-bit value defined by the AType field, described in
435 <a href="#section-2.4">Section 2.4</a>.
436
437
438
439
440
441
442
443
444 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
447
448
449 Res: 5 bits. The Res field is reserved. These bits have been
450 used by IEEE 802.11y [<a href="#ref-IEEE-802.11y">IEEE-802.11y</a>], but are not defined
451 within this specification.
452
453 Datum: 3 bits. The Map Datum used for the coordinates given in
454 this option.
455
456 <span class="h4"><a class="selflink" id="section-2.2.2" href="#section-2.2.2">2.2.2</a>. DHCPv4 GeoLoc Option</span>
457
458 The format of the DHCPv4 GeoLoc Option is as follows:
459
460 0 1 2 3
461 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
462 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
463 | Code 144 | Length | LatUnc | Latitude +
464 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
465 | Latitude (cont'd) | LongUnc | +
466 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
467 | Longitude |
468 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
469 | AType | AltUnc | Altitude +
470 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
471 | Alt.(cont'd) |Ver| Res |Datum|
472 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
473
474 Code: 8 bits. The code for the DHCPv4 GeoLoc Option (144).
475
476 Length: 8 bits. The length of the option, in octets.
477 For version 1, the option length is 16.
478
479 LatUnc: 6 bits. When the Ver field = 1, this field represents
480 latitude uncertainty. The contents of this field are
481 undefined for other values of the Ver field.
482
483 Latitude: A 34-bit fixed-point value consisting of 9 bits of
484 integer and 25 bits of fraction, interpreted as described
485 in <a href="#section-2.3">Section 2.3</a>.
486
487 LongUnc: 6 bits. When the Ver field = 1, this field represents
488 longitude uncertainty. The contents of this field are
489 undefined for other values of the Ver field.
490
491 Longitude: A 34-bit fixed-point value consisting of 9 bits of
492 integer and 25 bits of fraction, interpreted as described
493 in <a href="#section-2.3">Section 2.3</a>.
494
495 AType: 4 bits. Altitude Type, defined in <a href="#section-2.4">Section 2.4</a>.
496
497
498
499
500 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
503
504
505 AltUnc: 6 bits. When the Ver field = 1, this field represents
506 altitude uncertainty. The contents of this field are
507 undefined for other values of the Ver field.
508
509 Altitude: A 30-bit value defined by the AType field, described in
510 <a href="#section-2.4">Section 2.4</a>.
511
512 Ver: The Ver field is 2 bits, providing for four potential
513 versions. This specification defines the behavior of
514 version 1. The Ver field is always located at the same
515 offset from the beginning of the option, regardless of
516 the version in use.
517
518 Res: 3 bits. The Res field is reserved. These bits have been
519 used by [<a href="#ref-IEEE-802.11y">IEEE-802.11y</a>], but are not defined within this
520 specification.
521
522 Datum: 3 bits. The Map Datum used for the coordinates given in
523 this option.
524
525 <span class="h4"><a class="selflink" id="section-2.2.3" href="#section-2.2.3">2.2.3</a>. Option Support</span>
526
527 <span class="h5"><a class="selflink" id="section-2.2.3.1" href="#section-2.2.3.1">2.2.3.1</a>. Client Support</span>
528
529 DHCPv4 clients implementing this specification MUST support receiving
530 the DHCPv4 GeoLoc Option 144 (version 1), and MAY support receiving
531 the DHCPv4 GeoConf Option 123 (originally defined in <a href="./rfc3825">RFC 3825</a>
532 [<a href="./rfc3825" title="&quot;Dynamic Host Configuration Protocol Option for Coordinate- based Location Configuration Information&quot;">RFC3825</a>]).
533
534 DHCPv4 clients request the DHCPv4 server to send GeoConf Option 123,
535 GeoLoc Option 144, or both via inclusion of the Parameter Request
536 List option. As noted in <a href="./rfc2132#section-9.8">Section&nbsp;9.8 of RFC 2132</a> [<a href="./rfc2132" title="&quot;DHCP Options and BOOTP Vendor Extensions&quot;">RFC2132</a>]:
537
538 This option is used by a DHCP client to request values for
539 specified configuration parameters. The list of requested
540 parameters is specified as n octets, where each octet is a valid
541 DHCP option code as defined in this document.
542
543 The client MAY list the options in order of preference. The DHCP
544 server is not required to return the options in the requested
545 order, but MUST try to insert the requested options in the order
546 requested by the client.
547
548
549
550
551
552
553
554
555
556 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
559
560
561 When DHCPv4 and DHCPv6 clients implementing this specification do not
562 understand a datum value, they MUST assume a World Geodetic System
563 1984 (WGS84) [<a href="#ref-WGS84" title="&quot;Department of Defense (DoD) World Geodetic System 1984 (WGS 84), Third Edition&quot;">WGS84</a>] datum (European Petroleum Survey Group (EPSG)
564 [<a href="#ref-EPSG">EPSG</a>] 4326 or 4979, depending on whether there is an altitude value
565 present) and proceed accordingly. Assuming that a less accurate
566 location value is better than none, this ensures that some (perhaps
567 less accurate) location is available to the client.
568
569 <span class="h5"><a class="selflink" id="section-2.2.3.2" href="#section-2.2.3.2">2.2.3.2</a>. Server Option Selection</span>
570
571 A DHCPv4 server implementing this specification MUST support sending
572 GeoLoc Option 144 version 1 and SHOULD support sending GeoConf Option
573 123 in responses.
574
575 A DHCPv4 server that provides location information SHOULD honor the
576 Parameter Request List included by the DHCPv4 client in order to
577 decide whether to send GeoConf Option 123, GeoLoc Option 144, or both
578 in the Response.
579
580 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Latitude and Longitude Fields</span>
581
582 The latitude and longitude values in this specification are encoded
583 as 34-bit, two's complement, fixed-point values with 9 integer bits
584 and 25 fractional bits. The exact meaning of these values is
585 determined by the datum; the description in this section applies to
586 the datums defined in this document. This document uses the same
587 definition for all datums it specifies.
588
589 When encoding, latitude and longitude values are rounded to the
590 nearest 34-bit binary representation. This imprecision is considered
591 acceptable for the purposes to which this form is intended to be
592 applied and is ignored when decoding.
593
594 Positive latitudes are north of the equator, and negative latitudes
595 are south of the equator. Positive longitudes are east of the Prime
596 Meridian, and negative (two's complement) longitudes are west of the
597 Prime Meridian.
598
599 Within the coordinate reference systems defined in this document
600 (Datum values 1-3), longitude values outside the range of -180 to 180
601 decimal degrees or latitude values outside the range of -90 to 90
602 degrees MUST be considered invalid. Server implementations SHOULD
603 prevent the entry of invalid values within the selected coordinate
604 reference system. Location consumers MUST ignore invalid location
605 coordinates and SHOULD log errors related to invalid location.
606
607
608
609
610
611
612 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
615
616
617 <span class="h4"><a class="selflink" id="section-2.3.1" href="#section-2.3.1">2.3.1</a>. Latitude and Longitude Resolution</span>
618
619 In the DHCPv4 GeoConf Option 123, the LaRes value encodes the number
620 of high-order latitude bits that MUST be considered valid. Any bits
621 entered to the right of this limit MUST NOT be considered valid and
622 might be purposely false, or zeroed by the sender. The examples in
623 <a href="#appendix-B">Appendix B</a> illustrate that a smaller value in the resolution field
624 increases the area within which the device is located. A value of 2
625 in the LaRes field indicates a precision of no greater than 1/6th
626 that of the globe (see the first example of <a href="#appendix-B">Appendix B</a>). A value of
627 34 in the LaRes field indicates a precision of about 3.11 mm in
628 latitude at the equator.
629
630 In the DHCPv4 GeoConf Option 123, the LoRes value encodes the number
631 of high-order longitude bits that MUST be considered valid. Any bits
632 entered to the right of this limit MUST NOT be considered valid and
633 might be purposely false, or zeroed by the sender. A value of 2 in
634 the LoRes field indicates precision of no greater than 1/6th that of
635 the globe (see the first example of <a href="#appendix-B">Appendix B</a>). A value of 34 in
636 the LoRes field indicates a precision of about 2.42 mm in longitude
637 (at the equator). Because lines of longitude converge at the poles,
638 the distance is smaller (better precision) for locations away from
639 the equator.
640
641 <span class="h4"><a class="selflink" id="section-2.3.2" href="#section-2.3.2">2.3.2</a>. Latitude and Longitude Uncertainty</span>
642
643 In the DHCPv6 GeoLoc Option 63 and the DHCPv4 GeoLoc Option 144, the
644 Latitude and Longitude Uncertainty fields (LatUnc and LongUnc)
645 quantify the amount of uncertainty in each of the latitude and
646 longitude values, respectively. A value of 0 is reserved to indicate
647 that the uncertainty is unknown; values greater than 34 are reserved.
648
649 A point within the region of uncertainty is selected to be the
650 encoded point; the centroid of the region is often an appropriate
651 choice. The value for uncertainty is taken as the distance from the
652 selected point to the furthest extreme of the region of uncertainty
653 on that axis. This is demonstrated in the figure below, which shows
654 a two-dimensional polygon that is projected on each axis. In the
655 figure, "X" marks the point that is selected; the ranges marked with
656 "U" indicate the uncertainty.
657
658
659
660
661
662
663
664
665
666
667
668 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
671
672
673 ___ ___________
674 ^ | / |
675 | | / |
676 | | / |
677 U | / |
678 | | ( |
679 V | | |
680 --X | X |
681 | | `---------.
682 | | |
683 | | |
684 | | |
685 - `-------------------------'
686
687 |---------X---------------|
688 |&lt;------U------&gt;|
689
690 Key
691 ---
692
693 V, ^ = vertical arrows, delimiting the vertical uncertainty range.
694 &lt;&gt; = horizontal arrows, delimiting the horizontal uncertainty
695 range.
696
697 Uncertainty applies to each axis independently.
698
699 The amount of uncertainty can be determined from the encoding by
700 taking 2 to the power of 8, less the encoded value, as is shown in
701 the following formula, where "x" is the encoded integer value:
702
703 uncertainty = 2 ^ ( 8 - x )
704
705 The result of this formula is expressed in degrees of latitude or
706 longitude. The uncertainty is added to the base latitude or
707 longitude value to determine the maximum value in the uncertainty
708 range; similarly, the uncertainty is subtracted from the base value
709 to determine the minimum value. Note that because lines of longitude
710 converge at the poles, the actual distance represented by this
711 uncertainty changes with the distance from the equator.
712
713 If the maximum or minimum latitude values derived from applying
714 uncertainty are outside the range of -90 to +90, these values are
715 trimmed to within this range. If the maximum or minimum longitude
716 values derived from applying uncertainty are outside the range of
717 -180 to +180, then these values are normalized to this range by
718 adding or subtracting 360 as necessary.
719
720
721
722
723
724 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
727
728
729 The encoded value is determined by subtracting the next highest whole
730 integer value for the base 2 logarithm of uncertainty from 8, as is
731 shown by the following formula, where uncertainty is the midpoint of
732 the known range less the lower bound of that range:
733
734 x = 8 - ceil( log2( uncertainty ) )
735
736 Note that the result of encoding this value increases the range of
737 uncertainty to the next available power of two; subsequent repeated
738 encodings and decodings do not change the value. Only increasing
739 uncertainty means that the associated confidence does not have to
740 decrease.
741
742 <span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Altitude</span>
743
744 How the altitude value is interpreted depends on the Altitude Type
745 (AType) value and the selected datum. Three Altitude Type values are
746 defined in this document: unknown (0), meters (1), and floors (2).
747
748 <span class="h4"><a class="selflink" id="section-2.4.1" href="#section-2.4.1">2.4.1</a>. No Known Altitude (AType = 0)</span>
749
750 In some cases, the altitude of the location might not be provided.
751 An Altitude Type value of zero indicates that the altitude is not
752 given to the client. In this case, the Altitude and Altitude
753 Uncertainty fields can contain any value and MUST be ignored.
754
755 <span class="h4"><a class="selflink" id="section-2.4.2" href="#section-2.4.2">2.4.2</a>. Altitude in Meters (AType = 1)</span>
756
757 If the Altitude Type has a value of one, altitude is measured in
758 meters, in relation to the zero set by the vertical datum. For AType
759 = 1, the altitude value is expressed as a 30-bit, fixed-point, two's
760 complement integer with 22 integer bits and 8 fractional bits.
761
762 <span class="h4"><a class="selflink" id="section-2.4.3" href="#section-2.4.3">2.4.3</a>. Altitude in Floors (AType = 2)</span>
763
764 A value of two for Altitude Type indicates that the altitude value is
765 measured in floors. Since altitude in meters may not be known within
766 a building, a floor indication may be more useful. For AType = 2,
767 the altitude value is expressed as a 30-bit, fixed-point, two's
768 complement integer with 22 integer bits and 8 fractional bits.
769
770 This value is relevant only in relation to a building; the value is
771 relative to the ground level of the building. Floors located below
772 ground level are represented by negative values. In some buildings,
773 it might not be clear which floor is at ground level, or an
774 intermediate floor might be hard to identify as such. Determining
775
776
777
778
779
780 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
783
784
785 what floor is at ground level and what constitutes a sub-floor as
786 opposed to a naturally numbered floor is left to local
787 interpretation.
788
789 Larger values represent floors that are farther away from floor 0
790 such that:
791
792 - if positive, the floor value is farther above the ground floor.
793
794 - if negative, the floor value is farther below the ground floor.
795
796 Non-integer values can be used to represent intermediate or
797 sub-floors, such as mezzanine levels. Example: a mezzanine between
798 floor 1 and floor 2 could be represented as a value of 1.25.
799 Example: mezzanines between floor 4 and floor 5 could be represented
800 as values of 4.5 and 4.75.
801
802 <span class="h4"><a class="selflink" id="section-2.4.4" href="#section-2.4.4">2.4.4</a>. Altitude Resolution</span>
803
804 In the DHCPv4 GeoConf Option 123, the altitude resolution (AltRes)
805 value encodes the number of high-order altitude bits that should be
806 considered valid. Values above 30 (decimal) are undefined and
807 reserved.
808
809 If the Altitude Type value is one (AType = 1), an AltRes value of 0.0
810 would indicate an unknown altitude. The most precise altitude would
811 have an AltRes value of 30. Many values of AltRes would obscure any
812 variation due to vertical datum differences.
813
814 The AltRes field SHOULD be set to maximum precision when AType = 2
815 (floors) when a floor value is included in the DHCP Reply, or when
816 AType = 0, to denote that the floor isn't known. An altitude coded
817 as AType = 2, AltRes = 30, and Altitude = 0.0 is meaningful even
818 outside a building, and represents ground level at the given latitude
819 and longitude.
820
821 <span class="h4"><a class="selflink" id="section-2.4.5" href="#section-2.4.5">2.4.5</a>. Altitude Uncertainty</span>
822
823 In the DHCPv6 GeoLoc Option 63 or the DHCPv4 GeoLoc Option 144, the
824 AltUnc value quantifies the amount of uncertainty in the altitude
825 value. As with LatUnc and LongUnc, a value of 0 for AltUnc is
826 reserved to indicate that altitude uncertainty is not known; values
827 above 30 are also reserved. Altitude uncertainty only applies to
828 Altitude Type 1.
829
830
831
832
833
834
835
836 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
839
840
841 The amount of altitude uncertainty can be determined by the following
842 formula, where x is the encoded integer value:
843
844 Uncertainty = 2 ^ ( 21 - x )
845
846 This value uses the same units as the associated altitude.
847
848 Similarly, a value for the encoded integer value can be derived by
849 the following formula:
850
851 x = 21 - ceil( log2( uncertainty ) )
852
853 <span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Datum</span>
854
855 The Datum field determines how coordinates are organized and related
856 to the real world. Three datums are defined in this document, based
857 on the definitions in [<a href="#ref-OGP.Geodesy" title="Geomatics Committee">OGP.Geodesy</a>]:
858
859 1: WGS84 (Latitude, Longitude, Altitude): The World Geodetic System
860 1984 [<a href="#ref-WGS84" title="&quot;Department of Defense (DoD) World Geodetic System 1984 (WGS 84), Third Edition&quot;">WGS84</a>] coordinate reference system.
861
862 This datum is identified by the European Petroleum Survey Group
863 (EPSG)/International Association of Oil &amp; Gas Producers (OGP) with
864 the code 4979, or by the URN "urn:ogc:def:crs:EPSG::4979".
865 Without altitude, this datum is identified by the EPSG/OGP code
866 4326 and the URN "urn:ogc:def:crs:EPSG::4326".
867
868 2: NAD83 (Latitude, Longitude) + NAVD88: This datum uses a
869 combination of the North American Datum 1983 (NAD83) for
870 horizontal (Latitude and Longitude) values, plus the North
871 American Vertical Datum of 1988 (NAVD88) vertical datum.
872
873 This datum is used for referencing location on land (not near
874 tidal water) within North America.
875
876 NAD83 is identified by the EPSG/OGP code of 4269, or the URN
877 "urn:ogc:def:crs:EPSG::4269". NAVD88 is identified by the EPSG/
878 OGP code of 5703, or the URN "urn:ogc:def:crs:EPSG::5703".
879
880 3: NAD83 (Latitude, Longitude) + MLLW: This datum uses a combination
881 of the North American Datum 1983 (NAD83) for horizontal (Latitude
882 and Longitude) values, plus the Mean Lower Low Water (MLLW)
883 vertical datum.
884
885 This datum is used for referencing location on or near tidal water
886 within North America.
887
888
889
890
891
892 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
895
896
897 NAD83 is identified by the EPSG/OGP code of 4269, or the URN
898 "urn:ogc:def:crs:EPSG::4269". MLLW does not have a specific code
899 or URN.
900
901 All hosts MUST support the WGS84 datum (Datum 1).
902
903 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
904
905 Geopriv requirements (including security requirements) are discussed
906 in "Geopriv Requirements" [<a href="./rfc3693" title="&quot;Geopriv Requirements&quot;">RFC3693</a>]. A threat analysis is provided
907 in "Threat Analysis of the Geopriv Protocol" [<a href="./rfc3694" title="&quot;Threat Analysis of the Geopriv Protocol&quot;">RFC3694</a>].
908
909 Since there is no privacy protection for DHCP messages, an
910 eavesdropper who can monitor the link between the DHCP server and
911 requesting client can discover this LCI.
912
913 To minimize the unintended exposure of location information, the LCI
914 option SHOULD be returned by DHCP servers only when the DHCP client
915 has included this option in its 'parameter request list' (<a href="./rfc2131#section-3.5">Section&nbsp;3.5
916 of [RFC2131]</a>, <a href="./rfc2132#section-9.8">Section&nbsp;9.8 of [RFC2132]</a>).
917
918 Where critical decisions might be based on the value of this option,
919 DHCP authentication as defined in "Authentication for DHCP Messages"
920 [<a href="./rfc3118" title="&quot;Authentication for DHCP Messages&quot;">RFC3118</a>] and "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"
921 [<a href="./rfc3315" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3315</a>] SHOULD be used to protect the integrity of the DHCP
922 options.
923
924 Link-layer confidentiality and integrity protection may also be
925 employed to reduce the risk of location disclosure and tampering.
926
927 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
928
929 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. DHCP Options</span>
930
931 This document defines the DHCPv6 GeoLoc Option (see <a href="#section-2.1">Section 2.1</a>),
932 which has been assigned a DHCPv6 option code of 63 per [<a href="./rfc3315" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">RFC3315</a>]:
933
934 Value Description Reference
935 ---- ------------------ ----------
936 63 OPTION_GEOLOCATION <a href="./rfc6225">RFC 6225</a>
937
938 This document defines the DHCPv4 GeoConf Option (see <a href="#section-2.2.1">Section 2.2.1</a>),
939 which has been assigned a DHCPv4 option code of 123 from the DHCP
940 Option space.
941
942
943
944
945
946
947
948 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
951
952
953 This document also defines the DHCPv4 GeoLoc Option (see
954 <a href="#section-2.2.2">Section 2.2.2</a>), which has been assigned a DHCPv4 option code of 144
955 per [<a href="./rfc2132" title="&quot;DHCP Options and BOOTP Vendor Extensions&quot;">RFC2132</a>] [<a href="./rfc2939" title="&quot;Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types&quot;">RFC2939</a>]:
956
957 Data
958 Tag Name Length Meaning Reference
959 ---- ---- ------ ------- ---------
960 144 GeoLoc 16 Geospatial Location <a href="./rfc6225">RFC 6225</a>
961 with Uncertainty
962
963 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Altitude Type Registry</span>
964
965 IANA has created and now maintains the Altitude Type registry
966 following the guidelines below.
967
968 The registry consists of three values: Altitude Type, Description,
969 and Reference. These are described below.
970
971 Altitude Type: An integer, refers to the value used in the DHCPv4
972 GeoConf and the DHCPv4 and DHCPv6 GeoLoc options described in this
973 document. Values 0 - 2 are assigned. Values 3 - 15 are
974 Unassigned [<a href="./rfc5226" title="">RFC5226</a>].
975
976 Description: The description of the altitude described by this code.
977
978 Reference: The reference to the document that describes the altitude
979 code. This reference MUST define the way that the 30-bit altitude
980 values and the associated 6-bit uncertainty are interpreted.
981
982 Initial values are given below; new assignments are to be made
983 following the "Standards Action" policies [<a href="./rfc5226" title="">RFC5226</a>].
984
985 +------+---------------------+--------------+
986 | # | Description | Reference |
987 +------+---------------------+--------------+
988 | 0 | No known altitude | <a href="./rfc6225">RFC 6225</a> |
989 | 1 | Altitude in meters | <a href="./rfc6225">RFC 6225</a> |
990 | 2 | Altitude in floors | <a href="./rfc6225">RFC 6225</a> |
991 | 3-15 | Unassigned | |
992 +------+---------------------+--------------+
993
994 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Datum Registry</span>
995
996 IANA has created and now maintains the Datum registry following the
997 guidelines below.
998
999 The registry consists of three values: Datum, Description, and
1000 Reference. These are described below.
1001
1002
1003
1004 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
1007
1008
1009 Datum: An integer, refers to the value used in the DHCPv4 GeoConf and
1010 the DHCPv4 and DHCPv6 GeoLoc options described in this document.
1011 Value 0 is Reserved. Values 1 - 3 are assigned. Values 4 - 7 are
1012 Unassigned [<a href="./rfc5226" title="">RFC5226</a>].
1013
1014 Description: The description of the altitude described by this code.
1015
1016 Reference: The reference to the document that describes the Datum
1017 code. This reference MUST include specification of both the
1018 horizontal and vertical datum, and MUST define the way that the
1019 34-bit values and the respective 6-bit uncertainties are
1020 interpreted.
1021
1022 Initial values are given below; new assignments are to be made
1023 following the "Standards Action" policies [<a href="./rfc5226" title="">RFC5226</a>].
1024
1025 +------+----------------------------------------+--------------+
1026 | # | Description | Reference |
1027 +------+----------------------------------------+--------------+
1028 | 0 | Reserved | <a href="./rfc6225">RFC 6225</a> |
1029 +------+----------------------------------------+--------------+
1030 | 1 | Vertical datum WGS 84 defined by EPSG | <a href="./rfc6225">RFC 6225</a> |
1031 | | CRS Code 4327 | |
1032 +------+----------------------------------------+--------------+
1033 | 2 | Vertical datum NAD83 defined by EPSG | <a href="./rfc6225">RFC 6225</a> |
1034 | | CRS Code 4269 with North American | |
1035 | | Vertical Datum of 1988 (NAVD88) | |
1036 +------+----------------------------------------+--------------+
1037 | 3 | Vertical datum NAD83 defined by EPSG | <a href="./rfc6225">RFC 6225</a> |
1038 | | CRS Code 4269 with Mean Lower Low Water| |
1039 | | (MLLW) as associated vertical datum | |
1040 +------+----------------------------------------+--------------+
1041 | 4-7 | Unassigned | |
1042 +------+----------------------------------------+--------------+
1043
1044 <span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. GeoLoc Option Version Registry</span>
1045
1046 IANA has created and now maintains the GeoLoc Option Version registry
1047 following the guidelines below.
1048
1049 The registry consists of three values: GeoLoc Option Version,
1050 Description, and Reference. These are described below.
1051
1052 GeoLoc Option Version: An integer; refers to the version used in the
1053 DHCPv4 and DHCPv6 GeoLoc options described in this document.
1054 Value 0 is Reserved. Value 1 has been assigned. Values 2 - 3 are
1055 Unassigned [<a href="./rfc5226" title="">RFC5226</a>].
1056
1057
1058
1059
1060 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
1063
1064
1065 Description: The description of the version described by this code.
1066
1067 Reference: The reference to the document that describes the Version
1068 code.
1069
1070 Initial values are given below; new assignments are to be made
1071 following the "Standards Action" policies [<a href="./rfc5226" title="">RFC5226</a>].
1072
1073 +------+---------------------------------------+--------------+
1074 | # | Description | Reference |
1075 +------+---------------------------------------+--------------+
1076 | 0 | Reserved | <a href="./rfc6225">RFC 6225</a> |
1077 +------+---------------------------------------+--------------+
1078 | 1 | Implementations utilizing uncertainty | <a href="./rfc6225">RFC 6225</a> |
1079 | | parameters for both DHCPv4 and DHCPv6 | |
1080 | | GeoLoc options | |
1081 +------+---------------------------------------+--------------+
1082 | 2-3 | Unassigned | |
1083 +------+---------------------------------------+--------------+
1084
1085 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgments</span>
1086
1087 The authors would like to thank Randall Gellens, Patrik Falstrom,
1088 Ralph Droms, Ted Hardie, Jon Peterson, Robert Sparks, Nadine Abbott,
1089 and Mykyta Yevstifeyev for their inputs and constructive comments
1090 regarding this document. Additionally, the authors would like to
1091 thank Greg Troxel for the education on vertical datums, as well as
1092 Carl Reed. Thanks to Richard Barnes for his contribution on GML
1093 mapping for resolution.
1094
1095 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
1096
1097 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
1098
1099 [<a id="ref-EPSG">EPSG</a>] European Petroleum Survey Group,
1100 &lt;<a href="http://www.epsg.org/">http://www.epsg.org/</a>&gt; and
1101 &lt;<a href="http://www.epsg-registry.org/">http://www.epsg-registry.org/</a>&gt;.
1102
1103 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
1104 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
1105
1106 [<a id="ref-RFC2131">RFC2131</a>] Droms, R., "Dynamic Host Configuration Protocol",
1107 <a href="./rfc2131">RFC 2131</a>, March 1997.
1108
1109 [<a id="ref-RFC2132">RFC2132</a>] Alexander, S. and R. Droms, "DHCP Options and BOOTP
1110 Vendor Extensions", <a href="./rfc2132">RFC 2132</a>, March 1997.
1111
1112
1113
1114
1115
1116 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
1119
1120
1121 [<a id="ref-RFC2939">RFC2939</a>] Droms, R., "Procedures and IANA Guidelines for
1122 Definition of New DHCP Options and Message Types",
1123 <a href="https://www.rfc-editor.org/bcp/bcp43">BCP 43</a>, <a href="./rfc2939">RFC 2939</a>, September 2000.
1124
1125 [<a id="ref-RFC3118">RFC3118</a>] Droms, R., Ed., and W. Arbaugh, Ed., "Authentication
1126 for DHCP Messages", <a href="./rfc3118">RFC 3118</a>, June 2001.
1127
1128 [<a id="ref-RFC3315">RFC3315</a>] Droms, R., Ed., Bound, J., Volz, B., Lemon, T.,
1129 Perkins, C., and M. Carney, "Dynamic Host
1130 Configuration Protocol for IPv6 (DHCPv6)", <a href="./rfc3315">RFC 3315</a>,
1131 July 2003.
1132
1133 [<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing
1134 an IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC</a>
1135 <a href="./rfc5226">5226</a>, May 2008.
1136
1137 [<a id="ref-WGS84">WGS84</a>] US National Imagery and Mapping Agency, "Department of
1138 Defense (DoD) World Geodetic System 1984 (WGS 84),
1139 Third Edition", NIMA TR8350.2, January 2000,
1140 &lt;<a href="https://www1.nga.mil/PRODUCTSSERVICES/GEODESYGEOPHYSICS/WORLDGEODETICSYSTEM/Pages/default.aspx">https://www1.nga.mil/PRODUCTSSERVICES/</a>
1141 <a href="https://www1.nga.mil/PRODUCTSSERVICES/GEODESYGEOPHYSICS/WORLDGEODETICSYSTEM/Pages/default.aspx">GEODESYGEOPHYSICS/WORLDGEODETICSYSTEM/</a>
1142 <a href="https://www1.nga.mil/PRODUCTSSERVICES/GEODESYGEOPHYSICS/WORLDGEODETICSYSTEM/Pages/default.aspx">Pages/default.aspx</a>&gt; and
1143 &lt;<a href="http://www.ngs.noaa.gov/faq.shtml#WGS84">http://www.ngs.noaa.gov/faq.shtml#WGS84</a>&gt;.
1144
1145 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
1146
1147 [<a id="ref-Convey">Convey</a>] Polk, J., Rosen, B., and J. Peterson, "Location
1148 Conveyance for the Session Initiation Protocol", Work
1149 in Progress, May 2011.
1150
1151 [<a id="ref-GeoShape">GeoShape</a>] Thomson, M. and C. Reed, "GML 3.1.1 PIDF-LO Shape
1152 Application Schema for use by the Internet Engineering
1153 Task Force (IETF)", Candidate OpenGIS Implementation
1154 Specification 06-142, Version: 0.0.9, December 2006.
1155
1156 [<a id="ref-IEEE-802.11y">IEEE-802.11y</a>] IEEE Standard for Information technology -
1157 Telecommunications and information exchange between
1158 systems - Local and metropolitan area networks -
1159 Specific requirements - Part 11: Wireless LAN Medium
1160 Access Control (MAC) and Physical Layer (PHY)
1161 specifications Amendment 3: 3650-3700 MHz Operation in
1162 USA, November 2008.
1163
1164 [<a id="ref-NENA">NENA</a>] National Emergency Number Association (NENA), NENA
1165 Technical Information Document on Model Legislation
1166 Enhanced 911 for Multi-Line Telephone Systems,
1167 &lt;www.nena.org&gt;.
1168
1169
1170
1171
1172 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
1175
1176
1177 [<a id="ref-OGC-GML3.1.1">OGC-GML3.1.1</a>] Portele, C., Cox, S., Daisy, P., Lake, R., and A.
1178 Whiteside, "Geography Markup Language (GML) 3.1.1",
1179 OGC 03-105r1, July 2003.
1180
1181 [<a id="ref-OGP.Geodesy">OGP.Geodesy</a>] International Association of Oil &amp; Gas Producers (OGP)
1182 Geodesy Resources, Geomatics Committee,
1183 &lt;<a href="http://info.ogp.org.uk/geodesy/">http://info.ogp.org.uk/geodesy/</a>&gt;.
1184
1185 [<a id="ref-RFC3046">RFC3046</a>] Patrick, M., "DHCP Relay Agent Information Option",
1186 <a href="./rfc3046">RFC 3046</a>, January 2001.
1187
1188 [<a id="ref-RFC3693">RFC3693</a>] Cuellar, J., Morris, J., Mulligan, D., Peterson, J.,
1189 and J. Polk, "Geopriv Requirements", <a href="./rfc3693">RFC 3693</a>,
1190 February 2004.
1191
1192 [<a id="ref-RFC3694">RFC3694</a>] Danley, M., Mulligan, D., Morris, J., and J. Peterson,
1193 "Threat Analysis of the Geopriv Protocol", <a href="./rfc3694">RFC 3694</a>,
1194 February 2004.
1195
1196 [<a id="ref-RFC3825">RFC3825</a>] Polk, J., Schnizlein, J., and M. Linsner, "Dynamic
1197 Host Configuration Protocol Option for Coordinate-
1198 based Location Configuration Information", <a href="./rfc3825">RFC 3825</a>,
1199 July 2004.
1200
1201 [<a id="ref-RFC4119">RFC4119</a>] Peterson, J., "A Presence-based GEOPRIV Location
1202 Object Format", <a href="./rfc4119">RFC 4119</a>, December 2005.
1203
1204 [<a id="ref-RFC4776">RFC4776</a>] Schulzrinne, H., "Dynamic Host Configuration Protocol
1205 (DHCPv4 and DHCPv6) Option for Civic Addresses
1206 Configuration Information", <a href="./rfc4776">RFC 4776</a>, November 2006.
1207
1208 [<a id="ref-RFC5139">RFC5139</a>] Thomson, M. and J. Winterbottom, "Revised Civic
1209 Location Format for Presence Information Data Format
1210 Location Object (PIDF-LO)", <a href="./rfc5139">RFC 5139</a>, February 2008.
1211
1212 [<a id="ref-RFC5491">RFC5491</a>] Winterbottom, J., Thomson, M., and H. Tschofenig,
1213 "GEOPRIV Presence Information Data Format Location
1214 Object (PIDF-LO) Usage Clarification, Considerations,
1215 and Recommendations", <a href="./rfc5491">RFC 5491</a>, March 2009.
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
1231
1232
1233 <span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. GML Mapping</span>
1234
1235 The GML representation of a decoded DHCP option depends on what
1236 fields are specified. The DHCP format for location logically
1237 describes a geodetic prism, rectangle, or point, depending on whether
1238 altitude and uncertainty values are provided. In the absence of
1239 uncertainty information, the value decoded from the DHCP form can be
1240 expressed as a single point; this is true regardless of whether the
1241 version 0 or version 1 interpretations of the uncertainty fields are
1242 used. If the point includes altitude, it uses a three-dimensional
1243 Coordinate Reference System (CRS); otherwise, it uses a two-
1244 dimensional CRS. If all fields are included along with uncertainty,
1245 the shape described is a rectangular prism. Note that this is
1246 necessary given that uncertainty for each axis is provided
1247 independently.
1248
1249 If altitude or altitude uncertainty (AltUnc) is not specified, the
1250 shape is described as a rectangle using the "gml:Polygon" shape. If
1251 altitude is available, a three-dimensional CRS is used; otherwise, a
1252 two-dimensional CRS is used.
1253
1254 For Datum values of 2 or 3 (NAD83), there is no available CRS URN
1255 that covers three-dimensional coordinates. By necessity, locations
1256 described in these datums can be represented by two-dimensional
1257 shapes only; that is, either a two-dimensional point or a polygon.
1258
1259 If the Altitude Type is 2 (floors), then this value can be
1260 represented using a civic address object [<a href="./rfc5139" title="&quot;Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)&quot;">RFC5139</a>] that is presented
1261 alongside the geodetic object.
1262
1263 This Appendix describes how the location value encoded in DHCP format
1264 for geodetic location can be expressed in GML. The mapping is valid
1265 for the DHCPv6 GeoLoc Option as well as both of the DHCPv4 GeoConf
1266 and GeoLoc options, and for the currently defined datum values (1, 2,
1267 and 3). Further version or datum definitions should provide similar
1268 mappings.
1269
1270 These shapes can be mapped to GML by first computing the bounds that
1271 are described using the coordinate and uncertainty fields, then
1272 encoding the result in a GML Polygon or Prism shape.
1273
1274 <span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>. GML Templates</span>
1275
1276 If altitude is provided in meters (AType 1) and the datum value is
1277 WGS84 (value 1), then the proper GML shape is a Prism, with the
1278 following form (where $value$ indicates a value computed from the
1279 DHCP option as described below):
1280
1281
1282
1283
1284 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
1287
1288
1289 &lt;gs:Prism srsName="urn:ogc:def:crs:EPSG::4979"
1290 xmlns:gs="http://www.opengis.net/pidflo/1.0"
1291 xmlns:gml="http://www.opengis.net/gml"&gt;
1292 &lt;gs:base&gt;
1293 &lt;gml:Polygon&gt;
1294 &lt;gml:exterior&gt;
1295 &lt;gml:LinearRing&gt;
1296 &lt;gml:posList&gt;
1297 $lowLatitude$ $lowLongitude$ $lowAltitude$
1298 $lowLatitude$ $highLongitude$ $lowAltitude$
1299 $highLatitude$ $highLongitude$ $lowAltitude$
1300 $highLatitude$ $lowLongitude$ $lowAltitude$
1301 $lowLatitude$ $lowLongitude$ $lowAltitude$
1302 &lt;/gml:posList&gt;
1303 &lt;/gml:LinearRing&gt;
1304 &lt;/gml:exterior&gt;
1305 &lt;/gml:Polygon&gt;
1306 &lt;/gs:base&gt;
1307 &lt;gs:height uom="urn:ogc:def:uom:EPSG::9001"&gt;
1308 $highAltitude - lowAltitude$
1309 &lt;/gs:height&gt;
1310 &lt;/gs:Prism&gt;
1311
1312 The Polygon shape is used if altitude is omitted or specified in
1313 floors, or if either NAD83 datum is used (value 2 or 3). The
1314 corresponding GML Polygon has the following form:
1315
1316 &lt;gml:Polygon srsName="$2D-CRS-URN$"
1317 xmlns:gml="http://www.opengis.net/gml"&gt;&gt;
1318 &lt;gml:exterior&gt;
1319 &lt;gml:LinearRing&gt;
1320 &lt;gml:posList&gt;
1321 $lowLatitude$ $lowLongitude$
1322 $lowLatitude$ $highLongitude$
1323 $highLatitude$ $highLongitude$
1324 $highLatitude$ $lowLongitude$
1325 $lowLatitude$ $lowLongitude$
1326 &lt;/gml:posList&gt;
1327 &lt;/gml:LinearRing&gt;
1328 &lt;/gml:exterior&gt;
1329 &lt;/gml:Polygon&gt;
1330
1331 The value "2D-CRS-URN" is defined by the datum value: If the datum is
1332 WGS84 (value 1), then the 2D-CRS-URN is "urn:ogc:def:crs:EPSG::4326".
1333 If the datum is NAD83 (value 2 or 3), then the 2D-CRS-URN is
1334 "urn:ogc:def:crs:EPSG::4269".
1335
1336
1337
1338
1339
1340 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
1343
1344
1345 A Polygon shape with the WGS84 three-dimensional CRS is used if the
1346 datum is WGS84 (value 1) and the altitude is specified in meters
1347 (Altitude Type 1), but no altitude uncertainty is specified (that is,
1348 AltUnc is 0). In this case, the value of the Altitude field is added
1349 after each of the points above, and the srsName attribute is set to
1350 the three-dimensional WGS84 CRS, namely "urn:ogc:def:crs:EPSG::4979".
1351
1352 A simple point shape is used if either latitude uncertainty (LatUnc)
1353 or longitude uncertainty (LongUnc) is not specified. With altitude,
1354 this uses a three-dimensional CRS; otherwise, it uses a two-
1355 dimensional CRS.
1356
1357 &lt;gml:Point srsName="$CRS-URN$"
1358 xmlns:gml="http://www.opengis.net/gml"&gt;
1359 &lt;gml:pos&gt;$Latitude$ $Longitude$ $[Altitude]$&lt;/gml:pos&gt;
1360 &lt;/gml:Point&gt;
1361
1362 <span class="h4"><a class="selflink" id="appendix-A.1.1" href="#appendix-A.1.1">A.1.1</a>. Finding Low and High Values Using Uncertainty Fields</span>
1363
1364 For the DHCPv4 GeoConf Option 123, resolution fields are used (LaRes,
1365 LoRes, AltRes), indicating how many bits of a value contain
1366 information. Any bits beyond those indicated can be either zero or
1367 one.
1368
1369 For the DHCPv6 GeoLoc Option 63 and DHCPv4 GeoLoc Option 144, the
1370 LatUnc, LongUnc, and AltUnc fields indicate uncertainty distances,
1371 denoting the bounds of the location region described by the DHCP
1372 location object.
1373
1374 The two sections below describe how to compute the latitude,
1375 longitude, and altitude bounds (e.g., $lowLatitude$, $highAltitude$)
1376 in the templates above. The first section describes how these bounds
1377 are computed in the "resolution encoding" (DHCPv4 GeoConf
1378 Option 123), while the second section addresses the "uncertainty
1379 encoding" (DHCPv6 GeoLoc Option 63 and DHCPv4 GeoLoc Option 144).
1380
1381 <span class="h5"><a class="selflink" id="appendix-A.1.1.1" href="#appendix-A.1.1.1">A.1.1.1</a>. Resolution Encoding</span>
1382
1383 Given a number of resolution bits (i.e., the value of a resolution
1384 field), if all bits beyond those bits are set to zero, this gives the
1385 lowest possible value. The highest possible value can be found
1386 setting all bits to one.
1387
1388 If the encoded value of latitude/longitude and resolution (LaRes,
1389 LoRes) are treated as 34-bit unsigned integers, the following can be
1390 used (where "&gt;&gt;" is a bitwise right shift, "&amp;" is a bitwise AND, "~"
1391 is a bitwise negation, and "|" is a bitwise OR).
1392
1393
1394
1395
1396 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
1399
1400
1401 mask = 0x3ffffffff &gt;&gt; resolution
1402 lowvalue = value &amp; ~mask
1403 highvalue = value | mask + 1
1404
1405 Once these values are determined, the corresponding floating-point
1406 numbers can be computed by dividing the values by 2^25 (since there
1407 are 25 bits of fraction in the fixed-point representation).
1408
1409 Alternatively, the lowest possible value can be found by using
1410 resolution to determine the size of the range. This method has the
1411 advantage that it operates on the decoded floating-point values. It
1412 is equivalent to the first mechanism, to a possible error of 2^-25
1413 (2^-8 for altitude).
1414
1415 scale = 2 ^ ( 9 - resolution )
1416 lowvalue = floor( value / scale ) * scale
1417 highvalue = lowvalue + scale
1418
1419 Altitude resolution (AltRes) uses the same process with different
1420 constants. There are 22 whole bits in the altitude encoding (instead
1421 of 9) and 30 bits in total (instead of 34).
1422
1423 <span class="h5"><a class="selflink" id="appendix-A.1.1.2" href="#appendix-A.1.1.2">A.1.1.2</a>. Uncertainty Encoding</span>
1424
1425 In the uncertainty encoding, the uncertainty fields (LongUnc/LatUnc)
1426 directly represent the logarithms of uncertainty distances. So the
1427 low and high bounds are computed by first computing the uncertainty
1428 distances, then adding and subtracting these from the value provided.
1429 If "uncertainty" is the unsigned integer value of the uncertainty
1430 field and "value" is the value of the coordinate field:
1431
1432 distance = 2 ^ (8 - uncertainty)
1433 lowvalue = value - distance
1434 highvalue = value + distance
1435
1436 Altitude uncertainty (AltUnc in version 1) uses the same process with
1437 different constants:
1438
1439 distance = 2 ^ (21 - uncertainty)
1440 lowvalue = value - distance
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
1455
1456
1457 <span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. Calculations of Resolution</span>
1458
1459 The following examples for two different locations demonstrate how
1460 the resolution values for latitude, longitude, and altitude (used in
1461 DHCPv4 GeoConf Option 123) can be calculated. In both examples, the
1462 geo-location values were derived from maps using the WGS84 map datum;
1463 therefore, in these examples, the Datum field would have a value = 1
1464 (00000001, or 0x01).
1465
1466 <span class="h3"><a class="selflink" id="appendix-B.1" href="#appendix-B.1">B.1</a>. Location Configuration Information of "White House" (Example 1)</span>
1467
1468 The grounds of the White House in Washington D.C. (1600 Pennsylvania
1469 Ave. NW, Washington, DC 20006) can be found between 38.895375 and
1470 38.898653 degrees North and 77.037911 and 77.035116 degrees West. In
1471 this example, we assume that we are standing on the sidewalk on the
1472 north side of the White House, between driveways. Since we are not
1473 inside a structure, we assume an altitude value of 15 meters,
1474 interpolated from the US Geological survey map, Washington,
1475 Washington West quadrangle.
1476
1477 The address was NOT picked for any political reason and can easily be
1478 found on the Internet or mapping software, but was picked as an
1479 easily identifiable location on our planet.
1480
1481 In this example, the requirement of emergency responders in North
1482 America via their National Emergency Number Association (NENA) Model
1483 Legislation [<a href="#ref-NENA" title="NENA Technical Information Document on Model Legislation Enhanced 911 for Multi-Line Telephone Systems">NENA</a>] could be met by a LaRes value of 21 and a LoRes
1484 value of 20. This would yield a geo-location that is latitude
1485 38.8984375 north to latitude 38.8988616 north and longitude
1486 -77.0371094 to longitude -77.0375977. This is an area of
1487 approximately 89 feet by 75 feet or 6669 square feet, which is very
1488 close to the 7000 square feet requested by NENA. In this example, a
1489 service provider could enforce that a device send location
1490 configuration information with this minimum amount of resolution for
1491 this particular location when calling emergency services.
1492
1493 An approximate representation of this location might be provided
1494 using the DHCPv4 GeoConf Option 123 encoding as follows:
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
1511
1512
1513 0 1 2 3
1514 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
1515 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1516 | Code (123) | OptLen (16) | LaRes | Latitude .
1517 |0 1 1 1 1 0 1 1|0 0 0 1 0 0 0 0|0 1 0 0 1 0|0 0 0 1 0 0 1 1 0 1.
1518 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1519 . Latitude (cont'd) | LoRes | .
1520 .1 1 0 0 1 0 1 1 1 0 0 1 1 0 0 0 0 1 1 0 0 0 1 1|0 1 0 0 0 1|1 1.
1521 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1522 . Longitude (cont'd) |
1523 .0 1 1 0 0 1 0 1 1 1 1 0 1 1 0 1 0 1 0 0 0 0 1 0 1 1 0 0 0 1 0 0|
1524 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1525 | AType | AltRes | Altitude .
1526 |0 0 0 1|0 1 0 0 0 1|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1.
1527 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1528 . Alt (cont'd) | Res |Datum|
1529 .0 0 0 0 0 0 0 0|0 0 0 0 0|0 0 1|
1530 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1531
1532 In hexadecimal, this is 7B10484D CB986347 65ED42C4 1440000F 0001.
1533
1534 <span class="h4"><a class="selflink" id="appendix-B.1.1" href="#appendix-B.1.1">B.1.1</a>. Decoding Location Configuration Information with Resolution</span>
1535
1536 Decoding this option gives a latitude of 38.897647 (to 7 decimal
1537 places) with 18 bits of resolution, a longitude of -77.0366000 with
1538 17 bits of resolution, an Altitude Type of meters with a value of 15
1539 and 17 bits of resolution, version 0 (resolution), and the WGS84
1540 datum.
1541
1542 For the latitude value, 18 bits of resolution allow for values in the
1543 range from 38.8964844 to 38.8984375. For the longitude value, 17
1544 bits of resolution allow for values in the range from -77.0390625 to
1545 -77.0351563. Having 17 bits of resolution in the altitude allows for
1546 values in the range from 0 to 32 meters.
1547
1548 <span class="h4"><a class="selflink" id="appendix-B.1.2" href="#appendix-B.1.2">B.1.2</a>. GML Representation of Decoded Location Configuration Information</span>
1549
1550 The following GML shows the value decoded in the previous example as
1551 a point in a three-dimensional CRS:
1552
1553 &lt;gml:Point srsName="urn:ogc:def:crs:EPSG::4979"
1554 xmlns:gml="http://www.opengis.net/gml"&gt;
1555 &lt;gml:pos&gt;38.897647 -77.0366 15&lt;/gml:pos&gt;
1556 &lt;/gml:Point&gt;
1557
1558 This representation ignores the values included in the resolution
1559 parameters. If resolution values are provided, a rectangular prism
1560 can be used to represent the location.
1561
1562
1563
1564 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
1567
1568
1569 The following example uses all of the decoded information from the
1570 previous example:
1571
1572 &lt;gs:Prism srsName="urn:ogc:def:crs:EPSG::4979"
1573 xmlns:gs="http://www.opengis.net/pidflo/1.0"
1574 xmlns:gml="http://www.opengis.net/gml"&gt;
1575 &lt;gs:base&gt;
1576 &lt;gml:Polygon&gt;
1577 &lt;gml:exterior&gt;
1578 &lt;gml:LinearRing&gt;
1579 &lt;gml:posList&gt;
1580 38.8964844 -77.0390625 0
1581 38.8964844 -77.0351563 0
1582 38.8984375 -77.0351563 0
1583 38.8984375 -77.0390625 0
1584 38.8964844 -77.0390625 0
1585 &lt;/gml:posList&gt;
1586 &lt;/gml:LinearRing&gt;
1587 &lt;/gml:exterior&gt;
1588 &lt;/gml:Polygon&gt;
1589 &lt;/gs:base&gt;
1590 &lt;gs:height uom="urn:ogc:def:uom:EPSG::9001"&gt;
1591 32
1592 &lt;/gs:height&gt;
1593 &lt;/gs:Prism&gt;
1594
1595 <span class="h3"><a class="selflink" id="appendix-B.2" href="#appendix-B.2">B.2</a>. Location Configuration Information of "Sears Tower" (Example 2)</span>
1596
1597 Postal Address:
1598 Sears Tower
1599 103rd Floor
1600 233 S. Wacker Dr.
1601 Chicago, IL 60606
1602
1603 Viewing the Chicago area from the Observation Deck of the Sears
1604 Tower:
1605
1606 Latitude 41.87884 degrees North (or +41.87884 degrees)
1607 Using two's complement, 34-bit fixed point, 25 bits of fraction
1608 Latitude = 0x053c1f751,
1609 Latitude = 0001010011110000011111011101010001
1610 Longitude 87.63602 degrees West (or -87.63602 degrees)
1611 Using two's complement, 34-bit fixed point, 25 bits of fraction
1612 Longitude = 0xf50ba5b97,
1613 Longitude = 1101010000101110100101101110010111
1614
1615 Altitude 103
1616
1617
1618
1619
1620 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
1623
1624
1625 In this example, we are inside a structure; therefore, we will assume
1626 an altitude value of 103 to indicate the floor we are on. The
1627 Altitude Type value is 2, indicating floors. The AltRes field would
1628 indicate that all bits in the Altitude field are true, as we want to
1629 accurately represent the floor of the structure where we are located.
1630
1631 AltRes = 30, 0x1e, 011110
1632 AType = 2, 0x02, 000010
1633 Altitude = 103, 0x00006700, 000000000000000110011100000000
1634
1635 For the accuracy of the latitude and longitude, the best information
1636 available to us was supplied by a generic mapping service that shows
1637 a single geo-loc for all of the Sears Tower. Therefore, we are going
1638 to show LaRes as value 18 (0x12 or 010010) and LoRes as value 18
1639 (0x12 or 010010). This would be describing a geo-location area that
1640 is latitude 41.8769531 to latitude 41.8789062 and extends from
1641 -87.6367188 degrees to -87.6347657 degrees longitude. This is an
1642 area of approximately 373412 square feet (713.3 ft. x 523.5 ft.).
1643
1644 <span class="h2"><a class="selflink" id="appendix-C" href="#appendix-C">Appendix C</a>. Calculations of Uncertainty</span>
1645
1646 The following example demonstrates how uncertainty values for
1647 latitude, longitude, and altitude (LatUnc, LongUnc, and AltUnc used
1648 in the DHCPv6 GeoLoc Option 63 as well as DHCPv4 GeoLoc Option 144)
1649 can be calculated.
1650
1651 <span class="h3"><a class="selflink" id="appendix-C.1" href="#appendix-C.1">C.1</a>. Location Configuration Information of "Sydney Opera House"</span>
1652 (Example 3)
1653
1654 This section describes an example of encoding and decoding the
1655 geodetic DHCP Option. The textual results are expressed in GML
1656 [<a href="#ref-OGC-GML3.1.1" title="&quot;Geography Markup Language (GML) 3.1.1&quot;">OGC-GML3.1.1</a>] form, suitable for inclusion in PIDF-LO [<a href="./rfc4119" title="&quot;A Presence-based GEOPRIV Location Object Format&quot;">RFC4119</a>].
1657
1658 These examples all assume a datum of WGS84 (datum = 1) and an
1659 Altitude Type of meters (AType = 1).
1660
1661 <span class="h4"><a class="selflink" id="appendix-C.1.1" href="#appendix-C.1.1">C.1.1</a>. Encoding a Location into DHCP Geodetic Form</span>
1662
1663 This example draws a rough polygon around the Sydney Opera House.
1664 This polygon consists of the following six points:
1665
1666 33.856625 S, 151.215906 E
1667 33.856299 S, 151.215343 E
1668 33.856326 S, 151.214731 E
1669 33.857533 S, 151.214495 E
1670 33.857720 S, 151.214613 E
1671 33.857369 S, 151.215375 E
1672
1673
1674
1675
1676 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
1679
1680
1681 The top of the building is 67.4 meters above sea level, and a
1682 starting altitude of 0 meters above the WGS84 geoid is assumed.
1683
1684 The first step is to determine the range of latitude and longitude
1685 values. Latitude ranges from -33.857720 to -33.856299; longitude
1686 ranges from 151.214495 to 151.215906.
1687
1688 For this example, the point that is encoded is chosen by finding the
1689 middle of each range, that is (-33.8570095, 151.2152005). This is
1690 encoded as (1110111100010010010011011000001101,
1691 0100101110011011100010111011000011) in binary, or (3BC49360D,
1692 12E6E2EC3) in hexadecimal notation (with an extra 2 bits of leading
1693 padding on each). Altitude is set at 33.7 meters, which is
1694 000000000000000010000110110011 (binary) or 000021B3 (hexadecimal).
1695
1696 The latitude uncertainty (LatUnc) is given by inserting the
1697 difference between the center value and the outer value into the
1698 formula from <a href="#section-2.3.2">Section 2.3.2</a>. This gives:
1699
1700 x = 8 - ceil( log2( -33.8570095 - -33.857720 ) )
1701
1702 The result of this equation is 18; therefore, the uncertainty is
1703 encoded as 010010 in binary.
1704
1705 Similarly, longitude uncertainty (LongUnc) is given by the formula:
1706
1707 x = 8 - ceil( log2( 151.2152005 - 151.214495 ) )
1708
1709 The result of this equation is also 18, or 010010 in binary.
1710
1711 Altitude uncertainty (AltUnc) uses the formula from <a href="#section-2.4.5">Section 2.4.5</a>:
1712
1713 x = 21 - ceil( log2( 33.7 - 0 ) )
1714
1715 The result of this equation is 15, which is encoded as 001111 in
1716 binary.
1717
1718 Adding an Altitude Type of 1 (meters) and a Datum of 1 (WGS84), this
1719 gives the following DHCPv4 GeoLoc Option 144 form:
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
1735
1736
1737 0 1 2 3
1738 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
1739 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1740 | Code (144) | OptLen (16) | LatUnc | Latitude .
1741 |0 1 1 1 1 0 1 1|0 0 0 1 0 0 0 0|0 1 0 0 1 0|1 1 1 0 1 1 1 1 0 0.
1742 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1743 . Latitude (cont'd) | LongUnc | .
1744 .0 1 0 0 1 0 0 1 0 0 1 1 0 1 1 0 0 0 0 0 1 1 0 1|0 1 0 0 1 0|0 1.
1745 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1746 . Longitude (cont'd) |
1747 .0 0 1 0 1 1 1 0 0 1 1 0 1 1 1 0 0 0 1 0 1 1 1 0 1 1 0 0 0 0 1 1|
1748 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1749 | AType | AltUnc | Altitude .
1750 |0 0 0 1|0 0 1 1 1 1|0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1.
1751 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1752 . Alt (cont'd) |Ver| Res |Datum|
1753 .1 0 1 1 0 0 1 1|0 1|0 0 0|0 0 1|
1754 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1755
1756 In hexadecimal, this is 7B104BBC 49360D49 2E6E2EC3 13C00021 B341.
1757 The DHCPv6 form only differs in the code and option length portion.
1758
1759 <span class="h4"><a class="selflink" id="appendix-C.1.2" href="#appendix-C.1.2">C.1.2</a>. Decoding a Location from DHCP Geodetic Form</span>
1760
1761 If receiving the binary form created in the previous section, this
1762 section describes how that would be interpreted. The result is then
1763 represented as a GML object, as defined in [<a href="#ref-GeoShape" title="&quot;GML 3.1.1 PIDF-LO Shape Application Schema for use by the Internet Engineering Task Force (IETF)&quot;">GeoShape</a>].
1764
1765 A latitude value of 1110111100010010010011011000001101 decodes to a
1766 value of -33.8570095003 (to 10 decimal places). The longitude value
1767 of 0100101110011011100010111011000011 decodes to 151.2152005136.
1768
1769 Decoding Tip: If the raw values of latitude and longitude are placed
1770 in integer variables, the actual value can be derived by the
1771 following process:
1772
1773 1. If the highest order bit is set (i.e., the number is a two's
1774 complement negative), then subtract 2 to the power of 34 (the
1775 total number of bits).
1776
1777 2. Divide the result by 2 to the power of 25 (the number of
1778 fractional bits) to determine the final value.
1779
1780 The same principle can be applied when decoding altitude values,
1781 except with different powers of 2 (30 and 8, respectively).
1782
1783
1784
1785
1786
1787
1788 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
1791
1792
1793 The latitude and longitude uncertainty are both 18, which gives an
1794 uncertainty value of 0.0009765625 using the formula from
1795 <a href="#section-2.3.2">Section 2.3.2</a>. Therefore, the decoded latitude is -33.8570095003 +/-
1796 0.0009765625 (or the range from -33.8579860628 to -33.8560329378) and
1797 the decoded longitude is 151.2152005136 +/- 0.0009765625 (or the
1798 range from 151.2142239511 to 151.2161770761).
1799
1800 The encoded altitude of 000000000000000010000110110011 decodes to
1801 33.69921875. The encoded uncertainty of 15 gives a value of 64;
1802 therefore, the final uncertainty is 33.69921875 +/- 64 (or the range
1803 from -30.30078125 to 97.69921875).
1804
1805 <span class="h5"><a class="selflink" id="appendix-C.1.2.1" href="#appendix-C.1.2.1">C.1.2.1</a>. GML Representation of Decoded Locations</span>
1806
1807 The following GML shows the value decoded in the previous example as
1808 a point in a three-dimensional CRS:
1809
1810 &lt;gml:Point srsName="urn:ogc:def:crs:EPSG::4979"
1811 xmlns:gml="http://www.opengis.net/gml"&gt;
1812 &lt;gml:pos&gt;-33.8570095003 151.2152005136 33.69921875&lt;/gml:pos&gt;
1813 &lt;/gml:Point&gt;
1814
1815 The following example uses all of the decoded information from the
1816 previous example:
1817
1818 &lt;gs:Prism srsName="urn:ogc:def:crs:EPSG::4979"
1819 xmlns:gs="http://www.opengis.net/pidflo/1.0"
1820 xmlns:gml="http://www.opengis.net/gml"&gt;
1821 &lt;gs:base&gt;
1822 &lt;gml:Polygon&gt;
1823 &lt;gml:exterior&gt;
1824 &lt;gml:LinearRing&gt;
1825 &lt;gml:posList&gt;
1826 -33.8579860628 151.2142239511 -30.30078125
1827 -33.8579860628 151.2161770761 -30.30078125
1828 -33.8560329378 151.2161770761 -30.30078125
1829 -33.8560329378 151.2142239511 -30.30078125
1830 -33.8579860628 151.2142239511 -30.30078125
1831 &lt;/gml:posList&gt;
1832 &lt;/gml:LinearRing&gt;
1833 &lt;/gml:exterior&gt;
1834 &lt;/gml:Polygon&gt;
1835 &lt;/gs:base&gt;
1836 &lt;gs:height uom="urn:ogc:def:uom:EPSG::9001"&gt;
1837 128
1838 &lt;/gs:height&gt;
1839 &lt;/gs:Prism&gt;
1840
1841
1842
1843
1844 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
1847
1848
1849 Note that this representation is only appropriate if the uncertainty
1850 is sufficiently small. [<a href="#ref-GeoShape" title="&quot;GML 3.1.1 PIDF-LO Shape Application Schema for use by the Internet Engineering Task Force (IETF)&quot;">GeoShape</a>] recommends that distances between
1851 polygon vertices be kept short. A GML representation like this one
1852 is only appropriate where uncertainty is less than 1 degree (an
1853 encoded value of 9 or greater).
1854
1855 <span class="h2"><a class="selflink" id="appendix-D" href="#appendix-D">Appendix D</a>. Changes from <a href="./rfc3825">RFC 3825</a></span>
1856
1857 This section lists the major changes between <a href="./rfc3825">RFC 3825</a> and this
1858 document. Minor changes, including style, grammar, spelling, and
1859 editorial changes, are not mentioned here.
1860
1861 o <a href="#section-1">Section 1</a> now includes clarifications on wired and wireless uses.
1862
1863 o The former Sections <a href="#section-1.2">1.2</a> and <a href="#section-1.3">1.3</a> have been removed. <a href="#section-1.2">Section 1.2</a>
1864 now defines the concepts of uncertainty and resolution, as well as
1865 conversion between the DHCP option formats and PIDF-LO.
1866
1867 o A DHCPv6 GeoLoc Option is now defined (<a href="#section-2.1">Section 2.1</a>) as well as a
1868 new DHCPv4 GeoLoc Option (<a href="#section-2.2.2">Section 2.2.2</a>).
1869
1870 o The former Datum field has been split into three fields: Ver, Res,
1871 and Datum. These fields are used in both the DHCPv4 GeoLoc Option
1872 and the DHCPv6 GeoLoc Option.
1873
1874 o <a href="#section-2.2.3">Section 2.2.3</a> has been added, describing option support
1875 requirements on DHCP clients and servers.
1876
1877 o <a href="#section-2.3">Section 2.3</a> has been added, describing the Latitude and Longitude
1878 fields.
1879
1880 o <a href="#section-2.3.1">Section 2.3.1</a> has been added, covering latitude and longitude
1881 resolution.
1882
1883 o <a href="#section-2.3.2">Section 2.3.2</a> has been added, covering latitude and longitude
1884 uncertainty.
1885
1886 o <a href="#section-2.4">Section 2.4</a> has been added, covering values of the Altitude field
1887 (Sections <a href="#section-2.4.1">2.4.1</a>, <a href="#section-2.4.2">2.4.2</a>, and <a href="#section-2.4.3">2.4.3</a>), altitude resolution
1888 (<a href="#section-2.4.4">Section 2.4.4</a>), and altitude uncertainty (<a href="#section-2.4.5">Section 2.4.5</a>).
1889
1890 o <a href="#section-2.5">Section 2.5</a> has been added, covering the Datum field.
1891
1892 o <a href="#section-3">Section 3</a> (Security Considerations) has added a recommendation on
1893 link-layer confidentiality.
1894
1895
1896
1897
1898
1899
1900 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
1903
1904
1905 o <a href="#section-4">Section 4</a> (IANA Considerations) has consolidated material relating
1906 to parameter allocation for both the DHCPv4 and DHCPv6 option
1907 parameters, and has been rewritten to conform to the practices
1908 recommended in <a href="./rfc5226">RFC 5226</a>.
1909
1910 o The material formerly in <a href="#appendix-A">Appendix A</a> has been updated and shortened
1911 and has been moved to <a href="#appendix-B">Appendix B</a>.
1912
1913 o An <a href="#appendix-A">Appendix A</a> on GML mapping has been added.
1914
1915 o <a href="#appendix-C">Appendix C</a> has been added, providing an example of uncertainty
1916 encoding.
1917
1918 o <a href="#appendix-D">Appendix D</a> has been added, detailing the changes from <a href="./rfc3825">RFC 3825</a>.
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956 <span class="grey">Polk, 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="./rfc6225">RFC 6225</a> DHCP Options for Coordinate LCI July 2011</span>
1959
1960
1961 Authors' Addresses
1962
1963 James M. Polk
1964 Cisco Systems
1965 2200 East President George Bush Turnpike
1966 Richardson, TX 75082
1967 USA
1968
1969 EMail: [email protected]
1970
1971
1972 Marc Linsner
1973 Cisco Systems
1974 Marco Island, FL 34145
1975 USA
1976
1977 EMail: [email protected]
1978
1979
1980 Martin Thomson
1981 Andrew Corporation
1982 PO Box U40
1983 Wollongong University Campus, NSW 2500
1984 AU
1985
1986 EMail: [email protected]
1987
1988
1989 Bernard Aboba (editor)
1990 Microsoft Corporation
1991 One Microsoft Way
1992 Redmond, WA 98052
1993 USA
1994
1995 EMail: [email protected]
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012 Polk, et al. Standards Track [Page 36]
2013 </pre>