|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 5491 (2009)
|
|
Title:
|
GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations
|
|
|
2.
|
Status of approval:
|
|
|
All are approved IETF documents
|
|
3.
|
Justification for the specific reference:
|
|
|
H.460.geo transports geographic information using data structured defined in the IETF so that both SIP and H.323 transport the same data structures, thus lending to interoperability between the two protocols.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=5491
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC was approved in March 2009. Updates RFC 4119.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Standards track document approved March 2009
.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
This document clarifies the usage of RFC 4119 and 5139.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
/
[GeoShape] Thomson, M. and C. Reed, "GML 3.1.1 PIDF-LO Shape/
Application Schema for use by the Internet Engineering/
Task Force (IETF)", Candidate OpenGIS Implementation/
Specification 06-142r1, Version: 1.0, April 2007./
/
[OGC-GML3.1.1]/
Portele, C., Cox, S., Daisy, P., Lake, R., and A./
Whiteside, "Geography Markup Language (GML) 3.1.1",/
OGC 03-105r1, July 2003./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object/
Format", RFC 4119, December 2005./
/
[RFC4479] Rosenberg, J., "A Data Model for Presence", RFC 4479,/
July 2006./
/
[RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location/
Format for Presence Information Data Format Location/
Object (PIDF-LO)", RFC 5139, February 2008./
/
[W3C.REC-xmlschema-2-20041028]/
Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes/
Second Edition", World Wide Web Consortium/
Recommendation REC-xmlschema-2-20041028, October 2004,/
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028./
/
Informative References/
/
[3GPP.23.032]/
3rd Generation Partnership Project, "Universal/
Geographical Area Description (GAD)", 3GPP TS 23.032/
V6.0.0, January 2005,/
http://www.3gpp.org/ftp/Specs/html-info/23032.htm./
/
[CRS-URN] Whiteside, A., "GML 3.1.1 Common CRSs Profile", OGC 03-/
105r1, November 2005./
/
[RFC3693] Cuellar, J., Morris, J., Mulligan, D., Peterson, J., and/
J. Polk, "Geopriv Requirements", RFC 3693, February 2004./
/
[RFC4776] Schulzrinne, H., "Dynamic Host Configuration Protocol/
(DHCPv4 and DHCPv6) Option for Civic Addresses/
Configuration Information", RFC 4776, November 2006./
/
[WGS84] US National Imagery and Mapping Agency, "Department of/
Defense (DoD) World Geodetic System 1984 (WGS 84), Third/
Edition", NIMA TR8350.2, January 2000./
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
