Tech-invite3GPPspaceIETFspace
96959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 7105

Using Device-Provided Location-Related Measurements in Location Configuration Protocols

Pages: 74
Proposed Standard
Errata
Part 4 of 4 – Pages 51 to 74
First   Prev   None

Top   ToC   RFC7105 - Page 51   prevText

8.6. WiFi Measurement Schema

<?xml version="1.0"?> <xs:schema xmlns:wifi="urn:ietf:params:xml:ns:geopriv:lm:wifi" xmlns:bt="urn:ietf:params:xml:ns:geopriv:lm:basetypes" xmlns:gml="http://www.opengis.net/gml" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:wifi" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:annotation> <xs:appinfo source="urn:ietf:params:xml:schema:geopriv:lm:wifi"> 802.11 location measurements </xs:appinfo> <xs:documentation source="http://www.rfc-editor.org/rfc/rfc7105.txt"> This schema defines a basic set of 802.11 location measurements. </xs:documentation> </xs:annotation>
Top   ToC   RFC7105 - Page 52
    <xs:import namespace="urn:ietf:params:xml:ns:geopriv:lm:basetypes"/>
     <xs:import namespace="http://www.opengis.net/gml"/>

     <xs:element name="wifi" type="wifi:wifiNetworkType"/>

     <xs:complexType name="wifiNetworkType">
       <xs:complexContent>
         <xs:restriction base="xs:anyType">
           <xs:sequence>
             <xs:element name="nicType" type="xs:token"
                         minOccurs="0"/>
             <xs:element name="ap" type="wifi:wifiType"
                         maxOccurs="unbounded"/>
           </xs:sequence>
           <xs:anyAttribute namespace="##any" processContents="lax"/>
         </xs:restriction>
       </xs:complexContent>
     </xs:complexType>

     <xs:complexType name="wifiType">
       <xs:complexContent>
         <xs:restriction base="xs:anyType">
           <xs:sequence>
             <xs:element name="bssid" type="wifi:bssidType"/>
             <xs:element name="ssid" type="wifi:ssidType"
                         minOccurs="0"/>
             <xs:element name="channel" type="xs:nonNegativeInteger"
                         minOccurs="0"/>
             <xs:element name="location" minOccurs="0"
                         type="xs:anyType"/>
             <xs:element name="type" type="wifi:networkType"
                         minOccurs="0"/>
             <xs:element name="regclass" type="wifi:regclassType"
                         minOccurs="0"/>
             <xs:element name="antenna" type="wifi:octetType"
                         minOccurs="0"/>
             <xs:element name="flightTime" minOccurs="0"
                         type="bt:nnDoubleWithRMSError"/>
             <xs:element name="apSignal" type="wifi:signalType"
                         minOccurs="0"/>
             <xs:element name="deviceSignal" type="wifi:signalType"
                         minOccurs="0"/>
             <xs:any namespace="##other" processContents="lax"
                     minOccurs="0" maxOccurs="unbounded"/>
           </xs:sequence>
           <xs:attribute name="serving" type="xs:boolean"
                         default="false"/>
           <xs:anyAttribute namespace="##any" processContents="lax"/>
Top   ToC   RFC7105 - Page 53
         </xs:restriction>
       </xs:complexContent>
     </xs:complexType>

     <xs:complexType name="bssidType">
       <xs:simpleContent>
         <xs:extension base="bt:macAddressType">
           <xs:attribute name="verified" type="xs:boolean"
                         default="false"/>
         </xs:extension>
       </xs:simpleContent>
     </xs:complexType>

     <!-- Note that this pattern does not prevent multibyte UTF-8
          sequences that result in an SSID longer than 32 octets. -->
     <xs:simpleType name="ssidType">
       <xs:restriction base="xs:token">
         <xs:pattern value="(\\[\da-fA-F]{2}|[^\\]){0,32}"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="networkType">
       <xs:restriction base="xs:token">
         <xs:pattern value="[a-zA-Z]+"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:complexType name="regclassType">
       <xs:simpleContent>
         <xs:extension base="wifi:octetType">
           <xs:attribute name="country">
             <xs:simpleType>
               <xs:restriction base="xs:token">
                 <xs:pattern value="[A-Z]{2}[OIX]?"/>
               </xs:restriction>
             </xs:simpleType>
           </xs:attribute>
         </xs:extension>
       </xs:simpleContent>
     </xs:complexType>

     <xs:simpleType name="octetType">
       <xs:restriction base="xs:nonNegativeInteger">
         <xs:maxInclusive value="255"/>
       </xs:restriction>
     </xs:simpleType>
Top   ToC   RFC7105 - Page 54
     <xs:complexType name="signalType">
       <xs:complexContent>
         <xs:restriction base="xs:anyType">
           <xs:sequence>
             <xs:element name="transmit" type="xs:double"
                         minOccurs="0"/>
             <xs:element name="gain" type="xs:double" minOccurs="0"/>
             <xs:element name="rcpi" type="wifi:rssiType"
                         minOccurs="0"/>
             <xs:element name="rsni" type="bt:doubleWithRMSError"
                         minOccurs="0"/>
             <xs:any namespace="##other" processContents="lax"
                     minOccurs="0" maxOccurs="unbounded"/>
           </xs:sequence>
         </xs:restriction>
       </xs:complexContent>
     </xs:complexType>

     <xs:complexType name="rssiType">
       <xs:simpleContent>
         <xs:extension base="bt:doubleWithRMSError">
           <xs:attribute name="dBm" type="xs:boolean" default="true"/>
         </xs:extension>
       </xs:simpleContent>
     </xs:complexType>

     <!-- Measurement Request elements -->
     <xs:element name="type" type="wifi:networkType"/>
     <xs:element name="parameter" type="wifi:parameterType"/>

     <xs:complexType name="parameterType">
       <xs:simpleContent>
         <xs:extension base="xs:QName">
           <xs:attribute name="context" use="optional">
             <xs:simpleType>
               <xs:restriction base="xs:token">
                 <xs:enumeration value="ap"/>
                 <xs:enumeration value="device"/>
               </xs:restriction>
             </xs:simpleType>
           </xs:attribute>
         </xs:extension>
       </xs:simpleContent>
     </xs:complexType>
   </xs:schema>

                          WiFi Measurement Schema
Top   ToC   RFC7105 - Page 55

8.7. Cellular Measurement Schema

<?xml version="1.0"?> <xs:schema xmlns:cell="urn:ietf:params:xml:ns:geopriv:lm:cell" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:cell" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:annotation> <xs:appinfo source="urn:ietf:params:xml:schema:geopriv:lm:cell"> </xs:appinfo> <xs:documentation source="http://www.rfc-editor.org/rfc/rfc7105.txt"> This schema defines a set of cellular location measurements. </xs:documentation> </xs:annotation> <xs:element name="cellular" type="cell:cellularType"/> <xs:complexType name="cellularType"> <xs:complexContent> <xs:restriction base="xs:anyType"> <xs:sequence> <xs:choice> <xs:element name="servingCell" type="cell:cellType"/> <xs:element name="observedCell" type="cell:cellType"/> </xs:choice> <xs:element name="observedCell" type="cell:cellType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:anyAttribute namespace="##any" processContents="lax"/> </xs:restriction> </xs:complexContent> </xs:complexType> <xs:complexType name="cellType"> <xs:complexContent> <xs:restriction base="xs:anyType"> <xs:choice> <xs:sequence> <xs:element name="mcc" type="cell:mccType"/> <xs:element name="mnc" type="cell:mncType"/> <xs:choice> <xs:sequence> <xs:choice>
Top   ToC   RFC7105 - Page 56
                     <xs:element name="rnc" type="cell:cellIdType"/>
                     <xs:element name="lac" type="cell:cellIdType"/>
                   </xs:choice>
                   <xs:element name="cid" type="cell:cellIdType"/>
                 </xs:sequence>
                 <xs:element name="eucid" type="cell:cellIdType"/>
               </xs:choice>
               <xs:any namespace="##other" processContents="lax"
                       minOccurs="0" maxOccurs="unbounded"/>
             </xs:sequence>
             <xs:sequence>
               <xs:element name="sid" type="cell:cellIdType"/>
               <xs:element name="nid" type="cell:cellIdType"/>
               <xs:element name="baseid" type="cell:cellIdType"/>
               <xs:any namespace="##other" processContents="lax"
                       minOccurs="0" maxOccurs="unbounded"/>
             </xs:sequence>
             <xs:any namespace="##other" processContents="lax"
                     minOccurs="0" maxOccurs="unbounded"/>
           </xs:choice>
         </xs:restriction>
       </xs:complexContent>
     </xs:complexType>

     <xs:simpleType name="mccType">
       <xs:restriction base="xs:token">
         <xs:pattern value="[0-9]{3}"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="mncType">
       <xs:restriction base="xs:token">
         <xs:pattern value="[0-9]{2,3}"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:simpleType name="cellIdType">
       <xs:restriction base="xs:nonNegativeInteger">
         <xs:maxInclusive value="268435455"/> <!-- 2^28 (eucid) -->
       </xs:restriction>
     </xs:simpleType>

     <!-- Measurement Request elements -->
     <xs:element name="type" type="cell:typeType"/>
     <xs:simpleType name="typeType">
       <xs:restriction base="xs:token">
         <xs:enumeration value="gsm"/>
         <xs:enumeration value="umts"/>
