Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO), January 2013
- Canonical URL:
- File formats:
- PROPOSED STANDARD
- RFC 4776, RFC 5222
- J. Winterbottom
- geopriv (rai)
Discuss this RFC: Send questions or comments to firstname.lastname@example.org
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]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 4844.