idnits 2.17.1
draft-george-ecrit-lamp-post-02.txt:
Checking boilerplate required by RFC 5378 and the IETF Trust (see
https://trustee.ietf.org/license-info):
----------------------------------------------------------------------------
** You're using the IETF Trust Provisions' Section 6.b License Notice from
12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See
https://trustee.ietf.org/license-info/)
Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
----------------------------------------------------------------------------
No issues found here.
Checking nits according to https://www.ietf.org/id-info/checklist :
----------------------------------------------------------------------------
No issues found here.
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the IETF Trust and authors Copyright Line does not
match the current year
== The document doesn't use any RFC 2119 keywords, yet seems to have RFC
2119 boilerplate text.
-- The document date (March 8, 2010) is 5162 days in the past. Is this
intentional?
Checking references for intended status: Informational
----------------------------------------------------------------------------
== Unused Reference: 'RFC3693' is defined on line 195, but no explicit
reference was found in the text
Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 1 comment (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
2 ECRIT R. George
3 Internet-Draft Q. Sun
4 Intended status: Informational Huawei Technologies
5 Expires: September 9, 2010 H. Schulzrinne
6 Columbia University
7 B. Rosen
8 NeuStar
9 March 8, 2010
11 Civic Location Format Extension for Utility and Lamp Post Numbers
12 draft-george-ecrit-lamp-post-02
14 Abstract
16 This document describes an extension to civic location format and
17 adds two new CAtypes: PN (pole number) and MP (milepost). Pole
18 Numbers are used on poles such as lamp posts or utility poles, and
19 can be used in some circumstances as location information. Mileposts
20 are numeric values measured from an end of a trail, road, railway
21 line or other feature.
23 Status of this Memo
25 This Internet-Draft is submitted to IETF in full conformance with the
26 provisions of BCP 78 and BCP 79.
28 Internet-Drafts are working documents of the Internet Engineering
29 Task Force (IETF), its areas, and its working groups. Note that
30 other groups may also distribute working documents as Internet-
31 Drafts.
33 Internet-Drafts are draft documents valid for a maximum of six months
34 and may be updated, replaced, or obsoleted by other documents at any
35 time. It is inappropriate to use Internet-Drafts as reference
36 material or to cite them other than as "work in progress."
38 The list of current Internet-Drafts can be accessed at
39 http://www.ietf.org/ietf/1id-abstracts.txt.
41 The list of Internet-Draft Shadow Directories can be accessed at
42 http://www.ietf.org/shadow.html.
44 This Internet-Draft will expire on September 9, 2010.
46 Copyright Notice
48 Copyright (c) 2010 IETF Trust and the persons identified as the
49 document authors. All rights reserved.
51 This document is subject to BCP 78 and the IETF Trust's Legal
52 Provisions Relating to IETF Documents
53 (http://trustee.ietf.org/license-info) in effect on the date of
54 publication of this document. Please review these documents
55 carefully, as they describe your rights and restrictions with respect
56 to this document. Code Components extracted from this document must
57 include Simplified BSD License text as described in Section 4.e of
58 the Trust Legal Provisions and are provided without warranty as
59 described in the BSD License.
61 Table of Contents
63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
64 2. Terminology Used in This Document . . . . . . . . . . . . . . . 3
65 3. Pole Number and Milepost . . . . . . . . . . . . . . . . . . . 4
66 4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
67 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
68 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
69 6.1. CAtype Registry Update . . . . . . . . . . . . . . . . . . 5
70 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
71 7.1. Normative References . . . . . . . . . . . . . . . . . . . 5
72 7.2. Informative References . . . . . . . . . . . . . . . . . . 6
73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
75 1. Introduction
77 In some areas, utility and lamp posts carry a unique identifier,
78 which we call a pole number in this document. In some countries, the
79 label on the lamp post also carries the local emergency service
80 number, such as "110", encouraging callers to use the pole number to
81 identify their location.
83 _.-----,===.
84 | | (''''')
85 | | `---'
86 | |
87 | | ,---------,
88 | | ,---, |Emergency|
89 | | /|,-.|----->| Number |
90 | | / |110| '---------'
91 | | / |`-'|
92 |_|/ | 2 | ,---------,
93 | | | 1 | |Lamp Post|
94 | | | 2 |----->| Number |
95 |-| | 1 | '---------'
96 | |\ | 0 |
97 | | \ | 1 |
98 | | \ | 4 |
99 | | \|,,,|
100 _ | |
101 ``-..|.|
102 ``--.._
103 `'--.._
105 Lamp post with emergency number.
107 On some roads, and many trails, railroad rights of way and other
108 linear features, a post with a mile or kilometer distance from one
109 end of the feature may be found (a "milepost"). There are other
110 cases of poles or markers with numeric indications that are not the
111 same as a "house number" or street address number.
113 In this document, we define an extension of the civic address format
114 defined in [RFC4119] updated by [RFC5139] to carry such pole number
115 and milepost information.
117 2. Terminology Used in This Document
119 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
120 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
121 document are to be interpreted as described in [RFC2119].
123 3. Pole Number and Milepost
125 [RFC4776] and [RFC5139] provides a full set of parameters that may be
126 used to describe a civic location.
128 This document describes two new CAtypes, PN (pole number), which is
129 used to support post numbers, and MP (milepost), which is used to
130 support mileposts. The pole number can consist of any combination of
131 letters and digits. Punctuation characters and embedded spaces are
132 ignored; lower and upper case letters are treated as equivalent.
133 Mileposts are traditionally mile or kilometer distances from one end
134 of the feature, but the field may contain any combination of letters,
135 digits and punctuation characters. There could be country specific
136 considerations for PN or MP use, but none are described in this
137 document.
139 +---------+--------+-------------------------------+--------------+
140 | CAtype | PIDF | Description | Example |
141 +---------+--------+-------------------------------+--------------+
142 | 43 | PN | lamp post number | A12101S |
143 +---------+--------+-------------------------------+--------------+
144 | 44 | MP | Milepost | 102.4 |
145 +---------+--------+-------------------------------+--------------+
147 Table 1: New Civic PIDF-LO Types
149 4. Examples
150
152 CN
153 GD
154 Shenzhen
155 Bantian
156 Wuhe
157 Bai Cao Yuan
158 Front Gate
159 Video Rental Store
160 518129
161 2121014
162
164
166 US
167 PA
168 Hopewell
169 Baker Trail
170 11.4
171
173 5. Security Considerations
175 The security considerations of [RFC4119] is relevant to this
176 document. No new security considerations arise as a result of these
177 new fields
179 6. IANA Considerations
181 6.1. CAtype Registry Update
183 This document updates the CAtype registry established by [RFC4776].
184 Two entries are defined, with values as indicated in Table 1.
186 7. References
188 7.1. Normative References
190 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
191 Requirement Levels", BCP 14, RFC 2119, March 1997.
193 7.2. Informative References
195 [RFC3693] Cuellar, J., Morris, J., Mulligan, D., Peterson, J., and
196 J. Polk, "Geopriv Requirements", RFC 3693, February 2004.
198 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
199 Format", RFC 4119, December 2005.
201 [RFC4776] Schulzrinne, H., "Dynamic Host Configuration Protocol
202 (DHCPv4 and DHCPv6) Option for Civic Addresses
203 Configuration Information", RFC 4776, November 2006.
205 [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location
206 Format for Presence Information Data Format Location
207 Object (PIDF-LO)", RFC 5139, February 2008.
209 Authors' Addresses
211 Robins George
212 Huawei Technologies
213 Huawei Base, Bantian, Longgang District
214 Shenzhen, Guangdong 518129
215 P. R. China
217 Phone: +86-755-28788314
218 Email: robinsg@huawei.com
220 Qian Sun
221 Huawei Technologies
222 Huawei Base, Bantian, Longgang District
223 Shenzhen, Guangdong 518129
224 P. R. China
226 Phone: +86-755-28787351
227 Email: sunqian@huawei.com
228 Henning Schulzrinne
229 Columbia University
230 Department of Computer Science
231 450 Computer Science Building, New York NY, 10027
232 US
234 Phone: +1 212 939 7004
235 Email: hgs@cs.columbia.edu
236 URI: http://www.cs.columbia.edu
238 Brian Rosen
239 NeuStar, Inc.
240 470 Conrad Dr
241 Mars, PA 16046
242 US
244 Email: br@brianrosen.net