Re: Correct middlebox behavior
Joe Touch <touch@ISI.EDU> Thu, 29 September 2005 18:15 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EL2wT-0004kE-F6; Thu, 29 Sep 2005 14:15:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EL2wR-0004k8-0c for ietf@megatron.ietf.org; Thu, 29 Sep 2005 14:15:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26393 for <ietf@ietf.org>; Thu, 29 Sep 2005 14:15:33 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EL347-0000z8-Uf for ietf@ietf.org; Thu, 29 Sep 2005 14:23:33 -0400
Received: from [128.30.5.18] (30-5-18.wireless.csail.mit.edu [128.30.5.18]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j8TIEgL20152; Thu, 29 Sep 2005 11:14:42 -0700 (PDT)
Message-ID: <433C2F10.80001@isi.edu>
Date: Thu, 29 Sep 2005 11:14:40 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Fleischman, Eric" <eric.fleischman@boeing.com>
References: <474EEBD229DF754FB83D256004D02108BBC97E@XCH-NW-6V1.nw.nos.boeing.com>
In-Reply-To: <474EEBD229DF754FB83D256004D02108BBC97E@XCH-NW-6V1.nw.nos.boeing.com>
X-Enigmail-Version: 0.92.0.0
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: Keith Moore <moore@cs.utk.edu>, ietf@ietf.org
Subject: Re: Correct middlebox behavior
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1331832832=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
This doesn't cover all of what middleboxes do, but the part about them faking responses (e.g., to splice connections), hijacking, or NATing are covered in RFC1122 sec 3.2.1.3: When a host sends any datagram, the IP source address MUST be one of its own IP addresses (but not a broadcast or multicast address). I don't see anything in 1812 that prohibits routers from modifying the contents of an IP datagram, but the term 'forwarding' never permits modification of the IP payload either. Joe Fleischman, Eric wrote: > Friends, > > I believe that Keith's first paragraph below is widely accepted by the > IETF. However, after re-reading RFC 3234, RFC 3303, and others I did not > find any text within any RFC to explain our consensus opinion concerning > correct middlebox behavior to be used to guide those outside of our > community. Specifically, can anyone point me to text within any RFC that > states the ideas contained within Keith's first paragraph below? > > --Eric > > -----Original Message----- > From: Keith Moore [mailto:moore@cs.utk.edu] > Subject: Re: Question about the normative nature of IETF RFCs > > >>Most protocols weren't designed to operate with middleboxes. >>In the absence of a provision in a protocol specification for >>a middlebox, any middlebox that interferes with the >>interoperation of a protocol is inherently violating the >>protocol standards. > > >>In general, protocol specifications don't (and shouldn't) >>try to explicitly enumerate "don't do X" for every possible >>"X" that is harmful. And middleboxes are generally harmful. > > > > _______________________________________________ > Ietf mailing list > Ietf@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Correct middlebox behavior Fleischman, Eric
- Re: Correct middlebox behavior Ned Freed
- Re: Correct middlebox behavior Melinda Shore
- Re: Correct middlebox behavior Joe Touch