Re: [martini] Call for Consensus: Support for Public GRUUs

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Thu, 02 September 2010 15:55 UTC

Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: martini@core3.amsl.com
Delivered-To: martini@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E7143A6947 for <martini@core3.amsl.com>; Thu, 2 Sep 2010 08:55:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.071
X-Spam-Level:
X-Spam-Status: No, score=-103.071 tagged_above=-999 required=5 tests=[AWL=-0.822, BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
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 rEk72z5Wyyj8 for <martini@core3.amsl.com>; Thu, 2 Sep 2010 08:55:47 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by core3.amsl.com (Postfix) with ESMTP id 5F89C3A6783 for <martini@ietf.org>; Thu, 2 Sep 2010 08:55:47 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o82FuClt031214 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 2 Sep 2010 17:56:12 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.45]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Thu, 2 Sep 2010 17:56:09 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Brian Lindsay <brian.lindsay@genband.com>, "martini@ietf.org" <martini@ietf.org>
Date: Thu, 02 Sep 2010 17:56:06 +0200
Thread-Topic: [martini] Call for Consensus: Support for Public GRUUs
Thread-Index: AQHLSH/IKQ3MhHlFZ0qQLnxMeK98apL6giGggAJ3yvCAADRywIABrjxw
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE214D29B8B@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <BLU137-W878D9ABB4B6A396E0682493860@phx.gbl>, <F1A0ED6425368141998E077AC43334E414EA89F9@gbplmail01.genband.com> <BLU137-W122E29863A150E6483B96893870@phx.gbl> <B59189B7-671D-4627-9B78-4A60213D2475@cisco.com> <F1A0ED6425368141998E077AC43334E414EA8E49@gbplmail01.genband.com> <EDC0A1AE77C57744B664A310A0B23AE214CC0BBF@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <F1A0ED6425368141998E077AC43334E414EA92EC@gbplmail01.genband.com>
In-Reply-To: <F1A0ED6425368141998E077AC43334E414EA92EC@gbplmail01.genband.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.84
Subject: Re: [martini] Call for Consensus: Support for Public GRUUs
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of en-mass SIP PBX registration mechanisms <martini.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/martini>, <mailto:martini-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/martini>
List-Post: <mailto:martini@ietf.org>
List-Help: <mailto:martini-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/martini>, <mailto:martini-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Sep 2010 15:55:49 -0000

According to the rough rule of thumb figures I learnt 30 years ago, on average 50% of the traffic is internal to a PBX and 50% outside. While those figures may have changed over the intervening years due to more advance private networking, I'm sure they are not that far out. So you are eliminating the usages of services that may use GRUUs from 50% of the traffic, based on the desire or not of the service provider to implement a capability.

More concerning is that the absence or not of this capability is totally invisible to the end UA, and indeed even to many elements of the PBX itself. So we have no means to find out whether a capability exists before we actually try and use it.

regards

Keith 

> -----Original Message-----
> From: Brian Lindsay [mailto:brian.lindsay@genband.com] 
> Sent: Wednesday, September 01, 2010 3:29 PM
> To: DRAGE, Keith (Keith); martini@ietf.org
> Subject: RE: [martini] Call for Consensus: Support for Public GRUUs
> 
> Hi Keith,
> 
>    Agree an individual UA within an enterprise doesn't have 
> any choice about business trunking arrangement used, but the 
> parent enterprise deploying the PBX and UA's does. An 
> enterprise would be free to select a specific service 
> provider that offered a GRUU capability if that was important 
> to the enterprise from a service perspective. (Service 
> providers could hypothetically even charge for GRUU as an 
> incremental capability).
> 
>   Also, what precludes usage of GRUU's internally within an 
> enterprise as long as the PBX doesn't send them towards the network?
> 
>   Thanks
>      Brian
> 
> 
> -----Original Message-----
> From: DRAGE, Keith (Keith) [mailto:keith.drage@alcatel-lucent.com]
> Sent: Wednesday, September 01, 2010 7:09 AM
> To: Brian Lindsay; martini@ietf.org
> Subject: RE: [martini] Call for Consensus: Support for Public GRUUs
> 
> No.
> 
> The key question is whether the SSP end supports GRUU (as 
> originally posted), so it is available to a PBX UA if it 
> requires a service that uses it.
> 
> While I agree that GRUU is currently optional for registrars 
> to deploy, I suspect that if we started SIP now, an 
> appropriate mechanism would have been a mandatory element for 
> registrars. Optional is possible in the direct UA to 
> registrar case because the UA at least has some direct choice 
> over which registrars it uses.
> 
> In the PBX environment, a UA wishing to use GRUUs to 
> implement a service has very little choice over which 
> business trunking arrangements it uses.
> 
> So no support of GRUUs at the SSP in business trunking means 
> no service using GRUUs within the private network.
> 
> Keith
> 
> > -----Original Message-----
> > From: martini-bounces@ietf.org
> > [mailto:martini-bounces@ietf.org] On Behalf Of Brian Lindsay
> > Sent: Monday, August 30, 2010 10:30 PM
> > To: Cullen Jennings; martini@ietf.org
> > Subject: Re: [martini] Call for Consensus: Support for Public GRUUs
> > 
> > Hi,
> > 
> >   If GIN truly "breaks" SIP, then wouldn't that mean that SIP PBXs, 
> > and their UA's, would also need to be mandated to support 
> GRUU (which 
> > doesn't seem to be the suggestion).
> > 
> >   Now perhaps something like an out-of-dialog REFER for 
> Call Transfer 
> > to the SIP PBX won't be possible without GRUU. But is that truly a 
> > mandatory capability that is required to be supported as part of a 
> > basic SIP PBX offering by a service provider? Or would be 
> ubiquitously 
> > supported/allowed by SIP PBXs?
> > 
> >  Thanks
> >      Brian
> > 
> > -----Original Message-----
> > From: martini-bounces@ietf.org
> > [mailto:martini-bounces@ietf.org] On Behalf Of Cullen Jennings
> > Sent: Monday, August 30, 2010 4:13 PM
> > To: martini@ietf.org
> > Subject: Re: [martini] Call for Consensus: Support for Public GRUUs
> > 
> > 
> > GIN breaks significant parts of SIP without GRUUs (or some 
> equivalent 
> > functionality) so I think we need GRUUs to be required to 
> be implement 
> > on the SSP side of GIN.
> > 
> > 
> > On Aug 28, 2010, at 1:44 PM, Bernard Aboba wrote:
> > 
> > > At the IETF 78 MARTINI WG meeting, during the discussion of
> > Ticket 57 (relating to temporary GRUUs), a suggestion was made that 
> > public GRUUs be mandatory to implement for SSPs.
> > > 
> > > We will now attempt to determine whether consensus exists
> > within the MARTINI WG to make this change to the document. 
> > > 
> > > Please respond to this email and post your opinion as to
> > whether you agree that SSPs supporting MARTINI MUST 
> implement support 
> > for public GRUUs.
> > > 
> > > This consensus call will last until September 12, 2010.  
> > > _______________________________________________
> > > martini mailing list
> > > martini@ietf.org
> > > https://www.ietf.org/mailman/listinfo/martini
> > 
> > 
> > Cullen Jennings
> > For corporate legal information go to:
> > http://www.cisco.com/web/about/doing_business/legal/cri/index.html
> > 
> > 
> > 
> > _______________________________________________
> > martini mailing list
> > martini@ietf.org
> > https://www.ietf.org/mailman/listinfo/martini
> > _______________________________________________
> > martini mailing list
> > martini@ietf.org
> > https://www.ietf.org/mailman/listinfo/martini
> > 
>