From bliss-bounces@ietf.org Thu Nov 01 14:30:08 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 1Inenm-0005Ym-2A; Thu, 01 Nov 2007 14:29:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Inenl-0005YD-6f
	for bliss@ietf.org; Thu, 01 Nov 2007 14:29:57 -0400
Received: from tcmail23.telekom.de ([217.6.95.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Inene-0004TL-RW
	for bliss@ietf.org; Thu, 01 Nov 2007 14:29:57 -0400
Received: from S4DE9JSAANM.ost.t-com.de (S4DE9JSAANM.ost.t-com.de
	[10.125.177.122]) by tcmail21.telekom.de with ESMTP;
	Thu, 1 Nov 2007 19:29:42 +0100
Received: from S4DE9JSAAHW.ost.t-com.de ([10.125.177.160]) by
	S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 1 Nov 2007 19:29:41 +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: AW: AW: [BLISS] Call completion
Date: Thu, 1 Nov 2007 19:29:41 +0100
Message-Id: <CCA850DCD3FBE2479D5076C5C1873222029F52A2@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <4727750D.8070102@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AW: [BLISS] Call completion
Thread-Index: AcgbIR2+y3gmWIR7Q2Wn3iRZLOJxMQBg8QSg
From: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
To: <pkyzivat@cisco.com>
X-OriginalArrivalTime: 01 Nov 2007 18:29:41.0884 (UTC)
	FILETIME=[2B293BC0:01C81CB5]
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
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

Yes, that would be the prioritization of a CC call, and the monitor =
would have to have the possibility to reject the call.

Since the last revision the prioritization is not longer part of the =
Poetzl draft, the proposal was to handle the prioritization of a call =
independent from the completion. People than can decide if CC call =
prioritization is part of their CC service.

On the other hand, if rejection of not prioritized CC calls is part of a =
CC service, as you said this has influences on the capabilities of the =
monitor, and this has to be descibed in the draft.

Or is there a way to handle the prioritization independent from the =
monitor capabilities respectively the monitor involvement in the CC =
call?


BR, Martin







> -----Urspr=FCngliche Nachricht-----
> Von: Paul Kyzivat [mailto:pkyzivat@cisco.com]=20
> Gesendet: Dienstag, 30. Oktober 2007 19:17
> An: H=FClsemann, Martin
> Cc: bliss@ietf.org
> Betreff: Re: AW: [BLISS] Call completion
>=20
>=20
>=20
>=20
> Huelsemann, Martin wrote:
> > =20
> >>     Question: The CC must be marked in some way as a CC call=20
> >> in order for
> >>     the callee's monitor to know that the CC activation is=20
> being acted
> >>     upon by the caller's agent.  And the marking must include the
> >>     original Call-Id to allow correlation with the original call.
> >>     Possibilities for a marking are a special URI-parameter on the
> >>     request URI or a special header.
> >>
> >> Its not entirely clear to me that the monitor *needs* to know=20
> >> that this=20
> >> call is a completion for some missed call. What bad thing=20
> >> would happen=20
> >> if it didn't know that?
> > If there are still entries in the queue the callee's=20
> monitor shouldn't accept calls without this CC indication.=20
> Otherwise there could be the situation that immediately after=20
> the callee has become available there are other calls which=20
> are answered then, and the user who requested CC will never=20
> have a chance to complete the call.
>=20
> You are making an assumption about the "monitor" that Dale=20
> didn't make:
>=20
> You are assuming that calls flow through it before reaching=20
> the callee,=20
> and that the monitor can thus prevent those from being accepted.
>=20
> If that is a key part of the mechanism then it needs to be specified=20
> somewhere.
>=20
> 	Thanks,
> 	Paul
>=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 Nov 01 15:01:06 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 1InfHF-0002Vl-Be; Thu, 01 Nov 2007 15:00:25 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1InfHD-0002Ve-Sp
	for bliss@ietf.org; Thu, 01 Nov 2007 15:00:23 -0400
Received: from tcmail23.telekom.de ([217.6.95.237])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1InfHD-0002jx-4a
	for bliss@ietf.org; Thu, 01 Nov 2007 15:00:23 -0400
Received: from S4DE9JSAANM.ost.t-com.de (S4DE9JSAANM.ost.t-com.de
	[10.125.177.122]) by tcmail21.telekom.de with ESMTP;
	Thu, 1 Nov 2007 20:00:19 +0100
Received: from S4DE9JSAAHW.ost.t-com.de ([10.125.177.160]) by
	S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 1 Nov 2007 20:00:18 +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: AW: [BLISS] Re: notification/warning: call diversion active
Date: Thu, 1 Nov 2007 20:00:18 +0100
Message-Id: <CCA850DCD3FBE2479D5076C5C1873222029F52A3@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <0D4E483A0E6E0A46861409E5D6C2011CE1FBDA@sea02-mxc01.citel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] Re: notification/warning: call diversion active
Thread-Index: Acf2Dc5SYYg5A8DJSKS8mAEu8+G/NwEnGuzQAAIFrfAIPEFPMABFUm0w
From: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
To: <steve.langstaff@citel.com>,
    <bliss@ietf.org>
X-OriginalArrivalTime: 01 Nov 2007 19:00:18.0912 (UTC)
	FILETIME=[721D7600:01C81CB9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
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

The conclusion was that SUB/NOT is the appropriate mechanism to inform =
about CDIV active, so a subscription is necessary to receive this =
information. We haven't discussed on the content of the NOTIFY yet.

BR, Martin




> -----Urspr=FCngliche Nachricht-----
> Von: Steve Langstaff [mailto:steve.langstaff@citel.com]=20
> Gesendet: Mittwoch, 31. Oktober 2007 10:52
> An: bliss@ietf.org
> Betreff: [BLISS] Re: notification/warning: call diversion active
>=20
>=20
> [Sorry to follow up my own post, but I happened to have it handy!]
>=20
> Did the discussion on "Call-Diversion active" SUBSCRIBE/NOTIFY come to
> any conclusion?
>=20
> > -----Original Message-----
> > From: Steve Langstaff [mailto:steve.langstaff@citel.com]=20
> > Sent: 19 September 2007 12:51
> > To: Elwell, John; Paul Kyzivat; Huelsemann, Martin
> > Cc: bliss@ietf.org
> > Subject: RE: AW: AW: [BLISS] Re: notification/warning: call=20
> > diversion active
> >=20
> > I like the SUBSCRIBE/NOTIFY proposal - it seems to be the=20
> > right tool for the job.
> >=20
> > Might I suggest that we take a leaf out of RFC3842, and have=20
> > (at least) a boolean indication that there is some sort of=20
> > call diversion active?
> >=20
> > E.g. where RFC3842 says:
> > "The status line allows messaging systems or messaging=20
> > gateways to provide  the traditional boolean message waiting=20
> > notification.
> >=20
> >       Messages-Waiting: yes
> > "
> >=20
> > BLISS-CALL-DIVERSION could say:
> > "The status line allows call handling systems to provide  the=20
> > traditional boolean call diversion notification.
> >=20
> >       Call-Diversion: yes
> > "
> >=20
> >=20
> > > -----Original Message-----
> > > From: Elwell, John [mailto:john.elwell@siemens.com]
> > > Sent: 19 September 2007 12:00
> > > To: Paul Kyzivat; Huelsemann, Martin
> > > Cc: bliss@ietf.org
> > > Subject: RE: AW: AW: [BLISS] Re: notification/warning: call=20
> > diversion=20
> > > active
> > >=20
> > > Catching up after being away.
> > >=20
> > > I seem to sense a consensus that there is a requirement for=20
> > a UA to be=20
> > > aware of the status of call forwarding unconditional (or=20
> > maybe various=20
> > > types of conditional call forwarding too, although that=20
> seems to be=20
> > > outside the scope of the present thread). It can then use this=20
> > > information to advise the user in whatever way is=20
> > appropriate. To me,=20
> > > things like stutter dial tone or other indications at the time of=20
> > > outgoing call establishment are old fashioned - for a long=20
> > time I have=20
> > > had phones on my desk that permanently indicate my call=20
> forwarding=20
> > > status. Indeed I very rarely hear dial tone, let along=20
> stutter dial=20
> > > tone, because I dial from an address book or hot key or=20
> missed call=20
> > > list, or failing that I key my digits before going "off-hook" (or=20
> > > activating headset or speakerphone or whatever). My=20
> cellphone never=20
> > > gives me dialtone. So PLEASE let's leave the UI to the=20
> UA, and just=20
> > > consider how the UA becomes aware of the information.
> > >=20
> > > So if this is the requirement (to keep the UA informed), let's=20
> > > consider solutions.
> > >=20
> > > I have a certain sympathy with Martin Huelsemann's=20
> > contention that a=20
> > > SUBSCRIBE/NOTIFY mechanism is too heavy in signalling.
> > > For example, dialog-stateful proxies / B2BUAs seem to be=20
> > sensitive to=20
> > > lots of long-term dialogs from every UA.
> > >=20
> > > I like the idea of a URN, but I don't really like putting it=20
> > > Alert-Info in a response to INVITE, for all the reasons stated by=20
> > > various contributors to this thread.
> > >=20
> > > What about a REFER request, referring to a URN that=20
> indicates call=20
> > > forwarding status? URN parameters could even indicate=20
> > conditions, if=20
> > > we need to extend this to conditional call forwarding. Something=20
> > > similar has been proposed by others in the past in the context of=20
> > > remote call control.
> > >=20
> > > John
> >=20
> > _______________________________________________
> > BLISS mailing list
> > BLISS@ietf.org
> > https://www1.ietf.org/mailman/listinfo/bliss
> >=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 Wed Nov 07 13:04:54 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 1IppGo-0002Lm-Dc; Wed, 07 Nov 2007 13:04:54 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IppGm-0002IY-SO
	for bliss@ietf.org; Wed, 07 Nov 2007 13:04:52 -0500
Received: from agnada.com ([69.36.182.244])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IppGm-000289-Gg
	for bliss@ietf.org; Wed, 07 Nov 2007 13:04:52 -0500
Received: from [192.168.1.101] (S0106001839eceb7a.vc.shawcable.net
	[24.80.240.54]) (authenticated bits=0)
	by agnada.com (8.12.11.20060308/8.12.11) with ESMTP id lA7I4lRp006445
	for <bliss@ietf.org>; Wed, 7 Nov 2007 11:04:48 -0700
Message-ID: <4731FE29.7010504@ntt-at.com>
Date: Wed, 07 Nov 2007 10:04:25 -0800
From: Shida Schubert <shida@ntt-at.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
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: 7655788c23eb79e336f5f8ba8bce7906
Subject: [BLISS] The Automatic Handling Status 
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


All;

 We have received about dozen feedback regarding
automatic handling. It's not a representative samples,
as many of them were submitted by the same vendors.

 From the few feedbacks we have received, it's already
apparent that we do have problems in hand, but it's still
too early to tell how big are the problems. I want to thank
the small number of vendors/people that have contributed,
and encourage those who haven't.

 If you care about this problem, but you aren't an expert
in the field, please contact somebody more suitable and have
them finish the survey.

 http://www.bliss-ietf.org/autohandle/?id=27bl01dn22d

 Regards
  Shida (As a chair)

 

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



From bliss-bounces@ietf.org Thu Nov 08 14:45: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 1IqDJK-00047t-Ka; Thu, 08 Nov 2007 14:45:06 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IqDJJ-00043U-OP
	for bliss@ietf.org; Thu, 08 Nov 2007 14:45:05 -0500
Received: from agnada.com ([69.36.182.244])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IqDJJ-0002kv-Ax
	for bliss@ietf.org; Thu, 08 Nov 2007 14:45:05 -0500
Received: from [192.168.1.101] (S0106001839eceb7a.vc.shawcable.net
	[24.80.240.54]) (authenticated bits=0)
	by agnada.com (8.12.11.20060308/8.12.11) with ESMTP id lA8Jj1S3031612
	for <bliss@ietf.org>; Thu, 8 Nov 2007 12:45:01 -0700
Message-ID: <47336724.8090101@ntt-at.com>
Date: Thu, 08 Nov 2007 11:44:36 -0800
From: Shida Schubert <shida@ntt-at.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
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: 9182cfff02fae4f1b6e9349e01d62f32
Subject: [BLISS] IETF 70 is coming up...
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 am assembling the draft agenda for the Vancouver
meeting, so please send your requests for time on the
agenda.

 As a reminder, cutoff dates for drafts submissions
are as coming up.

 November 12th at 9:00 AM ET (14:00 UTC/GMT). 
  The only exception is for version -00 WG drafts that 
  replace existing non-WG drafts.

 All revised Internet-Drafts (version -01 and higher) 
  must be submitted by Monday, November 19th at 9:00 
  AM ET (14:00 UTC/GMT).

 I also advice people to use the new submission tool
accessible from the link below, which validates your
draft beforehand.

 https://datatracker.ietf.org/idst/upload.cgi

 Regards
  Shida


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



From bliss-bounces@ietf.org Sun Nov 11 12:33:19 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 1IrGgQ-0006lU-7w; Sun, 11 Nov 2007 12:33:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IrGgO-0006jk-AD
	for bliss@ietf.org; Sun, 11 Nov 2007 12:33:16 -0500
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 1IrGgL-0002rW-N6
	for bliss@ietf.org; Sun, 11 Nov 2007 12:33:16 -0500
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JRC00I61REMRG@siemenscomms.co.uk> for bliss@ietf.org;
	Sun, 11 Nov 2007 17:32:47 +0000 (GMT)
Date: Sun, 11 Nov 2007 17:33:12 +0000
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <E1IrG0Y-0005QB-5O@stiedprstage1.ietf.org>
To: bliss@ietf.org
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D03E9583@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-Topic: Questions in draft-elwell-bliss-ach-analysis-00.txt
Thread-Index: Acgkg2jtZcL1LGk6Rpq5BroSvg6lYAABRWyA
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <E1IrG0Y-0005QB-5O@stiedprstage1.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Subject: [BLISS] Questions in draft-elwell-bliss-ach-analysis-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>
Errors-To: bliss-bounces@ietf.org

Readers are referred to the questions in the Conclusions section. I
would encourage discussion of these (or any other aspects of the draft)
on the list prior to the Vancouver meeting.

John 

> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
> Sent: 11 November 2007 16:50
> To: i-d-announce@ietf.org
> Subject: I-D Action:draft-elwell-bliss-ach-analysis-00.txt
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> 
> 	Title           : An Analysis of Automatic Call 
> Handling Implementation Issues in the Session Initiation 
> Protocol (SIP)
> 	Author(s)       : J. Elwell
> 	Filename        : draft-elwell-bliss-ach-analysis-00.txt
> 	Pages           : 11
> 	Date            : 2007-11-11
> 
> This discusses problems associated with automatic call handling (ACH)
> when using the Session Initiation Protocol (SIP).
> 
> This work is being discussed on the bliss@ietf.org mailing list.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-elwell-bliss-ach-ana
> lysis-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-elwell-bliss-ach-analysis-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-elwell-bliss-ach-analysis-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



From bliss-bounces@ietf.org Sun Nov 11 18:15:46 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 1IrM1p-0008GM-5N; Sun, 11 Nov 2007 18:15:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IrM1n-0008Db-Bl
	for bliss@ietf.org; Sun, 11 Nov 2007 18:15:43 -0500
Received: from qmta03.emeryville.ca.mail.comcast.net ([76.96.30.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IrM1j-0005uj-Rs
	for bliss@ietf.org; Sun, 11 Nov 2007 18:15:43 -0500
Received: from OMTA02.emeryville.ca.mail.comcast.net ([76.96.30.19])
	by QMTA03.emeryville.ca.mail.comcast.net with smtp
	id BajA1Y0050QkzPw0101a00; Sun, 11 Nov 2007 23:15:41 +0000
Received: from dragon.ariadne.com ([24.34.79.42])
	by OMTA02.emeryville.ca.mail.comcast.net with comcast
	id BbFf1Y0080umElk0000000; Sun, 11 Nov 2007 23:15:41 +0000
X-Authority-Analysis: v=1.0 c=1 a=hMhbqezBlzFVHuMQV5wA:9
	a=PGf3_B7qGQ2JM9UI1A4A:7 a=wib0mnUStg6Qa2xSG5FOWOlclQQA:4
	a=JfD0Fch1gWkA:10 a=8y7tGHue6YMA:10
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 lABNFbSV021445
	for <bliss@ietf.org>; Sun, 11 Nov 2007 18:15:37 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id lABNFbFn021441;
	Sun, 11 Nov 2007 18:15:37 -0500
Date: Sun, 11 Nov 2007 18:15:37 -0500
Message-Id: <200711112315.lABNFbFn021441@dragon.ariadne.com>
To: bliss@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <4722614B.6080802@cisco.com> (pkyzivat@cisco.com)
Subject: Re: [BLISS] Call completion
References: <200710261945.l9QJjlGB031483@dragon.ariadne.com>
	<4722614B.6080802@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
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: Paul Kyzivat <pkyzivat@cisco.com>

   Note it is the act of being busy that can be used to infer presence, and 
   the act of becoming unbusy that is assumed to indicate availability for 
   a call completion. This is a very poor means of determining presence, 
   since the callee could be sitting beside the phone for hours without 
   being involved in a call. If some other means of determining presence is 
   available, one would hope it would be used.

   Its also not entirely reasonable to assume that being busy implies not 
   being available for call completion. With multiple lines, or call 
   waiting, it may be possible to take a call completion even when busy. 
   This is again an issue of presence - another means of determining 
   availability could override this inference.

All of this implies that what we really want to watch for is the
presence state "callee is available to receive a call", which is best
judged by the callee's monitor.

The protocol implementation is that CCBS and CCNR should not be
distinguished, other than possibly as information carried in the
monitor, to be used in trying to determine "callee is available to
receive a call".  That is, CCBS and CCNR are not distinguishable at
the caller's ends.

Dale

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



From bliss-bounces@ietf.org Mon Nov 12 17:39: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 1IrhwW-0003cg-1J; Mon, 12 Nov 2007 17:39:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IrhwU-0003Ws-Bf
	for bliss@ietf.org; Mon, 12 Nov 2007 17:39:42 -0500
Received: from agnada.com ([69.36.182.244])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IrhwS-0000bp-4U
	for bliss@ietf.org; Mon, 12 Nov 2007 17:39:42 -0500
Received: from [192.168.1.101] (S0106001839eceb7a.vc.shawcable.net
	[24.80.240.54]) (authenticated bits=0)
	by agnada.com (8.12.11.20060308/8.12.11) with ESMTP id lACMddq2020245
	for <bliss@ietf.org>; Mon, 12 Nov 2007 15:39:39 -0700
Message-ID: <4738D60B.1060800@ntt-at.com>
Date: Mon, 12 Nov 2007 14:39:07 -0800
From: Shida Schubert <shida@ntt-at.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: bliss@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by agnada.com id
	lACMddq2020245
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d16ce744298aacf98517bc7c108bd198
Subject: [BLISS] [Fwd: Call for Papers: SFSIW-1]
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


 Below is an announcement/call for paper for a workshop
addressing the fundamental SIP interoperability problems
(Not of certain feature groups) that's been discussed on
the RAI list.

--- Starting the original e-mail ----------

CALL FOR PAPERS AND PARTICIPATION
=20
The 1st SIP Forum SIP Interoperability Workshop (SFSIW-1)
=20
Co-located with the 70th Internet Engineering Task Force Meeting (IETF 70=
)
http://www.ietf.org/meetings/70-IETF.html
=20
=20
IMPORTANT DATES
Submission deadline: 27 November 2007
Notification of presentation acceptance: 30 November 2007
Workshop date: 3 December 2007, 11am =AD 12:30pm Pacific Time
=20
=20
AIMS AND SCOPE
SIP has been gaining traction as a preferred network signaling protocol f=
or
real-time communications networks. There has been a considerable amount o=
f
low-level protocol testing and interoperability, such as provided by the =
SIP
Interoperability Test event, or SIPit, which is in its seventh year. Ther=
e
are many independent implementations of clients, servers, proxies,
back-to-back User Agents, registrars, and the like. In addition, there ar=
e
significant network deployments, many at scale.
=20
While this is all good, deployment experience is showing that
interoperability is difficult to achieve. Products from a single vendor t=
end
to work well with each other. However, multi-vendor interoperability,
especially above the basic stack level, has historically been difficult t=
o
achieve. In fact, the proof point of the success of vendors attending SIP=
it
indicates interoperability problems may not be due to the specification
itself.
=20
This workshop serves as a forum to bring together researchers, engineers,
and service providers to exchange ideas, share experiences, and propose
approaches to address interoperability problems. Particular focus will be=
 on
systemic or architectural problems, as opposed to simple implementation
errors.=20
=20
If the workshop identifies concrete proposals to improve interoperability
that would require modifications to the underlying protocols, these
proposals will be forwarded to the appropriate groups in the IETF.
=20
We encourage contributions describing interoperability and SIP. The topic=
s
of interest include but are not limited to:
=20
* Interoperability failures seen in the field or lab
* Deployment experiences
* Development experiences
* Open source projects and experiences
* Failures discovered in the field after successful lab testing
* Common failure modes
* Interoperability test methodologies
* Interoperability test experiences
* Architectural principals
* Proposals for achieving interoperability
* Proposals for improving development
* Proposals for soliciting additional real-world feedback from implemente=
rs
and service providers
=20
=20
POSITION PAPERS
Individuals must submit a position paper relevant to SIP interoperability=
 to
participate in the workshop. Acceptable formats are IETF Internet Draft
style (in HTML or plain text), IEEE Computer Society Proceedings Manuscri=
pts
style (in PDF), ACM Transactions style (in PDF), or presentation style (i=
n
PDF). The papers should be no longer than 6 pages if in IEEE or ACM style=
 or
10 pages of text in Internet Draft style. There is no minimum length
requirement. You are allowed to submit relevant, previously published wor=
ks.
=20
Papers received by the submission deadline will be posted to the Workshop
web site, unless the author(s) request withholding publication. The
author(s) may retain copyright or assign it to the SIP Forum or the IETF.=
 If
you are submitting a paper that already has a copyright assignment, such =
as
an IEEE or ACM conference or journal paper, please apply the appropriate
self-publication disclaimers demanded by those organizations.
=20
Submit your position paper using EasyChair at the following address:
http://www.easychair.org/conferences/?conf=3Dsfsiw1
=20
=20
WORKSHOP FORMAT
There is only a limited time available at the venue for this first worksh=
op.
The expectation is this will be a highly interactive workshop. In order t=
o
frame the conversation, the workshop chair will open the discussion. At t=
he
discretion of the Program Committee and dependent upon the quality and
number of position papers received, a limited number of position papers m=
ay
be presented. Note that all position papers will be published, unless the
author(s) request withholding publication.
=20
=20
WORKSHOP FEES
The workshop, including lunch, is free of charge to participants. Stated
differently, submitting a position paper, no matter how brief, pays for y=
our
lunch. The IETF has graciously provided a conference room at the venue. A=
s
such, we will not turn away non-participants. However, it is possible
non-participants may not be allowed to participate and certainly will not
get lunch.
=20
WORKSHOP CHAIR:
Robert Sparks
Protocol Barbarian, Estacado Systems
rsparks@nostrum.com
=20
PROGRAM CHAIR:
Eric Burger
Deputy CTO, BEA Systems
eburger@sipforum.org
=20
PROGRAM COMMITTEE:
Robert Sparks, rsparks@nostrum.com
Anwar Siddiqui, anwars@avaya.com
Bob Penfield, BPenfield@acmepacket.com
Eric Burger, eburger@bea.com
=20
=20
=20






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



From bliss-bounces@ietf.org Wed Nov 14 09:31: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 1IsJHF-0001nd-55; Wed, 14 Nov 2007 09:31:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IsJHD-0001lJ-MR
	for bliss@ietf.org; Wed, 14 Nov 2007 09:31:35 -0500
Received: from tcmail23.telekom.de ([217.6.95.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IsJH9-0007Mm-3x
	for bliss@ietf.org; Wed, 14 Nov 2007 09:31:35 -0500
Received: from S4DE9JSAANO.ost.t-com.de (S4DE9JSAANO.ost.t-com.de
	[10.125.177.105]) by tcmail21.telekom.de with ESMTP;
	Wed, 14 Nov 2007 15:31:23 +0100
Received: from S4DE9JSAAHW.ost.t-com.de ([10.125.177.160]) by
	S4DE9JSAANO.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 14 Nov 2007 15:31:22 +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] Call completion
Date: Wed, 14 Nov 2007 15:31:22 +0100
Message-Id: <CCA850DCD3FBE2479D5076C5C1873222029F5318@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <200711112315.lABNFbFn021441@dragon.ariadne.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] Call completion
Thread-Index: AcgkuM3PPXI0QYglTcKd/xldJSWTqwCDsS7Q
From: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
To: <Dale.Worley@comcast.net>,
    <bliss@ietf.org>
X-OriginalArrivalTime: 14 Nov 2007 14:31:22.0843 (UTC)
	FILETIME=[07A37AB0:01C826CB]
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
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

On the protocol level the procedures for CCBS and CCNR are the same, the =
user experience probably will differ a littlebit, for example if you =
hear a ringing tone or a busy tone before activating CC.

I agree that it is best judged by the monitor when the condition is =
reached that the callee is available for the call, so that we don't need =
to define the criteria for that.=20

BR, Martin





> -----Urspr=FCngliche Nachricht-----
> Von: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net]=20
> Gesendet: Montag, 12. November 2007 00:16
> An: bliss@ietf.org
> Betreff: Re: [BLISS] Call completion
>=20
>=20
>=20
>    From: Paul Kyzivat <pkyzivat@cisco.com>
>=20
>    Note it is the act of being busy that can be used to infer=20
> presence, and=20
>    the act of becoming unbusy that is assumed to indicate=20
> availability for=20
>    a call completion. This is a very poor means of=20
> determining presence,=20
>    since the callee could be sitting beside the phone for=20
> hours without=20
>    being involved in a call. If some other means of=20
> determining presence is=20
>    available, one would hope it would be used.
>=20
>    Its also not entirely reasonable to assume that being busy=20
> implies not=20
>    being available for call completion. With multiple lines, or call=20
>    waiting, it may be possible to take a call completion even=20
> when busy.=20
>    This is again an issue of presence - another means of determining=20
>    availability could override this inference.
>=20
> All of this implies that what we really want to watch for is the
> presence state "callee is available to receive a call", which is best
> judged by the callee's monitor.
>=20
> The protocol implementation is that CCBS and CCNR should not be
> distinguished, other than possibly as information carried in the
> monitor, to be used in trying to determine "callee is available to
> receive a call".  That is, CCBS and CCNR are not distinguishable at
> the caller's ends.
>=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 Fri Nov 16 16:20: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 1It8c8-0003wt-0D; Fri, 16 Nov 2007 16:20:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1It8c6-0003wg-2P
	for bliss@ietf.org; Fri, 16 Nov 2007 16:20:34 -0500
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 1It8c3-00028Y-I8
	for bliss@ietf.org; Fri, 16 Nov 2007 16:20:34 -0500
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.0-24 #40642)
	with ESMTP id <0JRM0003JB8W1Y@siemenscomms.co.uk> for bliss@ietf.org;
	Fri, 16 Nov 2007 21:20:03 +0000 (GMT)
Date: Fri, 16 Nov 2007 18:16:31 +0000
From: "Elwell, John" <john.elwell@siemens.com>
To: bliss@ietf.org
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0441024@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-Topic: draft-elwell-bliss-dnd-01 posted
Thread-Index: AcgofNAVUtTzlBaBTSO64CgWtBwexQ==
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Spam-Score: 1.4 (+)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: Srivatsa Srinivasan <srivats@exchange.microsoft.com>
Subject: [BLISS] draft-elwell-bliss-dnd-01 posted
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

http://www.ietf.org/internet-drafts/draft-elwell-bliss-dnd-01.txt
This has been updated, mainly to reflect comments received around the
time of the Vancouver meeting and some further thoughts from the new
co-author, Srivatsa. Although part of the automatic call handling (ACH)
topic in BLISS, for which a separate draft has been submitted
(draft-elwell-bliss-ach), we felt we needed to maintain the DND draft
because there is not a 100% overlap with ACH (e.g., the DND draft also
contains something on presence).

Changes from draft-00 are mainly:
- additional means of invoking DND (casual, based on sensing a user's
current activity);
- distinction between conveying DND to a proxy and conveying the
condition to the caller;
- problem of indicating DND to a caller when the condition does not
relate to the original called party (e.g., the call was forwarded
first);
- whether to wait for all branches to respond or act immediately a
branch reports DND;


Comments?

John



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



From bliss-bounces@ietf.org Mon Nov 19 07:24: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 1Iu5fv-0007xC-72; Mon, 19 Nov 2007 07:24:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Iu5fu-0007wA-4B
	for bliss@ietf.org; Mon, 19 Nov 2007 07:24:26 -0500
Received: from sea02-mxf01.citel.com ([205.234.66.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iu5fr-0005HH-Lr
	for bliss@ietf.org; Mon, 19 Nov 2007 07:24:26 -0500
Received: from [10.8.50.21] (helo=sea02-mxc01.citel.com)
	by sea02-mxf01.citel.com with smtp (Exim 4.43)
	id 1Iu5gh-0007gc-Pn; Mon, 19 Nov 2007 04:25:15 -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] draft-elwell-bliss-dnd-01 posted
Date: Mon, 19 Nov 2007 04:24:11 -0800
Message-ID: <0D4E483A0E6E0A46861409E5D6C2011CEA9043@sea02-mxc01.citel.com>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0441024@GBNTHT12009MSX.gb002.siemens.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] draft-elwell-bliss-dnd-01 posted
thread-index: AcgofNAVUtTzlBaBTSO64CgWtBwexQCKGLtQ
References: <0D5F89FAC29E2C41B98A6A762007F5D0441024@GBNTHT12009MSX.gb002.siemens.net>
From: "Steve Langstaff" <steve.langstaff@citel.com>
To: "Elwell, John" <john.elwell@siemens.com>,
	<bliss@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: Srivatsa Srinivasan <srivats@exchange.microsoft.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

In the ID, where you say e.g.:

      REQ1 - There MUST be a way for a UA to indicate through presence
      that it is not willing to receive a call or message because the
      user does not wish to be disturbed.

Do you mean "There MUST be a single way for..." or "There MUST be at
least one way...".

> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens.com]=20
> Sent: 16 November 2007 18:17
> To: bliss@ietf.org
> Cc: Srivatsa Srinivasan
> Subject: [BLISS] draft-elwell-bliss-dnd-01 posted
>=20
> http://www.ietf.org/internet-drafts/draft-elwell-bliss-dnd-01.txt
> This has been updated, mainly to reflect comments received=20
> around the time of the Vancouver meeting and some further=20
> thoughts from the new co-author, Srivatsa. Although part of=20
> the automatic call handling (ACH) topic in BLISS, for which a=20
> separate draft has been submitted (draft-elwell-bliss-ach),=20
> we felt we needed to maintain the DND draft because there is=20
> not a 100% overlap with ACH (e.g., the DND draft also=20
> contains something on presence).
>=20
> Changes from draft-00 are mainly:
> - additional means of invoking DND (casual, based on sensing=20
> a user's current activity);
> - distinction between conveying DND to a proxy and conveying=20
> the condition to the caller;
> - problem of indicating DND to a caller when the condition=20
> does not relate to the original called party (e.g., the call=20
> was forwarded first);
> - whether to wait for all branches to respond or act=20
> immediately a branch reports DND;
>=20
>=20
> Comments?
>=20
> John
>=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 Nov 19 13:00: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 1IuAva-0000xU-3A; Mon, 19 Nov 2007 13:00:58 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IuAvY-0000wu-QI
	for bliss@ietf.org; Mon, 19 Nov 2007 13:00:56 -0500
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225]
	helo=mailhost.siemenscomms.co.uk)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IuAvW-0006MW-9H
	for bliss@ietf.org; Mon, 19 Nov 2007 13:00:54 -0500
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x11 #31430)
	with ESMTP id <0JRR005HOM1HDT@siemenscomms.co.uk> for bliss@ietf.org;
	Mon, 19 Nov 2007 18:00:53 +0000 (GMT)
Date: Mon, 19 Nov 2007 18:00:52 +0000
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [BLISS] draft-elwell-bliss-dnd-01 posted
In-reply-to: <0D4E483A0E6E0A46861409E5D6C2011CEA9043@sea02-mxc01.citel.com>
To: Steve Langstaff <steve.langstaff@citel.com>, bliss@ietf.org
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D04411E7@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-Topic: [BLISS] draft-elwell-bliss-dnd-01 posted
Thread-Index: AcgofNAVUtTzlBaBTSO64CgWtBwexQCKGLtQAAs82JA=
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <0D5F89FAC29E2C41B98A6A762007F5D0441024@GBNTHT12009MSX.gb002.siemens.net>
	<0D4E483A0E6E0A46861409E5D6C2011CEA9043@sea02-mxc01.citel.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: Srivatsa Srinivasan <srivats@exchange.microsoft.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

Steve,

What I mean is that there MUST be at least one way that an
implementation can use and be sure that other conformant implementations
will do the same.

John

> -----Original Message-----
> From: Steve Langstaff [mailto:steve.langstaff@citel.com] 
> Sent: 19 November 2007 12:24
> To: Elwell, John; bliss@ietf.org
> Cc: Srivatsa Srinivasan
> Subject: RE: [BLISS] draft-elwell-bliss-dnd-01 posted
> 
> In the ID, where you say e.g.:
> 
>       REQ1 - There MUST be a way for a UA to indicate through presence
>       that it is not willing to receive a call or message because the
>       user does not wish to be disturbed.
> 
> Do you mean "There MUST be a single way for..." or "There MUST be at
> least one way...".
> 
> > -----Original Message-----
> > From: Elwell, John [mailto:john.elwell@siemens.com] 
> > Sent: 16 November 2007 18:17
> > To: bliss@ietf.org
> > Cc: Srivatsa Srinivasan
> > Subject: [BLISS] draft-elwell-bliss-dnd-01 posted
> > 
> > http://www.ietf.org/internet-drafts/draft-elwell-bliss-dnd-01.txt
> > This has been updated, mainly to reflect comments received 
> > around the time of the Vancouver meeting and some further 
> > thoughts from the new co-author, Srivatsa. Although part of 
> > the automatic call handling (ACH) topic in BLISS, for which a 
> > separate draft has been submitted (draft-elwell-bliss-ach), 
> > we felt we needed to maintain the DND draft because there is 
> > not a 100% overlap with ACH (e.g., the DND draft also 
> > contains something on presence).
> > 
> > Changes from draft-00 are mainly:
> > - additional means of invoking DND (casual, based on sensing 
> > a user's current activity);
> > - distinction between conveying DND to a proxy and conveying 
> > the condition to the caller;
> > - problem of indicating DND to a caller when the condition 
> > does not relate to the original called party (e.g., the call 
> > was forwarded first);
> > - whether to wait for all branches to respond or act 
> > immediately a branch reports DND;
> > 
> > 
> > Comments?
> > 
> > John
> > 
> > 
> > 
> > _______________________________________________
> > 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 Tue Nov 20 16:19:57 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 1IuaVg-000286-VI; Tue, 20 Nov 2007 16:19:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IuaVe-00023U-5S
	for bliss@ietf.org; Tue, 20 Nov 2007 16:19:54 -0500
Received: from agnada.com ([69.36.182.244])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IuaVZ-0002uc-OP
	for bliss@ietf.org; Tue, 20 Nov 2007 16:19:54 -0500
Received: from [192.168.1.101] (S0106001839eceb7a.vc.shawcable.net
	[24.80.240.54]) (authenticated bits=0)
	by agnada.com (8.12.11.20060308/8.12.11) with ESMTP id lAKLJieb016401
	for <bliss@ietf.org>; Tue, 20 Nov 2007 14:19:45 -0700
Message-ID: <47434F71.7050406@ntt-at.com>
Date: Tue, 20 Nov 2007 13:19:45 -0800
From: Shida Schubert <shida@ntt-at.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
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: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: [BLISS] ACH Survey Result
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


 The result of the survey we have been conducting
is on the website, the number of feedbacks were smaller
than what we hoped for, but it has given us some idea of
the problem space.

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

 The result of the survey has led us to consider the
potential functional primitives alluded on John's draft
below (Section 5).

 http://tools.ietf.org/wg/bliss/draft-elwell-bliss-ach-analysis-00.txt

 I encourage people to look at the survey result and
read the analysis draft.

 The survey form is still open, so please contribute to the
survey, it should only take 5 minutes or so.

 Regards
  Shida (As Chair)

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



From bliss-bounces@ietf.org Wed Nov 21 08:58:23 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 1Iuq5q-00028S-SW; Wed, 21 Nov 2007 08:58:18 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Iuq5o-00027y-WC
	for bliss@ietf.org; Wed, 21 Nov 2007 08:58:17 -0500
Received: from tcmail23.telekom.de ([217.6.95.237])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Iuq5o-0001Uv-GO
	for bliss@ietf.org; Wed, 21 Nov 2007 08:58:16 -0500
Received: from S4DE9JSAANM.ost.t-com.de (S4DE9JSAANM.ost.t-com.de
	[10.125.177.122]) by tcmail21.telekom.de with ESMTP for
	bliss@ietf.org; Wed, 21 Nov 2007 14:58:12 +0100
Received: from S4DE9JSAAMW.ost.t-com.de ([10.125.177.114]) by
	S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 21 Nov 2007 14:58:12 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Wed, 21 Nov 2007 14:58:11 +0100
Message-Id: <F452BB3496398949B9D6634F9B6B155702A90A57@S4DE9JSAAMW.ost.t-com.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Use of Callee Capabilities for CCBS/CCNR support indication 
Thread-Index: AcgsRo0RELnBzWcAR4aq7vfyn9UIjw==
From: "Alexeitsev, D" <D.Alexeitsev@t-com.net>
To: <bliss@ietf.org>
X-OriginalArrivalTime: 21 Nov 2007 13:58:12.0198 (UTC)
	FILETIME=[8E036860:01C82C46]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Subject: [BLISS] Use of Callee Capabilities for CCBS/CCNR support indication 
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="===============0549615115=="
Errors-To: bliss-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0549615115==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C82C46.8DA37F78"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C82C46.8DA37F78
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Does any one aware of a possibility to transfer the callee capability
indication in an unsuccessful response?=20

The callee capabilities mechanism could be an alternative for the
transfer of the CCBS possible indication, but it suffers from the lack
of contact header in the unsuccessful responses. For the CCNR it would
immediately work.

Greetings,
Denis Alexeitsev






------_=_NextPart_001_01C82C46.8DA37F78
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>Use of Callee Capabilities for CCBS/CCNR support indication =
</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

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

<P><FONT SIZE=3D2 FACE=3D"Arial">Does any one aware of a possibility to =
transfer the callee capability indication in an unsuccessful response? =
</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The callee capabilities mechanism could =
be an alternative for the transfer of the CCBS possible indication, but =
it suffers from the lack of contact header in the unsuccessful =
responses. For the CCNR it would immediately work.</FONT></P>

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

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

</BODY>
</HTML>
------_=_NextPart_001_01C82C46.8DA37F78--


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

--===============0549615115==--




From bliss-bounces@ietf.org Wed Nov 21 23:13: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 1Iv3Rh-0008Af-F7; Wed, 21 Nov 2007 23:13:45 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Iv3Rg-0008AV-N2
	for bliss@ietf.org; Wed, 21 Nov 2007 23:13:44 -0500
Received: from agnada.com ([69.36.182.244])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Iv3Rg-0003Ln-BR
	for bliss@ietf.org; Wed, 21 Nov 2007 23:13:44 -0500
Received: from [192.168.1.101] (S0106001839eceb7a.vc.shawcable.net
	[24.80.240.54]) (authenticated bits=0)
	by agnada.com (8.12.11.20060308/8.12.11) with ESMTP id lAM4Ddvv021898
	for <bliss@ietf.org>; Wed, 21 Nov 2007 21:13:39 -0700
Message-ID: <474501F4.3070203@ntt-at.com>
Date: Wed, 21 Nov 2007 20:13:40 -0800
From: Shida Schubert <shida@ntt-at.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
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: de4f315c9369b71d7dd5909b42224370
Subject: [BLISS] draft agenda for IETF 70: BLISS
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


Folks;

 Below is the draft agenda so far based on
requests, list activity and milestones.

 13:00 Agenda Bash [Chairs]
 13:15 Problem Statement [Jonathan Rosenberg]
 13:35 Automatic Call Handling [John Elwell]
 14:30 Call Queuing [Denis Alexeitsev] 

 This is a draft agenda as I noted above, and we
can still change it. Please provide comment if I have
missed something.

 Regards
  Shida

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



From bliss-bounces@ietf.org Sat Nov 24 11:35: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 1Ivxyh-0005Z8-Pk; Sat, 24 Nov 2007 11:35:35 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iu70l-0002Nc-0n; Mon, 19 Nov 2007 08:50:03 -0500
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Iu70k-0008SG-KD; Mon, 19 Nov 2007 08:50:02 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 464CC175AC;
	Mon, 19 Nov 2007 13:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Iu70j-0004oi-QS; Mon, 19 Nov 2007 08:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Iu70j-0004oi-QS@stiedprstage1.ietf.org>
Date: Mon, 19 Nov 2007 08:50:01 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
X-Mailman-Approved-At: Sat, 24 Nov 2007 11:35:34 -0500
Cc: bliss@ietf.org
Subject: [BLISS] I-D Action:draft-ietf-bliss-problem-statement-01.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>
Errors-To: bliss-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Basic Level of Interoperability for SIP Services Working Group of the IETF.


	Title           : Basic Level of Interoperability for Session Initiation Protocol (SIP) Services (BLISS) Problem Statement
	Author(s)       : J. Rosenberg
	Filename        : draft-ietf-bliss-problem-statement-01.txt
	Pages           : 19
	Date            : 2007-11-19

The Session Initiation Protocol (SIP) has been designed as a general
purpose protocol for establishing and managing multimedia sessions.
It provides many core functions and extensions in support of features
such as transferring of calls, parking calls, and so on.  However,
interoperability of more advanced features between different vendors
has been poor.  This document describes the reason behind these
interoperability problems, and presents a framework for addressing
them.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-bliss-problem-statement-01.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-ietf-bliss-problem-statement-01.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-ietf-bliss-problem-statement-01.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-11-19084803.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-bliss-problem-statement-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-bliss-problem-statement-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-11-19084803.I-D\@ietf.org>


--OtherAccess--

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

--NextPart--




From bliss-bounces@ietf.org Mon Nov 26 10:25:23 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 1Iwfpq-0005Py-V8; Mon, 26 Nov 2007 10:25:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Iwfpp-0005Pb-8p
	for bliss@ietf.org; Mon, 26 Nov 2007 10:25:21 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iwfpi-0000Jn-Pw
	for bliss@ietf.org; Mon, 26 Nov 2007 10:25:21 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 26 Nov 2007 10:25:14 -0500
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id lAQFPE2q001009; 
	Mon, 26 Nov 2007 10:25:14 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id lAQFP6KT019100; 
	Mon, 26 Nov 2007 15:25:14 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, 26 Nov 2007 10:25:02 -0500
Received: from [161.44.174.179] ([161.44.174.179]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 26 Nov 2007 10:25:02 -0500
Message-ID: <474AE54D.8060205@cisco.com>
Date: Mon, 26 Nov 2007 10:25:01 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: "Alexeitsev, D" <D.Alexeitsev@t-com.net>
Subject: Re: [BLISS] Use of Callee Capabilities for CCBS/CCNR support
	indication
References: <F452BB3496398949B9D6634F9B6B155702A90A57@S4DE9JSAAMW.ost.t-com.de>
In-Reply-To: <F452BB3496398949B9D6634F9B6B155702A90A57@S4DE9JSAAMW.ost.t-com.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Nov 2007 15:25:02.0313 (UTC)
	FILETIME=[838C9D90:01C83040]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1428; t=1196090714;
	x=1196954714; 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]=20Use=20of=20Callee=20Capabilities=20for=20CC
	BS/CCNR=20support=20indication |Sender:=20
	|To:=20=22Alexeitsev,=20D=22=20<D.Alexeitsev@t-com.net>;
	bh=yrYomO/ae/88fwm5Rx6CCTGMAhw3eEsk+TobI4dDZEA=;
	b=LkTCoLSy3ySEaSqnkqwZH6gXcwHgmMVHbv6mtgEpRuGha0po0Ye0NogG5mly+N3oXaVLn+MC
	Rdqg6grKiH+LhrINThagyEan5i2u20CBMAt3hPnScydFBF8jgigEnJmw;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
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



Alexeitsev, D wrote:
> Hi,
> 
> Does any one aware of a possibility to transfer the callee capability 
> indication in an unsuccessful response?
> 
> The callee capabilities mechanism could be an alternative for the 
> transfer of the CCBS possible indication, but it suffers from the lack 
> of contact header in the unsuccessful responses. For the CCNR it would 
> immediately work.

The capabilities are conveyed as header parameters of the Contact header 
in the successful response, and indicate the capabilities of the UA with 
which you have established a session. If the request fails, then you 
don't return a Contact and so can't return capabilities.

The framework for callee capabilities and caller preferences assumes 
there are multiple potential targets that could have different 
capabilities. In that environment it is hard to imagine what would make 
sense to return as capabilities when a request fails, because you don't 
know which UA to return capabilities for.

To me this is an clear signal that callee capabilities are not the 
correct mechanism for what you are trying to do.

	Thanks,
	Paul

> Greetings,
> Denis Alexeitsev
> 
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> 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 Tue Nov 27 15:43: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 1Ix7H0-00040J-3K; Tue, 27 Nov 2007 15:43:14 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ix7Gx-0003sJ-UI
	for bliss@ietf.org; Tue, 27 Nov 2007 15:43:11 -0500
Received: from qmta07.emeryville.ca.mail.comcast.net ([76.96.30.64])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ix7Gx-0000Of-FP
	for bliss@ietf.org; Tue, 27 Nov 2007 15:43:11 -0500
Received: from OMTA06.emeryville.ca.mail.comcast.net ([76.96.30.51])
	by QMTA07.emeryville.ca.mail.comcast.net with comcast
	id HqQr1Y00316AWCU0A0cf00; Tue, 27 Nov 2007 20:43:15 +0000
Received: from dragon.ariadne.com ([24.34.79.42])
	by OMTA06.emeryville.ca.mail.comcast.net with comcast
	id HwjD1Y0050umElk0800000; Tue, 27 Nov 2007 20:43:14 +0000
X-Authority-Analysis: v=1.0 c=1 a=JWoP8dSEmqYA:10 a=x7Xoe9kPDzpvJTQgbJcA:9
	a=kqd-T-4NXZYIt61vhfzmeeKbc58A:4 a=JfD0Fch1gWkA:10
	a=8y7tGHue6YMA:10
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 lARKh8SV018944
	for <bliss@ietf.org>; Tue, 27 Nov 2007 15:43:08 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id lARKh8xs018940;
	Tue, 27 Nov 2007 15:43:08 -0500
Date: Tue, 27 Nov 2007 15:43:08 -0500
Message-Id: <200711272043.lARKh8xs018940@dragon.ariadne.com>
To: bliss@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <474AE54D.8060205@cisco.com> (pkyzivat@cisco.com)
Subject: Re: [BLISS] Use of Callee Capabilities for CCBS/CCNR support
	indication
References: <F452BB3496398949B9D6634F9B6B155702A90A57@S4DE9JSAAMW.ost.t-com.de>
	<474AE54D.8060205@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
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: Paul Kyzivat <pkyzivat@cisco.com>

   > Does any one aware of a possibility to transfer the callee capability 
   > indication in an unsuccessful response?
   > 
   > The callee capabilities mechanism could be an alternative for the 
   > transfer of the CCBS possible indication, but it suffers from the lack 
   > of contact header in the unsuccessful responses. For the CCNR it would 
   > immediately work.

   The capabilities are conveyed as header parameters of the Contact header 
   in the successful response, and indicate the capabilities of the UA with 
   which you have established a session. If the request fails, then you 
   don't return a Contact and so can't return capabilities.

   The framework for callee capabilities and caller preferences assumes 
   there are multiple potential targets that could have different 
   capabilities. In that environment it is hard to imagine what would make 
   sense to return as capabilities when a request fails, because you don't 
   know which UA to return capabilities for.

   To me this is an clear signal that callee capabilities are not the 
   correct mechanism for what you are trying to do.

In a non-forking environment, the (sole) destination's Contact does
get returned in failure responses, though.  And if we implemnted
HERFP, the same would probably be true.  But in the RFC 3261 model,
where the UAC only gets a response from one destination, there is no
way for the destination(s) to signal reliably that they support CC.

Dale

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



From bliss-bounces@ietf.org Tue Nov 27 16:04: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 1Ix7bZ-0006id-BS; Tue, 27 Nov 2007 16:04:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ix7bY-0006dp-IW
	for bliss@ietf.org; Tue, 27 Nov 2007 16:04:28 -0500
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ix7bX-0002wb-Uj
	for bliss@ietf.org; Tue, 27 Nov 2007 16:04:28 -0500
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0JS600I0CNVFKU@siemenscomms.co.uk> for bliss@ietf.org;
	Tue, 27 Nov 2007 21:04:27 +0000 (GMT)
Date: Tue, 27 Nov 2007 21:04:26 +0000
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [BLISS] Use of Callee Capabilities for CCBS/CCNR
	support	indication
In-reply-to: <200711272043.lARKh8xs018940@dragon.ariadne.com>
To: Dale.Worley@comcast.net, bliss@ietf.org
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0441DB1@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Thread-Topic: [BLISS] Use of Callee Capabilities for CCBS/CCNR support
	indication
Thread-Index: AcgxNiYXpqFTsai6SjiUAcFWFbSViQAAsyfQ
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <F452BB3496398949B9D6634F9B6B155702A90A57@S4DE9JSAAMW.ost.t-com.de>
	<474AE54D.8060205@cisco.com>
	<200711272043.lARKh8xs018940@dragon.ariadne.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
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,

See below.

John=20

> -----Original Message-----
> From: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net]=20
> Sent: 27 November 2007 20:43
> To: bliss@ietf.org
> Subject: Re: [BLISS] Use of Callee Capabilities for CCBS/CCNR=20
> support indication
>=20
>=20
>    From: Paul Kyzivat <pkyzivat@cisco.com>
>=20
>    > Does any one aware of a possibility to transfer the=20
> callee capability=20
>    > indication in an unsuccessful response?
>    >=20
>    > The callee capabilities mechanism could be an=20
> alternative for the=20
>    > transfer of the CCBS possible indication, but it suffers=20
> from the lack=20
>    > of contact header in the unsuccessful responses. For the=20
> CCNR it would=20
>    > immediately work.
>=20
>    The capabilities are conveyed as header parameters of the=20
> Contact header=20
>    in the successful response, and indicate the capabilities=20
> of the UA with=20
>    which you have established a session. If the request=20
> fails, then you=20
>    don't return a Contact and so can't return capabilities.
>=20
>    The framework for callee capabilities and caller=20
> preferences assumes=20
>    there are multiple potential targets that could have different=20
>    capabilities. In that environment it is hard to imagine=20
> what would make=20
>    sense to return as capabilities when a request fails,=20
> because you don't=20
>    know which UA to return capabilities for.
>=20
>    To me this is an clear signal that callee capabilities are not the=20
>    correct mechanism for what you are trying to do.
>=20
> In a non-forking environment, the (sole) destination's Contact does
> get returned in failure responses, though.
[JRE] How? The Contact header field is not specified for any 4xx/5xx/6xx
response except 485.

> And if we implemnted
> HERFP, the same would probably be true.  But in the RFC 3261 model,
> where the UAC only gets a response from one destination, there is no
> way for the destination(s) to signal reliably that they support CC.
>=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 Tue Nov 27 16:48: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 1Ix8Hq-0006Lp-OE; Tue, 27 Nov 2007 16:48:10 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ix8Hp-0006Lc-H3
	for bliss@ietf.org; Tue, 27 Nov 2007 16:48:09 -0500
Received: from qmta08.emeryville.ca.mail.comcast.net ([76.96.30.80])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ix8Hp-0000Qy-3p
	for bliss@ietf.org; Tue, 27 Nov 2007 16:48:09 -0500
Received: from OMTA12.emeryville.ca.mail.comcast.net ([76.96.30.44])
	by QMTA08.emeryville.ca.mail.comcast.net with comcast
	id Hwdx1Y00E0x6nqc0A09400; Tue, 27 Nov 2007 21:48:12 +0000
Received: from dragon.ariadne.com ([24.34.79.42])
	by OMTA12.emeryville.ca.mail.comcast.net with comcast
	id HxoA1Y00G0umElk0800000; Tue, 27 Nov 2007 21:48:12 +0000
X-Authority-Analysis: v=1.0 c=1 a=JWoP8dSEmqYA:10 a=7_Bl_LBBIEVgbnepk4YA:9
	a=AQ_-X2GJkxKJtYjQ44PhXpE-D_gA:4 a=k4qQewaewV0A:10
	a=8y7tGHue6YMA:10
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 lARLm6Tc003606
	for <bliss@ietf.org>; Tue, 27 Nov 2007 16:48:06 -0500
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id lARLm6xM003602;
	Tue, 27 Nov 2007 16:48:06 -0500
Date: Tue, 27 Nov 2007 16:48:06 -0500
Message-Id: <200711272148.lARLm6xM003602@dragon.ariadne.com>
To: bliss@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <0D5F89FAC29E2C41B98A6A762007F5D0441DB1@GBNTHT12009MSX.gb002.siemens.net>
	(john.elwell@siemens.com)
Subject: Re: [BLISS] Use of Callee Capabilities for CCBS/CCNR
	support	indication
References: <F452BB3496398949B9D6634F9B6B155702A90A57@S4DE9JSAAMW.ost.t-com.de>
	<474AE54D.8060205@cisco.com>
	<200711272043.lARKh8xs018940@dragon.ariadne.com> 
	<0D5F89FAC29E2C41B98A6A762007F5D0441DB1@GBNTHT12009MSX.gb002.siemens.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
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: "Elwell, John" <john.elwell@siemens.com>

   > In a non-forking environment, the (sole) destination's Contact does
   > get returned in failure responses, though.

   [JRE] How? The Contact header field is not specified for any 4xx/5xx/6xx
   response except 485.

I've been assuming that the UAS does put a Contact header on its 4xx
response, and that the intermediate proxies propagate the Contact
header back.

Dale

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



From bliss-bounces@ietf.org Tue Nov 27 17:34:31 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 1Ix90h-00069X-49; Tue, 27 Nov 2007 17:34:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ix90f-000630-VS
	for bliss@ietf.org; Tue, 27 Nov 2007 17:34:29 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ix90e-0001rI-KW
	for bliss@ietf.org; Tue, 27 Nov 2007 17:34:29 -0500
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 27 Nov 2007 17:34:29 -0500
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lARMYSQh013078; 
	Tue, 27 Nov 2007 17:34:28 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id lARMYQBc003786; 
	Tue, 27 Nov 2007 22:34:28 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); 
	Tue, 27 Nov 2007 17:34:15 -0500
Received: from [161.44.174.179] ([161.44.174.179]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 Nov 2007 17:34:15 -0500
Message-ID: <474C9B67.60604@cisco.com>
Date: Tue, 27 Nov 2007 17:34:15 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Dale.Worley@comcast.net
Subject: Re: [BLISS] Use of Callee Capabilities for
	CCBS/CCNR	support	indication
References: <F452BB3496398949B9D6634F9B6B155702A90A57@S4DE9JSAAMW.ost.t-com.de>	<474AE54D.8060205@cisco.com>	<200711272043.lARKh8xs018940@dragon.ariadne.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0441DB1@GBNTHT12009MSX.gb002.siemens.net>
	<200711272148.lARLm6xM003602@dragon.ariadne.com>
In-Reply-To: <200711272148.lARLm6xM003602@dragon.ariadne.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Nov 2007 22:34:15.0404 (UTC)
	FILETIME=[A40032C0:01C83145]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=569; t=1196202868;
	x=1197066868; 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]=20Use=20of=20Callee=20Capabilities=20for=20CC
	BS/CCNR=09support=09indication |Sender:=20
	|To:=20Dale.Worley@comcast.net;
	bh=1+DN9WZA9o4u0h7sAybvZghUCk/SS/NUa2tb+q2JknA=;
	b=egFywWaWxhMVkJFO/jMlR7oiGuUSluNblnEj+Wu0B05jTjuJbSghFndh1QLAZ9IkD20ndfeY
	7D3oZZhD/litabkCqdxZ1b3XAIXE3fYvqYUD7kQIo2SHeGiIHlRvccNa;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
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



Dale.Worley@comcast.net wrote:
>    From: "Elwell, John" <john.elwell@siemens.com>
> 
>    > In a non-forking environment, the (sole) destination's Contact does
>    > get returned in failure responses, though.
> 
>    [JRE] How? The Contact header field is not specified for any 4xx/5xx/6xx
>    response except 485.
> 
> I've been assuming that the UAS does put a Contact header on its 4xx
> response,

Why?

Even if it was permitted, what possible value would it serve?

> and that the intermediate proxies propagate the Contact
> header back.

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



From bliss-bounces@ietf.org Tue Nov 27 17:34: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 1Ix910-0006H1-Nj; Tue, 27 Nov 2007 17:34:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ix90z-0006Gq-J0
	for bliss@ietf.org; Tue, 27 Nov 2007 17:34:49 -0500
Received: from agnada.com ([69.36.182.244])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ix90z-0001wg-7W
	for bliss@ietf.org; Tue, 27 Nov 2007 17:34:49 -0500
Received: from [192.168.1.101] (S0106001839eceb7a.vc.shawcable.net
	[24.80.240.54]) (authenticated bits=0)
	by agnada.com (8.12.11.20060308/8.12.11) with ESMTP id lARMYmFm016712
	for <bliss@ietf.org>; Tue, 27 Nov 2007 15:34:48 -0700
Message-ID: <474C9B86.7070300@ntt-at.com>
Date: Tue, 27 Nov 2007 14:34:46 -0800
From: Shida Schubert <shida@ntt-at.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
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] new call-completion draft available 
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


 According to the author, submission of the draft was rejected
by the tool due to old boilerplate of some sorts, so author
asked me to upload the draft on bliss-ietf.org.

 You can fetch the new document from the link below.

 http://www.bliss-ietf.org/drafts/draft-poetzl-bliss-call-completion-01.txt

 Regards
  Shida

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



From bliss-bounces@ietf.org Wed Nov 28 13:24: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 1IxRZs-0008IV-0x; Wed, 28 Nov 2007 13:24:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IxRZq-0008IB-JH
	for bliss@ietf.org; Wed, 28 Nov 2007 13:24:02 -0500
Received: from tcmail23.telekom.de ([217.6.95.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IxRZo-0007Kt-7s
	for bliss@ietf.org; Wed, 28 Nov 2007 13:24:02 -0500
Received: from S4DE9JSAANM.ost.t-com.de (S4DE9JSAANM.ost.t-com.de
	[10.125.177.122]) by tcmail21.telekom.de with ESMTP;
	Wed, 28 Nov 2007 19:23:57 +0100
Received: from S4DE9JSAAHW.ost.t-com.de ([10.125.177.160]) by
	S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 28 Nov 2007 19:23:57 +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: AW: [BLISS] new call-completion draft available 
Date: Wed, 28 Nov 2007 19:23:57 +0100
Message-Id: <CCA850DCD3FBE2479D5076C5C1873222029F5391@S4DE9JSAAHW.ost.t-com.de>
In-reply-to: <474C9B86.7070300@ntt-at.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] new call-completion draft available 
Thread-Index: AcgxRbrvO8ySaFSSTzeARizNRISQugAklseQ
From: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
To: <bliss@ietf.org>
X-OriginalArrivalTime: 28 Nov 2007 18:23:57.0470 (UTC)
	FILETIME=[D70713E0:01C831EB]
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
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 all,

sorry for uploading the draft late and using an old template, I hope you =
take the time and have a look at the draft nevertheless.

The main changes in the 01-version are:

- the document was revised in order to meet the requirements on a BLISS =
deliverable; it's surely not a final deliverable yet

- the overview and requirement section was removed, a much better =
description of a call-completion implementation can be found at =
http://www.ietf.org/internet-drafts/draft-worley-call-completion-00.txt, =
which is planned to be finalised seperately before being integrated in =
the Poetzl draft; again thank you very much Dale for the work

- the solution proposal for the call-completion possible indication was =
deleted, the proposal to define the usage of an Allows-events header in =
a 486 response was regarded as problemativ in mail discussions, e.g. no =
Contact header is available in a 486; this issue is of course part of =
the interoperability problem and has to be discussed

- other existing solutions have been added, like the usage of the dialog =
event package for an automatic redial as described in the services =
examples draft

- other solution proposals have been added, like the enhancement of the =
dialog event package for  informations also about call-completion states =
or like the definition of a new event package with the possibility of =
the dialog event package as a fallback (just as a first proposal to =
start discussion)

- the flows have been removed, they need a major revision when we get =
closer to a solution


Question and comments welcome.=20

Denis will be in Vancouver to present the status of the discussion and =
looks forward to discuss details with you.


BR, Martin


> -----Urspr=FCngliche Nachricht-----
> Von: Shida Schubert [mailto:shida@ntt-at.com]=20
> Gesendet: Dienstag, 27. November 2007 23:35
> An: bliss@ietf.org
> Betreff: [BLISS] new call-completion draft available=20
>=20
>=20
>=20
>  According to the author, submission of the draft was rejected
> by the tool due to old boilerplate of some sorts, so author
> asked me to upload the draft on bliss-ietf.org.
>=20
>  You can fetch the new document from the link below.
>=20
> =20
> =
http://www.bliss-ietf.org/drafts/draft-poetzl-bliss-call-completion-01.tx=
t

 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 Wed Nov 28 14:51: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 1IxSwt-0000tp-AX; Wed, 28 Nov 2007 14:51:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IxSwr-0000tN-La
	for bliss@ietf.org; Wed, 28 Nov 2007 14:51:53 -0500
Received: from zrtps0kp.nortel.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IxSwr-0002RO-Bl
	for bliss@ietf.org; Wed, 28 Nov 2007 14:51: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
	lASJpn802208; Wed, 28 Nov 2007 19:51:49 GMT
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] Use of Callee Capabilities for CCBS/CCNR	support
	indication
Date: Wed, 28 Nov 2007 13:50:41 -0600
Message-ID: <1ECE0EB50388174790F9694F77522CCF136F66A3@zrc2hxm0.corp.nortel.com>
In-Reply-To: <200711272148.lARLm6xM003602@dragon.ariadne.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] Use of Callee Capabilities for CCBS/CCNR	support
	indication
Thread-Index: AcgxPzi4DjFtkr5WQqmSpnUd4FxBcwAt/j+Q
References: <F452BB3496398949B9D6634F9B6B155702A90A57@S4DE9JSAAMW.ost.t-com.de>
	<474AE54D.8060205@cisco.com>
	<200711272043.lARKh8xs018940@dragon.ariadne.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0441DB1@GBNTHT12009MSX.gb002.siemens.net>
	<200711272148.lARLm6xM003602@dragon.ariadne.com>
From: "Brian Stucker" <bstucker@nortel.com>
To: <Dale.Worley@comcast.net>, <bliss@ietf.org>
X-Spam-Score: -4.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

=20

> -----Original Message-----
> From: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net]=20
> Sent: Tuesday, November 27, 2007 3:48 PM
> To: bliss@ietf.org
> Subject: Re: [BLISS] Use of Callee Capabilities for CCBS/CCNR=20
> support indication
>=20
>    From: "Elwell, John" <john.elwell@siemens.com>
>=20
>    > In a non-forking environment, the (sole) destination's=20
> Contact does
>    > get returned in failure responses, though.
>=20
>    [JRE] How? The Contact header field is not specified for=20
> any 4xx/5xx/6xx
>    response except 485.
>=20
> I've been assuming that the UAS does put a Contact header on=20
> its 4xx response, and that the intermediate proxies propagate=20
> the Contact header back.

I don't think we should take into account any possible solution that
does not at least comply with 3261. I don't know under what
circumstances this assumption was made, and am not trying to comment on
that in any way. However, we definitely should exclude this type of
'solution' from any BLISS documentation outcome for this feature for
this reason.

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



From bliss-bounces@ietf.org Wed Nov 28 14:54:38 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 1IxSzW-0002kf-Lv; Wed, 28 Nov 2007 14:54:38 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IxSzV-0002kT-Px
	for bliss@ietf.org; Wed, 28 Nov 2007 14:54:37 -0500
Received: from zcars04e.nortel.com ([47.129.242.56])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IxSzV-0006n2-Dq
	for bliss@ietf.org; Wed, 28 Nov 2007 14:54:37 -0500
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	lASJpK122421; Wed, 28 Nov 2007 19:51:20 GMT
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] Use of Callee Capabilities for	CCBS/CCNR	support
	indication
Date: Wed, 28 Nov 2007 13:53:26 -0600
Message-ID: <1ECE0EB50388174790F9694F77522CCF136F66C9@zrc2hxm0.corp.nortel.com>
In-Reply-To: <474C9B67.60604@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] Use of Callee Capabilities for	CCBS/CCNR	support
	indication
Thread-Index: AcgxRbBaXIqOLnNvTs+YO2Eel8POhgAsk8dQ
References: <F452BB3496398949B9D6634F9B6B155702A90A57@S4DE9JSAAMW.ost.t-com.de>
	<474AE54D.8060205@cisco.com>
	<200711272043.lARKh8xs018940@dragon.ariadne.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0441DB1@GBNTHT12009MSX.gb002.siemens.net>
	<200711272148.lARLm6xM003602@dragon.ariadne.com>
	<474C9B67.60604@cisco.com>
From: "Brian Stucker" <bstucker@nortel.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>, <Dale.Worley@comcast.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
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

=20

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]=20
> Sent: Tuesday, November 27, 2007 4:34 PM
> To: Dale.Worley@comcast.net
> Cc: bliss@ietf.org
> Subject: Re: [BLISS] Use of Callee Capabilities for CCBS/CCNR=20
> support indication
>=20
>=20
>=20
> Dale.Worley@comcast.net wrote:
> >    From: "Elwell, John" <john.elwell@siemens.com>
> >=20
> >    > In a non-forking environment, the (sole) destination's=20
> Contact does
> >    > get returned in failure responses, though.
> >=20
> >    [JRE] How? The Contact header field is not specified for=20
> any 4xx/5xx/6xx
> >    response except 485.
> >=20
> > I've been assuming that the UAS does put a Contact header=20
> on its 4xx=20
> > response,
>=20
> Why?
>=20
> Even if it was permitted, what possible value would it serve?

Well, assuming that you know it's a non-forking environment (the
originator used the no-fork directive) I could theoretically see having
a GRUU in a contact header in a 4xx being used to re-attempt the session
to a particular user agent after presumably addressing the reason for
the 4xx response.

It's a pretty contrived situation though. Especially if the proxy is
deterministic in it's routing decisions given the absence of forking.


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



From bliss-bounces@ietf.org Wed Nov 28 19:42:48 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 1IxXUN-0003hK-BL; Wed, 28 Nov 2007 19:42:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IxXUL-0003gE-RX
	for bliss@ietf.org; Wed, 28 Nov 2007 19:42:45 -0500
Received: from agnada.com ([69.36.182.244])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IxXUL-0003c1-AG
	for bliss@ietf.org; Wed, 28 Nov 2007 19:42:45 -0500
Received: from [192.168.1.101] (S0106001839eceb7a.vc.shawcable.net
	[24.80.240.54]) (authenticated bits=0)
	by agnada.com (8.12.11.20060308/8.12.11) with ESMTP id lAT0gXIA007543; 
	Wed, 28 Nov 2007 17:42:34 -0700
Message-ID: <474E0AF9.3030909@ntt-at.com>
Date: Wed, 28 Nov 2007 16:42:33 -0800
From: Shida Schubert <shida@ntt-at.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: bliss@ietf.org, Jonathan Rosenberg <jdrosen@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: 
Subject: [BLISS] Feedback: Problem Statement
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


 From our experience tackling the automatic call handling, and through
talk we had with people interested in contributing to the existing 
milestones,
we realized a need to change few things in the problem statement.

 We are going to be discussing this at the meeting next week, during the
time slot we assigned for Jonathan..

1. Defining a feature group --------------------------------
  Currently BLISS Solution Framework proposes the WG
  to identify a set of features(feature group) which have been known to 
have
  interoperability problems that are likely to share common source of 
problems.

 Issue: If there is a feature with real problem out there in the wild, 
this may hinder
      the work from progressing, simply due to it being the only feature 
of its kind,
      with no other feature with commonality.

 Proposal: Text in this phase can be a bit more lenient,
      so a single feature/service with a known problem can be brought
      in and worked upon, rather than wasting the time searching
      for other features sharing the common problems/characteristics to
      be considered.

2. Submit Feature Flow -----------------------------------------
  Currently BLISS Solution Framework asks to collect flows or
  explanatory text that articulates the logic specific to the feature
  for each of the components involved.

 Issue:  For milestone such as ACH, Call-Completion and even possibly
      call-park/pickup the baseline technologies may differ dramatically,
      and looking and comparing call-flows may mean little or nothing, as
      problem reside somewhere else where SIP is not involved.

       On the other hand, when the problem is apparent and
      specification used to satisfy the baseline requirements are the same
      across products that are suffering from interoperability problems,
      closer look at the call-flow may be necessary.

 Proposal: Allow for alternative approach for collecting information about
      the "feature"/"feature group", whether it be simple 
questions/answers, list of
      supported specs and call-flow etc. 


3. Scoping the functional primitives/deliverables -----------------------

  The functional primitive as defined in phase 1 merely works as a 
filter to
find other feature that may fit in the feature group.

 For ACH, the functional primitives in Phase 1 may have been

 "features that result in a retargeting or response operation that 
depend on
   user-specified criteria"

 as documented in the problem statement.

 Though when we get to phase 3, there may be multitudes of issues
associated with the interoperability problems, each of which may have
applicability elsewhere. For ACH it may be..
 
  1. Lacking common configuration method.
  2. Inconsistency in status code used for signaling certain state.
  3. Lack of mechanism to inform the client of the current ACH settings.

 Now are each of these a potential functional primitive therefore 
separate deliverable?
If we want to re-use whatever we define whether it be some sort of 
standard or BCP,
then the answer may be yes, but we then face the dilemma of not having 
the ability to
satisfy what's defined in the section 6 of the problem statement.

 "It is important that the feature group be well articulated in the 
title, so that implementors
   seeking guidance on these features can find it."

 Current recommendation for the deliverable in section 6 seems to lack 
the flexibility. There
needs to be some room for BLISS to define a deliverable at smaller scope 
(e.g. BCP
for sharing configuration status between UA and Proxy), which may then 
be referenced by
another document named "features that result in a retargeting or 
response operation
that depend on user-specified criteria".

 Any thoughts?

Regards
Shida       

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



