idnits 2.17.1 draft-ietf-geopriv-prefix-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 date (January 19, 2010) is 5203 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC2119' is defined on line 113, but no explicit reference was found in the text Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group B. Rosen 3 Internet-Draft NeuStar 4 Intended status: Informational January 19, 2010 5 Expires: July 23, 2010 7 Prefix elements for Road and House Numbers in PIDF-LO 8 draft-ietf-geopriv-prefix-00 10 Abstract 12 RFC4119 updated by RFC5139 defines suffixes for street names and 13 house numbers, but does not define prefixes. Both occur regularly in 14 addresses and CAtypes are needed for them. This memo defines STP 15 Street Prefix and HNP house number prefix CAtypes. 17 Status of this Memo 19 This Internet-Draft is submitted to IETF in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF), its areas, and its working groups. Note that 24 other groups may also distribute working documents as Internet- 25 Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt. 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 This Internet-Draft will expire on July 23, 2010. 40 Copyright Notice 42 Copyright (c) 2010 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the BSD License. 55 Table of Contents 57 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 1.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3 59 1.2. Prefixes in addressing . . . . . . . . . . . . . . . . . . 3 60 1.3. Security Considerations . . . . . . . . . . . . . . . . . . 3 61 1.4. IANA Considerations . . . . . . . . . . . . . . . . . . . . 3 62 2. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 2.1. Normative References . . . . . . . . . . . . . . . . . . . 4 64 2.2. Informative References . . . . . . . . . . . . . . . . . . 4 65 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4 67 1. Terminology 69 This document uses terminology described in [RFC4119]. 71 1.1. Introduction 73 RFC4119 updated by RFC5139 defines suffixes for street names and 74 house numbers, but does not define prefixes. Both occur regularly in 75 addresses and CAtypes are needed for them. This memo defines STP 76 Street Prefix and HNP house number prefix CAtypes. 78 1.2. Prefixes in addressing 80 In [RFC4119] one can define a PIDF for 123 Main Street but not 123 81 Boulevard Coranado. There is an STS CAtype for a suffix, but no 82 corresponding prefix. [RFC5139] added PRM Premodifier and POM 83 Postmodifier, but those are not suitable for the purpose. 85 Similarly, one can express 123B Main, but not H123 Main. Although 86 one can include such letters in the house number, most addressing 87 authorities keep the number numeric only to facilitate sorting, and 88 have prefix and suffix fields for alphanumerics that appear in front 89 of or following the numeric house number. 91 To remedy this situation, new CAtypes are required: STP for a street 92 (road) prefix, and HNP for a house number prefix. 94 1.3. Security Considerations 96 The XML representation described in this document is designed for 97 inclusion in a PIDF-LO document. As such, it is subject to the same 98 security considerations as are described in [RFC4119]. 99 Considerations relating to the inclusion of this representation in 100 other XML documents are outside the scope of this document. 102 1.4. IANA Considerations 104 This document updates the civic address type registry established by 105 [RFC4776]. Two additional value are added: 107 41 STP Street (Road) Prefix 108 42 HNP House Number Prefix 110 2. References 111 2.1. Normative References 113 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 114 Requirement Levels", BCP 14, RFC 2119, March 1997. 116 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 117 Format", RFC 4119, December 2005. 119 2.2. Informative References 121 [RFC4776] Schulzrinne, H., "Dynamic Host Configuration Protocol 122 (DHCPv4 and DHCPv6) Option for Civic Addresses 123 Configuration Information", RFC 4776, November 2006. 125 [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location 126 Format for Presence Information Data Format Location 127 Object (PIDF-LO)", RFC 5139, February 2008. 129 Author's Address 131 Brian Rosen 132 NeuStar, Inc. 133 470 Conrad Dr 134 Mars, PA 16046 135 US 137 Email: br@brianrosen.net