|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
Rec.Q.OIP/OIR refers to IETF defined A Privacy Mechanism for the Session Initiation Protocol (SIP) specified in (1).
|
|
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=3323
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Proposed Standard
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Proposed Standard
|
|
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] Bradner, S., "Key words for use in RFCs to indicate requirement/
levels", BCP 14, RFC 2119, March 1997./
/
[3] Eastlake, D. and A. Panitz, "Reserved Top Level DNS Names", RFC/
2606, June 1999./
/
Informative References/
/
[4] Baugher, M., McGrew, D., Oran, D., Blom, R., Carrara, E.,/
Naslund, M. and K. Normann, "The Secure Real Time Transport/
Protocol", Work in Progress./
/
[5] Handley, M. and V. Jacobson, "SDP: Session Description/
Protocol", RFC 2327, April 1998./
/
[6] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson,/
"RTP: A Transport Protocol for Real-Time Applications", RFC/
1889, January 1996./
/
[7] Lennox, J. and H. Schulzrinne, "CPL: A Language for User Control/
of Internet Telephony Services", Work in Progress/
/
[8] Srisuresh, P., Kuthan, J., Rosenberg, J., Molitor, A. and A./
Rayhan, "Middlebox communication architecture and framework",/
RFC 3303, August 2002./
|
|
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
|
|
