BCP 67, RFC 7957 on DISPATCH-Style Working Groups and the SIP Change Process
rfc-editor@rfc-editor.org Wed, 24 August 2016 20:21 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 4865F12D097 for <ietf-announce@ietfa.amsl.com>; Wed, 24 Aug 2016 13:21:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.17
X-Spam-Level:
X-Spam-Status: No, score=-103.17 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 574nd84DVt6Q for <ietf-announce@ietfa.amsl.com>; Wed, 24 Aug 2016 13:21:07 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EF2912B02C for <ietf-announce@ietf.org>; Wed, 24 Aug 2016 13:21:07 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 53B99B809D7; Wed, 24 Aug 2016 13:21:07 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 67, RFC 7957 on DISPATCH-Style Working Groups and the SIP Change Process
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160824202107.53B99B809D7@rfc-editor.org>
Date: Wed, 24 Aug 2016 13:21:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/kIKKRsvVQNj02rskNL6feHOytl0>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: <https://mailarchive.ietf.org/arch/browse/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, 24 Aug 2016 20:21:09 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 67
RFC 7957
Title: DISPATCH-Style Working Groups and the
SIP Change Process
Author: B. Campbell, Ed.,
A. Cooper,
B. Leiba
Status: Best Current Practice
Stream: IETF
Date: August 2016
Mailbox: ben@nostrum.com,
alcoop@cisco.com,
barryleiba@computer.org
Pages: 6
Characters: 12097
Updates: RFC 5727
See Also: BCP 67
I-D Tag: draft-campbell-art-rfc5727-update-03.txt
URL: https://www.rfc-editor.org/info/rfc7957
DOI: http://dx.doi.org/10.17487/RFC7957
RFC 5727 defined several processes for the former Real-time
Applications and Infrastructure (RAI) area. These processes include
the evolution of the Session Initiation Protocol (SIP) and related
protocols, as well as the operation of the DISPATCH and SIPCORE
working groups. This document updates RFC 5727 to allow flexibility
for the area and working group structure, while preserving the SIP
change processes. It also generalizes the DISPATCH working group
processes so that they can be easily adopted by other working groups.
BCP: This document specifies an Internet Best Current Practice 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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
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