Re: [Sip] Is GRUU generated in the case of registration withinstance-ID and reg-ID
"Christer Holmberg" <christer.holmberg@ericsson.com> Tue, 14 October 2008 06:16 UTC
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B22DF3A6BB2; Mon, 13 Oct 2008 23:16:43 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A9F9728C0EA for <sip@core3.amsl.com>; Mon, 13 Oct 2008 23:16:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.196
X-Spam-Level:
X-Spam-Status: No, score=-6.196 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 DOt2cA7obMQv for <sip@core3.amsl.com>; Mon, 13 Oct 2008 23:16:41 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 7C6283A6BB2 for <sip@ietf.org>; Mon, 13 Oct 2008 23:16:41 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id CC81E20DAA; Tue, 14 Oct 2008 08:17:19 +0200 (CEST)
X-AuditID: c1b4fb3c-ad8cdbb0000015b5-85-48f4396ffa3c
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id A486620052; Tue, 14 Oct 2008 08:17:19 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 14 Oct 2008 08:17:08 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 14 Oct 2008 08:17:08 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0864D052@esealmw113.eemea.ericsson.se>
In-Reply-To: <7A726F54F791494C8D8C87F13736E80EF52279@vaebe106.NOE.Nokia.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Is GRUU generated in the case of registration withinstance-ID and reg-ID
Thread-Index: AcktB1xjBie2koRPTuygIDgnFDKCHAAVOQXAABh04SAAATzCcA==
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se> <1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com><CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se><48F23D27.8030305@voip.co.uk><CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se><48F2FC13.1070308@voip.co.uk> <CA9998CD4A020D418654FCDEF4E707DF05C0F8ED@esealmw113.eemea.ericsson.se> <7A726F54F791494C8D8C87F13736E80EF52279@vaebe106.NOE.Nokia.com>
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Erkki.Koivusalo@nokia.com, michael@voip.co.uk
X-OriginalArrivalTime: 14 Oct 2008 06:17:08.0750 (UTC) FILETIME=[7CCE3AE0:01C92DC4]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, audet@nortel.com
Subject: Re: [Sip] Is GRUU generated in the case of registration withinstance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
Hi Erkki, >>>Its been a long time, and the details are starting to get fuzzy in my mind. >> >>One should not have to remember the details - they should be clear by reading the specs :) > >I agree, however the specs often lack the rationale behind the agreed design choices. So even if you see something has specified in a certain >way, in some cases you will have hard time understanding why, unless you dig into the email archives. It is not about the rationale - but to understand the spec :) >>So, what is the justification for generating a gruu, but not returning it (after all, the gruu will be sent to the UA if it registers to the >>regevent package, so...)??? > >I also raised this question in march 2007 while reviewing GRUU spec and received an answer from Paul Kyzivat, who had a point: > > GRUU draft tells the registrar to create a public GRUU and a temporary > GRUU whenever it receives a REGISTER request with "+sip.instance" > Contact header parameter but only return them is the REGISTER request > contains Supported: gruu. > > Does this make any sense ? Why would the registrar have to create > those GRUUs if it would not return them to the UA ? > > The use case I am thinking is: > > - A registrar which supports both GRUU and Outbound > - An UA which supports Outbound but not GRUU > > Such an UA would send its Contact header with "+sip.instance" > parameter but it would not include Supported: gruu in its REGISTER. > Strictly speaking GRUU draft currently tells the registrar to create > GRUUs but not to return them to the UA. > > I would assume GRUU draft needs a small fix to tell the registrar to > create the GRUUs only if the REGISTER request contains "gruu" option > tag in Supported header. > > Do you agree or have I missed something ? > >This is partially one of those questions like "does a tree that falls make any noise if nobody is listening?" > >If in fact nobody will learn about this gruu then there is no need to create it. But that is all about the difference between the conceptual >model and the implementation, so it doesn't need to be stated. > >The problem arises when there are multiple observers of registration state. There are at least two ways this can happen: >- other UAs that register >- subscribers to the reg event package > >After you register, if others register they will get your contact back in the response to their register request, along with their own. If >they support gruu, then they will will see the permanent gruu and latest temp gruu for your contact. > >Similarly, when you register, any subscribers to the reg event package will get a notify telling of the change in registration state, >including your contact and the gruus that were "assigned" to you. > >Everything hangs together better this way. Still, if nobody is looking you don't have to assign these, as long as you do assign them when >somebody does start looking. If I don't support gruu, but I register to the regevent package, I WILL hear the tree falling, because I will receive the gruu in the NOTIFY :) Regards, Christer _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- [Sip] Is GRUU generated in the case of registrati… georg.mayer
- Re: [Sip] Is GRUU generated in the case of regist… Michael Procter
- Re: [Sip] Is GRUU generated in the case of regist… Francois Audet
- [Sip] Is GRUU generated in the case of registrati… Christer Holmberg
- Re: [Sip] Is GRUU generated in the case of regist… Francois Audet
- Re: [Sip] Is GRUU generated in the case of regist… Dale.Worley
- Re: [Sip] Is GRUU generated in the case of regist… Christer Holmberg
- Re: [Sip] Is GRUU generated in the case of regist… Christer Holmberg
- Re: [Sip] Is GRUU generated in the case of regist… Michael Procter
- Re: [Sip] Is GRUU generated in the case of regist… Paul Kyzivat
- Re: [Sip] Is GRUU generated in the case of regist… Francois Audet
- Re: [Sip] Is GRUU generated in the case of regist… Christer Holmberg
- Re: [Sip] Is GRUU generated in the case of regist… Christer Holmberg
- Re: [Sip] Is GRUU generated in the case of regist… Christer Holmberg
- Re: [Sip] Is GRUU generated in the case of regist… Michael Procter
- Re: [Sip] Is GRUU generated in the case of regist… Christer Holmberg
- Re: [Sip] Is GRUU generated in the case of regist… Michael Procter
- Re: [Sip] Is GRUU generated in the case of regist… Paul Kyzivat
- Re: [Sip] Is GRUU generated in the case of regist… Paul Kyzivat
- Re: [Sip] Is GRUU generated in the case of regist… Christer Holmberg
- Re: [Sip] Is GRUU generated in the case of regist… Erkki.Koivusalo
- Re: [Sip] Is GRUU generated in the case of regist… Christer Holmberg
- Re: [Sip] Is GRUU generated in the case of regist… Christer Holmberg
- Re: [Sip] Is GRUU generated in the case of regist… Paul Kyzivat
- Re: [Sip] Is GRUU generated in the case of regist… Francois Audet
- Re: [Sip] Is GRUU generated in the case of regist… Dean Willis
- Re: [Sip] Is GRUU generated in the case of regist… Christer Holmberg
- Re: [Sip] Is GRUU generated in the case of regist… Christer Holmberg
- Re: [Sip] Is GRUU generated in the case of regist… Dean Willis
- Re: [Sip] Is GRUU generated in the case of regist… Erkki.Koivusalo
- Re: [Sip] Is GRUU generated in the case of regist… Francois Audet
- Re: [Sip] Is GRUU generated in the case of regist… Francois Audet
- Re: [Sip] Is GRUU generated in the case of regist… Francois Audet
- Re: [Sip] Is GRUU generated in the case of regist… Christer Holmberg
- Re: [Sip] Is GRUU generated in the case of regist… Paul Kyzivat
- Re: [Sip] Is GRUU generated in the case of regist… DRAGE, Keith (Keith)