gruu in outbound-15 9.1

>

Original text:


>  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].  The flow used for the request is typically
>  the same flow the UA registered over, but it could be a new flow, for
>  example the initial subcription dialog for the configuration
>  framework [I-D.ietf-sipping-config-framework] needs to exist before
>  registration.


Proposed text:

Typically, a UAC using the procedures of this document and sending a
dialog-forming request will want all subsequent requests in the dialog
to arrive over the same flow. If the UAC is using a GRUU
[I-D.ietf-sip-gruu] that was instantiated using a Contact header field
value that included an "ob" parameter, the UAC sends teh request over
the flow used for registration and susequent requests will arrive over
that same flow. If the UAC is not using such a GRUU, then the UAC adds
an "ob" parameter to its Contact header field value.  This will cause
all subsequent requests in the dialog to arrive over the flow
instantiated by the dialog-forming request. This case is typical when
the request is sent prior to registration, such as in the the initial
subcription dialog for the configuration framework
[I-D.ietf-sipping-config-framework].


--
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