ECRIT R. George
Internet-Draft Q. Sun
Intended status: Standards Track Huawei Technologies
Expires: August 28, 2009 H. Schulzrinne
Columbia University
February 24, 2009
Civic Location Format Extension for Utility and Lamp Post Numbers
draft-george-ecrit-lamp-post-00
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and 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 August 28, 2009.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
George, et al. Expires August 28, 2009 [Page 1]
Internet-Draft Civic Location Format Extension February 2009
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Abstract
This document describes an extension to civic location format and
adds new element PN (pole number). PN carries pole number
information which can identify a civic location.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology Used in This Document . . . . . . . . . . . . . . . 4
3. Additional Civic Address Type . . . . . . . . . . . . . . . . . 4
4. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5
George, et al. Expires August 28, 2009 [Page 2]
Internet-Draft Civic Location Format Extension February 2009
1. Introduction
In many cities in China, utility and lamp posts carry a unique
identifier, which we call a pole number in this document. In some
countries, the label on the lamp post also carries the local
emergency service number, such as "110", encouraging callers to use
the pole number to identify their location. This method is initially
provided and implemented in China by Shenzhen police department.
(One suspects that this is particularly useful in cities where street
naming and numbering systems make it difficult to accurately identify
locations.)
The pole number is also useful to report broken street lights. The
major disadvantage is that callers would have to enter the pole
number manually, although it may be possible in the future to simply
point a camera phone at the number and have it recognize the number
using pattern recognition.
In this document, we define an extension of the civic address format
[RFC XXXX] to carry such pole number information. The following
figure is a diagram for this kind of lamp post number. "110" in the
circle is emergency service number or PSAP.
_.-----,===.
| | (''''')
| | `---'
| |
| | ,---------,
| | ,---, |Emergency|
| | /|,-.|----->| Number |
| | / |110| '---------'
| | / |`-'|
|_|/ | 2 | ,---------,
| | | 1 | |Lamp Post|
| | | 2 |----->| Number |
|-| | 1 | '---------'
| |\ | 0 |
| | \ | 1 |
| | \ | 4 |
| | \|,,,|
_ | |
``-..|.|
``--.._
`'--.._
Lamp post with emergency number.
George, et al. Expires August 28, 2009 [Page 3]
Internet-Draft Civic Location Format Extension February 2009
2. Terminology Used in This Document
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 [RFC2119].
3. Additional Civic Address Type
[RFC4776] and [RFC5139] provides a full set of parameters that may be
used to describe a civic location. Specifically, [RFC4776] lists
several civic address types (CAtypes) that require support in the
formal PIDF-LO definition that are not in [RFC4119].
The new element, PN (pole number), is used to support Lamp Post
number in street addresses. The pole number can consist of any
combination of letters and digits. Punctuation characters and
embedded spaces are ignored; lower and upper case letters are treated
as equivalent.
+-----------+--------+-------------------------------+--------------+
| New Field | CAtype | Description | Example |
+-----------+--------+-------------------------------+--------------+
| PN | 40 | lamp post number | 2121014 |
+-----------+--------+-------------------------------+--------------+
4. Example
<civicAddress xml:lang="en-AU"
xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">
<country> CN </country>
<A1> GD </A1>
<A3> Shenzhen </A3>
<A4> Bantian </A4>
<RD> Wuhe </RD>
<LMK> Bai Cao Yuan </LMK>
<LOC> Front Gate </LOC>
<NAM> Video Rental Store </NAM>
<PC> 518129 </PC>
<PN> 2121014 </PN>
</civicAddress>
George, et al. Expires August 28, 2009 [Page 4]
Internet-Draft Civic Location Format Extension February 2009
5. Security Considerations
TBD
6. IANA Considerations
TBD
7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
7.2. Informative References
[RFC3693] Cuellar, J., Morris, J., Mulligan, D., Peterson, J., and
J. Polk, "Geopriv Requirements", RFC 3693, February 2004.
[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
Format", RFC 4119, December 2005.
[RFC4776] Schulzrinne, H., "Dynamic Host Configuration Protocol
(DHCPv4 and DHCPv6) Option for Civic Addresses
Configuration Information", RFC 4776, November 2006.
[RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location
Format for Presence Information Data Format Location
Object (PIDF-LO)", RFC 5139, February 2008.
Authors' Addresses
Robins George
Huawei Technologies
Huawei Base, Bantian, Longgang District
Shenzhen, Guangdong 518129
P. R. China
Phone: +86-755-28788314
Email: robinsg@huawei.com
George, et al. Expires August 28, 2009 [Page 5]
Internet-Draft Civic Location Format Extension February 2009
Qian Sun
Huawei Technologies
Huawei Base, Bantian, Longgang District
Shenzhen, Guangdong 518129
P. R. China
Phone: +86-755-28787351
Email: sunqian@huawei.com
Henning Schulzrinne
Columbia University
Department of Computer Science
450 Computer Science Building, New York NY, 10027
US
Phone: +1 212 939 7004
Email: hgs@cs.columbia.edu
URI: http://www.cs.columbia.edu
George, et al. Expires August 28, 2009 [Page 6]