[BLISS] BLISS recharter review will start soon
Robert Sparks <rjsparks@nostrum.com> Thu, 02 February 2012 18:17 UTC
Return-Path: <rjsparks@nostrum.com>
X-Original-To: bliss@ietfa.amsl.com
Delivered-To: bliss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0980921F8534 for <bliss@ietfa.amsl.com>; Thu, 2 Feb 2012 10:17:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, SPF_PASS=-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 EgWvN6MwhLqg for <bliss@ietfa.amsl.com>; Thu, 2 Feb 2012 10:17:20 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 3253921F852E for <bliss@ietf.org>; Thu, 2 Feb 2012 10:17:20 -0800 (PST)
Received: from unexplicable.local (pool-173-57-95-103.dllstx.fios.verizon.net [173.57.95.103]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q12IHFYJ031080 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 2 Feb 2012 12:17:16 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <4F2AD32B.3010009@nostrum.com>
Date: Thu, 02 Feb 2012 12:17:15 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: bliss@ietf.org, Shida Schubert <shida@agnada.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 173.57.95.103 is authenticated by a trusted mechanism)
Subject: [BLISS] BLISS recharter review will start soon
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2012 18:17:21 -0000
BLISS WG: Both of the documents currently in publication requested extend protocols in ways the current BLISS charter rules out of scope. While we've discussed relaxing those restrictions in the past to let the group conclude, we've not formalized it in the charter. This needs to happen before these documents get to IETF review. The following proposed recharter will appear on the IETF general list for review early next week. ----- The BLISS working group is rechartered to adjust its scope to reflect changes in working group interest and RAI processes since its original chartering. BLISS was chartered prior to the creation of DISPATCH. The charter called for the WG to document how to realize four initial building blocks in an interoperable way with existing standards, and to describe the use of those building blocks to implement specific call features. Any extensions to the protocols beyond the creation of event packages or the addition of SIP URI parameters was set out of scope for this working group. Working group interest in all but two of those building blocks has diminished. The current drafts on those two propose extensions that under the original charter would need to be developed in other working groups. Given the update to the SIP change process (RFC5727) and the subsequent restructuring of the RAI area, these constraints are being revised as detailed below. The BLISS working group shall be closed after completing the following two proposed standards: - call completion with queuing as proposed in draft-ietf-bliss-call-completion - shared appearances as proposed in draft-ietf-bliss-shared-appearances The goal to produce a problem statement and a common template for describing primitives is abandoned. The group will continue to work within the constraints of the creation of event packages and SIP URI parameters, with the addition of the ability to - exercise the already standardized extension points of SIP header fields. Currently, the documents propose to extend the SIP Alert-Info header field (RFC3261) to carry an appearance identifier, and the SIP Call-Info header field (RFC3261) to carry a call completion indicator. - extend the SIP Dialog event package (RFC4235) to carry appearance related state, The working group will coordinate review of those extensions with the SIPCORE working group. Describing the security properties (particularly any privacy considerations) of these deliverables remains of special importance. Upon completion of these two work items, the working group will conclude. Future proposals should be directed to the DISPATCH working group. Goals and Milestones Mar 2012 Submit Shared Appearances to the IESG for publication as Proposed Standard Jul 2012 Submit Call Completion to the IESG for publication as Proposed Standard Sep 2012 Bliss concludes
- [BLISS] BLISS recharter review will start soon Robert Sparks