draft-ietf-geopriv-held-measurements-06.txt   draft-ietf-geopriv-held-measurements-07.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: September 23, 2013 Commscope Expires: October 13, 2013 Commscope
March 22, 2013 April 11, 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-06 draft-ietf-geopriv-held-measurements-07
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 41 skipping to change at page 1, line 41
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 September 23, 2013. This Internet-Draft will expire on October 13, 2013.
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 20 skipping to change at page 2, line 20
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Conventions used in this document . . . . . . . . . . . . . . 4 2. Conventions used in this document . . . . . . . . . . . . . . 4
3. Location-Related Measurements in LCPs . . . . . . . . . . . . 5 3. Location-Related Measurements in LCPs . . . . . . . . . . . . 5
4. Location-Related Measurement Data Types . . . . . . . . . . . 6 4. Location-Related Measurement Data Types . . . . . . . . . . . 6
4.1. Measurement Container . . . . . . . . . . . . . . . . . . 7 4.1. Measurement Container . . . . . . . . . . . . . . . . . . 7
4.1.1. Time of Measurement . . . . . . . . . . . . . . . . . 7 4.1.1. Time of Measurement . . . . . . . . . . . . . . . . . 7
4.1.2. Expiry Time on Location-Related Measurement Data . . 7 4.1.2. Expiry Time on Location-Related Measurement Data . . 8
4.2. RMS Error and Number of Samples . . . . . . . . . . . . . 8 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 . . . . . . . . . . . . . . . . . . . 9 4.3. Measurement Request . . . . . . . . . . . . . . . . . . . 9
4.4. Identifying Location Provenance . . . . . . . . . . . . . 10 4.4. Identifying Location Provenance . . . . . . . . . . . . . 10
5. Location-Related Measurement Data Types . . . . . . . . . . . 13 5. Location-Related Measurement Data Types . . . . . . . . . . . 12
5.1. LLDP Measurements . . . . . . . . . . . . . . . . . . . . 13 5.1. LLDP Measurements . . . . . . . . . . . . . . . . . . . . 13
5.2. DHCP Relay Agent Information Measurements . . . . . . . . 14 5.2. DHCP Relay Agent Information Measurements . . . . . . . . 14
5.3. 802.11 WLAN Measurements . . . . . . . . . . . . . . . . 14 5.3. 802.11 WLAN Measurements . . . . . . . . . . . . . . . . 14
5.3.1. Wifi Measurement Requests . . . . . . . . . . . . . . 18 5.3.1. Wifi Measurement Requests . . . . . . . . . . . . . . 17
5.4. Cellular Measurements . . . . . . . . . . . . . . . . . . 18 5.4. Cellular Measurements . . . . . . . . . . . . . . . . . . 18
5.4.1. Cellular Measurement Requests . . . . . . . . . . . . 21 5.4.1. Cellular Measurement Requests . . . . . . . . . . . . 20
5.5. GNSS Measurements . . . . . . . . . . . . . . . . . . . . 21 5.5. GNSS Measurements . . . . . . . . . . . . . . . . . . . . 21
5.5.1. GNSS System and Signal . . . . . . . . . . . . . . . 23 5.5.1. GNSS System and Signal . . . . . . . . . . . . . . . 22
5.5.2. Time . . . . . . . . . . . . . . . . . . . . . . . . 23 5.5.2. Time . . . . . . . . . . . . . . . . . . . . . . . . 23
5.5.3. Per-Satellite Measurement Data . . . . . . . . . . . 23 5.5.3. Per-Satellite Measurement Data . . . . . . . . . . . 23
5.5.4. GNSS Measurement Requests . . . . . . . . . . . . . . 24 5.5.4. GNSS Measurement Requests . . . . . . . . . . . . . . 24
5.6. DSL Measurements . . . . . . . . . . . . . . . . . . . . 24 5.6. DSL Measurements . . . . . . . . . . . . . . . . . . . . 24
5.6.1. L2TP Measurements . . . . . . . . . . . . . . . . . . 25 5.6.1. L2TP Measurements . . . . . . . . . . . . . . . . . . 25
5.6.2. RADIUS Measurements . . . . . . . . . . . . . . . . . 25 5.6.2. RADIUS Measurements . . . . . . . . . . . . . . . . . 25
5.6.3. Ethernet VLAN Tag Measurements . . . . . . . . . . . 26 5.6.3. Ethernet VLAN Tag Measurements . . . . . . . . . . . 26
5.6.4. ATM Virtual Circuit Measurements . . . . . . . . . . 27 5.6.4. ATM Virtual Circuit Measurements . . . . . . . . . . 26
6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 27 6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 27
6.1. Measurement Data Privacy Model . . . . . . . . . . . . . 27 6.1. Measurement Data Privacy Model . . . . . . . . . . . . . 27
6.2. LIS Privacy Requirements . . . . . . . . . . . . . . . . 28 6.2. LIS Privacy Requirements . . . . . . . . . . . . . . . . 27
6.3. Measurement Data and Location URIs . . . . . . . . . . . 28 6.3. Measurement Data and Location URIs . . . . . . . . . . . 28
6.4. Third-Party-Provided Measurement Data . . . . . . . . . . 28 6.4. Third-Party-Provided Measurement Data . . . . . . . . . . 28
7. Security Considerations . . . . . . . . . . . . . . . . . . . 29 7. Security Considerations . . . . . . . . . . . . . . . . . . . 28
7.1. Threat Model . . . . . . . . . . . . . . . . . . . . . . 29 7.1. Threat Model . . . . . . . . . . . . . . . . . . . . . . 29
7.1.1. Acquiring Location Information Without Authorization 29 7.1.1. Acquiring Location Information Without Authorization 29
7.1.2. Extracting Network Topology Data . . . . . . . . . . 30 7.1.2. Extracting Network Topology Data . . . . . . . . . . 30
7.1.3. Lying By Proxy . . . . . . . . . . . . . . . . . . . 31 7.1.3. Lying By Proxy . . . . . . . . . . . . . . . . . . . 30
7.1.4. Measurement Replay . . . . . . . . . . . . . . . . . 32 7.1.4. Measurement Replay . . . . . . . . . . . . . . . . . 31
7.1.5. Environment Spoofing . . . . . . . . . . . . . . . . 32 7.1.5. Environment Spoofing . . . . . . . . . . . . . . . . 32
7.2. Mitigation . . . . . . . . . . . . . . . . . . . . . . . 34 7.2. Mitigation . . . . . . . . . . . . . . . . . . . . . . . 33
7.2.1. Measurement Validation . . . . . . . . . . . . . . . 34 7.2.1. Measurement Validation . . . . . . . . . . . . . . . 34
7.2.1.1. Effectiveness . . . . . . . . . . . . . . . . . . 34 7.2.1.1. Effectiveness . . . . . . . . . . . . . . . . . . 34
7.2.1.2. Limitations (Unique Observer) . . . . . . . . . . 35 7.2.1.2. Limitations (Unique Observer) . . . . . . . . . . 35
7.2.2. Location Validation . . . . . . . . . . . . . . . . . 36 7.2.2. Location Validation . . . . . . . . . . . . . . . . . 35
7.2.2.1. Effectiveness . . . . . . . . . . . . . . . . . . 36 7.2.2.1. Effectiveness . . . . . . . . . . . . . . . . . . 36
7.2.2.2. Limitations . . . . . . . . . . . . . . . . . . . 36 7.2.2.2. Limitations . . . . . . . . . . . . . . . . . . . 36
7.2.3. Supporting Observations . . . . . . . . . . . . . . . 37 7.2.3. Supporting Observations . . . . . . . . . . . . . . . 37
7.2.3.1. Effectiveness . . . . . . . . . . . . . . . . . . 37 7.2.3.1. Effectiveness . . . . . . . . . . . . . . . . . . 37
7.2.3.2. Limitations . . . . . . . . . . . . . . . . . . . 38 7.2.3.2. Limitations . . . . . . . . . . . . . . . . . . . 37
7.2.4. Attribution . . . . . . . . . . . . . . . . . . . . . 38 7.2.4. Attribution . . . . . . . . . . . . . . . . . . . . . 38
7.2.5. Stateful Correlation of Location Requests . . . . . . 39 7.2.5. Stateful Correlation of Location Requests . . . . . . 39
8. Measurement Schemas . . . . . . . . . . . . . . . . . . . . . 40 8. Measurement Schemas . . . . . . . . . . . . . . . . . . . . . 39
8.1. Measurement Container Schema . . . . . . . . . . . . . . 40 8.1. Measurement Container Schema . . . . . . . . . . . . . . 39
8.2. Measurement Source Schema . . . . . . . . . . . . . . . . 42 8.2. Measurement Source Schema . . . . . . . . . . . . . . . . 41
8.3. Base Type Schema . . . . . . . . . . . . . . . . . . . . 43 8.3. Base Type Schema . . . . . . . . . . . . . . . . . . . . 42
8.4. LLDP Measurement Schema . . . . . . . . . . . . . . . . . 45 8.4. LLDP Measurement Schema . . . . . . . . . . . . . . . . . 45
8.5. DHCP Measurement Schema . . . . . . . . . . . . . . . . . 46 8.5. DHCP Measurement Schema . . . . . . . . . . . . . . . . . 46
8.6. WiFi Measurement Schema . . . . . . . . . . . . . . . . . 48 8.6. WiFi Measurement Schema . . . . . . . . . . . . . . . . . 47
8.7. Cellular Measurement Schema . . . . . . . . . . . . . . . 51 8.7. Cellular Measurement Schema . . . . . . . . . . . . . . . 51
8.8. GNSS Measurement Schema . . . . . . . . . . . . . . . . . 54 8.8. GNSS Measurement Schema . . . . . . . . . . . . . . . . . 53
8.9. DSL Measurement Schema . . . . . . . . . . . . . . . . . 56 8.9. DSL Measurement Schema . . . . . . . . . . . . . . . . . 55
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 57 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 57
9.1. IANA Registry for GNSS Types . . . . . . . . . . . . . . 57 9.1. IANA Registry for GNSS Types . . . . . . . . . . . . . . 57
9.2. URN Sub-Namespace Registration for 9.2. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc . . . . . . . 59 urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc . . . . . . . 58
9.3. URN Sub-Namespace Registration for 9.3. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm . . . . . . . . . . . . 59 urn:ietf:params:xml:ns:geopriv:lm . . . . . . . . . . . . 59
9.4. URN Sub-Namespace Registration for 9.4. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:basetypes . . . . . . . 60 urn:ietf:params:xml:ns:geopriv:lm:basetypes . . . . . . . 59
9.5. URN Sub-Namespace Registration for 9.5. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:lldp . . . . . . . . . 61 urn:ietf:params:xml:ns:geopriv:lm:lldp . . . . . . . . . 60
9.6. URN Sub-Namespace Registration for 9.6. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:dhcp . . . . . . . . . 61 urn:ietf:params:xml:ns:geopriv:lm:dhcp . . . . . . . . . 61
9.7. URN Sub-Namespace Registration for 9.7. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:wifi . . . . . . . . . 62 urn:ietf:params:xml:ns:geopriv:lm:wifi . . . . . . . . . 62
9.8. URN Sub-Namespace Registration for 9.8. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:cell . . . . . . . . . 63 urn:ietf:params:xml:ns:geopriv:lm:cell . . . . . . . . . 62
9.9. URN Sub-Namespace Registration for 9.9. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:gnss . . . . . . . . . 63 urn:ietf:params:xml:ns:geopriv:lm:gnss . . . . . . . . . 63
9.10. URN Sub-Namespace Registration for 9.10. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:dsl . . . . . . . . . . 64 urn:ietf:params:xml:ns:geopriv:lm:dsl . . . . . . . . . . 64
9.11. XML Schema Registration for Measurement Source Schema . . 65 9.11. XML Schema Registration for Measurement Source Schema . . 64
9.12. XML Schema Registration for Measurement Container Schema 65 9.12. XML Schema Registration for Measurement Container Schema 65
9.13. XML Schema Registration for Base Types Schema . . . . . . 65 9.13. XML Schema Registration for Base Types Schema . . . . . . 65
9.14. XML Schema Registration for LLDP Schema . . . . . . . . . 66 9.14. XML Schema Registration for LLDP Schema . . . . . . . . . 65
9.15. XML Schema Registration for DHCP Schema . . . . . . . . . 66 9.15. XML Schema Registration for DHCP Schema . . . . . . . . . 65
9.16. XML Schema Registration for WiFi Schema . . . . . . . . . 66 9.16. XML Schema Registration for WiFi Schema . . . . . . . . . 66
9.17. XML Schema Registration for Cellular Schema . . . . . . . 66 9.17. XML Schema Registration for Cellular Schema . . . . . . . 66
9.18. XML Schema Registration for GNSS Schema . . . . . . . . . 67 9.18. XML Schema Registration for GNSS Schema . . . . . . . . . 66
9.19. XML Schema Registration for DSL Schema . . . . . . . . . 67 9.19. XML Schema Registration for DSL Schema . . . . . . . . . 66
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 67 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 67
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 67 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 67
11.1. Normative References . . . . . . . . . . . . . . . . . . 67 11.1. Normative References . . . . . . . . . . . . . . . . . . 67
11.2. Informative References . . . . . . . . . . . . . . . . . 69 11.2. Informative References . . . . . . . . . . . . . . . . . 69
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 70
1. Introduction 1. Introduction
A location configuration protocol (LCP) provides a means for a Device A location configuration protocol (LCP) provides a means for a Device
to request information about its physical location from an access to request information about its physical location from an access
skipping to change at page 5, line 7 skipping to change at page 5, line 7
2. Conventions used in this document 2. Conventions used in this document
The terms LIS and Device are used in this document in a manner The terms LIS and Device are used in this document in a manner
consistent with the usage in [RFC5985]. consistent with the usage in [RFC5985].
This document also uses the following definitions: This document also uses the following definitions:
Location Measurement: An observation about the physical properties Location Measurement: An observation about the physical properties
of a particular Device's network access. The result of a location of a particular Device's network access. The result of a location
measurement-\u002D"location-related measurement data", or simply measurement - "location-related measurement data", or simply
"measurement data" given sufficient context-\u002Dcan be used to "measurement data" given sufficient context - can be used to
determine the location of a Device. Location-related measurement determine the location of a Device. Location-related measurement
data does not identify a Device; measurement data can change with data does not identify a Device; measurement data can change with
time if the location of the Device also changes. time if the location of the Device also changes.
Location-related measurement data does not necessarily contain Location-related measurement data does not necessarily contain
location information directly, but it can be used in combination location information directly, but it can be used in combination
with contextual knowledge of the network, or algorithms to derive with contextual knowledge of the network, or algorithms to derive
location information. Examples of location-related measurement location information. Examples of location-related measurement
data are: radio signal strength or timing measurements, Ethernet data are: radio signal strength or timing measurements, Ethernet
switch and port identifiers. switch and port identifiers.
Location-related measurement data can be considered sighting Location-related measurement data can be considered sighting
information, based on the definition in [RFC3693]. information, based on the definition in [RFC3693].
Location Estimate: The result of location determination, a location Location Estimate: A location estimate is an approximation of where
estimate is an approximation of where the Device is located. the Device is located. Location estimates are derived from
Location estimates are subject to uncertainty, which arise from location measurements. Location estimates are subject to
errors in measurement results. uncertainty, which arise from errors in measurement results.
GNSS: Global Navigation Satellite System. A satellite-based system GNSS: Global Navigation Satellite System. A satellite-based system
that provides positioning and time information. For example, the that provides positioning and time information. For example, the
US Global Positioning System (GPS) or the European Galileo system. US Global Positioning System (GPS) or the European Galileo system.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. Location-Related Measurements in LCPs 3. Location-Related Measurements in LCPs
skipping to change at page 6, line 25 skipping to change at page 6, line 25
ignored. The measurements defined in this document follow this rule; ignored. The measurements defined in this document follow this rule;
extensions that could result in backward incompatibility MUST be extensions that could result in backward incompatibility MUST be
added as new measurement definitions rather than extensions to added as new measurement definitions rather than extensions to
existing types. existing types.
Multiple sets of measurement data, either of the same type or from Multiple sets of measurement data, either of the same type or from
different sources can be included in the "measurements" element. See different sources can be included in the "measurements" element. See
Section 4.1.1 for details on repetition of this element. Section 4.1.1 for details on repetition of this element.
Use of location-related measurement data is at the discretion of the Use of location-related measurement data is at the discretion of the
LIS, but the "method" parameter in the PIDF-LO SHOULD be adjusted to LIS, but the "method" parameter in the Presence Information Data
Format - Location Object (PIDF-LO) [RFC4119] SHOULD be adjusted to
reflect the method used. reflect the method used.
Location-related measurement data need not be provided exclusively by Location-related measurement data need not be provided exclusively by
Devices. A third party location requester can request location Devices. A third party location requester can request location
information using measurement data, if they are able and authorized. information using measurement data, if they are able and authorized.
There are privacy considerations relating to the use of measurements There are privacy considerations relating to the use of measurements
by third parties, which are discussed in Section 6.4. by third parties, which are discussed in Section 6.4.
Location-related measurement data and its use presents a number of Location-related measurement data and its use presents a number of
security challenges. These are described in more detail in security challenges. These are described in more detail in
skipping to change at page 7, line 25 skipping to change at page 7, line 25
Figure 2: Measurement Example Figure 2: Measurement Example
4.1. Measurement Container 4.1. Measurement Container
The "measurement" element is used to encapsulate measurement data The "measurement" element is used to encapsulate measurement data
that is collected at a certain point in time. It contains time-based that is collected at a certain point in time. It contains time-based
attributes that are common to all forms of measurement data, and attributes that are common to all forms of measurement data, and
permits the inclusion of arbitrary measurement data. permits the inclusion of arbitrary measurement data.
This container can be added to any request for location information, This container can be added to a request for location information in
such as a HELD location request [RFC5985]. any protocol capable of carrying XML, such as a HELD location request
[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 is optional to avoid forcing an arbitrary choice The "time" attribute is optional to avoid forcing an arbitrary choice
skipping to change at page 9, line 10 skipping to change at page 9, line 16
appropriate. appropriate.
The "rmsError" and "samples" elements are added as attributes of The "rmsError" and "samples" elements are added as attributes of
specific measurement data types. specific measurement data types.
4.2.1. Time RMS Error 4.2.1. Time RMS Error
Measurement of time can be significant in certain circumstances. The Measurement of time can be significant in certain circumstances. The
GNSS measurements included in this document are one such case where a GNSS measurements included in this document are one such case where a
small error in time can result in a large error in location. Factors small error in time can result in a large error in location. Factors
such as clock drift and errors in time sychronization can result in such as clock drift and errors in time synchronization can result in
small, but significant, time errors. Including an indication of the small, but significant, time errors. Including an indication of the
quality of the time can be helpful. quality of the time can be helpful.
An optional "timeError" attribute can be added to the "measurement" An optional "timeError" attribute can be added to the "measurement"
element to indicate the RMS error in time. "timeError" indicates an element to indicate the RMS error in time. "timeError" indicates an
upper bound on the time RMS error in seconds. upper bound on the time RMS error in seconds.
The "timeError" attribute does not apply where multiple samples of a The "timeError" attribute does not apply where multiple samples of a
measurement is taken over time. If multiple samples are taken, each measurement are taken over time. If multiple samples are taken, each
SHOULD be included in a different "measurement" element. SHOULD be included in a different "measurement" element.
4.3. Measurement Request 4.3. Measurement Request
A measurement request is used by a protocol peer to describe a set of A measurement request is used by a protocol peer to describe a set of
measurement data that it desires. A "measurementRequest" element is measurement data that it desires. A "measurementRequest" element is
defined that can be included in a protocol exchange. defined that can be included in a protocol exchange.
For instance, a LIS can use a measurement request in HELD responses. For instance, a LIS can use a measurement request in HELD responses.
If the LIS is unable to provide location information, but it believes If the LIS is unable to provide location information, but it believes
skipping to change at page 9, line 48 skipping to change at page 10, line 11
The "measurement" element can be repeated to request multiple (or The "measurement" element can be repeated to request multiple (or
alternative) measurement types. alternative) measurement types.
Additional XML content might be defined for a particular measurement Additional XML content might be defined for a particular measurement
type that is used to further refine a request. These elements either type that is used to further refine a request. These elements either
constrain what is requested or specify optional components of the constrain what is requested or specify optional components of the
measurement data that are needed. These are defined along with the measurement data that are needed. These are defined along with the
specific measurement type. specific measurement type.
In the HELD protocol, the inclusion of a measurement request in a In the HELD protocol, the inclusion of a measurement request in an
error response with a code of "locationUnknown" indicates that the error response with a code of "locationUnknown" indicates that the
LIS believes that providing the indicated measurements would increase LIS believes that providing the indicated measurements would increase
the likelihood of a subsequent request being successful. the likelihood of a subsequent request being successful.
The following example shows a HELD error response that indicates that The following example shows a HELD error response that indicates that
WiFi measurement data would be useful if a later request were made. WiFi measurement data would be useful if a later request were made.
Additional elements indicate that received signal strength for an Additional elements indicate that received signal strength for an
802.11n access point is requested. 802.11n access point is requested.
<error xmlns="urn:ietf:params:xml:ns:geopriv:held" <error xmlns="urn:ietf:params:xml:ns:geopriv:held"
skipping to change at page 13, line 5 skipping to change at page 12, line 47
</gs:Circle> </gs:Circle>
</gp:location-info> </gp:location-info>
<gp:usage-rules/> <gp:usage-rules/>
<gp:method>Cell</gp:method> <gp:method>Cell</gp:method>
<lmsrc:source>lis</lmsrc:source> <lmsrc:source>lis</lmsrc:source>
</gp:geopriv> </gp:geopriv>
</status> </status>
</tuple> </tuple>
</presence> </presence>
PIDF-LO document with source labels
5. Location-Related Measurement Data Types 5. Location-Related Measurement Data Types
This document defines location-related measurement data types for a This document defines location-related measurement data types for a
range of common network types. range of common network types.
All included measurement data definitions allow for arbitrary All included measurement data definitions allow for arbitrary
extension in the corresponding schema. As new parameters that are extension in the corresponding schema. As new parameters that are
applicable to location determination are added, these can be added as applicable to location determination are added, these can be added as
new XML elements in a unique namespace. Though many of the new XML elements in a unique namespace. Though many of the
underlying protocols support extension, creation of specific XML- underlying protocols support extension, creation of specific XML-
based extensions to the measurement format is favored over based extensions to the measurement format is favored over
accomodating protocol-specific extensions in generic containers. accommodating protocol-specific extensions in generic containers.
5.1. LLDP Measurements 5.1. LLDP Measurements
Link-Layer Discovery Protocol (LLDP) [IEEE.8021AB] messages are sent Link-Layer Discovery Protocol (LLDP) [IEEE.8021AB] messages are sent
between adjacent nodes in an IEEE 802 network (e.g. wired Ethernet, between adjacent nodes in an IEEE 802 network (e.g. wired Ethernet,
WiFi, 802.16). These messages all contain identification information WiFi, 802.16). These messages all contain identification information
for the sending node, which can be used to determine location for the sending node, which can be used to determine location
information. A Device that receives LLDP messages can report this information. A Device that receives LLDP messages can report this
information as a location-related measurement to the LIS, which is information as a location-related measurement to the LIS, which is
then able to use the measurement data in determining the location of then able to use the measurement data in determining the location of
skipping to change at page 14, line 23 skipping to change at page 14, line 18
5.2. DHCP Relay Agent Information Measurements 5.2. DHCP Relay Agent Information Measurements
The DHCP Relay Agent Information option [RFC3046] provides The DHCP Relay Agent Information option [RFC3046] provides
measurement data about the network attachment of a Device. This measurement data about the network attachment of a Device. This
measurement data can be included in the "dhcp-rai" element. measurement data can be included in the "dhcp-rai" element.
The elements in the DHCP relay agent information options are opaque The elements in the DHCP relay agent information options are opaque
data types assigned by the DHCP relay agent. The three items are all data types assigned by the DHCP relay agent. The three items are all
optional: circuit identifier ("circuit", [RFC3046]), remote optional: circuit identifier ("circuit", [RFC3046]), remote
identifier ("remote", [RFC3046], [RFC4649]) and subscriber identifier identifier ("remote", Remote ID [RFC3046], or remote-id [RFC4649])
("subscriber", [RFC3993], [RFC4580]). The DHCPv6 remote identifier and subscriber identifier ("subscriber", subscriber-id [RFC3993],
has an associated enterprise number [IANA.enterprise] as an XML Subscriber-ID [RFC4580]). The DHCPv6 remote-id has an associated
attribute. enterprise number [IANA.enterprise] as an XML attribute.
<measurements xmlns="urn:ietf:params:xml:ns:geopriv:lm" <measurements xmlns="urn:ietf:params:xml:ns:geopriv:lm"
time="2008-04-29T14:33:58"> time="2008-04-29T14:33:58">
<dhcp-rai xmlns="urn:ietf:params:xml:ns:geopriv:lm:dhcp"> <dhcp-rai xmlns="urn:ietf:params:xml:ns:geopriv:lm:dhcp">
<giaddr>::ffff:192.0.2.158</giaddr> <giaddr>::ffff:192.0.2.158</giaddr>
<circuit>108b</circuit> <circuit>108b</circuit>
</dhcp-rai> </dhcp-rai>
</measurements> </measurements>
Figure 5: DHCP Relay Agent Information Measurement Example Figure 5: DHCP Relay Agent Information Measurement Example
skipping to change at page 16, line 37 skipping to change at page 16, line 27
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
introducted the radio interface, or PHY; e.g. "a", "b", "g", or introduced the radio interface, or PHY; e.g. "a", "b", "g", or
"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
skipping to change at page 20, line 29 skipping to change at page 20, line 14
<servingCell> <servingCell>
<sid>15892</sid><nid>4723</nid><baseid>12</baseid> <sid>15892</sid><nid>4723</nid><baseid>12</baseid>
</servingCell> </servingCell>
<observedCell> <observedCell>
<sid>15892</sid><nid>4723</nid><baseid>13</baseid> <sid>15892</sid><nid>4723</nid><baseid>13</baseid>
</observedCell> </observedCell>
</cellular> </cellular>
</measurements> </measurements>
Code division multiple access (CDMA) cells are not identified by Code division multiple access (CDMA) cells are not identified by
PLMN, instead these usea 15-bit system id (sid), a 16-bit network id PLMN, instead these use a 15-bit system id (sid), a 16-bit network id
(nid) and a 16-bit base station id (baseid). (nid) and a 16-bit base station id (baseid).
Figure 10: Example CDMA Cellular Measurement Figure 10: Example CDMA Cellular Measurement
In general a cellular Device will be attached to the cellular network In general a cellular Device will be attached to the cellular network
and so the notion of a serving cell exists. Cellular network also and so the notion of a serving cell exists. Cellular network also
provide overlap between neighbouring sites, so a mobile Device can provide overlap between neighbouring sites, so a mobile Device can
hear more than one cell. The measurement schema supports sending hear more than one cell. The measurement schema supports sending
both the serving cell and any other cells that the mobile might be both the serving cell and any other cells that the mobile might be
able to hear. In some cases, the Device may simply be listening to able to hear. In some cases, the Device may simply be listening to
skipping to change at page 25, line 25 skipping to change at page 25, line 12
necessary for location information to be correctly generated. The necessary for location information to be correctly generated. The
ISP LIS needs to acquire location information from the infrastructure ISP LIS needs to acquire location information from the infrastructure
provider. However, since the infrastructure provider could have no provider. However, since the infrastructure provider could have no
knowledge of Device identifiers, it can only identify a stream of knowledge of Device identifiers, it can only identify a stream of
data that is sent to the ISP. This is resolved by passing data that is sent to the ISP. This is resolved by passing
measurement data relating to the Device to a LIS operated by the measurement data relating to the Device to a LIS operated by the
infrastructure provider. infrastructure provider.
5.6.1. L2TP Measurements 5.6.1. L2TP Measurements
Layer 2 Tunneling Protocol (L2TP) is a common means of linking the Layer 2 Tunneling Protocol (L2TP) [RFC2661] is a common means of
infrastructure provider and the ISP. The infrastructure provider LIS linking the infrastructure provider and the ISP. The infrastructure
requires measurement data that identifies a single L2TP tunnel, from provider LIS requires measurement data that identifies a single L2TP
which it can generate location information. Figure 13 shows an tunnel, from which it can generate location information. Figure 13
example L2TP measurement. shows an example L2TP measurement.
<measurements xmlns="urn:ietf:params:xml:ns:geopriv:lm" <measurements xmlns="urn:ietf:params:xml:ns:geopriv:lm"
time="2008-04-29T14:33:58"> time="2008-04-29T14:33:58">
<dsl xmlns="urn:ietf:params:xml:ns:geopriv:lm:dsl"> <dsl xmlns="urn:ietf:params:xml:ns:geopriv:lm:dsl">
<l2tp> <l2tp>
<src>192.0.2.10</src> <src>192.0.2.10</src>
<dest>192.0.2.61</dest> <dest>192.0.2.61</dest>
<session>528</session> <session>528</session>
</l2tp> </l2tp>
</dsl> </dsl>
skipping to change at page 28, line 30 skipping to change at page 28, line 10
contains it, rules regarding data retention are not necessary. A LIS contains it, rules regarding data retention are not necessary. A LIS
MUST discard location-related measurement data after servicing a MUST discard location-related measurement data after servicing a
request, unless the Device grants permission to use that information request, unless the Device grants permission to use that information
for other purposes. for other purposes.
6.3. Measurement Data and Location URIs 6.3. Measurement Data and Location URIs
A LIS MAY use measurement data provided by the Device to serve A LIS MAY use measurement data provided by the Device to serve
requests to location URIs, if the Device permits it. A Device requests to location URIs, if the Device permits it. A Device
permits this by including measurement data in a request that permits this by including measurement data in a request that
explcitly requests a location URI. By requesting a location URI, the explicitly requests a location URI. By requesting a location URI,
Device grants permission for the LIS to use the measurement data in the Device grants permission for the LIS to use the measurement data
serving requests to that URI. in serving requests to that URI.
Note: In HELD, the "any" type is not an explicit request for a Note: In HELD, the "any" type is not an explicit request for a
location URI, though a location URI might be provided. location URI, though a location URI might be provided.
The usefulness of measurement data that is provided in this fashion The usefulness of measurement data that is provided in this fashion
is limited. The measurement data is only valid at the time that it is limited. The measurement data is only valid at the time that it
was acquired by the Device. At the time that a request is made to a was acquired by the Device. At the time that a request is made to a
location URI, the Device might have moved, rendering the measurement location URI, the Device might have moved, rendering the measurement
data incorrect. data incorrect.
skipping to change at page 30, line 18 skipping to change at page 30, line 5
such authorization checks if the association between measurement data such authorization checks if the association between measurement data
and Target Device is not validated by a LIS. and Target Device is not validated by a LIS.
A LIS can be coerced into providing location information for a Device A LIS can be coerced into providing location information for a Device
that a location recipient is not authorized to receive. A request that a location recipient is not authorized to receive. A request
identifies one Device (implicitly or explicitly), but measurement identifies one Device (implicitly or explicitly), but measurement
data is provided for another Device. If the LIS does not check that data is provided for another Device. If the LIS does not check that
the measurement data is for the identified Device, it could the measurement data is for the identified Device, it could
incorrectly authorize the request. incorrectly authorize the request.
By using unvalidated measurement data to generate a response, the LIS By using unverified measurement data to generate a response, the LIS
provides information about a Device without appropriate provides information about a Device without appropriate
authorization. authorization.
The feasibility of this attack depends on the availability of The feasibility of this attack depends on the availability of
information that links a Device with measurement data. In some information that links a Device with measurement data. In some
cases, measurement data that is correlated with a target is readily cases, measurement data that is correlated with a target is readily
available. For instance, LLDP measurements (Section 5.1) are available. For instance, LLDP measurements (Section 5.1) are
broadcast to all nodes on the same network segment. An attacker on broadcast to all nodes on the same network segment. An attacker on
that network segment can easily gain measurement data that relates a that network segment can easily gain measurement data that relates a
Device with measurements. Device with measurements.
skipping to change at page 33, line 11 skipping to change at page 32, line 45
Measurement of radio signal characteristics is especially vulnerable Measurement of radio signal characteristics is especially vulnerable
since an adversary need only be in the general vicinity of the Device since an adversary need only be in the general vicinity of the Device
and be able to transmit a signal. For instance, a GNSS spoofer is and be able to transmit a signal. For instance, a GNSS spoofer is
able to produce fake signals that claim to be transmitted by any able to produce fake signals that claim to be transmitted by any
satellite or set of satellites (see [GPS.SPOOF]). satellite or set of satellites (see [GPS.SPOOF]).
Measurements that require direct interaction increases the complexity Measurements that require direct interaction increases the complexity
of the attack. For measurements relating to the communication of the attack. For measurements relating to the communication
medium, a third party cannot avoid direct interaction, they need only medium, a third party cannot avoid direct interaction, they need only
be on the comminications path (that is, man in the middle). be on the communications path (that is, man in the middle).
Even if the entity that is interacted with is authenticated, this Even if the entity that is interacted with is authenticated, this
does not provide any assurance about the integrity of measurement does not provide any assurance about the integrity of measurement
data. For instance, the Device might authenticate the identity of a data. For instance, the Device might authenticate the identity of a
radio transmitter through the use of cryptographic means and obtain radio transmitter through the use of cryptographic means and obtain
signal strength measurements for that transmitter. Radio signal signal strength measurements for that transmitter. Radio signal
strength is trivial for an attacker to increase simply by receiving strength is trivial for an attacker to increase simply by receiving
and amplifying the raw signal; it is not necessary for the attacker and amplifying the raw signal; it is not necessary for the attacker
to be able to understand the signal content. to be able to understand the signal content.
skipping to change at page 40, line 44 skipping to change at page 40, line 24
<xs:appinfo <xs:appinfo
source="urn:ietf:params:xml:schema:geopriv:lm"> source="urn:ietf:params:xml:schema:geopriv:lm">
</xs:appinfo> </xs:appinfo>
<xs:documentation source="http://www.ietf.org/rfc/rfcXXXX.txt"> <xs:documentation source="http://www.ietf.org/rfc/rfcXXXX.txt">
<!-- [[NOTE TO RFC-EDITOR: Please replace above URL with URL of <!-- [[NOTE TO RFC-EDITOR: Please replace above URL with URL of
published RFC and remove this note.]] --> published RFC and remove this note.]] -->
This schema defines a framework for location measurements. This schema defines a framework for location measurements.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
<xs:import namespace="urn:ietf:params:xml:ns:geopriv:lm:basetypes"/> <xs:import namespace="urn:ietf:params:xml:ns:geopriv:lm:basetypes"/>
<xs:element name="measurements"> <xs:element name="measurements">
<xs:complexType> <xs:complexType>
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType"> <xs:restriction base="xs:anyType">
<xs:sequence> <xs:sequence>
<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="time" type="xs:dateTime"/> <xs:attribute name="time" type="xs:dateTime"/>
skipping to change at page 46, line 13 skipping to change at page 45, line 42
<xs:appinfo <xs:appinfo
source="urn:ietf:params:xml:schema:geopriv:lm:lldp"> source="urn:ietf:params:xml:schema:geopriv:lm:lldp">
</xs:appinfo> </xs:appinfo>
<xs:documentation source="http://www.ietf.org/rfc/rfcXXXX.txt"> <xs:documentation source="http://www.ietf.org/rfc/rfcXXXX.txt">
<!-- [[NOTE TO RFC-EDITOR: Please replace above URL with URL of <!-- [[NOTE TO RFC-EDITOR: Please replace above URL with URL of
published RFC and remove this note.]] --> published RFC and remove this note.]] -->
This schema defines a set of LLDP location measurements. This schema defines a set of LLDP location measurements.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
<xs:import namespace="urn:ietf:params:xml:ns:geopriv:lm:basetypes"/> <xs:import namespace="urn:ietf:params:xml:ns:geopriv:lm:basetypes"/>
<xs:element name="lldp" type="lldp:lldpMeasurementType"/> <xs:element name="lldp" type="lldp:lldpMeasurementType"/>
<xs:complexType name="lldpMeasurementType"> <xs:complexType name="lldpMeasurementType">
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType"> <xs:restriction base="xs:anyType">
<xs:sequence> <xs:sequence>
<xs:element name="chassis" type="lldp:lldpDataType"/> <xs:element name="chassis" type="lldp:lldpDataType"/>
<xs:element name="port" type="lldp:lldpDataType"/> <xs:element name="port" type="lldp:lldpDataType"/>
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
skipping to change at page 47, line 24 skipping to change at page 47, line 5
<xs:appinfo <xs:appinfo
source="urn:ietf:params:xml:schema:geopriv:lm:dhcp"> source="urn:ietf:params:xml:schema:geopriv:lm:dhcp">
</xs:appinfo> </xs:appinfo>
<xs:documentation source="http://www.ietf.org/rfc/rfcXXXX.txt"> <xs:documentation source="http://www.ietf.org/rfc/rfcXXXX.txt">
<!-- [[NOTE TO RFC-EDITOR: Please replace above URL with URL of <!-- [[NOTE TO RFC-EDITOR: Please replace above URL with URL of
published RFC and remove this note.]] --> published RFC and remove this note.]] -->
This schema defines a set of DHCP location measurements. This schema defines a set of DHCP location measurements.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
<xs:import namespace="urn:ietf:params:xml:ns:geopriv:lm:basetypes"/> <xs:import namespace="urn:ietf:params:xml:ns:geopriv:lm:basetypes"/>
<!-- DHCP Relay Agent Information Option --> <!-- DHCP Relay Agent Information Option -->
<xs:element name="dhcp-rai" type="dhcp:dhcpType"/> <xs:element name="dhcp-rai" type="dhcp:dhcpType"/>
<xs:complexType name="dhcpType"> <xs:complexType name="dhcpType">
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType"> <xs:restriction base="xs:anyType">
<xs:sequence> <xs:sequence>
<xs:element name="giaddr" type="bt:ipAddressType"/> <xs:element name="giaddr" type="bt:ipAddressType"/>
<xs:element name="circuit" <xs:element name="circuit"
type="xs:hexBinary" minOccurs="0"/> type="xs:hexBinary" minOccurs="0"/>
skipping to change at page 48, line 33 skipping to change at page 48, line 13
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
<xs:annotation> <xs:annotation>
<xs:appinfo <xs:appinfo
source="urn:ietf:params:xml:schema:geopriv:lm:wifi"> source="urn:ietf:params:xml:schema:geopriv:lm:wifi">
802.11 location measurements 802.11 location measurements
</xs:appinfo> </xs:appinfo>
<xs:documentation source="http://www.ietf.org/rfc/rfcXXXX.txt"> <xs:documentation source="http://www.ietf.org/rfc/rfcXXXX.txt">
<!-- [[NOTE TO RFC-EDITOR: Please replace above URL with URL of <!-- [[NOTE TO RFC-EDITOR: Please replace above URL with URL of
published RFC and remove this note.]] --> published RFC and remove this note.]] -->
This schema defines a basic set of 802.11 location measurements. This schema defines a basic set of 802.11 location measurements.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
<xs:import namespace="urn:ietf:params:xml:ns:geopriv:lm:basetypes"/> <xs:import namespace="urn:ietf:params:xml:ns:geopriv:lm:basetypes"/>
<xs:import namespace="http://www.opengis.net/gml"/> <xs:import namespace="http://www.opengis.net/gml"/>
<xs:element name="wifi" type="wifi:wifiNetworkType"/> <xs:element name="wifi" type="wifi:wifiNetworkType"/>
<xs:complexType name="wifiNetworkType"> <xs:complexType name="wifiNetworkType">
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType"> <xs:restriction base="xs:anyType">
<xs:sequence> <xs:sequence>
<xs:element name="nicType" type="xs:token" <xs:element name="nicType" type="xs:token"
minOccurs="0"/> minOccurs="0"/>
skipping to change at page 54, line 36 skipping to change at page 54, line 16
<xs:appinfo <xs:appinfo
source="urn:ietf:params:xml:schema:geopriv:lm:gnss"> source="urn:ietf:params:xml:schema:geopriv:lm:gnss">
</xs:appinfo> </xs:appinfo>
<xs:documentation source="http://www.ietf.org/rfc/rfcXXXX.txt"> <xs:documentation source="http://www.ietf.org/rfc/rfcXXXX.txt">
<!-- [[NOTE TO RFC-EDITOR: Please replace above URL with URL of <!-- [[NOTE TO RFC-EDITOR: Please replace above URL with URL of
published RFC and remove this note.]] --> published RFC and remove this note.]] -->
This schema defines a set of GNSS location measurements This schema defines a set of GNSS location measurements
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
<xs:import namespace="urn:ietf:params:xml:ns:geopriv:lm:basetypes"/> <xs:import namespace="urn:ietf:params:xml:ns:geopriv:lm:basetypes"/>
<!-- GNSS --> <!-- GNSS -->
<xs:element name="gnss" type="gnss:gnssMeasurementType"> <xs:element name="gnss" type="gnss:gnssMeasurementType">
<xs:unique name="gnssSatellite"> <xs:unique name="gnssSatellite">
<xs:selector xpath="sat"/> <xs:selector xpath="sat"/>
<xs:field xpath="@num"/> <xs:field xpath="@num"/>
</xs:unique> </xs:unique>
</xs:element> </xs:element>
<xs:complexType name="gnssMeasurementType"> <xs:complexType name="gnssMeasurementType">
skipping to change at page 56, line 29 skipping to change at page 56, line 10
source="urn:ietf:params:xml:schema:geopriv:lm:dsl"> source="urn:ietf:params:xml:schema:geopriv:lm:dsl">
DSL measurement definitions DSL measurement definitions
</xs:appinfo> </xs:appinfo>
<xs:documentation source="http://www.ietf.org/rfc/rfcXXXX.txt"> <xs:documentation source="http://www.ietf.org/rfc/rfcXXXX.txt">
<!-- [[NOTE TO RFC-EDITOR: Please replace above URL with URL of <!-- [[NOTE TO RFC-EDITOR: Please replace above URL with URL of
published RFC and remove this note.]] --> published RFC and remove this note.]] -->
This schema defines a basic set of DSL location measurements. This schema defines a basic set of DSL location measurements.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
<xs:import namespace="urn:ietf:params:xml:ns:geopriv:lm:basetypes"/> <xs:import namespace="urn:ietf:params:xml:ns:geopriv:lm:basetypes"/>
<xs:element name="dsl" type="dsl:dslVlanType"/> <xs:element name="dsl" type="dsl:dslVlanType"/>
<xs:complexType name="dslVlanType"> <xs:complexType name="dslVlanType">
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType"> <xs:restriction base="xs:anyType">
<xs:choice> <xs:choice>
<xs:element name="l2tp"> <xs:element name="l2tp">
<xs:complexType> <xs:complexType>
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType"> <xs:restriction base="xs:anyType">
skipping to change at page 57, line 50 skipping to change at page 57, line 31
DSL measurement schema DSL measurement schema
9. IANA Considerations 9. IANA Considerations
This section creates a registry for GNSS types (Section 5.5) and This section creates a registry for GNSS types (Section 5.5) and
registers the namespaces and schema defined in Section 8. registers the namespaces and schema defined in Section 8.
9.1. IANA Registry for GNSS Types 9.1. IANA Registry for GNSS Types
This document establishes a new IANA registry for Global Navigation This document establishes a new IANA registry for "Global Navigation
Satellite System (GNSS) types. The registry includes tokens for the Satellite System (GNSS) types". The registry includes tokens for the
GNSS type and for each of the signals within that type. Referring to GNSS type and for each of the signals within that type. Referring to
[RFC5226], this registry operates under "Specification Required" [RFC5226], this registry operates under "Specification Required"
rules. The IESG will appoint an Expert Reviewer who will advise IANA rules. The IESG will appoint an Expert Reviewer who will advise IANA
promptly on each request for a new or updated GNSS type. promptly on each request for a new or updated GNSS type.
Each entry in the registry requires the following information: Each entry in the registry requires the following information:
GNSS name: the name of the GNSS GNSS name: the name of the GNSS
Brief description: a brief description of the GNSS Brief description: a brief description of the GNSS
skipping to change at page 68, line 9 skipping to change at page 67, line 38
Darren Pawson provided expert LTE knowledge. Darren Pawson provided expert LTE knowledge.
11. References 11. References
11.1. Normative References 11.1. Normative References
[ASCII] , "US-ASCII. Coded Character Set - 7-Bit American Standard [ASCII] , "US-ASCII. Coded Character Set - 7-Bit American Standard
Code for Information Interchange. Standard ANSI X3.4-1986, Code for Information Interchange. Standard ANSI X3.4-1986,
ANSI, 1986.", . ANSI, 1986.", .
[DSL.TR025]
Wang, R., "Core Network Architecture Recommendations for
Access to Legacy Data Networks over ADSL", September 1999.
[DSL.TR101]
Cohen, A. and E. Shrum, "Migration to Ethernet-Based DSL
Aggregation", April 2006.
[GPS.ICD] , "Navstar GPS Space Segment/Navigation User Interface", [GPS.ICD] , "Navstar GPS Space Segment/Navigation User Interface",
ICD GPS-200, Apr 2000. ICD GPS-200, Apr 2000.
[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.
[RFC0020] Cerf, V., "ASCII format for network interchange", RFC 20, [IANA.enterprise]
October 1969. IANA, "Private Enterprise Numbers", 2011,
<http://www.iana.org/assignments/enterprise-numbers>.
[IEEE.80211V]
IEEE, "Wireless LAN Medium Access Control (MAC) and
Physical Layer (PHY) specifications - IEEE 802.11 Wireless
Network Management (Draft)", P802.11v D12.0, June 2010.
[IEEE.80211]
IEEE, "Wireless LAN Medium Access Control (MAC) and
Physical Layer (PHY) specifications - IEEE 802.11 Wireless
Network Management", IEEE Std 802.11-2007, June 2007.
[IEEE.8021AB]
IEEE, "IEEE Standard for Local and Metropolitan area
networks, Station and Media Access Control Connectivity
Discovery", IEEE Std 802.1AB-2009, September 2009.
[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.
[RFC3046] Patrick, M., "DHCP Relay Agent Information Option", RFC
3046, January 2001.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, November 2003. 10646", STD 63, RFC 3629, November 2003.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, RFC Resource Identifier (URI): Generic Syntax", STD 66, RFC
3986, January 2005. 3986, January 2005.
[RFC3993] Johnson, R., Palaniappan, T., and M. Stapp, "Subscriber-ID
Suboption for the Dynamic Host Configuration Protocol
(DHCP) Relay Agent Option", RFC 3993, March 2005.
[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 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
IANA Considerations Section in RFCs", BCP 26, RFC 5226, Architecture", RFC 4291, February 2006.
May 2008.
[RFC4580] Volz, B., "Dynamic Host Configuration Protocol for IPv6
(DHCPv6) Relay Agent Subscriber-ID Option", RFC 4580, June
2006.
[RFC4649] Volz, B., "Dynamic Host Configuration Protocol for IPv6
(DHCPv6) Relay Agent Remote-ID Option", RFC 4649, August
2006.
[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",
RFC 5491, March 2009. RFC 5491, March 2009.
[RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC
5985, September 2010. 5985, September 2010.
[TIA-2000.5] [TIA-2000.5]
skipping to change at page 69, line 18 skipping to change at page 69, line 28
[TS.3GPP.23.003] [TS.3GPP.23.003]
3GPP, "Numbering, addressing and identification", 3GPP TS 3GPP, "Numbering, addressing and identification", 3GPP TS
23.003 9.4.0, September 2010. 23.003 9.4.0, September 2010.
11.2. Informative References 11.2. Informative References
[ANSI-TIA-1057] [ANSI-TIA-1057]
ANSI/TIA, "Link Layer Discovery Protocol for Media ANSI/TIA, "Link Layer Discovery Protocol for Media
Endpoint Devices", TIA 1057, April 2006. Endpoint Devices", TIA 1057, April 2006.
[DSL.TR025]
Wang, R., "Core Network Architecture Recommendations for
Access to Legacy Data Networks over ADSL", September 1999.
[DSL.TR101]
Cohen, A. and E. Shrum, "Migration to Ethernet-Based DSL
Aggregation", April 2006.
[GPS.SPOOF] [GPS.SPOOF]
Scott, L., "Anti-Spoofing and Authenticated Signal Scott, L., "Anti-Spoofing and Authenticated Signal
Architectures for Civil Navigation Signals", ION-GNSS Architectures for Civil Navigation Signals", ION-GNSS
Portland, Oregon, 2003. Portland, Oregon, 2003.
[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>.
[IANA.enterprise] [RFC2661] Townsley, W., Valencia, A., Rubens, A., Pall, G., Zorn,
IANA, "Private Enterprise Numbers", 2011, G., and B. Palter, "Layer Two Tunneling Protocol "L2TP"",
<http://www.iana.org/assignments/enterprise-numbers>. RFC 2661, August 1999.
[IEEE.80211V]
IEEE, "Wireless LAN Medium Access Control (MAC) and
Physical Layer (PHY) specifications - IEEE 802.11 Wireless
Network Management (Draft)", P802.11v D12.0, June 2010.
[IEEE.80211]
IEEE, "Wireless LAN Medium Access Control (MAC) and
Physical Layer (PHY) specifications - IEEE 802.11 Wireless
Network Management", IEEE Std 802.11-2007, June 2007.
[IEEE.8021AB]
IEEE, "IEEE Standard for Local and Metropolitan area
networks, Station and Media Access Control Connectivity
Discovery", IEEE Std 802.1AB-2009, September 2009.
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)", RFC "Remote Authentication Dial In User Service (RADIUS)", RFC
2865, June 2000. 2865, June 2000.
[RFC3046] Patrick, M., "DHCP Relay Agent Information Option", RFC
3046, January 2001.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[RFC3693] Cuellar, J., Morris, J., Mulligan, D., Peterson, J., and [RFC3693] Cuellar, J., Morris, J., Mulligan, D., Peterson, J., and
J. Polk, "Geopriv Requirements", RFC 3693, February 2004. J. Polk, "Geopriv Requirements", RFC 3693, February 2004.
[RFC3993] Johnson, R., Palaniappan, T., and M. Stapp, "Subscriber-ID [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
Suboption for the Dynamic Host Configuration Protocol IANA Considerations Section in RFCs", BCP 26, RFC 5226,
(DHCP) Relay Agent Option", RFC 3993, March 2005. May 2008.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
[RFC4580] Volz, B., "Dynamic Host Configuration Protocol for IPv6
(DHCPv6) Relay Agent Subscriber-ID Option", RFC 4580, June
2006.
[RFC4649] Volz, B., "Dynamic Host Configuration Protocol for IPv6
(DHCPv6) Relay Agent Remote-ID Option", RFC 4649, August
2006.
[RFC6155] Winterbottom, J., Thomson, M., Tschofenig, H., and R. [RFC6155] 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)", RFC 6155, March 2011. Delivery (HELD)", RFC 6155, March 2011.
Authors' Addresses Authors' Addresses
Martin Thomson Martin Thomson
Microsoft Microsoft
3210 Porter Drive 3210 Porter Drive
 End of changes. 58 change blocks. 
119 lines changed or deleted 124 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/