GeoPriv M. Linsner
Internet Draft Cisco Systems
Intended status: Standards Track A. Thomson
Expires: October 20, 2007 Cisco Systems
April 18, 2007
Relative Location for Civic Location Format
draft-linsner-geopriv-relativeloc-00.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is
aware have been or will be disclosed, and any of which he or she
becomes aware will be disclosed, in accordance with Section 6 of
BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on September 3, 2007.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract
This document defines additional civic address parameters for use in
Location Objects [1] and [4]. The format is based on the civic
address definition of PIDF-LO. These addition parameters allow
expression of a relative location.
Linsner & Thomson Expires October 20, 2007 [Page 1]
Internet-Draft Relative Location for PIDF-LO April 2007
Conventions used in this document
In examples, "C:" and "S:" indicate lines sent by the client and
server respectively.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [1].
Table of Contents
1. Introduction...................................................2
2. Additions to PIDF-LO...........................................3
3. Relative Location..............................................3
3.1. Examples of the relative location parameters..............4
4. Security Considerations........................................5
5. IANA Considerations............................................5
6. Acknowledgments................................................5
7. References.....................................................6
7.1. Normative References......................................6
7.2. Informative References....................................6
Author's Addresses................................................6
Intellectual Property Statement...................................6
Disclaimer of Validity............................................7
1. Introduction
Wireless LAN technologies are adding capabilities to locate serving
hosts via radio frequency measurement technologies. This new
capability is able to provide additional and more accurate location
information when used inside a building where GPS technologies are
normally not available. The data produced from these technologies
is most useful if expressed as relative position. Similar to global
positioning coordinate systems, designation of a reference starting
point is used. Differing from global positioning coordinate systems,
distance from the starting point is expressed as a 2 dimensional
measurement instead of geographic coordinates.
The data included within the relative position parameters is
supplementary to, not exclusive of, the existing civic location data
expressed in PIDF-LO, [1] and [4]. An example of this may be a
popular wireless hotspot located at 234 N. Main St. It is reasonable
to expect that 234 N. Main St. covers a geographic area that
encompasses several hundred square meters. The wireless network
architecture for this hotspot could include several wireless
infrastructure access points. The supplementary data provided via
Linsner & Thomson Expires October 20, 2007 [Page 2]
Internet-Draft Relative Location for PIDF-LO April 2007
relative location would enable a more granular location expression.
In addition to providing 234 N. Main St., a relative position like
"20 feet south and 40 feet east of the main entrance" could be added.
Although PIDF-LO civic location currently supports additional
elements, like CAtypes 28 (room), 32 (additional code), or 33 (seat),
results from the radio frequency measurement technologies are
alternatives to these existing elements and in some cases the
resultant value is more accurate.
2. Additions to PIDF-LO
PIDF-LO, as updated by [2], includes a full set of parameters used to
describe civic locations. The new parameters defined here are
additional to the updated set and provide a means to describe a
host's civic location with added granularity.
3. Relative Location
Relative location is defined by 2 new parameters, reference point and
relative position. Reference point, similar to geodetic datum,
defines the anchor point (0,0 point) used for measurement of the
relative position parameter. Measurement from the anchor point is
provided in 2 dimensions, X and Y. The east-west dimension is
labeled X and north-south dimension is labeled Y. Similar to the
well-known geodetic systems, a positive value is considered north of
the reference point, a negative value south of the reference point, a
positive value for east of the reference point and a negative value
for west of the reference point. A third value in this relative
position parameter defines the measurement unit (MU). Lack of
expressing a measurement unit defaults the unit value to meters.
The height or altitude parameter (Z) found in normal geodetic systems
is not expressed via these new parameters as this is already covered
by CAtype 27, the FLR or Floor parameter, previously defined for
PIDF-LO.
Linsner & Thomson Expires October 20, 2007 [Page 3]
Internet-Draft Relative Location for PIDF-LO April 2007
New Civic |CAtype | Description | Example
Field | | |
------------+-------+---------------------+---------------
REFPT | 40 |Reference Point | Elevator
------------+-------+---------------------+---------------
RELPOS | 41 |Relative Position | -12
| | |
| | | 35
| | |
| | | feet
Table 1: New Civic CAtypes
3.1. Examples of the relative location parameters
A location that is 20 meters west and 31 meters south of elevator-1
elevator-1
-20
-31
A location that is 51 feet north and 23 feet east of the corner
office
corner_office
23
51
Linsner & Thomson Expires October 20, 2007 [Page 4]
Internet-Draft Relative Location for PIDF-LO April 2007
feet
4. Security Considerations
The XML parameters defined in the document are additions to the
current PIDF-LO specification. Therefore the parameters defined here
are subject to the same security considerations of [1].
5. IANA Considerations
IANA will register CAtypes 40 and 41 as shown in Table 1 in the
CAtypes registry under the Geopriv Location Types Registries.
6. Acknowledgments
This document was prepared using 2-Word-v2.0.template.dot.
Linsner & Thomson Expires October 20, 2007 [Page 5]
Internet-Draft Relative Location for PIDF-LO April 2007
7. References
7.1. Normative References
[1] Petersen, J., "A Presence-based GEOPRIV Location Object
Format", RFC 4119, December 2005.
[2] Thomson, M. & Winterbottom, J., "Revised Civic Location Format
for PIDF-LO", draft-ietf-geopriv-revised-civic-lo-05.txt,
February 2007.
[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[4] Schulzrinne, H., "Dynamic Host Configuration Protocol (DHCPv4
and DHCPv6) Option for Civic Addresses Configuration
Information", RFC4776, November 2006
7.2. Informative References
Author's Addresses
Marc Linsner
Cisco Systems, Inc.
Marco Island, Florida, USA
Email: mlinsner@cisco.com
Allan Thomson
Cisco Systems, Inc.
San Jose, California, USA
Email: althomso@cisco.com
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Linsner & Thomson Expires October 20, 2007 [Page 6]
Internet-Draft Relative Location for PIDF-LO April 2007
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Linsner & Thomson Expires October 20, 2007 [Page 7]