RFC 7879 on DTLS-SRTP Handling in SIP Back-to-Back User Agents
rfc-editor@rfc-editor.org Wed, 01 June 2016 00:42 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 D05F712D923; Tue, 31 May 2016 17:42:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Level:
X-Spam-Status: No, score=-108.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 3ox3dUvV5jyv; Tue, 31 May 2016 17:42:29 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 078D912D931; Tue, 31 May 2016 17:42:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id F3FCBB812A3; Tue, 31 May 2016 17:42:03 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7879 on DTLS-SRTP Handling in SIP Back-to-Back User Agents
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160601004203.F3FCBB812A3@rfc-editor.org>
Date: Tue, 31 May 2016 17:42:03 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/zuFv_jIStE4_JkO_sI7f60TVyRg>
Cc: straw@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 01 Jun 2016 00:42:42 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7879
Title: DTLS-SRTP Handling in SIP Back-to-Back
User Agents
Author: R. Ravindranath, T. Reddy,
G. Salgueiro, V. Pascual, P. Ravindran
Status: Standards Track
Stream: IETF
Date: May 2016
Mailbox: rmohanr@cisco.com,
tireddy@cisco.com,
gsalguei@cisco.com,
victor.pascual.avila@oracle.com,
partha@parthasarathi.co.in
Pages: 13
Characters: 29648
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-straw-b2bua-dtls-srtp-12.txt
URL: https://www.rfc-editor.org/info/rfc7879
DOI: http://dx.doi.org/10.17487/RFC7879
Session Initiation Protocol (SIP) Back-to-Back User Agents (B2BUAs)
exist on the signaling and media paths between the endpoints. This
document describes the behavior of B2BUAs when Secure Real-time
Transport (SRTP) security context is set up with the Datagram
Transport Layer Security (DTLS) protocol.
This document is a product of the Sip Traversal Required for Applications to Work 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