Document Action: 'Example call flows using Session Initiation Protocol (SIP) security mechanisms' to Informational RFC (draft-ietf-sipcore-sec-flows-09.txt)
The IESG <iesg-secretary@ietf.org> Mon, 14 February 2011 16:44 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EFF5A3A699E; Mon, 14 Feb 2011 08:44:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XAerTERRbbHT; Mon, 14 Feb 2011 08:44:15 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7EC383A6D68; Mon, 14 Feb 2011 08:44:14 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: 'Example call flows using Session Initiation Protocol (SIP) security mechanisms' to Informational RFC (draft-ietf-sipcore-sec-flows-09.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110214164414.20089.26199.idtracker@localhost>
Date: Mon, 14 Feb 2011 08:44:14 -0800
Cc: sipcore chair <sipcore-chairs@tools.ietf.org>, Internet Architecture Board <iab@iab.org>, sipcore mailing list <sipcore@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 14 Feb 2011 16:44:16 -0000
The IESG has approved the following document: - 'Example call flows using Session Initiation Protocol (SIP) security mechanisms' (draft-ietf-sipcore-sec-flows-09.txt) as an Informational RFC This document is the product of the Session Initiation Protocol Core Working Group. The IESG contact persons are Gonzalo Camarillo and Robert Sparks. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-sipcore-sec-flows/ Technical Summary This document shows example call flows demonstrating the use of Transport Layer Security (TLS), and Secure/Multipurpose Internet Mail Extensions (S/MIME) in Session Initiation Protocol (SIP). It also provides information that helps implementers build interoperable SIP software. Working Group Summary This work traces its roots back to 2003, when it was first introduced into the SIP working group. For much of its lifetime, it existed quietly alongside the document "Certificate Management Service for The Session Initiation Protocol," which is currently in the RFC Editors' queue. After moving into SIPCORE, repeated requests by the chairs for review yielded a small number of in-depth reviews. Document Quality According to one of the document authors, he has received "many emails from implementors that use this draft." Using this as our data point, the document's utility as a sanity check for the security aspects of SIP implementations would seem to be very high. Ole Johansson brought back practical feedback from SIPit interoperabilty testing events regarding some of the practical aspects of what needs to appear in TLS certificates. Personnel Adam Roach is the document shepherd. Gonzalo Camarillo is the responsible Area Director.