IETF Logo Mail Archive

Re: [nvo3] Carrying entropy, was: draft-ietf-nvo3-encap-00 should add considerations of traversing NAPT

Joe Touch <touch@isi.edu> Fri, 14 July 2017 03:41 UTC

Return-Path: <touch@isi.edu>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C5E5127201 for <nvo3@ietfa.amsl.com>; Thu, 13 Jul 2017 20:41:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 9fiaBv4XbvZQ for <nvo3@ietfa.amsl.com>; Thu, 13 Jul 2017 20:41:24 -0700 (PDT)
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 16DE3120454 for <nvo3@ietf.org>; Thu, 13 Jul 2017 20:41:23 -0700 (PDT)
Received: from [10.20.50.184] (ip-64-134-100-23.public.wayport.net [64.134.100.23]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v6E3erPo022182 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 13 Jul 2017 20:40:55 -0700 (PDT)
To: "Dale R. Worley" <worley@ariadne.com>, nvo3@ietf.org
References: <874luf3ipb.fsf@hobgoblin.ariadne.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <7aa5c707-8047-be7e-b9b6-b9c10a942bb3@isi.edu>
Date: Thu, 13 Jul 2017 20:40:51 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <874luf3ipb.fsf@hobgoblin.ariadne.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
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/MPdTWpE5k8dNCEyETemMAAPgk7g>
Subject: Re: [nvo3] Carrying entropy, was: draft-ietf-nvo3-encap-00 should add considerations of traversing NAPT
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jul 2017 03:41:25 -0000


On 7/13/2017 6:34 PM, Dale R. Worley wrote:
> Given that we're talking about encapsulations, I see that Geneve has a
> "Virtual Network Identifier" field that can be treated as part of the
> entropy.  If it isn't needed to identifiy a virtual network, it can
> loaded with entropy from the encapsulated packet.  In any case, packets
> with different NVI values can be freely reordered.
>
> And there is an 8-bit reserved field which could be defined to be
> entropy.
>
> These fields are at a fixed location relative to the containing headers,
> so they're easy to find.
Yes, but I sincerely doubt router vendors will peek into GENEVE headers.
IMO, they'll either use IPv6 flow IDs or look for transport flow
context. Even a NVI isn't really flow information, so might not have any
bearing on whether a set of packets (with the same NVI) should maintain
their relative order.

Joe

v2.23.0 | Report a Bug | By Email