Christer Holmberg wrote: > Hi, > >>> 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...)??? >>> >> Sending a header parameter to a UA that doesn't declare it supports it >> seems to be inviting interop issues. I suspect this is the reason, >> although I wasn't involved with that decision so I can't say >> categorically what the reason was. >> > > Fair enough, but the UA is still going to get it if it subscribes to the > regevent package, isn't it? >
Yes, it is. > Does instance-id AND Require:gruu also RETURN the gruu? > No. GRUU draft section 5.2 contains: "If the REGISTER request contained a Supported header field that included the "gruu" option..." so the Supported header is needed (although you might get a pub-gruu if you squint at the parenthetical 'and the client supports GRUUs' since having a Require: gruu could be considered evidence of supporting gruus - I don't think this follows the spirit of the draft though). > Or, if I want the gruu returned, and I want to mandate the registrar to > support gruu, do I have to send: > > Instance-id AND Supported:gruu AND Require:gruu > GRUU draft, section 4.1 (extract from last paragraph): "If a UA wishes to guarantee that the REGISTER request is not processed unless the domain supports and uses this extension, it MAY include a Require header field in the request with a value that contains the "gruu" option tag. This is in addition to the presence of the Supported header field also containing the "gruu" option tag." So it looks like you need all three: +sip.instance, Require:gruu and Supported: gruu. > Whatever the answer to my question is - clarification would be > appretiated :) > I hope this helps! Michael _______________________________________________ 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
