Re: [nvo3-dt-encap] [nvo3] Encap draft published by design team
Joe Touch <touch@isi.edu> Fri, 10 February 2017 21:41 UTC
Return-Path: <touch@isi.edu>
X-Original-To: nvo3-dt-encap@ietfa.amsl.com
Delivered-To: nvo3-dt-encap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 4B9FD129C5B;
Fri, 10 Feb 2017 13:41:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5,
RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id VgGRORdlyxLP; Fri, 10 Feb 2017 13:41:06 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id BAA7F129452;
Fri, 10 Feb 2017 13:41:06 -0800 (PST)
Received: from [128.9.184.104] ([128.9.184.104]) (authenticated bits=0)
by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1ALeHZQ018304
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT);
Fri, 10 Feb 2017 13:40:25 -0800 (PST)
To: Tom Herbert <tom@herbertland.com>
References: <CA+C0YO0yz4KBe=w+EXHVBA=XWErRAtTzdCNsca7h-BjJ2Bwdxg@mail.gmail.com>
<c7bdff0f-2f6a-c6e6-8bc5-15859b376ab8@isi.edu>
<CALx6S35WZn69U2F=XRwd55foVfBQHW=+aRYyv5YL+tJiuqOSMQ@mail.gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <c3774eb3-d47b-716d-d547-3134d41d1b92@isi.edu>
Date: Fri, 10 Feb 2017 13:40:19 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CALx6S35WZn69U2F=XRwd55foVfBQHW=+aRYyv5YL+tJiuqOSMQ@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="------------21BB0C728C214E31DD33880B"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3-dt-encap/YleuyYVfzBQBl3Q6D2Xd8dfeZE8>
X-Mailman-Approved-At: Sun, 12 Feb 2017 08:30:24 -0800
Cc: Sam Aldrin <aldrin.ietf@gmail.com>, "nvo3@ietf.org" <nvo3@ietf.org>,
nvo3-chairs@ietf.org, nvo3-dt-encap@ietf.org
Subject: Re: [nvo3-dt-encap] [nvo3] Encap draft published by design team
X-BeenThere: nvo3-dt-encap@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Private mailing list for internal NVO3 Encapsulation Design Team
discussions <nvo3-dt-encap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3-dt-encap>,
<mailto:nvo3-dt-encap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nvo3-dt-encap/>
List-Post: <mailto:nvo3-dt-encap@ietf.org>
List-Help: <mailto:nvo3-dt-encap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3-dt-encap>,
<mailto:nvo3-dt-encap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 21:41:08 -0000
On 2/10/2017 1:23 PM, Tom Herbert wrote: >> - I disagree with MUST support a minimum of 64 bytes of options; making that >> requirement effectively limits everyone to using only 64. IMO, that number >> is both too small and sets the protocol up to have "dead wood" (i.e., larger >> option space is specified but can't be relied upon so might never gain >> traction). >> > Having both a minimum and a different maximum value is superfluous. > The minimum value is the maximum value in practice. Agreed - that was basically my point (though you put it more succinctly). Joe
- [nvo3-dt-encap] Encap draft published by design t… Sam Aldrin
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Tom Herbert
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Tom Herbert
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Tom Herbert
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Tom Herbert
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Tom Herbert
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Joe Touch
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Joe Touch
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Joe Touch
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Joe Touch
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Sami Boutros
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Tom Herbert
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Sami Boutros
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Tom Herbert
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Joe Touch
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Tom Herbert
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Joe Touch
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Tom Herbert
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Joe Touch
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Tom Herbert
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Joe Touch
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Tom Herbert
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Joe Touch
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Tom Herbert
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Joe Touch
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Tom Herbert
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Joe Touch
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Tom Herbert
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Joe Touch
- Re: [nvo3-dt-encap] [nvo3] Encap draft published … Greg Mirsky