RFC 6446 on Session Initiation Protocol (SIP) Event Notification Extension for Notification Rate Control

rfc-editor@rfc-editor.org Fri, 27 January 2012 17:28 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1351921F850C; Fri, 27 Jan 2012 09:28:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.149
X-Spam-Level:
X-Spam-Status: No, score=-102.149 tagged_above=-999 required=5 tests=[AWL=-0.149, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WVClAQj366k3; Fri, 27 Jan 2012 09:28:31 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 3D7C621F8508; Fri, 27 Jan 2012 09:28:29 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 634D6B1E004; Fri, 27 Jan 2012 09:24:52 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6446 on Session Initiation Protocol (SIP) Event Notification Extension for Notification Rate Control
From: rfc-editor@rfc-editor.org
Message-Id: <20120127172452.634D6B1E004@rfc-editor.org>
Date: Fri, 27 Jan 2012 09:24:52 -0800
Cc: sipcore@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 27 Jan 2012 17:28:32 -0000

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

        
        RFC 6446

        Title:      Session Initiation Protocol (SIP) Event 
                    Notification Extension for Notification Rate Control 
        Author:     A. Niemi, K. Kiss,
                    S. Loreto
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2012
        Mailbox:    aki.niemi@nokia.com, 
                    krisztian.kiss@nokia.com, 
                    salvatore.loreto@ericsson.com
        Pages:      25
        Characters: 57971
        Updates:    RFC3265

        I-D Tag:    draft-ietf-sipcore-event-rate-control-09.txt

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

This document specifies mechanisms for adjusting the rate of Session
Initiation Protocol (SIP) event notifications.  These mechanisms can
be applied in subscriptions to all SIP event packages.  This document
updates RFC 3265.  [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