Hi Francois, Just in case you missed it, I repeat my proposal from yesterday. The clarification could be added to the note within section 6 of Outbound like this:
A Contact header field value with an instance-id media feature tag but no reg-id header field parameter is valid (this combination can be used in the GRUU [I-D.ietf-sip-gruu] specification as creation of gruu is not dependent on the presence or absence of reg-id parameter), but one with a reg-id but no instance-id is not. Regards, Erkki >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >Behalf Of ext Francois Audet >Sent: 14.October.2008 20:19 >To: Christer Holmberg; Paul Kyzivat >Cc: [email protected] >Subject: Re: [Sip] Is GRUU generated in the case of >registration withinstance-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 > _______________________________________________ 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
