|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved
|
|
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=4119
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This document describes an object format for carrying geographical information on the Internet. This location object extends the Presence Information Data Format (PIDF), which was designed for communicating privacy-sensitive presence information and which has similar properties.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Standards track document approved December 2005
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Updated by RFC 5139
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
/
[1] Bradner, S., "Key words for use in RFCs to indicate requirement/
levels", BCP 14, RFC 2119, March 1997./
/
[2] Sugano, H., Fujimoto, S., Klyne, G., Bateman, A., Carr, W., and/
J. Peterson, "Presence Information Data Format (PIDF)", RFC/
3863, August 2004./
/
[3] Peterson, J., "Common Profile for Presence (CPP)", RFC 3859,/
October 2003./
/
[4] Mealling, M., "The IETF XML Registry", RFC 3688, BCP 81, January/
2004./
/
[5] Ramsdell, B., "Secure/Multipurpose Internet Mail Extensions/
(S/MIME) Version 3.1 Message Specification", RFC 3851, July/
2004./
/
[6] Housley, R., "Cryptographic Message Syntax (CMS)", RFC 3852,/
July 2004./
/
[7] Levinson, E., "Content-ID and Message-ID Uniform Resource/
Locators", RFC 2392, August 1998./
/
[8] Schaad, J., "Use of the Advanced Encryption Standard (AES)/
Encryption Algorithm in Cryptographic Message Syntax (CMS)", RFC/
3565, July 2003./
/
[9] Ramsdell, B., "Secure/Multipurpose Internet Mail Extensions/
(S/MIME) Version 3.1 Certificate Handling", RFC 3850, 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
|
|
