UNLIMITED FREE
ACCESS
TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

IETF RFC 6848

Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)

active, Most Current
Buy Now
Organization: IETF
Publication Date: 1 January 2013
Status: active
Page Count: 20
scope:

New fields are occasionally added to civic addresses. A backwardcompatible 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.

Document History

IETF RFC 6848
January 1, 2013
Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)
New fields are occasionally added to civic addresses. A backwardcompatible mechanism for adding civic address elements to the Geopriv civic address format is described. A formal mechanism for...

References

Advertisement