Re: [middisc] middisc specification update

"Anantha Ramaiah (ananth)" <ananth@cisco.com> Thu, 08 March 2012 20:26 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 EF86D21E8049 for <middisc@ietfa.amsl.com>; Thu, 8 Mar 2012 12:26:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.77
X-Spam-Level:
X-Spam-Status: No, score=-9.77 tagged_above=-999 required=5 tests=[AWL=0.829, 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 RVY+nHEy-2mZ for <middisc@ietfa.amsl.com>; Thu, 8 Mar 2012 12:26:52 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 4F62121E8047 for <middisc@ietf.org>; Thu, 8 Mar 2012 12:26:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ananth@cisco.com; l=891; q=dns/txt; s=iport; t=1331238412; x=1332448012; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=NFt9CzwCMyQckeuXX6x/weWrnvp7MLTHYKXMZsIjcfo=; b=NMkHWMfLIaUyPlNJogNeVX7wdS2gkyV4PepLbNA8Ec+eCfUcvELqamPt awfjlPJ1gGPBOJKoK7b4ejNxpCsUQcAQYVRDWyRkUr8xgpfQ6cCqP/FBf tUuUQ0QQ0fJMTYaADrA9UWqowvGuAzQe5Y6HtdMnikKe+qSuJflE2SnWf 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAOsVWU+rRDoI/2dsb2JhbABDtSmBB4ILAQEEEgEdCj8QAgEIIgYYBgFWAgQTCBqHZwGbQQGfCI9zYwSIUp0LgwQ
X-IronPort-AV: E=Sophos;i="4.73,553,1325462400"; d="scan'208";a="32614050"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 08 Mar 2012 20:26:51 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q28KQod9027299; Thu, 8 Mar 2012 20:26:50 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 8 Mar 2012 12:26:50 -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: Thu, 08 Mar 2012 12:26:50 -0800
Message-ID: <0C53DCFB700D144284A584F54711EC580EAB248A@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <C06D0C27-D8F1-4847-BB0A-A1EBF458A55E@bluecoat.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [middisc] middisc specification update
Thread-Index: AcyG5wLVJKtf0Y74SiSodjFq7qJ2lxObcJ+QAAJE5sAI3dxCQACKW9EQAABRXxAAVSWDgAAHzeFAAEsLsQAADcGhoA==
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> <C06D0C27-D8F1-4847-BB0A-A1EBF458A55E@bluecoat.com>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Frederick, Ron" <ron.frederick@bluecoat.com>
X-OriginalArrivalTime: 08 Mar 2012 20:26:50.0873 (UTC) FILETIME=[CB289690:01CCFD69]
Cc: 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: Thu, 08 Mar 2012 20:26:53 -0000

Hi Ron,
> 
> > Allow standard type codes to be allocated starting with 0x00 in an
> increasing fashion and allow vendor codes to be allocated starting
with
> 0xFE in a decreasing fashion. At some point, if it looks like too many
> vendor codes are being allocated, IANA can declare that no more are
> available and that additional vendors must use the 0xFF form with an
> OUI, leaving the remainder of the space for standard type codes.
> 
> What do others think of this?

Question : when you say vendor code, are you saying one vendor can get
multiple vendor codes? Or is strictly one per vendor. I assumed the
latter.

When you say "standard type", what are those? Are those the ones used by
multiple vendors and really interoperable?

Just wanted to make sure we both are on the same page w.r.t terminology.

-Anantha
> --
> Ron Frederick
> ronf@bluecoat.com