[tsvwg] RFC 9260 on Stream Control Transmission Protocol
rfc-editor@rfc-editor.org Sat, 04 June 2022 17:38 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE7CFC15AAC4; Sat, 4 Jun 2022 10:38:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.655
X-Spam-Level:
X-Spam-Status: No, score=-1.655 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lp_SnFYToQhP; Sat, 4 Jun 2022 10:38:33 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAD26C15AAC7; Sat, 4 Jun 2022 10:38:33 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 506E285CD0; Sat, 4 Jun 2022 10:38:33 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, tsvwg@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20220604173833.506E285CD0@rfcpa.amsl.com>
Date: Sat, 04 Jun 2022 10:38:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/hzwKqZ8ayvc4nJeHlugTNOIsLAA>
Subject: [tsvwg] RFC 9260 on Stream Control Transmission Protocol
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Jun 2022 17:38:38 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9260
Title: Stream Control Transmission Protocol
Author: R. Stewart,
M. Tüxen,
K. Nielsen
Status: Standards Track
Stream: IETF
Date: June 2022
Mailbox: randall@lakerest.net,
tuexen@fh-muenster.de,
kee@kamstrup.com
Pages: 133
Obsoletes: RFC 4460, RFC 4960, RFC 6096, RFC 7053, RFC 8540
I-D Tag: draft-ietf-tsvwg-rfc4960-bis-19.txt
URL: https://www.rfc-editor.org/info/rfc9260
DOI: 10.17487/RFC9260
This document describes the Stream Control Transmission Protocol
(SCTP) and obsoletes RFC 4960. It incorporates the specification of
the chunk flags registry from RFC 6096 and the specification of the I
bit of DATA chunks from RFC 7053. Therefore, RFCs 6096 and 7053 are
also obsoleted by this document. In addition, RFCs 4460 and 8540,
which describe errata for SCTP, are obsoleted by this document.
SCTP was originally designed to transport Public Switched Telephone
Network (PSTN) signaling messages over IP networks. It is also suited
to be used for other applications, for example, WebRTC.
SCTP is a reliable transport protocol operating on top of a
connectionless packet network, such as IP. It offers the following
services to its users:
The design of SCTP includes appropriate congestion avoidance behavior
and resistance to flooding and masquerade attacks.
This document is a product of the Transport Area Working Group Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC