idnits 2.17.00 (12 Aug 2021) /tmp/idnits55429/draft-george-geopriv-lamp-post-00.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 (July 1, 2010) is 4335 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC3693' is defined on line 194, 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 GEOPRIV R. George 3 Internet-Draft Huawei Technologies 4 Intended status: Standards Track H. Schulzrinne 5 Expires: January 2, 2011 Columbia University 6 B. Rosen 7 NeuStar, Inc 8 July 1, 2010 10 Civic Location Format Extension for Utility and Lamp Post Numbers 11 draft-george-geopriv-lamp-post-00 13 Abstract 15 This document describes an extension to civic location format and 16 adds two new CAtypes: PN (pole number) and MP (milepost). Pole 17 Numbers are used on poles such as lamp posts or utility poles, and 18 can be used in some circumstances as location information. Mileposts 19 are numeric values measured from an end of a trail, road, railway 20 line or other feature. 22 Status of this Memo 24 This Internet-Draft is submitted to IETF in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF), its areas, and its working groups. Note that 29 other groups may also distribute working documents as Internet- 30 Drafts. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 The list of current Internet-Drafts can be accessed at 38 http://www.ietf.org/ietf/1id-abstracts.txt. 40 The list of Internet-Draft Shadow Directories can be accessed at 41 http://www.ietf.org/shadow.html. 43 This Internet-Draft will expire on January 2, 2011. 45 Copyright Notice 47 Copyright (c) 2010 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 2. Terminology Used in This Document . . . . . . . . . . . . . . . 4 64 3. Pole Number and Milepost . . . . . . . . . . . . . . . . . . . 4 65 4. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 67 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 68 6.1. CAtype Registry Update . . . . . . . . . . . . . . . . . . 5 69 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 70 7.1. Normative References . . . . . . . . . . . . . . . . . . . 5 71 7.2. Informative References . . . . . . . . . . . . . . . . . . 6 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 74 1. Introduction 76 In some areas, utility and lamp posts carry a unique identifier, 77 which we call a pole number in this document. In some countries, the 78 label on the lamp post also carries the local emergency service 79 number, such as "110", encouraging callers to use the pole number to 80 identify their location. 82 _.-----,===. 83 | | (''''') 84 | | `---' 85 | | 86 | | ,---------, 87 | | ,---, |Emergency| 88 | | /|,-.|----->| Number | 89 | | / |110| '---------' 90 | | / |`-'| 91 |_|/ | 2 | ,---------, 92 | | | 1 | |Lamp Post| 93 | | | 2 |----->| Number | 94 |-| | 1 | '---------' 95 | |\ | 0 | 96 | | \ | 1 | 97 | | \ | 4 | 98 | | \|,,,| 99 _ | | 100 ``-..|.| 101 ``--.._ 102 `'--.._ 104 Lamp post with emergency number. 106 On some roads, and many trails, railroad rights of way and other 107 linear features, a post with a mile or kilometer distance from one 108 end of the feature may be found (a "milepost"). There are other 109 cases of poles or markers with numeric indications that are not the 110 same as a "house number" or street address number. 112 In this document, we define an extension of the civic address format 113 defined in [RFC4119] updated by [RFC5139] to carry such pole number 114 and milepost information. 116 2. Terminology Used in This Document 118 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 119 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 120 document are to be interpreted as described in [RFC2119]. 122 3. Pole Number and Milepost 124 [RFC4776] and [RFC5139] provides a full set of parameters that may be 125 used to describe a civic location. 127 This document describes two new CAtypes, PN (pole number), which is 128 used to support post numbers, and MP (milepost), which is used to 129 support mileposts. The pole number can consist of any combination of 130 letters and digits. Punctuation characters and embedded spaces are 131 ignored; lower and upper case letters are treated as equivalent. 132 Mileposts are traditionally mile or kilometer distances from one end 133 of the feature, but the field may contain any combination of letters, 134 digits and punctuation characters. There could be country specific 135 considerations for PN or MP use, but none are described in this 136 document. 138 +---------+--------+-------------------------------+--------------+ 139 | CAtype | PIDF | Description | Example | 140 +---------+--------+-------------------------------+--------------+ 141 | 43 | PN | lamp post number | A12101S | 142 +---------+--------+-------------------------------+--------------+ 143 | 44 | MP | Milepost | 102.4 | 144 +---------+--------+-------------------------------+--------------+ 146 Table 1: New Civic PIDF-LO Types 148 4. Example 149 151 CN 152 GD 153 Shenzhen 154 Bantian 155 Wuhe 156 Bai Cao Yuan 157 Front Gate 158 Video Rental Store 159 518129 160 2121014 161 163 165 US 166 PA 167 Hopewell 168 Baker Trail 169 11.4 170 172 5. Security Considerations 174 The security considerations of [RFC4119] is relevant to this 175 document. No new security considerations arise as a result of these 176 new fields 178 6. IANA Considerations 180 6.1. CAtype Registry Update 182 This document updates the CAtype registry established by [RFC4776]. 183 Two entries are defined, with values as indicated in Table 1. 185 7. References 187 7.1. Normative References 189 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 190 Requirement Levels", BCP 14, RFC 2119, March 1997. 192 7.2. Informative References 194 [RFC3693] Cuellar, J., Morris, J., Mulligan, D., Peterson, J., and 195 J. Polk, "Geopriv Requirements", RFC 3693, February 2004. 197 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 198 Format", RFC 4119, December 2005. 200 [RFC4776] Schulzrinne, H., "Dynamic Host Configuration Protocol 201 (DHCPv4 and DHCPv6) Option for Civic Addresses 202 Configuration Information", RFC 4776, November 2006. 204 [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location 205 Format for Presence Information Data Format Location 206 Object (PIDF-LO)", RFC 5139, February 2008. 208 Authors' Addresses 210 Robins George 211 Huawei Technologies 212 Huawei Base, Bantian, Longgang District 213 Shenzhen, Guangdong 518129 214 P. R. China 216 Phone: +86-755-28788314 217 Email: robinsg@huawei.com 219 Henning Schulzrinne 220 Columbia University 221 Department of Computer Science 222 450 Computer Science Building, New York NY, 10027 223 US 225 Phone: +1 212 939 7004 226 Email: hgs@cs.columbia.edu 227 URI: http://www.cs.columbia.edu 229 Brian Rosen 230 NeuStar, Inc. 231 470 Conrad Dr 232 Mars, PA 16046 233 US 235 Email: br@brianrosen.net