|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 4412 (2006)
|
|
Title:
|
Communications Resource Priority for the Session Initiation Protocol (SIP).
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Recommendation Y.NGN-ET-Tech refers to IETF RFC 4412 for the Resource-Priority and the Accept-Resource-Priority header fields.
|
|
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=4412
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of IETF RFC 4412 is "Proposed Standard". Current status of these documents can be found at http://www.ietf.org/iesg/1rfc_index.txt.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of IETF RFC 4412 is "Proposed Standard". Current status of these documents can be found at http://www.ietf.org/iesg/1rfc_index.txt.
|
|
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/
/
[I.255.3] International Telecommunications Union, "Integrated/
Services Digital Network (ISDN) - General Structure and/
Service Capabilities - Multi-Level Precedence and/
Preemption", Recommendation I.255.3, July 1990./
/
[Q.735.3] International Telecommunications Union, "Stage 3/
description for community of interest supplementary/
services using Signalling System No. 7: Multi-level/
precedence and preemption", Recommendation Q.735.3,/
March 1993./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an/
IANA Considerations Section in RFCs", BCP 26, RFC 2434,/
October 1998./
/
[RFC3261] 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./
/
[RFC3262] Rosenberg, J. and H. Schulzrinne, "Reliability of/
Provisional Responses in Session Initiation Protocol/
(SIP)", RFC 3262, June 2002./
/
[RFC3265] Roach, A.B., "Session Initiation Protocol (SIP)-Specific/
Event Notification", RFC 3265, June 2002./
/
[RFC3311] Rosenberg, J., "The Session Initiation Protocol (SIP)/
UPDATE Method", RFC 3311, October 2002./
/
[RFC3420] Sparks, R., "Internet Media Type message/sipfrag", RFC/
3420, November 2002./
/
[RFC3428] Campbell, B., Rosenberg, J., Schulzrinne, H., Huitema, C.,/
and D. Gurle, "Session Initiation Protocol (SIP) Extension/
for Instant Messaging", RFC 3428, December 2002./
/
[RFC4411] Polk, J., "Extending the Session Initiation Protocol (SIP)/
Reason Header for Preemption Events", RFC 4411, February/
2006./
/
Informative References/
/
[RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S.,/
Leach, P., Luotonen, A., and L. Stewart, "HTTP/
Authentication: Basic and Digest Access Authentication",/
RFC 2617, June 1999./
/
[RFC2976] Donovan, S., "The SIP INFO Method", RFC 2976, October/
2000./
/
[RFC3323] Peterson, J., "A Privacy Mechanism for the Session/
Initiation Protocol (SIP)", RFC 3323, November 2002./
/
[RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private/
Extensions to the Session Initiation Protocol (SIP) for/
Asserted Identity within Trusted Networks", RFC 3325,/
November 2002./
/
[RFC3427] Mankin, A., Bradner, S., Mahy, R., Willis, D., Ott, J.,/
and B. Rosen, "Change Process for the Session Initiation/
Protocol (SIP)", BCP 67, RFC 3427, December 2002./
/
[RFC3487] Schulzrinne, H., "Requirements for Resource Priority/
Mechanisms for the Session Initiation Protocol (SIP)", RFC/
3487, February 2003./
/
[RFC3515] Sparks, R., "The Session Initiation Protocol (SIP) Refer/
Method", RFC 3515, April 2003./
/
[RFC3546] Blake-Wilson, S., Nystrom, M., Hopwood, D., Mikkelsen, J.,/
and T. Wright, "Transport Layer Security (TLS)/
Extensions", RFC 3546, June 2003./
/
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V./
Jacobson, "RTP: A Transport Protocol for Real-Time/
Applications", STD 64, RFC 3550, July 2003./
/
[RFC3665] Johnston, A., Donovan, S., Sparks, R., Cunningham, C., and/
K. Summers, "Session Initiation Protocol (SIP) Basic Call/
Flow Examples", BCP 75, RFC 3665, December 2003./
/
[RFC3851] Ramsdell, B., "Secure/Multipurpose Internet Mail/
Extensions (S/MIME) Version 3.1 Message Specification",/
RFC 3851, July 2004./
/
[RFC3893] Peterson, J., "Session Initiation Protocol (SIP)/
Authenticated Identity Body (AIB) Format", RFC 3893,/
September 2004./
/
[RFC3903] Niemi, A., "Session Initiation Protocol (SIP) Extension/
for Event State Publication", RFC 3903, October 2004. for/
Event State Publication", RFC 3903, October 2004./
/
[TRAIT] Peterson, J., Polk, J., Sicker, D., and H. Tschofenig,/
"Trait-based Authorization Requirements for the Session/
Initiation Protocol (SIP)", Work in Progress,/
February 2005./
|
|
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):
|
|
|
References should always be made to RFC numbers (and not by other designations such as STD, BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.
|
|
