draft-ietf-geopriv-local-civic-08.txt   draft-ietf-geopriv-local-civic-09.txt 
GEOPRIV J. Winterbottom GEOPRIV J. Winterbottom
Internet-Draft CommScope Internet-Draft CommScope
Updates: 5222 (if approved) M. Thomson Updates: 5222,4776 (if approved) M. Thomson
Intended status: Standards Track Skype Intended status: Standards Track Skype
Expires: April 4, 2013 R. Barnes Expires: April 4, 2013 R. Barnes
BBN Technologies BBN Technologies
B. Rosen B. Rosen
NeuStar, Inc. NeuStar, Inc.
R. George R. George
Huawei Technologies Huawei Technologies
Oct 2012 Oct 2012
Specifying Civic Address Extensions in PIDF-LO Specifying Civic Address Extensions in PIDF-LO
draft-ietf-geopriv-local-civic-08 draft-ietf-geopriv-local-civic-09
Abstract Abstract
New fields are occasionally added to civic addresses. A backwardly- New fields are occasionally added to civic addresses. A backwardly-
compatible mechanism for adding civic address elements to the Geopriv compatible mechanism for adding civic address elements to the Geopriv
civic address format is described. A formal mechanism for handling civic address format is described. A formal mechanism for handling
unsupported extensions when translating between XML and DHCP civic unsupported extensions when translating between XML and DHCP civic
address forms is defined for entities that need to perform this address forms is defined for entities that need to perform this
translation. Intial extensions for some new elements are also translation. Intial extensions for some new elements are also
defined. The LoST (RFC5222) protocol mechanism that returns civic defined. The LoST (RFC5222) protocol mechanism that returns civic
skipping to change at page 2, line 22 skipping to change at page 2, line 22
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Motivating Example . . . . . . . . . . . . . . . . . . . . 4 1.1. Motivating Example . . . . . . . . . . . . . . . . . . . . 4
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. Specifying Civic Address Extensions . . . . . . . . . . . . . 4 2. Specifying Civic Address Extensions . . . . . . . . . . . . . 5
3. Translating Unsupported Elements . . . . . . . . . . . . . . . 6 3. Translating Unsupported Elements . . . . . . . . . . . . . . . 6
3.1. XML to DHCP Format Translation . . . . . . . . . . . . . . 6 3.1. XML to DHCP Format Translation . . . . . . . . . . . . . . 6
3.2. Extension Civic Address Type (CAtype) . . . . . . . . . . 6 3.2. Extension Civic Address Type (CAtype) . . . . . . . . . . 6
3.3. DHCP to XML Format Translation . . . . . . . . . . . . . . 7 3.3. DHCP to XML Format Translation . . . . . . . . . . . . . . 7
3.4. Conversion Example . . . . . . . . . . . . . . . . . . . . 8 3.4. Conversion Example . . . . . . . . . . . . . . . . . . . . 8
4. CAtypes Registry . . . . . . . . . . . . . . . . . . . . . . . 8 4. CAtypes Registry . . . . . . . . . . . . . . . . . . . . . . . 8
5. Civic Extensions . . . . . . . . . . . . . . . . . . . . . . . 9 5. Civic Extensions . . . . . . . . . . . . . . . . . . . . . . . 9
5.1. Pole Number . . . . . . . . . . . . . . . . . . . . . . . 9 5.1. Pole Number . . . . . . . . . . . . . . . . . . . . . . . 9
5.2. Mile Post . . . . . . . . . . . . . . . . . . . . . . . . 10 5.2. Mile Post . . . . . . . . . . . . . . . . . . . . . . . . 10
5.3. Street Type Prefix . . . . . . . . . . . . . . . . . . . . 10 5.3. Street Type Prefix . . . . . . . . . . . . . . . . . . . . 10
skipping to change at page 3, line 15 skipping to change at page 3, line 15
1. Introduction 1. Introduction
The Geopriv civic location specifications ([RFC4776], [RFC5139]) The Geopriv civic location specifications ([RFC4776], [RFC5139])
define an XML and binary representations for civic addresses that define an XML and binary representations for civic addresses that
allow for the expression of civic addresses. Guidance for the use of allow for the expression of civic addresses. Guidance for the use of
these formats for the civic addresses in different countries is these formats for the civic addresses in different countries is
included in [RFC5774]. included in [RFC5774].
Subsequent to these specifications being produced, use cases for Subsequent to these specifications being produced, use cases for
extending the civic address format with new elements have emerged. extending the civic address format with new elements have emerged.
Extension elements do not readily fit existing elements, as [RFC5774] describes a mechanism for mapping long-standing address
recommended in [RFC5774]. formats into the civic address elements defined in [RFC4776] and
[RFC5139]. However, some of these existing address elements do not
readily fit into the civic address elements defined in [RFC4776] and
[RFC5139]. In these cases creating new civic address elements
provides a better solution than overloading existing civic address
fields which may cause confusion.
The XML format for civic addresses [RFC5139] provides a mechanism The XML format for civic addresses [RFC5139] provides a mechanism
that allows for the addition of standardized or privately understood that allows for the addition of standardized or privately understood
elements. A similar facility for private extension is not provided elements. A similar facility for private extension is not provided
for the DHCP format [RFC4776], though new specifications are able to for the DHCP format [RFC4776], though new specifications are able to
define new CAtypes (civic address types). define new CAtypes (civic address types).
A recipient of a civic address in either format currently has no A recipient of a civic address in either format currently has no
option other than to ignore elements that it does not understand. option other than to ignore elements that it does not understand.
This results in any elements that are unknown to that recipient being This results in any elements that are unknown to that recipient being
skipping to change at page 6, line 39 skipping to change at page 6, line 42
Extensions to the XML format [RFC5139] are defined in a new XML Extensions to the XML format [RFC5139] are defined in a new XML
namespace [XMLNS]. namespace [XMLNS].
Extensions in the XML format can be added to a DHCP format civic Extensions in the XML format can be added to a DHCP format civic
address using an extension CAtype. address using an extension CAtype.
3.2. Extension Civic Address Type (CAtype) 3.2. Extension Civic Address Type (CAtype)
The extension CAtype (CAtype code XX) [Note to IANA/RFC-Editor: The extension CAtype (CAtype code XX) [Note to IANA/RFC-Editor:
please replace XX here and in the figure below with the assigned please replace XX here and in Figure 3 and in Figure 5 with the
code] includes three values that uniquely identify the XML extension assigned code] includes three values that uniquely identify the XML
and its value: a namespace URI, the local name of the XML element, extension and its value: a namespace URI, the local name of the XML
and the text content of that element. These three values are all element, and the text content of that element. These three values
included in the value of the CAtype, each separated by a single are all included in the value of the CAtype, each separated by a
whitespace character. single whitespace character.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CAtype (XX) | Length | Namespace URI ... . | CAtype (XX) | Length | Namespace URI ... .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. Namespace URI (continued) ... . . Namespace URI (continued) .
. ... .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Space (U+20) | XML element local name ... . | Space (U+20) | XML element local name .
+---------------+ .
. ... .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Space (U+20) | Extension type value ... . | Space (U+20) | Extension type value .
+---------------+ .
. ... .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: XML Civic Address Extension CAtype Figure 3: XML Civic Address Extension CAtype
CAtype (XX) identifies the extension CAtype.
Length is the number of octets used to represent the namespace URI,
local name and value.
The content of a CAtype (after the CAtype code and length) is UTF-8 The content of a CAtype (after the CAtype code and length) is UTF-8
encoded Unicode text [RFC3629]. A maximum of 255 octets is allowed. encoded Unicode text [RFC3629]. A maximum of 255 octets is allowed.
Octets consumed by the namespace URI and local name reduce the space Octets consumed by the namespace URI and local name reduce the space
available for values. available for values.
This conversion only works for elements that have textual content and This conversion only works for elements that have textual content and
an optional "xml:lang" attribute. Elements with complex content or an optional "xml:lang" attribute. Elements with complex content or
other attributes - aside from namespace bindings - MUST be ignored if other attributes - aside from namespace bindings - MUST be ignored if
they are not understood. they are not understood.
skipping to change at page 14, line 12 skipping to change at page 14, line 12
This document alters the "CAtypes" registry on the "Civic Address This document alters the "CAtypes" registry on the "Civic Address
Types Registry" page established by [RFC4776]. Types Registry" page established by [RFC4776].
8.1. CAtype Registration for Extensions 8.1. CAtype Registration for Extensions
IANA has allocated a CAtype code of XX for the extension CAtype. IANA has allocated a CAtype code of XX for the extension CAtype.
Registrations using this code will be made below, in Section 8.4. Registrations using this code will be made below, in Section 8.4.
8.2. Changes to the CAtype Registry 8.2. Changes to the CAtype Registry
IANA ia asked to make the following changes to the CAtype registry: IANA is asked to make the following changes to the CAtype registry:
o No registrations of new CAtype numbers in the Civic Address Types o No registrations of new CAtype numbers in the Civic Address Types
Registry are permitted, except by IESG Approval [RFC5226] under Registry are permitted, except by IESG Approval [RFC5226] under
unusual circumstances. unusual circumstances.
o The following note will be placed in the header of the CAtypes o The following note will be placed in the header of the CAtypes
registry, above the table: registry, above the table:
Note: As specified in [[this RFC]], new registrations are only Note: As specified in [[this RFC]], new registrations are only
accepted for CAtype XX, using the template specified in accepted for CAtype XX, using the template specified in
 End of changes. 10 change blocks. 
15 lines changed or deleted 33 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/