Correction: RFC 8842 on Session Description Protocol (SDP) Offer/Answer Considerations for Datagram Transport Layer Security (DTLS) and Transport Layer Security (TLS)
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 92A1F3A1057; Mon, 18 Jan 2021 17:39:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 2ZqbZ_h27R5W; Mon, 18 Jan 2021 17:39:14 -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 128793A105A; Mon, 18 Jan 2021 17:39:14 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id A808FF407FE; Mon, 18 Jan 2021 17:38:58 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: Correction: RFC 8842 on Session Description Protocol (SDP) Offer/Answer Considerations for Datagram Transport Layer Security (DTLS) and Transport Layer Security (TLS)
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: <20210119013858.A808FF407FE@rfc-editor.org>
Date: Mon, 18 Jan 2021 17:38:58 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/WQCLkjAmjQI79JxBrC21pvFMyL4>
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:22 -0000
[Year corrected to "2021" below.]
A new Request for Comments is now available in online RFC libraries.
RFC 8842
Title: Session Description Protocol (SDP) Offer/Answer
Considerations for Datagram Transport Layer Security
(DTLS) and Transport Layer Security (TLS)
Author: C. Holmberg,
R. Shpount
Status: Standards Track
Stream: IETF
Date: January 2021
Mailbox: christer.holmberg@ericsson.com,
rshpount@turbobridge.com
Pages: 19
Updates: RFC 5763, RFC 7345
I-D Tag: draft-ietf-mmusic-dtls-sdp-32.txt
URL: https://www.rfc-editor.org/info/rfc8842
DOI: 10.17487/RFC8842
This document defines the Session Description Protocol (SDP)
offer/answer procedures for negotiating and establishing a Datagram
Transport Layer Security (DTLS) association. The document also
defines the criteria for when a new DTLS association must be
established. The document updates RFCs 5763 and 7345 by replacing
common SDP offer/answer procedures with a reference to this
specification.
This document defines a new SDP media-level attribute, "tls-id".
This document also defines how the "tls-id" attribute can be used for
negotiating and establishing a Transport Layer Security (TLS)
connection, in conjunction with the procedures in RFCs 4145 and 8122.
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