draft-ietf-geopriv-relative-location-07.txt   draft-ietf-geopriv-relative-location-08.txt 
GEOPRIV M. Thomson GEOPRIV M. Thomson
Internet-Draft Microsoft Internet-Draft Microsoft
Intended status: Standards Track B. Rosen Intended status: Standards Track B. Rosen
Expires: February 16, 2014 Neustar Expires: March 10, 2014 Neustar
D. Stanley D. Stanley
Aruba Networks Aruba Networks
G. Bajko G. Bajko
Nokia Nokia
A. Thomson A. Thomson
Cisco Systems, Inc. Cisco Systems, Inc.
August 15, 2013 September 06, 2013
Relative Location Representation Relative Location Representation
draft-ietf-geopriv-relative-location-07 draft-ietf-geopriv-relative-location-08
Abstract Abstract
This document defines an extension to PIDF-LO (RFC4119) for the This document defines an extension to PIDF-LO (RFC4119) for the
expression of location information that is defined relative to a expression of location information that is defined relative to a
reference point. The reference point may be expressed as a geodetic reference point. The reference point may be expressed as a geodetic
or civic location, and the relative offset may be one of several or civic location, and the relative offset may be one of several
shapes. An alternative binary representation is described. shapes. An alternative binary representation is described.
Optionally, a reference to a secondary document (such as a map image) Optionally, a reference to a secondary document (such as a map image)
skipping to change at page 1, line 46 skipping to change at page 1, line 46
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 February 16, 2014. This Internet-Draft will expire on March 10, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
skipping to change at page 3, line 6 skipping to change at page 3, line 6
4.11.3. Map Example . . . . . . . . . . . . . . . . . . . . 22 4.11.3. Map Example . . . . . . . . . . . . . . . . . . . . 22
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 22 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.1. Civic PIDF with Polygon Offset . . . . . . . . . . . . . 22 5.1. Civic PIDF with Polygon Offset . . . . . . . . . . . . . 22
5.2. Geo PIDF with Circle Offset . . . . . . . . . . . . . . . 24 5.2. Geo PIDF with Circle Offset . . . . . . . . . . . . . . . 24
5.3. Civic TLV with Point Offset . . . . . . . . . . . . . . . 25 5.3. Civic TLV with Point Offset . . . . . . . . . . . . . . . 25
6. Schema Definition . . . . . . . . . . . . . . . . . . . . . . 25 6. Schema Definition . . . . . . . . . . . . . . . . . . . . . . 25
7. Security Considerations . . . . . . . . . . . . . . . . . . . 28 7. Security Considerations . . . . . . . . . . . . . . . . . . . 28
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
8.1. Relative Location Registry . . . . . . . . . . . . . . . 29 8.1. Relative Location Registry . . . . . . . . . . . . . . . 29
8.2. URN Sub-Namespace Registration . . . . . . . . . . . . . 30 8.2. URN Sub-Namespace Registration . . . . . . . . . . . . . 30
8.3. XML Schema Registration . . . . . . . . . . . . . . . . . 30 8.3. XML Schema Registration . . . . . . . . . . . . . . . . . 31
8.4. Geopriv Identifiers Registry . . . . . . . . . . . . . . 31 8.4. Geopriv Identifiers Registry . . . . . . . . . . . . . . 31
8.4.1. Registration of Two-Dimentional Relative Coordinate 8.4.1. Registration of Two-Dimentional Relative Coordinate
Reference System URN . . . . . . . . . . . . . . . . 32 Reference System URN . . . . . . . . . . . . . . . . 32
8.4.2. Registration of Three-Dimentional Relative Coordinate 8.4.2. Registration of Three-Dimentional Relative Coordinate
Reference System URN . . . . . . . . . . . . . . . . 32 Reference System URN . . . . . . . . . . . . . . . . 32
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 32 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 33
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 33 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 33
10.1. Normative References . . . . . . . . . . . . . . . . . . 33 10.1. Normative References . . . . . . . . . . . . . . . . . . 33
10.2. Informative References . . . . . . . . . . . . . . . . . 34 10.2. Informative References . . . . . . . . . . . . . . . . . 35
1. Introduction 1. Introduction
This document describes a format for the expression of relative This document describes a format for the expression of relative
location information. location information.
A relative location is formed of a reference location, plus a A relative location is formed of a reference location, plus a
relative offset from that reference location. The reference location relative offset from that reference location. The reference location
can be represented in either civic or geodetic form. The reference can be represented in either civic or geodetic form. The reference
location can also have dynamic components such as velocity. The location can also have dynamic components such as velocity. The
skipping to change at page 29, line 33 skipping to change at page 29, line 33
Values requested to be assigned into this registry MUST NOT conflict Values requested to be assigned into this registry MUST NOT conflict
with values assigned in the "Civic Address Types Registry (CAtypes)" with values assigned in the "Civic Address Types Registry (CAtypes)"
registry or vice versa, unless the IANA considerations section for registry or vice versa, unless the IANA considerations section for
the new value explicitly overrides this prohibition and the document the new value explicitly overrides this prohibition and the document
defining the value describes how conflicting TLV codes will be defining the value describes how conflicting TLV codes will be
interpreted by implementations. To ensure this, the CAtypes entries interpreted by implementations. To ensure this, the CAtypes entries
are explicitly reserved in the initial values table below. Those are explicitly reserved in the initial values table below. Those
reserved entries can be changed, but only with caution as explained reserved entries can be changed, but only with caution as explained
here. here.
To make this clear for future users of the registry, the following
note is added to the "Civic Address Types Registry (CAtypes)": The
registration of new values should be accompanied by a corresponding
reservation in the "Relative Location Parameters" registry.
Similarly, the "Relative Location Parameters" registry bears the
note: The registration of new values should be accompanied by a
corresponding reservation in the "Civic Address Types Registry
(CAtypes)" registry.
The values defined are: The values defined are:
+--------+----------------------------------------+-----------+ +--------+----------------------------------------+-----------+
| RLtype | description | Reference | | RLtype | description | Reference |
+--------+----------------------------------------+-----------+ +--------+----------------------------------------+-----------+
| 0-40 | RESERVED by CAtypes registry | this RFC | | 0-40 | RESERVED by CAtypes registry | this RFC |
| 128 | | & RFC4776 | | 128 | | & RFC4776 |
+--------+----------------------------------------+-----------+ +--------+----------------------------------------+-----------+
| 111 | relative location reference | this RFC | | 111 | relative location reference | this RFC |
| 113 | relative location shape 2D point | this RFC | | 113 | relative location shape 2D point | this RFC |
skipping to change at page 30, line 42 skipping to change at page 31, line 4
<title>GEOPRIV Relative Location</title> <title>GEOPRIV Relative Location</title>
</head> </head>
<body> <body>
<h1>Format for representing relative location</h1> <h1>Format for representing relative location</h1>
<h2>urn:ietf:params:xml:ns:pidf:geopriv10:relative</h2> <h2>urn:ietf:params:xml:ns:pidf:geopriv10:relative</h2>
<p>See <a href="http://www.rfc-editor.org/rfc/rfcXXXX.txt"> <p>See <a href="http://www.rfc-editor.org/rfc/rfcXXXX.txt">
RFCXXXX</a>.</p> RFCXXXX</a>.</p>
</body> </body>
</html> </html>
<!-- <!--
[[NOTE TO RFC-EDITOR: Please replace all instances of RFCXXXX [[NOTE TO RFC-EDITOR: Please replace all instances of RFCXXXX
with the number of the published document and remove this note.]] with the number of the published document and remove this note.]]
--> -->
END END
8.3. XML Schema Registration 8.3. XML Schema Registration
This section registers an XML schema as per the procedures in This section registers an XML schema as per the procedures in
[RFC3688]. [RFC3688].
URI: urn:ietf:params:xml:schema:pidf:geopriv10:relativeLocation URI: urn:ietf:params:xml:schema:pidf:geopriv10:relative
Registratant Contact: IETF, GEOPRIV working group Registratant Contact: IETF, GEOPRIV working group
(geopriv@ietf.org), Martin Thomson (martin.thomson@skype.net). (geopriv@ietf.org), Martin Thomson (martin.thomson@skype.net).
Schema The XML for this schema is found in Section 6 of this Schema The XML for this schema is found in Section 6 of this
document. document.
8.4. Geopriv Identifiers Registry 8.4. Geopriv Identifiers Registry
This section registers two URNs for use in identifying relative This section registers two URNs for use in identifying relative
 End of changes. 11 change blocks. 
8 lines changed or deleted 19 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/