Specifying Civic Address Extensions in the Presence Information Data Format Location Object
RFC 6848, “Specifying Civic Address Extensions in the Presence Information Data Format Location Object”, is a Proposed Standard document published in January 2013 by J. Winterbottom, M. Thomson, R. Barnes, B. Rosen, R. George. It updates RFC 4776, RFC 5222. The canonical text is published by the RFC Editor.
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6848 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6847 Fibre Channel over Ethernet over Transparent Interconnection of Lots of Links
- RFC 6849 An Extension to the Session Description Protocol and Real-time Transport Protocol for Media Loopback
- RFC 6846 RObust Header Compression : A Profile for TCP/IP
- RFC 6850 Definitions of Managed Objects for Routing Bridges
- RFC 6845 OSPF Hybrid Broadcast and Point-to-Multipoint Interface Type
- RFC 6851 Internet Message Access Protocol - MOVE Extension
- RFC 6844 DNS Certification Authority Authorization Resource Record
- RFC 6852 Affirmation of the Modern Paradigm for Standards