|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 6083 (2011)
|
|
Title:
|
Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)
|
|
|
2.
|
Status of approval:
|
|
|
Standards track RFC (Proposed Standard) approved January 2011.
|
|
3.
|
Justification for the specific reference:
|
|
|
To allow H.245 to signal the support of the CLUE protocol and to establish a CLUE over WebRTC data channel which in turn uses SCTP / DTLS.
|
|
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/?draft=&rfc=6083&submit=rfc&doctitle=&group=&holder=&iprtitle=&patent=
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since January 2011. Updated by RFC 8996. Errata exist.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
It has been in use since January 2011. It is used by WebRTC for data channel transport. Updated by RFC 8996. Errata exist.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
N/A
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[RFC3758] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P. Conrad, "Stream Control Transmission Protocol (SCTP) Partial Reliability Extension", RFC 3758, May 2004./
[RFC4347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer Security", RFC 4347, April 2006./
[RFC4895] Tuexen, M., Stewart, R., Lei, P., and E. Rescorla, "Authenticated Chunks for the Stream Control Transmission Protocol (SCTP)", RFC 4895, August 2007./
[RFC4960] Stewart, R., "Stream Control Transmission Protocol", RFC 4960, September 2007./
[RFC5705] Rescorla, E., "Keying Material Exporters for Transport Layer Security (TLS)", RFC 5705, March 2010./
/
Informative References/
/
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7, RFC 793, September 1981./
[RFC3436] Jungmaier, A., Rescorla, E., and M. Tuexen, "Transport Layer Security over Stream Control Transmission Protocol", RFC 3436, December 2002./
[RFC5061] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M. Kozuka, "Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration", RFC 5061, September 2007.
|
|
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.
|
|
