Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 4119

Updated by:

RFC 7459

Authors:

J. Winterbottom
M. Thomson
H. Tschofenig

Stream:

IETF

Source:

geopriv (rai)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5491

Discuss this RFC: Send questions or comments to the mailing listgeopriv@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5491

Abstract

The Presence Information Data Format Location Object (PIDF-LO)specification provides a flexible and versatile means to representlocation information. There are, however, circumstances that arisewhen information needs to be constrained in how it is represented.In these circumstances, the range of options that need to beimplemented are reduced. There is growing interest in being able touse location information contained in a PIDF-LO for routingapplications. To allow successful interoperability betweenapplications, location information needs to be normative and moretightly constrained than is currently specified in RFC 4119(PIDF-LO). This document makes recommendations on how to constrain,represent, and interpret locations in a PIDF-LO. It furtherrecommends a subset of Geography Markup Language (GML) 3.1.1 that ismandatory to implement by applications involved in location-basedrouting. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.