Top   ToC   RFC7105 - Page 57
         <xs:enumeration value="lte"/>
         <xs:enumeration value="cdma"/>
       </xs:restriction>
     </xs:simpleType>

     <xs:element name="network" type="cell:networkType"/>
     <xs:complexType name="networkType">
       <xs:complexContent>
         <xs:restriction base="xs:anyType">
           <xs:choice>
             <xs:sequence>
               <xs:element name="mcc" type="cell:mccType"/>
               <xs:element name="mnc" type="cell:mncType"/>
             </xs:sequence>
             <xs:element name="nid" type="cell:cellIdType"/>
           </xs:choice>
         </xs:restriction>
       </xs:complexContent>
     </xs:complexType>
   </xs:schema>

                        Cellular Measurement Schema

8.8. GNSS Measurement Schema

<?xml version="1.0"?> <xs:schema xmlns:gnss="urn:ietf:params:xml:ns:geopriv:lm:gnss" xmlns:bt="urn:ietf:params:xml:ns:geopriv:lm:basetypes" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:gnss" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:annotation> <xs:appinfo source="urn:ietf:params:xml:schema:geopriv:lm:gnss"> </xs:appinfo> <xs:documentation source="http://www.rfc-editor.org/rfc/rfc7105.txt"> This schema defines a set of GNSS location measurements. </xs:documentation> </xs:annotation>
Top   ToC   RFC7105 - Page 58
    <xs:import namespace="urn:ietf:params:xml:ns:geopriv:lm:basetypes"/>

     <!-- GNSS -->
     <xs:element name="gnss" type="gnss:gnssMeasurementType">
       <xs:unique name="gnssSatellite">
         <xs:selector xpath="sat"/>
         <xs:field xpath="@num"/>
       </xs:unique>
     </xs:element>

     <xs:complexType name="gnssMeasurementType">
       <xs:complexContent>
         <xs:restriction base="xs:anyType">
           <xs:sequence>
             <xs:element name="gnssTime" type="bt:nnDoubleWithRMSError"
                         minOccurs="0"/>
             <xs:element name="sat" type="gnss:gnssSatelliteType"
                         minOccurs="1" maxOccurs="64"/>
             <xs:any namespace="##other" processContents="lax"
                     minOccurs="0" maxOccurs="unbounded"/>
           </xs:sequence>
           <xs:attribute name="system" type="xs:token" use="required"/>
           <xs:attribute name="signal" type="xs:token"/>
           <xs:anyAttribute namespace="##any" processContents="lax"/>
         </xs:restriction>
       </xs:complexContent>
     </xs:complexType>

     <xs:complexType name="gnssSatelliteType">
       <xs:complexContent>
         <xs:restriction base="xs:anyType">
           <xs:sequence>
             <xs:element name="doppler" type="bt:doubleWithRMSError"/>
             <xs:element name="codephase"
                         type="bt:nnDoubleWithRMSError"/>
             <xs:element name="cn0" type="bt:nonNegativeDouble"/>
             <xs:element name="mp" type="bt:positiveDouble"
                         minOccurs="0"/>
             <xs:element name="cq" type="gnss:codePhaseQualityType"
                         minOccurs="0"/>
             <xs:element name="adr" type="xs:double" minOccurs="0"/>
           </xs:sequence>
           <xs:attribute name="num" type="xs:positiveInteger"
                         use="required"/>
         </xs:restriction>
       </xs:complexContent>
     </xs:complexType>
