draft-ietf-geopriv-rfc3825bis-04.txt   draft-ietf-geopriv-rfc3825bis-05.txt 
GEOPRIV Working Group J. Polk GEOPRIV Working Group J. Polk
INTERNET-DRAFT Cisco Systems INTERNET-DRAFT Cisco Systems
Obsoletes: 3825 (if approved) J. Schnizlein Obsoletes: 3825 (if approved) J. Schnizlein
Category: Standards Track ISOC Category: Standards Track Individual Contributor
Expires: June 21, 2010 M. Linsner Expires: July 28, 2010 M. Linsner
17 December 2009 Cisco Systems 14 January 2010 Cisco Systems
M. Thomson M. Thomson
Andrew Andrew
B. Aboba (ed) B. Aboba (ed)
Microsoft Corporation Microsoft Corporation
Dynamic Host Configuration Protocol Options for Dynamic Host Configuration Protocol Options for
Coordinate-based Location Configuration Information Coordinate-based Location Configuration Information
draft-ietf-geopriv-rfc3825bis-04.txt draft-ietf-geopriv-rfc3825bis-05.txt
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from IETF Standards Process. Without obtaining an adequate license from
skipping to change at page 1, line 50 skipping to change at page 1, line 50
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 21, 2010. This Internet-Draft will expire on July 28, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. and restrictions with respect to this document.
Abstract Abstract
skipping to change at page 2, line 35 skipping to change at page 2, line 35
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Conventions . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Resolution and Uncertainty . . . . . . . . . . . . . . . 4 1.2 Resolution and Uncertainty . . . . . . . . . . . . . . . 4
2. DHCP Option Format . . . . . . . . . . . . . . . . . . . . . . 4 2. DHCP Option Format . . . . . . . . . . . . . . . . . . . . . . 4
2.1 DHCPv6 Option . . . . . . . . . . . . . . . . . . . . . 5 2.1 DHCPv6 Option . . . . . . . . . . . . . . . . . . . . . 5
2.2 DHCPv4 Option . . . . . . . . . . . . . . . . . . . . . 6 2.2 DHCPv4 Option . . . . . . . . . . . . . . . . . . . . . 6
2.3 Latitude and Longitude Fields . . . . . . . . . . . . . 8 2.3 Latitude and Longitude Fields . . . . . . . . . . . . . 8
2.4 Altitude . . . . . . . . . . . . . . . . . . . . . . . . 11 2.4 Altitude . . . . . . . . . . . . . . . . . . . . . . . . 11
2.5 Datum . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.5 Datum . . . . . . . . . . . . . . . . . . . . . . . . . 13
3. Security Considerations. . . . . . . . . . . . . . . . . . . . 13 3. Security Considerations. . . . . . . . . . . . . . . . . . . . 14
4. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 14 4. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 14
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.1. Normative References . . . . . . . . . . . . . . . . . . 15 6.1. Normative References . . . . . . . . . . . . . . . . . . 15
6.2. Informational References . . . . . . . . . . . . . . . . 15 6.2. Informational References . . . . . . . . . . . . . . . . 16
Appendix A. Calculations of Resolution . . . . . . . . . . . . . . 16 Appendix A. Calculations of Resolution . . . . . . . . . . . . . . 17
A.1. LCI of "White House" (Example 1) . . . . . . . . . . . . 16 A.1. LCI of "White House" (Example 1) . . . . . . . . . . . . 17
A.2. LCI of "Sears Tower" (Example 2) . . . . . . . . . . . . 19 A.2. LCI of "Sears Tower" (Example 2) . . . . . . . . . . . . 19
Appendix B. Calculations of Uncertainty . . . . . . . . . . . . . 20 Appendix B. Calculations of Uncertainty . . . . . . . . . . . . . 21
B.1 LCI of "Sydney Opera House" (Example 3) . . . . . . . . 20 B.1 LCI of "Sydney Opera House" (Example 3) . . . . . . . . 21
Appendix C. Changes from RFC 3825 . . . . . . . . . . . . . . . . 24 Appendix C. Changes from RFC 3825 . . . . . . . . . . . . . . . . 25
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 26
1. Introduction 1. Introduction
The physical location of a network device has a range of The physical location of a network device has a range of
applications. In particular, emergency telephony applications rely applications. In particular, emergency telephony applications rely
on knowing the location of a caller in order to determine the correct on knowing the location of a caller in order to determine the correct
emergency center. emergency center.
The location of a device can be represented either in terms of The location of a device can be represented either in terms of
geospatial (or geodetic) coordinates, or as a civic address. geospatial (or geodetic) coordinates, or as a civic address.
skipping to change at page 4, line 40 skipping to change at page 4, line 40
encoding covers these points. This increases the region of encoding covers these points. This increases the region of
uncertainty, but ensures that the region that is described uncertainty, but ensures that the region that is described
encompasses the target location. encompasses the target location.
The DHCPv4 option format defined in this document supports both The DHCPv4 option format defined in this document supports both
resolution and uncertainty parameters. Version 0 of the DHCPv4 resolution and uncertainty parameters. Version 0 of the DHCPv4
option format defined in this document includes a resolution option format defined in this document includes a resolution
parameter for each of the dimensions of location. Since this parameter for each of the dimensions of location. Since this
resolution parameter need not apply to all dimensions equally, a resolution parameter need not apply to all dimensions equally, a
resolution value is included for each of the 3 location elements. resolution value is included for each of the 3 location elements.
The DHCPv6 option format as well as version 1 of the DHCPv4 option The DHCPv6 option format (which supports only version 1) as well as
format utilizes an uncertainty parameter. Appendix A of this version 1 of the DHCPv4 option format utilizes an uncertainty
document provides examples showing the calculation of resolution parameter. Appendix A of this document provides examples showing the
values. Appendix B provides an example demonstrating calculation of calculation of resolution values. Appendix B provides an example
uncertainty values. demonstrating calculation of uncertainty values.
2. DHCP Option Format 2. DHCP Option Format
This section defines the format for the DHCPv4 and DHCPv6 options. This section defines the format for the DHCPv4 and DHCPv6 options.
These options utilize a similar format, differing primarily in the These options utilize a similar format, differing primarily in the
option code. option code.
2.1. DHCPv6 Option 2.1. DHCPv6 Option
The DHCPv6 [RFC3315] option format is as follows: The DHCPv6 [RFC3315] option format is as follows:
skipping to change at page 5, line 20 skipping to change at page 5, line 20
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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Code (TBD) | OptLen (16) | | Option Code (TBD) | OptLen (16) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LatUnc | Latitude + | LatUnc | Latitude +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Lat (cont'd) | LongUnc | Longitude + | Lat (cont'd) | LongUnc | Longitude +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Longitude (cont'd) | AT | AltUnc | Altitude + | Longitude (cont'd) | AT | AltUnc | Altitude +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Altitude (cont'd) | Datum | | Altitude (cont'd) |Ver| Res |Datum|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Code: GEOCONF_GEODETIC (8 bits). Code: GEOCONF_GEODETIC (16 bits).
OptLen: Option Length (8 bits). This option is fixed size, the OptLen: Option Length (16). This option is fixed size, the
value of this octet will always be 16. value of this octet will always be 16.
LatUnc: Latitude Uncertainty (6 bits). LatUnc: Latitude Uncertainty (6 bits).
Latitude: Latitude (34 bits). Latitude: Latitude (34 bits).
LongUnc: Longitude Uncertainty (6 bits). LongUnc: Longitude Uncertainty (6 bits).
Longitude: Longitude (34 bits). Longitude: Longitude (34 bits).
AType: Altitude Type (4 bits). AType: Altitude Type (4 bits).
AltUnc: Altitude Uncertainty (6 bits). AltUnc: Altitude Uncertainty (6 bits).
Altitude: Altitude (30 bits). Altitude: Altitude (30 bits).
Datum: Datum (8 bits). Ver: The Ver field is two bits, providing for four potential
versions. This specification defines the behavior of
version 1. The Ver field is always located at the same
offset from the beginning of the option, regardless of
the version in use.
Res: The Res field which is 3 bits, is reserved. These bits
have been used by [IEEE-802.11y], but are not defined
within this specification.
Datum: 3 bits. The Map Datum used for the coordinates given in
this Option.
2.2. DHCPv4 Option 2.2. DHCPv4 Option
The DHCPv4 option format is as follows: The DHCPv4 option format is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Code 123 | Length | LatUnc | Latitude + | Code 123 | Length | LatUnc | Latitude +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 10, line 26 skipping to change at page 10, line 29
--X | X | --X | X |
| | `---------. | | `---------.
| | | | | |
| | | | | |
| | | | | |
- `-------------------------' - `-------------------------'
|---------X---------------| |---------X---------------|
|<------U------>| |<------U------>|
Key
---
V, ^ = vertical arrows, delimiting the vertical uncertainty range.
<> = horizontal arrows, delimiting the horizontal uncertainty
range.
Uncertainty applies to each axis independently. Uncertainty applies to each axis independently.
The amount of uncertainty can be determined from the encoding by The amount of uncertainty can be determined from the encoding by
taking 2 to the power of 8, less the encoded value. As is shown in taking 2 to the power of 8, less the encoded value. As is shown in
the following formula, where "x" is the encoded integer value: the following formula, where "x" is the encoded integer value:
uncertainty = 2 ^ ( 8 - x ) uncertainty = 2 ^ ( 8 - x )
The result of this formula is expressed in degrees of latitude or The result of this formula is expressed in degrees of latitude or
longitude. The uncertainty is added to the base latitude or longitude. The uncertainty is added to the base latitude or
skipping to change at page 24, line 9 skipping to change at page 25, line 9
shapes only; that is, either a two dimensional point or a polygon. shapes only; that is, either a two dimensional point or a polygon.
If the altitude type is 2 (floors), then this value can be If the altitude type is 2 (floors), then this value can be
represented using a civic address object [RFC5139] that is presented represented using a civic address object [RFC5139] that is presented
alongside the geodetic object. alongside the geodetic object.
Appendix C. Changes from RFC 3825 Appendix C. Changes from RFC 3825
Technical changes: Technical changes:
-05: Added version field to DHCPv6 option.
-04: Added Appendix B providing an example relating to -04: Added Appendix B providing an example relating to
uncertainty. Added Section 2.3.1 on Latitude and Longitude uncertainty. Added Section 2.3.1 on Latitude and Longitude
resolution and Section 2.4.4 on Altitude resolution. resolution and Section 2.4.4 on Altitude resolution.
Added definition of Resolution to Section 1.2. Added definition of Resolution to Section 1.2.
-03: Clarified potential behavior of version 0 clients receiving -03: Clarified potential behavior of version 0 clients receiving
a version 1 option and added recommendations for clients and a version 1 option and added recommendations for clients and
servers. servers.
-02: Added Section 1.2 introducing uncertainty and resolution -02: Added Section 1.2 introducing uncertainty and resolution
skipping to change at page 24, line 30 skipping to change at page 25, line 32
-01: Within Section 2.1, split Datum field from RFC 3825 into three -01: Within Section 2.1, split Datum field from RFC 3825 into three
fields: Ver, Res and Datum fields. Explained that the Ver fields: Ver, Res and Datum fields. Explained that the Ver
field is always located at the same offset. Added Section 2.2 field is always located at the same offset. Added Section 2.2
relating to Version Support. relating to Version Support.
-00: None -00: None
Editorial changes: Editorial changes:
-05: Corrected length of DHCPv6 option. Added Key to uncertainty
figure.
-04: Changed all uses of the LoRes/LaRes/AltRes terminology to
LongUnc/LatUnc/AltUnc, and clarified when these parameters
were used to encode resolution vs. uncertainty. Reorganized
Section 1.2. Added references to RFC 4119, RFC 5139 and
[GeoShape].
-03: Changed "DHC" to "DHCP" in some usages. Clarified relationship -03: Changed "DHC" to "DHCP" in some usages. Clarified relationship
of resolution and uncertainty to privacy. Changed all uses of of resolution and uncertainty to privacy.
the LoRes/LaRes/AltRes terminology to LongUnc/LatUnc/AltUnc,
and clarified when these parameters were used to encode
resolution vs. uncertainty.
-02: Reorganized Sections 1 and 2. -02: Reorganized Sections 1 and 2.
-01: Added references to IEEE 802.11y, RFC 3825. -01: Added references to IEEE 802.11y, RFC 3825.
-00: Changed boilerplate. Added B. Aboba as editor. Re-positioned -00: Changed boilerplate. Added B. Aboba as editor. Re-positioned
Appendix A and Acknowledgments sections. Changed reference Appendix A and Acknowledgments sections. Changed reference
numbers to names, added reference to RFC 5226 (since RFC 3825 numbers to names, added reference to RFC 5226 (since RFC 3825
was missing a reference to RFC 2434, now obsolete), updated was missing a reference to RFC 2434, now obsolete), updated
references (and URLs). Updated author affiliations and email references (and URLs). Updated author affiliations and email
addresses. Changed references to "the appendix" to Appendix A. addresses. Changed references to "the appendix" to Appendix A.
Added Appendix B listing changes. Added additional appendix listing changes.
Authors' Addresses Authors' Addresses
James M. Polk James M. Polk
Cisco Systems Cisco Systems
2200 East President George Bush Turnpike 2200 East President George Bush Turnpike
Richardson, Texas 75082 USA Richardson, Texas 75082 USA
USA USA
EMail: jmpolk@cisco.com EMail: jmpolk@cisco.com
John Schnizlein John Schnizlein
Technology Program Manager
Internet Society
1775 Wiehle Avenue
Suite 201
Reston, VA 20190-5108 USA
USA
EMail: schnizlein@isoc.org EMail: john@schnizlein.org
Marc Linsner Marc Linsner
Cisco Systems Cisco Systems
Marco Island, FL 34145 USA Marco Island, FL 34145 USA
USA USA
EMail: marc.linsner@cisco.com EMail: marc.linsner@cisco.com
Martin Thomson Martin Thomson
Andrew Andrew
 End of changes. 24 change blocks. 
42 lines changed or deleted 62 lines changed or added

This html diff was produced by rfcdiff 1.37b. The latest version is available from http://tools.ietf.org/tools/rfcdiff/