RFC 6086 on Session Initiation Protocol (SIP) INFO Method and Package Framework

rfc-editor@rfc-editor.org Fri, 14 January 2011 20: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 944493A6C7A; Fri, 14 Jan 2011 12:41:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.987
X-Spam-Level:
X-Spam-Status: No, score=-101.987 tagged_above=-999 required=5 tests=[AWL=0.013, 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 Djp9W-WsiBVz; Fri, 14 Jan 2011 12:41:56 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id CFD873A6C79; Fri, 14 Jan 2011 12:41:56 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 751F4E072D; Fri, 14 Jan 2011 12:44:23 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6086 on Session Initiation Protocol (SIP) INFO Method and Package Framework
From: rfc-editor@rfc-editor.org
Message-Id: <20110114204423.751F4E072D@rfc-editor.org>
Date: Fri, 14 Jan 2011 12:44:23 -0800
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: Fri, 14 Jan 2011 20:41:57 -0000

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

        
        RFC 6086

        Title:      Session Initiation Protocol (SIP) INFO 
                    Method and Package Framework 
        Author:     C. Holmberg, E. Burger,
                    H. Kaplan
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2011
        Mailbox:    christer.holmberg@ericsson.com, 
                    eburger@standardstrack.com, 
                    hkaplan@acmepacket.com
        Pages:      36
        Characters: 75949
        Obsoletes:  RFC2976

        I-D Tag:    draft-ietf-sipcore-info-events-10.txt

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

This document defines a method, INFO, for the Session Initiation
Protocol (SIP), and an Info Package mechanism.  This document
obsoletes RFC 2976.  For backward compatibility, this document also
specifies a "legacy" mode of usage of the INFO method that is
compatible with the usage previously defined in RFC 2976, referred to
as "legacy INFO Usage" in this document.  [STANDARDS-TRACK]

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