RFC 8870 on Encrypted Key Transport for DTLS and Secure RTP

rfc-editor@rfc-editor.org Tue, 19 January 2021 00:47 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 7657E3A11BC; Mon, 18 Jan 2021 16:47:31 -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 k4Ks8CNTPCIX; Mon, 18 Jan 2021 16:47:29 -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 015F73A10B0; Mon, 18 Jan 2021 16:47:16 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id A7118F407DA; Mon, 18 Jan 2021 16:47:01 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg4NzAgb24gRW5jcnlwdGVkIEtleSBUcmFuc3BvcnQgZm9yIERUTFMgYW5kIFNlY3VyZSBSVFA=?=
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, perc@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210119004701.A7118F407DA@rfc-editor.org>
Date: Mon, 18 Jan 2021 16:47:01 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/RqJly7dj4al-W-aR8JneWhB4jvA>
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 00:47:38 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8870

        Title:      Encrypted Key Transport for DTLS and Secure RTP 
        Author:     C. Jennings,
                    J. Mattsson,
                    D. McGrew,
                    D. Wing,
                    F. Andreasen
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    fluffy@iii.ca,
                    john.mattsson@ericsson.com,
                    mcgrew@cisco.com,
                    dwing-ietf@fuggles.com,
                    fandreas@cisco.com
        Pages:      22
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-perc-srtp-ekt-diet-13.txt

        URL:        https://www.rfc-editor.org/info/rfc8870

        DOI:        10.17487/RFC8870

Encrypted Key Transport (EKT) is an extension to DTLS (Datagram
Transport Layer Security) and the Secure Real-time Transport Protocol
(SRTP) that provides for the secure transport of SRTP master keys,
rollover counters, and other information within SRTP. This facility
enables SRTP for decentralized conferences by distributing a common
key to all of the conference endpoints.

This document is a product of the Privacy Enhanced RTP Conferencing 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