|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 5061 (2007)
|
|
Title:
|
Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration
|
|
|
2.
|
Status of approval:
|
|
|
RFC - Proposed Standard. Approved September 2007
|
|
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/?option=rfc_search&rfc_search=5061
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since September 2007. No errata exists.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
It is a standards-track document and is currently in the "Proposed Standard" state.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
IETF RFC 5061 is one of a suite of document related to the Stream Control Transmission Protocol (SCTP) [RFC 4960].
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC1122] Braden, R., "Requirements for Internet Hosts - Communication Layers", STD 3, RFC 1122, October 1989./
[RFC1982] Elz, R. and R. Bush, "Serial Number Arithmetic", RFC 1982, August 1996./
[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./
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460, December 1998./
[RFC4960] Stewart, R., Ed., "Stream Control Transmission Protocol", RFC 4960, September 2007./
[RFC4895] Tuexen, M., Stewart, R., Lei, P., and E. Rescorla, "Authenticated Chunks for the Stream Control Transmission Protocol (SCTP)", RFC 4895, August 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):
|
|
|
None
|
