[Sipping] RFC 5363 on Framework and Security Considerations for Session Initiation Protocol (SIP) URI-List Services

rfc-editor@rfc-editor.org Thu, 30 October 2008 18:27 UTC

Return-Path: <sipping-bounces@ietf.org>
X-Original-To: sipping-archive@optimus.ietf.org
Delivered-To: ietfarch-sipping-archive@core3.amsl.com
Received: from [] (localhost []) by core3.amsl.com (Postfix) with ESMTP id 9CF7D28C1B0; Thu, 30 Oct 2008 11:27:31 -0700 (PDT)
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id AEC7E28C160; Thu, 30 Oct 2008 11:27:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.312
X-Spam-Status: No, score=-17.312 tagged_above=-999 required=5 tests=[AWL=-0.312, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id 7hJKP6+6wgAT; Thu, 30 Oct 2008 11:27:27 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu []) by core3.amsl.com (Postfix) with ESMTP id 77E273A69FB; Thu, 30 Oct 2008 11:27:22 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id AB37316CBAC; Thu, 30 Oct 2008 11:27:05 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20081030182705.AB37316CBAC@bosco.isi.edu>
Date: Thu, 30 Oct 2008 11:27:05 -0700
Cc: sipping@ietf.org, rfc-editor@rfc-editor.org
Subject: [Sipping] RFC 5363 on Framework and Security Considerations for Session Initiation Protocol (SIP) URI-List Services
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

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

        RFC 5363

        Title:      Framework and Security Considerations for 
                    Session Initiation Protocol (SIP) URI-List Services 
        Author:     G. Camarillo, A.B. Roach
        Status:     Standards Track
        Date:       October 2008
        Mailbox:    Gonzalo.Camarillo@ericsson.com, 
        Pages:      10
        Characters: 22912
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sipping-uri-services-07.txt

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

This document describes the need for SIP URI-list services and
provides requirements for their invocation.  Additionally, it defines
a framework for SIP URI-list services, which includes security
considerations applicable to these services.  [STANDARDS TRACK]

This document is a product of the Session Initiation Proposal 
Investigation 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

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
USC/Information Sciences Institute

Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP