Re: configuration NOTIFY in example 9.1 of outbound i-d

On Sep 29, 2008, at 3:26 PM, Paul Kyzivat wrote:

>
>
> Francois Audet wrote:
>>> > Section 4.3 states (UA procedures):
>>> >    If the UAC is sending a dialog-forming request, and wants all
>>> >    subsequent requests in the dialog to arrive over the same  
>>> flow, the
>>> >    UAC adds an 'ob' parameter to its Contact header.  Typically  
>>> this is
>>> >    desirable, but it is not necessary for example if the Contact  
>>> is a
>>> >    GRUU [I-D.ietf-sip-gruu].
>>> if contact is gruu, does it mean that 'ob' param is implicitly  
>>> included?
>> I am not sure why this is worded like this. I was thinking that  
>> using a GRUU as a contact in a dialog-forming request would mandate  
>> that
>> requests sent to that Contact would be sent using the same flow, but
>> I see no such rule in draft-ietf-sip-gruu.
>
> Gruu isn't dependent on outbound.
>
>

So explain this one for me, please.

Is it that, if the gruu was formed using outbound (that is, the "real"  
contact for which the gruu is an alias has an "ob") use of the gruu  
will use the "ob" in the dereferencing at the gruu-provider?

So for the example referenced above may be correct, but incomplete --  
it should talk about whether or not the gruu was formed using  
outbound, not just whether or not the contact isa gruu.

--
Dean




_______________________________________________
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