Top   ToC   RFC7105 - Page 59
     <xs:complexType name="codePhaseQualityType">
       <xs:complexContent>
         <xs:restriction base="xs:anyType">
           <xs:attribute name="continuous" type="xs:boolean"
                         default="true"/>
           <xs:attribute name="direct" use="required">
             <xs:simpleType>
               <xs:restriction base="xs:token">
                 <xs:enumeration value="direct"/>
                 <xs:enumeration value="inverted"/>
               </xs:restriction>
             </xs:simpleType>
           </xs:attribute>
         </xs:restriction>
       </xs:complexContent>
     </xs:complexType>
   </xs:schema>

                          GNSS Measurement Schema

8.9. DSL Measurement Schema

<?xml version="1.0"?> <xs:schema xmlns:dsl="urn:ietf:params:xml:ns:geopriv:lm:dsl" xmlns:bt="urn:ietf:params:xml:ns:geopriv:lm:basetypes" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:dsl" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:annotation> <xs:appinfo source="urn:ietf:params:xml:schema:geopriv:lm:dsl"> DSL measurement definitions </xs:appinfo> <xs:documentation source="http://www.rfc-editor.org/rfc/rfc7105.txt"> This schema defines a basic set of DSL location measurements. </xs:documentation> </xs:annotation>
Top   ToC   RFC7105 - Page 60
    <xs:import namespace="urn:ietf:params:xml:ns:geopriv:lm:basetypes"/>

     <xs:element name="dsl" type="dsl:dslVlanType"/>
     <xs:complexType name="dslVlanType">
       <xs:complexContent>
         <xs:restriction base="xs:anyType">
           <xs:choice>
             <xs:element name="l2tp">
               <xs:complexType>
                 <xs:complexContent>
                   <xs:restriction base="xs:anyType">
                     <xs:sequence>
                       <xs:element name="src" type="bt:ipAddressType"/>
                       <xs:element name="dest" type="bt:ipAddressType"/>
                       <xs:element name="session"
                                   type="xs:nonNegativeInteger"/>
                     </xs:sequence>
                   </xs:restriction>
                 </xs:complexContent>
               </xs:complexType>
             </xs:element>
             <xs:sequence>
               <xs:element name="an" type="xs:token"/>
               <xs:group ref="dsl:dslSlotPort"/>
             </xs:sequence>
             <xs:sequence>
               <xs:element name="stag" type="dsl:vlanIDType"/>
               <xs:choice>
                 <xs:sequence>
                   <xs:element name="ctag" type="dsl:vlanIDType"/>
                   <xs:group ref="dsl:dslSlotPort" minOccurs="0"/>
                 </xs:sequence>
                 <xs:group ref="dsl:dslSlotPort"/>
               </xs:choice>
             </xs:sequence>
             <xs:sequence>
               <xs:element name="vpi" type="bt:byteType"/>
               <xs:element name="vci" type="bt:twoByteType"/>
             </xs:sequence>
             <xs:any namespace="##other" processContents="lax"
                     minOccurs="0" maxOccurs="unbounded"/>
           </xs:choice>
           <xs:anyAttribute namespace="##other" processContents="lax"/>
         </xs:restriction>
       </xs:complexContent>
     </xs:complexType>
Top   ToC   RFC7105 - Page 61
     <xs:simpleType name="vlanIDType">
       <xs:restriction base="xs:nonNegativeInteger">
         <xs:maxInclusive value="4095"/>
       </xs:restriction>
     </xs:simpleType>
     <xs:group name="dslSlotPort">
       <xs:sequence>
         <xs:element name="slot" type="xs:token"/>
         <xs:element name="port" type="xs:token"/>
       </xs:sequence>
     </xs:group>
   </xs:schema>

                          DSL Measurement Schema

9. IANA Considerations

This section creates a registry for GNSS types (Section 5.5) and registers the namespaces and schemas defined in Section 8.

9.1. IANA Registry for GNSS Types

