Re: [middisc] TCP middlebox option requirements
Andrew Knutsen <andrew.knutsen@bluecoat.com> Thu, 27 May 2010 22:31 UTC
Return-Path: <andrew.knutsen@bluecoat.com>
X-Original-To: middisc@core3.amsl.com
Delivered-To: middisc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 015E43A6BDD for <middisc@core3.amsl.com>; Thu, 27 May 2010 15:31:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id trn4KHWbARPw for <middisc@core3.amsl.com>; Thu, 27 May 2010 15:31:37 -0700 (PDT)
Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by core3.amsl.com (Postfix) with ESMTP id C7C7A3A6A1D for <middisc@ietf.org>; Thu, 27 May 2010 15:29:42 -0700 (PDT)
Received: from exchfront1.internal.cacheflow.com (exchfront1 [10.2.2.114]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id o4RMTMJp022850 for <middisc@ietf.org>; Thu, 27 May 2010 15:29:22 -0700 (PDT)
Received: from [10.9.84.250] ([10.9.84.250]) by exchfront1.internal.cacheflow.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 27 May 2010 15:29:17 -0700
Message-ID: <4BFEF23D.5060005@bluecoat.com>
Date: Thu, 27 May 2010 15:29:17 -0700
From: Andrew Knutsen <andrew.knutsen@bluecoat.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Ron Frederick <ronf@bluecoat.com>
References: <0C53DCFB700D144284A584F54711EC5809BD740A@xmb-sjc-21c.amer.cisco.com> <4BF6CF8A.5030707@bluecoat.com> <AF3CDDFAE1BB6C41B8F9EF3F4ADA9D11ADAB3597@MAILBOXES2.nbttech.com> <4BFC6B29.1080706@bluecoat.com> <2A7D4A79-0E08-480F-A67B-35338D226E14@bluecoat.com> <AF3CDDFAE1BB6C41B8F9EF3F4ADA9D11ADB9D3D6@MAILBOXES2.nbttech.com> <93730462-B3C5-4ACA-8C0A-C69F52BF0822@bluecoat.com> <B583FBF374231F4A89607B4D08578A4303EB17F3@bcs-mail03.internal.cacheflow.com> <ECD8F3EA-A5DB-4B47-B33F-E8952A6D2B4E@bluecoat.com>
In-Reply-To: <ECD8F3EA-A5DB-4B47-B33F-E8952A6D2B4E@bluecoat.com>
Content-Type: multipart/alternative; boundary="------------070107070500060800070806"
X-OriginalArrivalTime: 27 May 2010 22:29:17.0033 (UTC) FILETIME=[0AE46590:01CAFDEC]
Cc: middisc@ietf.org
Subject: Re: [middisc] TCP middlebox option requirements
X-BeenThere: middisc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussions on TCP option for middlebox discovery." <middisc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 May 2010 22:31:39 -0000
Ron Frederick wrote: > Andrew also wrote: >> One issue I just remembered with the OUI, and I can't remember who >> brought it up, is that it opens the option to "safe" (but >> unsanctioned) use for arbitrary purposes by anyone with an OUI. With >> vendor codes, we can specify criteria for assignment, so the vendor >> would be breaking their agreement if they used it for other purposes. >> >> It seems like this might be an IESG policy issue. Lars, are you >> still here? > > Who would perform this oversight? This gets into the points Anantha > was raising: > >> OUI as exists today is standardized and managed and provides >> unquiness. If we were to define a 1 byte vendor it, it has all issues >> which Ron mentioned below + the need for standardizing that space, I >> don't know who is going to manage allocation and maintenance of that >> field. I don't think IANA would do that. > > I could potentially see IANA handling the registrations here, but I > wouldn't expect them to be able to handle the approvals or do any > checking on whether vendors were "breaking their agreement" in the way > they used the option. To be honest, I'm not even sure I know what that > means. What sort of criteria would we be looking for here? This > doesn't seem like something we necessarily want to burden this process > with. What I was thinking is simply that there would be a stipulation (in the option spec) that when an entity applied for a vendor code that they'd use it for the specified purpose. Ie, not for some other purpose, or just to sit on. Then, if the option was seen "in the wild" being used inappropriately, the vendor would have an interest in not doing that since they'd be publicly breaking their agreement. No police (unless you count the vendor itself), just peer pressure, so to speak. Of, course, if we went with the OUI, the owner of that OUI would be responsible for breaking the spec if the option was used inappropriately. However I've picked up concerns that we need a bit more accountability. Andrew
- [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