On Oct 2, 2008, at 11:03 AM, Juha Heinanen wrote:

Dean Willis writes:

So what do you think is broken now?

see my message a few days ago to the list.  i have read only a few
percent of outbound text and at least this paragraph is broken:

  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.


Ah. Thanks.

I'll follow that one up on the list on the thread in which it was raised.

also, i'm questioning why outbound i-d does not provide a general
solution to "usage of the same flow for in-dialog requests" problem:

 outbound behavior is also needed in case of regular presence server.
that is why i don't quite understand is why is this "usage of the same flow for in-dialog requests" feature tied to outbound proxy. why is it not useful to have a generic capability for UAC to tell to the next hop (a proxy or UAS) in its dialog initiating request that "please use this
 flow for subsequent requests of this dialog"?

It probably is useful, just as having keepalive separate from outbound is probably useful. If we were designing outbound from scratch, we'd probably break those two functions out into separate drafts, and have outbound use them.

Given that we can, if we find it sufficiently useful, add a generic connect-reuse modifier apart from outbound, Is it worth derailing outbound in order to fix it at this stage?

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

Reply via email to