IETF Logo Mail Archive

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

Dan Wing <dwing@vmware.com> Sat, 15 July 2017 02:36 UTC

Return-Path: <dwing@vmware.com>
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 068F7131687 for <nvo3@ietfa.amsl.com>; Fri, 14 Jul 2017 19:36:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.701
X-Spam-Level:
X-Spam-Status: No, score=-4.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=onevmw.onmicrosoft.com
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 SGqHlq2IUNsI for <nvo3@ietfa.amsl.com>; Fri, 14 Jul 2017 19:36:22 -0700 (PDT)
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01on0053.outbound.protection.outlook.com [104.47.32.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6800B12F299 for <nvo3@ietf.org>; Fri, 14 Jul 2017 19:36:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=onevmw.onmicrosoft.com; s=selector1-vmware-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=dI2SR1nSSiizISRadmXN/5R/x2WqpsLxq3TBWJoqJTg=; b=T89Srz78BJkMZuwYXoDrr8+7FLT4PGnuxu1JzOgNkNlL9il124gGG35tkA3n54Bne/mVpb4Skjvw2yRdAKY22TTLS6fACUlRvvbCNFgcH/4HVUFgXmUTRtVvLFggbTEwDepzdJ6KVyUfy8ujipg+gPy84p5sl5TdpDG5lxJIpq0=
Received: from SN2PR05MB2656.namprd05.prod.outlook.com (10.166.212.139) by SN2PR05MB2702.namprd05.prod.outlook.com (10.166.213.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1282.4; Sat, 15 Jul 2017 02:36:20 +0000
Received: from SN2PR05MB2656.namprd05.prod.outlook.com ([10.166.212.139]) by SN2PR05MB2656.namprd05.prod.outlook.com ([10.166.212.139]) with mapi id 15.01.1282.005; Sat, 15 Jul 2017 02:36:20 +0000
From: Dan Wing <dwing@vmware.com>
To: "Dale R. Worley" <worley@ariadne.com>
CC: Joe Touch <touch@isi.edu>, "nvo3@ietf.org" <nvo3@ietf.org>
Thread-Topic: [nvo3] Carrying entropy, was: draft-ietf-nvo3-encap-00 should add considerations of traversing NAPT
Thread-Index: AQHS/Q+prTJRwokRn0iJcebArUQZi6JULCqA
Date: Sat, 15 Jul 2017 02:36:20 +0000
Message-ID: <5AABFF10-9580-49CA-873A-26A51DCB6B4E@vmware.com>
References: <87y3rq1mb6.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87y3rq1mb6.fsf@hobgoblin.ariadne.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ariadne.com; dkim=none (message not signed) header.d=none;ariadne.com; dmarc=none action=none header.from=vmware.com;
x-originating-ip: [2001:470:1f05:1df9:7983:40ac:86d9:e9e3]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN2PR05MB2702; 20:KPa3aME/Ben1kO401VJR7SMKLvYOS/ToV19WegVsgMFP7jVe5OgQz+JN6k96yN1tCgn5vDrGyEGieShupYl3azHuAgVYB2zOKMRLSEZkLGZlaKnqDNWASmZOEd/sH3IKFZBo9pSYJlw6dzdfdnFwfLQ9JPLUDGHoln0hPJk0deo=
x-ms-office365-filtering-correlation-id: 1823f454-282c-4b1d-8339-08d4cb2a471e
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(2017052603031)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:SN2PR05MB2702;
x-ms-traffictypediagnostic: SN2PR05MB2702:
x-exchange-antispam-report-test: UriScan:(236129657087228)(247924648384137);
x-microsoft-antispam-prvs: <SN2PR05MB27026A88D60FD89548C04CFEDCA20@SN2PR05MB2702.namprd05.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(2017060910075)(5005006)(100000703101)(100105400095)(10201501046)(93006095)(93001095)(3002001)(6041248)(20161123555025)(20161123558100)(20161123562025)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:SN2PR05MB2702; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:SN2PR05MB2702;
x-forefront-prvs: 0369E8196C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39410400002)(39400400002)(39850400002)(39450400003)(39840400002)(24454002)(377454003)(76176999)(5660300001)(6486002)(50986999)(102836003)(54356999)(6916009)(2950100002)(3660700001)(53936002)(6436002)(6506006)(6116002)(229853002)(82746002)(54906002)(6512007)(99286003)(77096006)(36756003)(2900100001)(8676002)(230783001)(3280700002)(8936002)(305945005)(25786009)(4326008)(38730400002)(81166006)(83716003)(7736002)(189998001)(33656002)(478600001)(14454004)(53546010)(110136004)(6246003)(86362001); DIR:OUT; SFP:1101; SCL:1; SRVR:SN2PR05MB2702; H:SN2PR05MB2656.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8B4A568F09EC8044A2CFF3C358A769BA@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: vmware.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Jul 2017 02:36:20.5837 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: b39138ca-3cee-4b4a-a4d6-cd83d9dd62f0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN2PR05MB2702
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/Jbmp3S_Xt3MGtk_45uSBX88iJtE>
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: Sat, 15 Jul 2017 02:36:24 -0000

> On Jul 14, 2017, at 7:11 PM, Dale R. Worley <worley@ariadne.com> wrote:
> 
> Joe Touch <touch@isi.edu> writes:
>> 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.
> 
> Well, the definition of "flow information" is not in the positive
> sense -- if the value is the same between two packets, their order must
> be maintained -- but rather in the negative sense -- if the value is
> *different* between two packets, their order *need not* be maintained.
> That causes devices to behave conservatively, in that they are allowed
> to reorder packets only if they have specific knowledge that the packets
> are "in different flows".  From that point of view, if a device knows
> that a certain field is an NVI, then it can treat that field as flow
> information.

Using Geneve VNI doesn't take us towards that goal, though.  On a simple network, there is only one VNI (one virtual network), and if we used solely VNI for underlay ECMP, all tunneled packets would go over the same ECMP path.  We want each tunneled TCP flow to take one path, and ideally the next tunneled TCP flow taking another ECMP path.

-d

v2.23.0 | Report a Bug | By Email