IETF Logo Mail Archive

Re: Correct middlebox behavior

Ned Freed <ned.freed@mrochek.com> Wed, 28 September 2005 23:06 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKl0t-0001hp-2O; Wed, 28 Sep 2005 19:06:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKl0r-0001hb-FB for ietf@megatron.ietf.org; Wed, 28 Sep 2005 19:06:57 -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 TAA19820 for <ietf@ietf.org>; Wed, 28 Sep 2005 19:06:54 -0400 (EDT)
Received: from mauve.mrochek.com ([209.55.107.55]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKl8O-0006o8-C4 for ietf@ietf.org; Wed, 28 Sep 2005 19:14:45 -0400
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01LTKJQXYZUO0087DE@mauve.mrochek.com> (original mail from ned.freed@mrochek.com) for ietf@ietf.org; Wed, 28 Sep 2005 16:06:47 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=nowsp; d=mrochek.com; s=mauve; t=1127948807; h=Date: From:Subject:MIME-version:Content-type; b=FNJfoRRoduBv/mFQmRK0CpO/A T4nbNrYw30qYwILfWz/fuvFaOJulqM17WRTGEA8UTsEmluOMRJTVPHgucbDxg==
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01LTKE74NXDS000092@mauve.mrochek.com>; Wed, 28 Sep 2005 16:06:44 -0700 (PDT)
To: Fleischman Eric <eric.fleischman@boeing.com>
Message-id: <01LTKJQWUS8W000092@mauve.mrochek.com>
Date: Wed, 28 Sep 2005 16:04:43 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 28 Sep 2005 15:50:02 -0700" <474EEBD229DF754FB83D256004D02108BBC97E@XCH-NW-6V1.nw.nos.boeing.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <474EEBD229DF754FB83D256004D02108BBC97E@XCH-NW-6V1.nw.nos.boeing.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
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>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

> 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?

How about RFC 2979 section 3? It's specific to firewalls but of course
the concept generalizes to other sorts of middleboxes.

				Ned

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email