draft-ietf-geopriv-held-measurements-02.txt   draft-ietf-geopriv-held-measurements-03.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: April 28, 2011 October 25, 2010 Expires: September 12, 2011 March 11, 2011
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-02 draft-ietf-geopriv-held-measurements-03
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 April 28, 2011. This Internet-Draft will expire on September 12, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 43 skipping to change at page 3, line 43
5.6.3. Ethernet VLAN Tag Measurements . . . . . . . . . . . . 29 5.6.3. Ethernet VLAN Tag Measurements . . . . . . . . . . . . 29
5.6.4. ATM Virtual Circuit Measurements . . . . . . . . . . . 29 5.6.4. ATM Virtual Circuit Measurements . . . . . . . . . . . 29
6. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 29 6. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 29
6.1. Measurement Data Privacy Model . . . . . . . . . . . . . . 30 6.1. Measurement Data Privacy Model . . . . . . . . . . . . . . 30
6.2. LIS Privacy Requirements . . . . . . . . . . . . . . . . . 30 6.2. LIS Privacy Requirements . . . . . . . . . . . . . . . . . 30
6.3. Measurement Data and Location URIs . . . . . . . . . . . . 30 6.3. Measurement Data and Location URIs . . . . . . . . . . . . 30
6.4. Third-Party-Provided Measurement Data . . . . . . . . . . 31 6.4. Third-Party-Provided Measurement Data . . . . . . . . . . 31
7. Security Considerations . . . . . . . . . . . . . . . . . . . 31 7. Security Considerations . . . . . . . . . . . . . . . . . . . 31
7.1. Threat Model . . . . . . . . . . . . . . . . . . . . . . . 31 7.1. Threat Model . . . . . . . . . . . . . . . . . . . . . . . 31
7.1.1. Acquiring Location Information Without 7.1.1. Acquiring Location Information Without
Authorization . . . . . . . . . . . . . . . . . . . . 32 Authorization . . . . . . . . . . . . . . . . . . . . 32
7.1.2. Extracting Network Topology Data . . . . . . . . . . . 33 7.1.2. Extracting Network Topology Data . . . . . . . . . . . 33
7.1.3. Lying By Proxy . . . . . . . . . . . . . . . . . . . . 33 7.1.3. Lying By Proxy . . . . . . . . . . . . . . . . . . . . 33
7.1.4. Measurement Replay . . . . . . . . . . . . . . . . . . 34 7.1.4. Measurement Replay . . . . . . . . . . . . . . . . . . 34
7.1.5. Environment Spoofing . . . . . . . . . . . . . . . . . 35 7.1.5. Environment Spoofing . . . . . . . . . . . . . . . . . 35
7.2. Mitigation . . . . . . . . . . . . . . . . . . . . . . . . 36 7.2. Mitigation . . . . . . . . . . . . . . . . . . . . . . . . 36
7.2.1. Measurement Validation . . . . . . . . . . . . . . . . 37 7.2.1. Measurement Validation . . . . . . . . . . . . . . . . 37
7.2.1.1. Effectiveness . . . . . . . . . . . . . . . . . . 37 7.2.1.1. Effectiveness . . . . . . . . . . . . . . . . . . 37
7.2.1.2. Limitations (Unique Observer) . . . . . . . . . . 37 7.2.1.2. Limitations (Unique Observer) . . . . . . . . . . 37
7.2.2. Location Validation . . . . . . . . . . . . . . . . . 38 7.2.2. Location Validation . . . . . . . . . . . . . . . . . 38
7.2.2.1. Effectiveness . . . . . . . . . . . . . . . . . . 39
7.2.2.2. Limitations . . . . . . . . . . . . . . . . . . . 39 7.2.2.1. Effectiveness . . . . . . . . . . . . . . . . . . 39
7.2.2.2. Limitations . . . . . . . . . . . . . . . . . . . 39
7.2.3. Supporting Observations . . . . . . . . . . . . . . . 39 7.2.3. Supporting Observations . . . . . . . . . . . . . . . 39
7.2.3.1. Effectiveness . . . . . . . . . . . . . . . . . . 40 7.2.3.1. Effectiveness . . . . . . . . . . . . . . . . . . 40
7.2.3.2. Limitations . . . . . . . . . . . . . . . . . . . 40 7.2.3.2. Limitations . . . . . . . . . . . . . . . . . . . 40
7.2.4. Attribution . . . . . . . . . . . . . . . . . . . . . 41 7.2.4. Attribution . . . . . . . . . . . . . . . . . . . . . 41
7.2.5. Stateful Correlation of Location Requests . . . . . . 42 7.2.5. Stateful Correlation of Location Requests . . . . . . 42
8. Measurement Schemas . . . . . . . . . . . . . . . . . . . . . 42 8. Measurement Schemas . . . . . . . . . . . . . . . . . . . . . 42
8.1. Measurement Container Schema . . . . . . . . . . . . . . . 42 8.1. Measurement Container Schema . . . . . . . . . . . . . . . 42
8.2. Measurement Source Schema . . . . . . . . . . . . . . . . 45 8.2. Measurement Source Schema . . . . . . . . . . . . . . . . 45
8.3. Base Type Schema . . . . . . . . . . . . . . . . . . . . . 45 8.3. Base Type Schema . . . . . . . . . . . . . . . . . . . . . 45
8.4. LLDP Measurement Schema . . . . . . . . . . . . . . . . . 48 8.4. LLDP Measurement Schema . . . . . . . . . . . . . . . . . 48
8.5. DHCP Measurement Schema . . . . . . . . . . . . . . . . . 49 8.5. DHCP Measurement Schema . . . . . . . . . . . . . . . . . 49
8.6. WiFi Measurement Schema . . . . . . . . . . . . . . . . . 51 8.6. WiFi Measurement Schema . . . . . . . . . . . . . . . . . 51
8.7. Cellular Measurement Schema . . . . . . . . . . . . . . . 54 8.7. Cellular Measurement Schema . . . . . . . . . . . . . . . 54
8.8. GNSS Measurement Schema . . . . . . . . . . . . . . . . . 57 8.8. GNSS Measurement Schema . . . . . . . . . . . . . . . . . 57
8.9. DSL Measurement Schema . . . . . . . . . . . . . . . . . . 58 8.9. DSL Measurement Schema . . . . . . . . . . . . . . . . . . 58
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 60 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 60
9.1. IANA Registry for GNSS Types . . . . . . . . . . . . . . . 60 9.1. IANA Registry for GNSS Types . . . . . . . . . . . . . . . 60
9.2. URN Sub-Namespace Registration for 9.2. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc . . . . . . . 61 urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc . . . . . . . 61
9.3. URN Sub-Namespace Registration for 9.3. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm . . . . . . . . . . . . 62 urn:ietf:params:xml:ns:geopriv:lm . . . . . . . . . . . . 62
9.4. URN Sub-Namespace Registration for 9.4. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:basetypes . . . . . . . 63 urn:ietf:params:xml:ns:geopriv:lm:basetypes . . . . . . . 63
9.5. URN Sub-Namespace Registration for 9.5. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:lldp . . . . . . . . . . 64 urn:ietf:params:xml:ns:geopriv:lm:lldp . . . . . . . . . . 64
9.6. URN Sub-Namespace Registration for 9.6. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:dhcp . . . . . . . . . . 64 urn:ietf:params:xml:ns:geopriv:lm:dhcp . . . . . . . . . . 64
9.7. URN Sub-Namespace Registration for 9.7. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:wifi . . . . . . . . . . 65 urn:ietf:params:xml:ns:geopriv:lm:wifi . . . . . . . . . . 65
9.8. URN Sub-Namespace Registration for 9.8. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:cell . . . . . . . . . . 66 urn:ietf:params:xml:ns:geopriv:lm:cell . . . . . . . . . . 66
9.9. URN Sub-Namespace Registration for 9.9. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:gnss . . . . . . . . . . 66 urn:ietf:params:xml:ns:geopriv:lm:gnss . . . . . . . . . . 66
9.10. URN Sub-Namespace Registration for 9.10. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:dsl . . . . . . . . . . 67 urn:ietf:params:xml:ns:geopriv:lm:dsl . . . . . . . . . . 67
9.11. XML Schema Registration for Measurement Source Schema . . 68 9.11. XML Schema Registration for Measurement Source Schema . . 68
9.12. XML Schema Registration for Measurement Container 9.12. XML Schema Registration for Measurement Container
Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 68
9.13. XML Schema Registration for Base Types Schema . . . . . . 68 9.13. XML Schema Registration for Base Types Schema . . . . . . 68
9.14. XML Schema Registration for LLDP Schema . . . . . . . . . 68 9.14. XML Schema Registration for LLDP Schema . . . . . . . . . 68
9.15. XML Schema Registration for DHCP Schema . . . . . . . . . 69 9.15. XML Schema Registration for DHCP Schema . . . . . . . . . 69
9.16. XML Schema Registration for WiFi Schema . . . . . . . . . 69 9.16. XML Schema Registration for WiFi Schema . . . . . . . . . 69
9.17. XML Schema Registration for Cellular Schema . . . . . . . 69 9.17. XML Schema Registration for Cellular Schema . . . . . . . 69
9.18. XML Schema Registration for GNSS Schema . . . . . . . . . 70 9.18. XML Schema Registration for GNSS Schema . . . . . . . . . 70
9.19. XML Schema Registration for DSL Schema . . . . . . . . . . 70 9.19. XML Schema Registration for DSL Schema . . . . . . . . . . 70
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 70 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 70
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 70 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 70
11.1. Normative References . . . . . . . . . . . . . . . . . . . 70 11.1. Normative References . . . . . . . . . . . . . . . . . . . 70
11.2. Informative References . . . . . . . . . . . . . . . . . . 71 11.2. Informative References . . . . . . . . . . . . . . . . . . 72
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 73
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
network. A location information server (LIS) is the server that network. A location information server (LIS) is the server that
provides location information; information that is available due to provides location information; information that is available due to
the knowledge about the network and physical environment that is the knowledge about the network and physical environment that is
available to the LIS. available to the LIS.
skipping to change at page 6, line 32 skipping to change at page 6, line 32
or its physical environment. The location-related measurement data or its physical environment. The location-related measurement data
might be unavailable to the LIS; alternatively, the LIS might be able might be unavailable to the LIS; alternatively, the LIS might be able
to acquire the data, but at a higher cost in time or otherwise. to acquire the data, but at a higher cost in time or otherwise.
Providing measurement data gives the LIS more options in determining Providing measurement data gives the LIS more options in determining
location, which could improve the quality of the service provided by location, which could improve the quality of the service provided by
the LIS. Improvements in accuracy are one potential gain, but the LIS. Improvements in accuracy are one potential gain, but
improved response times and lower error rates are also possible. improved response times and lower error rates are also possible.
This document describes a means for a Device to report location- This document describes a means for a Device to report location-
related measurement data to the LIS. Examples based on the HELD related measurement data to the LIS. Examples based on the HELD
[I-D.ietf-geopriv-http-location-delivery] location configuration [RFC5985] location configuration protocol are provided.
protocol are provided.
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 consistent with the usage in [RFC5985].
[I-D.ietf-geopriv-http-location-delivery].
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--"location-related measurement data", or simply measurement--"location-related measurement data", or simply
"measurement data" given sufficient context--can 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.
skipping to change at page 7, line 43 skipping to change at page 7, line 41
that can be carried in the generic container. that can be carried in the generic container.
The simplest example of measurement data conveyance is illustrated by The simplest example of measurement data conveyance is illustrated by
the example message in Figure 1. This shows a HELD location request the example message in Figure 1. This shows a HELD location request
message with an Ethernet switch and port measurement taken using LLDP message with an Ethernet switch and port measurement taken using LLDP
[IEEE.8021AB]. [IEEE.8021AB].
<locationRequest xmlns="urn:ietf:params:xml:ns:geopriv:held"> <locationRequest xmlns="urn:ietf:params:xml:ns:geopriv:held">
<locationType exact="true">civic</locationType> <locationType exact="true">civic</locationType>
<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">
<lldp xmlns="urn:ietf:params:xml:ns:geopriv:lm:lldp"> <lldp xmlns="urn:ietf:params:xml:ns:geopriv:lm:lldp">
<chassis type="4">0a01003c</chassis> <chassis type="4">0a01003c</chassis>
<port type="6">c2</port> <port type="6">c2</port>
</lldp> </lldp>
</measurements> </measurements>
</locationRequest> </locationRequest>
Figure 1: HELD Location Request with Measurement Data
Figure 1: HELD Location Request with Measurement Data
Measurement data that the LIS does not support or understand can be Measurement data that the LIS does not support or understand can be
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.
skipping to change at page 8, line 40 skipping to change at page 8, line 38
4. Location-Related Measurement Data Types 4. Location-Related Measurement Data Types
A common container is defined for the expression of location A common container is defined for the expression of location
measurement data, as well as a simple means of identifying specific measurement data, as well as a simple means of identifying specific
types of measurement data for the purposes of requesting them. types of measurement data for the purposes of requesting them.
The following example shows a measurement container with measurement The following example shows a measurement container with measurement
time and expiration time included. A WiFi measurement is enclosed. time and expiration time included. A WiFi measurement is enclosed.
<lm:measurements xmlns:lm="urn:ietf:params:xml:ns:geopriv:lm" <lm:measurements xmlns:lm="urn:ietf:params:xml:ns:geopriv:lm"
time="2008-04-29T14:33:58" time="2008-04-29T14:33:58"
expires="2008-04-29T17:33:58"> expires="2008-04-29T17:33:58">
<wifi xmlns="urn:ietf:params:xml:ns:geopriv:lm:wifi"> <wifi xmlns="urn:ietf:params:xml:ns:geopriv:lm:wifi">
<ap serving="true"> <ap serving="true">
<bssid>00-12-F0-A0-80-EF</bssid> <bssid>00-12-F0-A0-80-EF</bssid>
<ssid>wlan-home</ssid> <ssid>wlan-home</ssid>
</ap> </ap>
</wifi> </wifi>
</lm:measurements> </lm:measurements>
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 any request for location information,
such as a HELD location request such as a HELD location request [RFC5985].
[I-D.ietf-geopriv-http-location-delivery].
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 12, line 11 skipping to change at page 12, line 11
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"
code="locationUnknown"> code="locationUnknown">
<message xml:lang="en">Insufficient measurement data</message> <message xml:lang="en">Insufficient measurement data</message>
<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: HELD Error Requesting Measurement Data 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 14, line 10 skipping to change at page 14, line 10
No assertion is made about the veracity of the measurement data from No assertion is made about the veracity of the measurement data from
sources other than the LIS. A combination of tags MAY be included to sources other than the LIS. A combination of tags MAY be included to
indicate that measurement data from both sources was used. indicate that measurement data from both sources was used.
For example, the first tuple of the following PIDF-LO indicates that For example, the first tuple of the following PIDF-LO indicates that
measurement data from a LIS and a device was combined to produce the measurement data from a LIS and a device was combined to produce the
result, the second tuple was produced by the LIS alone. result, the second tuple was produced by the LIS alone.
<presence xmlns="urn:ietf:params:xml:ns:pidf" <presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:gml="http://www.opengis.net/gml" xmlns:gml="http://www.opengis.net/gml"
xmlns:gs="http://www.opengis.net/pidflo/1.0" xmlns:gs="http://www.opengis.net/pidflo/1.0"
xmlns:lmsrc="urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc" xmlns:lmsrc="urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc"
entity="pres:lm@example.com"> entity="pres:lm@example.com">
<tuple id="deviceLoc"> <tuple id="deviceLoc">
<status> <status>
<gp:geopriv> <gp:geopriv>
<gp:location-info> <gp:location-info>
<gs:Circle srsName="urn:ogc:def:crs:EPSG::4326"> <gs:Circle srsName="urn:ogc:def:crs:EPSG::4326">
<gml:pos>7.34324 134.47162</gml:pos> <gml:pos>7.34324 134.47162</gml:pos>
<gs:radius uom="urn:ogc:def:uom:EPSG::9001"> <gs:radius uom="urn:ogc:def:uom:EPSG::9001">
850.24 850.24
</gs:radius> </gs:radius>
</gs:Circle> </gs:Circle>
</gp:location-info> </gp:location-info>
<gp:usage-rules/> <gp:usage-rules/>
<gp:method>OTDOA</gp:method> <gp:method>OTDOA</gp:method>
<lmsrc:source>lis device</lmsrc:source> <lmsrc:source>lis device</lmsrc:source>
</gp:geopriv> </gp:geopriv>
</status> </status>
</tuple> </tuple>
<tuple id="lisLoc"> <tuple id="lisLoc">
<status> <status>
<gp:geopriv> <gp:geopriv>
<gp:location-info> <gp:location-info>
<gs:Circle srsName="urn:ogc:def:crs:EPSG::4326"> <gs:Circle srsName="urn:ogc:def:crs:EPSG::4326">
<gml:pos>7.34379 134.46484</gml:pos> <gml:pos>7.34379 134.46484</gml:pos>
<gs:radius uom="urn:ogc:def:uom:EPSG::9001"> <gs:radius uom="urn:ogc:def:uom:EPSG::9001">
9000 9000
</gs:radius> </gs:radius>
</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>
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
skipping to change at page 15, line 30 skipping to change at page 15, line 30
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
the Device. the Device.
Note: The LLDP extensions defined in LLDP Media Endpoint Discovery Note: The LLDP extensions defined in LLDP Media Endpoint Discovery
(LLDP-MED) [ANSI/TIA-1057] provide the ability to acquire location (LLDP-MED) [ANSI-TIA-1057] provide the ability to acquire location
information directly from an LLDP endpoint. Where this information directly from an LLDP endpoint. Where this
information is available, it might be unnecessary to use any other information is available, it might be unnecessary to use any other
form of location configuration. form of location configuration.
The Device MUST report the values directly as they were provided by Values are provided as hexadecimal sequences. The Device MUST report
the adjacent node. Attempting to adjust or translate the type of the values directly as they were provided by the adjacent node.
identifier is likely to cause the measurement data to be useless. Attempting to adjust or translate the type of identifier is likely to
cause the measurement data to be useless.
Where a Device has received LLDP messages from multiple adjacent Where a Device has received LLDP messages from multiple adjacent
nodes, it should provide information extracted from those messages by nodes, it should provide information extracted from those messages by
repeating the "lldp" element. repeating the "lldp" element.
An example of an LLDP measurement is shown in Figure 4. This shows An example of an LLDP measurement is shown in Figure 4. This shows
an adjacent node (chassis) that is identified by the IP address an adjacent node (chassis) that is identified by the IP address
192.0.2.45 (hexadecimal c000022d) and the port on that node is 192.0.2.45 (hexadecimal c000022d) and the port on that node is
numbered using an agent circuit ID [RFC3046] of 162 (hexadecimal a2). numbered using an agent circuit ID [RFC3046] of 162 (hexadecimal a2).
<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">
<lldp xmlns="urn:ietf:params:xml:ns:geopriv:lm:lldp"> <lldp xmlns="urn:ietf:params:xml:ns:geopriv:lm:lldp">
<chassis type="4">c000022d</chassis> <chassis type="4">c000022d</chassis>
<port type="6">a2</port> <port type="6">a2</port>
</lldp> </lldp>
</measurements> </measurements>
Figure 4: LLDP Measurement Example Figure 4: LLDP Measurement Example
IEEE 802 Devices that are able to obtain information about adjacent IEEE 802 Devices that are able to obtain information about adjacent
network switches and their attachment to them by other means MAY use network switches and their attachment to them by other means MAY use
this data type to convey this information. this data type to convey this information.
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", [RFC3046], [RFC4649]) and subscriber identifier
("subscriber", [RFC3993], [RFC4580]). The DHCPv6 remote identifier ("subscriber", [RFC3993], [RFC4580]). The DHCPv6 remote identifier
has an associated enterprise number [IANA.enterprise] as an XML has an associated enterprise number [IANA.enterprise] as an XML
attribute. 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
The "giaddr" is specified as a dotted quad IPv4 address or an RFC The "giaddr" is specified as a dotted quad IPv4 address or an RFC
4291 [RFC4291] IPv6 address. The enterprise number is specified as a 4291 [RFC4291] IPv6 address, using the forms defined in [RFC3986].
decimal integer. All other information is included verbatim from the The enterprise number is specified as a decimal integer. All other
DHCP request in hexadecimal format. information is included verbatim from the DHCP request in hexadecimal
format.
5.3. 802.11 WLAN Measurements 5.3. 802.11 WLAN Measurements
In WiFi, or 802.11 [IEEE.80211], networks a Device might be able to In WiFi, or 802.11 [IEEE.80211], networks a Device might be able to
provide information about the access point (AP) that it is attached provide information about the access point (AP) that it is attached
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>
<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>
<antenna>2</antenna> <antenna>2</antenna>
<flightTime rmsError="4e-9" samples="1">2.56e-9</flightTime> <flightTime rmsError="4e-9" samples="1">2.56e-9</flightTime>
<apSignal> <apSignal>
<transmit>23</transmit> <transmit>23</transmit>
<gain>5</gain> <gain>5</gain>
<rcpi dBm="true" rmsError="12" samples="1">-59</rcpi> <rcpi dBm="true" rmsError="12" samples="1">-59</rcpi>
<rsni rmsError="15" samples="1">23</rsni> <rsni rmsError="15" samples="1">23</rsni>
</apSignal> </apSignal>
<deviceSignal> <deviceSignal>
<transmit>10</transmit> <transmit>10</transmit>
<gain>9</gain> <gain>9</gain>
<rcpi dBm="true" rmsError="9.5" samples="1">-98.5</rcpi> <rcpi dBm="true" rmsError="9.5" samples="1">-98.5</rcpi>
<rsni rmsError="6" samples="1">7.5</rsni> <rsni rmsError="6" samples="1">7.5</rsni>
</deviceSignal> </deviceSignal>
</ap> </ap>
</wifi> </wifi>
</measurements> </measurements>
Figure 6: 802.11 WLAN Measurement Example Figure 6: 802.11 WLAN Measurement Example
A wifi element is made up of one or more access points, and an A wifi element is made up of one or more access points, and an
optional "nicType" element. Each access point is described using the optional "nicType" element. Each access point is described using the
"ap" element, which is comprised of the following fields: "ap" element, which is comprised of the following fields:
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
skipping to change at page 19, line 24 skipping to change at page 19, line 24
from the reported RMS error in TOD and TOA. from the reported RMS error in TOD and TOA.
apSignal: Measurement information for the signal transmitted by the apSignal: Measurement information for the signal transmitted by the
access point, as observed by the Device. Some of these values are access point, as observed by the Device. Some of these values are
derived from 802.11v [IEEE.80211V] messages exchanged between derived from 802.11v [IEEE.80211V] messages exchanged between
Device and access point. The contents of this element include: Device and access point. The contents of this element include:
transmit: The transmit power reported by the access point, in dB. transmit: The transmit power reported by the access point, in dB.
gain: The gain of the access point antenna reported by the access gain: The gain of the access point antenna reported by the access
point, in dB. point, in dB.
rcpi: The received channel power indicator for the access point rcpi: The received channel power indicator for the access point
signal, as measured by the Device. This value SHOULD be in signal, as measured by the Device. This value SHOULD be in
units of dBm (with RMS error in dB). If power is measured in a units of dBm (with RMS error in dB). If power is measured in a
different fashion, the "dBm" attribute MUST be set to "false". different fashion, the "dBm" attribute MUST be set to "false".
Signal strength reporting on current hardware uses a range of Signal strength reporting on current hardware uses a range of
different mechanisms; therefore, the value of the "nicType" different mechanisms; therefore, the value of the "nicType"
element SHOULD be included if the units are not known to be in element SHOULD be included if the units are not known to be in
dBm and the value reported by the hardware should be included dBm and the value reported by the hardware should be included
without modification. This element includes optional without modification. This element includes optional
"rmsError" and "samples" attributes. "rmsError" and "samples" attributes.
rsni: The received signal to noise indicator in dBm. This rsni: The received signal to noise indicator in dBm. This
element includes optional "rmsError" and "samples" attributes. element includes optional "rmsError" and "samples" attributes.
deviceSignal: Measurement information for the signal transmitted by deviceSignal: Measurement information for the signal transmitted by
the device, as reported by the access point. This element the device, as reported by the access point. This element
contains the same child elements as the "ap" element, with the contains the same child elements as the "ap" element, with the
access point and Device roles reversed. access point and Device roles reversed.
All elements are optional except for "bssid". All elements are optional except for "bssid".
The "nicType" element is used to specify the make and model of the The "nicType" element is used to specify the make and model of the
wireless network interface in the Device. Different 802.11 chipsets wireless network interface in the Device. Different 802.11 chipsets
skipping to change at page 20, line 45 skipping to change at page 20, line 45
the wireless transmitter only; future efforts might define additional the wireless transmitter only; future efforts might define additional
parameters that enable more accurate methods of location parameters that enable more accurate methods of location
determination. determination.
The cellular measurement set allows a Device to report to a LIS any The cellular measurement set allows a Device to report to a LIS any
LTE (Figure 7), UMTS (Figure 8), GSM (Figure 9) or CDMA (Figure 10) LTE (Figure 7), UMTS (Figure 8), GSM (Figure 9) or CDMA (Figure 10)
cells that it is able to observe. Cells are reported using their cells that it is able to observe. Cells are reported using their
global identifiers. All 3GPP cells are identified by public land global identifiers. All 3GPP cells are identified by public land
mobile network (PLMN), which is formed of mobile country code (MCC) mobile network (PLMN), which is formed of mobile country code (MCC)
and mobile network code (MNC); specific fields are added for each and mobile network code (MNC); specific fields are added for each
network type. All other values are decimal integers. network type.
Formats for 3GPP cell identifiers are described in [TS.3GPP.23.003].
Bit-level formats for CDMA cell identifiers are described in
[TIA-2000.5]; decimal representations are used.
MCC and MNC are provided as digit sequences; a leading zero in an MCC
or MNC is significant. All other values are decimal integers.
<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">
<cellular xmlns="urn:ietf:params:xml:ns:geopriv:lm:cell"> <cellular xmlns="urn:ietf:params:xml:ns:geopriv:lm:cell">
<servingCell> <servingCell>
<mcc>465</mcc><mnc>20</mnc> <mcc>465</mcc><mnc>20</mnc><eucid>80936424</eucid>
<eucid>80936424</eucid> </servingCell>
</servingCell> <observedCell>
<observedCell> <mcc>465</mcc><mnc>06</mnc><eucid>10736789</eucid>
<mcc>465</mcc><mnc>06</mnc> </observedCell>
<eucid>10736789</eucid>
</observedCell>
</cellular> </cellular>
</measurements> </measurements>
Long term evolution (LTE) cells are identified by a 28-bit cell Long term evolution (LTE) cells are identified by a 28-bit cell
identifier (eucid). identifier (eucid).
Figure 7: Example LTE Cellular Measurement Figure 7: Example LTE Cellular 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">
<cellular xmlns="urn:ietf:params:xml:ns:geopriv:lm:cell"> <cellular xmlns="urn:ietf:params:xml:ns:geopriv:lm:cell">
<servingCell> <servingCell>
<mcc>465</mcc><mnc>20</mnc> <mcc>465</mcc><mnc>20</mnc>
<rnc>2000</rnc><cid>65000</cid> <rnc>2000</rnc><cid>65000</cid>
</servingCell> </servingCell>
<observedCell> <observedCell>
<mcc>465</mcc><mnc>06</mnc> <mcc>465</mcc><mnc>06</mnc>
<lac>16383</lac><cid>32767</cid> <lac>16383</lac><cid>32767</cid>
</observedCell> </observedCell>
</cellular> </cellular>
</measurements> </measurements>
Universal mobile telephony service (UMTS) cells are identified by Universal mobile telephony service (UMTS) cells are identified by 16-
radio network controller (rnc) and cell id (cid). bit radio network controller (rnc) id and a 16-bit cell id (cid).
Figure 8: Example UMTS Cellular Measurement
Figure 8: Example UMTS Cellular 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">
<cellular xmlns="urn:ietf:params:xml:ns:geopriv:lm:cell"> <cellular xmlns="urn:ietf:params:xml:ns:geopriv:lm:cell">
<servingCell> <servingCell>
<mcc>465</mcc><mnc>06</mnc> <mcc>465</mcc><mnc>06</mnc>
<lac>16383</lac><cid>32767</cid> <lac>16383</lac><cid>32767</cid>
</servingCell> </servingCell>
</cellular> </cellular>
</measurements> </measurements>
Global System for Mobile communication (GSM) cells are identified by Global System for Mobile communication (GSM) cells are identified by
local radio network controller (rnc) and cell id (cid). a 16-bit location area code (lac) and 16-bit cell id (cid).
Figure 9: Example GSM Cellular Measurement Figure 9: Example GSM Cellular 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">
<cellular xmlns="urn:ietf:params:xml:ns:geopriv:lm:cell"> <cellular xmlns="urn:ietf:params:xml:ns:geopriv:lm:cell">
<servingCell> <servingCell>
<nid>4723</nid><sid>15892</sid><baseid>12</baseid> <sid>15892</sid><nid>4723</nid><baseid>12</baseid>
</servingCell> </servingCell>
<observedCell> <observedCell>
<nid>4723</nid><sid>15892</sid><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 use network id (nid), system id (sid) and base PLMN, instead these usea 15-bit system id (sid), a 16-bit network id
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
cell information without actually attaching to the network, mobiles cell information without actually attaching to the network, mobiles
without a SIM are an example of this. In this case the Device may without a SIM are an example of this. In this case the Device may
simply report cells it can hear without flagging one as a serving simply report cells it can hear without flagging one as a serving
cell. An example of this is shown in Figure 11. cell. An example of this is shown in Figure 11.
<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">
<cellular xmlns="urn:ietf:params:xml:ns:geopriv:lm:cell"> <cellular xmlns="urn:ietf:params:xml:ns:geopriv:lm:cell">
<observedCell> <observedCell>
<mcc>465</mcc><mnc>20</mnc> <mcc>465</mcc><mnc>20</mnc>
<rnc>2000</rnc><cid>65000</cid> <rnc>2000</rnc><cid>65000</cid>
</observedCell> </observedCell>
<observedCell> <observedCell>
<mcc>465</mcc><mnc>06</mnc> <mcc>465</mcc><mnc>06</mnc>
<lac>16383</lac><cid>32767</cid> <lac>16383</lac><cid>32767</cid>
</observedCell> </observedCell>
</cellular> </cellular>
</measurements> </measurements>
Figure 11: Example Observed Cellular Measurement Figure 11: Example Observed Cellular Measurement
5.4.1. Cellular Measurement Requests 5.4.1. Cellular Measurement Requests
Two elements can be used in measurement requests for cellular Two elements can be used in measurement requests for cellular
measurements: measurements:
type: A label indicating the type of identifier to provide: one of type: A label indicating the type of identifier to provide: one of
"gsm", "umts", "lte", or "cdma". "gsm", "umts", "lte", or "cdma".
network: The network portion of the cell identifier. For 3GPP network: The network portion of the cell identifier. For 3GPP
skipping to change at page 25, line 6 skipping to change at page 25, line 6
reduce the amount of time required for the signal acquisition reduce the amount of time required for the signal acquisition
stage and obviate the need for the receiver to extract data on the stage and obviate the need for the receiver to extract data on the
satellite constellation. Provision of assistance data is outside satellite constellation. Provision of assistance data is outside
the scope of this document. the scope of this document.
Figure 12 shows an example of GNSS measurement data. The measurement Figure 12 shows an example of GNSS measurement data. The measurement
shown is for the GPS system and includes measurement data for three shown is for the GPS system and includes measurement data for three
satellites only. satellites only.
<measurements xmlns="urn:ietf:params:xml:ns:geopriv:lm" <measurements xmlns="urn:ietf:params:xml:ns:geopriv:lm"
time="2008-04-29T14:33:58" timeError="2e-5"> time="2008-04-29T14:33:58" timeError="2e-5">
<gnss xmlns="urn:ietf:params:xml:ns:geopriv:lm:gnss" <gnss xmlns="urn:ietf:params:xml:ns:geopriv:lm:gnss"
system="gps" signal="L1"> system="gps" signal="L1">
<sat num="19"> <sat num="19">
<doppler>499.9395</doppler> <doppler>499.9395</doppler>
<codephase rmsError="1.6e-9">0.87595747</codephase> <codephase rmsError="1.6e-9">0.87595747</codephase>
<cn0>45</cn0> <cn0>45</cn0>
</sat> </sat>
<sat num="27"> <sat num="27">
<doppler>378.2657</doppler> <doppler>378.2657</doppler>
<codephase rmsError="1.6e-9">0.56639479</codephase> <codephase rmsError="1.6e-9">0.56639479</codephase>
<cn0>52</cn0> <cn0>52</cn0>
</sat> </sat>
<sat num="20"> <sat num="20">
<doppler>-633.0309</doppler> <doppler>-633.0309</doppler>
<codephase rmsError="1.6e-9">0.57016835</codephase> <codephase rmsError="1.6e-9">0.57016835</codephase>
<cn0>48</cn0> <cn0>48</cn0>
</sat> </sat>
</gnss> </gnss>
</measurements> </measurements>
Figure 12: Example GNSS Measurement Figure 12: Example GNSS Measurement
Each "gnss" element represents a single set of GNSS measurement data, Each "gnss" element represents a single set of GNSS measurement data,
taken at a single point in time. Measurements taken at different taken at a single point in time. Measurements taken at different
times can be included in different "gnss" elements to enable times can be included in different "gnss" elements to enable
iterative refinement of results. iterative refinement of results.
GNSS measurement parameters are described in more detail in the GNSS measurement parameters are described in more detail in the
following sections. following sections.
5.5.1. GNSS System and Signal 5.5.1. GNSS System and Signal
skipping to change at page 25, line 51 skipping to change at page 25, line 51
also accounted for and can be measured separately. also accounted for and can be measured separately.
The GNSS type determines the time system that is used. An indication The GNSS type determines the time system that is used. An indication
of the type of system and signal can ensure that the LIS is able to of the type of system and signal can ensure that the LIS is able to
correctly use measurements. correctly use measurements.
Measurements for multiple GNSS types and signals can be included by Measurements for multiple GNSS types and signals can be included by
repeating the "gnss" element. repeating the "gnss" element.
This document creates an IANA registry for GNSS types. Two satellite This document creates an IANA registry for GNSS types. Two satellite
systems are registered by this document: GPS and Galileo. Details systems are registered by this document: GPS [GPS.ICD] and Galileo
for the registry are included in Section 9.1. [Galileo.ICD]. Details for the registry are included in Section 9.1.
5.5.2. Time 5.5.2. Time
Each set of GNSS measurements is taken at a specific point in time. Each set of GNSS measurements is taken at a specific point in time.
The "time" attribute is used to indicate the time that the The "time" attribute is used to indicate the time that the
measurement was acquired, if the receiver knows how the time system measurement was acquired, if the receiver knows how the time system
used by the GNSS relates to UTC time. used by the GNSS relates to UTC time.
Alternative to (or in addition to) the measurement time, the Alternative to (or in addition to) the measurement time, the
"gnssTime" element MAY be included. The "gnssTime" element includes "gnssTime" element MAY be included. The "gnssTime" element includes
skipping to change at page 26, line 47 skipping to change at page 26, line 47
satellite: satellite:
doppler: The observed Doppler shift of the satellite signal, doppler: The observed Doppler shift of the satellite signal,
measured in meters per second. This is converted from a value in measured in meters per second. This is converted from a value in
Hertz by the receiver to allow the measurement to be used without Hertz by the receiver to allow the measurement to be used without
knowledge of the carrier frequency of the satellite system. This knowledge of the carrier frequency of the satellite system. This
value includes an optional RMS error attribute, also measured in value includes an optional RMS error attribute, also measured in
meters per second. meters per second.
codephase: The observed code phase for the satellite signal, codephase: The observed code phase for the satellite signal,
measured in milliseconds. This is converted from a value in chips measured in milliseconds. This is converted the system-specific
or wavelengths. Increasing values indicate increasing value of chips or wavelengths into a system independent value.
pseudoranges. This value includes an optional RMS error Larger values indicate larger distances from satellite to
attribute, also measured in milliseconds. receiver. This value includes an optional RMS error attribute,
also measured in milliseconds.
cn0: The signal to noise ratio for the satellite signal, measured in cn0: The signal to noise ratio for the satellite signal, measured in
decibel-Hertz (dB-Hz). The expected range is between 20 and 50 decibel-Hertz (dB-Hz). The expected range is between 20 and 50
dB-Hz. dB-Hz.
mp: An estimation of the amount of error that multipath signals mp: An estimation of the amount of error that multipath signals
contribute in metres. This parameter is optional. contribute in metres. This parameter is optional.
cq: An indication of the carrier quality. Two attributes are cq: An indication of the carrier quality. Two attributes are
included: "continuous" may be either "true" or "false"; direct may included: "continuous" may be either "true" or "false"; direct may
be either "direct" or "inverted". This parameter is optional. be either "direct" or "inverted". This parameter is optional.
adr: The accumulated Doppler range, measured in metres. This adr: The accumulated Doppler range, measured in metres. This
parameter is optional and is not necessary unless multiple sets of parameter is optional and is not useful unless multiple sets of
GNSS measurements are provided. GNSS measurements are provided or differential positioning is
being performed.
All values are converted from measures native to the satellite system All values are converted from measures native to the satellite system
to generic measures to ensure consistency of interpretation. Unless to generic measures to ensure consistency of interpretation. Unless
necessary, the schema does not constrain these values. necessary, the schema does not constrain these values.
5.5.4. GNSS Measurement Requests 5.5.4. GNSS Measurement Requests
Measurement requests can include a "gnss" element, which includes the Measurement requests can include a "gnss" element, which includes the
"system" and "signal" attributes. Multiple elements can be included "system" and "signal" attributes. Multiple elements can be included
to indicate a requests for GNSS measurements from multiple systems or to indicate a requests for GNSS measurements from multiple systems or
skipping to change at page 27, line 42 skipping to change at page 27, line 43
Digital Subscriber Line (DSL) networks rely on a range of network Digital Subscriber Line (DSL) networks rely on a range of network
technology. DSL deployments regularly require cooperation between technology. DSL deployments regularly require cooperation between
multiple organizations. These fall into two broad categories: multiple organizations. These fall into two broad categories:
infrastructure providers and Internet service providers (ISPs). infrastructure providers and Internet service providers (ISPs).
Infrastructure providers manage the bulk of the physical Infrastructure providers manage the bulk of the physical
infrastructure including cabling. End users obtain their service infrastructure including cabling. End users obtain their service
from an ISP, which manages all aspects visible to the end user from an ISP, which manages all aspects visible to the end user
including IP address allocation and operation of a LIS. See including IP address allocation and operation of a LIS. See
[DSL.TR025] and [DSL.TR101] for further information on DSL network [DSL.TR025] and [DSL.TR101] for further information on DSL network
deployments. deployments and the parameters that are available.
Exchange of measurement information between these organizations is Exchange of measurement information between these organizations is
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, the infrastructure provider has no knowledge of provider. However, the infrastructure provider has no knowledge of
Device identifiers, it can only identify a stream of data that is Device identifiers, it can only identify a stream of data that is
sent to the ISP. This is resolved by passing measurement data sent to the ISP. This is resolved by passing measurement data
relating to the Device to a LIS operated by the infrastructure relating to the Device to a LIS operated by the infrastructure
provider. 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) is a common means of linking the
infrastructure provider and the ISP. The infrastructure provider LIS infrastructure provider and the ISP. The infrastructure provider LIS
requires measurement data that identifies a single L2TP tunnel, from requires measurement data that identifies a single L2TP tunnel, from
which it can generate location information. Figure 13 shows an which it can generate location information. Figure 13 shows an
example L2TP measurement. 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>
</measurements> </measurements>
Figure 13: Example DSL L2TP Measurement Figure 13: Example DSL L2TP Measurement
5.6.2. RADIUS Measurements 5.6.2. RADIUS Measurements
When authenticating network access, the infrastructure provider might When authenticating network access, the infrastructure provider might
employ a RADIUS [RFC2865] proxy at the DSL Access Module (DSLAM) or employ a RADIUS [RFC2865] proxy at the DSL Access Module (DSLAM) or
Access Node (AN). These messages provide the ISP RADIUS server with Access Node (AN). These messages provide the ISP RADIUS server with
an identifier for the DSLAM or AN, plus the slot and port that the an identifier for the DSLAM or AN, plus the slot and port that the
Device is attached on. These data can be provided as a measurement, Device is attached on. These data can be provided as a measurement,
which allows the infrastructure provider LIS to generate location which allows the infrastructure provider LIS to generate location
information. information.
The format of the AN, slot and port identifiers are not defined in The format of the AN, slot and port identifiers are not defined in
the RADIUS protocol. Slot and port together identify a circuit on the RADIUS protocol. Slot and port together identify a circuit on
the AN, analogous to the circuit identifier in [RFC3046]. These the AN, analogous to the circuit identifier in [RFC3046]. These
items are provided directly, as they were in the RADIUS message. An items are provided directly, as they were in the RADIUS message. An
example is shown in Figure 14. example is shown in Figure 14.
<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">
<an>AN-7692</an> <an>AN-7692</an>
<slot>3</slot> <slot>3</slot>
<port>06</port> <port>06</port>
</dsl> </dsl>
</measurements> </measurements>
Figure 14: Example DSL RADIUS Measurement Figure 14: Example DSL RADIUS Measurement
5.6.3. Ethernet VLAN Tag Measurements 5.6.3. Ethernet VLAN Tag Measurements
For Ethernet-based DSL access networks, the DSL Access Module (DSLAM) For Ethernet-based DSL access networks, the DSL Access Module (DSLAM)
or Access Node (AN) provide two VLAN tags on packets. A C-TAG is or Access Node (AN) provide two VLAN tags on packets. A C-TAG is
used to identify the incoming residential circuit, while the S-TAG is used to identify the incoming residential circuit, while the S-TAG is
used to identify the DSLAM or AN. The C-TAG and S-TAG together can used to identify the DSLAM or AN. The C-TAG and S-TAG together can
be used to identify a single point of network attachment. An example be used to identify a single point of network attachment. An example
is shown in Figure 15. is shown in Figure 15.
<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">
<stag>613</stag> <stag>613</stag>
<ctag>1097</ctag> <ctag>1097</ctag>
</dsl> </dsl>
</measurements> </measurements>
Figure 15: Example DSL VLAN Tag Measurement Figure 15: Example DSL VLAN Tag Measurement
Alternatively, the C-TAG can be replaced by data on the slot and port Alternatively, the C-TAG can be replaced by data on the slot and port
that the Device is attached to. This information might be included that the Device is attached to. This information might be included
in RADIUS requests that are proxied from the infrastructure provider in RADIUS requests that are proxied from the infrastructure provider
to the ISP RADIUS server. to the ISP RADIUS server.
5.6.4. ATM Virtual Circuit Measurements 5.6.4. ATM Virtual Circuit Measurements
An ATM virtual circuit can be employed between the ISP and An ATM virtual circuit can be employed between the ISP and
infrastructure provider. Providing the virtual port ID (VPI) and infrastructure provider. Providing the virtual port ID (VPI) and
virtual circuit ID (VCI) for the virtual circuit gives the virtual circuit ID (VCI) for the virtual circuit gives the
infrastructure provider LIS the ability to identify a single data infrastructure provider LIS the ability to identify a single data
stream. A sample measurement is shown in Figure 16. stream. A sample measurement is shown in Figure 16.
<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">
<vpi>55</vpi> <vpi>55</vpi>
<vci>6323</vci> <vci>6323</vci>
</dsl> </dsl>
</measurements> </measurements>
Figure 16: Example DSL ATM Measurement Figure 16: Example DSL ATM Measurement
6. Privacy Considerations 6. Privacy Considerations
Location-related measurement data can be as privacy sensitive as Location-related measurement data can be as privacy sensitive as
location information. location information.
Measurement data is effectively equivalent to location information if Measurement data is effectively equivalent to location information if
the contextual knowledge necessary to generate one from the other is the contextual knowledge necessary to generate one from the other is
readily accessible. Even where contextual knowledge is difficult to readily accessible. Even where contextual knowledge is difficult to
acquire, there can be no assurance that an authorized recipient of acquire, there can be no assurance that an authorized recipient of
skipping to change at page 30, line 29 skipping to change at page 30, line 29
fashion as location information. Measurement data is less useful to fashion as location information. Measurement data is less useful to
location recipients than location information. Therefore, a simple location recipients than location information. Therefore, a simple
distribution model is desirable. distribution model is desirable.
In this simple model, the Device is the only entity that is able to In this simple model, the Device is the only entity that is able to
distribute measurement data. To use an analogy from the GEOPRIV distribute measurement data. To use an analogy from the GEOPRIV
architecture, the Device - as the Location Generator (or the architecture, the Device - as the Location Generator (or the
Measurement Data Generator) - is the sole entity that can assume the Measurement Data Generator) - is the sole entity that can assume the
roles of Rule Maker and Location Server. roles of Rule Maker and Location Server.
No entity can redistribute measurement data. The Device directs No entity is permitted to redistribute measurement data. The Device
other entities in how measurement data is used and retained. directs other entities in how measurement data is used and retained.
6.2. LIS Privacy Requirements 6.2. LIS Privacy Requirements
A LIS MUST NOT reveal location-related measurement data or location A LIS MUST NOT reveal location-related measurement data or location
information based on measurement data to any other entity unless information based on measurement data to any other entity unless
directed to do so by the Device. directed to do so by the Device.
By adding measurement data to a request for location information, the By adding measurement data to a request for location information, the
Device implicitly grants permission for the LIS to generate the Device implicitly grants permission for the LIS to generate the
requested location information using the measurement data. requested location information using the measurement data.
skipping to change at page 43, line 7 skipping to change at page 43, line 7
<xs:schema <xs:schema
xmlns:lm="urn:ietf:params:xml:ns:geopriv:lm" xmlns:lm="urn:ietf:params:xml:ns:geopriv:lm"
xmlns:bt="urn:ietf:params:xml:ns:geopriv:lm:basetypes" xmlns:bt="urn:ietf:params:xml:ns:geopriv:lm:basetypes"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:ietf:params:xml:ns:geopriv:lm" targetNamespace="urn:ietf:params:xml:ns:geopriv:lm"
elementFormDefault="qualified" elementFormDefault="qualified"
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
<xs:annotation> <xs:annotation>
<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"/>
<xs:attribute name="timeError" type="bt:positiveDouble"/> <xs:attribute name="timeError" type="bt:positiveDouble"/>
<xs:attribute name="expires" type="xs:dateTime"/> <xs:attribute name="expires" type="xs:dateTime"/>
<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:element> </xs:element>
<xs:element name="measurementRequest" <xs:element name="measurementRequest"
type="lm:measurementRequestType"/> type="lm:measurementRequestType"/>
<xs:complexType name="measurementRequestType"> <xs:complexType name="measurementRequestType">
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType"> <xs:restriction base="xs:anyType">
<xs:sequence> <xs:sequence>
<xs:element ref="lm:measurement" <xs:element ref="lm:measurement"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<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:restriction> </xs:restriction>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
<xs:element name="measurement" type="lm:measurementType"/> <xs:element name="measurement" type="lm:measurementType"/>
<xs:complexType name="measurementType"> <xs:complexType name="measurementType">
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType">
<xs:sequence> <xs:restriction base="xs:anyType">
<xs:any namespace="##other" processContents="lax" <xs:sequence>
minOccurs="0" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax"
</xs:sequence> minOccurs="0" maxOccurs="unbounded"/>
<xs:attribute name="type" type="xs:QName" use="required"/> </xs:sequence>
<xs:attribute name="samples" type="xs:positiveInteger"/> <xs:attribute name="type" type="xs:QName" use="required"/>
</xs:restriction> <xs:attribute name="samples" type="xs:positiveInteger"/>
</xs:restriction>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
<!-- PIDF-LO extension for source --> <!-- PIDF-LO extension for source -->
<xs:element name="source" type="lm:sourceType"/> <xs:element name="source" type="lm:sourceType"/>
<xs:simpleType name="sourceType"> <xs:simpleType name="sourceType">
<xs:list> <xs:list>
<xs:simpleType> <xs:simpleType>
<xs:restriction base="xs:token"> <xs:restriction base="xs:token">
<xs:enumeration value="lis"/> <xs:enumeration value="lis"/>
<xs:enumeration value="device"/> <xs:enumeration value="device"/>
<xs:enumeration value="other"/> <xs:enumeration value="other"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
</xs:list> </xs:list>
</xs:simpleType> </xs:simpleType>
</xs:schema> </xs:schema>
Measurement Container Schema Measurement Container Schema
8.2. Measurement Source Schema 8.2. Measurement Source Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
xmlns:lmsrc="urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc" xmlns:lmsrc="urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc" targetNamespace="urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc"
elementFormDefault="qualified" elementFormDefault="qualified"
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
<xs:annotation> <xs:annotation>
<xs:appinfo <xs:appinfo
source="urn:ietf:params:xml:schema:pidf:geopriv10:lmsrc"> source="urn:ietf:params:xml:schema:pidf:geopriv10:lmsrc">
</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 an extension to PIDF-LO that indicates the This schema defines an extension to PIDF-LO that indicates the
type of source that produced the measurement data used in type of source that produced the measurement data used in
generating the associated location information. generating the associated location information.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
<xs:element name="source" type="lmsrc:sourceType"/> <xs:element name="source" type="lmsrc:sourceType"/>
<xs:simpleType name="sourceType"> <xs:simpleType name="sourceType">
<xs:list> <xs:list>
<xs:simpleType> <xs:simpleType>
<xs:restriction base="xs:token"> <xs:restriction base="xs:token">
<xs:enumeration value="lis"/> <xs:enumeration value="lis"/>
<xs:enumeration value="device"/> <xs:enumeration value="device"/>
<xs:enumeration value="other"/> <xs:enumeration value="other"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
</xs:list> </xs:list>
</xs:simpleType> </xs:simpleType>
</xs:schema> </xs:schema>
Measurement Source PIDF-LO Extension Schema Measurement Source PIDF-LO Extension Schema
8.3. Base Type Schema 8.3. Base Type Schema
Note that the pattern rules in the following schema wrap due to Note that the pattern rules in the following schema wrap due to
length constraints. None of the patterns contain whitespace. length constraints. None of the patterns contain whitespace.
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
xmlns:bt="urn:ietf:params:xml:ns:geopriv:lm:basetypes" xmlns:bt="urn:ietf:params:xml:ns:geopriv:lm:basetypes"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:basetypes" targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:basetypes"
elementFormDefault="qualified" elementFormDefault="qualified"
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
<xs:annotation>
<xs:appinfo
source="urn:ietf:params:xml:schema:geopriv:lm:basetypes">
</xs:appinfo>
<xs:documentation source="http://www.ietf.org/rfc/rfcXXXX.txt">
<!-- [[NOTE TO RFC-EDITOR: Please replace above URL with URL of
published RFC and remove this note.]] -->
This schema defines a set of base type elements.
</xs:documentation>
</xs:annotation>
<xs:simpleType name="byteType"> <xs:annotation>
<xs:restriction base="xs:integer"> <xs:appinfo
<xs:minInclusive value="0"/> source="urn:ietf:params:xml:schema:geopriv:lm:basetypes">
<xs:maxInclusive value="255"/> </xs:appinfo>
</xs:restriction> <xs:documentation source="http://www.ietf.org/rfc/rfcXXXX.txt">
</xs:simpleType> <!-- [[NOTE TO RFC-EDITOR: Please replace above URL with URL of
<xs:simpleType name="twoByteType"> published RFC and remove this note.]] -->
<xs:restriction base="xs:integer"> This schema defines a set of base type elements.
<xs:minInclusive value="0"/> </xs:documentation>
<xs:maxInclusive value="65535"/> </xs:annotation>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="nonNegativeDouble"> <xs:simpleType name="byteType">
<xs:restriction base="xs:double"> <xs:restriction base="xs:integer">
<xs:minInclusive value="0.0"/> <xs:minInclusive value="0"/>
</xs:restriction> <xs:maxInclusive value="255"/>
</xs:simpleType> </xs:restriction>
<xs:simpleType name="positiveDouble"> </xs:simpleType>
<xs:restriction base="bt:nonNegativeDouble"> <xs:simpleType name="twoByteType">
<xs:minExclusive value="0.0"/> <xs:restriction base="xs:integer">
</xs:restriction> <xs:minInclusive value="0"/>
</xs:simpleType> <xs:maxInclusive value="65535"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="doubleWithRMSError"> <xs:simpleType name="nonNegativeDouble">
<xs:simpleContent> <xs:restriction base="xs:double">
<xs:extension base="xs:double"> <xs:minInclusive value="0.0"/>
<xs:attribute name="rmsError" type="bt:positiveDouble"/>
<xs:attribute name="samples" type="xs:positiveInteger"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="nnDoubleWithRMSError">
<xs:simpleContent>
<xs:restriction base="bt:doubleWithRMSError">
<xs:minInclusive value="0"/>
</xs:restriction> </xs:restriction>
</xs:simpleContent> </xs:simpleType>
</xs:complexType> <xs:simpleType name="positiveDouble">
<xs:restriction base="bt:nonNegativeDouble">
<xs:minExclusive value="0.0"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="ipAddressType"> <xs:complexType name="doubleWithRMSError">
<xs:union memberTypes="bt:IPv6AddressType bt:IPv4AddressType"/> <xs:simpleContent>
</xs:simpleType> <xs:extension base="xs:double">
<xs:attribute name="rmsError" type="bt:positiveDouble"/>
<xs:attribute name="samples" type="xs:positiveInteger"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="nnDoubleWithRMSError">
<xs:simpleContent>
<xs:restriction base="bt:doubleWithRMSError">
<xs:minInclusive value="0"/>
</xs:restriction>
</xs:simpleContent>
</xs:complexType>
<!-- IPv6 format definition --> <xs:simpleType name="ipAddressType">
<xs:simpleType name="IPv6AddressType"> <xs:union memberTypes="bt:IPv6AddressType bt:IPv4AddressType"/>
<xs:annotation> </xs:simpleType>
<xs:documentation>
An IP version 6 address, based on RFC 4291.
</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:token">
<!-- Fully specified address -->
<xs:pattern value="[0-9A-Fa-f]{1,4}(:[0-9A-Fa-f]{1,4}){7}"/>
<!-- Double colon start -->
<xs:pattern value=":(:[0-9A-Fa-f]{1,4}){1,7}"/>
<!-- Double colon middle -->
<xs:pattern value="([0-9A-Fa-f]{1,4}:){1,6}
(:[0-9A-Fa-f]{1,4}){1}"/>
<xs:pattern value="([0-9A-Fa-f]{1,4}:){1,5}
(:[0-9A-Fa-f]{1,4}){1,2}"/>
<xs:pattern value="([0-9A-Fa-f]{1,4}:){1,4}
(:[0-9A-Fa-f]{1,4}){1,3}"/>
<xs:pattern value="([0-9A-Fa-f]{1,4}:){1,3}
(:[0-9A-Fa-f]{1,4}){1,4}"/>
<xs:pattern value="([0-9A-Fa-f]{1,4}:){1,2}
(:[0-9A-Fa-f]{1,4}){1,5}"/>
<xs:pattern value="([0-9A-Fa-f]{1,4}:){1}
(:[0-9A-Fa-f]{1,4}){1,6}"/>
<!-- Double colon end -->
<xs:pattern value="([0-9A-Fa-f]{1,4}:){1,7}:"/>
<!-- IPv4-Compatible and IPv4-Mapped Addresses -->
<xs:pattern value="((:(:0{1,4}){0,3}:[fF]{4})|(0{1,4}:
(:0{1,4}){0,2}:[fF]{4})|((0{1,4}:){2}
(:0{1,4})?:[fF]{4})|((0{1,4}:){3}:[fF]{4})
|((0{1,4}:){4}[fF]{4})):(25[0-5]|2[0-4][0-9]|
[0-1]?[0-9]?[0-9])\.(25[0-5]|2[0-4][0-9]|[0-1]
?[0-9]?[0-9])\.(25[0-5]|2[0-4][0-9]|[0-1]?
[0-9]?[0-9])\.(25[0-5]|2[0-4][0-9]|[0-1]?
[0-9]?[0-9])"/>
<!-- The unspecified address -->
<xs:pattern value="::"/>
</xs:restriction>
</xs:simpleType>
<!-- IPv4 format definition --> <!-- IPv6 format definition -->
<xs:simpleType name="IPv4AddressType"> <xs:simpleType name="IPv6AddressType">
<xs:restriction base="xs:token"> <xs:annotation>
<xs:pattern value="(25[0-5]|2[0-4][0-9]|[0-1]?[0-9]?[0-9])\. <xs:documentation>
(25[0-5]|2[0-4][0-9]|[0-1]?[0-9]?[0-9])\. An IP version 6 address, based on RFC 4291.
(25[0-5]|2[0-4][0-9]|[0-1]?[0-9]?[0-9])\. </xs:documentation>
(25[0-5]|2[0-4][0-9]|[0-1]?[0-9]?[0-9])"/> </xs:annotation>
</xs:restriction> <xs:restriction base="xs:token">
</xs:simpleType> <!-- Fully specified address -->
<xs:pattern value="[0-9A-Fa-f]{1,4}(:[0-9A-Fa-f]{1,4}){7}"/>
<!-- Double colon start -->
<xs:pattern value=":(:[0-9A-Fa-f]{1,4}){1,7}"/>
<!-- Double colon middle -->
<xs:pattern value="([0-9A-Fa-f]{1,4}:){1,6}
(:[0-9A-Fa-f]{1,4}){1}"/>
<xs:pattern value="([0-9A-Fa-f]{1,4}:){1,5}
(:[0-9A-Fa-f]{1,4}){1,2}"/>
<xs:pattern value="([0-9A-Fa-f]{1,4}:){1,4}
(:[0-9A-Fa-f]{1,4}){1,3}"/>
<xs:pattern value="([0-9A-Fa-f]{1,4}:){1,3}
(:[0-9A-Fa-f]{1,4}){1,4}"/>
<xs:pattern value="([0-9A-Fa-f]{1,4}:){1,2}
(:[0-9A-Fa-f]{1,4}){1,5}"/>
<xs:pattern value="([0-9A-Fa-f]{1,4}:){1}
(:[0-9A-Fa-f]{1,4}){1,6}"/>
<!-- Double colon end -->
<xs:pattern value="([0-9A-Fa-f]{1,4}:){1,7}:"/>
<!-- IPv4-Compatible and IPv4-Mapped Addresses -->
<xs:pattern value="((:(:0{1,4}){0,3}:[fF]{4})|(0{1,4}:
(:0{1,4}){0,2}:[fF]{4})|((0{1,4}:){2}
(:0{1,4})?:[fF]{4})|((0{1,4}:){3}:[fF]{4})
|((0{1,4}:){4}[fF]{4})):(25[0-5]|2[0-4][0-9]|
[0-1]?[0-9]?[0-9])\.(25[0-5]|2[0-4][0-9]|[0-1]
?[0-9]?[0-9])\.(25[0-5]|2[0-4][0-9]|[0-1]?
[0-9]?[0-9])\.(25[0-5]|2[0-4][0-9]|[0-1]?
[0-9]?[0-9])"/>
<!-- The unspecified address -->
<xs:pattern value="::"/>
</xs:restriction>
</xs:simpleType>
<!-- MAC address (EUI-48) or EUI-64 address --> <!-- IPv4 format definition -->
<xs:simpleType name="macAddressType"> <xs:simpleType name="IPv4AddressType">
<xs:restriction base="xs:token"> <xs:restriction base="xs:token">
<xs:pattern <xs:pattern value="(25[0-5]|2[0-4][0-9]|[0-1]?[0-9]?[0-9])\.
value="[\da-fA-F]{2}(-[\da-fA-F]{2}){5}((-[\da-fA-F]{2}){2})?"/> (25[0-5]|2[0-4][0-9]|[0-1]?[0-9]?[0-9])\.
</xs:restriction> (25[0-5]|2[0-4][0-9]|[0-1]?[0-9]?[0-9])\.
</xs:simpleType> (25[0-5]|2[0-4][0-9]|[0-1]?[0-9]?[0-9])"/>
</xs:restriction>
</xs:simpleType>
</xs:schema> <!-- MAC address (EUI-48) or EUI-64 address -->
<xs:simpleType name="macAddressType">
<xs:restriction base="xs:token">
<xs:pattern
value="[\da-fA-F]{2}(-[\da-fA-F]{2}){5}((-[\da-fA-F]{2}){2})?"/>
</xs:restriction>
</xs:simpleType>
Base Type Schema </xs:schema>
Base Type Schema
8.4. LLDP Measurement Schema 8.4. LLDP Measurement Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
xmlns:lldp="urn:ietf:params:xml:ns:geopriv:lm:lldp" xmlns:lldp="urn:ietf:params:xml:ns:geopriv:lm:lldp"
xmlns:bt="urn:ietf:params:xml:ns:geopriv:lm:basetypes" xmlns:bt="urn:ietf:params:xml:ns:geopriv:lm:basetypes"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:lldp" targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:lldp"
elementFormDefault="qualified" elementFormDefault="qualified"
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
<xs:annotation> <xs:annotation>
<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"/>
</xs:sequence> </xs:sequence>
<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="lldpDataType"> <xs:complexType name="lldpDataType">
<xs:simpleContent> <xs:simpleContent>
<xs:extension base="lldp:lldpOctetStringType"> <xs:extension base="lldp:lldpOctetStringType">
<xs:attribute name="type" type="bt:byteType" <xs:attribute name="type" type="bt:byteType"
use="required"/> use="required"/>
</xs:extension> </xs:extension>
</xs:simpleContent> </xs:simpleContent>
</xs:complexType> </xs:complexType>
<xs:simpleType name="lldpOctetStringType"> <xs:simpleType name="lldpOctetStringType">
<xs:restriction base="xs:hexBinary"> <xs:restriction base="xs:hexBinary">
<xs:minLength value="1"/> <xs:minLength value="1"/>
<xs:maxLength value="255"/> <xs:maxLength value="255"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
</xs:schema> </xs:schema>
LLDP measurement schema LLDP measurement schema
8.5. DHCP Measurement Schema 8.5. DHCP Measurement Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
xmlns:dhcp="urn:ietf:params:xml:ns:geopriv:lm:dhcp" xmlns:dhcp="urn:ietf:params:xml:ns:geopriv:lm:dhcp"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:bt="urn:ietf:params:xml:ns:geopriv:lm:basetypes" xmlns:bt="urn:ietf:params:xml:ns:geopriv:lm:basetypes"
targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:dhcp" targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:dhcp"
elementFormDefault="qualified" elementFormDefault="qualified"
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
<xs:annotation> <xs:annotation>
<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"/>
<xs:element name="remote" <xs:element name="remote"
type="dhcp:dhcpRemoteType" minOccurs="0"/> type="dhcp:dhcpRemoteType" minOccurs="0"/>
<xs:element name="subscriber" <xs:element name="subscriber"
type="xs:hexBinary" minOccurs="0"/> type="xs:hexBinary" minOccurs="0"/>
<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: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="dhcpRemoteType"> <xs:complexType name="dhcpRemoteType">
<xs:simpleContent> <xs:simpleContent>
<xs:extension base="xs:hexBinary"> <xs:extension base="xs:hexBinary">
<xs:attribute name="enterprise" type="xs:positiveInteger" <xs:attribute name="enterprise" type="xs:positiveInteger"
use="optional"/> use="optional"/>
</xs:extension> </xs:extension>
</xs:simpleContent> </xs:simpleContent>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
DHCP measurement schema DHCP measurement schema
8.6. WiFi Measurement Schema 8.6. WiFi Measurement Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
xmlns:wifi="urn:ietf:params:xml:ns:geopriv:lm:wifi" xmlns:wifi="urn:ietf:params:xml:ns:geopriv:lm:wifi"
xmlns:bt="urn:ietf:params:xml:ns:geopriv:lm:basetypes" xmlns:bt="urn:ietf:params:xml:ns:geopriv:lm:basetypes"
xmlns:gml="http://www.opengis.net/gml" xmlns:gml="http://www.opengis.net/gml"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:wifi" targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:wifi"
elementFormDefault="qualified" elementFormDefault="qualified"
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"/>
<xs:element name="ap" type="wifi:wifiType" <xs:element name="ap" type="wifi:wifiType"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<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="ssid" type="wifi:ssidType" <xs:element name="ssid" type="wifi:ssidType"
minOccurs="0"/> 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"/> <xs:element name="flightTime" minOccurs="0"
<xs:element name="flightTime "minOccurs="0" type="bt:nnDoubleWithRMSError"/>
type="bt:nnDoubleWithRMSError"/> <xs:element name="apSignal" type="wifi:signalType"
<xs:element name="apSignal" type="wifi:signalType" minOccurs="0"/>
minOccurs="0"/> <xs:element name="deviceSignal" type="wifi:signalType"
<xs:element name="deviceSignal" type="wifi:signalType" minOccurs="0"/>
minOccurs="0"/> <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: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 <!-- Note that this pattern does not prevent multibyte UTF-8
sequences that result in a SSID longer than 32 octets. --> sequences that result in a SSID longer than 32 octets. -->
<xs:simpleType name="ssidType"> <xs:simpleType name="ssidType">
<xs:restriction base="xs:token"> <xs:restriction base="xs:token">
<xs:pattern value="(\\[\da-fA-F]{2}|[^\\]){0,32}"/> <xs:pattern value="(\\[\da-fA-F]{2}|[^\\]){0,32}"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </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>
<xs:restriction base="xs:token"> <xs:restriction base="xs:token">
<xs:pattern value="[A-Z]{2}[OIX]?"/> <xs:pattern value="[A-Z]{2}[OIX]?"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
</xs:attribute> </xs:attribute>
</xs:extension> </xs:extension>
</xs:simpleContent> </xs:simpleContent>
</xs:complexType> </xs:complexType>
<xs:simpleType name="octetType"> <xs:simpleType name="octetType">
<xs:restriction base="xs:nonNegativeInteger"> <xs:restriction base="xs:nonNegativeInteger">
<xs:maxInclusive value="255"/> <xs:maxInclusive value="255"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<xs:complexType name="signalType"> <xs:complexType name="signalType">
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType"> <xs:restriction base="xs:anyType">
<xs:sequence> <xs:sequence>
<xs:element name="transmit" type="xs:double" <xs:element name="transmit" type="xs:double"
minOccurs="0"/> minOccurs="0"/>
<xs:element name="gain" type="xs:double" minOccurs="0"/> <xs:element name="gain" type="xs:double" minOccurs="0"/>
<xs:element name="rcpi" type="wifi:rssiType" <xs:element name="rcpi" type="wifi:rssiType"
minOccurs="0"/> minOccurs="0"/>
<xs:element name="rsni" type="bt:doubleWithRMSError" <xs:element name="rsni" type="bt:doubleWithRMSError"
minOccurs="0"/> minOccurs="0"/>
<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:restriction> </xs:restriction>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
<xs:complexType name="rssiType"> <xs:complexType name="rssiType">
<xs:simpleContent> <xs:simpleContent>
<xs:extension base="bt:doubleWithRMSError"> <xs:extension base="bt:doubleWithRMSError">
<xs:attribute name="dBm" type="xs:boolean" default="true"/> <xs:attribute name="dBm" type="xs:boolean" default="true"/>
</xs:extension> </xs:extension>
</xs:simpleContent> </xs:simpleContent>
</xs:complexType> </xs:complexType>
<!-- Measurement Request elements --> <!-- Measurement Request elements -->
<xs:element name="type" type="wifi:networkType"/> <xs:element name="type" type="wifi:networkType"/>
<xs:element name="parameter" type="wifi:parameterType"/> <xs:element name="parameter" type="wifi:parameterType"/>
<xs:complexType name="parameterType"> <xs:complexType name="parameterType">
<xs:simpleContent> <xs:simpleContent>
<xs:extension base="xs:QName"> <xs:extension base="xs:QName">
<xs:attribute name="context" use="optional"> <xs:attribute name="context" use="optional">
<xs:simpleType> <xs:simpleType>
<xs:restriction base="xs:token"> <xs:restriction base="xs:token">
<xs:enumeration value="ap"/> <xs:enumeration value="ap"/>
<xs:enumeration value="device"/> <xs:enumeration value="device"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
</xs:attribute> </xs:attribute>
</xs:extension> </xs:extension>
</xs:simpleContent> </xs:simpleContent>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
WiFi measurement schema WiFi measurement schema
8.7. Cellular Measurement Schema 8.7. Cellular Measurement Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
xmlns:cell="urn:ietf:params:xml:ns:geopriv:lm:cell" xmlns:cell="urn:ietf:params:xml:ns:geopriv:lm:cell"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:cell" targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:cell"
elementFormDefault="qualified" elementFormDefault="qualified"
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
<xs:annotation> <xs:annotation>
<xs:appinfo <xs:appinfo
source="urn:ietf:params:xml:schema:geopriv:lm:cell"> source="urn:ietf:params:xml:schema:geopriv:lm:cell">
</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 cellular location measurements. This schema defines a set of cellular location measurements.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
<xs:element name="cellular" type="cell:cellularType"/> <xs:element name="cellular" type="cell:cellularType"/>
<xs:complexType name="cellularType"> <xs:complexType name="cellularType">
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType"> <xs:restriction base="xs:anyType">
<xs:sequence> <xs:sequence>
<xs:choice> <xs:choice>
<xs:element name="servingCell" type="cell:cellType"/> <xs:element name="servingCell" type="cell:cellType"/>
<xs:element name="observedCell" type="cell:cellType"/> <xs:element name="observedCell" type="cell:cellType"/>
</xs:choice> </xs:choice>
<xs:element name="observedCell" type="cell:cellType" <xs:element name="observedCell" type="cell:cellType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<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="cellType"> <xs:complexType name="cellType">
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType"> <xs:restriction base="xs:anyType">
<xs:choice> <xs:choice>
<xs:sequence> <xs:sequence>
<xs:element name="mcc" type="cell:mccType"/> <xs:element name="mcc" type="cell:mccType"/>
<xs:element name="mnc" type="cell:mncType"/> <xs:element name="mnc" type="cell:mncType"/>
<xs:choice> <xs:choice>
<xs:sequence> <xs:sequence>
<xs:choice> <xs:choice>
<xs:element name="rnc" type="cell:cellIdType"/> <xs:element name="rnc" type="cell:cellIdType"/>
<xs:element name="lac" type="cell:cellIdType"/> <xs:element name="lac" type="cell:cellIdType"/>
</xs:choice> </xs:choice>
<xs:element name="cid" type="cell:cellIdType"/> <xs:element name="cid" type="cell:cellIdType"/>
</xs:sequence> </xs:sequence>
<xs:element name="eucid" type="cell:cellIdType"/> <xs:element name="eucid" type="cell:cellIdType"/>
</xs:choice> </xs:choice>
<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:sequence> <xs:sequence>
<xs:element name="nid" type="cell:cellIdType"/> <xs:element name="sid" type="cell:cellIdType"/>
<xs:element name="sid" type="cell:cellIdType"/> <xs:element name="nid" type="cell:cellIdType"/>
<xs:element name="baseid" type="cell:cellIdType"/> <xs:element name="baseid" type="cell:cellIdType"/>
<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:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:choice> </xs:choice>
</xs:restriction> </xs:restriction>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
<xs:simpleType name="mccType"> <xs:simpleType name="mccType">
<xs:restriction base="xs:token"> <xs:restriction base="xs:token">
<xs:pattern value="[0-9]{3}"/>
<xs:pattern value="[0-9]{3}"/>
</xs:restriction> </xs:restriction>
</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="268435456"/> <!-- 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"/>
<xs:enumeration value="umts"/> <xs:enumeration value="umts"/>
<xs:enumeration value="lte"/> <xs:enumeration value="lte"/>
<xs:enumeration value="cdma"/> <xs:enumeration value="cdma"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<xs:element name="network" type="cell:networkType"/> <xs:element name="network" type="cell:networkType"/>
<xs:complexType name="networkType"> <xs:complexType name="networkType">
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType"> <xs:restriction base="xs:anyType">
<xs:choice> <xs:choice>
<xs:sequence> <xs:sequence>
<xs:element name="mcc" type="cell:mccType"/> <xs:element name="mcc" type="cell:mccType"/>
<xs:element name="mnc" type="cell:mncType"/> <xs:element name="mnc" type="cell:mncType"/>
</xs:sequence> </xs:sequence>
<xs:element name="nid" type="cell:cellIdType"/> <xs:element name="nid" type="cell:cellIdType"/>
</xs:choice> </xs:choice>
</xs:restriction> </xs:restriction>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Cellular measurement schema Cellular measurement schema
8.8. GNSS Measurement Schema 8.8. GNSS Measurement Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
xmlns:gnss="urn:ietf:params:xml:ns:geopriv:lm:gnss" xmlns:gnss="urn:ietf:params:xml:ns:geopriv:lm:gnss"
xmlns:bt="urn:ietf:params:xml:ns:geopriv:lm:basetypes" xmlns:bt="urn:ietf:params:xml:ns:geopriv:lm:basetypes"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:gnss" targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:gnss"
elementFormDefault="qualified" elementFormDefault="qualified"
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
<xs:annotation> <xs:annotation>
<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">
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType"> <xs:restriction base="xs:anyType">
<xs:sequence> <xs:sequence>
<xs:element name="gnssTime" type="bt:nnDoubleWithRMSError" <xs:element name="gnssTime" type="bt:nnDoubleWithRMSError"
minOccurs="0"/> minOccurs="0"/>
<xs:element name="sat" type="gnss:gnssSatelliteType" <xs:element name="sat" type="gnss:gnssSatelliteType"
minOccurs="1" maxOccurs="64"/> minOccurs="1" maxOccurs="64"/>
<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="system" type="xs:token" use="required"/> <xs:attribute name="system" type="xs:token" use="required"/>
<xs:attribute name="signal" type="xs:token"/> <xs:attribute name="signal" type="xs:token"/>
<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="gnssSatelliteType"> <xs:complexType name="gnssSatelliteType">
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType"> <xs:restriction base="xs:anyType">
<xs:sequence> <xs:sequence>
<xs:element name="doppler" type="bt:doubleWithRMSError"/> <xs:element name="doppler" type="bt:doubleWithRMSError"/>
<xs:element name="codephase" type="bt:nnDoubleWithRMSError"/> <xs:element name="codephase"
<xs:element name="cn0" type="bt:nonNegativeDouble"/> type="bt:nnDoubleWithRMSError"/>
<xs:element name="mp" type="bt:positiveDouble" <xs:element name="cn0" type="bt:nonNegativeDouble"/>
minOccurs="0"/> <xs:element name="mp" type="bt:positiveDouble"
<xs:element name="cq" type="gnss:codePhaseQualityType" minOccurs="0"/>
minOccurs="0"/> <xs:element name="cq" type="gnss:codePhaseQualityType"
<xs:element name="adr" type="xs:double" minOccurs="0"/> minOccurs="0"/>
</xs:sequence> <xs:element name="adr" type="xs:double" minOccurs="0"/>
<xs:attribute name="num" type="xs:positiveInteger" </xs:sequence>
use="required"/> <xs:attribute name="num" type="xs:positiveInteger"
</xs:restriction> use="required"/>
</xs:complexContent> </xs:restriction>
</xs:complexType> </xs:complexContent>
</xs:complexType>
<xs:complexType name="codePhaseQualityType"> <xs:complexType name="codePhaseQualityType">
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType"> <xs:restriction base="xs:anyType">
<xs:attribute name="continuous" type="xs:boolean" <xs:attribute name="continuous" type="xs:boolean"
default="true"/> default="true"/>
<xs:attribute name="direct" use="required"> <xs:attribute name="direct" use="required">
<xs:simpleType> <xs:simpleType>
<xs:restriction base="xs:token"> <xs:restriction base="xs:token">
<xs:enumeration value="direct"/> <xs:enumeration value="direct"/>
<xs:enumeration value="inverted"/> <xs:enumeration value="inverted"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
</xs:attribute> </xs:attribute>
</xs:restriction> </xs:restriction>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
GNSS measurement Schema GNSS measurement Schema
8.9. DSL Measurement Schema 8.9. DSL Measurement Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
xmlns:dsl="urn:ietf:params:xml:ns:geopriv:lm:dsl" xmlns:dsl="urn:ietf:params:xml:ns:geopriv:lm:dsl"
xmlns:bt="urn:ietf:params:xml:ns:geopriv:lm:basetypes" xmlns:bt="urn:ietf:params:xml:ns:geopriv:lm:basetypes"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:dsl" targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:dsl"
elementFormDefault="qualified" elementFormDefault="qualified"
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
<xs:annotation> <xs:annotation>
<xs:appinfo <xs:appinfo
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">
<xs:sequence> <xs:sequence>
<xs:element name="src" type="bt:ipAddressType"/> <xs:element name="src" type="bt:ipAddressType"/>
<xs:element name="dest" type="bt:ipAddressType"/> <xs:element name="dest" type="bt:ipAddressType"/>
<xs:element name="session" <xs:element name="session"
type="xs:nonNegativeInteger"/> type="xs:nonNegativeInteger"/>
</xs:sequence> </xs:sequence>
</xs:restriction> </xs:restriction>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
<xs:sequence> <xs:sequence>
<xs:element name="an" type="xs:token"/> <xs:element name="an" type="xs:token"/>
<xs:group ref="dsl:dslSlotPort"/> <xs:group ref="dsl:dslSlotPort"/>
</xs:sequence> </xs:sequence>
<xs:sequence> <xs:sequence>
<xs:element name="stag" type="dsl:vlanIDType"/> <xs:element name="stag" type="dsl:vlanIDType"/>
<xs:choice> <xs:choice>
<xs:sequence> <xs:sequence>
<xs:element name="ctag" type="dsl:vlanIDType"/> <xs:element name="ctag" type="dsl:vlanIDType"/>
<xs:group ref="dsl:dslSlotPort" minOccurs="0"/> <xs:group ref="dsl:dslSlotPort" minOccurs="0"/>
</xs:sequence> </xs:sequence>
<xs:group ref="dsl:dslSlotPort"/> <xs:group ref="dsl:dslSlotPort"/>
</xs:choice> </xs:choice>
</xs:sequence>
</xs:sequence> <xs:sequence>
<xs:sequence> <xs:element name="vpi" type="bt:byteType"/>
<xs:element name="vpi" type="bt:byteType"/> <xs:element name="vci" type="bt:twoByteType"/>
<xs:element name="vci" type="bt:twoByteType"/> </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:choice>
</xs:choice> <xs:anyAttribute namespace="##other" processContents="lax"/>
<xs:anyAttribute namespace="##other" processContents="lax"/> </xs:restriction>
</xs:restriction>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
<xs:simpleType name="vlanIDType"> <xs:simpleType name="vlanIDType">
<xs:restriction base="xs:nonNegativeInteger"> <xs:restriction base="xs:nonNegativeInteger">
<xs:maxInclusive value="4095"/> <xs:maxInclusive value="4095"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<xs:group name="dslSlotPort"> <xs:group name="dslSlotPort">
<xs:sequence> <xs:sequence>
<xs:element name="slot" type="xs:token"/> <xs:element name="slot" type="xs:token"/>
<xs:element name="port" type="xs:token"/> <xs:element name="port" type="xs:token"/>
</xs:sequence> </xs:sequence>
</xs:group> </xs:group>
</xs:schema> </xs:schema>
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
skipping to change at page 62, line 12 skipping to change at page 62, line 12
"urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc", as per the guidelines "urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc", as per the guidelines
in [RFC3688]. in [RFC3688].
URI: urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc URI: urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc
Registrant Contact: IETF, GEOPRIV working group, Registrant Contact: IETF, GEOPRIV working group,
(geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com). (geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com).
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head> <head>
<title>Measurement Source for PIDF-LO</title> <title>Measurement Source for PIDF-LO</title>
</head> </head>
<body> <body>
<h1>Namespace for Location Measurement Source</h1> <h1>Namespace for Location Measurement Source</h1>
<h2>urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc</h2> <h2>urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc</h2>
[[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX [[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX
with the RFC number for this specification.]] with the RFC number for this specification.]]
<p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p> <p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p>
</body> </body>
</html> </html>
END END
9.3. URN Sub-Namespace Registration for 9.3. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm urn:ietf:params:xml:ns:geopriv:lm
This section registers a new XML namespace, This section registers a new XML namespace,
"urn:ietf:params:xml:ns:geopriv:lm", as per the guidelines in "urn:ietf:params:xml:ns:geopriv:lm", as per the guidelines in
[RFC3688]. [RFC3688].
URI: urn:ietf:params:xml:ns:geopriv:lm URI: urn:ietf:params:xml:ns:geopriv:lm
Registrant Contact: IETF, GEOPRIV working group, Registrant Contact: IETF, GEOPRIV working group,
(geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com). (geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com).
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head> <head>
<title>Measurement Container</title> <title>Measurement Container</title>
</head> </head>
<body> <body>
<h1>Namespace for Location Measurement Container</h1> <h1>Namespace for Location Measurement Container</h1>
<h2>urn:ietf:params:xml:ns:geopriv:lm</h2> <h2>urn:ietf:params:xml:ns:geopriv:lm</h2>
[[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX [[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX
with the RFC number for this specification.]] with the RFC number for this specification.]]
<p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p> <p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p>
</body> </body>
</html> </html>
END END
9.4. URN Sub-Namespace Registration for 9.4. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:basetypes urn:ietf:params:xml:ns:geopriv:lm:basetypes
This section registers a new XML namespace, This section registers a new XML namespace,
"urn:ietf:params:xml:ns:geopriv:lm:basetypes", as per the guidelines "urn:ietf:params:xml:ns:geopriv:lm:basetypes", as per the guidelines
in [RFC3688]. in [RFC3688].
URI: urn:ietf:params:xml:ns:geopriv:lm:basetypes URI: urn:ietf:params:xml:ns:geopriv:lm:basetypes
Registrant Contact: IETF, GEOPRIV working group, Registrant Contact: IETF, GEOPRIV working group,
(geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com). (geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com).
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head> <head>
<title>Base Device Types</title> <title>Base Device Types</title>
</head> </head>
<body> <body>
<h1>Namespace for Base Types</h1> <h1>Namespace for Base Types</h1>
<h2>urn:ietf:params:xml:ns:geopriv:lm:basetypes</h2> <h2>urn:ietf:params:xml:ns:geopriv:lm:basetypes</h2>
[[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX [[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX
with the RFC number for this specification.]] with the RFC number for this specification.]]
<p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p> <p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p>
</body> </body>
</html> </html>
END
END
9.5. URN Sub-Namespace Registration for 9.5. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:lldp urn:ietf:params:xml:ns:geopriv:lm:lldp
This section registers a new XML namespace, This section registers a new XML namespace,
"urn:ietf:params:xml:ns:geopriv:lm:lldp", as per the guidelines in "urn:ietf:params:xml:ns:geopriv:lm:lldp", as per the guidelines in
[RFC3688]. [RFC3688].
URI: urn:ietf:params:xml:ns:geopriv:lm:lldp URI: urn:ietf:params:xml:ns:geopriv:lm:lldp
Registrant Contact: IETF, GEOPRIV working group, Registrant Contact: IETF, GEOPRIV working group,
(geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com). (geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com).
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head> <head>
<title>LLDP Measurement Set</title> <title>LLDP Measurement Set</title>
</head> </head>
<body> <body>
<h1>Namespace for LLDP Measurement Set</h1> <h1>Namespace for LLDP Measurement Set</h1>
<h2>urn:ietf:params:xml:ns:geopriv:lm:lldp</h2> <h2>urn:ietf:params:xml:ns:geopriv:lm:lldp</h2>
[[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX [[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX
with the RFC number for this specification.]] with the RFC number for this specification.]]
<p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p> <p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p>
</body> </body>
</html> </html>
END END
9.6. URN Sub-Namespace Registration for 9.6. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:dhcp urn:ietf:params:xml:ns:geopriv:lm:dhcp
This section registers a new XML namespace, This section registers a new XML namespace,
"urn:ietf:params:xml:ns:geopriv:lm:dhcp", as per the guidelines in "urn:ietf:params:xml:ns:geopriv:lm:dhcp", as per the guidelines in
[RFC3688]. [RFC3688].
URI: urn:ietf:params:xml:ns:geopriv:lm:dhcp URI: urn:ietf:params:xml:ns:geopriv:lm:dhcp
Registrant Contact: IETF, GEOPRIV working group, Registrant Contact: IETF, GEOPRIV working group,
(geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com). (geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com).
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head> <head>
<title>DHCP Measurement Set</title> <title>DHCP Measurement Set</title>
</head> </head>
<body> <body>
<h1>Namespace for DHCP Measurement Set</h1> <h1>Namespace for DHCP Measurement Set</h1>
<h2>urn:ietf:params:xml:ns:geopriv:lm:dhcp</h2> <h2>urn:ietf:params:xml:ns:geopriv:lm:dhcp</h2>
[[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX [[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX
with the RFC number for this specification.]] with the RFC number for this specification.]]
<p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p> <p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p>
</body> </body>
</html> </html>
END END
9.7. URN Sub-Namespace Registration for 9.7. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:wifi urn:ietf:params:xml:ns:geopriv:lm:wifi
This section registers a new XML namespace, This section registers a new XML namespace,
"urn:ietf:params:xml:ns:geopriv:lm:wifi", as per the guidelines in "urn:ietf:params:xml:ns:geopriv:lm:wifi", as per the guidelines in
[RFC3688]. [RFC3688].
URI: urn:ietf:params:xml:ns:geopriv:lm:wifi URI: urn:ietf:params:xml:ns:geopriv:lm:wifi
Registrant Contact: IETF, GEOPRIV working group, Registrant Contact: IETF, GEOPRIV working group,
(geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com). (geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com).
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head> <head>
<title>WiFi Measurement Set</title> <title>WiFi Measurement Set</title>
</head> </head>
<body> <body>
<h1>Namespace for WiFi Measurement Set</h1> <h1>Namespace for WiFi Measurement Set</h1>
<h2>urn:ietf:params:xml:ns:geopriv:lm:wifi</h2> <h2>urn:ietf:params:xml:ns:geopriv:lm:wifi</h2>
[[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX [[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX
with the RFC number for this specification.]] with the RFC number for this specification.]]
<p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p> <p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p>
</body> </body>
</html> </html>
END
END
9.8. URN Sub-Namespace Registration for 9.8. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:cell urn:ietf:params:xml:ns:geopriv:lm:cell
This section registers a new XML namespace, This section registers a new XML namespace,
"urn:ietf:params:xml:ns:geopriv:lm:cell", as per the guidelines in "urn:ietf:params:xml:ns:geopriv:lm:cell", as per the guidelines in
[RFC3688]. [RFC3688].
URI: urn:ietf:params:xml:ns:geopriv:lm:cell URI: urn:ietf:params:xml:ns:geopriv:lm:cell
Registrant Contact: IETF, GEOPRIV working group, Registrant Contact: IETF, GEOPRIV working group,
(geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com). (geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com).
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head> <head>
<title>Cellular Measurement Set</title> <title>Cellular Measurement Set</title>
</head> </head>
<body> <body>
<h1>Namespace for Cellular Measurement Set</h1> <h1>Namespace for Cellular Measurement Set</h1>
<h2>urn:ietf:params:xml:ns:geopriv:lm:cell</h2> <h2>urn:ietf:params:xml:ns:geopriv:lm:cell</h2>
[[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX [[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX
with the RFC number for this specification.]] with the RFC number for this specification.]]
<p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p> <p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p>
</body> </body>
</html> </html>
END END
9.9. URN Sub-Namespace Registration for 9.9. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:gnss urn:ietf:params:xml:ns:geopriv:lm:gnss
This section registers a new XML namespace, This section registers a new XML namespace,
"urn:ietf:params:xml:ns:geopriv:lm:gnss", as per the guidelines in "urn:ietf:params:xml:ns:geopriv:lm:gnss", as per the guidelines in
[RFC3688]. [RFC3688].
URI: urn:ietf:params:xml:ns:geopriv:lm:gnss URI: urn:ietf:params:xml:ns:geopriv:lm:gnss
Registrant Contact: IETF, GEOPRIV working group, Registrant Contact: IETF, GEOPRIV working group,
(geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com). (geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com).
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head> <head>
<title>GNSS Measurement Set</title> <title>GNSS Measurement Set</title>
</head> </head>
<body> <body>
<h1>Namespace for GNSS Measurement Set</h1> <h1>Namespace for GNSS Measurement Set</h1>
<h2>urn:ietf:params:xml:ns:geopriv:lm:gnss</h2> <h2>urn:ietf:params:xml:ns:geopriv:lm:gnss</h2>
[[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX [[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX
with the RFC number for this specification.]] with the RFC number for this specification.]]
<p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p> <p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p>
</body> </body>
</html> </html>
END END
9.10. URN Sub-Namespace Registration for 9.10. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:geopriv:lm:dsl urn:ietf:params:xml:ns:geopriv:lm:dsl
This section registers a new XML namespace, This section registers a new XML namespace,
"urn:ietf:params:xml:ns:geopriv:lm:dsl", as per the guidelines in "urn:ietf:params:xml:ns:geopriv:lm:dsl", as per the guidelines in
[RFC3688]. [RFC3688].
URI: urn:ietf:params:xml:ns:geopriv:lm:dsl URI: urn:ietf:params:xml:ns:geopriv:lm:dsl
Registrant Contact: IETF, GEOPRIV working group, Registrant Contact: IETF, GEOPRIV working group,
(geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com). (geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com).
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head> <head>
<title>DSL Measurement Set</title> <title>DSL Measurement Set</title>
</head> </head>
<body> <body>
<h1>Namespace for DSL Measurement Set</h1> <h1>Namespace for DSL Measurement Set</h1>
<h2>urn:ietf:params:xml:ns:geopriv:lm:dsl</h2> <h2>urn:ietf:params:xml:ns:geopriv:lm:dsl</h2>
[[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX [[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX
with the RFC number for this specification.]] with the RFC number for this specification.]]
<p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p> <p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p>
</body> </body>
</html> </html>
END
END
9.11. XML Schema Registration for Measurement Source Schema 9.11. XML Schema Registration for Measurement Source Schema
This section registers an XML schema as per the guidelines in This section registers an XML schema as per the guidelines in
[RFC3688]. [RFC3688].
URI: urn:ietf:params:xml:schema:pidf:geopriv10:lmsrc URI: urn:ietf:params:xml:schema:pidf:geopriv10:lmsrc
Registrant Contact: IETF, GEOPRIV working group, (geopriv@ietf.org), Registrant Contact: IETF, GEOPRIV working group, (geopriv@ietf.org),
Martin Thomson (martin.thomson@andrew.com). Martin Thomson (martin.thomson@andrew.com).
skipping to change at page 70, line 50 skipping to change at page 70, line 50
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. David Waitzman and John Bressler both noted corrections. David Waitzman and John Bressler both noted
shortcomings with 802.11 measurements. 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]
Cohen, A. and E. Shrum, "Migration to Ethernet-Based DSL Cohen, A. and E. Shrum, "Migration to Ethernet-Based DSL
Aggregation", April 2006. 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.
[I-D.ietf-geopriv-http-location-delivery]
Barnes, M., Winterbottom, J., Thomson, M., and B. Stark,
"HTTP Enabled Location Delivery (HELD)",
draft-ietf-geopriv-http-location-delivery-16 (work in
progress), August 2009.
[RFC0020] Cerf, V., "ASCII format for network interchange", RFC 20, [RFC0020] Cerf, V., "ASCII format for network interchange", RFC 20,
October 1969. 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 [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
Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, January 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 [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",
RFC 5491, March 2009. RFC 5491, March 2009.
[RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)",
RFC 5985, September 2010.
[TIA-2000.5]
TIA/EIA, "Upper Layer (Layer 3) Signaling Standard for
cdma2000(R) Spread Spectrum Systems", TIA-2000.5-D,
March 2004.
[TS.3GPP.23.003]
3GPP, "Numbering, addressing and identification", 3GPP
TS 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.
[GPS.SPOOF] [GPS.SPOOF]
Scott, L., "Anti-Spoofing and Authenticated Signal Scott, L., "Anti-Spoofing and Authenticated Signal
Architectures for Civil Navigation Signals", ION- Architectures for Civil Navigation Signals", ION-
GNSS Portland, Oregon, 2003. GNSS 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>.
[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-05 (work in draft-ietf-geopriv-held-identity-extensions-06 (work in
progress), October 2010. progress), November 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-06 (work in progress),
May 2010. March 2011.
[IANA.enterprise] [IANA.enterprise]
IANA, "Private Enterprise Numbers", IANA, "Private Enterprise Numbers", 2011,
<http://www.iana.org/assignments/enterprise-numbers>. <http://www.iana.org/assignments/enterprise-numbers>.
[IEEE.80211] [IEEE.80211]
IEEE, "Wireless LAN Medium Access Control (MAC) and IEEE, "Wireless LAN Medium Access Control (MAC) and
Physical Layer (PHY) specifications - IEEE 802.11 Wireless Physical Layer (PHY) specifications - IEEE 802.11 Wireless
Network Management", IEEE Std 802.11-2007, June 2007. Network Management", IEEE Std 802.11-2007, June 2007.
[IEEE.80211V] [IEEE.80211V]
IEEE, "Wireless LAN Medium Access Control (MAC) and IEEE, "Wireless LAN Medium Access Control (MAC) and
Physical Layer (PHY) specifications - IEEE 802.11 Wireless Physical Layer (PHY) specifications - IEEE 802.11 Wireless
Network Management (Draft)", P802.11v D12.0, June 2010. Network Management (Draft)", P802.11v D12.0, June 2010.
[IEEE.8021AB] [IEEE.8021AB]
IEEE, "IEEE Standard for Local and Metropolitan area IEEE, "IEEE Standard for Local and Metropolitan area
networks, Station and Media Access Control Connectivity networks, Station and Media Access Control Connectivity
Discovery", 802.1AB, June 2005. Discovery", 802.1AB, June 2005.
[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)", "Remote Authentication Dial In User Service (RADIUS)",
RFC 2865, June 2000. RFC 2865, June 2000.
[RFC3046] Patrick, M., "DHCP Relay Agent Information Option", [RFC3046] Patrick, M., "DHCP Relay Agent Information Option",
RFC 3046, January 2001. 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 [RFC3993] Johnson, R., Palaniappan, T., and M. Stapp, "Subscriber-ID
Suboption for the Dynamic Host Configuration Protocol Suboption for the Dynamic Host Configuration Protocol
(DHCP) Relay Agent Option", RFC 3993, March 2005. (DHCP) Relay Agent Option", RFC 3993, March 2005.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, February 2006.
[RFC4580] Volz, B., "Dynamic Host Configuration Protocol for IPv6 [RFC4580] Volz, B., "Dynamic Host Configuration Protocol for IPv6
(DHCPv6) Relay Agent Subscriber-ID Option", RFC 4580, (DHCPv6) Relay Agent Subscriber-ID Option", RFC 4580,
June 2006. June 2006.
[RFC4649] Volz, B., "Dynamic Host Configuration Protocol for IPv6 [RFC4649] Volz, B., "Dynamic Host Configuration Protocol for IPv6
(DHCPv6) Relay Agent Remote-ID Option", RFC 4649, (DHCPv6) Relay Agent Remote-ID Option", RFC 4649,
August 2006. August 2006.
[RFC5808] Marshall, R., "Requirements for a Location-by-Reference [RFC5808] Marshall, R., "Requirements for a Location-by-Reference
Mechanism", RFC 5808, May 2010. Mechanism", RFC 5808, May 2010.
Authors' Addresses Authors' Addresses
Martin Thomson Martin Thomson
Andrew Andrew
Andrew Building (39) Andrew Building (39)
University of Wollongong University of Wollongong
Northfields Avenue Northfields Avenue
Wollongong, NSW 2522 Wollongong, NSW 2522
AU AU
 End of changes. 205 change blocks. 
936 lines changed or deleted 947 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/