[Sipbrandy] BCP 228, RFC 8862 on Best Practices for Securing RTP Media Signaled with SIP
rfc-editor@rfc-editor.org Tue, 19 January 2021 00:47 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sipbrandy@ietfa.amsl.com
Delivered-To: sipbrandy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79B5C3A117F; Mon, 18 Jan 2021 16:47: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 pc6cOSSnRwdd; Mon, 18 Jan 2021 16:47:13 -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 D82D63A0E1C; Mon, 18 Jan 2021 16:47:03 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 7AB6BF407C9; Mon, 18 Jan 2021 16:46:48 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20210119004648.7AB6BF407C9@rfc-editor.org>
Date: Mon, 18 Jan 2021 16:46:48 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipbrandy/XqQuCnEzi8hlQUo50NtRG3quG-M>
Subject: [Sipbrandy] BCP 228, RFC 8862 on Best Practices for Securing RTP Media Signaled with SIP
X-BeenThere: sipbrandy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIPBRANDY working group discussion list <sipbrandy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipbrandy>, <mailto:sipbrandy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipbrandy/>
List-Post: <mailto:sipbrandy@ietf.org>
List-Help: <mailto:sipbrandy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipbrandy>, <mailto:sipbrandy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jan 2021 00:47:22 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 228
RFC 8862
Title: Best Practices for Securing RTP Media
Signaled with SIP
Author: J. Peterson,
R. Barnes,
R. Housley
Status: Best Current Practice
Stream: IETF
Date: January 2021
Mailbox: jon.peterson@team.neustar,
rlb@ipv.sx,
housley@vigilsec.com
Pages: 12
See Also: BCP 228
I-D Tag: draft-ietf-sipbrandy-rtpsec-08.txt
URL: https://www.rfc-editor.org/info/rfc8862
DOI: 10.17487/RFC8862
Although the Session Initiation Protocol (SIP) includes a suite of
security services that has been expanded by numerous specifications
over the years, there is no single place that explains how to use SIP
to establish confidential media sessions. Additionally, existing
mechanisms have some feature gaps that need to be identified and
resolved in order for them to address the pervasive monitoring threat
model. This specification describes best practices for negotiating
confidential media with SIP, including a comprehensive protection
solution that binds the media layer to SIP layer identities.
This document is a product of the SIP Best-practice Recommendations Against Network Dangers to privacY Working Group of the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. 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