|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Standards Track RFC approved March 2012.
|
|
3.
|
Justification for the specific reference:
|
|
|
ICE is basically in scope of H.248.50 and this RFC defines the TCP ICE extension on top of UDP.
|
|
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=6544
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Standards track RFC approved March 2012. Errata exist.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Standards track RFC approved March 2012.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[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./
/
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model/
with Session Description Protocol (SDP)", RFC 3264,/
June 2002./
/
[RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K./
Norrman, "The Secure Real-time Transport Protocol/
(SRTP)", RFC 3711, March 2004./
/
[RFC4145] Yon, D. and G. Camarillo, "TCP-Based Media Transport in/
the Session Description Protocol (SDP)", RFC 4145,/
September 2005./
/
[RFC4571] Lazzaro, J., "Framing Real-time Transport Protocol (RTP)/
and RTP Control Protocol (RTCP) Packets over Connection-/
Oriented Transport", RFC 4571, July 2006./
/
[RFC4572] Lennox, J., "Connection-Oriented Media Transport over the/
Transport Layer Security (TLS) Protocol in the Session/
Description Protocol (SDP)", RFC 4572, July 2006./
/
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an/
IANA Considerations Section in RFCs", BCP 26, RFC 5226,/
May 2008./
/
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax/
Specifications: ABNF", STD 68, RFC 5234, January 2008./
/
[RFC5245] Rosenberg, J., "Interactive Connectivity Establishment/
(ICE): A Protocol for Network Address Translator (NAT)/
Traversal for Offer/Answer Protocols", RFC 5245,/
April 2010./
/
[RFC5389] Rosenberg, J., Mahy, R., Matthews, P., and D. Wing,/
"Session Traversal Utilities for NAT (STUN)", RFC 5389,/
October 2008./
/
[RFC5764] McGrew, D. and E. Rescorla, "Datagram Transport Layer/
Security (DTLS) Extension to Establish Keys for the/
Secure Real-time Transport Protocol (SRTP)", RFC 5764,/
May 2010./
/
[RFC5766] Mahy, R., Matthews, P., and J. Rosenberg, "Traversal/
Using Relays around NAT (TURN): Relay Extensions to/
Session Traversal Utilities for NAT (STUN)", RFC 5766,/
April 2010.
|
|
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
|
|
