RFC 8643 on An Opportunistic Approach for Secure Real-time Transport Protocol (OSRTP)

rfc-editor@rfc-editor.org Fri, 09 August 2019 23: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 []) by ietfa.amsl.com (Postfix) with ESMTP id 0B87D120251; Fri, 9 Aug 2019 16:39:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id ow-HjbRRuqhP; Fri, 9 Aug 2019 16:39:47 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EDDC12023C; Fri, 9 Aug 2019 16:39:42 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9992EB81F39; Fri, 9 Aug 2019 16:39:15 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg2NDMgb24gQW4gT3Bwb3J0dW5pc3RpYyBBcHByb2FjaCBmb3IgU2VjdXJlIFJlYWwtdGltZSBUcmFuc3BvcnQgUHJvdG9jb2wgKE9TUlRQKQ==?=
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, sipbrandy@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20190809233915.9992EB81F39@rfc-editor.org>
Date: Fri, 9 Aug 2019 16:39:15 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/CnzseU_-wQ1yL--QLocO39OyAW0>
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: Fri, 09 Aug 2019 23:39:57 -0000

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

        RFC 8643

        Title:      An Opportunistic Approach for Secure 
                    Real-time Transport Protocol (OSRTP) 
        Author:     A. Johnston, 
                    B. Aboba,
                    A. Hutton,
                    R. Jesske,
                    T. Stach
        Status:     Informational
        Stream:     IETF
        Date:       August 2019
        Mailbox:    alan.b.johnston@gmail.com, 
        Pages:      8
        Characters: 18189
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sipbrandy-osrtp-10.txt

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

        DOI:        10.17487/RFC8643

Opportunistic Secure Real-time Transport Protocol (OSRTP) is an
implementation of the Opportunistic Security mechanism, as defined in
RFC 7435, applied to the Real-time Transport Protocol (RTP).  OSRTP
allows encrypted media to be used in environments where support for
encryption is not known in advance and is not required.  OSRTP does
not require Session Description Protocol (SDP) extensions or features
and is fully backwards compatible with existing implementations using
encrypted and authenticated media and implementations that do not
encrypt or authenticate media packets.  OSRTP is not specific to any
key management technique for Secure RTP (SRTP).  OSRTP is a
transitional approach useful for migrating existing deployments of
real-time communications to a fully encrypted and authenticated

This document is a product of the SIP Best-practice Recommendations Against Network Dangers to privacY 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

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