|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 5139 (2008)
|
|
Title:
|
Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)
|
|
|
2.
|
Status of approval:
|
|
|
Standards Track RFC
|
|
3.
|
Justification for the specific reference:
|
|
|
H.460 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=5139
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This document has been an IETF RFC since 2008 and updates RFC 4119. No errata.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Standards Track RFC approved February 2008.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
This document revised RFC 4119.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
8.1. Normative References/
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[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./
/
[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object/
Format", RFC 4119, December 2005./
/
[RFC4589] Schulzrinne, H. and H. Tschofenig, "Location Types/
Registry", RFC 4589, July 2006./
/
[RFC4646] Phillips, A. and M. Davis, "Tags for Identifying/
Languages", BCP 47, RFC 4646, September 2006./
/
[RFC4776] Schulzrinne, H., "Dynamic Host Configuration Protocol/
(DHCPv4 and DHCPv6) Option for Civic Addresses/
Configuration Information", RFC 4776, November 2006./
/
[ISO.3166-1] International Organization for Standardization, "Codes/
for the representation of names of countries and their/
subdivisions - Part 1: Country codes", ISO Standard/
3166- 1:1997, 1997./
/
[ISO.3166-2] International Organization for Standardization, "Codes/
for the representation of names of countries and their/
subdivisions - Part 2: Country subdivision code",/
ISO Standard 3166-2:1998, 1998./
/
8.2. Informative References/
/
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,/
January 2004./
/
[UPU-S42] Universal Postal Union (UPU), "International Postal/
Address Components and Templates", UPS SB42-4,/
July 2004.
|
|
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
|
|
