Re: [middisc] middisc specification update
"Anantha Ramaiah (ananth)" <ananth@cisco.com> Tue, 06 March 2012 15:17 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 7A91E21F8783 for <middisc@ietfa.amsl.com>; Tue, 6 Mar 2012 07:17:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.237
X-Spam-Level:
X-Spam-Status: No, score=-9.237 tagged_above=-999 required=5 tests=[AWL=0.762, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U+aSSRn32CqH for <middisc@ietfa.amsl.com>; Tue, 6 Mar 2012 07:17:02 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 5052E21F8793 for <middisc@ietf.org>; Tue, 6 Mar 2012 07:17:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ananth@cisco.com; l=3615; q=dns/txt; s=iport; t=1331047022; x=1332256622; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=zyEJ7/I26t3iP2IYvzsgmImJokrWZEF04asVI9hJFs8=; b=U8jm7O2Qm6g/PDiwaLGCU2u6as8HbLCTb5G+A9gsc8/sGEfNNEQlXSqj 3Mhx660dkcn1qHH5qQR8x76Y9pocGt33tt+gBHfqzhAL45eb24CzVpKPS FJSXHmdGAan7GSnVMlOvocfbAqjczFsksCPWBDOwjjj/N+i3bS4rzZZYY I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAGgpVk+rRDoI/2dsb2JhbABDtGuBB4F9AQEBAwESAR0KPwwEAgEIEQEDAQEBCgYXAQYBRQMGCAEBBAESCBqHYAQBmiEBnxGPe2MEiFKdA4MEgTs
X-IronPort-AV: E=Sophos;i="4.73,540,1325462400"; d="scan'208";a="34659700"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 06 Mar 2012 15:17:02 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q26FH2xY001778; Tue, 6 Mar 2012 15:17:02 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 6 Mar 2012 07:17:02 -0800
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: Tue, 06 Mar 2012 07:17:00 -0800
Message-ID: <0C53DCFB700D144284A584F54711EC580EA21EDC@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <DB9B280D-B61E-4E4C-A7CC-7BCB08FD361E@netapp.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [middisc] middisc specification update
Thread-Index: AcyG5wLVJKtf0Y74SiSodjFq7qJ2lxObcJ+QAAJE5sAI3dxCQACIKKiAAC1JnuA=
References: <4E9241F7.5090406@mti-systems.com><2AE215BDC76842F885AC7E9D34BD2CA4@davidPC><0C53DCFB700D144284A584F54711EC580E546254@xmb-sjc-21c.amer.cisco.com><0C53DCFB700D144284A584F54711EC580EA21847@xmb-sjc-21c.amer.cisco.com> <DB9B280D-B61E-4E4C-A7CC-7BCB08FD361E@netapp.com>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Eggert, Lars" <lars@netapp.com>, middisc@ietf.org
X-OriginalArrivalTime: 06 Mar 2012 15:17:02.0081 (UTC) FILETIME=[2E8C8710:01CCFBAC]
Subject: Re: [middisc] middisc specification update
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: Tue, 06 Mar 2012 15:17:03 -0000
Hi Lars, I missed this email and just got to this. Comments inline.. > -----Original Message----- > From: middisc-bounces@ietf.org [mailto:middisc-bounces@ietf.org] On > Behalf Of Eggert, Lars > Sent: Monday, March 05, 2012 1:32 AM > To: middisc@ietf.org > Cc: Martin Stiemerling > Subject: Re: [middisc] middisc specification update > > Hi, > > On Mar 3, 2012, at 1:42, Anantha Ramaiah (ananth) wrote: > > I just posted a draft (draft-ananth-middisc-tcpopt-00.txt) which is a > > result of all the discussions we have had among the stakeholders. > > a few comments on the ID. (Also CC'ing Martin as the incoming AD.) > > Lars > > > I think you need to add some text that says that although TCP is > end-to-end and therefore network infrastructure was supposed to not > mess with the TCP headers, current deployment practice has resulted > in > middleboxes that do in fact "violate" the original architecture in > order to address a perceived need. This shouldn't say whether that's > good or bad, but merely acknowledges reality and encourages use of a > shared documented option number for such uses. Right, to my reply to Wes's other email, I acknowledged that there is need to add text to cover the aspect of option poaching etc., > > > INTRODUCTION, paragraph 1: > > Intended status: Informational > > You need to make this PS. Or do you want to ask for IESG Approval of > the option number? Wes's response to my comment was to make it Experimental. So we have 3 choices : info (current), experimental and PS. I am not sure, whichever is the fastest route in getting the TCP option allocated, I'll take that :-) Of course, this is just my opinion. Other stakeholders may have different opinion. > > > INTRODUCTION, paragraph 5: > > This document describes a TCP option for use by middleboxes to > > facilitate transparent detection of other middleboxes along the > path > > of the TCP connection during the connection initiation phase. The > > option has no effect if an appropriate middlebox is not present on > > the path. > > I'd move all the rest of the abstract to the introduction; not > appropriate > for the abstract. Good point. I'll move the rest to the introduction section. > > > Section 6., paragraph 4: > > The TCP-MDO option is incompatible with TCP options which aim to > > protect the integrity of the TCP SYN. An example of such an > option > > is the TCP MD5 signature option[RFC2385]. Such TCP options are > not > > commonly seen by current WAN optimization systems, so the > restriction > > should not pose any worries. > > Also, more importantly, TCP-AO. Right, I just gave an example. I can also list AO as reference. > > > Section 7., paragraph 3: > > IANA is also requested to assign an 8 bit vendor code that can be > > used to differentiate multiple vendors and to maintain an > associated > > registry. > > Insufficient information to define the registry. Please read RFC5226 > on how to write an IANA considerations section. Ok. > > > Section 7., paragraph 5: > > Vendor TCP option number > > -------------------------------------- > > Bluecoat 253 > > Cisco 33 > > I thought we also knew about Riverbed and Citrix? Right, I know Riverbed's option usage, not sure about Citrix. Does anyone have a contact point for Citrix? Thanks, -Anantha >
- Re: [middisc] middisc specification update Anantha Ramaiah (ananth)
- [middisc] middisc specification update Wesley Eddy
- Re: [middisc] middisc specification update Anantha Ramaiah (ananth)
- Re: [middisc] middisc specification update David Harrington
- Re: [middisc] middisc specification update Anantha Ramaiah (ananth)
- Re: [middisc] middisc specification update Andrew Knutsen
- Re: [middisc] middisc specification update Anantha Ramaiah (ananth)
- Re: [middisc] middisc specification update Andrew Knutsen
- Re: [middisc] middisc specification update Anantha Ramaiah (ananth)
- Re: [middisc] middisc specification update Eggert, Lars
- Re: [middisc] middisc specification update Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]
- Re: [middisc] middisc specification update Anantha Ramaiah (ananth)
- Re: [middisc] middisc specification update Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]
- Re: [middisc] middisc specification update Anantha Ramaiah (ananth)
- Re: [middisc] middisc specification update Anantha Ramaiah (ananth)
- Re: [middisc] middisc specification update Frederick, Ron
- Re: [middisc] middisc specification update Anantha Ramaiah (ananth)
- Re: [middisc] middisc specification update Eggert, Lars
- Re: [middisc] middisc specification update Anantha Ramaiah (ananth)
- Re: [middisc] middisc specification update Mani Ramasamy (mani)
- Re: [middisc] middisc specification update David Harrington
- Re: [middisc] middisc specification update Frederick, Ron
- Re: [middisc] middisc specification update Andrew Knutsen
- Re: [middisc] middisc specification update Anantha Ramaiah (ananth)
- Re: [middisc] middisc specification update Frederick, Ron
- Re: [middisc] middisc specification update Wesley Eddy
- Re: [middisc] middisc specification update Knutsen, Andrew
- Re: [middisc] middisc specification update Anantha Ramaiah (ananth)