|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3325 (2002)
|
|
Title:
|
Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
normative reference
|
|
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=3325
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Informational
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Informational
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item 8.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
/
[1] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,/
Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP:/
Session Initiation Protocol", RFC 3261, June 2002./
/
[2] Peterson, J., "A Privacy Mechanism for the Session Initiation/
Protocol (SIP)", RFC 3323, November 2002./
/
[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", BCP 14, RFC 2119, March 1997./
/
[4] Crocker, D. and P. Overell, "Augmented BNF for Syntax/
Specifications: ABNF", RFC 2234, November 1997./
/
Informational References/
/
[5] Watson, M., "Short Term Requirements for Network Asserted/
Identity", RFC 3324, November 2002./
/
[6] Andreasen, F., "SIP Extensions for Network-Asserted Caller/
Identity and Privacy within Trusted Networks", Work in Progress./
/
[7] Peterson, J., "Enhancements for Authenticated Identity Management/
in the Session Initiation Protocol (SIP)", Work in Progress./
|
|
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
|
|
