From bliss-bounces@ietf.org Thu Mar 01 10:31:30 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMnFi-0008NL-Uk; Thu, 01 Mar 2007 10:31:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMnFi-0008L6-4z
	for bliss@ietf.org; Thu, 01 Mar 2007 10:31:30 -0500
Received: from rwcrmhc11.comcast.net ([216.148.227.151])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMnFg-0004ZK-N0
	for bliss@ietf.org; Thu, 01 Mar 2007 10:31:30 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (rwcrmhc11) with ESMTP
	id <20070301153127m1100g1beve>; Thu, 1 Mar 2007 15:31:27 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l21FVQJs018310
	for <bliss@ietf.org>; Thu, 1 Mar 2007 10:31:26 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l21FVQZn018306;
	Thu, 1 Mar 2007 10:31:26 -0500
Date: Thu, 1 Mar 2007 10:31:26 -0500
Message-Id: <200703011531.l21FVQZn018306@dragon.ariadne.com>
To: bliss@ietf.org
From: Dale.Worley@comcast.net
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Subject: [BLISS] I-Ds concerning problems with response codes
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

I've submitted a set of Internet-Drafts about three problems with SIP
response codes:

(1) the current response codes are not in some instances fine-grained
enough to support networks in which there are redundant paths to
destination UAs,

(2) the 6xx class responses are (as defined) harmful in most
applications and should not be generated by UAs, and

(3) the response codes in the category "no usable destination for this
URI" are muddled and need careful redefinition.

The abstracts are:

   Classifying Response Codes to Support Multiple Path Routing in the
   Session Initiation Protocol (SIP)
   draft-worley-redundancy-response-00

   http://www.ietf.org/internet-drafts/draft-worley-redundancy-response-00.txt

   An increasing number of SIP architectures implement multiple path
   routing (MPR), which is the providing of more than one path for a
   call to reach a destination user agent (UA).  To implement MPR
   well, the proxy which forks a request onto the paths needs to be
   able to determine if a fork that failed reached the destination UA
   and was rejected by the UA (and so an alternate path should not be
   tried), or if the fork failed before reaching the UA (and so an
   alternate path should be attempted).  In order that the proxy can
   distinguish these two situations, response codes should
   unambiguously identify which of these situations applies.  This
   Internet-Draft begins classifying the current usage of response
   codes, their implications for MPR, and possible improvements.

   6xx-Class Responses Considered Harmful in the Session Initiation
   Protocol (SIP)
   draft-worley-6xx-considered-harmful-00

   http://www.ietf.org/internet-drafts/draft-worley-6xx-considered-harmful-00.txt

   The specification of the Session Initiation Protocol (SIP) permits a
   user agent (UA) that receives a call to generate a response in the
   "6xx class" that not only rejects the call but also requires the
   termination of all attempts to route the call to alternative
   destinations.  As the call may have reached the UA through multiple
   forwardings whose meanings cannot be known by the UA, the global
   termination of alternative routing can only rarely be correctly
   requested by the UA.  Because such responses are almost never
   appropriate, ability of a UA to generate such responses is harmful,
   and all 6xx class responses should be replaced with 4xx class
   responses with similar meanings.  However, there is no 4xx class
   response similar to "603 Decline", and so one needs to be created.

   Response Codes Regarding URIs that Cannot Be Routed to a
   Destination in the Session Initiation Protocol (SIP)
   draft-worley-ex-uri-00

   http://www.ietf.org/internet-drafts/draft-worley-ex-uri-00.txt

   The Session Initiation Protocol (SIP) provides a number of response
   codes which a SIP agent can use to indicate that it cannot find a
   suitable destination to which to send a request.  Unfortunately, this
   set of response codes was not carefully designed, making it difficult
   in many cases for a proxy to select a response code that accurately
   reflects the proxy's knowledge about the request URI.  This document
   describes these response codes and their current usage.

Feel free to contact me with any comments.

Dale

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



From bliss-bounces@ietf.org Thu Mar 01 13:17:30 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMpq7-0002pW-JH; Thu, 01 Mar 2007 13:17:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HMpq6-0002pK-KC
	for bliss@ietf.org; Thu, 01 Mar 2007 13:17:14 -0500
Received: from zrtps0kp.nortel.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMpq5-0002Uk-6y
	for bliss@ietf.org; Thu, 01 Mar 2007 13:17:14 -0500
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l21IH8n06547; Thu, 1 Mar 2007 13:17:09 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [BLISS] I-Ds concerning problems with response codes
Date: Thu, 1 Mar 2007 12:17:05 -0600
Message-ID: <1ECE0EB50388174790F9694F77522CCF0F67A4CB@zrc2hxm0.corp.nortel.com>
In-Reply-To: <200703011531.l21FVQZn018306@dragon.ariadne.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] I-Ds concerning problems with response codes
Thread-Index: AcdcFrp0HUF5LLyhQ1Se8LZbxCDqNAAE9sQQ
References: <200703011531.l21FVQZn018306@dragon.ariadne.com>
From: "Francois Audet" <audet@nortel.com>
To: <Dale.Worley@comcast.net>, <bliss@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 225414c974e0d6437992164e91287a51
Cc: 
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

Dale,

While I understand the motivation for this draft, it does not
address at all the reason why people actually use 600/603 to Decline
a call everywhere (which, it is true, may cause the session to=20
be delivered to voicemail, or may just result in busy tone).

There are real scenarios where you want to have busy/decline everywhere.

If you call me, and I don't want to take your call at all, I may
want to send 600 or 603. It is not harmful. That's what I want.

I specifically do not want to use 486 or 441 because I do not want
other devices to continue to ring. This would be particularly=20
annoying for people who have both a phone at their desk and a PC
client.=20

So in my mind, the use case for 6XX is not "harmul" if that is the
desired behavior. What may be harmful is the improper usage of 6XX.
I think the document should really be "Best Current Practice for
the use of 6XX-Class Response". And should make this clear how to
use 6XX: i.e., warn of the consequences.

Now, for the specific issue of voicemail.

The reason why people send a 603 today is for the same reason described
above (i.e., I want it to go to voicemail NOW, not after all my other
phones
stop ringing. This is mostly because I don't want my phone to keep
ringing
in my face, especially if I'm talking on another phone). Again, a 4XX
class response will not solve this problem.

That particular usage of 6XX is perhaps an abuse of the protocol (at
least for
the description of 600). I don't know why we put that restriction about
voicemail
in 600 in the first place as it sounds kind of stupid to me, but
assuming=20
we want to keep it, we must find a way to allow for dynamically
forwarding
to voicemail. A 302 to voicemail may work (at first glance this may seem
to be
an extra requiremnt to have the voicemail address configured in the
phone, but I'd=20
argue you need it anyways to access voicemail, unless the user memorizes
the
voicemail number).

Also, voicemail is only one usecase. There is the more general case of
"default=20
treatment". This could include retargeting to an automata, operator, and
so forth.

To me it would be much more logical if 6XX meant that the AOR was not
reachable
anywhere, thereby allowing retargeting. I find the notion that service
operators
will not provide "alternative treatment" when a 6XX is received just
because of
"considered harmful" spec extremely naive. At the end of the day,
customers
and legal considerations are more important than a spec.

On the desireability of a new 441 "Decline": I don't think it is
warranted.
One can use 480 "Temporarily unavailable" which is described as being=20
the proper value for a "Do not disturb" service.



> -----Original Message-----
> From: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net]=20
> Sent: Thursday, March 01, 2007 07:31
> To: bliss@ietf.org
> Subject: [BLISS] I-Ds concerning problems with response codes
>=20
> I've submitted a set of Internet-Drafts about three problems=20
> with SIP response codes:
>=20
> (1) the current response codes are not in some instances=20
> fine-grained enough to support networks in which there are=20
> redundant paths to destination UAs,
>=20
> (2) the 6xx class responses are (as defined) harmful in most=20
> applications and should not be generated by UAs, and
>=20
> (3) the response codes in the category "no usable destination=20
> for this URI" are muddled and need careful redefinition.
>=20
> The abstracts are:
>=20
>    Classifying Response Codes to Support Multiple Path Routing in the
>    Session Initiation Protocol (SIP)
>    draft-worley-redundancy-response-00
>=20
>   =20
> http://www.ietf.org/internet-drafts/draft-worley-redundancy-re
> sponse-00.txt
>=20
>    An increasing number of SIP architectures implement multiple path
>    routing (MPR), which is the providing of more than one path for a
>    call to reach a destination user agent (UA).  To implement MPR
>    well, the proxy which forks a request onto the paths needs to be
>    able to determine if a fork that failed reached the destination UA
>    and was rejected by the UA (and so an alternate path should not be
>    tried), or if the fork failed before reaching the UA (and so an
>    alternate path should be attempted).  In order that the proxy can
>    distinguish these two situations, response codes should
>    unambiguously identify which of these situations applies.  This
>    Internet-Draft begins classifying the current usage of response
>    codes, their implications for MPR, and possible improvements.
>=20
>    6xx-Class Responses Considered Harmful in the Session Initiation
>    Protocol (SIP)
>    draft-worley-6xx-considered-harmful-00
>=20
>   =20
> http://www.ietf.org/internet-drafts/draft-worley-6xx-considere
> d-harmful-00.txt
>=20
>    The specification of the Session Initiation Protocol (SIP)=20
> permits a
>    user agent (UA) that receives a call to generate a response in the
>    "6xx class" that not only rejects the call but also requires the
>    termination of all attempts to route the call to alternative
>    destinations.  As the call may have reached the UA through multiple
>    forwardings whose meanings cannot be known by the UA, the global
>    termination of alternative routing can only rarely be correctly
>    requested by the UA.  Because such responses are almost never
>    appropriate, ability of a UA to generate such responses is harmful,
>    and all 6xx class responses should be replaced with 4xx class
>    responses with similar meanings.  However, there is no 4xx class
>    response similar to "603 Decline", and so one needs to be created.
>=20
>    Response Codes Regarding URIs that Cannot Be Routed to a
>    Destination in the Session Initiation Protocol (SIP)
>    draft-worley-ex-uri-00
>=20
>    http://www.ietf.org/internet-drafts/draft-worley-ex-uri-00.txt
>=20
>    The Session Initiation Protocol (SIP) provides a number of response
>    codes which a SIP agent can use to indicate that it cannot find a
>    suitable destination to which to send a request. =20
> Unfortunately, this
>    set of response codes was not carefully designed, making=20
> it difficult
>    in many cases for a proxy to select a response code that accurately
>    reflects the proxy's knowledge about the request URI. =20
> This document
>    describes these response codes and their current usage.
>=20
> Feel free to contact me with any comments.
>=20
> Dale
>=20
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www1.ietf.org/mailman/listinfo/bliss
>=20

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



From bliss-bounces@ietf.org Mon Mar 05 09:11:22 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HODuL-00008s-SC; Mon, 05 Mar 2007 09:11:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HODuK-00008e-Pb
	for bliss@ietf.org; Mon, 05 Mar 2007 09:11:20 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HODuI-00010G-Eg
	for bliss@ietf.org; Mon, 05 Mar 2007 09:11:20 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by sj-iport-6.cisco.com with ESMTP; 05 Mar 2007 06:11:17 -0800
X-IronPort-AV: i="4.14,249,1170662400"; 
	d="scan'208"; a="117997938:sNHT276285654"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l25EBHr7012333
	for <bliss@ietf.org>; Mon, 5 Mar 2007 09:11:17 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l25EBCa3020564
	for <bliss@ietf.org>; Mon, 5 Mar 2007 14:11:16 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Mar 2007 09:11:13 -0500