This document establishes a new IANA registry for "Global Navigation Satellite System (GNSS)" types. The registry includes tokens for the GNSS type and for each of the signals within that type. Referring to [RFC5226], this registry operates under "Specification Required" rules. The IESG will appoint an Expert Reviewer who will advise IANA promptly on each request for a new or updated GNSS type. Each entry in the registry requires the following information: GNSS Name: the name of the GNSS Brief Description: a brief description of the GNSS GNSS Token: a token that can be used to identify the GNSS Signals: a set of tokens that represent each of the signals that the system provides Documentation Reference: a reference to one or more stable, public specifications that outline usage of the GNSS, including (but not limited to) signal specifications and time systems The registry initially includes two registrations: GNSS Name: Global Positioning System (GPS)
Top   ToC   RFC7105 - Page 62
   Brief Description:  a system of satellites that use spread-spectrum
      transmission, operated by the US military for commercial and
      military applications

   GNSS Token:  gps

   Signals:  L1, L2, L1C, L2C, L5

   Documentation Reference:  Navstar GPS Space Segment/Navigation User
      Interface [GPS.ICD]

   GNSS Name:  Galileo

   Brief Description:  a system of satellites that operate in the same
      spectrum as GPS, operated by the European Union for commercial
      applications

   GNSS Token:  galileo

   Signals:  L1, E5A, E5B, E5A+B, E6

   Documentation Reference:  Galileo Open Service Signal In Space
      Interface Control Document (SIS ICD) [Galileo.ICD]

9.2. URN Sub-Namespace Registration for urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc

This section registers a new XML namespace, "urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc", as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org), Martin Thomson (martin.thomson@gmail.com). XML: BEGIN <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <head> <title>Measurement Source for PIDF-LO</title> </head>
Top   ToC   RFC7105 - Page 63
         <body>
           <h1>Namespace for Location Measurement Source</h1>
           <h2>urn:ietf:params:xml:ns:pidf:geopriv10:lmsrc</h2>
           <p>See <a href="http://www.rfc-editor.org/rfc/rfc7105.txt">
              RFC 7105</a>.</p>
         </body>
       </html>
         END

9.3. URN Sub-Namespace Registration for urn:ietf:params:xml:ns:geopriv:lm

This section registers a new XML namespace, "urn:ietf:params:xml:ns:geopriv:lm", as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:ns:geopriv:lm Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org), Martin Thomson (martin.thomson@gmail.com). XML: BEGIN <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <head> <title>Measurement Container</title> </head> <body> <h1>Namespace for Location Measurement Container</h1> <h2>urn:ietf:params:xml:ns:geopriv:lm</h2> <p>See <a href="http://www.rfc-editor.org/rfc/rfc7105.txt"> RFC 7105</a>.</p> </body> </html> END

9.4. URN Sub-Namespace Registration for urn:ietf:params:xml:ns:geopriv:lm:basetypes

This section registers a new XML namespace, "urn:ietf:params:xml:ns:geopriv:lm:basetypes", as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:ns:geopriv:lm:basetypes
Top   ToC   RFC7105 - Page 64
      Registrant Contact: IETF, GEOPRIV working group
      (geopriv@ietf.org), Martin Thomson (martin.thomson@gmail.com).

      XML:

         BEGIN
       <?xml version="1.0"?>
       <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
         "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
       <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
         <head>
           <title>Base Device Types</title>
         </head>
         <body>
           <h1>Namespace for Base Types</h1>
           <h2>urn:ietf:params:xml:ns:geopriv:lm:basetypes</h2>
           <p>See <a href="http://www.rfc-editor.org/rfc/rfc7105.txt">
              RFC 7105</a>.</p>
         </body>
       </html>
         END

9.5. URN Sub-Namespace Registration for urn:ietf:params:xml:ns:geopriv:lm:lldp

This section registers a new XML namespace, "urn:ietf:params:xml:ns:geopriv:lm:lldp", as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:ns:geopriv:lm:lldp Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org), Martin Thomson (martin.thomson@gmail.com). XML: BEGIN <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <head> <title>LLDP Measurement Set</title> </head>
Top   ToC   RFC7105 - Page 65
         <body>
           <h1>Namespace for LLDP Measurement Set</h1>
           <h2>urn:ietf:params:xml:ns:geopriv:lm:lldp</h2>
           <p>See <a href="http://www.rfc-editor.org/rfc/rfc7105.txt">
              RFC 7105</a>.</p>
         </body>
       </html>
         END

