RFC 8844 on Unknown Key-Share Attacks on Uses of TLS with the Session Description Protocol (SDP)
rfc-editor@rfc-editor.org Mon, 18 January 2021 21:32 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 754353A0BEB; Mon, 18 Jan 2021 13:32:55 -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 wW2aZjwkLE01; Mon, 18 Jan 2021 13:32:54 -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 457993A0E47; Mon, 18 Jan 2021 13:32:40 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 02C78F4076A; Mon, 18 Jan 2021 13:32:25 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8844 on Unknown Key-Share Attacks on Uses of TLS with the Session Description Protocol (SDP)
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: <20210118213225.02C78F4076A@rfc-editor.org>
Date: Mon, 18 Jan 2021 13:32:25 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/E9k-0xOb3Px8m_37We4x4phFml0>
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: Mon, 18 Jan 2021 21:33:01 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8844
Title: Unknown Key-Share Attacks on Uses of TLS
with the Session Description Protocol (SDP)
Author: M. Thomson,
E. Rescorla
Status: Standards Track
Stream: IETF
Date: January 2020
Mailbox: mt@lowentropy.net,
ekr@rtfm.com
Pages: 17
Updates: RFC 8122
I-D Tag: draft-ietf-mmusic-sdp-uks-07.txt
URL: https://www.rfc-editor.org/info/rfc8844
DOI: 10.17487/RFC8844
This document describes unknown key-share attacks on the use of
Datagram Transport Layer Security for the Secure Real-Time Transport
Protocol (DTLS-SRTP). Similar attacks are described on the use of
DTLS-SRTP with the identity bindings used in Web Real-Time
Communications (WebRTC) and SIP identity. These attacks are
difficult to mount, but they cause a victim to be misled about the
identity of a communicating peer. This document defines mitigation
techniques that implementations of RFC 8122 are encouraged to deploy.
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