draft-ietf-geopriv-local-civic-06.txt | draft-ietf-geopriv-local-civic-07.txt | |||
---|---|---|---|---|
GEOPRIV J. Winterbottom | GEOPRIV J. Winterbottom | |||
Internet-Draft CommScope | Internet-Draft CommScope | |||
Updates: 5222 (if approved) M. Thomson | Updates: 5222 (if approved) M. Thomson | |||
Intended status: Standards Track Skype | Intended status: Standards Track Skype | |||
Expires: March 5, 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 | |||
Sep 2012 | Oct 2012 | |||
Specifying Civic Address Extensions in PIDF-LO | Specifying Civic Address Extensions in PIDF-LO | |||
draft-ietf-geopriv-local-civic-06 | draft-ietf-geopriv-local-civic-07 | |||
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 1, line 47 | skipping to change at page 1, line 47 | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
This Internet-Draft will expire on March 5, 2013. | This Internet-Draft will expire on April 4, 2013. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2012 IETF Trust and the persons identified as the | Copyright (c) 2012 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
(http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | publication of this document. Please review these documents | |||
carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
skipping to change at page 2, line 47 | skipping to change at page 2, line 47 | |||
7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 | 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 | |||
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 | 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 | |||
8.1. CAtype Registration for Extensions . . . . . . . . . . . . 15 | 8.1. CAtype Registration for Extensions . . . . . . . . . . . . 15 | |||
8.2. Changes to the CAtype Registry . . . . . . . . . . . . . . 15 | 8.2. Changes to the CAtype Registry . . . . . . . . . . . . . . 15 | |||
8.3. URN sub-namespace registration for | 8.3. URN sub-namespace registration for | |||
'urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr:ext' . . 15 | 'urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr:ext' . . 15 | |||
8.4. XML Schema Registration . . . . . . . . . . . . . . . . . 16 | 8.4. XML Schema Registration . . . . . . . . . . . . . . . . . 16 | |||
8.5. Registration Template . . . . . . . . . . . . . . . . . . 16 | 8.5. Registration Template . . . . . . . . . . . . . . . . . . 16 | |||
8.5.1. Registration of the schema defined in this document . 17 | 8.5.1. Registration of the schema defined in this document . 17 | |||
8.6. Registration Policy and Expert Guidance . . . . . . . . . 18 | 8.6. Registration Policy and Expert Guidance . . . . . . . . . 18 | |||
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18 | 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19 | |||
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 | 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 | |||
10.1. Normative References . . . . . . . . . . . . . . . . . . . 18 | 10.1. Normative References . . . . . . . . . . . . . . . . . . . 19 | |||
10.2. Informative References . . . . . . . . . . . . . . . . . . 19 | 10.2. Informative References . . . . . . . . . . . . . . . . . . 20 | |||
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20 | |||
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 | |||
skipping to change at page 14, line 43 | skipping to change at page 14, line 43 | |||
This document defines a formal way to extend the existing Geopriv | This document defines a formal way to extend the existing Geopriv | |||
civic address schema. No security threats are introduced by this | civic address schema. No security threats are introduced by this | |||
document. | document. | |||
Security threats applicable to the civic address formats are | Security threats applicable to the civic address formats are | |||
described in [RFC4776] (DHCP) and [RFC5139] (XML). | described in [RFC4776] (DHCP) and [RFC5139] (XML). | |||
8. IANA Considerations | 8. IANA Considerations | |||
This document alters the "CAtypes" registry established by [RFC4776]. | This document alters the "CAtypes" registry on the "Civic Address | |||
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. | |||
[[IANA/RFC-EDITOR: Please replace XX with the allocated CAtype]] | [[IANA/RFC-EDITOR: Please replace XX with the allocated CAtype]] | |||
8.2. Changes to the CAtype Registry | 8.2. Changes to the CAtype Registry | |||
No further registration of numeric CAtypes is permitted. | No further registration of numeric CAtypes in the Civic Address Types | |||
Registry is permitted. | ||||
The column called "NENA" is removed. | The column called "NENA" is removed. | |||
The column called "PIDF" is renamed to "Local Name". | The column called "PIDF" is renamed to "Local Name". | |||
New columns are added named "Namespace URI", "Contact", "Schema" and | New columns are added named "Namespace URI", "Contact", "Schema" and | |||
"Type". | "Type". | |||
New registrations use the registration template in Section 8.5. | New registrations use the registration template in Section 8.5. | |||
skipping to change at page 16, line 22 | skipping to change at page 16, line 38 | |||
URI: urn:ietf:params:xml:schema:pidf:geopriv10:civicAddr:ext | URI: urn:ietf:params:xml:schema:pidf:geopriv10:civicAddr:ext | |||
Registrant Contact: IETF, GEOPRIV working group, (geopriv@ietf.org), | Registrant Contact: IETF, GEOPRIV working group, (geopriv@ietf.org), | |||
James Winterbottom (james.Winterbottom@commscope.com). | James Winterbottom (james.Winterbottom@commscope.com). | |||
The XML for this schema can be found as the entirety of | The XML for this schema can be found as the entirety of | |||
Section 5.5 of this document. | Section 5.5 of this document. | |||
8.5. Registration Template | 8.5. Registration Template | |||
New registrations in the "CAtypes" registry require the following | New registrations in the Civic Address Types Registry require the | |||
information: | following information: | |||
CAtype: The assigned numeric CAtype. All new registrations use the | CAtype: The assigned numeric CAtype. All new registrations use the | |||
value XX. [[IANA/RFC-Editor: update XX] Existing registrations | value XX. [[IANA/RFC-Editor: update XX] Existing registrations | |||
use their assigned value. | use their assigned value. | |||
Namespace URI: A unique identifier for the XML namespace used for | Namespace URI: A unique identifier for the XML namespace used for | |||
the extension element. | the extension element. | |||
Local Name: The local name of an XML element that carries the civic | Local Name: The local name of an XML element that carries the civic | |||
address element. | address element. | |||
skipping to change at page 17, line 24 | skipping to change at page 17, line 43 | |||
(geopriv@ietf.org). | (geopriv@ietf.org). | |||
Specification: RFC4776 and RFC5139 | Specification: RFC4776 and RFC5139 | |||
Schema: urn:ietf:params:xml:schema:pidf:geopriv10:civicAddr | Schema: urn:ietf:params:xml:schema:pidf:geopriv10:civicAddr | |||
Type: A | Type: A | |||
8.5.1. Registration of the schema defined in this document | 8.5.1. Registration of the schema defined in this document | |||
This section registers the following four new CATypes per the scheme | This section registers the following four new CATypes in the Civic | |||
in Section 5.5 whose parameters are identical except for their Local | Address Types Registry per the scheme in Section 5.5 whose parameters | |||
Names and Descriptions:" | are identical except for their Local Names and Descriptions: | |||
CAtype: The assigned numeric CAtype value is XX. [[IANA/RFC-Editor: | CAtype: The assigned numeric CAtype value is XX. [[IANA/RFC-Editor: | |||
update XX] | update XX] | |||
Namespace URI: urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr:ext | Namespace URI: urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr:ext | |||
Local Name: PN | Local Name: PN | |||
Description: PN: Post number that is attributed to a lamp post or | Description: PN: Post number that is attributed to a lamp post or | |||
utility pole. | utility pole. | |||
End of changes. 10 change blocks. | ||||
16 lines changed or deleted | 18 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/ |