9.6. URN Sub-Namespace Registration for urn:ietf:params:xml:ns:geopriv:lm:dhcp

This section registers a new XML namespace, "urn:ietf:params:xml:ns:geopriv:lm:dhcp", as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:ns:geopriv:lm:dhcp Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org), Martin Thomson (martin.thomson@gmail.com). XML: BEGIN <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <head> <title>DHCP Measurement Set</title> </head> <body> <h1>Namespace for DHCP Measurement Set</h1> <h2>urn:ietf:params:xml:ns:geopriv:lm:dhcp</h2> <p>See <a href="http://www.rfc-editor.org/rfc/rfc7105.txt"> RFC 7105</a>.</p> </body> </html> END

9.7. URN Sub-Namespace Registration for urn:ietf:params:xml:ns:geopriv:lm:wifi

This section registers a new XML namespace, "urn:ietf:params:xml:ns:geopriv:lm:wifi", as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:ns:geopriv:lm:wifi
Top   ToC   RFC7105 - Page 66
      Registrant Contact: IETF, GEOPRIV working group
      (geopriv@ietf.org), Martin Thomson (martin.thomson@gmail.com).

      XML:

         BEGIN
       <?xml version="1.0"?>
       <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
         "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
       <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
         <head>
           <title>WiFi Measurement Set</title>
         </head>
         <body>
           <h1>Namespace for WiFi Measurement Set</h1>
           <h2>urn:ietf:params:xml:ns:geopriv:lm:wifi</h2>
           <p>See <a href="http://www.rfc-editor.org/rfc/rfc7105.txt">
              RFC 7105</a>.</p>
         </body>
       </html>
         END

9.8. URN Sub-Namespace Registration for urn:ietf:params:xml:ns:geopriv:lm:cell

This section registers a new XML namespace, "urn:ietf:params:xml:ns:geopriv:lm:cell", as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:ns:geopriv:lm:cell Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org), Martin Thomson (martin.thomson@gmail.com). XML: BEGIN <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <head> <title>Cellular Measurement Set</title> </head>
Top   ToC   RFC7105 - Page 67
         <body>
           <h1>Namespace for Cellular Measurement Set</h1>
           <h2>urn:ietf:params:xml:ns:geopriv:lm:cell</h2>
           <p>See <a href="http://www.rfc-editor.org/rfc/rfc7105.txt">
              RFC 7105</a>.</p>
         </body>
       </html>
         END

9.9. URN Sub-Namespace Registration for urn:ietf:params:xml:ns:geopriv:lm:gnss

This section registers a new XML namespace, "urn:ietf:params:xml:ns:geopriv:lm:gnss", as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:ns:geopriv:lm:gnss Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org), Martin Thomson (martin.thomson@gmail.com). XML: BEGIN <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <head> <title>GNSS Measurement Set</title> </head> <body> <h1>Namespace for GNSS Measurement Set</h1> <h2>urn:ietf:params:xml:ns:geopriv:lm:gnss</h2> <p>See <a href="http://www.rfc-editor.org/rfc/rfc7105.txt"> RFC 7105</a>.</p> </body> </html> END

9.10. URN Sub-Namespace Registration for urn:ietf:params:xml:ns:geopriv:lm:dsl

This section registers a new XML namespace, "urn:ietf:params:xml:ns:geopriv:lm:dsl", as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:ns:geopriv:lm:dsl
Top   ToC   RFC7105 - Page 68
      Registrant Contact: IETF, GEOPRIV working group
      (geopriv@ietf.org), Martin Thomson (martin.thomson@gmail.com).

      XML:

         BEGIN
       <?xml version="1.0"?>
       <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
         "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
       <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
         <head>
           <title>DSL Measurement Set</title>
         </head>
         <body>
           <h1>Namespace for DSL Measurement Set</h1>
           <h2>urn:ietf:params:xml:ns:geopriv:lm:dsl</h2>
           <p>See <a href="http://www.rfc-editor.org/rfc/rfc7105.txt">
              RFC 7105</a>.</p>
         </body>
       </html>
         END

