1. Summary for draft-ietf-tsvwg-rfc4960-bis
The document shepherd is Gorry Fairhurst.
The responsible Area Director is Martin Duke <martin.h.duke@gmail.com>.
This document specifies the SCTP transport protocol. The intended status listed
in the document is "Proposed Standard”.
This will obsolete RFC 4960, if approved. It describes the Stream Control
Transmission Protocol (SCTP). SCTP was designed to transport Public Switched
Telephone Network (PSTN) signaling messages over IP networks. The transport is
also suitable for a range other applications. The design of SCTP includes
appropriate congestion avoidance behavior and resistance to flooding and
masquerade attacks.
2. Review and Consensus
WG Summary:
The TSVWG working group has worked on this document since 2018, and SCTP
contributors have reviewed the specification during that time. In particular,
many SCTP implementers have provided detailed comments based on operational
experience, that informed RFC8540 which details the core changes in the spec.
The document has been relatively stable in the latest versions. All open
issues from WGLC has been resolved. The shepherd believes that this document
(rev 15) has the support of the TSVWG working group.
The basis of the document was set out in RFC 8540, changes also include
editorial improvements. All currently known errata to RFC 4960 and related RFCs
have been considered in this "bis" document.When published, the document will
resolve known issues in the standards-track specification, and improves the
quality of the specification of SCTP. It introduces a limited set of
modifications to the currently deployed protocol, these changes with respect to
RFC4960 are noted in the document.
3. Intellectual Property
Each editor has stated that his direct, personal knowledge of any IPR related
to this document has already been disclosed, in conformance with BCPs 78 and
79. Since RFC4960 does not change the STCP protocol, relevant IPR would have
to be disclosed already for the existing RFCs.
4. Other Points
SCTP is implemented in endpoints either in the operating system or a user
stack. Running code for SCTP exists in several TCP/IP stacks. All main STCP
implementations are expected to comply with 4960.bis. The document is expected
to fulfill the requirements of an "Internet Standard" according to RFC 2026 and
RFC 7127. The intention of this update is therefore, in part, to ready the
SCTP specification for progression along the standards track.
The document has been reviewed several time by the work group and in a number
of specific detailed reviews (the last during WGLC). This included several
complete detailed reviews by the document shepherd. The use of normative
language was revised to clarify the meaning and align with usage in other
recent TSVWG specifications. There is no specific need for extra expert review
(e.g. AAA, DNS, DHCP, XML, or internationalization).
The publication of this document will change the status of existing RFCs.
These are all listed on the title page header, in the abstract, and in the
introduction.
The document contains a disclaimer for pre-RFC5378 work. While the RFC4960
authors of the source material are willing to grant the BCP78 rights to the
IETF Trust, the document also revises and obsolete older RFCs, incorporating
significant amounts of text from those older RFCs. The disclaimer is therefore
currently necessary.
IANA
The IANA Considerations section contains updated text in relation to SCTP
registries. It also documents how IANA should update current registries to
refer to the new specification.
References
There is a Non-RFC normative reference to v.42: 'ITU.V42.1994’, as in REF 1
of RFC4960.
An informational historic reference to RFC 2960 is included in the
acknowledgment to describe the history of the spec.