Correction: RFC 8841 on Session Description Protocol (SDP) Offer/Answer Procedures for Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) Transport
rfc-editor@rfc-editor.org Tue, 19 January 2021 01:39 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 2BD6B3A0F4A; Mon, 18 Jan 2021 17:39:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 OG6AvE1ihO4B; Mon, 18 Jan 2021 17:39:11 -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 294D63A1062; Mon, 18 Jan 2021 17:39:11 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id AF94AF407F7; Mon, 18 Jan 2021 17:38:55 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: Correction: RFC 8841 on Session Description Protocol (SDP) Offer/Answer Procedures for Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) Transport
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, mmusic@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210119013855.AF94AF407F7@rfc-editor.org>
Date: Mon, 18 Jan 2021 17:38:55 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/eze-c6SkvMQ_QfPP9h_N8ATvsk0>
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: Tue, 19 Jan 2021 01:39:19 -0000
[Year corrected to "2021" below.]
A new Request for Comments is now available in online RFC libraries.
RFC 8841
Title: Session Description Protocol (SDP) Offer/Answer
Procedures for Stream Control Transmission Protocol
(SCTP) over Datagram Transport Layer Security
(DTLS) Transport
Author: C. Holmberg,
R. Shpount,
S. Loreto,
G. Camarillo
Status: Standards Track
Stream: IETF
Date: January 2021
Mailbox: christer.holmberg@ericsson.com,
rshpount@turbobridge.com,
Salvatore.Loreto@ericsson.com,
gonzalo.camarillo@ericsson.com
Pages: 21
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mmusic-sctp-sdp-26.txt
URL: https://www.rfc-editor.org/info/rfc8841
DOI: 10.17487/RFC8841
The Stream Control Transmission Protocol (SCTP) is a transport
protocol used to establish associations between two endpoints. RFC
8261 specifies how SCTP can be used on top of the Datagram Transport
Layer Security (DTLS) protocol, which is referred to as
SCTP-over-DTLS.
This specification defines the following new Session Description
Protocol (SDP) protocol identifiers (proto values): "UDP/DTLS/SCTP"
and "TCP/DTLS/SCTP". This specification also specifies how to use the
new proto values with the SDP offer/answer mechanism for negotiating
SCTP-over-DTLS associations.
This document is a product of the Multiparty Multimedia Session Control 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