draft-ietf-geopriv-held-measurements-08.txt   draft-ietf-geopriv-held-measurements-09.txt 
GEOPRIV M. Thomson GEOPRIV M. Thomson
Internet-Draft Microsoft Internet-Draft Microsoft
Intended status: Standards Track J. Winterbottom Intended status: Standards Track J. Winterbottom
Expires: December 26, 2013 Unaffiliated Expires: March 10, 2014 Unaffiliated
June 24, 2013 September 06, 2013
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-08 draft-ietf-geopriv-held-measurements-09
Abstract Abstract
This document describes a protocol for a Device to provide location- This document describes a protocol for a Device to provide location-
related measurement data to a Location Information Server (LIS) related measurement data to a Location Information Server (LIS)
within a request for location information. Location-related within a request for location information. Location-related
measurement information are observations concerning properties measurement information are observations concerning properties
related to the position of a Device, which could be data about related to the position of a Device, which could be data about
network attachment or about the physical environment. A LIS is able network attachment or about the physical environment. A LIS is able
to use the location-related measurement data to improve the accuracy to use the location-related measurement data to improve the accuracy
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 December 26, 2013. This Internet-Draft will expire on March 10, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 2, line 24 skipping to change at page 2, line 24
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Conventions used in this document . . . . . . . . . . . . . . 5 2. Conventions used in this document . . . . . . . . . . . . . . 5
3. Location-Related Measurements in LCPs . . . . . . . . . . . . 5 3. Location-Related Measurements in LCPs . . . . . . . . . . . . 5
4. Location-Related Measurement Data Types . . . . . . . . . . . 7 4. Location-Related Measurement Data Types . . . . . . . . . . . 7
4.1. Measurement Container . . . . . . . . . . . . . . . . . . 7 4.1. Measurement Container . . . . . . . . . . . . . . . . . . 7
4.1.1. Time of Measurement . . . . . . . . . . . . . . . . . 8 4.1.1. Time of Measurement . . . . . . . . . . . . . . . . . 8
4.1.2. Expiry Time on Location-Related Measurement Data . . 8 4.1.2. Expiry Time on Location-Related Measurement Data . . 8
4.2. RMS Error and Number of Samples . . . . . . . . . . . . . 9 4.2. RMS Error and Number of Samples . . . . . . . . . . . . . 8
4.2.1. Time RMS Error . . . . . . . . . . . . . . . . . . . 9 4.2.1. Time RMS Error . . . . . . . . . . . . . . . . . . . 9
4.3. Measurement Request . . . . . . . . . . . . . . . . . . . 10 4.3. Measurement Request . . . . . . . . . . . . . . . . . . . 10
4.4. Identifying Location Provenance . . . . . . . . . . . . . 11 4.4. Identifying Location Provenance . . . . . . . . . . . . . 11
5. Location-Related Measurement Data Types . . . . . . . . . . . 13 5. Location-Related Measurement Data Types . . . . . . . . . . . 13
5.1. LLDP Measurements . . . . . . . . . . . . . . . . . . . . 14 5.1. LLDP Measurements . . . . . . . . . . . . . . . . . . . . 14
5.2. DHCP Relay Agent Information Measurements . . . . . . . . 15 5.2. DHCP Relay Agent Information Measurements . . . . . . . . 15
5.3. 802.11 WLAN Measurements . . . . . . . . . . . . . . . . 15 5.3. 802.11 WLAN Measurements . . . . . . . . . . . . . . . . 15
5.3.1. Wifi Measurement Requests . . . . . . . . . . . . . . 19 5.3.1. Wifi Measurement Requests . . . . . . . . . . . . . . 19
5.4. Cellular Measurements . . . . . . . . . . . . . . . . . . 19 5.4. Cellular Measurements . . . . . . . . . . . . . . . . . . 19
5.4.1. Cellular Measurement Requests . . . . . . . . . . . . 22 5.4.1. Cellular Measurement Requests . . . . . . . . . . . . 22
skipping to change at page 8, line 13 skipping to change at page 8, line 13
[RFC5985]. [RFC5985].
4.1.1. Time of Measurement 4.1.1. Time of Measurement
The "time" attribute records the time that the measurement or The "time" attribute records the time that the measurement or
observation was made. This time can be different to the time that observation was made. This time can be different to the time that
the measurement information was reported. Time information can be the measurement information was reported. Time information can be
used to populate a timestamp on the location result, or to determine used to populate a timestamp on the location result, or to determine
if the measurement information is used. if the measurement information is used.
The "time" attribute SHOULD be used to avoid forcing an arbitrary The "time" attribute SHOULD be provided whenever possible. This
choice of timestamp for relatively static types of measurement (for allows a LIS to avoid selecting an arbitrary timestamp. Exceptions
instance, the DSL measurements in Section 5.6) and for legacy Devices to this, where omitting time might make sense, include relatively
that don't record time information (such as the Home Location static types of measurement (for instance, the DSL measurements in
Register/Home Subscriber Server for cellular). However, time SHOULD Section 5.6) or for legacy Devices that don't record time information
be provided whenever possible. (such as the Home Location Register/Home Subscriber Server for
cellular).
The "time" attribute is attached to the root "measurement" element. The "time" attribute is attached to the root "measurement" element.
Multiple measurements can often be given the same timestamp, even Multiple measurements can often be given the same timestamp, even
when the measurements were not actually taken at the same time when the measurements were not actually taken at the same time
(consider a set of measurements taken sequentially, where the (consider a set of measurements taken sequentially, where the
difference in time between observations is not significant). difference in time between observations is not significant).
Measurements cannot be grouped if they have different types, or there Measurements cannot be grouped if they have different types, or there
is a need for independent time values on each measurement. In these is a need for independent time values on each measurement. In these
instances, multiple measurement sets are necessary. instances, multiple measurement sets are necessary.
skipping to change at page 36, line 32 skipping to change at page 36, line 32
Any costs in validation are balanced against the degree of integrity Any costs in validation are balanced against the degree of integrity
desired from the resulting location information. desired from the resulting location information.
7.2.1. Measurement Validation 7.2.1. Measurement Validation
Detecting that measurement data has been falsified is difficult in Detecting that measurement data has been falsified is difficult in
the absence of integrity mechanisms. the absence of integrity mechanisms.
Independent confirmation of the veracity of measurement data ensures Independent confirmation of the veracity of measurement data ensures
that the measurement is accurate and that it applies to the correct that the measurement is accurate and that it applies to the correct
Device. When it's possible to gathering the same measurement data Device. When it's possible to gather the same measurement data from
from a trusted and independent source without undue expense, the LIS a trusted and independent source without undue expense, the LIS can
can use the trusted data in place of what the untrusted Device has use the trusted data in place of what the untrusted Device has sent.
sent. In cases where that is impractical, the untrusted data can In cases where that is impractical, the untrusted data can provide
provide hints that allow corroboration of the data (see hints that allow corroboration of the data (see Section 7.2.1.1).
Section 7.2.1.1).
Measurement information might contain no inherent indication that it Measurement information might contain no inherent indication that it
is falsified. On the contrary, it can be difficult to obtain is falsified. On the contrary, it can be difficult to obtain
information that would provide any degree of assurance that the information that would provide any degree of assurance that the
measurement device is physically at any particular location. measurement device is physically at any particular location.
Measurements that are difficult to verify require other forms of Measurements that are difficult to verify require other forms of
assurance before they can be used. assurance before they can be used.
7.2.1.1. Effectiveness 7.2.1.1. Effectiveness
skipping to change at page 55, line 50 skipping to change at page 55, line 50
</xs:simpleType> </xs:simpleType>
<xs:simpleType name="mncType"> <xs:simpleType name="mncType">
<xs:restriction base="xs:token"> <xs:restriction base="xs:token">
<xs:pattern value="[0-9]{2,3}"/> <xs:pattern value="[0-9]{2,3}"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<xs:simpleType name="cellIdType"> <xs:simpleType name="cellIdType">
<xs:restriction base="xs:nonNegativeInteger"> <xs:restriction base="xs:nonNegativeInteger">
<xs:maxInclusive value="268435456"/> <!-- 2^28 (eucid) --> <xs:maxInclusive value="268435455"/> <!-- 2^28 (eucid) -->
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<!-- Measurement Request elements --> <!-- Measurement Request elements -->
<xs:element name="type" type="cell:typeType"/> <xs:element name="type" type="cell:typeType"/>
<xs:simpleType name="typeType"> <xs:simpleType name="typeType">
<xs:restriction base="xs:token"> <xs:restriction base="xs:token">
<xs:enumeration value="gsm"/> <xs:enumeration value="gsm"/>
 End of changes. 7 change blocks. 
18 lines changed or deleted 18 lines changed or added

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