IETF Logo Mail Archive

Re: [middisc] middisc specification update

"Mani Ramasamy (mani)" <mani@cisco.com> Wed, 07 March 2012 14:31 UTC

Return-Path: <mani@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 6FAFE21F869A for <middisc@ietfa.amsl.com>; Wed, 7 Mar 2012 06:31:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 Iv7Wiy7gDOLv for <middisc@ietfa.amsl.com>; Wed, 7 Mar 2012 06:31:54 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 8912721F8693 for <middisc@ietf.org>; Wed, 7 Mar 2012 06:31:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mani@cisco.com; l=2390; q=dns/txt; s=iport; t=1331130714; x=1332340314; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=VIj85I35JgoXw7bG3YQjkVgMaoGeKkCGDiChDlFQeoI=; b=U03jvPnOMc7F7rbOr/ijntkTTkZmby4UhdtY76eUGyB2Paz0uEYj++n4 8dFuHZeIiezgAAwMLGgi9xGC9j9u5tqAu5gZRJrnGLvZRKpEN9yy+hzdc opjhlEUFq35Fnq0S4G0q7j2FSjyqY9TmeY37PPC09yn4fyvNeFyRIWve3 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAFJwV0+rRDoH/2dsb2JhbABDtReBB4IKAQEBBAEBAQ8BHQo0CwwEAgEIEQQBAQEKBhcBBgEmHwkIAgQTCBMHh2UBC5oKAZ8qBJAMYwSIUp0GgwQ
X-IronPort-AV: E=Sophos;i="4.73,546,1325462400"; d="scan'208";a="34971862"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 07 Mar 2012 14:31:54 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q27EVskl028620; Wed, 7 Mar 2012 14:31:54 GMT
Received: from xmb-sjc-223.amer.cisco.com ([128.107.191.124]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 7 Mar 2012 06:31:54 -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: Wed, 07 Mar 2012 06:31:54 -0800
Message-ID: <4EF101F7236DB443A8FABF8164BFBD0C0F46BE0C@xmb-sjc-223.amer.cisco.com>
In-Reply-To: <0C53DCFB700D144284A584F54711EC580EA222B6@xmb-sjc-21c.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [middisc] middisc specification update
Thread-Index: AcyG5wLVJKtf0Y74SiSodjFq7qJ2lxObcJ+QAAJE5sAI3dxCQACKW9EQAABRXxAAVSWDgAAHzeFAAAIEGQAAEL2wEAAULzrw
References: <4E9241F7.5090406@mti-systems.com><2AE215BDC76842F885AC7E9D34BD2CA4@davidPC><0C53DCFB700D144284A584F54711EC580E546254@xmb-sjc-21c.amer.cisco.com><0C53DCFB700D144284A584F54711EC580EA21847@xmb-sjc-21c.amer.cisco.com><C304DB494AC0C04C87C6A6E2FF5603DB5ACE4EFBB5@NDJSSCC01.ndc.nasa.gov><0C53DCFB700D144284A584F54711EC580EA21B2D@xmb-sjc-21c.amer.cisco.com><56A8F14C-C1E1-4793-BC82-F27E89A9F8D4@bluecoat.com><0C53DCFB700D144284A584F54711EC580EA222B2@xmb-sjc-21c.amer.cisco.com><71231A86-7A22-48C0-987F-5C01C25E7B33@netapp.com> <0C53DCFB700D144284A584F54711EC580EA222B6@xmb-sjc-21c.amer.cisco.com>
From: "Mani Ramasamy (mani)" <mani@cisco.com>
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>, "Eggert, Lars" <lars@netapp.com>
X-OriginalArrivalTime: 07 Mar 2012 14:31:54.0321 (UTC) FILETIME=[0B02E410:01CCFC6F]
Cc: "Frederick, Ron" <ron.frederick@bluecoat.com>, middisc@ietf.org
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: Wed, 07 Mar 2012 14:31:55 -0000

I agree with Anantha. If the process is light weight with a reasonably
quick turnaround time, I think it would encourage the vendors to get
their code points registered.


Mani.

-----Original Message-----
From: middisc-bounces@ietf.org [mailto:middisc-bounces@ietf.org] On
Behalf Of Anantha Ramaiah (ananth)
Sent: Wednesday, March 07, 2012 12:19 AM
To: Eggert, Lars
Cc: Frederick, Ron; middisc@ietf.org
Subject: Re: [middisc] middisc specification update

Lars,
    Actually a good question. My simple answer (as you probably can
guess) is to have some provision made in a hope that any vendor would
try to approach the IETF before trying to adopt other evil means. It is
a just a best effort, I guess :-)
    Funny, since IETF is not a policing agency, but I would be tempted
to think if enough visibility is made on use cases that are "illegal"
then that would force vendors to change, but there seems to be no formal
way of enforcing this other than using some methods like this. Just let
us take the example of the current draft. Mani (Cisco) who was one of
the early architect of the WAN opt solution approached the IANA for
getting this TCP option allocated, but later on got busy and never
followed it up. Then with Bluecoat's draft,  and the formation of
middisc we have multiple vendors participating on this effort and
agreeing in principle to move to the new TCP option. This is definitely
a good progress and I should thank the initiative taken by you and Wes
and David's support for getting this alias formed.

-Anantha

> -----Original Message-----
> From: Eggert, Lars [mailto:lars@netapp.com]
> Sent: Wednesday, March 07, 2012 12:04 AM
> To: Anantha Ramaiah (ananth)
> Cc: Frederick, Ron; <middisc@ietf.org>
> Subject: Re: [middisc] middisc specification update
> 
> On Mar 7, 2012, at 8:55, Anantha Ramaiah (ananth) wrote:
> > Fair enough.  We can note that some vendor codes are going to be
> > reserved (FF to F0). These can be used to extend as needed tomorrow.
> > Would that address your concern?
> 
> Idle thought: What makes us think that vendors will go through IANA to
> get one of these codepoints, when they have been squatting on option
> numbers already?
> 
> Lars
_______________________________________________
middisc mailing list
middisc@ietf.org
https://www.ietf.org/mailman/listinfo/middisc

v2.23.0 | Report a Bug | By Email