RFC 6072 on Certificate Management Service for the Session Initiation Protocol (SIP)

rfc-editor@rfc-editor.org Tue, 08 February 2011 19:41 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 1E8643A683E; Tue, 8 Feb 2011 11:41:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.867
X-Spam-Level:
X-Spam-Status: No, score=-101.867 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, 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 vYO2GA6uWlci; Tue, 8 Feb 2011 11:41:47 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 48EF53A6837; Tue, 8 Feb 2011 11:41:47 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 24E08E0749; Tue, 8 Feb 2011 11:41:55 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6072 on Certificate Management Service for the Session Initiation Protocol (SIP)
From: rfc-editor@rfc-editor.org
Message-Id: <20110208194155.24E08E0749@rfc-editor.org>
Date: Tue, 08 Feb 2011 11:41:55 -0800
Cc: sip@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: Tue, 08 Feb 2011 19:41:48 -0000

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

        
        RFC 6072

        Title:      Certificate Management Service for the 
                    Session Initiation Protocol (SIP) 
        Author:     C. Jennings, J. Fischl, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2011
        Mailbox:    fluffy@cisco.com, 
                    jason.fischl@skype.net
        Pages:      30
        Characters: 69071
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sip-certs-15.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6072.txt

This document defines a credential service that allows Session
Initiation Protocol (SIP) User Agents (UAs) to use a SIP event
package to discover the certificates of other users.  This mechanism
allows User Agents that want to contact a given Address-of-Record
(AOR) to retrieve that AOR's certificate by subscribing to the
credential service, which returns an authenticated response
containing that certificate.  The credential service also allows
users to store and retrieve their own certificates and private keys. 
[STANDARDS-TRACK]

This document is a product of the Session Initiation Protocol Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 Internet
Official Protocol Standards (STD 1) 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
  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