Re: [Sip] RE: Correction: WGLC for draft-ietf-sip-outbound
Rohan Mahy <rohan@ekabal.com> Mon, 03 December 2007 22:45 UTC
Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzK2R-0007eX-5C; Mon, 03 Dec 2007 17:45:19 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IzK2O-0007A8-QN for sip-confirm+ok@megatron.ietf.org; Mon, 03 Dec 2007 17:45:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzK2O-00074K-9g for sip@ietf.org; Mon, 03 Dec 2007 17:45:16 -0500
Received: from figas.ekabal.com ([204.61.215.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IzK2M-0002Ak-Do for sip@ietf.org; Mon, 03 Dec 2007 17:45:16 -0500
Received: from [127.0.0.1] (figas.ekabal.com [204.61.215.10]) (authenticated) by figas.ekabal.com (8.11.6/8.11.6) with ESMTP id lB3MieU21025; Mon, 3 Dec 2007 14:44:40 -0800
In-Reply-To: <1196674882.13248.28.camel@scotty>
References: <46928F5F.3080502@softarmor.com> <46966F52.9040004@softarmor.com> <5D1A7985295922448D5550C94DE2918001473D89@DEEXC1U01.de.lucent.com> <46B7ABEB.50207@nokia.com> <0C12AF7F-AB54-4B2D-A028-4C394761024A@ekabal.com> <1196674882.13248.28.camel@scotty>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <8739474A-FC28-4626-BB7E-A705A4C2262A@ekabal.com>
Content-Transfer-Encoding: 7bit
From: Rohan Mahy <rohan@ekabal.com>
Subject: Re: [Sip] RE: Correction: WGLC for draft-ietf-sip-outbound
Date: Mon, 03 Dec 2007 14:44:40 -0800
To: Aki Niemi <aki.niemi@nokia.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Cc: sip@ietf.org, Rohan Mahy <rohan@ekabal.com>, "ext DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>, Cullen Jennings <fluffy@cisco.com>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org
Hi Aki, Don't shoot the messenger ;-) I think most of our disconnect here is based on the ability to do keepalives outside of outbound. We had consensus to make the document so someone could implement STUN keepalives over UDP that does not implement outbound. This motivated the keep-stun URI parameter, later merged into the keep URI parameter. Since the correct keepalive responses are required by the first hop when doing outbound, the UAC *could* infer the ability to send keepalive pings and receive pongs based on the a successful outbound registration working over the same flow. We could get rid of the keep parameter for outbound registration and only use it in non-outbound keepalive uses (and move the definition to section 8), but we would need to get the consensus of the WG to do that. More brief comments inline... On Dec 3, 2007, at 1:41 AM, Aki Niemi wrote: > Inline. > > la, 2007-12-01 kello 12:59 -0800, ext Rohan Mahy kirjoitti: >>> o First, I don't understand why the keepalive params are needed at >>> all. >>> It's simple, really: if the UAC opens a TCP flow, it needs to use >>> CRLF. >>> If it opens a UDP flow, it needs to use STUN. Or am I missing >>> something? >> >> we merged the keep-stun and keep-crlf into a simple 'keep' parameter. >> this 'keep' parameter just allows the UAC to know if it will get a >> pong in response to its pings. > > Huh? Sending the pong is mandatory. if the implementation supports outbound. (see above) >>> Why does the UA need to know beforehand that it needs to use the >>> default >>> interval keepalive? Could this not be returned in the 200 OK >>> instead? >> it probably could, but it is not clear where it would go in the >> 200 OK. > > How about Flow-Expires: 120 I like it, but we need consensus to switch to that. >>> All in all, I don't see the reason that these parameters need to be >>> pre-configured to the UA as the draft suggests. Seems they are >>> either >>> self-evident (based on transport), or something the registrar/edge- >>> proxy >>> could return in a header field or parameter at register-time. Much >>> cleaner IMHO. >> what we have may be ugly, but it will work and we appear to have >> consensus on it. > > I remember some very wise advice on these sorts of things: a spec is > ready only when there are no non-critical features left to remove. > > I think this is definitely one such feature. More below. > >>> o In 3.2. example message: >>> >>> REGISTER sip:example.com;keep-crlf SIP/2.0 >>> >>> Why does this parameter need to be in the R-URI? >> >> the parameter does not need to be there. It could instead be in the >> topmost Route header for example. > > You mean could, SHOULD, or MUST? whether the parameter is there or not is a by product of where it appears (in which URIs). depending on where the URI came from , it gets copied to various places. outbound does not change those rules. > </snip> > >> This should just work, but the single UA/proxy would need to return a >> Path header, otherwise the UA would have no way of discovering >> support for keepalive responses. > > Again, what purpose does the keep parameter then server? again, we would need to agree to assume that an outbound registration is "good-enough". This is certainly safe for any server that correctly implements the spec. >>> My question is: where did this 2 minutes come from? Is it based on >>> some >>> hard data, like empirical evidence or user experience studies? >> >> No. It was pulled out of thin air. >> >>> If not, >>> how about 14 minutes instead? Much better on the battery and should >>> still play nice with the NATs. >> >> There was some expectation that the UA would be willing to lose 2 >> minutes of phone calls, but 14 minutes would be a lot of time to be >> off the air. > > We don't have that today. In fact, today we have a one hour > re-registration interval, and I don't see a lot of people complaining. > >> Certainly, the UA can use something short (like 2 >> minutes) for one flow, and 14 minutes for any additional flows >> without many ill effects. > > 2 minutes is too short. It drains the battery. Do you think having an > additional flow in addition to the 2-minute flow will improve the > situation? I'm not the one you need to convince here. ;-) thanks, -rohan _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- [Sip] WGLC for draft-ietf-sip-outbound Dean Willis
- [Sip] RE: WGLC for draft-ietf-sip-outbound DRAGE, Keith (Keith)
- [Sip] 4xx message for informing user of an existi… Avasarala Ranjit-A20990
- Re: [Sip] 4xx message for informing user of an ex… Paul Kyzivat
- Re: [Sip] 4xx message for informing user of an ex… Dale.Worley
- [Sip] Correction: WGLC for draft-ietf-sip-outbound Dean Willis
- [Sip] Outbound: TCP and SigComp Adam Roach
- [Sip] Outbound: Feature Tag (Ab)Use Adam Roach
- Re: [Sip] Outbound: Feature Tag (Ab)Use Jeroen van Bemmel
- Re: [Sip] Outbound: Feature Tag (Ab)Use Dale.Worley
- Re: [Sip] Outbound: Feature Tag (Ab)Use Dale.Worley
- Re: [Sip] Outbound: Feature Tag (Ab)Use Adam Roach
- [Sip] Re: Outbound: Feature Tag (Ab)Use Rohan Mahy
- [Sip] Re: Outbound: Feature Tag (Ab)Use Rohan Mahy
- Re: [Sip] Re: Outbound: Feature Tag (Ab)Use Jeroen van Bemmel
- [Sip] RE: Correction: WGLC for draft-ietf-sip-out… DRAGE, Keith (Keith)
- Re: [Sip] RE: Correction: WGLC for draft-ietf-sip… Robert Sparks
- RE: [Sip] RE: Correction: WGLC for draft-ietf-sip… DRAGE, Keith (Keith)
- Re: [Sip] RE: Correction: WGLC for draft-ietf-sip… Aki Niemi
- [Sip] Re: Outbound: TCP and SigComp Rohan Mahy
- Re: [Sip] RE: Correction: WGLC for draft-ietf-sip… Rohan Mahy
- [Sip] Re: Outbound: Feature Tag (Ab)Use Rohan Mahy
- Re: [Sip] Re: Outbound: Feature Tag (Ab)Use Rohan Mahy
- Re: [Sip] Re: Outbound: Feature Tag (Ab)Use Rohan Mahy
- Re: [Sip] RE: Correction: WGLC for draft-ietf-sip… Aki Niemi
- Re: [Sip] RE: Correction: WGLC for draft-ietf-sip… Rohan Mahy