9.11. XML Schema Registration for Measurement Source Schema

This section registers an XML schema as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:schema:pidf:geopriv10:lmsrc Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org), Martin Thomson (martin.thomson@gmail.com). Schema: The XML for this schema can be found in Section 8.2 of this document.

9.12. XML Schema Registration for Measurement Container Schema

This section registers an XML schema as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:schema:geopriv:lm Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org), Martin Thomson (martin.thomson@gmail.com). Schema: The XML for this schema can be found in Section 8.1 of this document.
Top   ToC   RFC7105 - Page 69

9.13. XML Schema Registration for Base Types Schema

This section registers an XML schema as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:schema:geopriv:lm:basetypes Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org), Martin Thomson (martin.thomson@gmail.com). Schema: The XML for this schema can be found in Section 8.3 of this document.

9.14. XML Schema Registration for LLDP Schema

This section registers an XML schema as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:schema:geopriv:lm:lldp Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org), Martin Thomson (martin.thomson@gmail.com). Schema: The XML for this schema can be found in Section 8.4 of this document.

9.15. XML Schema Registration for DHCP Schema

This section registers an XML schema as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:schema:geopriv:lm:dhcp Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org), Martin Thomson (martin.thomson@gmail.com). Schema: The XML for this schema can be found in Section 8.5 of this document.

9.16. XML Schema Registration for WiFi Schema

This section registers an XML schema as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:schema:geopriv:lm:wifi Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org), Martin Thomson (martin.thomson@gmail.com).
Top   ToC   RFC7105 - Page 70
   Schema:  The XML for this schema can be found in Section 8.6 of this
      document.

9.17. XML Schema Registration for Cellular Schema

This section registers an XML schema as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:schema:geopriv:lm:cell Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org), Martin Thomson (martin.thomson@gmail.com). Schema: The XML for this schema can be found in Section 8.7 of this document.

9.18. XML Schema Registration for GNSS Schema

This section registers an XML schema as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:schema:geopriv:lm:gnss Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org), Martin Thomson (martin.thomson@gmail.com). Schema: The XML for this schema can be found in Section 8.8 of this document.

9.19. XML Schema Registration for DSL Schema

This section registers an XML schema as per the guidelines in [RFC3688]. URI: urn:ietf:params:xml:schema:geopriv:lm:dsl Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org), Martin Thomson (martin.thomson@gmail.com). Schema: The XML for this schema can be found in Section 8.9 of this document.

10. Acknowledgements

Thanks go to Simon Cox for his comments relating to terminology; his comments have helped ensure that this document is aligned with ongoing work in the Open Geospatial Consortium (OGC). Thanks to Neil Harper for his review and comments on the GNSS sections of this
Top   ToC   RFC7105 - Page 71
   document.  Thanks to Noor-E-Gagan Singh, Gabor Bajko, Russell Priebe,
   and Khalid Al-Mufti for their significant input to, and suggestions
   for, improving the 802.11 measurements.  Thanks to Cullen Jennings
   for feedback and suggestions.  Bernard Aboba provided review and
   feedback on a range of measurement data definitions.  Mary Barnes and
   Geoff Thompson provided a review and corrections.  David Waitzman and
   John Bressler both noted shortcomings with 802.11 measurements.
   Keith Drage and Darren Pawson provided expert LTE knowledge.

11. References

11.1. Normative References

