datatracker.ietf.org
Sign in
Version 5.6.2.p5, 2014-08-04
Report a bug

Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)
RFC 6848

Internet Engineering Task Force (IETF)                   J. Winterbottom
Request for Comments: 6848                                     CommScope
Updates: 4776, 5222                                           M. Thomson
Category: Standards Track                                          Skype
ISSN: 2070-1721                                                R. Barnes
                                                        BBN Technologies
                                                                B. Rosen
                                                           NeuStar, Inc.
                                                               R. George
                                                     Huawei Technologies
                                                            January 2013

                 Specifying Civic Address Extensions in
     the Presence Information Data Format Location Object (PIDF-LO)

Abstract

   New fields are occasionally added to civic addresses.  A backward-
   compatible mechanism for adding civic address elements to the Geopriv
   civic address format is described.  A formal mechanism for handling
   unsupported extensions when translating between XML and DHCP civic
   address forms is defined for entities that need to perform this
   translation.  Initial extensions for some new elements are also
   defined.  The Location-to-Service Translation (LoST) protocol
   mechanism (defined in RFC 5222) that returns civic address element
   names used for validation of location information is clarified and is
   normatively updated to require a qualifying namespace identifier on
   each civic address element returned as part of the validation
   process.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6848.

Winterbottom, et al.         Standards Track                    [Page 1]
RFC 6848                    Civic Extensions                January 2013

Copyright Notice

   Copyright (c) 2013 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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Motivating Example . . . . . . . . . . . . . . . . . . . .  4
     1.2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Specifying Civic Address Extensions  . . . . . . . . . . . . .  5
   3.  Translating Unsupported Elements . . . . . . . . . . . . . . .  6
     3.1.  XML to DHCP Format Translation . . . . . . . . . . . . . .  6
     3.2.  Extension Civic Address Type (CAtype)  . . . . . . . . . .  6
     3.3.  DHCP to XML Format Translation . . . . . . . . . . . . . .  7
     3.4.  Conversion Example . . . . . . . . . . . . . . . . . . . .  8
   4.  CAtypes Registry . . . . . . . . . . . . . . . . . . . . . . .  9
   5.  Civic Extensions . . . . . . . . . . . . . . . . . . . . . . .  9
     5.1.  Pole Number  . . . . . . . . . . . . . . . . . . . . . . .  9
     5.2.  Milepost . . . . . . . . . . . . . . . . . . . . . . . . . 10
     5.3.  Street Type Prefix . . . . . . . . . . . . . . . . . . . . 10
     5.4.  House Number Prefix  . . . . . . . . . . . . . . . . . . . 10
     5.5.  XML Extension Schema . . . . . . . . . . . . . . . . . . . 11
     5.6.  Extension Examples . . . . . . . . . . . . . . . . . . . . 11
   6.  Using Local Civic Extension with the LoST Protocol . . . . . . 12
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 13
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 13
     8.1.  CAtype Registration for Extensions . . . . . . . . . . . . 13
     8.2.  Changes to the CAtype Registry . . . . . . . . . . . . . . 14
     8.3.  Registration Template  . . . . . . . . . . . . . . . . . . 14
     8.4.  Registration of the CAtypes Defined in this Document . . . 15

[include full document text]