BCP 67, RFC 5727 on Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area
rfc-editor@rfc-editor.org Wed, 10 March 2010 19:18 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 CFACA3A6C45 for <ietf-announce@core3.amsl.com>; Wed, 10 Mar 2010 11:18:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.473
X-Spam-Level:
X-Spam-Status: No, score=-2.473 tagged_above=-999 required=5 tests=[AWL=0.127, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 qrvzLibzczwW for <ietf-announce@core3.amsl.com>; Wed, 10 Mar 2010 11:18:37 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id AC0E33A6BFF for <ietf-announce@ietf.org>; Wed, 10 Mar 2010 11:17:58 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 2D242E0734; Wed, 10 Mar 2010 11:18:04 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 67, RFC 5727 on Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area
From: rfc-editor@rfc-editor.org
Message-Id: <20100310191804.2D242E0734@rfc-editor.org>
Date: Wed, 10 Mar 2010 11:18:04 -0800
Cc: 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: Wed, 10 Mar 2010 19:18:39 -0000
A new Request for Comments is now available in online RFC libraries. BCP 67 RFC 5727 Title: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area Author: J. Peterson, C. Jennings, R. Sparks Status: Best Current Practice Date: March 2010 Mailbox: jon.peterson@neustar.biz, fluffy@cisco.com, rjsparks@nostrum.com Pages: 14 Characters: 35033 Obsoletes: RFC3427 Updates: RFC3265, RFC3969 See Also: BCP0067 I-D Tag: draft-peterson-rai-rfc3427bis-04.txt URL: http://www.rfc-editor.org/rfc/rfc5727.txt This memo documents a process intended to organize the future development of the Session Initiation Protocol (SIP) and related work in the Real-time Applications and Infrastructure (RAI) Area. As the environments in which SIP is deployed grow more numerous and diverse, modifying or extending SIP in certain ways may threaten the interoperability and security of the protocol; however, the IETF process must also cater to the realities of existing deployments and serve the needs of the implementers working with SIP. This document therefore defines the functions of two long-lived working groups in the RAI Area that are, respectively, responsible for the maintenance of the core SIP specifications and the development of new efforts to extend and apply work in this space. This document obsoletes RFC 3427. This memo documents an Internet Best Current Practice. BCP: This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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