RFC 8540 on Stream Control Transmission Protocol: Errata and Issues in RFC 4960
rfc-editor@rfc-editor.org Wed, 20 February 2019 06:58 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A6CB1310D5; Tue, 19 Feb 2019 22:58:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hI_ijsFGHtR7; Tue, 19 Feb 2019 22:58:08 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A632B1310A9; Tue, 19 Feb 2019 22:58:07 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id A4660B804E6; Tue, 19 Feb 2019 22:57:52 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8540 on Stream Control Transmission Protocol: Errata and Issues in RFC 4960
X-PHP-Originating-Script: 1005:ams_util_lib.php
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: <20190220065752.A4660B804E6@rfc-editor.org>
Date: Tue, 19 Feb 2019 22:57:52 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/-N-XMFWmiJTelzp0UOXggzLuyXE>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Feb 2019 06:58:14 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8540
Title: Stream Control Transmission Protocol: Errata
and Issues in RFC 4960
Author: R. Stewart,
M. Tuexen,
M. Proshin
Status: Informational
Stream: IETF
Date: February 2019
Mailbox: randall@lakerest.net,
tuexen@fh-muenster.de,
mproshin@tieto.mera.ru
Pages: 94
Characters: 166198
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-tsvwg-rfc4960-errata-08.txt
URL: https://www.rfc-editor.org/info/rfc8540
DOI: 10.17487/RFC8540
This document is a compilation of issues found since the publication
of RFC 4960 in September 2007, based on experience with implementing,
testing, and using the Stream Control Transmission Protocol (SCTP)
along with the suggested fixes. This document provides deltas to RFC
4960 and is organized in a time-ordered way. The issues are listed
in the order in which they were brought up. Because some text is
changed several times, the last delta in the text is the one that
should be applied. In addition to the deltas, a description of each
problem and the details of the solution for each are also provided.
This document is a product of the Transport Area Working Group Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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