Received: from [192.168.1.104] ([10.86.242.117]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Mar 2007 09:11:13 -0500
Message-ID: <45EC2500.3070403@cisco.com>
Date: Mon, 05 Mar 2007 09:11:12 -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: bliss@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Mar 2007 14:11:13.0133 (UTC)
	FILETIME=[21ABE1D0:01C75F30]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1551; t=1173103877;
	x=1173967877; c=relaxed/simple; s=rtpdkim2001;
	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:=20Proposed=20Pragua=20agenda=20for=20BLISS
	|Sender:=20 |To:=20bliss@ietf.org;
	bh=6uZkMKvXyeg0PF9bV8MCPZSNNeiZPuIQBhs59QK+Z6I=;
	b=nfu3vvjxG3bAFVRzaW2O183tw14lQqOr+wviRSp/QUjrLv1969GHbxRXCHw/eeW7XqwDzFZX
	skQtqckWeJJ1orYKc4wNEZNtJtYTJO2f/cIWZio0lytebVYDMauL2wxF;
Authentication-Results: rtp-dkim-2; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Subject: [BLISS] Proposed Pragua agenda for BLISS
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

Fortunately, bliss has been moved off of the SIMPLE conflict, and we are 
now scheduled here:

TUESDAY, March 20, 2007

1300-1500 Afternoon Session I
Roma/Vienna/Madrid      INT     ancp	Access Node Control Protocol WG
Congress II             INT     mipshop	Mobility for IP: Performance,
                                         Signaling and Handoff
                                         Optimization WG
Karlin I                OPS     bmwg	Benchmarking Methodology WG
Grand Ballroom          RAI     bliss	Basic Level of Interoperability
                                         for SIP Services BOF
Congress III            RTG     ccamp	Common Control and Measurement 

                                         Plane WG
Congress I              SEC     nea	Network Endpoint Assessment WG
Athens/Barcelona/Berlin TSV     dccp	Datagram Congestion Control
                                         Protocol WG

Here is my proposed agenda:

1. Agenda Bashing [5m, chairs]
2. Problem statement and motivation [30m, Jonathan R.]
3. Charter review [45m, Shida]
4. Shared line [30m]


Please let me or Shida know if there are additional items you'd like to 
see on the charter.

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

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



From bliss-bounces@ietf.org Mon Mar 05 09:38:47 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOEKi-00043c-8H; Mon, 05 Mar 2007 09:38:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOEKg-00042R-8i
	for bliss@ietf.org; Mon, 05 Mar 2007 09:38:34 -0500
Received: from sea02-mxf01.citel.com ([205.234.66.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOEKe-00084r-T5
	for bliss@ietf.org; Mon, 05 Mar 2007 09:38:34 -0500
Received: from [10.8.50.21] (helo=sea02-mxc01.citel.com)
	by sea02-mxf01.citel.com with smtp (Exim 4.43)
	id 1HOEKY-0006Vu-0x; Mon, 05 Mar 2007 06:38:26 -0800
Subject: RE: [BLISS] I-Ds concerning problems with response codes
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 5 Mar 2007 06:38:16 -0800
Content-class: urn:content-classes:message
Message-ID: <76431CABEC5EED489807DB8AEBCCA0BCC1D0F2@sea02-mxc01.citel.com>
X-MimeOLE: Produced By Microsoft Exchange V6.5
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF0F67A4CB@zrc2hxm0.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] I-Ds concerning problems with response codes
Thread-index: AcdcFrp0HUF5LLyhQ1Se8LZbxCDqNAAE9sQQAMCpb+A=
References: <200703011531.l21FVQZn018306@dragon.ariadne.com>
	<1ECE0EB50388174790F9694F77522CCF0F67A4CB@zrc2hxm0.corp.nortel.com>
From: "Michael Procter" <michael.procter@citel.com>
To: "Francois Audet" <audet@nortel.com>, <Dale.Worley@comcast.net>,
	<bliss@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: 
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

Francois, Dale,

I agree with both of you, but I think there is a problem associated with
both approaches.  On the one hand, Dale is right when he observes that
global termination of a call attempt by a UA is almost never correct.
And on the other, Francois is right when saying that there are
circumstances when you do want to cancel multiple forks from one UA.

Dale wrote (in hid 6xx-considered-harmful draft):
> As the call may have reached the UA through multiple
> forwardings whose meanings cannot be known by the UA, the global
> termination of alternative routing can only rarely be correctly
> requested by the UA.

To which Francois replied:
> There are real scenarios where you want to have busy/decline
everywhere.
>=20
> If you call me, and I don't want to take your call at all, I may
> want to send 600 or 603. It is not harmful. That's what I want.
>=20
> I specifically do not want to use 486 or 441 because I do not want
> other devices to continue to ring. This would be particularly
> annoying for people who have both a phone at their desk and a PC
> client.

Here is a clear case when the fork-cancelling property of a 6xx code is
very desirable.  However, there is a related case where it is not.

Consider three salespeople (Alice, Bob and Colin) who each have multiple
devices (desk-phones and soft-clients for example).  If a call arrives
at sip:sales@example.com, it is forked to each salesperson.  The call to
each salesperson is in turn forked to each device.  Now, Alice is busy
with a client, and wishes to hit one button to cancel the call attempt
for both her UAs.  603 is a natural choice, as Francois suggests.  But
because of the problem that Dale describes, the calls to Bob and Colin
are also cancelled.  This is clearly undesirable.

I think that the problem arises because the request-uri is rewritten
multiple times (e.g. from sip:sales@example.com to sip:alice@example.com
to sip:alice-desk-phone@some-ip).  It is far from clear what the scope
of a 6xx code should be.  The description of 6xx codes from RFC3261
Section 21.6 is quite broad:

   6xx responses indicate that a server has definitive information about
   a particular user, not just the particular instance indicated in the
   Request-URI.

I suspect that 6xx codes would work a lot better if this was taken to
refer to the request-uri just prior to the final rewriting.  That is to
say, when Alice's desk-phone rejects a call with 6xx, it is assumed that
it refers to sip:alice@example.com and not any earlier one (such as
sip:sales@example.com).

This could be achieved by saying that 6xx responses propagate back until
they reach a proxy that forked, at which point the cancelling occurs as
expected.  But the forking proxy should map the 6xx code to an
appropriate 4xx code before sending it further upstream.

This approach seems to me to answer both problems raised - it clearly
puts a limit on the scope of a 6xx, whilst still giving a useful action
for a specific user.

Regards,

Michael Procter

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



From bliss-bounces@ietf.org Mon Mar 05 11:31:10 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOG5Z-0002qR-Ei; Mon, 05 Mar 2007 11:31:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOG5Y-0002oz-EN
	for bliss@ietf.org; Mon, 05 Mar 2007 11:31:04 -0500
Received: from usnwksmtp02e.usa.siemens.com ([12.46.135.31]
	helo=usnwk220srv.usa.siemens.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOG5W-0007xd-Lw
	for bliss@ietf.org; Mon, 05 Mar 2007 11:31:04 -0500
Received: from usnwk202a.ww017.siemens.net ([155.45.111.47]) by
	usnwk220srv.usa.siemens.com with InterScan Messaging Security
	Suite; Mon, 05 Mar 2007 08:30:58 -0800
Received: from USNWK101MSX.ww017.siemens.net ([155.45.111.55]) by
	usnwk202a.ww017.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Mar 2007 08:30:54 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [BLISS] I-Ds concerning problems with response codes
Date: Mon, 5 Mar 2007 08:30:53 -0800
Message-ID: <55AF62549C5C4049B13A2A273445C48627A199D0@USNWK101MSX.ww017.siemens.net>
In-Reply-To: <76431CABEC5EED489807DB8AEBCCA0BCC1D0F2@sea02-mxc01.citel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] I-Ds concerning problems with response codes
Thread-Index: AcdcFrp0HUF5LLyhQ1Se8LZbxCDqNAAE9sQQAMCpb+AABONIwA==
From: "Kucmerowski, Dennis \(Com US\)" <dennis.kucmerowski@siemens.com>
To: "Michael Procter" <michael.procter@citel.com>,
	"Francois Audet" <audet@nortel.com>, <Dale.Worley@comcast.net>,
	<bliss@ietf.org>
X-OriginalArrivalTime: 05 Mar 2007 16:30:54.0579 (UTC)
	FILETIME=[A5670C30:01C75F43]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Cc: 
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

Francois and Dale,

In reply to the 6xx to cancel the call.  Very few business will allow an
employee the capability to cancel/reject a call.  It is not good
business to take an incoming call whereby the calling party is ringing
and reject the call which may then return busy tone to the calling
party. Loss of business. The calling party would go from hearing
ringback to busy and think someone has answered and then disconnected
them.  The call party will most likely call again.

The proper way to handled the call is to redirect to another destination
e.g., human or voicemail, in order to not lose business.

As for not wishing to listen to ringing; the UA has multiple ways to
locally handle ringing (e.g., Ringer Off, low volume ringing, ring
burst, no ringing (audible) when the user is active in a connection,
etc.

Do Not Disturb is another issue and should have an explicit DND response
(note: 480 is not explicit since 480 can be used for many functions to
indicate temporary unavailable) so that the originating UA can act on a
DND in a specific way is needed.

Reject the call 6xx is the exception case for releasing all multiple
forked call and not the normal case, once a call is alerting.

I agree there are cases when forking calls, where releasing a single
call is needed.


Best Regards,
=20
Dennis L. Kucmerowski=20

561-923-1703
Systems Engineering
=20

-----Original Message-----
From: Michael Procter [mailto:michael.procter@citel.com]=20
Sent: Monday, March 05, 2007 9:38 AM
To: Francois Audet; Dale.Worley@comcast.net; bliss@ietf.org
Subject: RE: [BLISS] I-Ds concerning problems with response codes

Francois, Dale,

I agree with both of you, but I think there is a problem associated with
both approaches.  On the one hand, Dale is right when he observes that
global termination of a call attempt by a UA is almost never correct.
And on the other, Francois is right when saying that there are
circumstances when you do want to cancel multiple forks from one UA.

Dale wrote (in hid 6xx-considered-harmful draft):
> As the call may have reached the UA through multiple
> forwardings whose meanings cannot be known by the UA, the global
> termination of alternative routing can only rarely be correctly
> requested by the UA.

To which Francois replied:
> There are real scenarios where you want to have busy/decline
everywhere.
>=20
> If you call me, and I don't want to take your call at all, I may
> want to send 600 or 603. It is not harmful. That's what I want.
>=20
> I specifically do not want to use 486 or 441 because I do not want
> other devices to continue to ring. This would be particularly
> annoying for people who have both a phone at their desk and a PC
> client.

Here is a clear case when the fork-cancelling property of a 6xx code is
very desirable.  However, there is a related case where it is not.

Consider three salespeople (Alice, Bob and Colin) who each have multiple
devices (desk-phones and soft-clients for example).  If a call arrives
at sip:sales@example.com, it is forked to each salesperson.  The call to
each salesperson is in turn forked to each device.  Now, Alice is busy
with a client, and wishes to hit one button to cancel the call attempt
for both her UAs.  603 is a natural choice, as Francois suggests.  But
because of the problem that Dale describes, the calls to Bob and Colin
are also cancelled.  This is clearly undesirable.

I think that the problem arises because the request-uri is rewritten
multiple times (e.g. from sip:sales@example.com to sip:alice@example.com
to sip:alice-desk-phone@some-ip).  It is far from clear what the scope
of a 6xx code should be.  The description of 6xx codes from RFC3261
Section 21.6 is quite broad:

   6xx responses indicate that a server has definitive information about
   a particular user, not just the particular instance indicated in the
   Request-URI.

I suspect that 6xx codes would work a lot better if this was taken to
refer to the request-uri just prior to the final rewriting.  That is to
say, when Alice's desk-phone rejects a call with 6xx, it is assumed that
it refers to sip:alice@example.com and not any earlier one (such as
sip:sales@example.com).

This could be achieved by saying that 6xx responses propagate back until
they reach a proxy that forked, at which point the cancelling occurs as
expected.  But the forking proxy should map the 6xx code to an
appropriate 4xx code before sending it further upstream.

This approach seems to me to answer both problems raised - it clearly
puts a limit on the scope of a 6xx, whilst still giving a useful action
for a specific user.

Regards,

Michael Procter

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

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



From bliss-bounces@ietf.org Mon Mar 05 12:49:58 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOHJq-0007PB-H0; Mon, 05 Mar 2007 12:49:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOHJp-0007P1-9Z
	for bliss@ietf.org; Mon, 05 Mar 2007 12:49:53 -0500
Received: from zrtps0kp.nortel.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOHJo-0007t3-1h
	for bliss@ietf.org; Mon, 05 Mar 2007 12:49:53 -0500
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l25Hngt13818; Mon, 5 Mar 2007 12:49:42 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [BLISS] I-Ds concerning problems with response codes
Date: Mon, 5 Mar 2007 11:49:25 -0600
Message-ID: <1ECE0EB50388174790F9694F77522CCF0F74993F@zrc2hxm0.corp.nortel.com>
In-Reply-To: <55AF62549C5C4049B13A2A273445C48627A199D0@USNWK101MSX.ww017.siemens.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] I-Ds concerning problems with response codes
Thread-Index: AcdcFrp0HUF5LLyhQ1Se8LZbxCDqNAAE9sQQAMCpb+AABONIwAADKFrg
References: <76431CABEC5EED489807DB8AEBCCA0BCC1D0F2@sea02-mxc01.citel.com>
	<55AF62549C5C4049B13A2A273445C48627A199D0@USNWK101MSX.ww017.siemens.net>
From: "Francois Audet" <audet@nortel.com>
To: "Kucmerowski, Dennis \(Com US\)" <dennis.kucmerowski@siemens.com>,
	"Michael Procter" <michael.procter@citel.com>, <Dale.Worley@comcast.net>,
	<bliss@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: 
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

Dennis and Michael both brought some interesting point, which I agree
with.

To me the core problem is the definition of 6XX in RFC 3261.

I can not imagine anybody that would be foolish enough to have an
implementation=20
that would let a user effectively reject all legs of a call and prevent=20
alternative treatment. It doesn't matter what RFC 3261 says really: the
business
or service provider will do what it needs to do, which may include
retargeting=20
elsewhere (operator, voicemail, etc.).

I believe that what we need is a BCP for this topic, and possibly an
errata
for RFC 3261 if we come to conclusion that there is something
fundamentally wrong
with it.

Cheers

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



From bliss-bounces@ietf.org Mon Mar 05 14:04:15 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOITm-0000gm-OJ; Mon, 05 Mar 2007 14:04:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOITl-0000fe-F4
	for bliss@ietf.org; Mon, 05 Mar 2007 14:04:13 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOITU-0003wK-UR
	for bliss@ietf.org; Mon, 05 Mar 2007 14:04:13 -0500
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-6.cisco.com with ESMTP; 05 Mar 2007 11:03:56 -0800
X-IronPort-AV: i="4.14,251,1170662400"; 
	d="scan'208"; a="118105792:sNHT53170992"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id l25J3tMg027531; 
	Mon, 5 Mar 2007 11:03:55 -0800
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l25J3sa5005424;
	Mon, 5 Mar 2007 19:03:55 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Mar 2007 14:03:44 -0500
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Mar 2007 14:03:44 -0500
Message-ID: <45EC698F.1030603@cisco.com>
Date: Mon, 05 Mar 2007 14:03:43 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
Subject: Re: [BLISS] I-Ds concerning problems with response codes
References: <76431CABEC5EED489807DB8AEBCCA0BCC1D0F2@sea02-mxc01.citel.com>	<55AF62549C5C4049B13A2A273445C48627A199D0@USNWK101MSX.ww017.siemens.net>
	<1ECE0EB50388174790F9694F77522CCF0F74993F@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF0F74993F@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Mar 2007 19:03:44.0782 (UTC)
	FILETIME=[FF44FAE0:01C75F58]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1354; t=1173121435;
	x=1173985435; c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[BLISS]=20I-Ds=20concerning=20problems=20with=20respo
	nse=20codes |Sender:=20;
	bh=uzMw2MvzimcHXaw2cLAi13h4av82WtqEKjT7+5lewOE=;
	b=gBL7WaZXy66jVmSp9BzimQ3xfRrqnBJl0I+BS/DZGCC0BTRbMceAJ8zi+FSAiRoznQkGnoD6
	PL9wknsefnjemMrKSO0cDLpPDDlzlLGcxKhcSeP04SgXTQXU1p3j5mCB;
Authentication-Results: sj-dkim-7; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim7002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
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



Francois Audet wrote:
> Dennis and Michael both brought some interesting point, which I agree
> with.
> 
> To me the core problem is the definition of 6XX in RFC 3261.
> 
> I can not imagine anybody that would be foolish enough to have an
> implementation 
> that would let a user effectively reject all legs of a call and prevent 
> alternative treatment. It doesn't matter what RFC 3261 says really: the
> business
> or service provider will do what it needs to do, which may include
> retargeting 
> elsewhere (operator, voicemail, etc.).

IMO this is strictly a policy issue. If a SP is providing service to me, 
and I want to do this, I see no reason why the SP should prevent me. 
OTOH, a business may not want to give its employees this capability.

If we assume that a UA registered to an AOR is authoritative for the 
AOR, then it should have as much right as the home proxy to reject a 
call. But maybe we should not make that assumption.

I guess that the definition of 6xx handling may be a problem as it 
stands because it effectively prevents a policy of trapping 6xx and 
sending the call to voicemail.

> I believe that what we need is a BCP for this topic, and possibly an
> errata
> for RFC 3261 if we come to conclusion that there is something
> fundamentally wrong
> with it.

Possibly.

	Paul

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



From bliss-bounces@ietf.org Mon Mar 05 14:06:25 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOIVt-0002KU-DL; Mon, 05 Mar 2007 14:06:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOIVs-0002KG-8y
	for bliss@ietf.org; Mon, 05 Mar 2007 14:06:24 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOIVj-0004mt-Df
	for bliss@ietf.org; Mon, 05 Mar 2007 14:06:24 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 05 Mar 2007 14:06:16 -0500
X-IronPort-AV: i="4.14,251,1170651600"; 
	d="scan'208"; a="54072263:sNHT56818176"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l25J6F0b018213; 
	Mon, 5 Mar 2007 14:06:15 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l25J5ma9009576; 
	Mon, 5 Mar 2007 19:06:02 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Mar 2007 14:06:00 -0500
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Mar 2007 14:06:00 -0500
Message-ID: <45EC6A17.6040004@cisco.com>
Date: Mon, 05 Mar 2007 14:05:59 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: "Kucmerowski, Dennis \(Com US\)" <dennis.kucmerowski@siemens.com>
Subject: Re: [BLISS] I-Ds concerning problems with response codes
References: <55AF62549C5C4049B13A2A273445C48627A199D0@USNWK101MSX.ww017.siemens.net>
In-Reply-To: <55AF62549C5C4049B13A2A273445C48627A199D0@USNWK101MSX.ww017.siemens.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Mar 2007 19:06:00.0191 (UTC)
	FILETIME=[4FFAC0F0:01C75F59]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5449; t=1173121575;
	x=1173985575; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[BLISS]=20I-Ds=20concerning=20problems=20with=20respo
	nse=20codes |Sender:=20 |To:=20=22Kucmerowski,
	=20Dennis=20\(Com=20US\)=22=20<dennis.kucmerowski@s
	iemens.com>; bh=PeDdCh8/BdII2heOqkoafTY4WJLmmMKrhjyH7kwo9I4=;
	b=AVza9s52633LxYAjCKzaAUy6jC8k1TgztIUs56s7Li0wmkEv7o2tl/Do693eIQlAIku+24iH
	W3fNcAKc3qn8giMzKH9dBzp6u6FQiyH9VIXMqim9k3ckWfzzQ84krTyw;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
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



Kucmerowski, Dennis (Com US) wrote:
> Francois and Dale,
> 
> In reply to the 6xx to cancel the call.  Very few business will allow an
> employee the capability to cancel/reject a call.  It is not good
> business to take an incoming call whereby the calling party is ringing
> and reject the call which may then return busy tone to the calling
> party. Loss of business. The calling party would go from hearing
> ringback to busy and think someone has answered and then disconnected
> them.  The call party will most likely call again.
> 
> The proper way to handled the call is to redirect to another destination
> e.g., human or voicemail, in order to not lose business.

That's a policy issue, not a protocol issue.

> As for not wishing to listen to ringing; the UA has multiple ways to
> locally handle ringing (e.g., Ringer Off, low volume ringing, ring
> burst, no ringing (audible) when the user is active in a connection,
> etc.

That doesn't solve the problem if there are multiple UAs registered that 
are within hearing distance but not within reach.

	Paul

> Do Not Disturb is another issue and should have an explicit DND response
> (note: 480 is not explicit since 480 can be used for many functions to
> indicate temporary unavailable) so that the originating UA can act on a
> DND in a specific way is needed.
> 
> Reject the call 6xx is the exception case for releasing all multiple
> forked call and not the normal case, once a call is alerting.
> 
> I agree there are cases when forking calls, where releasing a single
> call is needed.
> 
> 
> Best Regards,
>  
> Dennis L. Kucmerowski 
> 
> 561-923-1703
> Systems Engineering
>  
> 
> -----Original Message-----
> From: Michael Procter [mailto:michael.procter@citel.com] 
> Sent: Monday, March 05, 2007 9:38 AM
> To: Francois Audet; Dale.Worley@comcast.net; bliss@ietf.org
> Subject: RE: [BLISS] I-Ds concerning problems with response codes
> 
> Francois, Dale,
> 
> I agree with both of you, but I think there is a problem associated with
> both approaches.  On the one hand, Dale is right when he observes that
> global termination of a call attempt by a UA is almost never correct.
> And on the other, Francois is right when saying that there are
> circumstances when you do want to cancel multiple forks from one UA.
> 
> Dale wrote (in hid 6xx-considered-harmful draft):
>> As the call may have reached the UA through multiple
>> forwardings whose meanings cannot be known by the UA, the global
>> termination of alternative routing can only rarely be correctly
>> requested by the UA.
> 
> To which Francois replied:
>> There are real scenarios where you want to have busy/decline
> everywhere.
>> If you call me, and I don't want to take your call at all, I may
>> want to send 600 or 603. It is not harmful. That's what I want.
>>
>> I specifically do not want to use 486 or 441 because I do not want
>> other devices to continue to ring. This would be particularly
>> annoying for people who have both a phone at their desk and a PC
>> client.
> 
> Here is a clear case when the fork-cancelling property of a 6xx code is
> very desirable.  However, there is a related case where it is not.
> 
> Consider three salespeople (Alice, Bob and Colin) who each have multiple
> devices (desk-phones and soft-clients for example).  If a call arrives
> at sip:sales@example.com, it is forked to each salesperson.  The call to
> each salesperson is in turn forked to each device.  Now, Alice is busy
> with a client, and wishes to hit one button to cancel the call attempt
> for both her UAs.  603 is a natural choice, as Francois suggests.  But
> because of the problem that Dale describes, the calls to Bob and Colin
> are also cancelled.  This is clearly undesirable.
> 
> I think that the problem arises because the request-uri is rewritten
> multiple times (e.g. from sip:sales@example.com to sip:alice@example.com
> to sip:alice-desk-phone@some-ip).  It is far from clear what the scope
> of a 6xx code should be.  The description of 6xx codes from RFC3261
> Section 21.6 is quite broad:
> 
>    6xx responses indicate that a server has definitive information about
>    a particular user, not just the particular instance indicated in the
>    Request-URI.
> 
> I suspect that 6xx codes would work a lot better if this was taken to
> refer to the request-uri just prior to the final rewriting.  That is to
> say, when Alice's desk-phone rejects a call with 6xx, it is assumed that
> it refers to sip:alice@example.com and not any earlier one (such as
> sip:sales@example.com).
> 
> This could be achieved by saying that 6xx responses propagate back until
> they reach a proxy that forked, at which point the cancelling occurs as
> expected.  But the forking proxy should map the 6xx code to an
> appropriate 4xx code before sending it further upstream.
> 
> This approach seems to me to answer both problems raised - it clearly
> puts a limit on the scope of a 6xx, whilst still giving a useful action
> for a specific user.
> 
> Regards,
> 
> Michael Procter
> 
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www1.ietf.org/mailman/listinfo/bliss
> 
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www1.ietf.org/mailman/listinfo/bliss
> 

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



From bliss-bounces@ietf.org Mon Mar 05 14:06:51 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOIWJ-0002SX-Sg; Mon, 05 Mar 2007 14:06:51 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOIWI-0002SK-5w
	for bliss@ietf.org; Mon, 05 Mar 2007 14:06:50 -0500
Received: from zcars04f.nortel.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOIWG-0004w1-Sw
	for bliss@ietf.org; Mon, 05 Mar 2007 14:06:50 -0500
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l25J6if19340; Mon, 5 Mar 2007 14:06:44 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [BLISS] I-Ds concerning problems with response codes
Date: Mon, 5 Mar 2007 13:06:42 -0600
Message-ID: <1ECE0EB50388174790F9694F77522CCF0F749AFC@zrc2hxm0.corp.nortel.com>
In-Reply-To: <45EC698F.1030603@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] I-Ds concerning problems with response codes
Thread-Index: AcdfWQxd3pzvBdluQSabcPEhaH0VJwAAFclQ
References: <76431CABEC5EED489807DB8AEBCCA0BCC1D0F2@sea02-mxc01.citel.com>
	<55AF62549C5C4049B13A2A273445C48627A199D0@USNWK101MSX.ww017.siemens.net>
	<1ECE0EB50388174790F9694F77522CCF0F74993F@zrc2hxm0.corp.nortel.com>
	<45EC698F.1030603@cisco.com>
From: "Francois Audet" <audet@nortel.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
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

Correct. That is my view.=20

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]=20
> Sent: Monday, March 05, 2007 11:04
> To: Audet, Francois (SC100:3055)
> Cc: Kucmerowski, Dennis (Com US); Michael Procter;=20
> Dale.Worley@comcast.net; bliss@ietf.org
> Subject: Re: [BLISS] I-Ds concerning problems with response codes
>=20
>=20
>=20
> Francois Audet wrote:
> > Dennis and Michael both brought some interesting point,=20
> which I agree=20
> > with.
> >=20
> > To me the core problem is the definition of 6XX in RFC 3261.
> >=20
> > I can not imagine anybody that would be foolish enough to have an=20
> > implementation that would let a user effectively reject all=20
> legs of a=20
> > call and prevent alternative treatment. It doesn't matter what RFC=20
> > 3261 says really: the business or service provider will do what it=20
> > needs to do, which may include retargeting elsewhere (operator,=20
> > voicemail, etc.).
>=20
> IMO this is strictly a policy issue. If a SP is providing=20
> service to me, and I want to do this, I see no reason why the=20
> SP should prevent me.=20
> OTOH, a business may not want to give its employees this capability.
>=20
> If we assume that a UA registered to an AOR is authoritative=20
> for the AOR, then it should have as much right as the home=20
> proxy to reject a call. But maybe we should not make that assumption.
>=20
> I guess that the definition of 6xx handling may be a problem=20
> as it stands because it effectively prevents a policy of=20
> trapping 6xx and sending the call to voicemail.
>=20
> > I believe that what we need is a BCP for this topic, and=20
> possibly an=20
> > errata for RFC 3261 if we come to conclusion that there is=20
> something=20
> > fundamentally wrong with it.
>=20
> Possibly.
>=20
> 	Paul
>=20

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



From bliss-bounces@ietf.org Mon Mar 05 15:16:44 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOJbw-0000SP-Nh; Mon, 05 Mar 2007 15:16:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOJbu-0000SG-Vk
	for bliss@ietf.org; Mon, 05 Mar 2007 15:16:42 -0500
Received: from outbound.mailhop.org ([63.208.196.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOJbt-00033k-3n
	for bliss@ietf.org; Mon, 05 Mar 2007 15:16:42 -0500
Received: from 24-107-197-43.dhcp.stls.mo.charter.com ([24.107.197.43]
	helo=[192.168.0.40])
	by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.63) (envelope-from <alan@sipstation.com>)
	id 1HOJbC-0007Ol-OH; Mon, 05 Mar 2007 15:15:59 -0500
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 24.107.197.43
X-Report-Abuse-To: abuse@dyndns.com (see
	http://www.mailhop.org/outbound/abuse.html for abuse reporting
	information)
X-MHO-User: digitalari
Message-ID: <45EC7A7D.5020305@sipstation.com>
Date: Mon, 05 Mar 2007 14:15:57 -0600
From: Alan Johnston <alan@sipstation.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
Subject: Re: [BLISS] I-Ds concerning problems with response codes
References: <76431CABEC5EED489807DB8AEBCCA0BCC1D0F2@sea02-mxc01.citel.com>	<55AF62549C5C4049B13A2A273445C48627A199D0@USNWK101MSX.ww017.siemens.net>
	<1ECE0EB50388174790F9694F77522CCF0F74993F@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF0F74993F@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
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

What is wrong with a 6xx?

When I give SIP tutorials, I say it is what you send to a telemarketer 
when they call.  Do you really want a voicemail from a telemarketer??  
Do you want your other devices to ring??

If UAs are generating 6xx responses and they don't really mean it, then 
that is a problem with the UAs not 3261.

Thanks,
Alan

Francois Audet wrote:
> Dennis and Michael both brought some interesting point, which I agree
> with.
>
> To me the core problem is the definition of 6XX in RFC 3261.
>
> I can not imagine anybody that would be foolish enough to have an
> implementation 
> that would let a user effectively reject all legs of a call and prevent 
> alternative treatment. It doesn't matter what RFC 3261 says really: the
> business
> or service provider will do what it needs to do, which may include
> retargeting 
> elsewhere (operator, voicemail, etc.).
>
> I believe that what we need is a BCP for this topic, and possibly an
> errata
> for RFC 3261 if we come to conclusion that there is something
> fundamentally wrong
> with it.
>
> Cheers
>
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www1.ietf.org/mailman/listinfo/bliss
>
>
>   


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



From bliss-bounces@ietf.org Mon Mar 05 17:29:29 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOLgP-00046X-TW; Mon, 05 Mar 2007 17:29:29 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOKtk-0006mY-NP
	for bliss@ietf.org; Mon, 05 Mar 2007 16:39:12 -0500
Received: from zrtps0kn.nortel.com ([47.140.192.55])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HOKUd-0004WK-UX
	for bliss@ietf.org; Mon, 05 Mar 2007 16:13:48 -0500
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l25LDBw28502; Mon, 5 Mar 2007 16:13:11 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [BLISS] I-Ds concerning problems with response codes
Date: Mon, 5 Mar 2007 15:13:10 -0600
Message-ID: <1ECE0EB50388174790F9694F77522CCF0F749DE5@zrc2hxm0.corp.nortel.com>
In-Reply-To: <45EC7A7D.5020305@sipstation.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] I-Ds concerning problems with response codes
Thread-Index: AcdfYym/eq4OW+9lSvyIautLb47yagAB9isg
References: <76431CABEC5EED489807DB8AEBCCA0BCC1D0F2@sea02-mxc01.citel.com>
	<55AF62549C5C4049B13A2A273445C48627A199D0@USNWK101MSX.ww017.siemens.net>
	<1ECE0EB50388174790F9694F77522CCF0F74993F@zrc2hxm0.corp.nortel.com>
	<45EC7A7D.5020305@sipstation.com>
From: "Francois Audet" <audet@nortel.com>
To: "Alan Johnston" <alan@sipstation.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
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

Yep, I agree.

Again, I think we need a BCP to explain how it is supposed to be used.=20

> -----Original Message-----
> From: Alan Johnston [mailto:alan@sipstation.com]=20
> Sent: Monday, March 05, 2007 12:16
> To: Audet, Francois (SC100:3055)
> Cc: Kucmerowski, Dennis (Com US); Michael Procter;=20
> Dale.Worley@comcast.net; bliss@ietf.org
> Subject: Re: [BLISS] I-Ds concerning problems with response codes
>=20
> What is wrong with a 6xx?
>=20
> When I give SIP tutorials, I say it is what you send to a=20
> telemarketer when they call.  Do you really want a voicemail=20
> from a telemarketer?? =20
> Do you want your other devices to ring??
>=20
> If UAs are generating 6xx responses and they don't really=20
> mean it, then that is a problem with the UAs not 3261.
>=20
> Thanks,
> Alan
>=20
> Francois Audet wrote:
> > Dennis and Michael both brought some interesting point,=20
> which I agree=20
> > with.
> >
> > To me the core problem is the definition of 6XX in RFC 3261.
> >
> > I can not imagine anybody that would be foolish enough to have an=20
> > implementation that would let a user effectively reject all=20
> legs of a=20
> > call and prevent alternative treatment. It doesn't matter what RFC=20
> > 3261 says really: the business or service provider will do what it=20
> > needs to do, which may include retargeting elsewhere (operator,=20
> > voicemail, etc.).
> >
> > I believe that what we need is a BCP for this topic, and=20
> possibly an=20
> > errata for RFC 3261 if we come to conclusion that there is=20
> something=20
> > fundamentally wrong with it.
> >
> > Cheers
> >
> > _______________________________________________
> > BLISS mailing list
> > BLISS@ietf.org
> > https://www1.ietf.org/mailman/listinfo/bliss
> >
> >
> >  =20
>=20
>=20

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



From bliss-bounces@ietf.org Mon Mar 05 18:23:42 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOMWs-0003eh-Ej; Mon, 05 Mar 2007 18:23:42 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOMWq-0003eZ-RY
	for bliss@ietf.org; Mon, 05 Mar 2007 18:23:40 -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 1HOMWp-00018M-Fe
	for bliss@ietf.org; Mon, 05 Mar 2007 18:23:40 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by sj-iport-3.cisco.com with ESMTP; 05 Mar 2007 15:23:39 -0800
X-IronPort-AV: i="4.14,252,1170662400"; 
	d="scan'208"; a="468560702:sNHT56679404"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l25NNc8k030365; 
	Mon, 5 Mar 2007 18:23:38 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l25NNcZn013896; 
	Mon, 5 Mar 2007 23:23:38 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Mar 2007 18:23:37 -0500
Received: from [161.44.174.118] ([161.44.174.118]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Mar 2007 18:23:37 -0500
Message-ID: <45ECA678.6060801@cisco.com>
Date: Mon, 05 Mar 2007 18:23:36 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Alan Johnston <alan@sipstation.com>
Subject: Re: [BLISS] I-Ds concerning problems with response codes
References: <76431CABEC5EED489807DB8AEBCCA0BCC1D0F2@sea02-mxc01.citel.com>	<55AF62549C5C4049B13A2A273445C48627A199D0@USNWK101MSX.ww017.siemens.net>	<1ECE0EB50388174790F9694F77522CCF0F74993F@zrc2hxm0.corp.nortel.com>
	<45EC7A7D.5020305@sipstation.com>
In-Reply-To: <45EC7A7D.5020305@sipstation.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Mar 2007 23:23:37.0681 (UTC)
	FILETIME=[4D5C8C10:01C75F7D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2139; t=1173137018;
	x=1174001018; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[BLISS]=20I-Ds=20concerning=20problems=20with=20respo
	nse=20codes |Sender:=20
	|To:=20Alan=20Johnston=20<alan@sipstation.com>;
	bh=cPXkN7vXSpMXrlYnMemqW4LztKNsCYqASbANQ31SkDU=;
	b=ZvT6DA8Stu5KILs9JcT6OwqCCogkrlwMlWveQDTDz2IY6/n6tjYMhzVI5TW+RxqocTHoN8rT
	X53XOlnYI1aka9sdAzgvdLFsaTKDy3qtWrutvvJbt7fFUbrppfhly+OE;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
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



Alan Johnston wrote:
> What is wrong with a 6xx?
> 
> When I give SIP tutorials, I say it is what you send to a telemarketer 
> when they call.  Do you really want a voicemail from a telemarketer??  
> Do you want your other devices to ring??
> 
> If UAs are generating 6xx responses and they don't really mean it, then 
> that is a problem with the UAs not 3261.

I don't think there is anything wrong with 6xx. But what might be wrong 
is that no latitude is given to a proxy to consider or try other 
alternatives once a 6xx is received. There seems to be a justified need 
for a proxy to have some policy control in this regard. In some cases 
each and every UA may be allowed to have the last word, but not in all 
cases.

In particular, when a proxy is authoritative for an AOR, and chooses to 
translate and forward, it should have the discretionary authority to 
ignore the 6xx and try something else if it wishes. In some cases the 
proxy may trump the UA, and in other cases it may not.

	Paul

> Thanks,
> Alan
> 
> Francois Audet wrote:
>> Dennis and Michael both brought some interesting point, which I agree
>> with.
>>
>> To me the core problem is the definition of 6XX in RFC 3261.
>>
>> I can not imagine anybody that would be foolish enough to have an
>> implementation that would let a user effectively reject all legs of a 
>> call and prevent alternative treatment. It doesn't matter what RFC 
>> 3261 says really: the
>> business
>> or service provider will do what it needs to do, which may include
>> retargeting elsewhere (operator, voicemail, etc.).
>>
>> I believe that what we need is a BCP for this topic, and possibly an
>> errata
>> for RFC 3261 if we come to conclusion that there is something
>> fundamentally wrong
>> with it.
>>
>> Cheers
>>
>> _______________________________________________
>> BLISS mailing list
>> BLISS@ietf.org
>> https://www1.ietf.org/mailman/listinfo/bliss
>>
>>
>>   
> 
> 
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www1.ietf.org/mailman/listinfo/bliss
> 

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



From bliss-bounces@ietf.org Mon Mar 05 21:55:22 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOPpb-0003zm-Pk; Mon, 05 Mar 2007 21:55:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOPpa-0003z7-V1
	for bliss@ietf.org; Mon, 05 Mar 2007 21:55:14 -0500
Received: from usaga01-in.huawei.com ([206.16.17.211])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOPpZ-0005w4-NW
	for bliss@ietf.org; Mon, 05 Mar 2007 21:55:14 -0500
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JEG00L0NO401Q@usaga01-in.huawei.com> for
	bliss@ietf.org; Mon, 05 Mar 2007 18:55:13 -0800 (PST)
Received: from s73602 (cpe-72-190-0-23.tx.res.rr.com [72.190.0.23])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with ESMTPA id <0JEG00B10O3Z50@usaga01-in.huawei.com> for
	bliss@ietf.org; Mon, 05 Mar 2007 18:55:12 -0800 (PST)
Date: Mon, 05 Mar 2007 20:54:31 -0600
From: Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Re: [BLISS] I-Ds concerning problems with response codes
To: bliss@ietf.org
Message-id: <004801c75f9a$c3f2a590$6401a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
Content-type: text/plain; format=flowed; charset=iso-8859-1;
	reply-type=response
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <76431CABEC5EED489807DB8AEBCCA0BCC1D0F2@sea02-mxc01.citel.com>
	<55AF62549C5C4049B13A2A273445C48627A199D0@USNWK101MSX.ww017.siemens.net>
	<1ECE0EB50388174790F9694F77522CCF0F74993F@zrc2hxm0.corp.nortel.com>
	<45EC7A7D.5020305@sipstation.com> <45ECA678.6060801@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
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

Hi, Paul,

From: "Paul Kyzivat" <pkyzivat@cisco.com>

> Alan Johnston wrote:
>> What is wrong with a 6xx?
>> 
>> When I give SIP tutorials, I say it is what you send to a telemarketer 
>> when they call.  Do you really want a voicemail from a telemarketer??  
>> Do you want your other devices to ring??
>> 
>> If UAs are generating 6xx responses and they don't really mean it, then 
>> that is a problem with the UAs not 3261.
> 
> I don't think there is anything wrong with 6xx. But what might be wrong 
> is that no latitude is given to a proxy to consider or try other 
> alternatives once a 6xx is received. There seems to be a justified need 
> for a proxy to have some policy control in this regard. In some cases 
> each and every UA may be allowed to have the last word, but not in all 
> cases.
> 
> In particular, when a proxy is authoritative for an AOR, and chooses to 
> translate and forward, it should have the discretionary authority to 
> ignore the 6xx and try something else if it wishes. In some cases the 
> proxy may trump the UA, and in other cases it may not.
> 
> Paul

Yeah, where the answer is "it depends", a BCP would help a lot!

Thanks,

Spencer


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



From bliss-bounces@ietf.org Tue Mar 06 01:08:21 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOSqC-0000WT-CY; Tue, 06 Mar 2007 01:08:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOSqA-0000WE-Ev; Tue, 06 Mar 2007 01:08:02 -0500
Received: from tcmail31.telekom.de ([217.6.95.238])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HOSq7-0003QY-Pa; Tue, 06 Mar 2007 01:08:02 -0500
Received: from S4DE8PSAANQ.mitte.t-com.de by tcmail31.telekom.de with ESMTP;
	Tue, 6 Mar 2007 07:07:51 +0100
Received: from S4DE8PSAAGO.mitte.t-com.de ([10.151.180.14]) by
	S4DE8PSAANQ.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 Mar 2007 07:07:33 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 6 Mar 2007 07:07:33 +0100
Message-Id: <85108216918A984C8C60172D7C84770A011EF71B@S4DE8PSAAGO.mitte.t-com.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draf draft-poetzl-sipping-call-completion-02.txt: now available
Thread-Index: AcdftbqTXozlXpeyRpywAZW7M60QXA==
From: "Jesske, R" <R.Jesske@t-com.net>
To: <bliss@ietf.org>,
    <sipping@ietf.org>
X-OriginalArrivalTime: 06 Mar 2007 06:07:33.0768 (UTC)
	FILETIME=[BB31F080:01C75FB5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1
Cc: esasaki@NTT-AT.COM, "Alexeitsev, D" <D.Alexeitsev@t-com.net>,
	Martin.Huelsemann@gmx.de, "Huelsemann,
	Martin" <Martin.Huelsemann@t-com.net>
Subject: [BLISS] draf draft-poetzl-sipping-call-completion-02.txt: now
	available
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>
Content-Type: multipart/mixed; boundary="===============1656496032=="
Errors-To: bliss-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1656496032==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C75FB5.BACB1D31"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C75FB5.BACB1D31
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear all,
The draft draft-poetzl-sipping-call-completion-02.txt is now available.

http://tools.ietf.org/wg/sipping/draft-poetzl-sipping-call-completion-02.=
txt

We would be happy about comments and discussion

Best Regards

Roland


Deutsche Telekom AG
T-Com, Zentrum Technik Einf=FChrung
Roland Jesske
Gateways, Protokolle, Konvergenz, TE33-6
Deutsche-Telekom-Allee 1, 64295 Darmstadt, Raum 314(Besucheradresse)
Postfach, 64307 Darmstadt (Postanschrift)
06151 83-5940 (Tel.)
06151 83-4577 (Fax)
E-Mail: r.jesske@t-com.net
http://www.t-com.de

Registerrechtliche Unternehmensangaben:
Deutsche Telekom AG
Aufsichtsrat: Dr. Klaus Zumwinkel (Vorsitzender)
Vorstand: Ren=E9 Obermann (Vorsitzender),=20
Dr. Karl-Gerhard Eick (stellvertretender Vorsitzender),
Hamid Akhavan, Timotheus H=F6ttges, Lothar Pauly
Handelsregister: Amtsgericht Bonn HRB 6794,
Sitz der Gesellschaft: Bonn
WEEE-Reg.-Nr.: DE50478376
***************************************************************
Deutsche Telekom AG
Supervisory Board: Dr. Klaus Zumwinkel (Chairman)
Board of Management: Ren=E9 Obermann (Chairman),=20
Dr. Karl-Gerhard Eick (Deputy Chairman),
Hamid Akhavan, Timotheus H=F6ttges, Lothar Pauly
Commercial register: Amtsgericht Bonn HRB 6794,
corporate seat: Bonn
WEEEreg.no: DE50478376


------_=_NextPart_001_01C75FB5.BACB1D31
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7651.59">
<TITLE>draf draft-poetzl-sipping-call-completion-02.txt: now =
available</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Dear all,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">The draft =
draft-poetzl-sipping-call-completion-02.txt is now available.</FONT>
</P>

<P><A =
HREF=3D"http://tools.ietf.org/wg/sipping/draft-poetzl-sipping-call-comple=
tion-02.txt"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://tools.ietf.org/wg/sipping/draft-poetzl-sipping-call=
-completion-02.txt</FONT></U></A>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">We would be happy about comments and =
discussion</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Best Regards</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Roland</FONT>
</P>
<BR>

<P><FONT SIZE=3D1 FACE=3D"Arial">Deutsche Telekom AG</FONT>

<BR><FONT SIZE=3D1 FACE=3D"Arial">T-Com, Zentrum Technik =
Einf=FChrung</FONT>

<BR><FONT SIZE=3D1 FACE=3D"Arial">Roland Jesske</FONT>

<BR><FONT SIZE=3D1 FACE=3D"Arial">Gateways, Protokolle, Konvergenz, =
TE33-6</FONT>

<BR><FONT SIZE=3D1 FACE=3D"Arial">Deutsche-Telekom-Allee 1, 64295 =
Darmstadt, Raum 314(Besucheradresse)</FONT>

<BR><FONT SIZE=3D1 FACE=3D"Arial">Postfach, 64307 Darmstadt =
(Postanschrift)</FONT>

<BR><FONT SIZE=3D1 FACE=3D"Arial">06151 83-5940 (Tel.)</FONT>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D1 FACE=3D"Arial">06151 83-4577 =
(Fax)</FONT></SPAN><SPAN LANG=3D"de"></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D1 FACE=3D"Arial">E-Mail: =
r.jesske@t-com.net</FONT></SPAN>

<BR><SPAN LANG=3D"fr"></SPAN><A HREF=3D"http://www.t-com.de"><SPAN =
LANG=3D"fr"><U><FONT COLOR=3D"#0000FF" SIZE=3D1 =
FACE=3D"Arial">http://www.t-com.de</FONT></U></SPAN></A><SPAN =
LANG=3D"fr"></SPAN><SPAN LANG=3D"de"></SPAN><SPAN =
LANG=3D"de"></SPAN><SPAN LANG=3D"de"><BR>
</SPAN><SPAN LANG=3D"de"><U></U><U></U><U></U></SPAN>

<BR><SPAN LANG=3D"de"><U><FONT SIZE=3D1 =
FACE=3D"Arial">Registerrechtliche Unternehmensangaben:</FONT></U></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D1 FACE=3D"Arial">Deutsche Telekom =
AG<BR>
Aufsichtsrat: Dr. Klaus Zumwinkel (Vorsitzender)<BR>
Vorstand: Ren=E9 Obermann (Vorsitzender),<BR>
Dr. Karl-Gerhard Eick (stellvertretender Vorsitzender),<BR>
Hamid Akhavan, Timotheus H=F6ttges, Lothar Pauly<BR>
Handelsregister: Amtsgericht Bonn HRB 6794,</FONT></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D1 FACE=3D"Arial">Sitz der =
Gesellschaft: Bonn</FONT></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D1 FACE=3D"Arial">WEEE-Reg.-Nr.: =
DE50478376</FONT></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D1 =
FACE=3D"Arial">**********************************************************=
*****</FONT></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D1 FACE=3D"Arial">Deutsche Telekom =
AG</FONT></SPAN>

<BR><SPAN LANG=3D"en-gb"><FONT SIZE=3D1 FACE=3D"Arial">Supervisory =
Board: Dr. Klaus Zumwinkel (Chairman)</FONT></SPAN>

<BR><SPAN LANG=3D"en-gb"><FONT SIZE=3D1 FACE=3D"Arial">Board of =
Management: Ren=E9 Obermann (Chairman), </FONT></SPAN>

<BR><SPAN LANG=3D"en-gb"><FONT SIZE=3D1 FACE=3D"Arial">Dr. Karl-Gerhard =
Eick (Deputy Chairman),</FONT></SPAN>

<BR><SPAN LANG=3D"en-gb"><FONT SIZE=3D1 FACE=3D"Arial">Hamid Akhavan, =
Timotheus H=F6ttges, Lothar Pauly</FONT></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D1 FACE=3D"Arial">Commercial register: =
Amtsgericht Bonn HRB 6794,</FONT></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D1 FACE=3D"Arial">corporate seat: =
Bonn</FONT></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D1 FACE=3D"Arial">WEEEreg.no: =
DE50478376</FONT></SPAN>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C75FB5.BACB1D31--


--===============1656496032==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1656496032==--




From bliss-bounces@ietf.org Tue Mar 06 11:52:50 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOcuA-0002Zq-Bl; Tue, 06 Mar 2007 11:52:50 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOcu9-0002Zl-D9
	for bliss@ietf.org; Tue, 06 Mar 2007 11:52:49 -0500
Received: from rwcrmhc14.comcast.net ([216.148.227.154])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HOcu8-0003mh-1G
	for bliss@ietf.org; Tue, 06 Mar 2007 11:52:49 -0500
Received: from dragon.ariadne.com (failure[24.34.79.42])
	by comcast.net (rwcrmhc14) with ESMTP
	id <20070306165225m1400g0hpde>; Tue, 6 Mar 2007 16:52:42 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l26Gq16f002822
	for <bliss@ietf.org>; Tue, 6 Mar 2007 11:52:01 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l26Gq1Yk002818;
	Tue, 6 Mar 2007 11:52:01 -0500
Date: Tue, 6 Mar 2007 11:52:01 -0500
Message-Id: <200703061652.l26Gq1Yk002818@dragon.ariadne.com>
To: bliss@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <1ECE0EB50388174790F9694F77522CCF0F67A4CB@zrc2hxm0.corp.nortel.com>
	(audet@nortel.com)
Subject: Re: [BLISS] I-Ds concerning problems with response codes
References: <200703011531.l21FVQZn018306@dragon.ariadne.com>
	<1ECE0EB50388174790F9694F77522CCF0F67A4CB@zrc2hxm0.corp.nortel.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
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

Let me construct a slightly elaborate, but as far as I can tell,
completely realistic use case.

I, <sip:Dale.Worley@comcast.net> call a call distributor
<sip:my-friends@example.com>.  my-friends serial forks in random
order to a series of URIs.  In this case, the first is
<sip:audet@nortel.com> and the second is <michael.procter@citel.com>.

When the first fork reaches the proxy for nortel.com, it parallel
forks to your two user agents, <sip:10.1.1.1> and <sip:10.2.2.2>.
There is also a lower-priority contact, <sip:audet@192.168.0.0>, which
is a voicemail automaton.

So <sip:10.1.1.1> and <sip:10.2.2.2> start ringing, and you wish to
decline on sip:10.1.1.1.  This can have several meanings, each with
different implications:

1. You wish for <sip:10.1.1.1> to stop ringing, but for processing to
   continue elsewhere.  This can be accomplished by the UA just not
   ringing.  This has no protocol effect.

2. You wish for <sip:10.1.1.1> to stop ringing, but for processing to
   continue elsewhere immediately.  For this, the UA has to send a 4xx
   response.  There is no specific "Decline Here" response, although
   480 has a similar meaning.

3. You wish for <sip:10.1.1.1> and <sip:10.2.2.2> to stop ringing,
   thus causing the fork to the voicemail server to ring.

4. You wish for <sip:10.1.1.1> and <sip:10.2.2.2> to stop ringing, and
   for the call to not go to voicemail, which means that it will then
   continue with ringing <michael.procter@citel.com>.

5. You wish to terminate all forks of the call everywhere.  This can
   be accomplished with a 603 response.

These are all effects that you might want to achieve.  1, 2, and 5 can
be done with SIP as it currently stands.  (Note that effect 5 is the
*specified* effect of any 6xx response, and though a proxy can violate
that specification in a nearly-transparent manner, it would be good to
document that that deviation is considered acceptable.)  (In regard to
2, I object that "this call was specifically rejected" is not within
the defined meanings of 480, and would like to see a specific "Decline
Here" response code, but that's a smaller issue.)

Interestingly, effect 5 *should not* be achievable -- You are not
authoritative for calls to Michael, and you have no right to terminate
the forks of my call to his UA.

3 and 4, the most desirable and reasonable "reject" effects, simply
cannot be achieved under RFC 3261.

What I'm trying to establish is:

1. Consensus that the defined effect of 6xx is not a good idea,
   because of the authority problem in case 5.

2. Consensus that proxies should, by default, treat 6xx as 4xx, and
   translate them into 4xx in their upstream responses (to prevent
   upstream proxies that conform to RFC 3261 from having the authority
   problem).

3. Establish a proper 4xx translation of 603, either by defining a new
   code (e.g. 441) or enlarging the definition of 480.

4. Start discussion on how to provide a properly scoped "non-local
   decline" response.  (draft-rajesh-sipping-605-01 is an approach to
   this issue.)

And it turns out that the "non-local decline" issue is more
complicated than it appears -- it's not at all clear (in the face of
the messy routing that SIP makes possible) how to reliably determine
when a response should be treated as having authority over a
particular forking transaction.

Dale

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



From bliss-bounces@ietf.org Tue Mar 06 13:18:07 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOeEa-00064O-Qn; Tue, 06 Mar 2007 13:18:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOeEZ-00063o-DU
	for bliss@ietf.org; Tue, 06 Mar 2007 13:17:59 -0500
Received: from zrtps0kn.nortel.com ([47.140.192.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOeEZ-0000D2-2v
	for bliss@ietf.org; Tue, 06 Mar 2007 13:17:59 -0500
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l26IHtE23905; Tue, 6 Mar 2007 13:17:55 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [BLISS] I-Ds concerning problems with response codes
Date: Tue, 6 Mar 2007 12:17:52 -0600
Message-ID: <1ECE0EB50388174790F9694F77522CCF0F799676@zrc2hxm0.corp.nortel.com>
In-Reply-To: <200703061652.l26Gq1Yk002818@dragon.ariadne.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] I-Ds concerning problems with response codes
Thread-Index: AcdgD+V+WpN1GNLVRMWErPVMaSsWEgACS4Gg
References: <200703011531.l21FVQZn018306@dragon.ariadne.com>
	<1ECE0EB50388174790F9694F77522CCF0F67A4CB@zrc2hxm0.corp.nortel.com>
	<200703061652.l26Gq1Yk002818@dragon.ariadne.com>
From: "Francois Audet" <audet@nortel.com>
To: <Dale.Worley@comcast.net>, <bliss@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Cc: 
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

Hi Dale, you did a good job. I think we are going somewhere.

> -----Original Message-----
> From: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net]=20
> Sent: Tuesday, March 06, 2007 08:52
> To: bliss@ietf.org
> Subject: Re: [BLISS] I-Ds concerning problems with response codes
>=20
> Let me construct a slightly elaborate, but as far as I can=20
> tell, completely realistic use case.
>=20
> I, <sip:Dale.Worley@comcast.net> call a call distributor=20
> <sip:my-friends@example.com>.  my-friends serial forks in=20
> random order to a series of URIs.  In this case, the first is=20
> <sip:audet@nortel.com> and the second is <michael.procter@citel.com>.
>=20
> When the first fork reaches the proxy for nortel.com, it=20
> parallel forks to your two user agents, <sip:10.1.1.1> and=20
> <sip:10.2.2.2>.
> There is also a lower-priority contact,=20
> <sip:audet@192.168.0.0>, which is a voicemail automaton.

This is ONE way to implement voicemail. Probably the simplest and
best way when living in a uniform SIP environment.

However, voicemail is often done differently. Often, sessions
are retargeted to a voicemail server (as opposed to forked to
voicemail). And the mailbox are then derived from "redirection
number information", such as that available from History-Info
(RFC 4244) or from the URI itself (RFC 4458, RFC 4240). This
is extremely common when you have to deal with legacy voicemail
systems through PSTN gateways (but is not limited to that).

This explains a bit why some implementations have been=20
relying of 603.

> So <sip:10.1.1.1> and <sip:10.2.2.2> start ringing, and you=20
> wish to decline on sip:10.1.1.1.  This can have several=20
> meanings, each with different implications:
>=20
> 1. You wish for <sip:10.1.1.1> to stop ringing, but for processing to
>    continue elsewhere.  This can be accomplished by the UA just not
>    ringing.  This has no protocol effect.

Yes, valid case. I call this the "Ignore" function.

> 2. You wish for <sip:10.1.1.1> to stop ringing, but for processing to
>    continue elsewhere immediately.  For this, the UA has to send a 4xx
>    response.  There is no specific "Decline Here" response, although
>    480 has a similar meaning.

Correct. This is a "Decline local" (and I really don't see a reason
for anything but 480).

>=20
> 3. You wish for <sip:10.1.1.1> and <sip:10.2.2.2> to stop ringing,
>    thus causing the fork to the voicemail server to ring.

Correct. Depending on your reading of 603 in RFC 3261, it may or may
not be usable for this purpose. This would also depends on the way
your voicemail is set up.

With your description (forked voicemail server), it wouldn't work.=20
Behavior 4 would happen instead.

> 4. You wish for <sip:10.1.1.1> and <sip:10.2.2.2> to stop ringing, and
>    for the call to not go to voicemail, which means that it will then
>    continue with ringing <michael.procter@citel.com>.

Yes, that is interesting. Especially if Michael is the Enterprise's=20
operator. That could be quite useful.

As per my comment on 3, depending how voicemail is implemented and your
reading of 603, this may or may not be the result.

> 5. You wish to terminate all forks of the call everywhere.  This can
>    be accomplished with a 603 response.

That depends on your reading of 3261.

> These are all effects that you might want to achieve.  1, 2,=20
> and 5 can be done with SIP as it currently stands.  (Note=20
> that effect 5 is the
> *specified* effect of any 6xx response, and though a proxy=20
> can violate that specification in a nearly-transparent=20
> manner, it would be good to document that that deviation is=20
> considered acceptable.)  (In regard to 2, I object that "this=20
> call was specifically rejected" is not within the defined=20
> meanings of 480, and would like to see a specific "Decline=20
> Here" response code, but that's a smaller issue.)
>=20
> Interestingly, effect 5 *should not* be achievable -- You are=20
> not authoritative for calls to Michael, and you have no right=20
> to terminate the forks of my call to his UA.

I don't think that's the conclusion. I think Paul said it best
when he said it was policy.

If my service provider is OK with a "Decline (really) everywhere"
behavior, then it's fine.

But the service provider could decide he's not and provide alternative
treatment. Policy decisions.

> 3 and 4, the most desirable and reasonable "reject" effects,=20
> simply cannot be achieved under RFC 3261.
>=20
> What I'm trying to establish is:
>=20
> 1. Consensus that the defined effect of 6xx is not a good idea,
>    because of the authority problem in case 5.

As above, I think we need to clarify it's a policy issue.

> 2. Consensus that proxies should, by default, treat 6xx as 4xx, and
>    translate them into 4xx in their upstream responses (to prevent
>    upstream proxies that conform to RFC 3261 from having the authority
>    problem).
>=20
> 3. Establish a proper 4xx translation of 603, either by defining a new
>    code (e.g. 441) or enlarging the definition of 480.

I think 480 is already enlarged to be honest.

> 4. Start discussion on how to provide a properly scoped "non-local
>    decline" response.  (draft-rajesh-sipping-605-01 is an approach to
>    this issue.)

Yes, I like this draft too.

It basically does the following:
- 603 =3D=3D "my" reading of RFC 3261, i.e., "Decline fork"
- 605 =3D=3D "your" reading of RFC 3261, i.e., "Decline really =
everywhere"

> And it turns out that the "non-local decline" issue is more=20
> complicated than it appears -- it's not at all clear (in the=20
> face of the messy routing that SIP makes possible) how to=20
> reliably determine when a response should be treated as=20
> having authority over a particular forking transaction.

Agreed.

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



From bliss-bounces@ietf.org Wed Mar 07 04:03:44 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOs3N-0003Na-Fr; Wed, 07 Mar 2007 04:03:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOaSV-0007Ha-KQ; Tue, 06 Mar 2007 09:16:07 -0500
Received: from tcmail23.telekom.de ([217.6.95.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HOaST-0002Gp-6f; Tue, 06 Mar 2007 09:16:07 -0500
Received: from S4DE9JSAANO.ost.t-com.de (S4DE9JSAANO.ost.t-com.de
	[10.125.177.105]) by tcmail21.telekom.de with ESMTP;
	Tue, 6 Mar 2007 15:15:13 +0100
Received: from S4DE9JSAAIG.ost.t-com.de ([10.125.177.192]) by
	S4DE9JSAANO.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 Mar 2007 15:14:54 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 6 Mar 2007 15:14:53 +0100
Message-Id: <1E4CCB2441C5C0409AD8A929482A09F31BB764@S4DE9JSAAIG.ost.t-com.de>
In-Reply-To: <85108216918A984C8C60172D7C84770A011EF71B@S4DE8PSAAGO.mitte.t-com.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] draf draft-poetzl-sipping-call-completion-02.txt;
	queue-operation
Thread-Index: AcdftbqTXozlXpeyRpywAZW7M60QXAAQbyew
From: "Beck01, Wolfgang" <BeckW@t-systems.com>
To: <bliss@ietf.org>,
    <sipping@ietf.org>
X-OriginalArrivalTime: 06 Mar 2007 14:14:54.0029 (UTC)
	FILETIME=[CFBFAFD0:01C75FF9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
X-Mailman-Approved-At: Tue, 06 Mar 2007 21:25:09 -0500
Cc: esasaki@NTT-AT.COM, Martin.Huelsemann@gmx.de
Subject: [BLISS] AW: [Sipping] draf
	draft-poetzl-sipping-call-completion-02.txt; queue-operation
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

Roland,

is the queue-operation parameter really necessary?
'add' is just a synonym for a SUBSCRIBE with an Expire > 0

The 'suspend' / 'resume' functionality can be done by the calling UA: it
can ignore ('suspend') or handle ('resume') incoming NOTIFYs.

What's the point of the 'caller' parameter? The SUBSCRIBE request =
already
contains 'From' and possibly P-Asserted-Id.=20

Aren't the 'short-term-denial' and 'long-term-denial' parameters already
covered by existing SIP response codes?


Wolfgang


[non-standard sig as required by dubious EU regulations]
--
T-Systems Enterprise Services GmbH
Aufsichtsrat: Ren=E9 Obermann (Vorsitzender)
Executive Committee: Lothar Pauly (Vorsitzender)*, Helmut Binder, Albert =
Henn, Olaf Heyden*, Katrin Horstmann, Ulrich Kemp, Axel Knobe*,
Wilfried Peters*, Dr. Herbert Schaaff*, Zvezdana Seeger*
Handelsregister: Amtsgericht Frankfurt am Main HRB 55933
Sitz der Gesellschaft: Frankfurt am Main
WEEE-Reg.-Nr. DE87523644
*Gesch=E4ftsf=FChrer gem. =A7 35 GmbHG

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



From bliss-bounces@ietf.org Wed Mar 07 04:03:50 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOs3N-0003NU-Ad; Wed, 07 Mar 2007 04:03:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOVAj-0008Ry-QG
	for bliss@ietf.org; Tue, 06 Mar 2007 03:37:25 -0500
Received: from mail.exchange.microsoft.com ([131.107.1.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOV28-0005Wj-Sf
	for bliss@ietf.org; Tue, 06 Mar 2007 03:28:34 -0500
Received: from df-bhd-02.exchange.corp.microsoft.com (157.54.71.211) by
	DF-GWY-07.exchange.corp.microsoft.com (157.54.63.164) with Microsoft
	SMTP Server (TLS) id 8.0.685.24; Tue, 6 Mar 2007 00:28:32 -0800
Received: from DF-COLLIE-MSG.exchange.corp.microsoft.com ([10.255.255.1]) by
	df-bhd-02.exchange.corp.microsoft.com ([157.54.71.211]) with mapi;
	Tue, 6 Mar 2007 00:28:32 -0800
From: Sriram Parameswar <Sriram.Parameswar@microsoft.com>
To: "bliss@ietf.org" <bliss@ietf.org>
Date: Tue, 6 Mar 2007 00:28:30 -0800
Subject: Re: [BLISS] I-Ds concerning problems with response codes
Thread-Topic: [BLISS] I-Ds concerning problems with response codes
Thread-Index: AcdfmuzOQ77ieIrRSselsSZB91Y42AALeuHw
Message-ID: <EB9237EDF079AA4C9462B2ABC5D571647B5F34F1CE@DF-COLLIE-MSG.exchange.corp.microsoft.com>
References: <E1HOPpc-0003zv-Tz@megatron.ietf.org>
In-Reply-To: <E1HOPpc-0003zv-Tz@megatron.ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
X-Mailman-Approved-At: Tue, 06 Mar 2007 21:25:18 -0500
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

I agree with Francois that there is a problem with the way 6xx is currently=
 defined in 3261. We have a draft (in SIPPING) that aims to clarify the dif=
ference between cancelling all branches and cancelling all current branches=
 while allowing for serial forking (i.e. route call to voicemail or team et=
c.)

Till it appears in the archive you may find a copy here:

http://home.comcast.net/~sriramkp/Drafts/draft-rajesh-sipping-605-01.txt

Thanks and looking forward to continuing this discussion in SIPPING (or her=
e if you prefer).

Thanks,

Sriram



----------------------------------------------------------------------

Message: 1
Date: Mon, 05 Mar 2007 20:54:31 -0600
From: Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Re: [BLISS] I-Ds concerning problems with response codes
To: bliss@ietf.org
Message-ID: <004801c75f9a$c3f2a590$6401a8c0@china.huawei.com>
Content-Type: text/plain; format=3Dflowed; charset=3Diso-8859-1;
        reply-type=3Dresponse

Hi, Paul,

From: "Paul Kyzivat" <pkyzivat@cisco.com>

> Alan Johnston wrote:
>> What is wrong with a 6xx?
>>
>> When I give SIP tutorials, I say it is what you send to a telemarketer
>> when they call.  Do you really want a voicemail from a telemarketer??
>> Do you want your other devices to ring??
>>
>> If UAs are generating 6xx responses and they don't really mean it, then
>> that is a problem with the UAs not 3261.
>
> I don't think there is anything wrong with 6xx. But what might be wrong
> is that no latitude is given to a proxy to consider or try other
> alternatives once a 6xx is received. There seems to be a justified need
> for a proxy to have some policy control in this regard. In some cases
> each and every UA may be allowed to have the last word, but not in all
> cases.
>
> In particular, when a proxy is authoritative for an AOR, and chooses to
> translate and forward, it should have the discretionary authority to
> ignore the 6xx and try something else if it wishes. In some cases the
> proxy may trump the UA, and in other cases it may not.
>
> Paul

Yeah, where the answer is "it depends", a BCP would help a lot!

Thanks,

Spencer




------------------------------

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


End of BLISS Digest, Vol 3, Issue 13
************************************

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



From bliss-bounces@ietf.org Wed Mar 07 10:38:14 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOyDW-0008EM-R0; Wed, 07 Mar 2007 10:38:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOyDV-0008AH-Bv
	for bliss@ietf.org; Wed, 07 Mar 2007 10:38:13 -0500
Received: from alnrmhc12.comcast.net ([204.127.225.92])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOyDU-0002PN-2d
	for bliss@ietf.org; Wed, 07 Mar 2007 10:38:13 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (alnrmhc12) with ESMTP
	id <20070307153809b1200nnb9re>; Wed, 7 Mar 2007 15:38:10 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l27Fc96f005675
	for <bliss@ietf.org>; Wed, 7 Mar 2007 10:38:09 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l27Fc9Ci005671;
	Wed, 7 Mar 2007 10:38:09 -0500
Date: Wed, 7 Mar 2007 10:38:09 -0500
Message-Id: <200703071538.l27Fc9Ci005671@dragon.ariadne.com>
To: bliss@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <1ECE0EB50388174790F9694F77522CCF0F799676@zrc2hxm0.corp.nortel.com>
	(audet@nortel.com)
Subject: Re: [BLISS] I-Ds concerning problems with response codes
References: <200703011531.l21FVQZn018306@dragon.ariadne.com>
	<1ECE0EB50388174790F9694F77522CCF0F67A4CB@zrc2hxm0.corp.nortel.com>
	<200703061652.l26Gq1Yk002818@dragon.ariadne.com>
	<1ECE0EB50388174790F9694F77522CCF0F799676@zrc2hxm0.corp.nortel.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
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

Some initial comments:

   From: "Francois Audet" <audet@nortel.com>

   However, voicemail is often done differently. Often, sessions
   are retargeted to a voicemail server (as opposed to forked to
   voicemail). And the mailbox are then derived from "redirection
   number information", such as that available from History-Info
   (RFC 4244) or from the URI itself (RFC 4458, RFC 4240). This
   is extremely common when you have to deal with legacy voicemail
   systems through PSTN gateways (but is not limited to that).

This "retargeting" system has implications that extend beyond
call-decline.  I'm going to have to think about it some more.  At the
very least, it's an alternative configuration whose operation in this
situation has to be considered as well.

   > 2. You wish for <sip:10.1.1.1> to stop ringing, but for processing to
   >    continue elsewhere immediately.  For this, the UA has to send a 4xx
   >    response.  There is no specific "Decline Here" response, although
   >    480 has a similar meaning.

   Correct. This is a "Decline local" (and I really don't see a reason
   for anything but 480).

Actually, I've got another I-D that I hoping to get a discussion going
in regard to 404, 410, 480, and 604, which not only overlap, but also
provide no choice for reporting certain common conditions.

And within the "decline" semantic, there are further sociological
complications, as the user may wish to decline the call *without*
providing specific indication to the caller that the call was
declined, versus cases where he wants to make such a specific
indication.

   > 4. You wish for <sip:10.1.1.1> and <sip:10.2.2.2> to stop ringing, and
   >    for the call to not go to voicemail, which means that it will then
   >    continue with ringing <michael.procter@citel.com>.

   Yes, that is interesting. Especially if Michael is the Enterprise's 
   operator. That could be quite useful.

What do you mean by "the Enterprise"?  NCC-1701?

   > 5. You wish to terminate all forks of the call everywhere.  This can
   >    be accomplished with a 603 response.

   That depends on your reading of 3261.

True, but the text of 3261 is quite clear on the required processing.
If we discover that we want the *default* behavior of proxies to be
different, we should formally decide so.

   > Interestingly, effect 5 *should not* be achievable -- You are 
   > not authoritative for calls to Michael, and you have no right 
   > to terminate the forks of my call to his UA.

   I don't think that's the conclusion. I think Paul said it best
   when he said it was policy.

   If my service provider is OK with a "Decline (really) everywhere"
   behavior, then it's fine.

   But the service provider could decide he's not and provide alternative
   treatment. Policy decisions.

Whose policy?  Which service provider?

   I think 480 is already enlarged to be honest.

In practice, it's very poorly defined.  My personal preference is that
as part of straightening out those response codes, we create a
specific Decline Here response.  But that is really a Different Topic.

Dale

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



From bliss-bounces@ietf.org Wed Mar 07 10:50:55 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOyPh-0003Od-J3; Wed, 07 Mar 2007 10:50:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOyPf-0003Mv-Rh
	for bliss@ietf.org; Wed, 07 Mar 2007 10:50:47 -0500
Received: from sea02-mxf01.citel.com ([205.234.66.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOyPe-0003qi-En
	for bliss@ietf.org; Wed, 07 Mar 2007 10:50:47 -0500
Received: from [10.8.50.21] (helo=sea02-mxc01.citel.com)
	by sea02-mxf01.citel.com with smtp (Exim 4.43)
	id 1HOyRB-0006sW-2P; Wed, 07 Mar 2007 07:52:21 -0800
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [BLISS] I-Ds concerning problems with response codes
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Wed, 7 Mar 2007 07:50:34 -0800
Message-ID: <76431CABEC5EED489807DB8AEBCCA0BCC1D53D@sea02-mxc01.citel.com>
In-Reply-To: <200703061652.l26Gq1Yk002818@dragon.ariadne.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] I-Ds concerning problems with response codes
Thread-index: AcdgD9/OLwM3XbcxRgaUkW5rnvLSrwAu83rQ
References: <200703011531.l21FVQZn018306@dragon.ariadne.com><1ECE0EB50388174790F9694F77522CCF0F67A4CB@zrc2hxm0.corp.nortel.com>
	<200703061652.l26Gq1Yk002818@dragon.ariadne.com>
From: "Michael Procter" <michael.procter@citel.com>
To: <Dale.Worley@comcast.net>,
	<bliss@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: 
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

Dale wrote:
> Let me construct a slightly elaborate, but as far as I can tell,
> completely realistic use case.

Thanks Dale.  I think this is what I was trying to say.  Breaking out
the 5 cases is very helpful.

I think case 3 is the most interesting for 'normal' use, and 4 is most
relevant for calls that have already been forked multiple times (your
example has this as my-friends@example.com --> audet@nortel.com +
michael.procter@citel.com --> collection of contacts).

The obvious difference between cases 3 and 4 (one goes to VM, and one
doesn't) can be explained by the fact that in case 4, you are unlikely
to want to talk to voicemail for audet@nortel.com, nor for
michael.procter@citel.com.  If there was a voicemail system for=20
my-friends@example.com, that might be useful, though.

Whilst it is probably a little premature to discuss implementation, I
would like to point out that the distinction between 3 and can already
be handled in SIP, using RFC3841 (and examples in RFC4596).  At the time
of the first fork, the proxy could add the following to the outgoing
INVITEs:

	Reject-Contact: *;msgserver		// taken from RFC4596
[1]

This would have the effect of avoiding Francois' and my voicemail
systems in the unlikely case that we decline[2] a call from you.

But, if you called me directly (michael.procter@citel.com), and I
declined the call in the same way[2], then you could get my voicemail
account, since such a Reject-Contact line would not have been added.

Therefore, I suggest that whatever approach to declining a call in case
3 is found, the same approach should be used in case 4.  Handling the
difference in voicemail behaviour can be achieved using RFC3841/RFC4596
Reject-Contact headers added by the first proxy.

[1] RFC3840 defines 'msg-taker', used in RFC3841, but RFC4596 prefers
'msgserver', whilst not mentioning 'msg-taker' at all.  I think they are
supposed to be roughly comparable.
[2] Mechanism to be defined.  But draft-rajesh-sipping-605-01 seems
useful.

Regards,

Michael

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



From bliss-bounces@ietf.org Wed Mar 07 11:32:14 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HOz3l-0008KK-FJ; Wed, 07 Mar 2007 11:32:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HOz3k-0008Ij-61
	for bliss@ietf.org; Wed, 07 Mar 2007 11:32:12 -0500
Received: from zrtps0kp.nortel.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOz3i-0004jR-SQ
	for bliss@ietf.org; Wed, 07 Mar 2007 11:32:12 -0500
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l27GW7L13485; Wed, 7 Mar 2007 11:32:07 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [BLISS] I-Ds concerning problems with response codes
Date: Wed, 7 Mar 2007 10:31:53 -0600
Message-ID: <1ECE0EB50388174790F9694F77522CCF0F79A4A1@zrc2hxm0.corp.nortel.com>
In-Reply-To: <200703071538.l27Fc9Ci005671@dragon.ariadne.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] I-Ds concerning problems with response codes
Thread-Index: AcdgzqvZgotJgQNRS8KOb7zmQQaw5AAAgieg
References: <200703011531.l21FVQZn018306@dragon.ariadne.com>
	<1ECE0EB50388174790F9694F77522CCF0F67A4CB@zrc2hxm0.corp.nortel.com>
	<200703061652.l26Gq1Yk002818@dragon.ariadne.com>
	<1ECE0EB50388174790F9694F77522CCF0F799676@zrc2hxm0.corp.nortel.com>
	<200703071538.l27Fc9Ci005671@dragon.ariadne.com>
From: "Francois Audet" <audet@nortel.com>
To: <Dale.Worley@comcast.net>, <bliss@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: 
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

=20

> -----Original Message-----
> From: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net]=20
> Sent: Wednesday, March 07, 2007 07:38
> To: bliss@ietf.org
> Subject: Re: [BLISS] I-Ds concerning problems with response codes
>
> And within the "decline" semantic, there are further=20
> sociological complications, as the user may wish to decline=20
> the call *without* providing specific indication to the=20
> caller that the call was declined, versus cases where he=20
> wants to make such a specific indication.

Correct.

For example, an "ignore" button (i.e., stop called party user
ringing, but let's the other user ring) looks like you are not=20
there.

A "Make busy" makes it look like you are busy.

A "Decline" may make it look like you don't want to talk to the
user (depending on that user's UI).

>    > 4. You wish for <sip:10.1.1.1> and <sip:10.2.2.2> to=20
> stop ringing, and
>    >    for the call to not go to voicemail, which means that=20
> it will then
>    >    continue with ringing <michael.procter@citel.com>.
>=20
>    Yes, that is interesting. Especially if Michael is the=20
> Enterprise's=20
>    operator. That could be quite useful.
>=20
> What do you mean by "the Enterprise"?  NCC-1701?

No, I mean the Corporation that received the call.

Say you call my phone number (assigned to Nortel), or
my SIP address (@nortel.com).=20

Nortel may decide that if I can't take the call, it gets
anwered by our operator.

Nortel is probably a bad example, but for some Enteprises, this
is exactly the expectation.

>    > 5. You wish to terminate all forks of the call=20
> everywhere.  This can
>    >    be accomplished with a 603 response.
>=20
>    That depends on your reading of 3261.
>=20
> True, but the text of 3261 is quite clear on the required processing.
> If we discover that we want the *default* behavior of proxies=20
> to be different, we should formally decide so.

I don't think it's clear at all...=20

The introduction in 21.6 implies we are talking about a particular user,
i.e., the "AOR", as opposed to, "any user". It's only the definition of
600 that expand it to "any other endpoint". And even then, you could
interpret it (as I did) as saying that it's the endpoints that share
the AOR. That would validate the Voicemail comment (provided we use
your Voicemail model where the mailbox shares the user's AOR).


>    > Interestingly, effect 5 *should not* be achievable -- You are=20
>    > not authoritative for calls to Michael, and you have no right=20
>    > to terminate the forks of my call to his UA.
>=20
>    I don't think that's the conclusion. I think Paul said it best
>    when he said it was policy.
>=20
>    If my service provider is OK with a "Decline (really) everywhere"
>    behavior, then it's fine.
>=20
>    But the service provider could decide he's not and provide=20
> alternative
>    treatment. Policy decisions.
>=20
> Whose policy?  Which service provider?

The proxy responsible for the domain will decide what to do when it=20
receives a 6XX from a UA in that domain based on it's own policy.=20
It may forward the 6XX or it may map it to 4XX or it may provide
alternative treatment.


>    I think 480 is already enlarged to be honest.
>=20
> In practice, it's very poorly defined.  My personal=20
> preference is that as part of straightening out those=20
> response codes, we create a specific Decline Here response. =20
> But that is really a Different Topic.

Yeah, it is a different topic.

I think it's too late to change it because 480 is widely used for that
purpose (and other purposes).

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



From bliss-bounces@ietf.org Thu Mar 08 04:25:33 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HPEsG-0003AJ-OF; Thu, 08 Mar 2007 04:25:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HPEsF-0003AE-Qo
	for bliss@ietf.org; Thu, 08 Mar 2007 04:25:23 -0500
Received: from py-out-1112.google.com ([64.233.166.182])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HPEsE-0002g0-CT
	for bliss@ietf.org; Thu, 08 Mar 2007 04:25:23 -0500
Received: by py-out-1112.google.com with SMTP id f47so155429pye
	for <bliss@ietf.org>; Thu, 08 Mar 2007 01:25:22 -0800 (PST)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
	b=RJL4Mf1R4l2d7jjusbF4qrMXCjejdPGZ4r+73g3V3xLi8pZpWjJSgYPTiSZ3/+QsHSLsPPYabEH3bsHS6XKKcfse09xeYvMMqRMwGpbZeTnDZddBacbntcNXjf5GVQz/uZOdpHmA1qQpL2MrROT6cQKg64t9Yp2iMkMBlTwVUWE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=DnFSs08fzCennZKk9/CT3OwidfPj4DB7jCED96cGceUPkhAXfwM0hhWWE4gaPIqtJYZ+hWERZD27aHATEmtkD1i+Uxyff7ocD+GOSo5c52pQ1agDi70CBHY8V9DmmjIYk2GkVQKWgKj94KKZV3PWe8RUpwox2k9LIf9i43N+L+8=
Received: by 10.35.27.1 with SMTP id e1mr544985pyj.1173345922091;
	Thu, 08 Mar 2007 01:25:22 -0800 (PST)
Received: by 10.35.94.3 with HTTP; Thu, 8 Mar 2007 01:25:22 -0800 (PST)
Message-ID: <5c5981350703080125v53bcd933y1b7da4dab5e49a28@mail.gmail.com>
Date: Thu, 8 Mar 2007 01:25:22 -0800
From: "Mohsen Soroushnejad" <msoroush@gmail.com>
To: bliss@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1
Subject: [BLISS] draft-anil-sipping-bla-04 is now available
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>
Content-Type: multipart/mixed; boundary="===============0212004746=="
Errors-To: bliss-bounces@ietf.org

--===============0212004746==
Content-Type: multipart/alternative; 
	boundary="----=_Part_297_23061284.1173345922044"

------=_Part_297_23061284.1173345922044
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

FYI.

The above draft, along with the companion document "
draft-johnston-bliss-mla-req-00"
are the basis of the "shared line" topic at the upcoming BLISS BOF.

Comments are most welcome.

Regards,
Mohsen

------------------------------------------------------------------------------------------

A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Implementing Multiple Line Appearances using the Session
Initiation Protocol (SIP)
	Author(s)	: A. Kumar, et al.
	Filename	: draft-anil-sipping-bla-04.txt
	Pages		: 46
	Date		: 2007-3-6
	
This document describes the implementation of a group telephony
   feature commonly known as Bridged Line Appearance (BLA), Multiple
   Line Appearance (MLA), or Shared Call/Line Appearance (SCA).  When
   implemented using the Session Initiation Protocol (SIP), it is
   referred to as Multiple Appearances.  This feature is commonly
   offered in the IP Centrex services and IP-PBX offerings and is likely
   to be implemented on SIP IP telephones and SIP feature servers used
   in a business environment.  This specification defines a new SIP
   dialog event package tag "appearance" and a method for a group of SIP
   user agents to coordinate the identification of appearances between
   them using SIP dialog package subscriptions.

A URL for this Internet-Draft
is:http://www.ietf.org/internet-drafts/draft-anil-sipping-bla-04.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request at ietf.org with the word unsubscribe in the body of
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
"get draft-anil-sipping-bla-04.txt".

A list of Internet-Drafts directories can be found
inhttp://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv at ietf.org.
In the body type:
	"FILE /internet-drafts/draft-anil-sipping-bla-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

 <ftp://ftp.ietf.org/internet-drafts/draft-anil-sipping-bla-04.txt><ftp://ftp.ietf.org/internet-drafts/draft-anil-sipping-bla-04.txt>

_______________________________________________
I-D-Announce mailing list
I-D-Announce at ietf.orghttps://www1.ietf.org/mailman/listinfo/i-d-announce

------=_Part_297_23061284.1173345922044
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>FYI.</div>
<div>&nbsp;</div>
<div>The above&nbsp;draft, along with the companion document &quot;<font face="Courier New">draft-johnston-bliss-mla-req-00&quot;</font></div>
<div>are the basis of the &quot;shared line&quot; topic at the upcoming BLISS BOF.</div>
<div>&nbsp;</div>
<div>Comments are most welcome.</div>
<div>&nbsp;</div>
<div>Regards,</div>
<div>Mohsen</div>
<div><pre>------------------------------------------------------------------------------------------</pre><pre>A New Internet-Draft is available from the on-line Internet-Drafts 
directories.


	Title		: Implementing Multiple Line Appearances using the Session Initiation Protocol (SIP)
	Author(s)	: A. Kumar, et al.
	Filename	: draft-anil-sipping-bla-04.txt
	Pages		: 46
	Date		: 2007-3-6
	
This document describes the implementation of a group telephony
   feature commonly known as Bridged Line Appearance (BLA), Multiple
   Line Appearance (MLA), or Shared Call/Line Appearance (SCA).  When
   implemented using the Session Initiation Protocol (SIP), it is
   referred to as Multiple Appearances.  This feature is commonly
   offered in the IP Centrex services and IP-PBX offerings and is likely
   to be implemented on SIP IP telephones and SIP feature servers used
   in a business environment.  This specification defines a new SIP
   dialog event package tag &quot;appearance&quot; and a method for a group of SIP
   user agents to coordinate the identification of appearances between
   them using SIP dialog package subscriptions.

A URL for this Internet-Draft is:
<a href="http://www.ietf.org/internet-drafts/draft-anil-sipping-bla-04.txt">http://www.ietf.org/internet-drafts/draft-anil-sipping-bla-04.txt</a>

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request at <a href="http://ietf.org">ietf.org</a> with the word unsubscribe in the body of 
the message. 
You can also visit <a href="https://www1.ietf.org/mailman/listinfo/I-D-announce"><font color="#810081">https://www1.ietf.org/mailman/listinfo/I-D-announce</font></a> 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username &quot;anonymous&quot; and a password of your e-mail address. After 
logging in, type &quot;cd internet-drafts&quot; and then 
&quot;get draft-anil-sipping-bla-04.txt&quot;.

A list of Internet-Drafts directories can be found in
<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a> 
or <a href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a>

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv at <a href="http://ietf.org">ietf.org</a>.
In the body type:
	&quot;FILE /internet-drafts/draft-anil-sipping-bla-04.txt&quot;.
	
NOTE:	The mail server at <a href="http://ietf.org">ietf.org</a> can return the document in
	MIME-encoded form by using the &quot;mpack&quot; utility.  To use this
	feature, insert the command &quot;ENCODING mime&quot; before the &quot;FILE&quot;
	command.  To decode the response(s), you will need &quot;munpack&quot; or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	&quot;multipart&quot; MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
</pre>
<dl>
<dt><a href="ftp://ftp.ietf.org/internet-drafts/draft-anil-sipping-bla-04.txt">&lt;ftp://ftp.ietf.org/internet-drafts/draft-anil-sipping-bla-04.txt&gt;</a> 
<dd></dd></dt></dl><pre>_______________________________________________
I-D-Announce mailing list
I-D-Announce at <a href="http://ietf.org">ietf.org</a>
<a href="https://www1.ietf.org/mailman/listinfo/i-d-announce">https://www1.ietf.org/mailman/listinfo/i-d-announce</a>
</pre></div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>&nbsp;</div>

------=_Part_297_23061284.1173345922044--


--===============0212004746==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0212004746==--




From bliss-bounces@ietf.org Thu Mar 15 12:42:10 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HRt1X-0002HK-2E; Thu, 15 Mar 2007 12:41:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HRt1W-0002Fx-49; Thu, 15 Mar 2007 12:41:54 -0400
Received: from tcmail23.telekom.de ([217.6.95.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HRt1U-0000ws-LD; Thu, 15 Mar 2007 12:41:54 -0400
Received: from S4DE9JSAANM.ost.t-com.de (S4DE9JSAANM.ost.t-com.de
	[10.125.177.122]) by tcmail21.telekom.de with ESMTP;
	Thu, 15 Mar 2007 17:41:49 +0100
Received: from S4DE9JSAAHW.ost.t-com.de ([10.125.177.160]) by
	S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 15 Mar 2007 17:41:26 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: AW: [BLISS] AW: [Sipping]
	drafdraft-poetzl-sipping-call-completion-02.txt; queue-operation
Date: Thu, 15 Mar 2007 17:41:26 +0100
Message-Id: <CCA850DCD3FBE2479D5076C5C18732220168A957@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <1E4CCB2441C5C0409AD8A929482A09F31BB764@S4DE9JSAAIG.ost.t-com.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] AW: [Sipping]
	drafdraft-poetzl-sipping-call-completion-02.txt; queue-operation
Thread-Index: AcdftbqTXozlXpeyRpywAZW7M60QXAAQbyewAcBkLoA=
From: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
To: "Beck01, Wolfgang" <BeckW@t-systems.com>, <jason@counterpath.com>,
	<sipping@ietf.org>, <bliss@ietf.org>
X-OriginalArrivalTime: 15 Mar 2007 16:41:26.0891 (UTC)
	FILETIME=[C66BB3B0:01C76720]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: 
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

Hi Wolfgang, Jason,


using 'suspend' and 'resume' is a question of the effectiveness of =
running the service, because if a UAC knows that the user is busy and =
sends a 'suspend', the UAS doesn't has to initiate a call-completion =
recall to that user, wait for his response, cancel the recall, not =
knowing anyway if there is still a need to recall this user, and first =
then recall the next user in the queue.

You are right 'add' is a synonyme for SUBSCRIBE with Expires > 0, the =
advantage of it's usage is that it can very easily be interworked with =
the PSTN TCAP ccbsRequest invoke component.

For the denial reasons, there might be SIP response codes which match =
those reasons, but for me they seem to be more appropriate for the SIP =
transactions itself then for the call-completion event. So we decided to =
use an extra parameter, to have a clear separation between those two =
things.

For the caller parameter, there might be the service operation scenario =
where not the originating user is initiating the call-completion =
request, but an Application Server handles the call-completion =
operations for the user. In this case the UAC on the terminating side =
cannot derive the served user from the From header or P-Asserted ID, but =
the caller must be explicitly identified.


Regards, Martin





> -----Urspr=FCngliche Nachricht-----
> Von: Beck, Wolfgang=20
> Gesendet: Dienstag, 6. M=E4rz 2007 15:15
> An: bliss@ietf.org; sipping@ietf.org
> Cc: esasaki@NTT-AT.COM; Martin.Huelsemann@gmx.de
> Betreff: [BLISS] AW: [Sipping]=20
> drafdraft-poetzl-sipping-call-completion-02.txt; queue-operation
>=20
>=20
> Roland,
>=20
> is the queue-operation parameter really necessary?
> 'add' is just a synonym for a SUBSCRIBE with an Expire > 0
>=20
> The 'suspend' / 'resume' functionality can be done by the=20
> calling UA: it
> can ignore ('suspend') or handle ('resume') incoming NOTIFYs.
>=20
> What's the point of the 'caller' parameter? The SUBSCRIBE=20
> request already
> contains 'From' and possibly P-Asserted-Id.=20
>=20
> Aren't the 'short-term-denial' and 'long-term-denial'=20
> parameters already
> covered by existing SIP response codes?
>=20
>=20
> Wolfgang
>=20
>=20
> [non-standard sig as required by dubious EU regulations]
> --
> T-Systems Enterprise Services GmbH
> Aufsichtsrat: Ren=E9 Obermann (Vorsitzender)
> Executive Committee: Lothar Pauly (Vorsitzender)*, Helmut=20
> Binder, Albert Henn, Olaf Heyden*, Katrin Horstmann, Ulrich=20
> Kemp, Axel Knobe*,
> Wilfried Peters*, Dr. Herbert Schaaff*, Zvezdana Seeger*
> Handelsregister: Amtsgericht Frankfurt am Main HRB 55933
> Sitz der Gesellschaft: Frankfurt am Main
> WEEE-Reg.-Nr. DE87523644
> *Gesch=E4ftsf=FChrer gem. =A7 35 GmbHG
>=20
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www1.ietf.org/mailman/listinfo/bliss
>=20

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



From bliss-bounces@ietf.org Thu Mar 15 12:42:58 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HRt2Y-0002pq-DV; Thu, 15 Mar 2007 12:42:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HRt2W-0002pa-TX; Thu, 15 Mar 2007 12:42:56 -0400
Received: from tcmail23.telekom.de ([217.6.95.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HRt2V-000156-EV; Thu, 15 Mar 2007 12:42:56 -0400
Received: from S4DE9JSAANM.ost.t-com.de (S4DE9JSAANM.ost.t-com.de
	[10.125.177.122]) by tcmail21.telekom.de with ESMTP;
	Thu, 15 Mar 2007 17:42:54 +0100
Received: from S4DE9JSAAHW.ost.t-com.de ([10.125.177.160]) by
	S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 15 Mar 2007 17:42:32 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 15 Mar 2007 17:42:31 +0100
Message-Id: <CCA850DCD3FBE2479D5076C5C18732220168A958@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <C9FB7588-25AB-4005-87D4-FD14AA647E51@counterpath.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: comments on draft-poetzl-sipping-call-completion-02
Thread-Index: Acdk3BGaFfUCRjr5RfK5gsW6uAfibQCOsSHw
From: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
To: <jason@counterpath.com>,
    <bliss@ietf.org>,
    <sipping@ietf.org>
X-OriginalArrivalTime: 15 Mar 2007 16:42:32.0375 (UTC)
	FILETIME=[ED73C470:01C76720]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Cc: jean-marie.stupka@siemens.com, "Poetzl, Joachim" <Joachim.Poetzl@t-com.net>
Subject: [BLISS] AW: comments on draft-poetzl-sipping-call-completion-02
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

Hi Jason,

thanks for your comments.

It's conceivable to add oneself to  a call-completion queue by =
subscribing to the dialog-event and being informed the the called user =
is available when one's position in the queue is reached, but I think =
that is not the intention of the dialog-event, and as answered in the =
other mail, also the other queue-manipulation operations are needed, so =
the dialog-event is not enough here.

A mistake at the notifier is not considered in the draft. But as there =
is a limit for the subscription duration, the served user knows that he =
has to try again after 45 min, if there was no recall notification =
during this time.

The adding of text for the recall INVITE is noted. I agree there is text =
missing what happens to the subscription in the case of a successful =
recall. The idea is in fact that a successful recall terminates the =
subscrition.

An invalid call-completion information subscription format can be =
handled by the existing SIP error responses, I will add some text.

8. P-Service indication: thanks for your comments, they will be =
considered for the revision.



Regards, Martin





> -----Urspr=FCngliche Nachricht-----
> Von: Jason Fischl [mailto:jason@counterpath.com]=20
> Gesendet: Montag, 12. M=E4rz 2007 16:55
> An: sipping@ietf.org
> Cc: P=F6tzl, Joachim; H=FClsemann, Martin; =
jean-marie.stupka@siemens.com
> Betreff: comments on draft-poetzl-sipping-call-completion-02
>=20
>=20
> Hello,
>=20
> High level comments:
> - Is it possible to use a restricted version of the dialog-event =20
> package to communicate this information to the UAC? I realize that =20
> dialog-event would only communicate that the callee is available but =20
> this may be all that we really need here.
>=20
> - How would you handle the case where the notifier goes offline =20
> unexpectedly?  e.g. Notifier is a softphone or mobile device and =20
> loses network connectivity or is restarted.
>=20
> - Should the invite after a notification of user-free-for-recall be =20
> sent in the same dialog as the original INVITE and SUBSCRIBE?  If =20
> not, then the INVITE may fork and be answered by a different UAS =20
> which will leave the subscription intact. In this case, the UAC =20
> should remove the subscription upon successful call completion.
>=20
> Specific comments:
> 6.10 Handling of Forked Requests
> - implies that the SUBSCRIBE MUST be sent within the existing dialog =20
> formed by the INVITE or sent to a gruu discovered from the response =20
> to the INVITE. This should probably be called out.
>=20
> 7.1 queue-nature
> - typo SUBSRIBE -> SUBSCRIBE
>=20
> 7.2 queue-operation
> - are subscribe/resume operations really necessary? It seems to me =20
> that these could be handled entirely by the subscriber.
> - what is the behavior of the notifier if an invalid call-completion =20
> information format is received? i.e. what error response code should =20
> be sent?
>=20
> 7.4 caller
> - why is this component needed? Isn't this always the same as the =20
>  From header?
>=20
> 7.5 service-retention
> - Is this option needed? Isn't this always the desired behavior?
>=20
> 8. P-Service-Indication Header
> - the text here is confusing. I think I understood what the header =20
> was for after reading the entire section but the first paragraph was =20
> hard to understand.
> - I'm not sure the UAC and UAS behavior sections are clear as they =20
> are written. There should probably also be a Proxy behavior section.
> - seems like this header could be easily abused.
>=20
> Proposed text:
> The P-Service-Indication header is used to indicate to intermediate =20
> elements or to the UAS that  special processing may be applied. Any =20
> elements in the path that do not understand the header or the=20
> service =20
> indication must ignore it. The header consists of a list of service =20
> indications represented by tokens.
>=20
> I think it would be helpful to describe an example of how a proxy =20
> might use the SI ccss.
>=20
> 8.1 UAC Behavior
> - the text describing behavior in ACK and CANCEL requests that is a =20
> bit confusing.
>=20
> 9. Signaling Flows
> - F3 has a typo in CSeq. Should be SUBSCRIBE not SUBSCRIBEOLO
> - the first example should show the termination of the subscription =20
> after a successful call completion.
>=20
>=20
>=20

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



From bliss-bounces@ietf.org Fri Mar 16 00:36:15 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HS4Aa-0002v0-PQ; Fri, 16 Mar 2007 00:36:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HS4AZ-0002ur-40
	for bliss@ietf.org; Fri, 16 Mar 2007 00:35:59 -0400
Received: from agnada.com ([69.36.182.244])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HS4AK-0003XQ-IG
	for bliss@ietf.org; Fri, 16 Mar 2007 00:35:59 -0400
Received: from [192.168.1.101] (S0106001839eceb7a.vc.shawcable.net
	[70.79.14.230]) (authenticated bits=0)
	by agnada.com (8.12.11.20060308/8.12.11) with ESMTP id l2G4Zf4U030258
	for <bliss@ietf.org>; Thu, 15 Mar 2007 22:35:41 -0600
Message-ID: <45FA1E97.4030801@ntt-at.com>
Date: Thu, 15 Mar 2007 20:35:35 -0800
From: Shida Schubert <shida@ntt-at.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: bliss@ietf.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Subject: [BLISS] Charter updated
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: shida@ntt-at.com
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


 I just updated the charter, I know its kind of last minutes
but I believe all the comments are reflected.

 Diff from ver2 > ver 3 is available at 
http://www.bliss-ietf.org/charter.txt

 Text version is available at http://www.bliss-ietf.org/diff2.html

 Regards
  Shida

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



From bliss-bounces@ietf.org Fri Mar 16 05:38:11 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HS8sX-0007Zx-70; Fri, 16 Mar 2007 05:37:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HS8sV-0007Z7-V8
	for bliss@ietf.org; Fri, 16 Mar 2007 05:37:39 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HS8sQ-0005lc-Cn
	for bliss@ietf.org; Fri, 16 Mar 2007 05:37:39 -0400
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JEZ00DCJPDJWM@siemenscomms.co.uk> for bliss@ietf.org;
	Fri, 16 Mar 2007 09:36:55 +0000 (GMT)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <G8VCVM5N>; Fri, 16 Mar 2007 09:36:56 +0000
Content-return: allowed
Date: Fri, 16 Mar 2007 09:36:56 +0000
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [BLISS] Charter updated
To: shida@ntt-at.com, bliss@ietf.org
Message-id: <50B1CBA96870A34799A506B2313F26670B4F5637@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: 
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

"...presence....IM....are 
clearly out of scope for BLISS and remain the sole province of SIPPING"
Doesn't SIMPLE figure here somewhere?

John 

> -----Original Message-----
> From: Shida Schubert [mailto:shida@ntt-at.com] 
> Sent: 16 March 2007 04:36
> To: bliss@ietf.org
> Subject: [BLISS] Charter updated
> 
> 
>  I just updated the charter, I know its kind of last minutes
> but I believe all the comments are reflected.
> 
>  Diff from ver2 > ver 3 is available at 
> http://www.bliss-ietf.org/charter.txt
> 
>  Text version is available at http://www.bliss-ietf.org/diff2.html
> 
>  Regards
>   Shida
> 
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www1.ietf.org/mailman/listinfo/bliss
> 

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



From bliss-bounces@ietf.org Fri Mar 16 07:57:17 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HSB34-00010W-3W; Fri, 16 Mar 2007 07:56:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HSB30-00010A-SS
	for bliss@ietf.org; Fri, 16 Mar 2007 07:56:38 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSB2x-0001u4-54
	for bliss@ietf.org; Fri, 16 Mar 2007 07:56:38 -0400
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JEZ003E3VTIT6@siemenscomms.co.uk> for bliss@ietf.org;
	Fri, 16 Mar 2007 11:56:06 +0000 (GMT)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <G8VCVQ8D>; Fri, 16 Mar 2007 11:56:08 +0000
Content-return: allowed
Date: Fri, 16 Mar 2007 11:56:07 +0000
From: "Elwell, John" <john.elwell@siemens.com>
To: bliss@ietf.org, mohsen.soroush@sylantro.com, venkatar@sylantro.com,
	paul.pepper@citel.com, anil@yahoo-inc.com, alan@sipstation.com
Message-id: <50B1CBA96870A34799A506B2313F26670B4F587B@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: 
Subject: [BLISS] Comments on draft-anil-sipping-bla-04
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

If this draft is worked on I think terminology will prove a difficult area.
For example, some people use the term "bridged lined appearance" for the
particular situation where there is bridging (mixing) of media so that users
on different devices can participate in the call simultaneously. We should
avoid the term "bridging" for matters that do not involve this type of
bridging. Also the term "appearance" is misleading, because often people use
the term appearance to refer to a particular registered contact for an AoR,
i.e., a device on which that AoR appears. In the draft, however, it is used
to identify a particular call.

In fact terminology throughout the document seems to be inconsistent. A vast
number of terms are used, often meaning the same thing (I think). Some of my
comments below identify particular terminology issues.

In some places the term "line" is used alone without definition.

"Calls can be joined (also called bridged or conferenced together)". Is this
usual? If two devices A1 and A2 have appearances of the same AoR A, and A1
makes a call to B and A2 makes a call to C, this suggests that you can
bridge together A1, A2, B and C. I have not heard of such a behaviour
(although it could be done by conventional SIP conferencing). I think what
the authors may have in mind is that if A1 makes a call to B, A2 can bridge
into that call. However, this is not reflected by the current text.

Section 3.1:
"Executive/Assistant arrangement: The executive may appear as an
   appearance on the assistant SIP telephony device."
This does not seem to match the description of appearance in section 3. If
an appearance is a call, how can an executive be an appearance?

"taking over a
   call on a particular appearance."
This too does not seem to align with the description of appearance in
section 3.

A BLA call group appears to be just the set of registered contacts for a
given AoR - why do we need a special term? Or can there be registered
contacts that are not members of the BLA call group, in which case how are
such contacts identified?

What are "APPEARANCE group", "BLA group" and "AOR
   group"? How do they relate to "BLA call group"? 

"Virtual BLA: Allows a AOR, not assigned as a primary appearance". What is a
primary appearance? It is not defined and not used elsewhere.

"The Appearance Agent can select the appearance number for an incoming
   call."
What about an outgoing call?

"Some implementations of this feature utilize a URI parameter such as
   "line=3" on the Contact URI."
How can a parameter on the contact URI identify a call? Perhaps it doesn't
matter, because this is not the chosen method. Just rather confusing.

"the proxy could fetch this information by initiating a
   SUBSCRIBE request with Expires: 0 for the AOR to fetch the list of
   lines that are in use."
If an appearance number identifies a call, what is the relevance of the
number of lines in use - shouldn't it be the number of calls (where each
line can have multiple calls potentially)? Of course, this depends exactly
what is meant by "line".

"When calls are placed on hold, the UAs MAY include local session
   description in the dialog package notification.  The element should
   indicate that the call that is the subject of the dialog is being
   held (use of a=inactive or a=sendonly is RECOMMENDED [9])."
Do we really want to get into the parsing of SDP in order to determine the
state of a call? We would start getting into considerations like whether
a=inactive or a=sendonly is at the session level or media level, and if
different media have different values, which is the authoritative value. The
status of the media is of less relevance than whether the call is in a state
where it can be picked up by another device, so we should ensure that
appropriate, easy to interpret indications are given in the dialog event
package document.

"when it is
   attempting to 'seize' a line appearance"
This sounds like an outgoing call attempt, but previously it says that
appearance numbers are assigned only for incoming calls. However, it does
seem reasonable to assign an appearance number to an outgoing call, to allow
it to be picked up, bridged into, etc.

"but this MUST be implemented to resolve glare
   issues."
I think the glare issue talked about is where there is some limit to the
number of calls than can be in progress for a given AoR. This isn't really
discussed much.

"This is needed to resolve conflicts in the use of a particular
   appearance."
What is meant by "appearance" here?

Regards,

John

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



From bliss-bounces@ietf.org Fri Mar 16 11:57:34 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HSEnt-0005dy-27; Fri, 16 Mar 2007 11:57:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HSEnr-0005dt-QM
	for bliss@ietf.org; Fri, 16 Mar 2007 11:57:15 -0400
Received: from mail44.opentransfer.com ([71.18.216.13])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HSEnq-00009Z-8S
	for bliss@ietf.org; Fri, 16 Mar 2007 11:57:15 -0400
Received: (qmail 22621 invoked by uid 399); 16 Mar 2007 15:57:12 -0000
Received: from unknown (HELO ?192.168.0.40?) (24.107.197.43)
	by mail44.opentransfer.com with SMTP; 16 Mar 2007 15:57:12 -0000
Message-ID: <45FABE58.6040703@sipstation.com>
Date: Fri, 16 Mar 2007 10:57:12 -0500
From: Alan Johnston <alan@sipstation.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens.com>
References: <50B1CBA96870A34799A506B2313F26670B4F587B@ntht201e.siemenscomms.co.uk>
In-Reply-To: <50B1CBA96870A34799A506B2313F26670B4F587B@ntht201e.siemenscomms.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48
Cc: bliss@ietf.org, anil@yahoo-inc.com, mohsen.soroush@sylantro.com,
	venkatar@sylantro.com
Subject: [BLISS] Re: Comments on draft-anil-sipping-bla-04
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

John,

Thank you for your comments on the draft.   See my comments below.   
Since this is the BLISS list, I'm hoping to have more discussion about 
the requirements in draft-johnston-bliss-mla-req-00.txt rather then the 
mechanism in this draft.

You are right that terminology is difficult, and despite a major rewrite 
of the document we didn't quite get it right.  Hopefully we will get 
closer in the next version.

Thanks,
Alan


Elwell, John wrote:
> If this draft is worked on I think terminology will prove a difficult area.
> For example, some people use the term "bridged lined appearance" for the
> particular situation where there is bridging (mixing) of media so that users
> on different devices can participate in the call simultaneously. We should
> avoid the term "bridging" for matters that do not involve this type of
> bridging.

We tried to only use the term bridging early in the draft in the 
non-normative sections.  After that, we tried to switch to the 
appearance term.

>  Also the term "appearance" is misleading, because often people use
> the term appearance to refer to a particular registered contact for an AoR,
> i.e., a device on which that AoR appears. In the draft, however, it is used
> to identify a particular call.
>
>   

We are open to other terms, but I thought appearance was pretty good.  
I've never heard of appearance being used to indicated a registered 
contact - is there a document you can point me to here?  We definitely 
want to avoid naming collisions.

> In fact terminology throughout the document seems to be inconsistent. A vast
> number of terms are used, often meaning the same thing (I think). Some of my
> comments below identify particular terminology issues.
>
> In some places the term "line" is used alone without definition.
>   

Well, there is actually no real definition for a "line" in SIP - it is a 
virtual construct.  Even though I generally dislike long terminology 
sections, we probably should add one to this document.

> "Calls can be joined (also called bridged or conferenced together)". Is this
> usual? If two devices A1 and A2 have appearances of the same AoR A, and A1
> makes a call to B and A2 makes a call to C, this suggests that you can
> bridge together A1, A2, B and C. 

No, this is not the behavior we meant - we'll reword to avoid confusion.

> I have not heard of such a behaviour
> (although it could be done by conventional SIP conferencing). I think what
> the authors may have in mind is that if A1 makes a call to B, A2 can bridge
> into that call. However, this is not reflected by the current text.
>   

Yes, this is what we meant.

> Section 3.1:
> "Executive/Assistant arrangement: The executive may appear as an
>    appearance on the assistant SIP telephony device."
> This does not seem to match the description of appearance in section 3. If
> an appearance is a call, how can an executive be an appearance?
>
> "taking over a
>    call on a particular appearance."
> This too does not seem to align with the description of appearance in
> section 3.
>   

You are right - we will fix this wording problem.

> A BLA call group appears to be just the set of registered contacts for a
> given AoR - why do we need a special term? Or can there be registered
> contacts that are not members of the BLA call group, in which case how are
> such contacts identified?
>
> What are "APPEARANCE group", "BLA group" and "AOR
>    group"? How do they relate to "BLA call group"? 
>   

I don't believe there are any differences between these.

> "Virtual BLA: Allows a AOR, not assigned as a primary appearance". What is a
> primary appearance? It is not defined and not used elsewhere.
>
> "The Appearance Agent can select the appearance number for an incoming
>    call."
> What about an outgoing call?
>   

Yes - that is described a few sentences later.

> "Some implementations of this feature utilize a URI parameter such as
>    "line=3" on the Contact URI."
> How can a parameter on the contact URI identify a call? Perhaps it doesn't
> matter, because this is not the chosen method. Just rather confusing.
>   

Does the description in draft-johnston-bliss-mla-req-00.txt make better 
sense?  The intention was not to discuss the URI contact method in this 
draft but I guess this text got left in by accident.

> "the proxy could fetch this information by initiating a
>    SUBSCRIBE request with Expires: 0 for the AOR to fetch the list of
>    lines that are in use."
> If an appearance number identifies a call, what is the relevance of the
> number of lines in use - shouldn't it be the number of calls (where each
> line can have multiple calls potentially)? Of course, this depends exactly
> what is meant by "line".
>   

We don't use the word line here.  This discussion is about how a proxy 
server, which does not necessarily have any knowledge of which UAs are 
in active sessions, could learn which appearance numbers are in use so 
that an unused one can be assigned.

> "When calls are placed on hold, the UAs MAY include local session
>    description in the dialog package notification.  The element should
>    indicate that the call that is the subject of the dialog is being
>    held (use of a=inactive or a=sendonly is RECOMMENDED [9])."
> Do we really want to get into the parsing of SDP in order to determine the
> state of a call? We would start getting into considerations like whether
> a=inactive or a=sendonly is at the session level or media level, and if
> different media have different values, which is the authoritative value. The
> status of the media is of less relevance than whether the call is in a state
> where it can be picked up by another device, so we should ensure that
> appropriate, easy to interpret indications are given in the dialog event
> package document.
>   

This is a mistake - the next sentence was meant to replace that one:  
"When calls are placed on hold, the "+sip.rendering=no" [RFC 3840 
<http://tools.ietf.org/html/rfc3840>] feature tag MUST be used."  We 
don't want to send SDP in the dialog package notifications.

> "when it is
>    attempting to 'seize' a line appearance"
> This sounds like an outgoing call attempt, but previously it says that
> appearance numbers are assigned only for incoming calls. However, it does
> seem reasonable to assign an appearance number to an outgoing call, to allow
> it to be picked up, bridged into, etc.
>
>   

No, it says both earlier, but we'll go over to make sure any confusing 
text is fixed.

> "but this MUST be implemented to resolve glare
>    issues."
> I think the glare issue talked about is where there is some limit to the
> number of calls than can be in progress for a given AoR. This isn't really
> discussed much.
>
> "This is needed to resolve conflicts in the use of a particular
>    appearance."
> What is meant by "appearance" here?
>   

If two UAs in the group both select appearance number 2 at the same time 
- only one of them may use it, the other must select appearance number 3 
instead.

> Regards,
>
> John
>
>
>   


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



From bliss-bounces@ietf.org Fri Mar 16 14:40:58 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HSHM8-0008Sr-VQ; Fri, 16 Mar 2007 14:40:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HSHM7-0008SE-I0
	for bliss@ietf.org; Fri, 16 Mar 2007 14:40:47 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSHM3-0007kK-UG
	for bliss@ietf.org; Fri, 16 Mar 2007 14:40:47 -0400
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JF000CB5EJK9O@siemenscomms.co.uk> for bliss@ietf.org;
	Fri, 16 Mar 2007 18:40:32 +0000 (GMT)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <G8VCV5B9>; Fri, 16 Mar 2007 18:40:34 +0000
Content-return: allowed
Date: Fri, 16 Mar 2007 18:40:33 +0000
From: "Elwell, John" <john.elwell@siemens.com>
To: Alan Johnston <alan@sipstation.com>
Message-id: <50B1CBA96870A34799A506B2313F26670B4F5D1F@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ba0d4c5f57f7c289496fce758bbf4798
Cc: bliss@ietf.org, anil@yahoo-inc.com, mohsen.soroush@sylantro.com,
	venkatar@sylantro.com
Subject: [BLISS] RE: Comments on draft-anil-sipping-bla-04
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

Alan,

Yes, I sent it to BLISS because I thought that was where the feature would
be discussed, but I still need to review the requirements draft. See below
for more on this draft.

John 

> -----Original Message-----
> From: Alan Johnston [mailto:alan@sipstation.com] 
> Sent: 16 March 2007 15:57
> To: Elwell, John
> Cc: bliss@ietf.org; mohsen.soroush@sylantro.com; 
> venkatar@sylantro.com; paul.pepper@citel.com; anil@yahoo-inc.com
> Subject: Re: Comments on draft-anil-sipping-bla-04
> 
> John,
> 
> Thank you for your comments on the draft.   See my comments below.   
> Since this is the BLISS list, I'm hoping to have more 
> discussion about 
> the requirements in draft-johnston-bliss-mla-req-00.txt 
> rather then the 
> mechanism in this draft.
> 
> You are right that terminology is difficult, and despite a 
> major rewrite 
> of the document we didn't quite get it right.  Hopefully we will get 
> closer in the next version.
> 
> Thanks,
> Alan
> 
> 
> Elwell, John wrote:
> > If this draft is worked on I think terminology will prove a 
> difficult area.
> > For example, some people use the term "bridged lined 
> appearance" for the
> > particular situation where there is bridging (mixing) of 
> media so that users
> > on different devices can participate in the call 
> simultaneously. We should
> > avoid the term "bridging" for matters that do not involve 
> this type of
> > bridging.
> 
> We tried to only use the term bridging early in the draft in the 
> non-normative sections.  After that, we tried to switch to the 
> appearance term.
> 
> >  Also the term "appearance" is misleading, because often people use
> > the term appearance to refer to a particular registered 
> contact for an AoR,
> > i.e., a device on which that AoR appears. In the draft, 
> however, it is used
> > to identify a particular call.
> >
> >   
> 
> We are open to other terms, but I thought appearance was 
> pretty good.  
> I've never heard of appearance being used to indicated a registered 
> contact - is there a document you can point me to here?  We 
> definitely 
> want to avoid naming collisions.
[JRE] My company uses it internally and when talking to customers. When I
say a registered contact, I mean only in the context of multi-line
appearance or shared line appearance (where one device can have appearances
of multiple lines, or a line can be shared among multiple devices
respectively).

> 
> > In fact terminology throughout the document seems to be 
> inconsistent. A vast
> > number of terms are used, often meaning the same thing (I 
> think). Some of my
> > comments below identify particular terminology issues.
> >
> > In some places the term "line" is used alone without definition.
> >   
> 
> Well, there is actually no real definition for a "line" in 
> SIP - it is a 
> virtual construct.  Even though I generally dislike long terminology 
> sections, we probably should add one to this document.
[JRE] Either that or avoid duplicate terminology, if there is another
defined term meaning the same thing.

> 
> > "Calls can be joined (also called bridged or conferenced 
> together)". Is this
> > usual? If two devices A1 and A2 have appearances of the 
> same AoR A, and A1
> > makes a call to B and A2 makes a call to C, this suggests 
> that you can
> > bridge together A1, A2, B and C. 
> 
> No, this is not the behavior we meant - we'll reword to avoid 
> confusion.
> 
> > I have not heard of such a behaviour
> > (although it could be done by conventional SIP 
> conferencing). I think what
> > the authors may have in mind is that if A1 makes a call to 
> B, A2 can bridge
> > into that call. However, this is not reflected by the current text.
> >   
> 
> Yes, this is what we meant.
> 
> > Section 3.1:
> > "Executive/Assistant arrangement: The executive may appear as an
> >    appearance on the assistant SIP telephony device."
> > This does not seem to match the description of appearance 
> in section 3. If
> > an appearance is a call, how can an executive be an appearance?
> >
> > "taking over a
> >    call on a particular appearance."
> > This too does not seem to align with the description of 
> appearance in
> > section 3.
> >   
> 
> You are right - we will fix this wording problem.
> 
> > A BLA call group appears to be just the set of registered 
> contacts for a
> > given AoR - why do we need a special term? Or can there be 
> registered
> > contacts that are not members of the BLA call group, in 
> which case how are
> > such contacts identified?
> >
> > What are "APPEARANCE group", "BLA group" and "AOR
> >    group"? How do they relate to "BLA call group"? 
> >   
> 
> I don't believe there are any differences between these.
[JRE] So stick to one term.

> 
> > "Virtual BLA: Allows a AOR, not assigned as a primary 
> appearance". What is a
> > primary appearance? It is not defined and not used elsewhere.
> >
> > "The Appearance Agent can select the appearance number for 
> an incoming
> >    call."
> > What about an outgoing call?
> >   
> 
> Yes - that is described a few sentences later.
[JRE] I think the problem I had was that it gave me the impression initially
that appearance numbers were assigned only to incoming calls, but that did
seem to get contradicted later.

> 
> > "Some implementations of this feature utilize a URI 
> parameter such as
> >    "line=3" on the Contact URI."
> > How can a parameter on the contact URI identify a call? 
> Perhaps it doesn't
> > matter, because this is not the chosen method. Just rather 
> confusing.
> >   
> 
> Does the description in draft-johnston-bliss-mla-req-00.txt 
> make better 
> sense?  The intention was not to discuss the URI contact 
> method in this 
> draft but I guess this text got left in by accident.
> 
> > "the proxy could fetch this information by initiating a
> >    SUBSCRIBE request with Expires: 0 for the AOR to fetch 
> the list of
> >    lines that are in use."
> > If an appearance number identifies a call, what is the 
> relevance of the
> > number of lines in use - shouldn't it be the number of 
> calls (where each
> > line can have multiple calls potentially)? Of course, this 
> depends exactly
> > what is meant by "line".
> >   
> 
> We don't use the word line here.
[JRE] OK, but you use the word "lines".

>  This discussion is about 
> how a proxy 
> server, which does not necessarily have any knowledge of 
> which UAs are 
> in active sessions, could learn which appearance numbers are 
> in use so 
> that an unused one can be assigned.
> 
> > "When calls are placed on hold, the UAs MAY include local session
> >    description in the dialog package notification.  The 
> element should
> >    indicate that the call that is the subject of the dialog is being
> >    held (use of a=inactive or a=sendonly is RECOMMENDED [9])."
> > Do we really want to get into the parsing of SDP in order 
> to determine the
> > state of a call? We would start getting into considerations 
> like whether
> > a=inactive or a=sendonly is at the session level or media 
> level, and if
> > different media have different values, which is the 
> authoritative value. The
> > status of the media is of less relevance than whether the 
> call is in a state
> > where it can be picked up by another device, so we should 
> ensure that
> > appropriate, easy to interpret indications are given in the 
> dialog event
> > package document.
> >   
> 
> This is a mistake - the next sentence was meant to replace that one:  
> "When calls are placed on hold, the "+sip.rendering=no" [RFC 3840 
> <http://tools.ietf.org/html/rfc3840>] feature tag MUST be used."  We 
> don't want to send SDP in the dialog package notifications.
> 
> > "when it is
> >    attempting to 'seize' a line appearance"
> > This sounds like an outgoing call attempt, but previously 
> it says that
> > appearance numbers are assigned only for incoming calls. 
> However, it does
> > seem reasonable to assign an appearance number to an 
> outgoing call, to allow
> > it to be picked up, bridged into, etc.
> >
> >   
> 
> No, it says both earlier, but we'll go over to make sure any 
> confusing 
> text is fixed.
> 
> > "but this MUST be implemented to resolve glare
> >    issues."
> > I think the glare issue talked about is where there is some 
> limit to the
> > number of calls than can be in progress for a given AoR. 
> This isn't really
> > discussed much.
> >
> > "This is needed to resolve conflicts in the use of a particular
> >    appearance."
> > What is meant by "appearance" here?
> >   
> 
> If two UAs in the group both select appearance number 2 at 
> the same time 
> - only one of them may use it, the other must select 
> appearance number 3 
> instead.
> 
> > Regards,
> >
> > John
> >
> >
> >   
> 

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



From bliss-bounces@ietf.org Sun Mar 18 03:58:33 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HSqHM-0003Aw-Bu; Sun, 18 Mar 2007 03:58:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HSqHL-0003Al-3v
	for bliss@ietf.org; Sun, 18 Mar 2007 03:58:11 -0400
Received: from agnada.com ([69.36.182.244])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSqHG-00048i-Pm
	for bliss@ietf.org; Sun, 18 Mar 2007 03:58:11 -0400
Received: from [130.129.17.120] (dhcp-1178.ietf68.org [130.129.17.120])
	(authenticated bits=0)
	by agnada.com (8.12.11.20060308/8.12.11) with ESMTP id l2I7vtjB002946; 
	Sun, 18 Mar 2007 01:58:03 -0600
Message-ID: <45FCF0FA.3090506@ntt-at.com>
Date: Sun, 18 Mar 2007 08:57:46 +0100
From: Shida Schubert <shida@ntt-at.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens.com>
Subject: Re: [BLISS] Charter updated
References: <50B1CBA96870A34799A506B2313F26670B4F5637@ntht201e.siemenscomms.co.uk>
In-Reply-To: <50B1CBA96870A34799A506B2313F26670B4F5637@ntht201e.siemenscomms.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
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


John;

 Thanks for your review.

 SIMPLE is mentioned for its involvement/relationship in the
guiding principles. Is it sufficient or do you suggest we add
the relationship with the SIMPLE WG somewhere in the main
body of the charter? If so I would appreciate any suggestions.

 Thanks
  Shida


Elwell, John wrote:
> "...presence....IM....are 
> clearly out of scope for BLISS and remain the sole province of SIPPING"
> Doesn't SIMPLE figure here somewhere?
>
> John 
>
>   
>> -----Original Message-----
>> From: Shida Schubert [mailto:shida@ntt-at.com] 
>> Sent: 16 March 2007 04:36
>> To: bliss@ietf.org
>> Subject: [BLISS] Charter updated
>>
>>
>>  I just updated the charter, I know its kind of last minutes
>> but I believe all the comments are reflected.
>>
>>  Diff from ver2 > ver 3 is available at 
>> http://www.bliss-ietf.org/charter.txt
>>
>>  Text version is available at http://www.bliss-ietf.org/diff2.html
>>
>>  Regards
>>   Shida
>>
>> _______________________________________________
>> BLISS mailing list
>> BLISS@ietf.org
>> https://www1.ietf.org/mailman/listinfo/bliss
>>
>>     
>
>
>   


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



From bliss-bounces@ietf.org Sun Mar 18 08:17:59 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HSuKi-0000wA-MS; Sun, 18 Mar 2007 08:17:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HSuKh-0000w1-4N
	for bliss@ietf.org; Sun, 18 Mar 2007 08:17:55 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSuKa-0001VB-Nc
	for bliss@ietf.org; Sun, 18 Mar 2007 08:17:55 -0400
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JF300J1UM5DZU@siemenscomms.co.uk> for bliss@ietf.org;
	Sun, 18 Mar 2007 12:17:37 +0000 (GMT)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <G8VCV0GS>; Sun, 18 Mar 2007 12:17:39 +0000
Content-return: allowed
Date: Sun, 18 Mar 2007 12:17:38 +0000
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [BLISS] Charter updated
To: Shida Schubert <shida@ntt-at.com>
Message-id: <50B1CBA96870A34799A506B2313F26670B4F5D6C@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
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

Shida,

The statement that presence and IM remain the sole province of SIPPING is
clearly wrong and should be corrected.

John 

> -----Original Message-----
> From: Shida Schubert [mailto:shida@ntt-at.com] 
> Sent: 18 March 2007 07:58
> To: Elwell, John
> Cc: bliss@ietf.org
> Subject: Re: [BLISS] Charter updated
> 
> 
> John;
> 
>  Thanks for your review.
> 
>  SIMPLE is mentioned for its involvement/relationship in the
> guiding principles. Is it sufficient or do you suggest we add
> the relationship with the SIMPLE WG somewhere in the main
> body of the charter? If so I would appreciate any suggestions.
> 
>  Thanks
>   Shida
> 
> 
> Elwell, John wrote:
> > "...presence....IM....are 
> > clearly out of scope for BLISS and remain the sole province 
> of SIPPING"
> > Doesn't SIMPLE figure here somewhere?
> >
> > John 
> >
> >   
> >> -----Original Message-----
> >> From: Shida Schubert [mailto:shida@ntt-at.com] 
> >> Sent: 16 March 2007 04:36
> >> To: bliss@ietf.org
> >> Subject: [BLISS] Charter updated
> >>
> >>
> >>  I just updated the charter, I know its kind of last minutes
> >> but I believe all the comments are reflected.
> >>
> >>  Diff from ver2 > ver 3 is available at 
> >> http://www.bliss-ietf.org/charter.txt
> >>
> >>  Text version is available at http://www.bliss-ietf.org/diff2.html
> >>
> >>  Regards
> >>   Shida
> >>
> >> _______________________________________________
> >> BLISS mailing list
> >> BLISS@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/bliss
> >>
> >>     
> >
> >
> >   
> 

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



From bliss-bounces@ietf.org Sun Mar 18 18:05:25 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HT3VF-0003MO-Gb; Sun, 18 Mar 2007 18:05:25 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HT3VE-0003MG-CY
	for bliss@ietf.org; Sun, 18 Mar 2007 18:05:24 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HT3VA-0002pQ-Oy
	for bliss@ietf.org; Sun, 18 Mar 2007 18:05:24 -0400
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JF40002PDCRBN@siemenscomms.co.uk> for bliss@ietf.org;
	Sun, 18 Mar 2007 22:05:15 +0000 (GMT)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <G8VCWA4R>; Sun, 18 Mar 2007 22:05:17 +0000
Content-return: allowed
Date: Sun, 18 Mar 2007 22:05:11 +0000
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [BLISS] Fwd: I-D ACTION:draft-johnston-bliss-mla-req-00.txt
To: Alan Johnston <alan@sipstation.com>, bliss@ietf.org
Message-id: <50B1CBA96870A34799A506B2313F26670B4F5D99@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985
Cc: Mohsen Soroush-nejad <Mohsen.Soroushnejad@sylantro.com>,
	Venkatesh Venkataramanan <venkatesh@sylantro.com>,
	Anil Kumar <anil@yahoo-inc.com>
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

Alan,

Some of the terminology concerns I already made on draft=anil-sipping-bla
apply also to this document, so I won't repeat them. Other comments:

REQ-4: "UAs registering against the group AOR should be able
   to learn about each other and join the appearance group."
Why do UAs need to learn about each other? Isn't it just necessary for a UA
to know that the AoR is a group AoR and therefore is shared by other UAs?
Although specific solutions might require the UA to know about specific
other UAs, I don't think this is a basic requirement. I don't think the
solutions discussed in the draft require this.

"REQ-5 The mechanism must scale for large numbers of appearances, n,
   and large numbers of UAs, N, without introducing excessive messaging
   traffic."
One consequence of a large N is, depending on solution, the establishment of
N early dialogs towards the UAC and N parallel ICE procedures, N parallel
key management procedures, etc.. This might not be important for values of N
of the order of 3-5, but with much larger values of N this could certainly
be a problem. I assume this requirement is intended to cover this and to
include messages in general (such as STUN and whatever in-band key
management is used) as well as SIP messaging.

"The use of a State Agent for the Dialog Package meets REQ-5."
Well, I don't think it does, for reasons in my previous comment.

The comparison of options and the conclusions that are reached seem
reasonable to me. My only concern is the scalability to large values of N in
environments where NAT traversal and media security are managed on an
end-to-end basis, although it would work in environments where SBCs handle
NAT traversal and where key management for media security is not done until
one of the UAs answers.

John





 

> -----Original Message-----
> From: Alan Johnston [mailto:alan@sipstation.com] 
> Sent: 27 February 2007 21:13
> To: bliss@ietf.org
> Cc: Mohsen Soroush-nejad; Venkatesh Venkataramanan; Anil Kumar
> Subject: [BLISS] Fwd: I-D ACTION:draft-johnston-bliss-mla-req-00.txt
> 
> All,
> 
> The authors of draft-anil-sipping-bla (which will be revised 
> as -04 next 
> week) have put together this draft discussing requirements and 
> implementation options for set of features known as Bridged Line 
> Appearance (BLA), Multiple Line Appearance (MLA), Single Line 
> Extension, 
> etc.
> 
> Comments are most welcome.
> 
> Thanks,
> Alan
> 
> -------- Original Message --------
> Subject: 	I-D ACTION:draft-johnston-bliss-mla-req-00.txt
> Date: 	Tue, 27 Feb 2007 15:50:03 -0500
> From: 	Internet-Drafts@ietf.org
> Reply-To: 	internet-drafts@ietf.org
> To: 	i-d-announce@ietf.org
> 
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> 
> 
> 	Title		: Requirements and Implementation Options for
>                           the Multiple Line Appearance Feature using 
>                           the Session Initiation Protocol (SIP)
> 	Author(s)	: A. Johnston, et al.
> 	Filename	: draft-johnston-bliss-mla-req-00.txt
> 	Pages		: 16
> 	Date		: 2007-2-27
> 	
>    This document describes the requirements for implementation of a
>    group telephony feature commonly known as Bridged Line Appearance
>    (BLA) or Multiple Line Appearance, or Shared Call/Line Appearance
>    (SCA).  When implemented using the Session Initiation 
> Protocol (SIP),
>    it is referred to as Multiple Appearances.  This feature 
> is commonly
>    offered in the IP Centrex services and IP-PBX offerings 
> and is likely
>    to be implemented on SIP IP telephones and SIP feature servers used
>    in a business environment.  This document lists requirements and
>    compares implementation options for this feature.
> 
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-johnston-bliss-mla-r
eq-00.txt
> 
> To remove yourself from the I-D Announcement list, send a message to 
> i-d-announce-request@ietf.org with the word unsubscribe in 
> the body of 
> the message. 
> You can also visit 
> https://www1.ietf.org/mailman/listinfo/I-D-announce 
> to change your subscription settings.
> 
> Internet-Drafts are also available by anonymous FTP. Login with the 
> username "anonymous" and a password of your e-mail address. After 
> logging in, type "cd internet-drafts" and then 
> "get draft-johnston-bliss-mla-req-00.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html 
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-johnston-bliss-mla-req-00.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant 
> mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 
> 
> 
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www1.ietf.org/mailman/listinfo/bliss
> 

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



From bliss-bounces@ietf.org Mon Mar 19 03:55:44 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTCiU-0000ED-9u; Mon, 19 Mar 2007 03:55:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTCiT-00006G-0v
	for bliss@ietf.org; Mon, 19 Mar 2007 03:55:41 -0400
Received: from agnada.com ([69.36.182.244])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTCiO-0004Jo-MB
	for bliss@ietf.org; Mon, 19 Mar 2007 03:55:41 -0400
Received: from [130.129.17.120] (dhcp-1178.ietf68.org [130.129.17.120])
	(authenticated bits=0)
	by agnada.com (8.12.11.20060308/8.12.11) with ESMTP id l2J7tY5b026792; 
	Mon, 19 Mar 2007 01:55:35 -0600
Message-ID: <45FE41F0.80406@ntt-at.com>
Date: Mon, 19 Mar 2007 08:55:28 +0100
From: Shida Schubert <shida@ntt-at.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens.com>
Subject: Re: [BLISS] Charter updated
References: <50B1CBA96870A34799A506B2313F26670B4F5D6C@ntht201e.siemenscomms.co.uk>
In-Reply-To: <50B1CBA96870A34799A506B2313F26670B4F5D6C@ntht201e.siemenscomms.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
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


John,

 How is something like this?

"SIP applications such as configuration, presence, SIP extensions for 
IM, and session policy
are clearly out of scope for BLISS and remain the sole province of 
either SIPPING or SIMPLE."

 Regards
  Shida Schubert

Elwell, John wrote:
> Shida,
>
> The statement that presence and IM remain the sole province of SIPPING is
> clearly wrong and should be corrected.
>
> John 
>
>   
>> -----Original Message-----
>> From: Shida Schubert [mailto:shida@ntt-at.com] 
>> Sent: 18 March 2007 07:58
>> To: Elwell, John
>> Cc: bliss@ietf.org
>> Subject: Re: [BLISS] Charter updated
>>
>>
>> John;
>>
>>  Thanks for your review.
>>
>>  SIMPLE is mentioned for its involvement/relationship in the
>> guiding principles. Is it sufficient or do you suggest we add
>> the relationship with the SIMPLE WG somewhere in the main
>> body of the charter? If so I would appreciate any suggestions.
>>
>>  Thanks
>>   Shida
>>
>>
>> Elwell, John wrote:
>>     
>>> "...presence....IM....are 
>>> clearly out of scope for BLISS and remain the sole province 
>>>       
>> of SIPPING"
>>     
>>> Doesn't SIMPLE figure here somewhere?
>>>
>>> John 
>>>
>>>   
>>>       
>>>> -----Original Message-----
>>>> From: Shida Schubert [mailto:shida@ntt-at.com] 
>>>> Sent: 16 March 2007 04:36
>>>> To: bliss@ietf.org
>>>> Subject: [BLISS] Charter updated
>>>>
>>>>
>>>>  I just updated the charter, I know its kind of last minutes
>>>> but I believe all the comments are reflected.
>>>>
>>>>  Diff from ver2 > ver 3 is available at 
>>>> http://www.bliss-ietf.org/charter.txt
>>>>
>>>>  Text version is available at http://www.bliss-ietf.org/diff2.html
>>>>
>>>>  Regards
>>>>   Shida
>>>>
>>>> _______________________________________________
>>>> BLISS mailing list
>>>> BLISS@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/bliss
>>>>
>>>>     
>>>>         
>>>   
>>>       
>
>
>   


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



From bliss-bounces@ietf.org Mon Mar 19 04:23:09 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTD92-0006cm-Vl; Mon, 19 Mar 2007 04:23:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTD91-0006cL-LQ
	for bliss@ietf.org; Mon, 19 Mar 2007 04:23:07 -0400
Received: from ihemail4.lucent.com ([135.245.0.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTD8z-0007sG-5q
	for bliss@ietf.org; Mon, 19 Mar 2007 04:23:07 -0400
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id l2J8N3oE008844;
	Mon, 19 Mar 2007 03:23:03 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 19 Mar 2007 03:23:03 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.29]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 19 Mar 2007 09:22:59 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [BLISS] Charter updated
Date: Mon, 19 Mar 2007 09:22:57 +0100
Message-ID: <5D1A7985295922448D5550C94DE29180E97B80@DEEXC1U01.de.lucent.com>
In-Reply-To: <45FE41F0.80406@ntt-at.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] Charter updated
Thread-Index: Acdp/CqyUDWTXyYeTF+12L9RT9pOawAAplEQ
References: <50B1CBA96870A34799A506B2313F26670B4F5D6C@ntht201e.siemenscomms.co.uk>
	<45FE41F0.80406@ntt-at.com>
From: "Drage, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "Shida Schubert" <shida@ntt-at.com>,
	"Elwell, John" <john.elwell@siemens.com>
X-OriginalArrivalTime: 19 Mar 2007 08:22:59.0359 (UTC)
	FILETIME=[CDCB7AF0:01C769FF]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
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

So where does that leave us on SIP extensions such as normal event =
packages (not event template-packages) and new URI parameters which at =
the moment require RFCs, but do not automatically require SIP or SIPPING =
to produce them.

Does BLISS do those for the services it is working on, or do they go =
back to SIPPING?

Regards

Keith

> -----Original Message-----
> From: Shida Schubert [mailto:shida@ntt-at.com]=20
> Sent: Monday, March 19, 2007 7:55 AM
> To: Elwell, John
> Cc: bliss@ietf.org
> Subject: Re: [BLISS] Charter updated
>=20
>=20
> John,
>=20
>  How is something like this?
>=20
> "SIP applications such as configuration, presence, SIP=20
> extensions for IM, and session policy are clearly out of=20
> scope for BLISS and remain the sole province of either=20
> SIPPING or SIMPLE."
>=20
>  Regards
>   Shida Schubert
>=20
> Elwell, John wrote:
> > Shida,
> >
> > The statement that presence and IM remain the sole province=20
> of SIPPING=20
> > is clearly wrong and should be corrected.
> >
> > John
> >
> >  =20
> >> -----Original Message-----
> >> From: Shida Schubert [mailto:shida@ntt-at.com]
> >> Sent: 18 March 2007 07:58
> >> To: Elwell, John
> >> Cc: bliss@ietf.org
> >> Subject: Re: [BLISS] Charter updated
> >>
> >>
> >> John;
> >>
> >>  Thanks for your review.
> >>
> >>  SIMPLE is mentioned for its involvement/relationship in=20
> the guiding=20
> >> principles. Is it sufficient or do you suggest we add the=20
> >> relationship with the SIMPLE WG somewhere in the main body of the=20
> >> charter? If so I would appreciate any suggestions.
> >>
> >>  Thanks
> >>   Shida
> >>
> >>
> >> Elwell, John wrote:
> >>    =20
> >>> "...presence....IM....are
> >>> clearly out of scope for BLISS and remain the sole province
> >>>      =20
> >> of SIPPING"
> >>    =20
> >>> Doesn't SIMPLE figure here somewhere?
> >>>
> >>> John
> >>>
> >>>  =20
> >>>      =20
> >>>> -----Original Message-----
> >>>> From: Shida Schubert [mailto:shida@ntt-at.com]
> >>>> Sent: 16 March 2007 04:36
> >>>> To: bliss@ietf.org
> >>>> Subject: [BLISS] Charter updated
> >>>>
> >>>>
> >>>>  I just updated the charter, I know its kind of last=20
> minutes but I=20
> >>>> believe all the comments are reflected.
> >>>>
> >>>>  Diff from ver2 > ver 3 is available at=20
> >>>> http://www.bliss-ietf.org/charter.txt
> >>>>
> >>>>  Text version is available at=20
> http://www.bliss-ietf.org/diff2.html
> >>>>
> >>>>  Regards
> >>>>   Shida
> >>>>
> >>>> _______________________________________________
> >>>> BLISS mailing list
> >>>> BLISS@ietf.org
> >>>> https://www1.ietf.org/mailman/listinfo/bliss
> >>>>
> >>>>    =20
> >>>>        =20
> >>>  =20
> >>>      =20
> >
> >
> >  =20
>=20
>=20
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www1.ietf.org/mailman/listinfo/bliss
>=20

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



From bliss-bounces@ietf.org Mon Mar 19 04:36:44 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTDMC-0000xA-4w; Mon, 19 Mar 2007 04:36:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTDMA-0000x0-SY
	for bliss@ietf.org; Mon, 19 Mar 2007 04:36:42 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTDM5-00010h-GK
	for bliss@ietf.org; Mon, 19 Mar 2007 04:36:42 -0400
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JF500G3Y6KOC6@siemenscomms.co.uk> for bliss@ietf.org;
	Mon, 19 Mar 2007 08:36:24 +0000 (GMT)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <G8VCWCV2>; Mon, 19 Mar 2007 08:36:26 +0000
Content-return: allowed
Date: Mon, 19 Mar 2007 08:36:17 +0000
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [BLISS] Charter updated
To: Shida Schubert <shida@ntt-at.com>
Message-id: <50B1CBA96870A34799A506B2313F26670B4F5DFC@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
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

OK 

> -----Original Message-----
> From: Shida Schubert [mailto:shida@ntt-at.com] 
> Sent: 19 March 2007 07:55
> To: Elwell, John
> Cc: bliss@ietf.org
> Subject: Re: [BLISS] Charter updated
> 
> 
> John,
> 
>  How is something like this?
> 
> "SIP applications such as configuration, presence, SIP extensions for 
> IM, and session policy
> are clearly out of scope for BLISS and remain the sole province of 
> either SIPPING or SIMPLE."
> 
>  Regards
>   Shida Schubert
> 
> Elwell, John wrote:
> > Shida,
> >
> > The statement that presence and IM remain the sole province 
> of SIPPING is
> > clearly wrong and should be corrected.
> >
> > John 
> >
> >   
> >> -----Original Message-----
> >> From: Shida Schubert [mailto:shida@ntt-at.com] 
> >> Sent: 18 March 2007 07:58
> >> To: Elwell, John
> >> Cc: bliss@ietf.org
> >> Subject: Re: [BLISS] Charter updated
> >>
> >>
> >> John;
> >>
> >>  Thanks for your review.
> >>
> >>  SIMPLE is mentioned for its involvement/relationship in the
> >> guiding principles. Is it sufficient or do you suggest we add
> >> the relationship with the SIMPLE WG somewhere in the main
> >> body of the charter? If so I would appreciate any suggestions.
> >>
> >>  Thanks
> >>   Shida
> >>
> >>
> >> Elwell, John wrote:
> >>     
> >>> "...presence....IM....are 
> >>> clearly out of scope for BLISS and remain the sole province 
> >>>       
> >> of SIPPING"
> >>     
> >>> Doesn't SIMPLE figure here somewhere?
> >>>
> >>> John 
> >>>
> >>>   
> >>>       
> >>>> -----Original Message-----
> >>>> From: Shida Schubert [mailto:shida@ntt-at.com] 
> >>>> Sent: 16 March 2007 04:36
> >>>> To: bliss@ietf.org
> >>>> Subject: [BLISS] Charter updated
> >>>>
> >>>>
> >>>>  I just updated the charter, I know its kind of last minutes
> >>>> but I believe all the comments are reflected.
> >>>>
> >>>>  Diff from ver2 > ver 3 is available at 
> >>>> http://www.bliss-ietf.org/charter.txt
> >>>>
> >>>>  Text version is available at 
> http://www.bliss-ietf.org/diff2.html
> >>>>
> >>>>  Regards
> >>>>   Shida
> >>>>
> >>>> _______________________________________________
> >>>> BLISS mailing list
> >>>> BLISS@ietf.org
> >>>> https://www1.ietf.org/mailman/listinfo/bliss
> >>>>
> >>>>     
> >>>>         
> >>>   
> >>>       
> >
> >
> >   
> 

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



From bliss-bounces@ietf.org Mon Mar 19 04:59:28 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTDhy-0007m8-48; Mon, 19 Mar 2007 04:59:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTDhw-0007m2-T5
	for bliss@ietf.org; Mon, 19 Mar 2007 04:59:12 -0400
Received: from mail44.opentransfer.com ([71.18.216.13])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HTDhv-000499-Af
	for bliss@ietf.org; Mon, 19 Mar 2007 04:59:12 -0400
Received: (qmail 6054 invoked by uid 399); 19 Mar 2007 08:59:08 -0000
Received: from unknown (HELO ?130.129.20.251?) (130.129.20.251)
	by mail44.opentransfer.com with SMTP; 19 Mar 2007 08:59:08 -0000
Message-ID: <45FE50D9.1010708@sipstation.com>
Date: Mon, 19 Mar 2007 03:59:05 -0500
From: Alan Johnston <alan@sipstation.com>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens.com>
Subject: Re: [BLISS] Fwd: I-D ACTION:draft-johnston-bliss-mla-req-00.txt
References: <50B1CBA96870A34799A506B2313F26670B4F5D99@ntht201e.siemenscomms.co.uk>
In-Reply-To: <50B1CBA96870A34799A506B2313F26670B4F5D99@ntht201e.siemenscomms.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb
Cc: bliss@ietf.org, Mohsen Soroush-nejad <Mohsen.Soroushnejad@sylantro.com>,
	Venkatesh Venkataramanan <venkatesh@sylantro.com>,
	Anil Kumar <anil@yahoo-inc.com>
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

Hi John,

Thanks for your comments on the draft - see mine below.

Thanks,
Alan

Elwell, John wrote:
> Alan,
>
> Some of the terminology concerns I already made on draft=anil-sipping-bla
> apply also to this document, so I won't repeat them. 

Hopefully this draft suffers a little less, but we will fix this as well.

> Other comments:
>
> REQ-4: "UAs registering against the group AOR should be able
>    to learn about each other and join the appearance group."
> Why do UAs need to learn about each other? Isn't it just necessary for a UA
> to know that the AoR is a group AoR and therefore is shared by other UAs?
> Although specific solutions might require the UA to know about specific
> other UAs, I don't think this is a basic requirement. I don't think the
> solutions discussed in the draft require this.
>   

I guess you are correct.  If a UA registers against the AOR and never 
makes or receives a call, the other UAs don't care about it.  However, 
if it makes or receives a call, it needs to be known to the other UAs so 
that SIP call control operations can be performed.  If you agree with 
this, perhaps we can reword the requirement to reflect this.

> "REQ-5 The mechanism must scale for large numbers of appearances, n,
>    and large numbers of UAs, N, without introducing excessive messaging
>    traffic."
> One consequence of a large N is, depending on solution, the establishment of
> N early dialogs towards the UAC and N parallel ICE procedures, N parallel
> key management procedures, etc.. This might not be important for values of N
> of the order of 3-5, but with much larger values of N this could certainly
> be a problem. I assume this requirement is intended to cover this and to
> include messages in general (such as STUN and whatever in-band key
> management is used) as well as SIP messaging.
>   

This is a very interesting idea.  I agree that this requirement should 
include traffic such as ICE messaging and RTP keying.  I'm not sure we 
have good options for optimizing, though.

> "The use of a State Agent for the Dialog Package meets REQ-5."
> Well, I don't think it does, for reasons in my previous comment.
>
>   

Yes, a state agent does not help with N ICE and media path keying traffic. 

> The comparison of options and the conclusions that are reached seem
> reasonable to me. My only concern is the scalability to large values of N in
> environments where NAT traversal and media security are managed on an
> end-to-end basis, although it would work in environments where SBCs handle
> NAT traversal and where key management for media security is not done until
> one of the UAs answers.
>   

Well, we have discussed an alternative model in which instead of the 
INVITE being forked to all N endpoints, the endpoints first get a NOTIFY 
from the Appearance Agent.  If a UA wants to answer the call, it sends 
some kind of indication to the Appearance Agent which then causes the 
INVITE to get sent to the endpoint.  Now, this is a major change to the 
way UAs answer calls, but it might help reduce ICE and media path keying 
messaging.


> John
>
>
>
>
>
>  
>
>   
>> -----Original Message-----
>> From: Alan Johnston [mailto:alan@sipstation.com] 
>> Sent: 27 February 2007 21:13
>> To: bliss@ietf.org
>> Cc: Mohsen Soroush-nejad; Venkatesh Venkataramanan; Anil Kumar
>> Subject: [BLISS] Fwd: I-D ACTION:draft-johnston-bliss-mla-req-00.txt
>>
>> All,
>>
>> The authors of draft-anil-sipping-bla (which will be revised 
>> as -04 next 
>> week) have put together this draft discussing requirements and 
>> implementation options for set of features known as Bridged Line 
>> Appearance (BLA), Multiple Line Appearance (MLA), Single Line 
>> Extension, 
>> etc.
>>
>> Comments are most welcome.
>>
>> Thanks,
>> Alan
>>
>> -------- Original Message --------
>> Subject: 	I-D ACTION:draft-johnston-bliss-mla-req-00.txt
>> Date: 	Tue, 27 Feb 2007 15:50:03 -0500
>> From: 	Internet-Drafts@ietf.org
>> Reply-To: 	internet-drafts@ietf.org
>> To: 	i-d-announce@ietf.org
>>
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts 
>> directories.
>>
>>
>> 	Title		: Requirements and Implementation Options for
>>                           the Multiple Line Appearance Feature using 
>>                           the Session Initiation Protocol (SIP)
>> 	Author(s)	: A. Johnston, et al.
>> 	Filename	: draft-johnston-bliss-mla-req-00.txt
>> 	Pages		: 16
>> 	Date		: 2007-2-27
>> 	
>>    This document describes the requirements for implementation of a
>>    group telephony feature commonly known as Bridged Line Appearance
>>    (BLA) or Multiple Line Appearance, or Shared Call/Line Appearance
>>    (SCA).  When implemented using the Session Initiation 
>> Protocol (SIP),
>>    it is referred to as Multiple Appearances.  This feature 
>> is commonly
>>    offered in the IP Centrex services and IP-PBX offerings 
>> and is likely
>>    to be implemented on SIP IP telephones and SIP feature servers used
>>    in a business environment.  This document lists requirements and
>>    compares implementation options for this feature.
>>
>>
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-johnston-bliss-mla-r
>>     
> eq-00.txt
>   
>> To remove yourself from the I-D Announcement list, send a message to 
>> i-d-announce-request@ietf.org with the word unsubscribe in 
>> the body of 
>> the message. 
>> You can also visit 
>> https://www1.ietf.org/mailman/listinfo/I-D-announce 
>> to change your subscription settings.
>>
>> Internet-Drafts are also available by anonymous FTP. Login with the 
>> username "anonymous" and a password of your e-mail address. After 
>> logging in, type "cd internet-drafts" and then 
>> "get draft-johnston-bliss-mla-req-00.txt".
>>
>> A list of Internet-Drafts directories can be found in
>> http://www.ietf.org/shadow.html 
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>> Internet-Drafts can also be obtained by e-mail.
>>
>> Send a message to:
>> 	mailserv@ietf.org.
>> In the body type:
>> 	"FILE /internet-drafts/draft-johnston-bliss-mla-req-00.txt".
>> 	
>> NOTE:	The mail server at ietf.org can return the document in
>> 	MIME-encoded form by using the "mpack" utility.  To use this
>> 	feature, insert the command "ENCODING mime" before the "FILE"
>> 	command.  To decode the response(s), you will need "munpack" or
>> 	a MIME-compliant mail reader.  Different MIME-compliant 
>> mail readers
>> 	exhibit different behavior, especially when dealing with
>> 	"multipart" MIME messages (i.e. documents which have been split
>> 	up into multiple messages), so check your local documentation on
>> 	how to manipulate these messages.
>>
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Internet-Draft.
>>
>>
>>
>> _______________________________________________
>> BLISS mailing list
>> BLISS@ietf.org
>> https://www1.ietf.org/mailman/listinfo/bliss
>>
>>     
>
>
>   


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



From bliss-bounces@ietf.org Mon Mar 19 06:11:05 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTEpV-0006HN-Cg; Mon, 19 Mar 2007 06:11:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTEpU-0006HB-D6
	for bliss@ietf.org; Mon, 19 Mar 2007 06:11:04 -0400
Received: from mail120.messagelabs.com ([216.82.250.83])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HTEpS-0005kC-Np
	for bliss@ietf.org; Mon, 19 Mar 2007 06:11:04 -0400
X-VirusChecked: Checked
X-Env-Sender: mdolly@att.com
X-Msg-Ref: server-3.tower-120.messagelabs.com!1174299061!22108893!1
X-StarScan-Version: 5.5.10.7.1; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 7130 invoked from network); 19 Mar 2007 10:11:01 -0000
Received: from unknown (HELO attrh9i.attrh.att.com) (134.24.146.4)
	by server-3.tower-120.messagelabs.com with SMTP;
	19 Mar 2007 10:11:01 -0000
Received: from attrh.att.com (localhost [127.0.0.1])
	by attrh9i.attrh.att.com (8.13.8/8.13.8) with ESMTP id l2JA1lLU013015; 
	Mon, 19 Mar 2007 06:01:47 -0400 (EDT)
Received: from OCCLUST04EVS1.ugd.att.com (ocst07.ugd.att.com [135.38.164.12])
	by attrh9i.attrh.att.com (8.13.8/8.13.8) with ESMTP id
	l2JA1jug013003; Mon, 19 Mar 2007 06:01:45 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [BLISS] Fwd: I-D ACTION:draft-johnston-bliss-mla-req-00.txt
Date: Mon, 19 Mar 2007 05:10:58 -0500
Message-ID: <28F05913385EAC43AF019413F674A017101B77C7@OCCLUST04EVS1.ugd.att.com>
In-Reply-To: <45FE50D9.1010708@sipstation.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] Fwd: I-D ACTION:draft-johnston-bliss-mla-req-00.txt
Thread-Index: AcdqBOP3dmD0EWkyRTijjXvyNOcmBwACb7+A
References: <50B1CBA96870A34799A506B2313F26670B4F5D99@ntht201e.siemenscomms.co.uk>
	<45FE50D9.1010708@sipstation.com>
From: "DOLLY, MARTIN C, ATTLABS" <mdolly@att.com>
To: "Alan Johnston" <alan@sipstation.com>, <bliss@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: 
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

Alan=20

Section 6.2 "Call Originated by a UA in a BLA group", the first
paragraph states that "the UA just before allowing the user to place a
call,
shall send out a dialog event NOTIFY with state (trying). The User Agent
MUST wait for a 200 OK response from the State Agent, before it proceeds
with sending out the INVITE to the address entered by the end user."
This
places the State Agent in the critical path for whether or not a call
goes
through.  In a 911 scenario I don't know if we want to have a dependency
on
the responsiveness of the State Agent (which has to deal with many
SUBSCRIBEs and NOTIFYs as per this draft) before a 911 call (or some
other
type of emergency call) can go through. =20

Cheers,

Martin

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



From bliss-bounces@ietf.org Mon Mar 19 09:44:13 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTI9R-0003qE-DM; Mon, 19 Mar 2007 09:43:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTI9R-0003q8-0i
	for bliss@ietf.org; Mon, 19 Mar 2007 09:43:53 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTI9G-0000qN-Ag
	for bliss@ietf.org; Mon, 19 Mar 2007 09:43:53 -0400
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JF50044DKSI2G@siemenscomms.co.uk> for bliss@ietf.org;
	Mon, 19 Mar 2007 13:43:30 +0000 (GMT)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <G8VCWLH6>; Mon, 19 Mar 2007 13:43:32 +0000
Content-return: allowed
Date: Mon, 19 Mar 2007 13:43:24 +0000
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [BLISS] Fwd: I-D ACTION:draft-johnston-bliss-mla-req-00.txt
To: Alan Johnston <alan@sipstation.com>
Message-id: <50B1CBA96870A34799A506B2313F26670B56B951@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 223e3c753032a50d5dc4443c921c3fcd
Cc: bliss@ietf.org, Mohsen Soroush-nejad <Mohsen.Soroushnejad@sylantro.com>,
	Venkatesh Venkataramanan <venkatesh@sylantro.com>,
	Anil Kumar <anil@yahoo-inc.com>
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

Alan,

Thanks for your responses. See below.

John 

> -----Original Message-----
> From: Alan Johnston [mailto:alan@sipstation.com] 
> Sent: 19 March 2007 08:59
> To: Elwell, John
> Cc: bliss@ietf.org; Mohsen Soroush-nejad; Venkatesh 
> Venkataramanan; Anil Kumar
> Subject: Re: [BLISS] Fwd: I-D 
> ACTION:draft-johnston-bliss-mla-req-00.txt
> 
> Hi John,
> 
> Thanks for your comments on the draft - see mine below.
> 
> Thanks,
> Alan
> 
> Elwell, John wrote:
> > Alan,
> >
> > Some of the terminology concerns I already made on 
> draft=anil-sipping-bla
> > apply also to this document, so I won't repeat them. 
> 
> Hopefully this draft suffers a little less, but we will fix 
> this as well.
> 
> > Other comments:
> >
> > REQ-4: "UAs registering against the group AOR should be able
> >    to learn about each other and join the appearance group."
> > Why do UAs need to learn about each other? Isn't it just 
> necessary for a UA
> > to know that the AoR is a group AoR and therefore is shared 
> by other UAs?
> > Although specific solutions might require the UA to know 
> about specific
> > other UAs, I don't think this is a basic requirement. I 
> don't think the
> > solutions discussed in the draft require this.
> >   
> 
> I guess you are correct.  If a UA registers against the AOR and never 
> makes or receives a call, the other UAs don't care about it.  
> However, 
> if it makes or receives a call, it needs to be known to the 
> other UAs so 
> that SIP call control operations can be performed.  If you agree with 
> this, perhaps we can reword the requirement to reflect this.
[JRE] OK, if it makes or receives a call then the other UAs need sufficient
information to pick-up or join that call, but whether this requires the
other UAs to have this UA's identity depends on the particular solution.
Some rewording would help.

> 
> > "REQ-5 The mechanism must scale for large numbers of appearances, n,
> >    and large numbers of UAs, N, without introducing 
> excessive messaging
> >    traffic."
> > One consequence of a large N is, depending on solution, the 
> establishment of
> > N early dialogs towards the UAC and N parallel ICE 
> procedures, N parallel
> > key management procedures, etc.. This might not be 
> important for values of N
> > of the order of 3-5, but with much larger values of N this 
> could certainly
> > be a problem. I assume this requirement is intended to 
> cover this and to
> > include messages in general (such as STUN and whatever in-band key
> > management is used) as well as SIP messaging.
> >   
> 
> This is a very interesting idea.  I agree that this 
> requirement should 
> include traffic such as ICE messaging and RTP keying.  I'm 
> not sure we 
> have good options for optimizing, though.
> 
> > "The use of a State Agent for the Dialog Package meets REQ-5."
> > Well, I don't think it does, for reasons in my previous comment.
> >
> >   
> 
> Yes, a state agent does not help with N ICE and media path 
> keying traffic. 
> 
> > The comparison of options and the conclusions that are reached seem
> > reasonable to me. My only concern is the scalability to 
> large values of N in
> > environments where NAT traversal and media security are 
> managed on an
> > end-to-end basis, although it would work in environments 
> where SBCs handle
> > NAT traversal and where key management for media security 
> is not done until
> > one of the UAs answers.
> >   
> 
> Well, we have discussed an alternative model in which instead of the 
> INVITE being forked to all N endpoints, the endpoints first 
> get a NOTIFY 
> from the Appearance Agent.  If a UA wants to answer the call, 
> it sends 
> some kind of indication to the Appearance Agent which then causes the 
> INVITE to get sent to the endpoint.  Now, this is a major 
> change to the 
> way UAs answer calls, but it might help reduce ICE and media 
> path keying 
> messaging.
[JRE] The point is, I think we need both. For low values of N, the present
mechanism seems OK, but for larger values of N, I think there might need to
two classes of UA - those who really must receive a forked INVITE request
and those that can make do with a NOTIFY request- perhaps users less likely
to answer calls from that AoR who would be content with the longer
post-answer delays (and associated media clipping) associated with the
pick-up type operation (e.g., based on INVITE/Replaces) that would need to
occur.

> 
> 
> > John
> >
> >
> >
> >
> >
> >  
> >
> >   
> >> -----Original Message-----
> >> From: Alan Johnston [mailto:alan@sipstation.com] 
> >> Sent: 27 February 2007 21:13
> >> To: bliss@ietf.org
> >> Cc: Mohsen Soroush-nejad; Venkatesh Venkataramanan; Anil Kumar
> >> Subject: [BLISS] Fwd: I-D 
> ACTION:draft-johnston-bliss-mla-req-00.txt
> >>
> >> All,
> >>
> >> The authors of draft-anil-sipping-bla (which will be revised 
> >> as -04 next 
> >> week) have put together this draft discussing requirements and 
> >> implementation options for set of features known as Bridged Line 
> >> Appearance (BLA), Multiple Line Appearance (MLA), Single Line 
> >> Extension, 
> >> etc.
> >>
> >> Comments are most welcome.
> >>
> >> Thanks,
> >> Alan
> >>
> >> -------- Original Message --------
> >> Subject: 	I-D ACTION:draft-johnston-bliss-mla-req-00.txt
> >> Date: 	Tue, 27 Feb 2007 15:50:03 -0500
> >> From: 	Internet-Drafts@ietf.org
> >> Reply-To: 	internet-drafts@ietf.org
> >> To: 	i-d-announce@ietf.org
> >>
> >>
> >>
> >> A New Internet-Draft is available from the on-line Internet-Drafts 
> >> directories.
> >>
> >>
> >> 	Title		: Requirements and Implementation Options for
> >>                           the Multiple Line Appearance 
> Feature using 
> >>                           the Session Initiation Protocol (SIP)
> >> 	Author(s)	: A. Johnston, et al.
> >> 	Filename	: draft-johnston-bliss-mla-req-00.txt
> >> 	Pages		: 16
> >> 	Date		: 2007-2-27
> >> 	
> >>    This document describes the requirements for implementation of a
> >>    group telephony feature commonly known as Bridged Line 
> Appearance
> >>    (BLA) or Multiple Line Appearance, or Shared Call/Line 
> Appearance
> >>    (SCA).  When implemented using the Session Initiation 
> >> Protocol (SIP),
> >>    it is referred to as Multiple Appearances.  This feature 
> >> is commonly
> >>    offered in the IP Centrex services and IP-PBX offerings 
> >> and is likely
> >>    to be implemented on SIP IP telephones and SIP feature 
> servers used
> >>    in a business environment.  This document lists requirements and
> >>    compares implementation options for this feature.
> >>
> >>
> >>
> >> A URL for this Internet-Draft is:
> >> http://www.ietf.org/internet-drafts/draft-johnston-bliss-mla-r
> >>     
> > eq-00.txt
> >   
> >> To remove yourself from the I-D Announcement list, send a 
> message to 
> >> i-d-announce-request@ietf.org with the word unsubscribe in 
> >> the body of 
> >> the message. 
> >> You can also visit 
> >> https://www1.ietf.org/mailman/listinfo/I-D-announce 
> >> to change your subscription settings.
> >>
> >> Internet-Drafts are also available by anonymous FTP. Login 
> with the 
> >> username "anonymous" and a password of your e-mail address. After 
> >> logging in, type "cd internet-drafts" and then 
> >> "get draft-johnston-bliss-mla-req-00.txt".
> >>
> >> A list of Internet-Drafts directories can be found in
> >> http://www.ietf.org/shadow.html 
> >> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >>
> >> Internet-Drafts can also be obtained by e-mail.
> >>
> >> Send a message to:
> >> 	mailserv@ietf.org.
> >> In the body type:
> >> 	"FILE /internet-drafts/draft-johnston-bliss-mla-req-00.txt".
> >> 	
> >> NOTE:	The mail server at ietf.org can return the document in
> >> 	MIME-encoded form by using the "mpack" utility.  To use this
> >> 	feature, insert the command "ENCODING mime" before the "FILE"
> >> 	command.  To decode the response(s), you will need "munpack" or
> >> 	a MIME-compliant mail reader.  Different MIME-compliant 
> >> mail readers
> >> 	exhibit different behavior, especially when dealing with
> >> 	"multipart" MIME messages (i.e. documents which have been split
> >> 	up into multiple messages), so check your local documentation on
> >> 	how to manipulate these messages.
> >>
> >> Below is the data which will enable a MIME compliant mail reader
> >> implementation to automatically retrieve the ASCII version of the
> >> Internet-Draft.
> >>
> >>
> >>
> >> _______________________________________________
> >> BLISS mailing list
> >> BLISS@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/bliss
> >>
> >>     
> >
> >
> >   
> 

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



From bliss-bounces@ietf.org Mon Mar 19 10:45:41 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTJ6s-0007Wj-1N; Mon, 19 Mar 2007 10:45:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTJ6p-0007WV-Vv
	for bliss@ietf.org; Mon, 19 Mar 2007 10:45:15 -0400
Received: from ug-out-1314.google.com ([66.249.92.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTJ6m-0003zS-Na
	for bliss@ietf.org; Mon, 19 Mar 2007 10:45:15 -0400
Received: by ug-out-1314.google.com with SMTP id 72so1211705ugd
	for <bliss@ietf.org>; Mon, 19 Mar 2007 07:45:12 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=MucmM5UEe//BaWhILKleKQHZr9onC5L6BhKJDly2Zu8g733CsOEFpYGVHbHh1dq+jv8EZR8vm2WxCSp20TANDe1rVBUEvybwLOUWGPcNb/NKheaCfpmEus59uq9FzHFnEdhaDjTj5rR+kuZgePJVx15n/qfjcc8HcfBDQDTZJZk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=qSKBMW79WxBIMPRkWw9BUhelaFdUF9q9T2wO4YOidQEyC2vjrwL4egtMujXecwa8NZYntRrq0Io38afM57ddAE7N72cMPcFm82y8ubzE5SKaGcw56MbdIwof+1yjjpc8yG72GhQ2iIaQ1bXkrPj3A4/lLH8yraTVCkbRyL7K6x0=
Received: by 10.65.59.11 with SMTP id m11mr9080186qbk.1174315511272;
	Mon, 19 Mar 2007 07:45:11 -0700 (PDT)
Received: by 10.65.218.16 with HTTP; Mon, 19 Mar 2007 07:45:11 -0700 (PDT)
Message-ID: <4ff4e7370703190745l6449e6demd846315209d0f05e@mail.gmail.com>
Date: Mon, 19 Mar 2007 07:45:11 -0700
From: Venkatesh <vvenkatar@gmail.com>
To: "Elwell, John" <john.elwell@siemens.com>
Subject: Re: [BLISS] Fwd: I-D ACTION:draft-johnston-bliss-mla-req-00.txt
In-Reply-To: <50B1CBA96870A34799A506B2313F26670B56B951@ntht201e.siemenscomms.co.uk>
MIME-Version: 1.0
References: <50B1CBA96870A34799A506B2313F26670B56B951@ntht201e.siemenscomms.co.uk>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 5b943e80df8c8cad631fd60298783617
Cc: bliss@ietf.org, Mohsen Soroush-nejad <Mohsen.Soroushnejad@sylantro.com>,
	Anil Kumar <anil@yahoo-inc.com>,
	Venkatesh Venkataramanan <venkatesh@sylantro.com>
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>
Content-Type: multipart/mixed; boundary="===============0854403348=="
Errors-To: bliss-bounces@ietf.org

--===============0854403348==
Content-Type: multipart/alternative; 
	boundary="----=_Part_27846_33346250.1174315511180"

------=_Part_27846_33346250.1174315511180
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

John:

IMHO, we should try to avoid multiple ways for supporting the feature. This
is a sure recipe for interoperability issues which BLISS is trying to
address in the first place. Believe using NOTIFY's instead of forked
INVITE's seem to solve your problem with ICE. I am not sure I understand
your concern about media cut thru's with this solution. Just for the record,
the alternative solution we had discussed is as below:

The State Agent is the only entity that REGISTER's on behalf of the BLA AoR.
All other UA's simply SUBSCRIBE to the State-Agent. On receipt of an
incoming call, the State-Agent is the only entity that receives the INVITE
request. It sends out a NOTIFY to all the UA's in the BLA group. Any UA that
intends to 'answer' this call uses INVITE with Replaces header using the
dialog identifiers in the NOTIFY request.

Thanks,
Venkatesh


On 3/19/07, Elwell, John <john.elwell@siemens.com> wrote:
>
> Alan,
>
> Thanks for your responses. See below.
>
> John
>
> > -----Original Message-----
> > From: Alan Johnston [mailto:alan@sipstation.com]
> > Sent: 19 March 2007 08:59
> > To: Elwell, John
> > Cc: bliss@ietf.org; Mohsen Soroush-nejad; Venkatesh
> > Venkataramanan; Anil Kumar
> > Subject: Re: [BLISS] Fwd: I-D
> > ACTION:draft-johnston-bliss-mla-req-00.txt
> >
> > Hi John,
> >
> > Thanks for your comments on the draft - see mine below.
> >
> > Thanks,
> > Alan
> >
> > Elwell, John wrote:
> > > Alan,
> > >
> > > Some of the terminology concerns I already made on
> > draft=anil-sipping-bla
> > > apply also to this document, so I won't repeat them.
> >
> > Hopefully this draft suffers a little less, but we will fix
> > this as well.
> >
> > > Other comments:
> > >
> > > REQ-4: "UAs registering against the group AOR should be able
> > >    to learn about each other and join the appearance group."
> > > Why do UAs need to learn about each other? Isn't it just
> > necessary for a UA
> > > to know that the AoR is a group AoR and therefore is shared
> > by other UAs?
> > > Although specific solutions might require the UA to know
> > about specific
> > > other UAs, I don't think this is a basic requirement. I
> > don't think the
> > > solutions discussed in the draft require this.
> > >
> >
> > I guess you are correct.  If a UA registers against the AOR and never
> > makes or receives a call, the other UAs don't care about it.
> > However,
> > if it makes or receives a call, it needs to be known to the
> > other UAs so
> > that SIP call control operations can be performed.  If you agree with
> > this, perhaps we can reword the requirement to reflect this.
> [JRE] OK, if it makes or receives a call then the other UAs need
> sufficient
> information to pick-up or join that call, but whether this requires the
> other UAs to have this UA's identity depends on the particular solution.
> Some rewording would help.
>
> >
> > > "REQ-5 The mechanism must scale for large numbers of appearances, n,
> > >    and large numbers of UAs, N, without introducing
> > excessive messaging
> > >    traffic."
> > > One consequence of a large N is, depending on solution, the
> > establishment of
> > > N early dialogs towards the UAC and N parallel ICE
> > procedures, N parallel
> > > key management procedures, etc.. This might not be
> > important for values of N
> > > of the order of 3-5, but with much larger values of N this
> > could certainly
> > > be a problem. I assume this requirement is intended to
> > cover this and to
> > > include messages in general (such as STUN and whatever in-band key
> > > management is used) as well as SIP messaging.
> > >
> >
> > This is a very interesting idea.  I agree that this
> > requirement should
> > include traffic such as ICE messaging and RTP keying.  I'm
> > not sure we
> > have good options for optimizing, though.
> >
> > > "The use of a State Agent for the Dialog Package meets REQ-5."
> > > Well, I don't think it does, for reasons in my previous comment.
> > >
> > >
> >
> > Yes, a state agent does not help with N ICE and media path
> > keying traffic.
> >
> > > The comparison of options and the conclusions that are reached seem
> > > reasonable to me. My only concern is the scalability to
> > large values of N in
> > > environments where NAT traversal and media security are
> > managed on an
> > > end-to-end basis, although it would work in environments
> > where SBCs handle
> > > NAT traversal and where key management for media security
> > is not done until
> > > one of the UAs answers.
> > >
> >
> > Well, we have discussed an alternative model in which instead of the
> > INVITE being forked to all N endpoints, the endpoints first
> > get a NOTIFY
> > from the Appearance Agent.  If a UA wants to answer the call,
> > it sends
> > some kind of indication to the Appearance Agent which then causes the
> > INVITE to get sent to the endpoint.  Now, this is a major
> > change to the
> > way UAs answer calls, but it might help reduce ICE and media
> > path keying
> > messaging.
> [JRE] The point is, I think we need both. For low values of N, the present
> mechanism seems OK, but for larger values of N, I think there might need
> to
> two classes of UA - those who really must receive a forked INVITE request
> and those that can make do with a NOTIFY request- perhaps users less
> likely
> to answer calls from that AoR who would be content with the longer
> post-answer delays (and associated media clipping) associated with the
> pick-up type operation (e.g., based on INVITE/Replaces) that would need to
> occur.
>
> >
> >
> > > John
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >> -----Original Message-----
> > >> From: Alan Johnston [mailto:alan@sipstation.com]
> > >> Sent: 27 February 2007 21:13
> > >> To: bliss@ietf.org
> > >> Cc: Mohsen Soroush-nejad; Venkatesh Venkataramanan; Anil Kumar
> > >> Subject: [BLISS] Fwd: I-D
> > ACTION:draft-johnston-bliss-mla-req-00.txt
> > >>
> > >> All,
> > >>
> > >> The authors of draft-anil-sipping-bla (which will be revised
> > >> as -04 next
> > >> week) have put together this draft discussing requirements and
> > >> implementation options for set of features known as Bridged Line
> > >> Appearance (BLA), Multiple Line Appearance (MLA), Single Line
> > >> Extension,
> > >> etc.
> > >>
> > >> Comments are most welcome.
> > >>
> > >> Thanks,
> > >> Alan
> > >>
> > >> -------- Original Message --------
> > >> Subject:   I-D ACTION:draft-johnston-bliss-mla-req-00.txt
> > >> Date:      Tue, 27 Feb 2007 15:50:03 -0500
> > >> From:      Internet-Drafts@ietf.org
> > >> Reply-To:  internet-drafts@ietf.org
> > >> To:        i-d-announce@ietf.org
> > >>
> > >>
> > >>
> > >> A New Internet-Draft is available from the on-line Internet-Drafts
> > >> directories.
> > >>
> > >>
> > >>    Title           : Requirements and Implementation Options for
> > >>                           the Multiple Line Appearance
> > Feature using
> > >>                           the Session Initiation Protocol (SIP)
> > >>    Author(s)       : A. Johnston, et al.
> > >>    Filename        : draft-johnston-bliss-mla-req-00.txt
> > >>    Pages           : 16
> > >>    Date            : 2007-2-27
> > >>
> > >>    This document describes the requirements for implementation of a
> > >>    group telephony feature commonly known as Bridged Line
> > Appearance
> > >>    (BLA) or Multiple Line Appearance, or Shared Call/Line
> > Appearance
> > >>    (SCA).  When implemented using the Session Initiation
> > >> Protocol (SIP),
> > >>    it is referred to as Multiple Appearances.  This feature
> > >> is commonly
> > >>    offered in the IP Centrex services and IP-PBX offerings
> > >> and is likely
> > >>    to be implemented on SIP IP telephones and SIP feature
> > servers used
> > >>    in a business environment.  This document lists requirements and
> > >>    compares implementation options for this feature.
> > >>
> > >>
> > >>
> > >> A URL for this Internet-Draft is:
> > >> http://www.ietf.org/internet-drafts/draft-johnston-bliss-mla-r
> > >>
> > > eq-00.txt
> > >
> > >> To remove yourself from the I-D Announcement list, send a
> > message to
> > >> i-d-announce-request@ietf.org with the word unsubscribe in
> > >> the body of
> > >> the message.
> > >> You can also visit
> > >> https://www1.ietf.org/mailman/listinfo/I-D-announce
> > >> to change your subscription settings.
> > >>
> > >> Internet-Drafts are also available by anonymous FTP. Login
> > with the
> > >> username "anonymous" and a password of your e-mail address. After
> > >> logging in, type "cd internet-drafts" and then
> > >> "get draft-johnston-bliss-mla-req-00.txt".
> > >>
> > >> A list of Internet-Drafts directories can be found in
> > >> http://www.ietf.org/shadow.html
> > >> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> > >>
> > >> Internet-Drafts can also be obtained by e-mail.
> > >>
> > >> Send a message to:
> > >>    mailserv@ietf.org.
> > >> In the body type:
> > >>    "FILE /internet-drafts/draft-johnston-bliss-mla-req-00.txt".
> > >>
> > >> NOTE:      The mail server at ietf.org can return the document in
> > >>    MIME-encoded form by using the "mpack" utility.  To use this
> > >>    feature, insert the command "ENCODING mime" before the "FILE"
> > >>    command.  To decode the response(s), you will need "munpack" or
> > >>    a MIME-compliant mail reader.  Different MIME-compliant
> > >> mail readers
> > >>    exhibit different behavior, especially when dealing with
> > >>    "multipart" MIME messages (i.e. documents which have been split
> > >>    up into multiple messages), so check your local documentation on
> > >>    how to manipulate these messages.
> > >>
> > >> Below is the data which will enable a MIME compliant mail reader
> > >> implementation to automatically retrieve the ASCII version of the
> > >> Internet-Draft.
> > >>
> > >>
> > >>
> > >> _______________________________________________
> > >> BLISS mailing list
> > >> BLISS@ietf.org
> > >> https://www1.ietf.org/mailman/listinfo/bliss
> > >>
> > >>
> > >
> > >
> > >
> >
>
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www1.ietf.org/mailman/listinfo/bliss
>

------=_Part_27846_33346250.1174315511180
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>John:<br>&nbsp;</div>
<div>IMHO, we should try to avoid multiple ways for supporting the feature. This is a sure recipe for interoperability issues which BLISS is trying to address in the first place. Believe using NOTIFY&#39;s instead of forked INVITE&#39;s seem to solve your problem with ICE. I am not sure I understand your concern about media cut thru&#39;s with this solution. Just for the record, the alternative solution we had discussed is as below:
</div>
<div>&nbsp;</div>
<div>The State Agent is the only entity that REGISTER&#39;s on behalf of the BLA AoR. All other UA&#39;s simply SUBSCRIBE to the State-Agent. On receipt of an incoming call, the State-Agent is the only entity that receives the INVITE request. It sends out a NOTIFY to all the UA&#39;s in the BLA group. Any UA that intends to &#39;answer&#39; this call uses INVITE with Replaces header using the dialog identifiers in the NOTIFY request.
</div>
<div>&nbsp;</div>
<div>Thanks,</div>
<div>Venkatesh<br><br>&nbsp;</div>
<div><span class="gmail_quote">On 3/19/07, <b class="gmail_sendername">Elwell, John</b> &lt;<a href="mailto:john.elwell@siemens.com">john.elwell@siemens.com</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Alan,<br><br>Thanks for your responses. See below.<br><br>John<br><br>&gt; -----Original Message-----<br>&gt; From: Alan Johnston [mailto:
<a href="mailto:alan@sipstation.com">alan@sipstation.com</a>]<br>&gt; Sent: 19 March 2007 08:59<br>&gt; To: Elwell, John<br>&gt; Cc: <a href="mailto:bliss@ietf.org">bliss@ietf.org</a>; Mohsen Soroush-nejad; Venkatesh<br>&gt; Venkataramanan; Anil Kumar
<br>&gt; Subject: Re: [BLISS] Fwd: I-D<br>&gt; ACTION:draft-johnston-bliss-mla-req-00.txt<br>&gt;<br>&gt; Hi John,<br>&gt;<br>&gt; Thanks for your comments on the draft - see mine below.<br>&gt;<br>&gt; Thanks,<br>&gt; Alan
<br>&gt;<br>&gt; Elwell, John wrote:<br>&gt; &gt; Alan,<br>&gt; &gt;<br>&gt; &gt; Some of the terminology concerns I already made on<br>&gt; draft=anil-sipping-bla<br>&gt; &gt; apply also to this document, so I won&#39;t repeat them.
<br>&gt;<br>&gt; Hopefully this draft suffers a little less, but we will fix<br>&gt; this as well.<br>&gt;<br>&gt; &gt; Other comments:<br>&gt; &gt;<br>&gt; &gt; REQ-4: &quot;UAs registering against the group AOR should be able
<br>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;to learn about each other and join the appearance group.&quot;<br>&gt; &gt; Why do UAs need to learn about each other? Isn&#39;t it just<br>&gt; necessary for a UA<br>&gt; &gt; to know that the AoR is a group AoR and therefore is shared
<br>&gt; by other UAs?<br>&gt; &gt; Although specific solutions might require the UA to know<br>&gt; about specific<br>&gt; &gt; other UAs, I don&#39;t think this is a basic requirement. I<br>&gt; don&#39;t think the<br>&gt; &gt; solutions discussed in the draft require this.
<br>&gt; &gt;<br>&gt;<br>&gt; I guess you are correct.&nbsp;&nbsp;If a UA registers against the AOR and never<br>&gt; makes or receives a call, the other UAs don&#39;t care about it.<br>&gt; However,<br>&gt; if it makes or receives a call, it needs to be known to the
<br>&gt; other UAs so<br>&gt; that SIP call control operations can be performed.&nbsp;&nbsp;If you agree with<br>&gt; this, perhaps we can reword the requirement to reflect this.<br>[JRE] OK, if it makes or receives a call then the other UAs need sufficient
<br>information to pick-up or join that call, but whether this requires the<br>other UAs to have this UA&#39;s identity depends on the particular solution.<br>Some rewording would help.<br><br>&gt;<br>&gt; &gt; &quot;REQ-5 The mechanism must scale for large numbers of appearances, n,
<br>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;and large numbers of UAs, N, without introducing<br>&gt; excessive messaging<br>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;traffic.&quot;<br>&gt; &gt; One consequence of a large N is, depending on solution, the<br>&gt; establishment of
<br>&gt; &gt; N early dialogs towards the UAC and N parallel ICE<br>&gt; procedures, N parallel<br>&gt; &gt; key management procedures, etc.. This might not be<br>&gt; important for values of N<br>&gt; &gt; of the order of 3-5, but with much larger values of N this
<br>&gt; could certainly<br>&gt; &gt; be a problem. I assume this requirement is intended to<br>&gt; cover this and to<br>&gt; &gt; include messages in general (such as STUN and whatever in-band key<br>&gt; &gt; management is used) as well as SIP messaging.
<br>&gt; &gt;<br>&gt;<br>&gt; This is a very interesting idea.&nbsp;&nbsp;I agree that this<br>&gt; requirement should<br>&gt; include traffic such as ICE messaging and RTP keying.&nbsp;&nbsp;I&#39;m<br>&gt; not sure we<br>&gt; have good options for optimizing, though.
<br>&gt;<br>&gt; &gt; &quot;The use of a State Agent for the Dialog Package meets REQ-5.&quot;<br>&gt; &gt; Well, I don&#39;t think it does, for reasons in my previous comment.<br>&gt; &gt;<br>&gt; &gt;<br>&gt;<br>&gt; Yes, a state agent does not help with N ICE and media path
<br>&gt; keying traffic.<br>&gt;<br>&gt; &gt; The comparison of options and the conclusions that are reached seem<br>&gt; &gt; reasonable to me. My only concern is the scalability to<br>&gt; large values of N in<br>&gt; &gt; environments where NAT traversal and media security are
<br>&gt; managed on an<br>&gt; &gt; end-to-end basis, although it would work in environments<br>&gt; where SBCs handle<br>&gt; &gt; NAT traversal and where key management for media security<br>&gt; is not done until<br>&gt; &gt; one of the UAs answers.
<br>&gt; &gt;<br>&gt;<br>&gt; Well, we have discussed an alternative model in which instead of the<br>&gt; INVITE being forked to all N endpoints, the endpoints first<br>&gt; get a NOTIFY<br>&gt; from the Appearance Agent.&nbsp;&nbsp;If a UA wants to answer the call,
<br>&gt; it sends<br>&gt; some kind of indication to the Appearance Agent which then causes the<br>&gt; INVITE to get sent to the endpoint.&nbsp;&nbsp;Now, this is a major<br>&gt; change to the<br>&gt; way UAs answer calls, but it might help reduce ICE and media
<br>&gt; path keying<br>&gt; messaging.<br>[JRE] The point is, I think we need both. For low values of N, the present<br>mechanism seems OK, but for larger values of N, I think there might need to<br>two classes of UA - those who really must receive a forked INVITE request
<br>and those that can make do with a NOTIFY request- perhaps users less likely<br>to answer calls from that AoR who would be content with the longer<br>post-answer delays (and associated media clipping) associated with the
<br>pick-up type operation (e.g., based on INVITE/Replaces) that would need to<br>occur.<br><br>&gt;<br>&gt;<br>&gt; &gt; John<br>&gt; &gt;<br>&gt; &gt;<br>&gt; &gt;<br>&gt; &gt;<br>&gt; &gt;<br>&gt; &gt;<br>&gt; &gt;<br>
&gt; &gt;<br>&gt; &gt;&gt; -----Original Message-----<br>&gt; &gt;&gt; From: Alan Johnston [mailto:<a href="mailto:alan@sipstation.com">alan@sipstation.com</a>]<br>&gt; &gt;&gt; Sent: 27 February 2007 21:13<br>&gt; &gt;&gt; To: 
<a href="mailto:bliss@ietf.org">bliss@ietf.org</a><br>&gt; &gt;&gt; Cc: Mohsen Soroush-nejad; Venkatesh Venkataramanan; Anil Kumar<br>&gt; &gt;&gt; Subject: [BLISS] Fwd: I-D<br>&gt; ACTION:draft-johnston-bliss-mla-req-00.txt
<br>&gt; &gt;&gt;<br>&gt; &gt;&gt; All,<br>&gt; &gt;&gt;<br>&gt; &gt;&gt; The authors of draft-anil-sipping-bla (which will be revised<br>&gt; &gt;&gt; as -04 next<br>&gt; &gt;&gt; week) have put together this draft discussing requirements and
<br>&gt; &gt;&gt; implementation options for set of features known as Bridged Line<br>&gt; &gt;&gt; Appearance (BLA), Multiple Line Appearance (MLA), Single Line<br>&gt; &gt;&gt; Extension,<br>&gt; &gt;&gt; etc.<br>&gt; &gt;&gt;
<br>&gt; &gt;&gt; Comments are most welcome.<br>&gt; &gt;&gt;<br>&gt; &gt;&gt; Thanks,<br>&gt; &gt;&gt; Alan<br>&gt; &gt;&gt;<br>&gt; &gt;&gt; -------- Original Message --------<br>&gt; &gt;&gt; Subject:&nbsp;&nbsp; I-D ACTION:draft-johnston-bliss-mla-req-00.txt
<br>&gt; &gt;&gt; Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Tue, 27 Feb 2007 15:50:03 -0500<br>&gt; &gt;&gt; From:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a><br>&gt; &gt;&gt; Reply-To:&nbsp;&nbsp;<a href="mailto:internet-drafts@ietf.org">
internet-drafts@ietf.org</a><br>&gt; &gt;&gt; To:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a><br>&gt; &gt;&gt;<br>&gt; &gt;&gt;<br>&gt; &gt;&gt;<br>&gt; &gt;&gt; A New Internet-Draft is available from the on-line Internet-Drafts
<br>&gt; &gt;&gt; directories.<br>&gt; &gt;&gt;<br>&gt; &gt;&gt;<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Requirements and Implementation Options for<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the Multiple Line Appearance<br>
&gt; Feature using<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the Session Initiation Protocol (SIP)<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : A. Johnston, et al.<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: draft-johnston-bliss-mla-req-00.txt
<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 16<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 2007-2-27<br>&gt; &gt;&gt;<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;This document describes the requirements for implementation of a<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;group telephony feature commonly known as Bridged Line
<br>&gt; Appearance<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;(BLA) or Multiple Line Appearance, or Shared Call/Line<br>&gt; Appearance<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;(SCA).&nbsp;&nbsp;When implemented using the Session Initiation<br>&gt; &gt;&gt; Protocol (SIP),<br>
&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;it is referred to as Multiple Appearances.&nbsp;&nbsp;This feature<br>&gt; &gt;&gt; is commonly<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;offered in the IP Centrex services and IP-PBX offerings<br>&gt; &gt;&gt; and is likely<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;to be implemented on SIP IP telephones and SIP feature
<br>&gt; servers used<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;in a business environment.&nbsp;&nbsp;This document lists requirements and<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;compares implementation options for this feature.<br>&gt; &gt;&gt;<br>&gt; &gt;&gt;<br>&gt; &gt;&gt;
<br>&gt; &gt;&gt; A URL for this Internet-Draft is:<br>&gt; &gt;&gt; <a href="http://www.ietf.org/internet-drafts/draft-johnston-bliss-mla-r">http://www.ietf.org/internet-drafts/draft-johnston-bliss-mla-r</a><br>&gt; &gt;&gt;
<br>&gt; &gt; eq-00.txt<br>&gt; &gt;<br>&gt; &gt;&gt; To remove yourself from the I-D Announcement list, send a<br>&gt; message to<br>&gt; &gt;&gt; <a href="mailto:i-d-announce-request@ietf.org">i-d-announce-request@ietf.org
</a> with the word unsubscribe in<br>&gt; &gt;&gt; the body of<br>&gt; &gt;&gt; the message.<br>&gt; &gt;&gt; You can also visit<br>&gt; &gt;&gt; <a href="https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1.ietf.org/mailman/listinfo/I-D-announce
</a><br>&gt; &gt;&gt; to change your subscription settings.<br>&gt; &gt;&gt;<br>&gt; &gt;&gt; Internet-Drafts are also available by anonymous FTP. Login<br>&gt; with the<br>&gt; &gt;&gt; username &quot;anonymous&quot; and a password of your e-mail address. After
<br>&gt; &gt;&gt; logging in, type &quot;cd internet-drafts&quot; and then<br>&gt; &gt;&gt; &quot;get draft-johnston-bliss-mla-req-00.txt&quot;.<br>&gt; &gt;&gt;<br>&gt; &gt;&gt; A list of Internet-Drafts directories can be found in
<br>&gt; &gt;&gt; <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a><br>&gt; &gt;&gt; or <a href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br>&gt; &gt;&gt;
<br>&gt; &gt;&gt; Internet-Drafts can also be obtained by e-mail.<br>&gt; &gt;&gt;<br>&gt; &gt;&gt; Send a message to:<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;<a href="mailto:mailserv@ietf.org">mailserv@ietf.org</a>.<br>&gt; &gt;&gt; In the body type:
<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&quot;FILE /internet-drafts/draft-johnston-bliss-mla-req-00.txt&quot;.<br>&gt; &gt;&gt;<br>&gt; &gt;&gt; NOTE:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The mail server at <a href="http://ietf.org">ietf.org</a> can return the document in
<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;MIME-encoded form by using the &quot;mpack&quot; utility.&nbsp;&nbsp;To use this<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;feature, insert the command &quot;ENCODING mime&quot; before the &quot;FILE&quot;<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;command.&nbsp;&nbsp;To decode the response(s), you will need &quot;munpack&quot; or
<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;a MIME-compliant mail reader.&nbsp;&nbsp;Different MIME-compliant<br>&gt; &gt;&gt; mail readers<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;exhibit different behavior, especially when dealing with<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&quot;multipart&quot; MIME messages (
i.e. documents which have been split<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;up into multiple messages), so check your local documentation on<br>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;how to manipulate these messages.<br>&gt; &gt;&gt;<br>&gt; &gt;&gt; Below is the data which will enable a MIME compliant mail reader
<br>&gt; &gt;&gt; implementation to automatically retrieve the ASCII version of the<br>&gt; &gt;&gt; Internet-Draft.<br>&gt; &gt;&gt;<br>&gt; &gt;&gt;<br>&gt; &gt;&gt;<br>&gt; &gt;&gt; _______________________________________________
<br>&gt; &gt;&gt; BLISS mailing list<br>&gt; &gt;&gt; <a href="mailto:BLISS@ietf.org">BLISS@ietf.org</a><br>&gt; &gt;&gt; <a href="https://www1.ietf.org/mailman/listinfo/bliss">https://www1.ietf.org/mailman/listinfo/bliss
</a><br>&gt; &gt;&gt;<br>&gt; &gt;&gt;<br>&gt; &gt;<br>&gt; &gt;<br>&gt; &gt;<br>&gt;<br><br>_______________________________________________<br>BLISS mailing list<br><a href="mailto:BLISS@ietf.org">BLISS@ietf.org</a><br><a href="https://www1.ietf.org/mailman/listinfo/bliss">
https://www1.ietf.org/mailman/listinfo/bliss</a><br></blockquote></div><br>

------=_Part_27846_33346250.1174315511180--


--===============0854403348==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0854403348==--




From bliss-bounces@ietf.org Mon Mar 19 13:18:33 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTLUv-0004Kp-4D; Mon, 19 Mar 2007 13:18:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTLUt-0004Jm-BU
	for bliss@ietf.org; Mon, 19 Mar 2007 13:18:15 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HTLUe-0007Cj-5b
	for bliss@ietf.org; Mon, 19 Mar 2007 13:18:15 -0400
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JF500D1TUPM1R@siemenscomms.co.uk> for bliss@ietf.org;
	Mon, 19 Mar 2007 17:17:46 +0000 (GMT)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <G8VCWR66>; Mon, 19 Mar 2007 17:17:48 +0000
Content-return: allowed
Date: Mon, 19 Mar 2007 17:17:44 +0000
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [BLISS] Fwd: I-D ACTION:draft-johnston-bliss-mla-req-00.txt
To: Venkatesh <vvenkatar@gmail.com>
Message-id: <50B1CBA96870A34799A506B2313F26670B56BC58@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b83962958e2d910ed948e2f9e138d171
Cc: bliss@ietf.org, Mohsen Soroush-nejad <Mohsen.Soroushnejad@sylantro.com>,
	Anil Kumar <anil@yahoo-inc.com>,
	Venkatesh Venkataramanan <venkatesh@sylantro.com>
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>
Content-Type: multipart/mixed; boundary="===============1394776122=="
Errors-To: bliss-bounces@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============1394776122==
Content-return: allowed
Content-type: multipart/alternative;
	boundary="Boundary_(ID_CBDqo6hNsaHu5UYZBrbM1g)"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--Boundary_(ID_CBDqo6hNsaHu5UYZBrbM1g)
Content-type: text/plain
Content-transfer-encoding: 7BIT

Venkatesh,
 
The critical thing is how large can N be - I think it just said "large" in
the draft. Can you quantify it?
 
John


  _____  

From: Venkatesh [mailto:vvenkatar@gmail.com] 
Sent: 19 March 2007 14:45
To: Elwell, John
Cc: Alan Johnston; bliss@ietf.org; Mohsen Soroush-nejad; Venkatesh
Venkataramanan; Anil Kumar
Subject: Re: [BLISS] Fwd: I-D ACTION:draft-johnston-bliss-mla-req-00.txt


John:
 
IMHO, we should try to avoid multiple ways for supporting the feature. This
is a sure recipe for interoperability issues which BLISS is trying to
address in the first place. Believe using NOTIFY's instead of forked
INVITE's seem to solve your problem with ICE. I am not sure I understand
your concern about media cut thru's with this solution. Just for the record,
the alternative solution we had discussed is as below: 
 
The State Agent is the only entity that REGISTER's on behalf of the BLA AoR.
All other UA's simply SUBSCRIBE to the State-Agent. On receipt of an
incoming call, the State-Agent is the only entity that receives the INVITE
request. It sends out a NOTIFY to all the UA's in the BLA group. Any UA that
intends to 'answer' this call uses INVITE with Replaces header using the
dialog identifiers in the NOTIFY request. 
 
Thanks,
Venkatesh

 
On 3/19/07, Elwell, John <john.elwell@siemens.com
<mailto:john.elwell@siemens.com> > wrote: 

Alan,

Thanks for your responses. See below.

John

> -----Original Message-----
> From: Alan Johnston [mailto: alan@sipstation.com
<mailto:alan@sipstation.com> ]
> Sent: 19 March 2007 08:59
> To: Elwell, John
> Cc: bliss@ietf.org <mailto:bliss@ietf.org> ; Mohsen Soroush-nejad;
Venkatesh
> Venkataramanan; Anil Kumar 
> Subject: Re: [BLISS] Fwd: I-D
> ACTION:draft-johnston-bliss-mla-req-00.txt
>
> Hi John,
>
> Thanks for your comments on the draft - see mine below.
>
> Thanks,
> Alan 
>
> Elwell, John wrote:
> > Alan,
> >
> > Some of the terminology concerns I already made on
> draft=anil-sipping-bla
> > apply also to this document, so I won't repeat them. 
>
> Hopefully this draft suffers a little less, but we will fix
> this as well.
>
> > Other comments:
> >
> > REQ-4: "UAs registering against the group AOR should be able 
> >    to learn about each other and join the appearance group."
> > Why do UAs need to learn about each other? Isn't it just
> necessary for a UA
> > to know that the AoR is a group AoR and therefore is shared 
> by other UAs?
> > Although specific solutions might require the UA to know
> about specific
> > other UAs, I don't think this is a basic requirement. I
> don't think the
> > solutions discussed in the draft require this. 
> >
>
> I guess you are correct.  If a UA registers against the AOR and never
> makes or receives a call, the other UAs don't care about it.
> However,
> if it makes or receives a call, it needs to be known to the 
> other UAs so
> that SIP call control operations can be performed.  If you agree with
> this, perhaps we can reword the requirement to reflect this.
[JRE] OK, if it makes or receives a call then the other UAs need sufficient 
information to pick-up or join that call, but whether this requires the
other UAs to have this UA's identity depends on the particular solution.
Some rewording would help.

>
> > "REQ-5 The mechanism must scale for large numbers of appearances, n, 
> >    and large numbers of UAs, N, without introducing
> excessive messaging
> >    traffic."
> > One consequence of a large N is, depending on solution, the
> establishment of 
> > N early dialogs towards the UAC and N parallel ICE
> procedures, N parallel
> > key management procedures, etc.. This might not be
> important for values of N
> > of the order of 3-5, but with much larger values of N this 
> could certainly
> > be a problem. I assume this requirement is intended to
> cover this and to
> > include messages in general (such as STUN and whatever in-band key
> > management is used) as well as SIP messaging. 
> >
>
> This is a very interesting idea.  I agree that this
> requirement should
> include traffic such as ICE messaging and RTP keying.  I'm
> not sure we
> have good options for optimizing, though. 
>
> > "The use of a State Agent for the Dialog Package meets REQ-5."
> > Well, I don't think it does, for reasons in my previous comment.
> >
> >
>
> Yes, a state agent does not help with N ICE and media path 
> keying traffic.
>
> > The comparison of options and the conclusions that are reached seem
> > reasonable to me. My only concern is the scalability to
> large values of N in
> > environments where NAT traversal and media security are 
> managed on an
> > end-to-end basis, although it would work in environments
> where SBCs handle
> > NAT traversal and where key management for media security
> is not done until
> > one of the UAs answers. 
> >
>
> Well, we have discussed an alternative model in which instead of the
> INVITE being forked to all N endpoints, the endpoints first
> get a NOTIFY
> from the Appearance Agent.  If a UA wants to answer the call, 
> it sends
> some kind of indication to the Appearance Agent which then causes the
> INVITE to get sent to the endpoint.  Now, this is a major
> change to the
> way UAs answer calls, but it might help reduce ICE and media 
> path keying
> messaging.
[JRE] The point is, I think we need both. For low values of N, the present
mechanism seems OK, but for larger values of N, I think there might need to
two classes of UA - those who really must receive a forked INVITE request 
and those that can make do with a NOTIFY request- perhaps users less likely
to answer calls from that AoR who would be content with the longer
post-answer delays (and associated media clipping) associated with the 
pick-up type operation (e.g., based on INVITE/Replaces) that would need to
occur.

>
>
> > John
> >
> >
> >
> >
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: Alan Johnston [mailto:alan@sipstation.com
<mailto:alan@sipstation.com> ]
> >> Sent: 27 February 2007 21:13
> >> To: bliss@ietf.org <mailto:bliss@ietf.org> 
> >> Cc: Mohsen Soroush-nejad; Venkatesh Venkataramanan; Anil Kumar
> >> Subject: [BLISS] Fwd: I-D
> ACTION:draft-johnston-bliss-mla-req-00.txt 
> >>
> >> All,
> >>
> >> The authors of draft-anil-sipping-bla (which will be revised
> >> as -04 next
> >> week) have put together this draft discussing requirements and 
> >> implementation options for set of features known as Bridged Line
> >> Appearance (BLA), Multiple Line Appearance (MLA), Single Line
> >> Extension,
> >> etc.
> >> 
> >> Comments are most welcome.
> >>
> >> Thanks,
> >> Alan
> >>
> >> -------- Original Message --------
> >> Subject:   I-D ACTION:draft-johnston-bliss-mla-req-00.txt 
> >> Date:      Tue, 27 Feb 2007 15:50:03 -0500
> >> From:      Internet-Drafts@ietf.org <mailto:Internet-Drafts@ietf.org> 
> >> Reply-To:    <mailto:internet-drafts@ietf.org> internet-drafts@ietf.org
> >> To:        i-d-announce@ietf.org <mailto:i-d-announce@ietf.org> 
> >>
> >>
> >>
> >> A New Internet-Draft is available from the on-line Internet-Drafts 
> >> directories.
> >>
> >>
> >>    Title           : Requirements and Implementation Options for
> >>                           the Multiple Line Appearance
> Feature using
> >>                           the Session Initiation Protocol (SIP)
> >>    Author(s)       : A. Johnston, et al.
> >>    Filename        : draft-johnston-bliss-mla-req-00.txt 
> >>    Pages           : 16
> >>    Date            : 2007-2-27
> >>
> >>    This document describes the requirements for implementation of a
> >>    group telephony feature commonly known as Bridged Line 
> Appearance
> >>    (BLA) or Multiple Line Appearance, or Shared Call/Line
> Appearance
> >>    (SCA).  When implemented using the Session Initiation
> >> Protocol (SIP),
> >>    it is referred to as Multiple Appearances.  This feature
> >> is commonly
> >>    offered in the IP Centrex services and IP-PBX offerings
> >> and is likely
> >>    to be implemented on SIP IP telephones and SIP feature 
> servers used
> >>    in a business environment.  This document lists requirements and
> >>    compares implementation options for this feature.
> >>
> >>
> >> 
> >> A URL for this Internet-Draft is:
> >> http://www.ietf.org/internet-drafts/draft-johnston-bliss-mla-r
<http://www.ietf.org/internet-drafts/draft-johnston-bliss-mla-r> 
> >> 
> > eq-00.txt
> >
> >> To remove yourself from the I-D Announcement list, send a
> message to
> >> i-d-announce-request@ietf.org  <mailto:i-d-announce-request@ietf.org>
with the word unsubscribe in
> >> the body of
> >> the message.
> >> You can also visit
> >> https://www1.ietf.org/mailman/listinfo/I-D-announce
<https://www1.ietf.org/mailman/listinfo/I-D-announce> 
> >> to change your subscription settings.
> >>
> >> Internet-Drafts are also available by anonymous FTP. Login
> with the
> >> username "anonymous" and a password of your e-mail address. After 
> >> logging in, type "cd internet-drafts" and then
> >> "get draft-johnston-bliss-mla-req-00.txt".
> >>
> >> A list of Internet-Drafts directories can be found in 
> >> http://www.ietf.org/shadow.html <http://www.ietf.org/shadow.html> 
> >> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
<ftp://ftp.ietf.org/ietf/1shadow-sites.txt> 
> >> 
> >> Internet-Drafts can also be obtained by e-mail.
> >>
> >> Send a message to:
> >>    mailserv@ietf.org <mailto:mailserv@ietf.org> .
> >> In the body type: 
> >>    "FILE /internet-drafts/draft-johnston-bliss-mla-req-00.txt".
> >>
> >> NOTE:      The mail server at ietf.org <http://ietf.org>  can return
the document in 
> >>    MIME-encoded form by using the "mpack" utility.  To use this
> >>    feature, insert the command "ENCODING mime" before the "FILE"
> >>    command.  To decode the response(s), you will need "munpack" or 
> >>    a MIME-compliant mail reader.  Different MIME-compliant
> >> mail readers
> >>    exhibit different behavior, especially when dealing with
> >>    "multipart" MIME messages ( i.e. documents which have been split
> >>    up into multiple messages), so check your local documentation on
> >>    how to manipulate these messages.
> >>
> >> Below is the data which will enable a MIME compliant mail reader 
> >> implementation to automatically retrieve the ASCII version of the
> >> Internet-Draft.
> >>
> >>
> >>
> >> _______________________________________________ 
> >> BLISS mailing list
> >> BLISS@ietf.org <mailto:BLISS@ietf.org> 
> >> https://www1.ietf.org/mailman/listinfo/bliss
<https://www1.ietf.org/mailman/listinfo/bliss> 
> >>
> >>
> >
> >
> >
>

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




--Boundary_(ID_CBDqo6hNsaHu5UYZBrbM1g)
Content-type: text/html
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">


<META content="MSHTML 6.00.2900.3020" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=375124316-19032007><FONT face=Arial 
color=#0000ff size=2>Venkatesh,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=375124316-19032007><FONT face=Arial 
color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=375124316-19032007><FONT face=Arial 
color=#0000ff size=2>The critical thing is how large can N be - I think it just 
said "large" in the draft. Can you quantify it?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=375124316-19032007><FONT face=Arial 
color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=ltr align=left><SPAN class=375124316-19032007><FONT face=Arial 
color=#0000ff size=2>John</FONT></SPAN></DIV><BR>
<BLOCKQUOTE 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
  <HR tabIndex=-1>
  <FONT face=Tahoma size=2><B>From:</B> Venkatesh [mailto:vvenkatar@gmail.com] 
  <BR><B>Sent:</B> 19 March 2007 14:45<BR><B>To:</B> Elwell, John<BR><B>Cc:</B> 
  Alan Johnston; bliss@ietf.org; Mohsen Soroush-nejad; Venkatesh Venkataramanan; 
  Anil Kumar<BR><B>Subject:</B> Re: [BLISS] Fwd: I-D 
  ACTION:draft-johnston-bliss-mla-req-00.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV>John:<BR>&nbsp;</DIV>
  <DIV>IMHO, we should try to avoid multiple ways for supporting the feature. 
  This is a sure recipe for interoperability issues which BLISS is trying to 
  address in the first place. Believe using NOTIFY's instead of forked INVITE's 
  seem to solve your problem with ICE. I am not sure I understand your concern 
  about media cut thru's with this solution. Just for the record, the 
  alternative solution we had discussed is as below: </DIV>
  <DIV>&nbsp;</DIV>
  <DIV>The State Agent is the only entity that REGISTER's on behalf of the BLA 
  AoR. All other UA's simply SUBSCRIBE to the State-Agent. On receipt of an 
  incoming call, the State-Agent is the only entity that receives the INVITE 
  request. It sends out a NOTIFY to all the UA's in the BLA group. Any UA that 
  intends to 'answer' this call uses INVITE with Replaces header using the 
  dialog identifiers in the NOTIFY request. </DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Thanks,</DIV>
  <DIV>Venkatesh<BR><BR>&nbsp;</DIV>
  <DIV><SPAN class=gmail_quote>On 3/19/07, <B class=gmail_sendername>Elwell, 
  John</B> &lt;<A 
  href="mailto:john.elwell@siemens.com">john.elwell@siemens.com</A>&gt; 
  wrote:</SPAN> 
  <BLOCKQUOTE class=gmail_quote 
  style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Alan,<BR><BR>Thanks 
    for your responses. See below.<BR><BR>John<BR><BR>&gt; -----Original 
    Message-----<BR>&gt; From: Alan Johnston [mailto: <A 
    href="mailto:alan@sipstation.com">alan@sipstation.com</A>]<BR>&gt; Sent: 19 
    March 2007 08:59<BR>&gt; To: Elwell, John<BR>&gt; Cc: <A 
    href="mailto:bliss@ietf.org">bliss@ietf.org</A>; Mohsen Soroush-nejad; 
    Venkatesh<BR>&gt; Venkataramanan; Anil Kumar <BR>&gt; Subject: Re: [BLISS] 
    Fwd: I-D<BR>&gt; ACTION:draft-johnston-bliss-mla-req-00.txt<BR>&gt;<BR>&gt; 
    Hi John,<BR>&gt;<BR>&gt; Thanks for your comments on the draft - see mine 
    below.<BR>&gt;<BR>&gt; Thanks,<BR>&gt; Alan <BR>&gt;<BR>&gt; Elwell, John 
    wrote:<BR>&gt; &gt; Alan,<BR>&gt; &gt;<BR>&gt; &gt; Some of the terminology 
    concerns I already made on<BR>&gt; draft=anil-sipping-bla<BR>&gt; &gt; apply 
    also to this document, so I won't repeat them. <BR>&gt;<BR>&gt; Hopefully 
    this draft suffers a little less, but we will fix<BR>&gt; this as 
    well.<BR>&gt;<BR>&gt; &gt; Other comments:<BR>&gt; &gt;<BR>&gt; &gt; REQ-4: 
    "UAs registering against the group AOR should be able <BR>&gt; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;to learn about each other and join the 
    appearance group."<BR>&gt; &gt; Why do UAs need to learn about each other? 
    Isn't it just<BR>&gt; necessary for a UA<BR>&gt; &gt; to know that the AoR 
    is a group AoR and therefore is shared <BR>&gt; by other UAs?<BR>&gt; &gt; 
    Although specific solutions might require the UA to know<BR>&gt; about 
    specific<BR>&gt; &gt; other UAs, I don't think this is a basic requirement. 
    I<BR>&gt; don't think the<BR>&gt; &gt; solutions discussed in the draft 
    require this. <BR>&gt; &gt;<BR>&gt;<BR>&gt; I guess you are 
    correct.&nbsp;&nbsp;If a UA registers against the AOR and never<BR>&gt; 
    makes or receives a call, the other UAs don't care about it.<BR>&gt; 
    However,<BR>&gt; if it makes or receives a call, it needs to be known to the 
    <BR>&gt; other UAs so<BR>&gt; that SIP call control operations can be 
    performed.&nbsp;&nbsp;If you agree with<BR>&gt; this, perhaps we can reword 
    the requirement to reflect this.<BR>[JRE] OK, if it makes or receives a call 
    then the other UAs need sufficient <BR>information to pick-up or join that 
    call, but whether this requires the<BR>other UAs to have this UA's identity 
    depends on the particular solution.<BR>Some rewording would 
    help.<BR><BR>&gt;<BR>&gt; &gt; "REQ-5 The mechanism must scale for large 
    numbers of appearances, n, <BR>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;and large 
    numbers of UAs, N, without introducing<BR>&gt; excessive messaging<BR>&gt; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;traffic."<BR>&gt; &gt; One consequence of a 
    large N is, depending on solution, the<BR>&gt; establishment of <BR>&gt; 
    &gt; N early dialogs towards the UAC and N parallel ICE<BR>&gt; procedures, 
    N parallel<BR>&gt; &gt; key management procedures, etc.. This might not 
    be<BR>&gt; important for values of N<BR>&gt; &gt; of the order of 3-5, but 
    with much larger values of N this <BR>&gt; could certainly<BR>&gt; &gt; be a 
    problem. I assume this requirement is intended to<BR>&gt; cover this and 
    to<BR>&gt; &gt; include messages in general (such as STUN and whatever 
    in-band key<BR>&gt; &gt; management is used) as well as SIP messaging. 
    <BR>&gt; &gt;<BR>&gt;<BR>&gt; This is a very interesting idea.&nbsp;&nbsp;I 
    agree that this<BR>&gt; requirement should<BR>&gt; include traffic such as 
    ICE messaging and RTP keying.&nbsp;&nbsp;I'm<BR>&gt; not sure we<BR>&gt; 
    have good options for optimizing, though. <BR>&gt;<BR>&gt; &gt; "The use of 
    a State Agent for the Dialog Package meets REQ-5."<BR>&gt; &gt; Well, I 
    don't think it does, for reasons in my previous comment.<BR>&gt; 
    &gt;<BR>&gt; &gt;<BR>&gt;<BR>&gt; Yes, a state agent does not help with N 
    ICE and media path <BR>&gt; keying traffic.<BR>&gt;<BR>&gt; &gt; The 
    comparison of options and the conclusions that are reached seem<BR>&gt; &gt; 
    reasonable to me. My only concern is the scalability to<BR>&gt; large values 
    of N in<BR>&gt; &gt; environments where NAT traversal and media security are 
    <BR>&gt; managed on an<BR>&gt; &gt; end-to-end basis, although it would work 
    in environments<BR>&gt; where SBCs handle<BR>&gt; &gt; NAT traversal and 
    where key management for media security<BR>&gt; is not done until<BR>&gt; 
    &gt; one of the UAs answers. <BR>&gt; &gt;<BR>&gt;<BR>&gt; Well, we have 
    discussed an alternative model in which instead of the<BR>&gt; INVITE being 
    forked to all N endpoints, the endpoints first<BR>&gt; get a NOTIFY<BR>&gt; 
    from the Appearance Agent.&nbsp;&nbsp;If a UA wants to answer the call, 
    <BR>&gt; it sends<BR>&gt; some kind of indication to the Appearance Agent 
    which then causes the<BR>&gt; INVITE to get sent to the 
    endpoint.&nbsp;&nbsp;Now, this is a major<BR>&gt; change to the<BR>&gt; way 
    UAs answer calls, but it might help reduce ICE and media <BR>&gt; path 
    keying<BR>&gt; messaging.<BR>[JRE] The point is, I think we need both. For 
    low values of N, the present<BR>mechanism seems OK, but for larger values of 
    N, I think there might need to<BR>two classes of UA - those who really must 
    receive a forked INVITE request <BR>and those that can make do with a NOTIFY 
    request- perhaps users less likely<BR>to answer calls from that AoR who 
    would be content with the longer<BR>post-answer delays (and associated media 
    clipping) associated with the <BR>pick-up type operation (e.g., based on 
    INVITE/Replaces) that would need to<BR>occur.<BR><BR>&gt;<BR>&gt;<BR>&gt; 
    &gt; John<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; 
    &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;&gt; -----Original 
    Message-----<BR>&gt; &gt;&gt; From: Alan Johnston [mailto:<A 
    href="mailto:alan@sipstation.com">alan@sipstation.com</A>]<BR>&gt; &gt;&gt; 
    Sent: 27 February 2007 21:13<BR>&gt; &gt;&gt; To: <A 
    href="mailto:bliss@ietf.org">bliss@ietf.org</A><BR>&gt; &gt;&gt; Cc: Mohsen 
    Soroush-nejad; Venkatesh Venkataramanan; Anil Kumar<BR>&gt; &gt;&gt; 
    Subject: [BLISS] Fwd: I-D<BR>&gt; ACTION:draft-johnston-bliss-mla-req-00.txt 
    <BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; All,<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; 
    The authors of draft-anil-sipping-bla (which will be revised<BR>&gt; 
    &gt;&gt; as -04 next<BR>&gt; &gt;&gt; week) have put together this draft 
    discussing requirements and <BR>&gt; &gt;&gt; implementation options for set 
    of features known as Bridged Line<BR>&gt; &gt;&gt; Appearance (BLA), 
    Multiple Line Appearance (MLA), Single Line<BR>&gt; &gt;&gt; 
    Extension,<BR>&gt; &gt;&gt; etc.<BR>&gt; &gt;&gt; <BR>&gt; &gt;&gt; Comments 
    are most welcome.<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; Thanks,<BR>&gt; &gt;&gt; 
    Alan<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; -------- Original Message 
    --------<BR>&gt; &gt;&gt; Subject:&nbsp;&nbsp; I-D 
    ACTION:draft-johnston-bliss-mla-req-00.txt <BR>&gt; &gt;&gt; 
    Date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Tue, 27 Feb 2007 15:50:03 
    -0500<BR>&gt; &gt;&gt; From:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A 
    href="mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</A><BR>&gt; 
    &gt;&gt; Reply-To:&nbsp;&nbsp;<A href="mailto:internet-drafts@ietf.org"> 
    internet-drafts@ietf.org</A><BR>&gt; &gt;&gt; 
    To:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A 
    href="mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</A><BR>&gt; 
    &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; A New 
    Internet-Draft is available from the on-line Internet-Drafts <BR>&gt; 
    &gt;&gt; directories.<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    : Requirements and Implementation Options for<BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    the Multiple Line Appearance<BR>&gt; Feature using<BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    the Session Initiation Protocol (SIP)<BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    : A. Johnston, et al.<BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 
    draft-johnston-bliss-mla-req-00.txt <BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    : 16<BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 
    2007-2-27<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;This 
    document describes the requirements for implementation of a<BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;group telephony feature commonly known as 
    Bridged Line <BR>&gt; Appearance<BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;(BLA) or Multiple Line Appearance, or Shared 
    Call/Line<BR>&gt; Appearance<BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;(SCA).&nbsp;&nbsp;When implemented using the 
    Session Initiation<BR>&gt; &gt;&gt; Protocol (SIP),<BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;it is referred to as Multiple 
    Appearances.&nbsp;&nbsp;This feature<BR>&gt; &gt;&gt; is commonly<BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;offered in the IP Centrex services and 
    IP-PBX offerings<BR>&gt; &gt;&gt; and is likely<BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;to be implemented on SIP IP telephones and 
    SIP feature <BR>&gt; servers used<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;in 
    a business environment.&nbsp;&nbsp;This document lists requirements 
    and<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;compares implementation options 
    for this feature.<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; 
    <BR>&gt; &gt;&gt; A URL for this Internet-Draft is:<BR>&gt; &gt;&gt; <A 
    href="http://www.ietf.org/internet-drafts/draft-johnston-bliss-mla-r">http://www.ietf.org/internet-drafts/draft-johnston-bliss-mla-r</A><BR>&gt; 
    &gt;&gt; <BR>&gt; &gt; eq-00.txt<BR>&gt; &gt;<BR>&gt; &gt;&gt; To remove 
    yourself from the I-D Announcement list, send a<BR>&gt; message to<BR>&gt; 
    &gt;&gt; <A 
    href="mailto:i-d-announce-request@ietf.org">i-d-announce-request@ietf.org 
    </A>with the word unsubscribe in<BR>&gt; &gt;&gt; the body of<BR>&gt; 
    &gt;&gt; the message.<BR>&gt; &gt;&gt; You can also visit<BR>&gt; &gt;&gt; 
    <A 
    href="https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1.ietf.org/mailman/listinfo/I-D-announce 
    </A><BR>&gt; &gt;&gt; to change your subscription settings.<BR>&gt; 
    &gt;&gt;<BR>&gt; &gt;&gt; Internet-Drafts are also available by anonymous 
    FTP. Login<BR>&gt; with the<BR>&gt; &gt;&gt; username "anonymous" and a 
    password of your e-mail address. After <BR>&gt; &gt;&gt; logging in, type 
    "cd internet-drafts" and then<BR>&gt; &gt;&gt; "get 
    draft-johnston-bliss-mla-req-00.txt".<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; A 
    list of Internet-Drafts directories can be found in <BR>&gt; &gt;&gt; <A 
    href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</A><BR>&gt; 
    &gt;&gt; or <A 
    href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</A><BR>&gt; 
    &gt;&gt; <BR>&gt; &gt;&gt; Internet-Drafts can also be obtained by 
    e-mail.<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; Send a message to:<BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;<A 
    href="mailto:mailserv@ietf.org">mailserv@ietf.org</A>.<BR>&gt; &gt;&gt; In 
    the body type: <BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;"FILE 
    /internet-drafts/draft-johnston-bliss-mla-req-00.txt".<BR>&gt; 
    &gt;&gt;<BR>&gt; &gt;&gt; NOTE:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The mail 
    server at <A href="http://ietf.org">ietf.org</A> can return the document in 
    <BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;MIME-encoded form by using the 
    "mpack" utility.&nbsp;&nbsp;To use this<BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;feature, insert the command "ENCODING mime" 
    before the "FILE"<BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;command.&nbsp;&nbsp;To decode the 
    response(s), you will need "munpack" or <BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;a MIME-compliant mail 
    reader.&nbsp;&nbsp;Different MIME-compliant<BR>&gt; &gt;&gt; mail 
    readers<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;exhibit different behavior, 
    especially when dealing with<BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;"multipart" MIME messages ( i.e. documents 
    which have been split<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;up into 
    multiple messages), so check your local documentation on<BR>&gt; 
    &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;how to manipulate these messages.<BR>&gt; 
    &gt;&gt;<BR>&gt; &gt;&gt; Below is the data which will enable a MIME 
    compliant mail reader <BR>&gt; &gt;&gt; implementation to automatically 
    retrieve the ASCII version of the<BR>&gt; &gt;&gt; Internet-Draft.<BR>&gt; 
    &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; 
    _______________________________________________ <BR>&gt; &gt;&gt; BLISS 
    mailing list<BR>&gt; &gt;&gt; <A 
    href="mailto:BLISS@ietf.org">BLISS@ietf.org</A><BR>&gt; &gt;&gt; <A 
    href="https://www1.ietf.org/mailman/listinfo/bliss">https://www1.ietf.org/mailman/listinfo/bliss 
    </A><BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; 
    &gt;<BR>&gt;<BR><BR>_______________________________________________<BR>BLISS 
    mailing list<BR><A href="mailto:BLISS@ietf.org">BLISS@ietf.org</A><BR><A 
    href="https://www1.ietf.org/mailman/listinfo/bliss">https://www1.ietf.org/mailman/listinfo/bliss</A><BR></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_CBDqo6hNsaHu5UYZBrbM1g)--


--===============1394776122==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1394776122==--




From bliss-bounces@ietf.org Mon Mar 19 18:21:42 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTQEC-0006yo-Fq; Mon, 19 Mar 2007 18:21:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTQEA-0006yi-Ot
	for bliss@ietf.org; Mon, 19 Mar 2007 18:21:18 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTQE6-0003DW-4h
	for bliss@ietf.org; Mon, 19 Mar 2007 18:21:18 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 19 Mar 2007 23:21:14 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l2JMLDK2024755; 
	Mon, 19 Mar 2007 23:21:13 +0100
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l2JMLClZ021426; 
	Mon, 19 Mar 2007 22:21:13 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 19 Mar 2007 23:21:12 +0100
Received: from [10.0.1.206] ([10.58.48.90]) by xfe-ams-332.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 19 Mar 2007 23:21:11 +0100
Message-ID: <45FF0CD6.9050106@cisco.com>
Date: Mon, 19 Mar 2007 18:21:10 -0400
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: "Drage, Keith \(Keith\)" <drage@alcatel-lucent.com>
Subject: Re: [BLISS] Charter updated
References: <50B1CBA96870A34799A506B2313F26670B4F5D6C@ntht201e.siemenscomms.co.uk>	<45FE41F0.80406@ntt-at.com>
	<5D1A7985295922448D5550C94DE29180E97B80@DEEXC1U01.de.lucent.com>
In-Reply-To: <5D1A7985295922448D5550C94DE29180E97B80@DEEXC1U01.de.lucent.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Mar 2007 22:21:11.0869 (UTC)
	FILETIME=[E6777ED0:01C76A74]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3523; t=1174342873;
	x=1175206873; c=relaxed/simple; s=amsdkim2001;
	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]=20Charter=20updated |Sender:=20;
	bh=d6pGUbpuh/zt6IHbZIWTo9MY1B08ILFR6KyMv8g8uoc=;
	b=r442tHdJ55dLJU8PhJV99ZD3hkScaDYQ+Rr4zz0yJF2IXHyQyw7u0cJK7JDm35Ci/ukf/zoo
	cfQpGykk53g/i2/q2iu/PdBYB4p3l3ioXoSSSSEU9sWpnNXGQ9X6t6gG;
Authentication-Results: ams-dkim-2; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb
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

I think it would be appropriate to do those in bliss if we decide that 
is all we need.

-Jonathan R.

Drage, Keith (Keith) wrote:

> So where does that leave us on SIP extensions such as normal event packages (not event template-packages) and new URI parameters which at the moment require RFCs, but do not automatically require SIP or SIPPING to produce them.
> 
> Does BLISS do those for the services it is working on, or do they go back to SIPPING?
> 
> Regards
> 
> Keith
> 
> 
>>-----Original Message-----
>>From: Shida Schubert [mailto:shida@ntt-at.com] 
>>Sent: Monday, March 19, 2007 7:55 AM
>>To: Elwell, John
>>Cc: bliss@ietf.org
>>Subject: Re: [BLISS] Charter updated
>>
>>
>>John,
>>
>> How is something like this?
>>
>>"SIP applications such as configuration, presence, SIP 
>>extensions for IM, and session policy are clearly out of 
>>scope for BLISS and remain the sole province of either 
>>SIPPING or SIMPLE."
>>
>> Regards
>>  Shida Schubert
>>
>>Elwell, John wrote:
>>
>>>Shida,
>>>
>>>The statement that presence and IM remain the sole province 
>>
>>of SIPPING 
>>
>>>is clearly wrong and should be corrected.
>>>
>>>John
>>>
>>>  
>>>
>>>>-----Original Message-----
>>>>From: Shida Schubert [mailto:shida@ntt-at.com]
>>>>Sent: 18 March 2007 07:58
>>>>To: Elwell, John
>>>>Cc: bliss@ietf.org
>>>>Subject: Re: [BLISS] Charter updated
>>>>
>>>>
>>>>John;
>>>>
>>>> Thanks for your review.
>>>>
>>>> SIMPLE is mentioned for its involvement/relationship in 
>>
>>the guiding 
>>
>>>>principles. Is it sufficient or do you suggest we add the 
>>>>relationship with the SIMPLE WG somewhere in the main body of the 
>>>>charter? If so I would appreciate any suggestions.
>>>>
>>>> Thanks
>>>>  Shida
>>>>
>>>>
>>>>Elwell, John wrote:
>>>>    
>>>>
>>>>>"...presence....IM....are
>>>>>clearly out of scope for BLISS and remain the sole province
>>>>>      
>>>>
>>>>of SIPPING"
>>>>    
>>>>
>>>>>Doesn't SIMPLE figure here somewhere?
>>>>>
>>>>>John
>>>>>
>>>>>  
>>>>>      
>>>>>
>>>>>>-----Original Message-----
>>>>>>From: Shida Schubert [mailto:shida@ntt-at.com]
>>>>>>Sent: 16 March 2007 04:36
>>>>>>To: bliss@ietf.org
>>>>>>Subject: [BLISS] Charter updated
>>>>>>
>>>>>>
>>>>>> I just updated the charter, I know its kind of last 
>>
>>minutes but I 
>>
>>>>>>believe all the comments are reflected.
>>>>>>
>>>>>> Diff from ver2 > ver 3 is available at 
>>>>>>http://www.bliss-ietf.org/charter.txt
>>>>>>
>>>>>> Text version is available at 
>>
>>http://www.bliss-ietf.org/diff2.html
>>
>>>>>> Regards
>>>>>>  Shida
>>>>>>
>>>>>>_______________________________________________
>>>>>>BLISS mailing list
>>>>>>BLISS@ietf.org
>>>>>>https://www1.ietf.org/mailman/listinfo/bliss
>>>>>>
>>>>>>    
>>>>>>        
>>>>>
>>>>>  
>>>>>      
>>>
>>>
>>>  
>>
>>
>>_______________________________________________
>>BLISS mailing list
>>BLISS@ietf.org
>>https://www1.ietf.org/mailman/listinfo/bliss
>>
> 
> 
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www1.ietf.org/mailman/listinfo/bliss
> 

-- 
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



From bliss-bounces@ietf.org Tue Mar 20 04:23:28 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTZcf-0005as-5z; Tue, 20 Mar 2007 04:23:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTZcd-0005Xq-NI
	for bliss@ietf.org; Tue, 20 Mar 2007 04:23:11 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTZcc-0003lR-DI
	for bliss@ietf.org; Tue, 20 Mar 2007 04:23:11 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 20 Mar 2007 09:23:10 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l2K8N9Ac026280
	for <bliss@ietf.org>; Tue, 20 Mar 2007 09:23:09 +0100
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l2K8Molj017660
	for <bliss@ietf.org>; Tue, 20 Mar 2007 08:23:09 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 20 Mar 2007 09:23:07 +0100
Received: from [130.129.23.206] ([10.58.48.66]) by xfe-ams-332.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 20 Mar 2007 09:23:07 +0100
Message-ID: <45FF99E9.8030109@cisco.com>
Date: Tue, 20 Mar 2007 04:23:05 -0400
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: bliss@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Mar 2007 08:23:07.0214 (UTC)
	FILETIME=[FCE3CEE0:01C76AC8]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=360; t=1174378989;
	x=1175242989; c=relaxed/simple; s=amsdkim1002;
	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:=20Presentations=20for=20todays=20BLISS=20session=20now=20availa
	ble=20on=20IETF=20site |Sender:=20;
	bh=ffeFo+dlBlrzCOVehc69vdcJtg4aIe0OYoA67KPq/vw=;
	b=sfKHiM1P5Z1+S05QCh9ZKBjCb3fO86d0gF7X/VMaYv6/nvd65W2LItJ1jT/3YA7YsBRtRHMk
	cEZs1xuDT2A93SYrPA8VXNoWtve1fkCPNz/mRvdNIGx4gSLIuYK8upnd;
Authentication-Results: ams-dkim-1; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Subject: [BLISS] Presentations for todays BLISS session now available on IETF
	site
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

Subject says it all.

-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



From bliss-bounces@ietf.org Tue Mar 20 06:04:26 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTbCb-00017g-M9; Tue, 20 Mar 2007 06:04:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTbCa-00017F-QE
	for bliss@ietf.org; Tue, 20 Mar 2007 06:04:24 -0400
Received: from mail.cedarpointcom.com ([67.151.79.70]
	helo=MAILSRV01.cedarpointcom.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTbCV-0003mW-GP
	for bliss@ietf.org; Tue, 20 Mar 2007 06:04:24 -0400
Received: from MAIL02.cedarpointcom.com ([192.168.1.222]) by
	MAILSRV01.cedarpointcom.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 20 Mar 2007 06:04:15 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 20 Mar 2007 06:04:15 -0400
Message-ID: <402F25FC1EB2BD44831F8A4A4F6DF9420185E692@MAIL02.cedarpointcom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: comments on draft-johnston-bliss-mla-req-00.txt
Thread-Index: Acdq1x3tbVuYZ6zYS9mkJFCxSoCNdg==
From: "Geoff Devine" <gdevine@cedarpointcom.com>
To: <bliss@ietf.org>
X-OriginalArrivalTime: 20 Mar 2007 10:04:15.0258 (UTC)
	FILETIME=[1DB9D7A0:01C76AD7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 958aa603499a3de6b2b87d68741ed60e
Subject: [BLISS] comments on draft-johnston-bliss-mla-req-00.txt
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>
Content-Type: multipart/mixed; boundary="===============1377760755=="
Errors-To: bliss-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1377760755==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C76AD7.1D7E10C3"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C76AD7.1D7E10C3
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I think this is a great first cut at requirements.  Some comments....

=20

REQ-2 Each UA in the group must be able to learn the call status of

   the others in the group for the purpose of rendering this information

   to the user.

=20

[geoff]   I think you at least need to add a requirement REQ-2A to
administratively disable this feature or at least have a mode where
specific UA status is kept private.  In 1A2 Key Systems, you convey
"line" status (where "line" maps to an E.164 telephone number or a
private telephone number) to the other "stations" (UA's).  You don't
necessarily want to convey station status to the other stations that
share a line appearance.

=20

 REQ-3 Calls can be joined (also called bridged or conferenced

   together) or can be picked up (taken) by another UA in the group in a

   secure way.

=20

[geoff] Regulatory issue: In the carrier class universe, there are parts
of the world where you can ring multiple UAs but a bridging function is
forbidden.  I suggest a REQ-3A as: "It must be possible to
administratively disable the Call Join (also called bridged or
conferenced together) function."

=20

   REQ-4 The mechanism should require the minimal amount of

   configuration.  UAs registering against the group AOR should be able

   to learn about each other and join the appearance group.

=20

[geoff] This is in conflict with other requirements I've been listing
that imply careful administrative control of this feature set.

=20

   REQ-5 The mechanism must scale for large numbers of appearances, n,

   and large numbers of UAs, N, without introducing excessive messaging

   traffic.

=20

[geoff] Yes!  The first time I built this function for a PBX in 1985, an
early deployment was in a large hospital where they had a dozen hallways
of 16 examination rooms where each examination room had a feature phone
with 16 line appearances.  The traffic characteristics of that switch
were about 10x what they would have been without a key system emulation
feature.  The engineers called that deployment "The Baby Killer".  As a
practical thing, you will always have a flood of messaging since you
need to line status (Idle, Ringing, Talking, On-Hold (several flavors of
the feature), DND, ...)  to each station.  I think the requirement is
more like "... should minimize messaging traffic."

=20

   REQ-6 Each call or session (incoming or outgoing) must be assigned a

   common "appearance" number from a managed pool administered for the

   AOR group.  Once the session has terminated, the appearance number is

   released back into the pool and can be reused by another incoming or

   outgoing session.

=20

[geoff]  Why "appearance number"?  Using a small integer is one
possibility but there are other ways you may want to name a line
appearance.  You could use E.164 number, a URI, or any unique character
string. =20

=20

[geoff] The wording of the first sentence is a little confusing.  A
reader may interpret this as a hunting requirement.  In PSTN-land key
system emulation, an E.164 number is 1-to-1 with a line appearance
button on a station.  I think this is what you mean.=20

=20

=20

Best regards,

Geoff

=20

=20


------_=_NextPart_001_01C76AD7.1D7E10C3
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I think this is a great first cut at requirements. =
&nbsp;Some
comments&#8230;.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>REQ-2 Each UA in the group must be able to learn the =
call
status of<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; the others in the group for the purpose =
of
rendering this information<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; to the =
user.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>[geoff] &nbsp;&nbsp;I think you at least need to add =
a
requirement REQ-2A to administratively disable this feature or at least =
have a
mode where specific UA status is kept private. &nbsp;In 1A2 Key Systems, =
you
convey &#8220;line&#8221; status (where &#8220;line&#8221; maps to an =
E.164
telephone number or a private telephone number) to the other =
&#8220;stations&#8221;
(UA&#8217;s).&nbsp; You don&#8217;t necessarily want to convey station =
status
to the other stations that share a line =
appearance.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;REQ-3 Calls can be joined (also called bridged =
or
conferenced<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; together) or can be picked up (taken) by
another UA in the group in a<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; secure way.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>[geoff] Regulatory issue: In the carrier class =
universe,
there are parts of the world where you can ring multiple UAs but a =
bridging
function is forbidden.&nbsp; I suggest a REQ-3A as: &#8220;It must be =
possible
to administratively disable the Call Join (also called bridged or =
conferenced
together) function.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; REQ-4 The mechanism should require the =
minimal
amount of<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; configuration.&nbsp; UAs registering =
against
the group AOR should be able<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; to learn about each other and join the
appearance group.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>[geoff] This is in conflict with other requirements =
I&#8217;ve
been listing that imply careful administrative control of this feature =
set.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; REQ-5 The mechanism must scale for large
numbers of appearances, n,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; and large numbers of UAs, N, without
introducing excessive messaging<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; traffic.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>[geoff] Yes!&nbsp; The first time I built this =
function for
a PBX in 1985, an early deployment was in a large hospital where they =
had a
dozen hallways of 16 examination rooms where each examination room had a =
feature
phone with 16 line appearances. &nbsp;The traffic characteristics of =
that
switch were about 10x what they would have been without a key system =
emulation
feature. &nbsp;The engineers called that deployment &#8220;The Baby =
Killer&#8221;.&nbsp;
As a practical thing, you will always have a flood of messaging since =
you need
to line status (Idle, Ringing, Talking, On-Hold (several flavors of the =
feature),
DND, &#8230;) &nbsp;to each station.&nbsp; I think the requirement is =
more like
&#8220;&#8230; should minimize messaging =
traffic.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; REQ-6 Each call or session (incoming or
outgoing) must be assigned a<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; common &quot;appearance&quot; number =
from a
managed pool administered for the<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; AOR group.&nbsp; Once the session has
terminated, the appearance number is<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; released back into the pool and can be =
reused
by another incoming or<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; outgoing =
session.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>[geoff]&nbsp; Why &#8220;appearance =
number&#8221;?&nbsp;
Using a small integer is one possibility but there are other ways you =
may want
to name a line appearance. &nbsp;You could use E.164 number, a URI, or =
any
unique character string. &nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>[geoff] The wording of the first sentence is a little
confusing. &nbsp;A reader may interpret this as a hunting =
requirement.&nbsp; In
PSTN-land key system emulation, an E.164 number is 1-to-1 with a line =
appearance
button on a station.&nbsp; I think this is what you mean. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Best regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Geoff<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C76AD7.1D7E10C3--


--===============1377760755==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1377760755==--




From bliss-bounces@ietf.org Wed Mar 21 04:25:45 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTw8f-00051j-BG; Wed, 21 Mar 2007 04:25:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTw8d-00051H-Lp
	for bliss@ietf.org; Wed, 21 Mar 2007 04:25:43 -0400
Received: from agnada.com ([69.36.182.244])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTw8N-0000Yf-LT
	for bliss@ietf.org; Wed, 21 Mar 2007 04:25:43 -0400
Received: from [130.129.17.120] (dhcp-1178.ietf68.org [130.129.17.120])
	(authenticated bits=0)
	by agnada.com (8.12.11.20060308/8.12.11) with ESMTP id l2L8PIfG001712
	for <bliss@ietf.org>; Wed, 21 Mar 2007 02:25:24 -0600
Message-ID: <4600EBEB.8000409@ntt-at.com>
Date: Wed, 21 Mar 2007 09:25:15 +0100
From: Shida Schubert <shida@ntt-at.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: bliss@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Subject: [BLISS] Minutes from IETF 68 available
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


here you have the draft minutes from the BoF session.

 http://www.bliss-ietf.org/meetings.html

 Comments are welcome.

 Thanks to Vijay and Spencer for writing minutes.

 Regards
  Shida 

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



From bliss-bounces@ietf.org Wed Mar 21 11:01:17 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HU2JO-0000Ta-UZ; Wed, 21 Mar 2007 11:01:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HU2JN-0000Ra-BF
	for bliss@ietf.org; Wed, 21 Mar 2007 11:01:13 -0400
Received: from usaga01-in.huawei.com ([206.16.17.211])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HU2J7-00085d-Mx
	for bliss@ietf.org; Wed, 21 Mar 2007 11:01:13 -0400
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JF900MBGDPLOT@usaga01-in.huawei.com> for
	bliss@ietf.org; Wed, 21 Mar 2007 08:00:57 -0700 (PDT)
Received: from s73602 (dhcp-1671.ietf68.org [130.129.22.113])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with ESMTPA id <0JF900KDODPGR7@usaga01-in.huawei.com> for
	bliss@ietf.org; Wed, 21 Mar 2007 08:00:57 -0700 (PDT)
Date: Wed, 21 Mar 2007 15:59:56 +0100
From: Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Re: [BLISS] Minutes from IETF 68 available
To: bliss@ietf.org
Message-id: <0e9901c76bc9$97d51070$e700000a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
Content-type: text/plain; format=flowed; charset=iso-8859-1;
	reply-type=response
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <4600EBEB.8000409@ntt-at.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
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

I have no one to blame but myself, of course...


>
> here you have the draft minutes from the BoF session.
>
> http://www.bliss-ietf.org/meetings.html

I may not have said this clearly at the mike, but I agreed pretty strongly 
with Ben that organizing by service sends a message, and organizing by 
something technical, including text that says "we have seen the following 
services implementing using this header/whatever:" followed by a list.

I am fine with doing the analysis a service at a time. That seems very 
natural.

I also believe that the technical orientation, with "includes the following 
service", may make it easier for implementers to explain to marketing people 
what they get if they fund development (since it's likely that you'd have 
more than one feature listed, if we're really using SIP in a building-block 
approach).

One comment I heard after the meeting was, "gee, those documents will be 
revised a bunch of times, if they're organized by something technical". I'm 
not sure that SIP services are as broken as NAT behavior, but I note that 
(quoting Cullen) we have discovered new NAT behaviors every time we tested, 
and we have no expectation that we've seen all the possibilities now. If we 
keep seeing new implementations, the service-based docs would have to be 
revised, too.

If we don't see any new implementations after we publish a service-based 
doc, I'd argue that we have successfully "defined the service", which is 
exactly what we said we don't want to do (and I agreed with this). But 
forget I said anything :-)

Thanks,

Spencer 



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



From bliss-bounces@ietf.org Wed Mar 21 21:38:10 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HUCFF-00061d-Az; Wed, 21 Mar 2007 21:37:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HUCFD-00061Y-ID
	for bliss@ietf.org; Wed, 21 Mar 2007 21:37:35 -0400
Received: from rwcrmhc15.comcast.net ([204.127.192.85])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUCFC-0004Cs-Aj
	for bliss@ietf.org; Wed, 21 Mar 2007 21:37:35 -0400
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (rwcrmhc15) with ESMTP
	id <20070322013723m1500em2eae>; Thu, 22 Mar 2007 01:37:29 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l2M1bMLv016400
	for <bliss@ietf.org>; Wed, 21 Mar 2007 20:37:22 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l2M1bMOw016396;
	Wed, 21 Mar 2007 20:37:22 -0500
Date: Wed, 21 Mar 2007 20:37:22 -0500
Message-Id: <200703220137.l2M1bMOw016396@dragon.ariadne.com>
To: bliss@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <0e9901c76bc9$97d51070$e700000a@china.huawei.com>
	(spencer@mcsr-labs.org)
Subject: Re: [BLISS] Minutes from IETF 68 available
References: <4600EBEB.8000409@ntt-at.com>
	<0e9901c76bc9$97d51070$e700000a@china.huawei.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
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

   From: Spencer Dawkins <spencer@mcsr-labs.org>

   I may not have said this clearly at the mike, but I agreed pretty strongly 
   with Ben that organizing by service sends a message, and organizing by 
   something technical, including text that says "we have seen the following 
   services implementing using this header/whatever:" followed by a list.

Uh, what?  "organizing by service sends a message, and organizing by
something technical" does what?

Dale

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



From bliss-bounces@ietf.org Thu Mar 22 03:48:36 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HUI1x-0002K8-TQ; Thu, 22 Mar 2007 03:48:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HUI1w-0002Jy-Q2
	for bliss@ietf.org; Thu, 22 Mar 2007 03:48:16 -0400
Received: from usaga01-in.huawei.com ([206.16.17.211])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUI1v-00059j-It
	for bliss@ietf.org; Thu, 22 Mar 2007 03:48:16 -0400
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JFA00KB3OCCDQ@usaga01-in.huawei.com> for
	bliss@ietf.org; Thu, 22 Mar 2007 00:48:13 -0700 (PDT)
Received: from s73602 (dhcp-1671.ietf68.org [130.129.22.113])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with ESMTPA id <0JFA00243OBZUK@usaga01-in.huawei.com> for
	bliss@ietf.org; Thu, 22 Mar 2007 00:48:12 -0700 (PDT)
Date: Thu, 22 Mar 2007 08:47:06 +0100
From: Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Re: [BLISS] Minutes from IETF 68 available
To: bliss@ietf.org
Message-id: <124e01c76c56$50ce8ed0$e700000a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
Content-type: text/plain; format=flowed; charset=Windows-1252;
	reply-type=original
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <4600EBEB.8000409@ntt-at.com>
	<0e9901c76bc9$97d51070$e700000a@china.huawei.com>
	<200703220137.l2M1bMOw016396@dragon.ariadne.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: Ben Campbell <ben@estacado.net>
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

Sigh. Buffer overrun while typing... Thanks for asking, Dale.


>   From: Spencer Dawkins <spencer@mcsr-labs.org>
>
>   I may not have said this clearly at the mike, but I agreed pretty 
> strongly
>   with Ben that organizing by service sends a message, and organizing by
>   something technical, including text that says "we have seen the 
> following
>   services implementing using this header/whatever:" followed by a list.
>
> Uh, what?  "organizing by service sends a message, and organizing by
> something technical" does what?
>
> Dale

Organizing by something technical sends a different message.

My point is TRYING to be that if we have a BCP spec that's called DND, 
that's going to be more (semi-)normative than we would like for it to be, 
but if we have a spec that says "this is how you support method X, and we've 
seen people using method X to do DND (along with these other services", that 
will probably be less "normative".

Ben - am I totally misunderstanding you on this?

Spencer 



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



From bliss-bounces@ietf.org Thu Mar 22 04:02:44 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HUIFv-0006u7-W2; Thu, 22 Mar 2007 04:02:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HUIFs-0006rL-Va
	for bliss@ietf.org; Thu, 22 Mar 2007 04:02:41 -0400
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=bemg01.siemenscomms.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUIFn-0007Mj-GA
	for bliss@ietf.org; Thu, 22 Mar 2007 04:02:40 -0400
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JFA00MAFOZK9W@siemenscomms.co.uk> for bliss@ietf.org;
	Thu, 22 Mar 2007 08:02:08 +0000 (GMT)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service
	(5.5.2657.72)	id <G8VCX9HB>; Thu, 22 Mar 2007 08:02:10 +0000
Content-return: allowed
Date: Thu, 22 Mar 2007 08:02:07 +0000
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [BLISS] Fwd: I-D ACTION:draft-johnston-bliss-mla-req-00.txt
To: Alan Johnston <alan@sipstation.com>
Message-id: <50B1CBA96870A34799A506B2313F26670B5BAF44@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: bliss@ietf.org, Mohsen Soroush-nejad <Mohsen.Soroushnejad@sylantro.com>,
	Venkatesh Venkataramanan <venkatesh@sylantro.com>,
	Anil Kumar <anil@yahoo-inc.com>
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

Alan,

Just catching up again. A further question on your last point.
 
<snip/>
> > The comparison of options and the conclusions that are reached seem
> > reasonable to me. My only concern is the scalability to 
> large values of N in
> > environments where NAT traversal and media security are 
> managed on an
> > end-to-end basis, although it would work in environments 
> where SBCs handle
> > NAT traversal and where key management for media security 
> is not done until
> > one of the UAs answers.
> >   
> 
> Well, we have discussed an alternative model in which instead of the 
> INVITE being forked to all N endpoints, the endpoints first 
> get a NOTIFY 
> from the Appearance Agent.  If a UA wants to answer the call, 
> it sends 
> some kind of indication to the Appearance Agent which then causes the 
> INVITE to get sent to the endpoint.  Now, this is a major 
> change to the 
> way UAs answer calls, but it might help reduce ICE and media 
> path keying 
> messaging.
[JRE] You say you discussed this, but what was your reason for rejecting it?

John

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



From bliss-bounces@ietf.org Thu Mar 22 04:36:52 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HUImx-0003pH-Kn; Thu, 22 Mar 2007 04:36:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HUImw-0003o4-Bn
	for bliss@ietf.org; Thu, 22 Mar 2007 04:36:50 -0400
Received: from dsl001-129-069.dfw1.dsl.speakeasy.net ([72.1.129.69]
	helo=vicuna.estacado.net) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HUIml-0006ZB-Vl
	for bliss@ietf.org; Thu, 22 Mar 2007 04:36:50 -0400
Received: from [130.129.16.51] (dhcp-1033.ietf68.org [130.129.16.51])
	(authenticated bits=0)
	by vicuna.estacado.net (8.13.8/8.13.8) with ESMTP id l2M8aUjL074936
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 22 Mar 2007 03:36:36 -0500 (CDT)
	(envelope-from ben@estacado.net)
In-Reply-To: <124e01c76c56$50ce8ed0$e700000a@china.huawei.com>
References: <4600EBEB.8000409@ntt-at.com>
	<0e9901c76bc9$97d51070$e700000a@china.huawei.com>
	<200703220137.l2M1bMOw016396@dragon.ariadne.com>
	<124e01c76c56$50ce8ed0$e700000a@china.huawei.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
X-Priority: 3
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <AFA6D55F-A14B-470A-ACCA-75B6D9EC30C7@estacado.net>
Content-Transfer-Encoding: 7bit
From: Ben Campbell <ben@estacado.net>
Subject: Re: [BLISS] Minutes from IETF 68 available
Date: Thu, 22 Mar 2007 09:36:24 +0100
To: Spencer Dawkins <spencer@mcsr-labs.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
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


On Mar 22, 2007, at 8:47 AM, Spencer Dawkins wrote:

> Sigh. Buffer overrun while typing... Thanks for asking, Dale.
>
>
>>   From: Spencer Dawkins <spencer@mcsr-labs.org>
>>
>>   I may not have said this clearly at the mike, but I agreed  
>> pretty strongly
>>   with Ben that organizing by service sends a message, and  
>> organizing by
>>   something technical, including text that says "we have seen the  
>> following
>>   services implementing using this header/whatever:" followed by a  
>> list.
>>
>> Uh, what?  "organizing by service sends a message, and organizing by
>> something technical" does what?
>>
>> Dale
>
> Organizing by something technical sends a different message.
>
> My point is TRYING to be that if we have a BCP spec that's called  
> DND, that's going to be more (semi-)normative than we would like  
> for it to be, but if we have a spec that says "this is how you  
> support method X, and we've seen people using method X to do DND  
> (along with these other services", that will probably be less  
> "normative".
>
> Ben - am I totally misunderstanding you on this?

I think you understand me perfectly :-)

I think the idea is that DND et al are _examples_ of common things  
that use the various SIP stuff. The important message is what SIP  
stuff you need to implement for general interoperability in a certain  
context. If we organize by service, we are putting the focus on the  
examples rather than the "what stuff I need to worry about as an  
implementer" info.

>
> Spencer
>


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



From bliss-bounces@ietf.org Thu Mar 22 09:31:45 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HUNO6-0000VN-9C; Thu, 22 Mar 2007 09:31:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HUNO5-0000V2-1A
	for bliss@ietf.org; Thu, 22 Mar 2007 09:31:29 -0400
Received: from mail7.exchange.microsoft.com ([131.107.1.27]
	helo=mail.exchange.microsoft.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUNO3-0001QQ-Ml
	for bliss@ietf.org; Thu, 22 Mar 2007 09:31:29 -0400
Received: from df-bhd-02.exchange.corp.microsoft.com (157.54.71.211) by
	DF-GWY-07.exchange.corp.microsoft.com (157.54.63.164) with Microsoft
	SMTP Server (TLS) id 8.1.85.3; Thu, 22 Mar 2007 06:31:27 -0700
Received: from DF-COLLIE-MSG.exchange.corp.microsoft.com ([10.255.255.1]) by
	df-bhd-02.exchange.corp.microsoft.com ([157.54.71.211]) with mapi;
	Thu, 22 Mar 2007 06:31:26 -0700
From: Sriram Parameswar <Sriram.Parameswar@microsoft.com>
To: "bliss@ietf.org" <bliss@ietf.org>
Date: Thu, 22 Mar 2007 06:31:26 -0700
Thread-Topic: Minutes from IETF 68 available
Thread-Index: AcdsXfROlngsHGwQQO+11dnt6mpXQwAGIVsQAAKGXpA=
Message-ID: <EB9237EDF079AA4C9462B2ABC5D571647BD90F6343@DF-COLLIE-MSG.exchange.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Subject: [BLISS] FW: Minutes from IETF 68 available
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

Hi,

On a related note - this is what I was trying to say at the mike at the BLI=
SS meeting. Let us take services/applications and chunk them into classes -=
 for example DND could be chunked into "Presence based Routing" (example cl=
ass only!!). Then we can say - these are the drafts/SIP messages/payloads t=
hat you need to support to solve these problems. This way we do not have to=
 go through an exhaustive list of services/applications that exist in the w=
ild - with their multitude of variations.

Thanks,

Sriram

Date: Thu, 22 Mar 2007 09:36:24 +0100
From: Ben Campbell <ben@estacado.net>
Subject: Re: [BLISS] Minutes from IETF 68 available
To: Spencer Dawkins <spencer@mcsr-labs.org>
Cc: bliss@ietf.org
Message-ID: <AFA6D55F-A14B-470A-ACCA-75B6D9EC30C7@estacado.net>
Content-Type: text/plain; charset=3DUS-ASCII; delsp=3Dyes; format=3Dflowed


On Mar 22, 2007, at 8:47 AM, Spencer Dawkins wrote:

> Sigh. Buffer overrun while typing... Thanks for asking, Dale.
>
>
>>   From: Spencer Dawkins <spencer@mcsr-labs.org>
>>
>>   I may not have said this clearly at the mike, but I agreed
>> pretty strongly
>>   with Ben that organizing by service sends a message, and
>> organizing by
>>   something technical, including text that says "we have seen the
>> following
>>   services implementing using this header/whatever:" followed by a
>> list.
>>
>> Uh, what?  "organizing by service sends a message, and organizing by
>> something technical" does what?
>>
>> Dale
>
> Organizing by something technical sends a different message.
>
> My point is TRYING to be that if we have a BCP spec that's called
> DND, that's going to be more (semi-)normative than we would like
> for it to be, but if we have a spec that says "this is how you
> support method X, and we've seen people using method X to do DND
> (along with these other services", that will probably be less
> "normative".
>
> Ben - am I totally misunderstanding you on this?

I think you understand me perfectly :-)

I think the idea is that DND et al are _examples_ of common things
that use the various SIP stuff. The important message is what SIP
stuff you need to implement for general interoperability in a certain
context. If we organize by service, we are putting the focus on the
examples rather than the "what stuff I need to worry about as an
implementer" info.

>
> Spencer
>




------------------------------

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


End of BLISS Digest, Vol 3, Issue 49
************************************

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



From bliss-bounces@ietf.org Thu Mar 22 11:49:16 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HUPX6-0008Of-AR; Thu, 22 Mar 2007 11:48:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HUPBk-0005JB-7d
	for bliss@ietf.org; Thu, 22 Mar 2007 11:26:52 -0400
Received: from agnada.com ([69.36.182.244])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUP7e-0000oB-1V
	for bliss@ietf.org; Thu, 22 Mar 2007 11:22:40 -0400
Received: from [130.129.17.120] (dhcp-1178.ietf68.org [130.129.17.120])
	(authenticated bits=0)
	by agnada.com (8.12.11.20060308/8.12.11) with ESMTP id l2MFMLNW019912; 
	Thu, 22 Mar 2007 09:22:22 -0600
Message-ID: <46029F28.60706@ntt-at.com>
Date: Thu, 22 Mar 2007 16:22:16 +0100
From: Shida Schubert <shida@ntt-at.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Ben Campbell <ben@estacado.net>
Subject: Re: [BLISS] Minutes from IETF 68 available
References: <4600EBEB.8000409@ntt-at.com>	<0e9901c76bc9$97d51070$e700000a@china.huawei.com>	<200703220137.l2M1bMOw016396@dragon.ariadne.com>	<124e01c76c56$50ce8ed0$e700000a@china.huawei.com>
	<AFA6D55F-A14B-470A-ACCA-75B6D9EC30C7@estacado.net>
In-Reply-To: <AFA6D55F-A14B-470A-ACCA-75B6D9EC30C7@estacado.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
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


 I agree on the value of having a draft which lists the benefit of
implementing a specific SIP primitive such that document
describes

 "If you implement A right, you can use it for XYZ.".

 and this may be a bi-product of work in BLISS.

 But this doesn't cover the whole set of primitives one would
need to implement to accomplish interoperability, it may but
more than one primitives are generally needed thus a single
document specifying "This is useful if you want to implement
XYZ" is not sufficient to solve the problem we are trying to
solve. I believe...

 With the approach mentioned, implementors would need to
find number of documents equal to that of primitives needed
to implement the feature desired.

 If you want to implement A and this A needs XYZ, one
needs to somehow find this XYZ. If each primitive has a
document then you would somehow find XYZ, if you miss
one then you would probably not achieve interoperability..

 Anyhow, I see the output to be very valuable in a similar
fashion that Hitch Hiker's Guide is useful to the whole SIP.

 Regards
  Shida

Ben Campbell wrote:
>
> On Mar 22, 2007, at 8:47 AM, Spencer Dawkins wrote:
>
>> Sigh. Buffer overrun while typing... Thanks for asking, Dale.
>>
>>
>>>   From: Spencer Dawkins <spencer@mcsr-labs.org>
>>>
>>>   I may not have said this clearly at the mike, but I agreed pretty 
>>> strongly
>>>   with Ben that organizing by service sends a message, and 
>>> organizing by
>>>   something technical, including text that says "we have seen the 
>>> following
>>>   services implementing using this header/whatever:" followed by a 
>>> list.
>>>
>>> Uh, what?  "organizing by service sends a message, and organizing by
>>> something technical" does what?
>>>
>>> Dale
>>
>> Organizing by something technical sends a different message.
>>
>> My point is TRYING to be that if we have a BCP spec that's called 
>> DND, that's going to be more (semi-)normative than we would like for 
>> it to be, but if we have a spec that says "this is how you support 
>> method X, and we've seen people using method X to do DND (along with 
>> these other services", that will probably be less "normative".
>>
>> Ben - am I totally misunderstanding you on this?
>
> I think you understand me perfectly :-)
>
> I think the idea is that DND et al are _examples_ of common things 
> that use the various SIP stuff. The important message is what SIP 
> stuff you need to implement for general interoperability in a certain 
> context. If we organize by service, we are putting the focus on the 
> examples rather than the "what stuff I need to worry about as an 
> implementer" info.
>
>>
>> Spencer
>>
>
>
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www1.ietf.org/mailman/listinfo/bliss
>
>


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



