Re: [middisc] TCP middlebox option requirements
"Anantha Ramaiah (ananth)" <ananth@cisco.com> Wed, 08 June 2011 21:57 UTC
Return-Path: <ananth@cisco.com>
X-Original-To: middisc@ietfa.amsl.com
Delivered-To: middisc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3048C21F853C for <middisc@ietfa.amsl.com>; Wed, 8 Jun 2011 14:57:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.436
X-Spam-Level:
X-Spam-Status: No, score=-10.436 tagged_above=-999 required=5 tests=[AWL=0.163, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uyq-trUZPFNz for <middisc@ietfa.amsl.com>; Wed, 8 Jun 2011 14:57:10 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id 532D721F843E for <middisc@ietf.org>; Wed, 8 Jun 2011 14:57:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ananth@cisco.com; l=1856; q=dns/txt; s=iport; t=1307570230; x=1308779830; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=/rUkG4gyZHUPv78VFE6yGOEU5wAMyMvDKhjR1VHDzUw=; b=fotBQsn/LubOWOPSYrlesbTuKA6LXjso3hVRpzTlJyUJCsVdhPq2F5n8 M+Cj+rTV4hMZeIuA5coUCPPnsEIFBGOgzV1QnJlgnTkH8/zzLdhEFbbiJ oFHAcCHnr/ek2YUQbrN0IKLk9aSXIRfOiKrGW++v5j92aMEvScnD8S5jg 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsBAOvv702rRDoG/2dsb2JhbABTl0aOb3eIcaBcnXyGIwSGf45yixU
X-IronPort-AV: E=Sophos;i="4.65,340,1304294400"; d="scan'208";a="333057397"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-3.cisco.com with ESMTP; 08 Jun 2011 21:56:53 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p58Lurhj031819; Wed, 8 Jun 2011 21:56:53 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 8 Jun 2011 14:56:53 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 08 Jun 2011 14:56:49 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC580CEE513B@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <974FE049BD0F2E4188567FAD99DEF03301B4BD@PWSVL-EXCMBX-01.internal.cacheflow.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [middisc] TCP middlebox option requirements
Thread-Index: AcwmI0zFfltUolLcSMitiuc7V9sSUAAAn9xA
References: <974FE049BD0F2E4188567FAD99DEF03301B4BD@PWSVL-EXCMBX-01.internal.cacheflow.com>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Knutsen, Andrew" <andrew.knutsen@bluecoat.com>, middisc@ietf.org
X-OriginalArrivalTime: 08 Jun 2011 21:56:53.0134 (UTC) FILETIME=[F9F8B2E0:01CC2626]
Subject: Re: [middisc] TCP middlebox option requirements
X-BeenThere: middisc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussions on TCP option for middlebox discovery." <middisc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/middisc>, <mailto:middisc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/middisc>
List-Post: <mailto:middisc@ietf.org>
List-Help: <mailto:middisc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/middisc>, <mailto:middisc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2011 21:57:11 -0000
I am in the process of forming a outline for the new draft which I'll be sharing soon. That said, response to the comment inline :- > -----Original Message----- > From: middisc-bounces@ietf.org [mailto:middisc-bounces@ietf.org] On > Behalf Of Knutsen, Andrew > Sent: Wednesday, June 08, 2011 2:44 PM > To: middisc@ietf.org > Subject: [middisc] TCP middlebox option requirements > > > While we're waiting for any more details that may help us reach > consensus on the format of the option, I've been thinking about the > text we'll use to restrict its uses. This text would be guidance to > the IANA (or other assigning authority) to determine when to assign a > vendor or standard code. It could also be used for policing after > assignment, but thats a bit more problematic (although that's all that > would be possible in the OUI/PEN case). > > There are a few details to be considered, but I'm curious about one > thing which is perhaps fundamental: > > Do we anticipate any use of this option where the intended consumer > of the option is the actual host at the destination IP address? > (Excepting responses). I would think the answer is : yes. But, we want to accommodate such an use case if possible without burning a lot of cycles and making modifications. I believe this shouldn't be a problem. > > To me, this is a pretty clear discriminator for a "middlebox > option". My impression is that we want a minimum of requirements in > the text, so that we can all use this for the things we need it for; > however we also want to make sure its not a "catch-all", like the old > SNAP option. Agreed. -Anantha > > Andrew > > _______________________________________________ > middisc mailing list > middisc@ietf.org > https://www.ietf.org/mailman/listinfo/middisc
- [middisc] TCP middlebox option requirements Anantha Ramaiah (ananth)
- Re: [middisc] TCP middlebox option requirements Andrew Knutsen
- Re: [middisc] TCP middlebox option requirements Mark Day
- Re: [middisc] TCP middlebox option requirements Mark Day
- Re: [middisc] TCP middlebox option requirements Andrew Knutsen
- Re: [middisc] TCP middlebox option requirements Mark Day
- Re: [middisc] TCP middlebox option requirements Andrew Knutsen
- Re: [middisc] TCP middlebox option requirements Ron Frederick
- Re: [middisc] TCP middlebox option requirements Anantha Ramaiah (ananth)
- Re: [middisc] TCP middlebox option requirements Mark Day
- Re: [middisc] TCP middlebox option requirements Ron Frederick
- Re: [middisc] TCP middlebox option requirements Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]
- Re: [middisc] TCP middlebox option requirements Knutsen, Andrew
- Re: [middisc] TCP middlebox option requirements Andrew Knutsen
- Re: [middisc] TCP middlebox option requirements Ron Frederick
- Re: [middisc] TCP middlebox option requirements Andrew Knutsen
- Re: [middisc] TCP middlebox option requirements Mark Day
- Re: [middisc] TCP middlebox option requirements Lars Eggert
- Re: [middisc] TCP middlebox option requirements Andrew Knutsen
- Re: [middisc] TCP middlebox option requirements Ron Frederick
- Re: [middisc] TCP middlebox option requirements Ron Frederick
- Re: [middisc] TCP middlebox option requirements David Harrington
- Re: [middisc] TCP middlebox option requirements Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]
- Re: [middisc] TCP middlebox option requirements Anantha Ramaiah (ananth)
- Re: [middisc] TCP middlebox option requirements Andrew Knutsen
- Re: [middisc] TCP middlebox option requirements Andrew Knutsen
- Re: [middisc] TCP middlebox option requirements Anantha Ramaiah (ananth)
- Re: [middisc] TCP middlebox option requirements Andrew Knutsen
- Re: [middisc] TCP middlebox option requirements Anantha Ramaiah (ananth)
- Re: [middisc] TCP middlebox option requirements Andrew Knutsen
- Re: [middisc] TCP middlebox option requirements Anantha Ramaiah (ananth)
- Re: [middisc] TCP middlebox option requirements Andrew Knutsen
- Re: [middisc] TCP middlebox option requirements Frederick, Ron
- [middisc] TCP middlebox option requirements Knutsen, Andrew
- Re: [middisc] TCP middlebox option requirements Anantha Ramaiah (ananth)
- Re: [middisc] TCP middlebox option requirements Frederick, Ron
- Re: [middisc] TCP middlebox option requirements Andrew Knutsen