[RAI] new proposed BoF and mailing list on feature interoperability
Jonathan Rosenberg <jdrosen@cisco.com> Fri, 19 January 2007 21:03 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H80tW-0005x9-Jt; Fri, 19 Jan 2007 16:03:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H80tU-0005tf-Jl; Fri, 19 Jan 2007 16:03:28 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H80tQ-0001Cg-77; Fri, 19 Jan 2007 16:03:28 -0500
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-3.cisco.com with ESMTP; 19 Jan 2007 13:03:24 -0800
X-IronPort-AV: i="4.13,212,1167638400"; d="scan'208"; a="458537975:sNHT102601984"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l0JL3Nbr032287; Fri, 19 Jan 2007 13:03:23 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l0JL3MUw004853; Fri, 19 Jan 2007 13:03:22 -0800 (PST)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 19 Jan 2007 13:03:20 -0800
Received: from [10.32.241.158] ([10.32.241.158]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 19 Jan 2007 13:03:20 -0800
Message-ID: <45B13215.7060500@cisco.com>
Date: Fri, 19 Jan 2007 16:03:17 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF Sipping List <sipping@ietf.org>, rai@ietf.org
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Jan 2007 21:03:20.0549 (UTC) FILETIME=[3FC56150:01C73C0D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2625; t=1169240603; x=1170104603; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com> |Subject:=20new=20proposed=20BoF=20and=20mailing=20list=20on=20feature=20 interoperability |Sender:=20; bh=AiYFENnVo6mu9iB9F49qQMDur0QNDUZHImkRBpYwhZw=; b=k4gOQPQrtLzhVAU4hZofkIPkrC5lGsdUOR4kw+y8Csoh49pQflbB3WHeLwlfANrjkTYLkLnT T0zL41/WlcTP6Hk8MdMl/SFXX2ws+/PL9ZIxEwjrazbxjtM4U9H7+n/D;
Authentication-Results: sj-dkim-3; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc:
Subject: [RAI] new proposed BoF and mailing list on feature interoperability
X-BeenThere: rai@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Real-time Applications and Infrastructure \(RAI\)" <rai.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rai>
List-Post: <mailto:rai@ietf.org>
List-Help: <mailto:rai-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=subscribe>
Errors-To: rai-bounces@ietf.org
Please do not reply to this mail. SIP has come a long way in terms of interoperability over the years. However, there are several places where we still have a poor track record of interoperability. One of these is in the area of more advanced types of features. These include many of the features traditionally found on enterprise PBXs, such as park/pickup, shared line extension, and so on. There has been sporadic work on this topic, with many drafts, but no real solution yet. There is a real need to get these interoperability problems solved. This need is coming from the IP PBX/Centrex side and from the consumer side, from groups like TISPAN that want some of these features to work. The interop problems stem from several root cause issues. One is too much variety in the way these features can be implemented. This is good from a flexibility point of view, but it causes interop problems when both endpoints do things differently and won't work together as a consequence. Another problem is lack of sufficient functionality from the specs, in which cases people turn to proprietary techniques. Combine this with the standard "dont want to implement the right thing because its too hard" and general bug problems, and its a mess. To fix this, I think it makes sense to start a working group thats formally tasked with the problem. The idea is to take on individual features, one at a time, figure out the real issues causing interop problems, and address them by either writing some requirements for sip enhancements, or developing some BCPs or informational documents specifying minimum interop requirements. Its also important to do this without trying to formally define what the feature is; we want to allow variation as much as possible while preserving interop. I've been with Cullen, Shida Schubert and a number of others on getting a BoF going in Prague on this. We've got a mailing list that is now set up, and a proposed charter, all of which can be found here: http://sip101.net/index.html Please join the list and participate in the discussions. The more of it we can have prior to Prague, the better the chances we can arrive there with a charter and deliverables that are on target. Thanks, Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza Cisco Fellow Parsippany, NJ 07054-2711 Cisco Systems jdrosen@cisco.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.cisco.com _______________________________________________ RAI mailing list RAI@ietf.org https://www1.ietf.org/mailman/listinfo/rai
- [RAI] new proposed BoF and mailing list on featur… Jonathan Rosenberg