[Docs] [txt|pdf|xml|html] [Tracker] [Email] [Nits] [IPR]

Versions: 00 draft-ietf-geopriv-prefix

Network Working Group                                           B. Rosen
Internet-Draft                                                   NeuStar
Intended status: Informational                              July 3, 2009
Expires: January 4, 2010


         Prefix elements for Road and House Numbers in PIDF-LO
                     draft-rosen-geopriv-prefix-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 January 4, 2010.

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 in effect on the date of
   publication of this document (http://trustee.ietf.org/license-info).
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.

Abstract

   RFC4119 updated by RFC5139 defines suffixes for street names and
   house numbers, but does not define prefixes.  Both occur regularly in
   addresses and CAtypes are needed for them.  This memo defines STP



Rosen                    Expires January 4, 2010                [Page 1]


Internet-Draft            Road and House Prefix                July 2009


   Street Prefix and HNP house number prefix CAtypes.


Table of Contents

   1.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
     1.1.  Prefixes in addressing  . . . . . . . . . . . . . . . . . . 3
     1.2.  Security Considerations . . . . . . . . . . . . . . . . . . 3
     1.3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . 3
   2.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 3
     2.1.  Normative References  . . . . . . . . . . . . . . . . . . . 3
     2.2.  Informative References  . . . . . . . . . . . . . . . . . . 4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 4






































Rosen                    Expires January 4, 2010                [Page 2]


Internet-Draft            Road and House Prefix                July 2009


1.  Terminology

   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].

1.1.  Prefixes in addressing

   In [RFC4119] one can define a PIDF for 123 Main Street but not 123
   Boulevard Coranado.  There is an STS CAtype for a suffix, but no
   corresponding prefix.  [RFC5139] added PRM Premodifier and POM
   Postmodifier, but those are not suitable for the purpose.

   Similarly, one can express 123B Main, but not H123 Main.  Although
   one can include such letters in the house number, most addressing
   authorities keep the number numeric only to facilitate sorting, and
   have prefix and suffix fields for alphanumerics that appear in front
   of or following the numeric house number.

   To remedy this situation, new CAtypes are required: STP for a street
   (road) prefix, and HNP for a house number prefix.

1.2.  Security Considerations

   The XML representation described in this document is designed for
   inclusion in a PIDF-LO document.  As such, it is subject to the same
   security considerations as are described in [RFC4119].
   Considerations relating to the inclusion of this representation in
   other XML documents are outside the scope of this document.

1.3.  IANA Considerations

   This document updates the civic address type registry established by
   [RFC4776].  Two additional value are added:

       41      STP    Street (Road) Prefix
       42      HNP    House Number Prefix


2.  References

2.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC4119]  Peterson, J., "A Presence-based GEOPRIV Location Object
              Format", RFC 4119, December 2005.



Rosen                    Expires January 4, 2010                [Page 3]


Internet-Draft            Road and House Prefix                July 2009


2.2.  Informative References

   [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.


Author's Address

   Brian Rosen
   NeuStar, Inc.
   470 Conrad Dr
   Mars, PA  16046
   US

   Email: br@brianrosen.net































Rosen                    Expires January 4, 2010                [Page 4]


Html markup produced by rfcmarkup 1.129c, available from https://tools.ietf.org/tools/rfcmarkup/