IETF Logo Mail Archive

Re: [BLISS] Welcome! Main question - what services?

Jonathan Rosenberg <jdrosen@cisco.com> Wed, 24 January 2007 15:21 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9jvo-00079a-0k; Wed, 24 Jan 2007 10:21:00 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H9jvm-00079Q-8i for bliss@ietf.org; Wed, 24 Jan 2007 10:20:58 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1H9jvb-0006S5-NX for bliss@ietf.org; Wed, 24 Jan 2007 10:20:58 -0500
Received: from sj-dkim-6.cisco.com ([171.68.10.81]) by sj-iport-4.cisco.com with ESMTP; 24 Jan 2007 07:20:47 -0800
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-6.cisco.com (8.12.11/8.12.11) with ESMTP id l0OFKkrY023742; Wed, 24 Jan 2007 07:20:46 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l0OFKkho016281; Wed, 24 Jan 2007 07:20:46 -0800 (PST)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 Jan 2007 07:20:46 -0800
Received: from [10.71.9.227] ([10.21.98.138]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 24 Jan 2007 07:20:46 -0800
Message-ID: <45B7794D.6000103@cisco.com>
Date: Wed, 24 Jan 2007 10:20:45 -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: jaiminp@huawei.com
Subject: Re: [BLISS] Welcome! Main question - what services?
References: <002b01c73ea5$bb2c0a20$5208120a@china.huawei.com>
In-Reply-To: <002b01c73ea5$bb2c0a20$5208120a@china.huawei.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Jan 2007 15:20:46.0034 (UTC) FILETIME=[38640B20:01C73FCB]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1803; t=1169652046; x=1170516046; c=relaxed/simple; s=sjdkim6002; 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:=20Re=3A=20[BLISS]=20Welcome!=20Main=20question=20-=20what=20ser vices? |Sender:=20; bh=bTSzpUislnwG7o52y1m3OKHXgzucTnZzJJI3D9tGX8w=; b=GW9o6UphbaFVIw34KSWcKUUp4ma4tLhzoOYS0CNDMIU6TtQDsjsCVpjHskkhYoWwN++w2eaG AexPYVTjvSMYZeF1DHkRSv+Ea/iTUssojx+RURxyE+sAGW8kaTGODqX3;
Authentication-Results: sj-dkim-6; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com/sjdkim6002 verified; );
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: bliss@ietf.org
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
Errors-To: bliss-bounces@ietf.org


Jaimin Pancholi wrote:

> Some thoughts:
> 
> I think first we should list the services we need to address as part of this
> forum !

Right. The proposed charter identifies four. We can expand this to more 
later, but I think we need to start with a small number of the highest 
priority services, and demonstrate that we can usefully solve the 
problem. Then we can move on to more.

> 
> After which we can divide them based on the Network Entity who need to
> support the same.
> i.e. some services can work by UA supporting it, Some services can work by
> Server supporting it.

Right, this is one of the things which leads to interop problems - 
different solutions for who implements what. As I alluded to in my 
previous message, there are a few ways one can solve this. One way is to 
standardize a single approach. Another way, as I suggested in my note, 
is to allow variation but require some of the participants to support 
more than one mechanism to support variation in the capabilities of the 
others. The third is to demonstrate that you can still interoperate 
successfully even when all of the entities do the service differently.

This is why the key part of working on each of these services is to have 
a section in the document for each that is an EXHAUSTIVE enumeration of 
the various ways in which the feature has been implemented, so we can 
figure out what the right path is to take for that feature.

-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

_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www1.ietf.org/mailman/listinfo/bliss

v2.23.0 | Report a Bug | By Email