datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)
draft-ietf-geopriv-local-civic-10

RFC
Document Stream: IETF
Last updated: 2012-12-04
Replaces: draft-ietf-geopriv-prefix
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document (geopriv)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6848
IANA Action State: RFC-Ed-Ack 
On agenda of 2012-10-25 IESG telechat
Responsible AD: Robert Sparks
IESG Note: Alissa Cooper (acooper@cdt.org) is the document shepherd.
Send notices to: geopriv-chairs@tools.ietf.org, draft-ietf-geopriv-local-civic@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-geopriv-local-civic.

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. [STANDARDS-TRACK]

Authors:
James Winterbottom <james.winterbottom@commscope.com>
Martin Thomson <martin.thomson@gmail.com>
Richard Barnes <rbarnes@bbn.com>
Brian Rosen <br@brianrosen.net>
Robins George <robinsgv@gmail.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)