draft-ietf-geopriv-held-measurements-01.txt   draft-ietf-geopriv-held-measurements-02.txt 
GEOPRIV M. Thomson GEOPRIV M. Thomson
Internet-Draft J. Winterbottom Internet-Draft J. Winterbottom
Intended status: Standards Track Andrew Intended status: Standards Track Andrew
Expires: March 10, 2011 September 6, 2010 Expires: April 28, 2011 October 25, 2010
Using Device-provided Location-Related Measurements in Location Using Device-provided Location-Related Measurements in Location
Configuration Protocols Configuration Protocols
draft-ietf-geopriv-held-measurements-01 draft-ietf-geopriv-held-measurements-02
Abstract Abstract
A method is described by which a Device is able to provide location- A method is described by which a Device is able to provide location-
related measurement data to a LIS within a request for location related measurement data to a LIS within a request for location
information. Location-related measurement information are information. Location-related measurement information are
observations concerning properties related to the position of a observations concerning properties related to the position of a
Device, which could be data about network attachment or about the Device, which could be data about network attachment or about the
physical environment. When a LIS generates location information for physical environment. When a LIS generates location information for
a Device, information from the Device can improve the accuracy of the a Device, information from the Device can improve the accuracy of the
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on March 10, 2011. This Internet-Draft will expire on April 28, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 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 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 3, line 22 skipping to change at page 3, line 22
4.1.1. Time of Measurement . . . . . . . . . . . . . . . . . 9 4.1.1. Time of Measurement . . . . . . . . . . . . . . . . . 9
4.1.2. Expiry Time on Location-Related Measurement Data . . . 9 4.1.2. Expiry Time on Location-Related Measurement Data . . . 9
4.2. RMS Error and Number of Samples . . . . . . . . . . . . . 10 4.2. RMS Error and Number of Samples . . . . . . . . . . . . . 10
4.2.1. Time RMS Error . . . . . . . . . . . . . . . . . . . . 10 4.2.1. Time RMS Error . . . . . . . . . . . . . . . . . . . . 10
4.3. Measurement Request . . . . . . . . . . . . . . . . . . . 11 4.3. Measurement Request . . . . . . . . . . . . . . . . . . . 11
4.4. Identifying Location Provenance . . . . . . . . . . . . . 12 4.4. Identifying Location Provenance . . . . . . . . . . . . . 12
5. Location-Related Measurement Data Types . . . . . . . . . . . 15 5. Location-Related Measurement Data Types . . . . . . . . . . . 15
5.1. LLDP Measurements . . . . . . . . . . . . . . . . . . . . 15 5.1. LLDP Measurements . . . . . . . . . . . . . . . . . . . . 15
5.2. DHCP Relay Agent Information Measurements . . . . . . . . 16 5.2. DHCP Relay Agent Information Measurements . . . . . . . . 16
5.3. 802.11 WLAN Measurements . . . . . . . . . . . . . . . . . 16 5.3. 802.11 WLAN Measurements . . . . . . . . . . . . . . . . . 16
5.3.1. Wifi Measurement Requests . . . . . . . . . . . . . . 19 5.3.1. Wifi Measurement Requests . . . . . . . . . . . . . . 20
5.4. Cellular Measurements . . . . . . . . . . . . . . . . . . 20 5.4. Cellular Measurements . . . . . . . . . . . . . . . . . . 20
5.4.1. Cellular Measurement Requests . . . . . . . . . . . . 23 5.4.1. Cellular Measurement Requests . . . . . . . . . . . . 23
5.5. GNSS Measurements . . . . . . . . . . . . . . . . . . . . 23 5.5. GNSS Measurements . . . . . . . . . . . . . . . . . . . . 23
5.5.1. GNSS System and Signal . . . . . . . . . . . . . . . . 25 5.5.1. GNSS System and Signal . . . . . . . . . . . . . . . . 25
5.5.2. Time . . . . . . . . . . . . . . . . . . . . . . . . . 26 5.5.2. Time . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.5.3. Per-Satellite Measurement Data . . . . . . . . . . . . 26 5.5.3. Per-Satellite Measurement Data . . . . . . . . . . . . 26
5.5.4. GNSS Measurement Requests . . . . . . . . . . . . . . 27 5.5.4. GNSS Measurement Requests . . . . . . . . . . . . . . 27
5.6. DSL Measurements . . . . . . . . . . . . . . . . . . . . . 27 5.6. DSL Measurements . . . . . . . . . . . . . . . . . . . . . 27
5.6.1. L2TP Measurements . . . . . . . . . . . . . . . . . . 28 5.6.1. L2TP Measurements . . . . . . . . . . . . . . . . . . 28
5.6.2. RADIUS Measurements . . . . . . . . . . . . . . . . . 28 5.6.2. RADIUS Measurements . . . . . . . . . . . . . . . . . 28
skipping to change at page 12, line 23 skipping to change at page 12, line 23
<measurementRequest <measurementRequest
xmlns="urn:ietf:params:xml:ns:geopriv:lm" xmlns="urn:ietf:params:xml:ns:geopriv:lm"
xmlns:wifi="urn:ietf:params:xml:ns:geopriv:lm:wifi"> xmlns:wifi="urn:ietf:params:xml:ns:geopriv:lm:wifi">
<measurement type="wifi:wifi"> <measurement type="wifi:wifi">
<wifi:type>n</wifi:type> <wifi:type>n</wifi:type>
<wifi:parameter context="ap">wifi:rcpi</wifi:parameter> <wifi:parameter context="ap">wifi:rcpi</wifi:parameter>
</measurement> </measurement>
</measurementRequest> </measurementRequest>
</error> </error>
Figure 3 Figure 3: HELD Error Requesting Measurement Data
A measurement request that is included in other HELD messages has A measurement request that is included in other HELD messages has
undefined semantics and can be safely ignored. Other specifications undefined semantics and can be safely ignored. Other specifications
might define semantics for measurement requests under other might define semantics for measurement requests under other
conditions. conditions.
4.4. Identifying Location Provenance 4.4. Identifying Location Provenance
An extension is made to the PIDF-LO [RFC4119] that allows a location An extension is made to the PIDF-LO [RFC4119] that allows a location
recipient to identify the source (or sources) of location information recipient to identify the source (or sources) of location information
skipping to change at page 17, line 13 skipping to change at page 17, line 13
to, or other WiFi points it is able to see. This is provided using to, or other WiFi points it is able to see. This is provided using
the "wifi" element, as shown in Figure 6, which shows a single the "wifi" element, as shown in Figure 6, which shows a single
complete measurement for a single access point. complete measurement for a single access point.
<measurements xmlns="urn:ietf:params:xml:ns:geopriv:lm" <measurements xmlns="urn:ietf:params:xml:ns:geopriv:lm"
time="2011-04-29T14:33:58"> time="2011-04-29T14:33:58">
<wifi xmlns="urn:ietf:params:xml:ns:geopriv:lm:wifi"> <wifi xmlns="urn:ietf:params:xml:ns:geopriv:lm:wifi">
<nicType>Intel(r)PRO/Wireless 2200BG</nicType> <nicType>Intel(r)PRO/Wireless 2200BG</nicType>
<ap serving="true"> <ap serving="true">
<bssid>AB-CD-EF-AB-CD-EF</bssid> <bssid>AB-CD-EF-AB-CD-EF</bssid>
<name>Example</name>
<ssid>example</ssid> <ssid>example</ssid>
<channel>5</channel> <channel>5</channel>
<location> <location>
<gml:Point xmlns:gml="http://opengis.net/gml"> <gml:Point xmlns:gml="http://opengis.net/gml">
<gml:pos>-34.4 150.8</gml:pos> <gml:pos>-34.4 150.8</gml:pos>
</gml:Point> </gml:Point>
</location> </location>
<type>a</type> <type>a</type>
<band>5</band> <band>5</band>
<regclass country="AU">2</regclass> <regclass country="AU">2</regclass>
skipping to change at page 18, line 10 skipping to change at page 18, line 9
bssid: The basic service set identifier. In an Infrastructure BSS bssid: The basic service set identifier. In an Infrastructure BSS
network, the bssid is the 48 bit MAC address of the access point. network, the bssid is the 48 bit MAC address of the access point.
The "verified" attribute of this element describes whether the The "verified" attribute of this element describes whether the
device has verified the MAC address or it authenticated the access device has verified the MAC address or it authenticated the access
point or the network operating the access point (for example, a point or the network operating the access point (for example, a
captive portal accessed through the access point has been captive portal accessed through the access point has been
authenticated). This attributes defaults to a value of "false" authenticated). This attributes defaults to a value of "false"
when omitted. when omitted.
name: The broadcast name for the access point. ssid: The service set identifier (SSID) for the wireless network
served by the access point.
ssid: The service set identifier for the wireless network served by The SSID is a 32-octet identifier that is commonly represented as
the access point. a ASCII [RFC0020] or UTF-8 [RFC3629] encoded string. To represent
octets that cannot be directly included in an XML element,
escaping is used. Sequences of octets that do not represent a
valid UTF-8 encoding can be escaped using a backslash ('\')
followed by two case-insensitive hexadecimal digits representing
the value of a single octet.
The canonical or value-space form of an SSID is a sequence of up
to 32 octets that is produced from the concatenation of UTF-8
encoded sequences of unescaped characters and octets derived from
escaped components.
channel: The channel number (frequency) that the access point channel: The channel number (frequency) that the access point
operates on. operates on.
location: The location of the access point, as reported by the location: The location of the access point, as reported by the
access point. This element contains any valid location, using the access point. This element contains any valid location, using the
rules for a "location-info" element, as described in [RFC5491]. rules for a "location-info" element, as described in [RFC5491].
type: The network type for the network access. This element type: The network type for the network access. This element
includes the alphabetic suffix of the 802.11 specification that includes the alphabetic suffix of the 802.11 specification that
skipping to change at page 18, line 35 skipping to change at page 18, line 45
"n". "n".
band: The frequency band for the radio, in gigahertz (GHz). 802.11 band: The frequency band for the radio, in gigahertz (GHz). 802.11
[IEEE.80211] specifies PHY layers that use 2.4, 3.7 and 5 [IEEE.80211] specifies PHY layers that use 2.4, 3.7 and 5
gigahertz frequency bands. gigahertz frequency bands.
regclass: The regulatory domain and class. The "country" attribute regclass: The regulatory domain and class. The "country" attribute
optionally includes the applicable two character country optionally includes the applicable two character country
identifier (dot11CountryString), which can be followed by an 'O', identifier (dot11CountryString), which can be followed by an 'O',
'I' or 'X'. The element text content includes the value of the 'I' or 'X'. The element text content includes the value of the
regulatory class: an 8-bit integer. regulatory class: an 8-bit integer in decimal form.
antenna: The antenna identifier for the antenna that the access antenna: The antenna identifier for the antenna that the access
point is using to transmit the measured signals. point is using to transmit the measured signals.
flightTime: Flight time is the difference between the time of flightTime: Flight time is the difference between the time of
departure (TOD) of signal from a transmitting station and time of departure (TOD) of signal from a transmitting station and time of
arrival (TOA) of signal at a receiving station, as defined in arrival (TOA) of signal at a receiving station, as defined in
[IEEE.80211V]. Measurement of this value requires that stations [IEEE.80211V]. Measurement of this value requires that stations
synchronize their clocks. This value can be measured by access synchronize their clocks. This value can be measured by access
point or Device; because the flight time is assumed to be the same point or Device; because the flight time is assumed to be the same
skipping to change at page 51, line 50 skipping to change at page 51, line 50
<xs:anyAttribute namespace="##any" processContents="lax"/> <xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:restriction> </xs:restriction>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
<xs:complexType name="wifiType"> <xs:complexType name="wifiType">
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType"> <xs:restriction base="xs:anyType">
<xs:sequence> <xs:sequence>
<xs:element name="bssid" type="wifi:bssidType"/> <xs:element name="bssid" type="wifi:bssidType"/>
<xs:element name="name" type="wifi:ssidBaseType" <xs:element name="ssid" type="wifi:ssidType"
minOccurs="0"/> minOccurs="0"/>
<xs:element name="ssid" type="wifi:ssidBaseType"
minOccurs="0"/>
<xs:element name="channel" type="xs:nonNegativeInteger" <xs:element name="channel" type="xs:nonNegativeInteger"
minOccurs="0"/> minOccurs="0"/>
<xs:element name="location" minOccurs="0" <xs:element name="location" minOccurs="0"
type="xs:anyType"/> type="xs:anyType"/>
<xs:element name="type" type="wifi:networkType" <xs:element name="type" type="wifi:networkType"
minOccurs="0"/> minOccurs="0"/>
<xs:element name="regclass" type="wifi:regclassType" <xs:element name="regclass" type="wifi:regclassType"
minOccurs="0"/> minOccurs="0"/>
<xs:element name="antenna" type="wifi:octetType" <xs:element name="antenna" type="wifi:octetType"
minOccurs="0"/> minOccurs="0"/>
skipping to change at page 52, line 33 skipping to change at page 52, line 31
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="serving" type="xs:boolean" <xs:attribute name="serving" type="xs:boolean"
default="false"/> default="false"/>
<xs:anyAttribute namespace="##any" processContents="lax"/> <xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:restriction> </xs:restriction>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
<xs:simpleType name="ssidBaseType">
<xs:restriction base="xs:token">
<xs:maxLength value="32"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="bssidType"> <xs:complexType name="bssidType">
<xs:simpleContent> <xs:simpleContent>
<xs:extension base="bt:macAddressType"> <xs:extension base="bt:macAddressType">
<xs:attribute name="verified" type="xs:boolean" <xs:attribute name="verified" type="xs:boolean"
default="false"/> default="false"/>
</xs:extension> </xs:extension>
</xs:simpleContent> </xs:simpleContent>
</xs:complexType> </xs:complexType>
<!-- Note that this pattern does not prevent multibyte UTF-8
sequences that result in a SSID longer than 32 octets. -->
<xs:simpleType name="ssidType">
<xs:restriction base="xs:token">
<xs:pattern value="(\\[\da-fA-F]{2}|[^\\]){0,32}"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="networkType"> <xs:simpleType name="networkType">
<xs:restriction base="xs:token"> <xs:restriction base="xs:token">
<xs:pattern value="[a-zA-Z]+"/> <xs:pattern value="[a-zA-Z]+"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<xs:complexType name="regclassType"> <xs:complexType name="regclassType">
<xs:simpleContent> <xs:simpleContent>
<xs:extension base="wifi:octetType"> <xs:extension base="wifi:octetType">
<xs:attribute name="country"> <xs:attribute name="country">
<xs:simpleType> <xs:simpleType>
skipping to change at page 70, line 42 skipping to change at page 70, line 42
Thanks go to Simon Cox for his comments relating to terminology that Thanks go to Simon Cox for his comments relating to terminology that
have helped ensure that this document is aligns with ongoing work in have helped ensure that this document is aligns with ongoing work in
the Open Geospatial Consortium (OGC). Thanks to Neil Harper for his the Open Geospatial Consortium (OGC). Thanks to Neil Harper for his
review and comments on the GNSS sections of this document. Thanks to review and comments on the GNSS sections of this document. Thanks to
Noor-E-Gagan Singh, Gabor Bajko and Russell Priebe for their Noor-E-Gagan Singh, Gabor Bajko and Russell Priebe for their
significant input to and suggestions for improving the 802.11 significant input to and suggestions for improving the 802.11
measurements. Thanks to Cullen Jennings for feedback and measurements. Thanks to Cullen Jennings for feedback and
suggestions. Bernard Aboba provided review and feedback on a range suggestions. Bernard Aboba provided review and feedback on a range
of measurement data definitions. Mary Barnes provided a review and of measurement data definitions. Mary Barnes provided a review and
corrections. corrections. David Waitzman and John Bressler both noted
shortcomings with 802.11 measurements.
11. References 11. References
11.1. Normative References 11.1. Normative References
[DSL.TR025] [DSL.TR025]
Wang, R., "Core Network Architecture Recommendations for Wang, R., "Core Network Architecture Recommendations for
Access to Legacy Data Networks over ADSL", September 1999. Access to Legacy Data Networks over ADSL", September 1999.
[DSL.TR101] [DSL.TR101]
skipping to change at page 71, line 22 skipping to change at page 71, line 23
[Galileo.ICD] [Galileo.ICD]
GJU, "Galileo Open Service Signal In Space Interface GJU, "Galileo Open Service Signal In Space Interface
Control Document (SIS ICD)", May 2006. Control Document (SIS ICD)", May 2006.
[I-D.ietf-geopriv-http-location-delivery] [I-D.ietf-geopriv-http-location-delivery]
Barnes, M., Winterbottom, J., Thomson, M., and B. Stark, Barnes, M., Winterbottom, J., Thomson, M., and B. Stark,
"HTTP Enabled Location Delivery (HELD)", "HTTP Enabled Location Delivery (HELD)",
draft-ietf-geopriv-http-location-delivery-16 (work in draft-ietf-geopriv-http-location-delivery-16 (work in
progress), August 2009. progress), August 2009.
[RFC0020] Cerf, V., "ASCII format for network interchange", RFC 20,
October 1969.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, November 2003.
[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
Format", RFC 4119, December 2005. Format", RFC 4119, December 2005.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
[RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV
Presence Information Data Format Location Object (PIDF-LO) Presence Information Data Format Location Object (PIDF-LO)
Usage Clarification, Considerations, and Recommendations", Usage Clarification, Considerations, and Recommendations",
skipping to change at page 72, line 9 skipping to change at page 72, line 17
[HARPER] Harper, N., Dawson, M., and D. Evans, "Server-side [HARPER] Harper, N., Dawson, M., and D. Evans, "Server-side
spoofing and detection for Assisted-GPS", Proceedings of spoofing and detection for Assisted-GPS", Proceedings of
International Global Navigation Satellite Systems Society International Global Navigation Satellite Systems Society
(IGNSS) Symposium 2009 16, December 2009, (IGNSS) Symposium 2009 16, December 2009,
<http://ignss.org/files/Paper16.pdf>. <http://ignss.org/files/Paper16.pdf>.
[I-D.ietf-geopriv-held-identity-extensions] [I-D.ietf-geopriv-held-identity-extensions]
Winterbottom, J., Thomson, M., Tschofenig, H., and R. Winterbottom, J., Thomson, M., Tschofenig, H., and R.
Barnes, "Use of Device Identity in HTTP-Enabled Location Barnes, "Use of Device Identity in HTTP-Enabled Location
Delivery (HELD)", Delivery (HELD)",
draft-ietf-geopriv-held-identity-extensions-04 (work in draft-ietf-geopriv-held-identity-extensions-05 (work in
progress), June 2010. progress), October 2010.
[I-D.thomson-geopriv-uncertainty] [I-D.thomson-geopriv-uncertainty]
Thomson, M. and J. Winterbottom, "Representation of Thomson, M. and J. Winterbottom, "Representation of
Uncertainty and Confidence in PIDF-LO", Uncertainty and Confidence in PIDF-LO",
draft-thomson-geopriv-uncertainty-05 (work in progress), draft-thomson-geopriv-uncertainty-05 (work in progress),
May 2010. May 2010.
[IANA.enterprise] [IANA.enterprise]
IANA, "Private Enterprise Numbers", IANA, "Private Enterprise Numbers",
<http://www.iana.org/assignments/enterprise-numbers>. <http://www.iana.org/assignments/enterprise-numbers>.
 End of changes. 17 change blocks. 
22 lines changed or deleted 39 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/