Re: Is GRUU generated in the case of registration with instance-ID and reg-ID

"Christer Holmberg" <[email protected]>
Newsgroups gmane.ietf.sip
Message-ID <CA9998CD4A020D418654FCDEF4E707DF086A6463@esealmw113.eemea.ericsson.se>
Hi,

The text would be something like:

"NOTE: If the registrar supports gruu [reference-to-gruu-spec], the
presence of the instance-id in the REGISTER request will also trigger
the registrar to generate a gruu for the user, as described in
[reference-to-gruu-spec]."

I will look for a place in the outbound draft where to put it, but it
really isn't more complicated than that. Just a simple clarification
note :)

Regards,

Christer

 

-----Original Message-----
From: Francois Audet [mailto:[email protected]] 
Sent: 14. lokakuuta 2008 20:19
To: Christer Holmberg; Paul Kyzivat
Cc: Michael Procter; [email protected]
Subject: RE: [Sip] Is GRUU generated in the case of registration with
instance-ID and reg-ID

Can you propose actual text for a specific section. 

> -----Original Message-----
> From: Christer Holmberg [mailto:[email protected]]
> Sent: Monday, October 13, 2008 22:13
> To: Paul Kyzivat
> Cc: Michael Procter; [email protected]; Audet, Francois (SC100:3055)
> Subject: RE: [Sip] Is GRUU generated in the case of registration with 
> instance-ID and reg-ID
> 
> 
> Hi,
> 
> >>Yes. The question was whether instance-id AND reg-id also create a
> gruu.
> >>The answer seems to be yes, but I think it would be good to clarify 
> >>that somewhere.
> >
> >Since reg-id isn't mentioned in gruu, its irrelevant to the
> gruu spec,
> just as any other parameters are.
> 
> That is why I proposed it is clarified in the outbound spec :)
> 
> Regards,
> 
> Christer
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email protected] for questions on current sip
Use [email protected] for new developments on the application of sip
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.