Re: [Sip] WGLC for draft-ietf-sip-fork-loop-fix-01.txt

Robert Sparks <rjsparks@estacado.net> Thu, 20 April 2006 23:07 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FWiFM-0000I7-F7; Thu, 20 Apr 2006 19:07:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FWiFK-0000Hw-JU for sip@ietf.org; Thu, 20 Apr 2006 19:07:34 -0400
Received: from dsl001-129-069.dfw1.dsl.speakeasy.net ([72.1.129.69] helo=vicuna.estacado.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWiFK-0006bO-8C for sip@ietf.org; Thu, 20 Apr 2006 19:07:34 -0400
Received: from [203.178.157.234] (203-178-157-234.ip.sipit.net [203.178.157.234] (may be forged)) (authenticated bits=0) by vicuna.estacado.net (8.13.4/8.13.4) with ESMTP id k3KN7VXr043273 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Thu, 20 Apr 2006 18:07:32 -0500 (CDT) (envelope-from rjsparks@estacado.net)
In-Reply-To: <4447B6EC.9090007@lucent.com>
References: <5EB80D22825EEE42872083AD5BFFB5945D1D59@esealmw113.eemea.ericsson.se> <19567930-BFE9-4B19-AB59-ED30AEB365D0@estacado.net> <4447A6DB.5000607@lucent.com> <A2DDCCAD-61BD-47E8-A2E9-2899E70FD56E@estacado.net> <4447B6EC.9090007@lucent.com>
Mime-Version: 1.0 (Apple Message framework v749.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <EE88D63F-DD5F-4BFF-B775-E38F8CC7BC3F@estacado.net>
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@estacado.net>
Subject: Re: [Sip] WGLC for draft-ietf-sip-fork-loop-fix-01.txt
Date: Fri, 21 Apr 2006 08:07:11 +0900
To: "Vijay K. Gurbani" <vkg@lucent.com>
X-Mailer: Apple Mail (2.749.3)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: sip@ietf.org
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

inline
On 21-Apr-06, at 1:29 AM, Vijay K. Gurbani wrote:

> Robert Sparks wrote:
>>> Also, I am confused -- in previous bakeoffs, we have successfully  
>>> tested loop detection; so why can't we do this now?
>> Well - if you remember, we went through a lot of pain at each event
>> when we were testing new implementations of loop detection. By the
>> end of  each event, most of the people that were trying to get it
>> right got it working, but at the start, it was a mess.
>
> Yes, I remember those pains very well.  But most implementations
> that did the "advanced scenarios" did eventually -- after much
> configuration problems -- get it working with the set of headers
> (except the Via header) suggested in rfc3261.
>
>> That basically went away when we went to max-forwards because most  
>> people just took that logic out. Now that we're asking for it again,
>> we're right back to things not working.
>
> That's the thing that puzzles me -- rfc3261 never deprecated loop
> detection in favor of M-F.  All through until rfc3261 was released
> (June 2002) and even thereafter, we used to do the loop detection
> tests in the bakeoffs.  But I have not attended the bakeoff in the
> last couple of years, so is it the case that somewhere down the
> line we stopped doing loop detection tests in the bakeoffs
> despite it still being a MAY in rfc3261?

We still run the loop/spirals test. But for the last several years of  
SIPits,
almost no-one used the loop-detection concept. The vast majority of
implementations relied on max-forwards to end loops.

RjS

>
> Oh well...
>
> - vijay
> -- 
> Vijay K. Gurbani  vkg@{lucent.com,research.bell-labs.com,acm.org}
> Bell Laboratories, Lucent Technologies, Inc.
> 2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)


_______________________________________________
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