draft-ietf-geopriv-rfc3825bis-15.txt   draft-ietf-geopriv-rfc3825bis-16.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 Individual Contributor Category: Standards Track Individual Contributor
Expires: July 4, 2011 M. Linsner Expires: July 25, 2011 M. Linsner
14 January 2011 Cisco Systems 25 January 2011 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-15.txt draft-ietf-geopriv-rfc3825bis-16.txt
Abstract Abstract
This document specifies Dynamic Host Configuration Protocol Options This document specifies Dynamic Host Configuration Protocol Options
(both DHCPv4 and DHCPv6) for the coordinate-based geographic location (both DHCPv4 and DHCPv6) for the coordinate-based geographic location
of the client. The Location Configuration Information (LCI) includes of the client. The Location Configuration Information (LCI) includes
Latitude, Longitude, and Altitude, with resolution or uncertainty Latitude, Longitude, and Altitude, with resolution or uncertainty
indicators for each. Separate parameters indicate the reference indicators for each. Separate parameters indicate the reference
datum for each of these values. This document obsoletes RFC 3825. datum for each of these values. This document obsoletes RFC 3825.
skipping to change at page 1, line 49 skipping to change at page 1, line 49
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 July 4, 2011. This Internet-Draft will expire on July 25, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 11, line 25 skipping to change at page 11, line 25
2.3. Latitude and Longitude Fields 2.3. Latitude and Longitude Fields
The Latitude and Longitude values in this specification are encoded The Latitude and Longitude values in this specification are encoded
as 34 bit, twos complement, fixed point values with 9 integer bits as 34 bit, twos complement, fixed point values with 9 integer bits
and 25 fractional bits. The exact meaning of these values is and 25 fractional bits. The exact meaning of these values is
determined by the datum; the description in this section applies to determined by the datum; the description in this section applies to
the datums defined in this document. This document uses the same the datums defined in this document. This document uses the same
definition for all datums it specifies. definition for all datums it specifies.
Latitude values encoded by the DHCP server MUST be constrained to the
range from -90 to +90 degrees. Location consumers MUST be prepared
to normalize values outside this range. Values outside the range are
normalized by clamping (e.g. values less than -90 degrees are set to
-90; values greater than 90 degrees are set to +90). Positive
latitudes are north of the equator and negative latitudes are south
of the equator.
Longitude values encoded by the DHCP server MUST be normalized to the
range from -180 to +180 degrees. Location consumers MUST be prepared
to normalize values outside this range. Values outside the range are
normalized by wrapping (e.g. adding or subtracting 360 until they
fall within the range of -180 to 180). Positive longitudes are east
of the Prime Meridian (Greenwich) and negative (2s complement)
longitudes are west of the Prime Meridian.
When encoding, Latitude and Longitude values are rounded to the When encoding, Latitude and Longitude values are rounded to the
nearest 34-bit binary representation. This imprecision is considered nearest 34-bit binary representation. This imprecision is considered
acceptable for the purposes to which this form is intended to be acceptable for the purposes to which this form is intended to be
applied and is ignored when decoding. applied and is ignored when decoding.
Positive latitudes are north of the equator and negative latitudes
are south of the equator. Positive longitudes are east of the Prime
Meridian (Greenwich) and negative (2s complement) longitudes are west
of the Prime Meridian.
Within the coordinate reference systems defined in this document
(Datum values 1-3), longitude values outside the range of -180 to 180
decimal degrees or latitude values outside the range of -90 to 90
degrees MUST be considered invalid. Server implementations SHOULD
prevent the entry of invalid values within the selected coordinate
reference system. Location consumers MUST ignore invalid location
coordinates and SHOULD log invalid location errors.
2.3.1. Latitude and Longitude Resolution 2.3.1. Latitude and Longitude Resolution
The Latitude (LaRes), Longitude (LoRes) and Altitude (AltRes) The Latitude (LaRes), Longitude (LoRes) and Altitude (AltRes)
Resolution fields are encoded as 6 bit, unsigned integer values. In Resolution fields are encoded as 6 bit, unsigned integer values. In
the DHCPv4 Option 123, the LaRes, LoRes and AltRes fields are used to the DHCPv4 Option 123, the LaRes, LoRes and AltRes fields are used to
encode the number of bits of resolution. The resolution sub-fields encode the number of bits of resolution. The resolution sub-fields
accommodate the desire to easily adjust the precision of a reported accommodate the desire to easily adjust the precision of a reported
location. Contents beyond the claimed resolution MAY be randomized location. Contents beyond the claimed resolution MAY be randomized
to obscure greater precision that might be available. to obscure greater precision that might be available.
skipping to change at page 32, line 20 skipping to change at page 32, line 20
o Section 1 now includes clarifications on wired and wireless uses. o Section 1 now includes clarifications on wired and wireless uses.
o The former Sections 1.2 and 1.3 have been removed. Section 1.2 o The former Sections 1.2 and 1.3 have been removed. Section 1.2
now defines the concepts of uncertainty and resolution, as well now defines the concepts of uncertainty and resolution, as well
as conversion between the DHCP option format and PIDF-LO. as conversion between the DHCP option format and PIDF-LO.
o A DHCPv6 option is now defined (Section 2.1) as well o A DHCPv6 option is now defined (Section 2.1) as well
as DHCPv4 options (Section 2.2). as DHCPv4 options (Section 2.2).
o The former Datum field has been split into three fields: o The former Datum field has been split into three fields:
Ver, Res and Datum. These fields are used in both the Ver, Res and Datum. These fields are used in both the
DHCPv4 and DHCPv6 options. DHCPv4 and DHCPv6 options.
o Section 2.2.3 has been added, describing Option support. o Section 2.2.3 has been added, describing option support.
o Section 2.3 has been added, describing the Latitude and o Section 2.3 has been added, describing the Latitude and
Longitude fields. Longitude fields.
o Section 2.3.1 has been added, covering Latitude and Longitude o Section 2.3.1 has been added, covering Latitude and Longitude
resolution. resolution.
o Section 2.3.2 has been added, covering Latitude and Longitude o Section 2.3.2 has been added, covering Latitude and Longitude
uncertainty. uncertainty.
o Section 2.4 has been added, covering values of the Altitude o Section 2.4 has been added, covering values of the Altitude
field (Sections 2.4.1, 2.4.2 and 2.4.3), Altitude resolution field (Sections 2.4.1, 2.4.2 and 2.4.3), Altitude resolution
(Section 2.4.4), and Altitude uncertainty (Section 2.4.5). (Section 2.4.4), and Altitude uncertainty (Section 2.4.5).
o Section 2.5 has been added, covering the Datum field. o Section 2.5 has been added, covering the Datum field.
 End of changes. 6 change blocks. 
21 lines changed or deleted 18 lines changed or added

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