[ASCII] ANSI, "US-ASCII. Coded Character Set - 7-Bit American Standard Code for Information Interchange. Standard ANSI X3.4-1986", 1986. [GPS.ICD] "Navstar GPS Space Segment/Navigation User Interface", ICD GPS-200, April 2000. [Galileo.ICD] GJU, "Galileo Open Service Signal In Space Interface Control Document (SIS ICD)", May 2006. [IANA.enterprise] IANA, "Private Enterprise Numbers", 2014, <http://www.iana.org/assignments/enterprise-numbers>. [IEEE.80211] IEEE, "Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications", IEEE Std 802.11-2012, March 2012. [IEEE.8021AB] IEEE, "IEEE Standard for Local and Metropolitan Area Networks, Station and Media Access Control Connectivity Discovery", IEEE Std 802.1AB-2009, September 2009. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3046] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046, January 2001. [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, July 2003.
Top   ToC   RFC7105 - Page 72
   [RFC3629]  Yergeau, F., "UTF-8, a transformation format of
              ISO 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.

   [RFC3993]  Johnson, R., Palaniappan, T., and M. Stapp, "Subscriber-ID
              Suboption for the Dynamic Host Configuration Protocol
              (DHCP) Relay Agent Option", RFC 3993, March 2005.

   [RFC4119]  Peterson, J., "A Presence-based GEOPRIV Location Object
              Format", RFC 4119, December 2005.

   [RFC4291]  Hinden, R. and S. Deering, "IP Version 6 Addressing
              Architecture", RFC 4291, February 2006.

   [RFC4580]  Volz, B., "Dynamic Host Configuration Protocol for IPv6
              (DHCPv6) Relay Agent Subscriber-ID Option", RFC 4580,
              June 2006.

   [RFC4649]  Volz, B., "Dynamic Host Configuration Protocol for IPv6
              (DHCPv6) Relay Agent Remote-ID Option", RFC 4649,
              August 2006.

   [RFC5491]  Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV
              Presence Information Data Format Location Object (PIDF-LO)
              Usage Clarification, Considerations, and Recommendations",
              RFC 5491, March 2009.

   [RFC5952]  Kawamura, S. and M. Kawashima, "A Recommendation for IPv6
              Address Text Representation", RFC 5952, August 2010.

   [RFC5985]  Barnes, M., "HTTP-Enabled Location Delivery (HELD)",
              RFC 5985, September 2010.

   [RFC5986]  Thomson, M. and J. Winterbottom, "Discovering the Local
              Location Information Server (LIS)", RFC 5986,
              September 2010.

   [TIA-2000.5]
              TIA/EIA, "Upper Layer (Layer 3) Signaling Standard for
              cdma2000(R) Spread Spectrum Systems", TR-45.5 / TSG-C
              TIA-2000.5-E / C.S0005-E v1.0, September 2009.
Top   ToC   RFC7105 - Page 73
   [TS.3GPP.23.003]
              3GPP, "Numbering, addressing and identification", 3GPP TS
              23.003 12.0.0, September 2013,
              <http://www.3gpp.org/ftp/Specs/html-info/23003.htm>.

11.2. Informative References

[ANSI-TIA-1057] ANSI/TIA, "Link Layer Discovery Protocol for Media Endpoint Devices", TIA 1057, April 2006. [DSL.TR025] Wang, R., "Core Network Architecture Recommendations for Access to Legacy Data Networks over ADSL", September 1999. [DSL.TR101] Cohen, A. and E. Shrum, "Migration to Ethernet-Based DSL Aggregation", April 2006. [GPS.SPOOF] Scott, L., "Anti-Spoofing and Authenticated Signal Architectures for Civil Navigation Signals", ION-GNSS Portland, Oregon, 2003. [HARPER] Harper, N., "Server-side GPS and Assisted-GPS in Java", December 2009. [RFC2661] Townsley, W., Valencia, A., Rubens, A., Pall, G., Zorn, G., and B. Palter, "Layer Two Tunneling Protocol "L2TP"", RFC 2661, August 1999. [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, "Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June 2000. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RFC3693] Cuellar, J., Morris, J., Mulligan, D., Peterson, J., and J. Polk, "Geopriv Requirements", RFC 3693, February 2004. [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. [RFC6155] Winterbottom, J., Thomson, M., Tschofenig, H., and R. Barnes, "Use of Device Identity in HTTP-Enabled Location Delivery (HELD)", RFC 6155, March 2011.
Top   ToC   RFC7105 - Page 74
   [RFC6280]  Barnes, R., Lepinski, M., Cooper, A., Morris, J.,
              Tschofenig, H., and H. Schulzrinne, "An Architecture for
              Location and Location Privacy in Internet Applications",
              BCP 160, RFC 6280, July 2011.

Authors' Addresses

Martin Thomson Mozilla Suite 300 650 Castro Street Mountain View, CA 94041 US EMail: martin.thomson@gmail.com James Winterbottom Unaffiliated AU EMail: a.james.winterbottom@gmail.com