Re: [tcpm] WGLC: TCP's Reaction to Soft Errors

Ted Faber <faber@ISI.EDU> Tue, 08 May 2007 18:57 UTC

Return-path: <tcpm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlUsp-0002UG-7w; Tue, 08 May 2007 14:57:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlUsn-0002UA-Oc for tcpm@ietf.org; Tue, 08 May 2007 14:57:57 -0400
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HlUsm-0000Lz-BX for tcpm@ietf.org; Tue, 08 May 2007 14:57:57 -0400
Received: from hut.isi.edu (hut.isi.edu [128.9.168.160]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id l48IvSEB001104 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 8 May 2007 11:57:28 -0700 (PDT)
Received: (from faber@localhost) by hut.isi.edu (8.14.1/8.14.1/Submit) id l48IvSJd039604; Tue, 8 May 2007 11:57:28 -0700 (PDT) (envelope-from faber)
Date: Tue, 08 May 2007 11:57:28 -0700
From: Ted Faber <faber@ISI.EDU>
To: Joe Touch <touch@ISI.EDU>
Subject: Re: [tcpm] WGLC: TCP's Reaction to Soft Errors
Message-ID: <20070508185728.GE35315@hut.isi.edu>
References: <20070425034624.117871E18C7@lawyers.icir.org> <1178109923.25526.63.camel@localhost.localdomain> <20070503164412.GG46833@hut.isi.edu> <7.0.1.0.0.20070504050029.0357d590@gont.com.ar> <463BB4D9.8020801@isi.edu>
Mime-Version: 1.0
In-Reply-To: <463BB4D9.8020801@isi.edu>
User-Agent: Mutt/1.4.2.2i
X-url: http://www.isi.edu/~faber
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: faber@hut.isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: tcpm@ietf.org, Fernando Gont <fernando@gont.com.ar>, mallman@icir.org
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1695142242=="
Errors-To: tcpm-bounces@ietf.org

On Fri, May 04, 2007 at 03:34:01PM -0700, Joe Touch wrote:
> 
> 
> Fernando Gont wrote:
> > At 13:44 03/05/2007, Ted Faber wrote:
> > 
> >> This seems to have generated some discussion, and seems to me (with
> >> my chair hat) to be an interaction worth mentioning in the tcpm draft.
> >> I think that would be a lot easier to accomodate (i.e., easy to add
> >> without another WGLC round) if someone were to suggest a paragraph or 2
> >> to be included in the tcpm draft and we hammered out a quick consensus.
> >>
> >> Any takers?
> >>
> >> (And if I'm reading the group's take wrong here, let me know that, too.)
> > 
> > So far Saikat is for documenting this, and Joe for not doing so.
> 
> Largely because it focuses on behavior that is not BEHAVE compliant;
> IMO, this sort of thing should be for a BEHAVE-based 'implementation
> problems' doc. If we want to add this, are we adding all other known
> ICMP implementation errors?

It seems to me (hat's off) that a pitfall that this soft-errors response
causes when combined with an IETF BCP is a more constrained and
important case than an interaction between this response and a buggy
system.  I agree it needs to be flagged in the NAT literature as a
pitfall for BEHAVE NAT implementers.  I think it should also be flagged
here for TCP implementers who want to understand the ramifications of
this design choice (soft error == hard error during connection setup).
It's worth calling out against all the other potential design choices
because it conflicts with a BCP - implementation advice - rather than
just against observed behavior.

In the same way the soft-errs doc points out that a TCP that treats soft
errors as hard is out of step with ICMP and TCP standards, I think it
should point out that the decision violates the assumptions of the
BEHAVE BCP.

Anyone else care?  If it's just Saikat and me who think this warning
needs to be added, I'm not opposed to having the draft go to RFC as-is.

-- 
Ted Faber
http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.asc
Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www1.ietf.org/mailman/listinfo/tcpm