RFC 6216 on Example Call Flows Using Session Initiation Protocol (SIP) Security Mechanisms
rfc-editor@rfc-editor.org Wed, 06 April 2011 00:33 UTC
Return-Path: <wwwrun@rfc-editor.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 EDC7E28C170; Tue, 5 Apr 2011 17:33:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.405
X-Spam-Level:
X-Spam-Status: No, score=-102.405 tagged_above=-999 required=5 tests=[AWL=0.195, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 hn58Z+6COlhB; Tue, 5 Apr 2011 17:33:20 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 25C4628C16F; Tue, 5 Apr 2011 17:33:20 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9265BE0772; Tue, 5 Apr 2011 17:34:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6216 on Example Call Flows Using Session Initiation Protocol (SIP) Security Mechanisms
From: rfc-editor@rfc-editor.org
Message-Id: <20110406003441.9265BE0772@rfc-editor.org>
Date: Tue, 05 Apr 2011 17:34:41 -0700
Cc: sipcore@ietf.org, 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: Wed, 06 Apr 2011 00:33:21 -0000
A new Request for Comments is now available in online RFC libraries. RFC 6216 Title: Example Call Flows Using Session Initiation Protocol (SIP) Security Mechanisms Author: C. Jennings, K. Ono, R. Sparks, B. Hibbard, Ed. Status: Informational Stream: IETF Date: April 2011 Mailbox: fluffy@cisco.com, kumiko@cs.columbia.edu, Robert.Sparks@tekelec.com, Brian.Hibbard@tekelec.com Pages: 67 Characters: 143891 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-sipcore-sec-flows-09.txt URL: http://www.rfc-editor.org/rfc/rfc6216.txt 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. To help facilitate interoperability testing, it includes certificates used in the example call flows and processes to create certificates for testing. This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Session Initiation Protocol Core 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 http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. 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