RFC 5362 on The Session Initiation Protocol (SIP) Pending Additions Event Package

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

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1135F3A6A45; Thu, 30 Oct 2008 11:27:28 -0700 (PDT)
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 6599E3A6A45; Thu, 30 Oct 2008 11:27:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.356
X-Spam-Level:
X-Spam-Status: No, score=-17.356 tagged_above=-999 required=5 tests=[AWL=-0.357, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
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 jW5q578wf26H; Thu, 30 Oct 2008 11:27:26 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 12B2A3A6AC6; Thu, 30 Oct 2008 11:27:19 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 16F5E16CBAA; Thu, 30 Oct 2008 11:27:02 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5362 on The Session Initiation Protocol (SIP) Pending Additions Event Package
From: rfc-editor@rfc-editor.org
Message-Id: <20081030182702.16F5E16CBAA@bosco.isi.edu>
Date: Thu, 30 Oct 2008 11:27:02 -0700
Cc: sipping@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/pipermail/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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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

        
        RFC 5362

        Title:      The Session Initiation Protocol (SIP) 
                    Pending Additions Event Package 
        Author:     G. Camarillo
        Status:     Standards Track
        Date:       October 2008
        Mailbox:    Gonzalo.Camarillo@ericsson.com
        Pages:      16
        Characters: 32137
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sipping-pending-additions-05.txt

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


This document defines the SIP Pending Additions event package.  This
event package is used by SIP relays to inform user agents about the
consent-related status of the entries to be added to a resource list.
[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
  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
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce