IETF Logo Mail Archive

Re: [BLISS] Comments ondraft-procter-bliss-call-park-extension-04(AutoRetrieve proposal)

"Elwell, John" <john.elwell@siemens-enterprise.com> Wed, 29 April 2009 13:21 UTC

Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D08BE3A6EE4 for <bliss@core3.amsl.com>; Wed, 29 Apr 2009 06:21:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.459
X-Spam-Level:
X-Spam-Status: No, score=-2.459 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EOOsXJ-IwmR4 for <bliss@core3.amsl.com>; Wed, 29 Apr 2009 06:21:17 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk [195.171.110.225]) by core3.amsl.com (Postfix) with ESMTP id 7D3673A6EBE for <bliss@ietf.org>; Wed, 29 Apr 2009 06:20:39 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235]) by siemenscomms.co.uk (PMDF V6.3-x14 #31430) with ESMTP id <0KIV004CJ6GOWN@siemenscomms.co.uk> for bliss@ietf.org; Wed, 29 Apr 2009 14:22:00 +0100 (BST)
Date: Wed, 29 Apr 2009 14:22:07 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
In-reply-to: <1ECE0EB50388174790F9694F77522CCF1DAFDC77@zrc2hxm0.corp.nortel.com>
To: Francois Audet <audet@nortel.com>, Michael Procter <michael@voip.co.uk>, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D001D4AED1@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] Comments ondraft-procter-bliss-call-park-extension-04(AutoRetrieve proposal)
Thread-Index: AcnH379mPYvnr/YMSiWHVN2WIN5LmQAM/XnAAC5piyA=
Content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
References: <F592E36A5C943E4E91F25880D05AD1140937CB3E@zrc2hxm0.corp.nortel.com> <a2ef85430904240846k3a301efk4302165a3d9eded1@mail.gmail.com> <1ECE0EB50388174790F9694F77522CCF1DA436E8@zrc2hxm0.corp.nortel.com> <a2ef85430904242329p1baf3fa4o7e366d9a3f7a928c@mail.gmail.com> <719F9BBB3E7E71428A2D13F3D76C768F01A1EF33@GBNTHT12009MSX.gb002.siemens.net> <a2ef85430904271011m17fedc62n23f4487790aed62@mail.gmail.com> <1ECE0EB50388174790F9694F77522CCF1DAA2BE6@zrc2hxm0.corp.nortel.com> <719F9BBB3E7E71428A2D13F3D76C768F01A1F19E@GBNTHT12009MSX.gb002.siemens.net> <a2ef85430904280200n226f218asd75ee82a426d7727@mail.gmail.com> <1ECE0EB50388174790F9694F77522CCF1DAFDC77@zrc2hxm0.corp.nortel.com>
Cc: bliss@ietf.org, Scott Orton <orton@nortel.com>
Subject: Re: [BLISS] Comments ondraft-procter-bliss-call-park-extension-04(AutoRetrieve proposal)
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Apr 2009 13:21:19 -0000

I agree - I would like something to be said about it.

John 

> -----Original Message-----
> From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org] 
> On Behalf Of Francois Audet
> Sent: 28 April 2009 16:13
> To: Michael Procter; Hutton, Andrew
> Cc: bliss@ietf.org; Scott Orton
> Subject: Re: [BLISS] Comments 
> ondraft-procter-bliss-call-park-extension-04(AutoRetrieve proposal)
> 
> Basically, I think a CallPark without an autoretrieve is
> effectively an "unsafe" feature, since it will result in
> users (typically customers) to wait forever in the 
> parking space. 
> 
> > -----Original Message-----
> > From: Michael Procter [mailto:michael@voip.co.uk] 
> > Sent: Tuesday, April 28, 2009 02:00
> > To: Hutton, Andrew
> > Cc: Audet, Francois (SC100:3055); bliss@ietf.org; Orton, 
> > Scott (RICH1:B620)
> > Subject: Re: [BLISS] Comments on 
> > draft-procter-bliss-call-park-extension-04(AutoRetrieve proposal)
> > 
> > 2009/4/28 Hutton, Andrew <andrew.hutton@siemens-enterprise.com>:
> > >
> > > I agree with Francois it would I assume be the Referred-by 
> > header that 
> > > contains the URI of the park server and as long as the UA 
> can match 
> > > this against it's local configuration then this will be ok.
> > 
> > That would probably be more straightforward.  But it assumes 
> > a particular way of achieving the feature.
> > 
> > > I do think we should have a short description of the 
> auto-retrieve 
> > > procedure including an example message flow in the draft.
> > 
> > I'm still not entirely convinced that it belongs in this 
> > draft, although I agree it is an important aspect to consider 
> > in an implementation.  I'm also not sure that it is within 
> > scope for BLISS, given that it does seem to be trying to 
> > standardise a feature over and above the level needed for 
> > 'basic interoperability'.
> > 
> > However, I am open to persuasion!  To that end, I'd 
> > appreciate contributions of text / message flows.
> > 
> > Michael
> > 
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www.ietf.org/mailman/listinfo/bliss
>

v2.23.0 | Report a Bug | By Email