IETF Logo Mail Archive

Re: Correct middlebox behavior

Melinda Shore <mshore@cisco.com> Thu, 29 September 2005 12:32 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKxaP-0000Z1-R9; Thu, 29 Sep 2005 08:32:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKxaN-0000XZ-Kh for ietf@megatron.ietf.org; Thu, 29 Sep 2005 08:32:27 -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 IAA07963 for <ietf@ietf.org>; Thu, 29 Sep 2005 08:32:25 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKxi1-0000bd-K7 for ietf@ietf.org; Thu, 29 Sep 2005 08:40:22 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 29 Sep 2005 05:32:18 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.97,156,1125903600"; d="scan'208"; a="11732607:sNHT21462692"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j8TCWFT6022491; Thu, 29 Sep 2005 08:32:15 -0400 (EDT)
Received: from xmb-rtp-205.amer.cisco.com ([64.102.31.59]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 29 Sep 2005 08:32:14 -0400
Received: from 10.21.96.44 ([10.21.96.44]) by xmb-rtp-205.amer.cisco.com ([64.102.31.59]) via Exchange Front-End Server email.cisco.com ([171.70.151.187]) with Microsoft Exchange Server HTTP-DAV ; Thu, 29 Sep 2005 12:32:14 +0000
User-Agent: Microsoft-Entourage/11.0.0.040405
Date: Thu, 29 Sep 2005 08:32:13 -0400
From: Melinda Shore <mshore@cisco.com>
To: "Fleischman, Eric" <eric.fleischman@boeing.com>
Message-ID: <BF61570D.F61%mshore@cisco.com>
In-Reply-To: <474EEBD229DF754FB83D256004D02108BBC97E@XCH-NW-6V1.nw.nos.boeing.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 29 Sep 2005 12:32:15.0138 (UTC) FILETIME=[D2B84020:01C5C4F1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
Cc: 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

On 9/28/05 6:50 PM, "Fleischman, Eric" <eric.fleischman@boeing.com> wrote:
> 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.

Well, there is no IETF consensus on correct middlebox behavior.
The behave working group is putting together documents that
I think are probably pretty close to what you're asking for.
RFC 3424 describes IAB concerns about some NAT workaround
techniques but in that case the burden is on the workaround,
not the middlebox.

Melinda

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

v2.23.0 | Report a Bug | By Email