I agree with Christer: I thought the keep-alive indication was staying too, and that it was the timer part that was out. The keep-alive mechanism is really independent of the rest of outbound. It could have been a separate draft even. While I like the overall outbound extension, there are plenty of people supporting endpoints behind NATs today, for whom the new keep-alive mechanism would be very useful by itself while the rest of outbound is not.
I do agree with a point someone made about going down a slippery-slope of separating individual behaviors of extensions being a bad idea in general. But there's always a judgment call that has to be made based on what we think people will want and what it useful, and personally I think keep-alive fits that bill. Otherwise I am fairly confident we will see the "proxies" lying about outbound support to the endpoints, simply to get the keep-alive behavior from them. -hadriel > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Christer Holmberg > Sent: Friday, March 07, 2008 10:22 PM > To: Dean Willis > Cc: [email protected]; Rohan Mahy; Francois Audet; Xavier Marjou; Cullen > Jennings > Subject: Re: [Sip] Outbound-12: STUN keep-alives without outbound > > Hi Dean, > > >>> The edge proxy is only supposed to add the ob parameter to > >>> the Path if the edge proxy included a flow token in the path > >>> URI. This should only happen when the UA included a reg-id > >>> and instance-id parameter in its Contact header. > >> > >> Correct. But, the point is that the UA would then still be "allowed" > >> to use STUN keep-alive between itself and the outbound proxy, even if > the > >> registrar doesn't support outbound. > > > >So I think you're saying that we've gotten the decision as to whether > >to use keepalive between the UA and the edge proxy tangled up with > >whether or not we use the outbound-style persistent binding at the > >registrar? > > Yes. > > >Perhaps if the keepalive negotiation were independent of outbound, it > >would work better for you. > > Well, that is what I initially said in this thread, and what I believe we > already did have before Outbound-12: the outbound proxy was able to insert > the "keep" parameter in the Path header to indicate support of keep- > alive... > > I think that the UA relying on configuration whether the outbound proxy > supports keep-alive or not is never going to work - especially not in > mobile environments... > > 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
