[nvo3] Comments on the draft-ietf-nvo3-vxlan-gpe-07

"Liubing (Remy)" <remy.liubing@huawei.com> Fri, 19 April 2019 07:56 UTC

Return-Path: <remy.liubing@huawei.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 AECFB120113 for <nvo3@ietfa.amsl.com>; Fri, 19 Apr 2019 00:56:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 uorunUp6O5WU for <nvo3@ietfa.amsl.com>; Fri, 19 Apr 2019 00:56:22 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 115471200F7 for <nvo3@ietf.org>; Fri, 19 Apr 2019 00:56:22 -0700 (PDT)
Received: from lhreml708-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 428FBB78EA7948DB1473 for <nvo3@ietf.org>; Fri, 19 Apr 2019 08:56:20 +0100 (IST)
Received: from DGGEMM404-HUB.china.huawei.com (10.3.20.212) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 19 Apr 2019 08:56:20 +0100
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.162]) by DGGEMM404-HUB.china.huawei.com ([10.3.20.212]) with mapi id 14.03.0415.000; Fri, 19 Apr 2019 15:56:16 +0800
From: "Liubing (Remy)" <remy.liubing@huawei.com>
To: "nvo3@ietf.org" <nvo3@ietf.org>
Thread-Topic: Comments on the draft-ietf-nvo3-vxlan-gpe-07
Thread-Index: AdT2gkL96H38bA2+SUm2OGn0fvSgvQ==
Date: Fri, 19 Apr 2019 07:56:16 +0000
Message-ID: <BB09947B5326FE42BA3918FA28765C2EF85176@DGGEMM506-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.180.83]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/7_1zALT7arhs58SffTgDDFR36JE>
Subject: [nvo3] Comments on the draft-ietf-nvo3-vxlan-gpe-07
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Apr 2019 07:56:24 -0000

Hello authors,

Thank you for bring up this draft again. I've read this new version and I think the design of the shim header is a big improvement.

If I understand it correctly, the logic of the shim header is similar  to the non-critical TLV in GENEVE. But I think some clarification is required.

Quote from the draft: "Implementations that are not aware of a given shim header MUST ignore the header and proceed to parse the next protocol." The definition of "implementations" is not clear at all. The implementation can be a transit node or the NVE and the related operations should be differentiated. In my opinion, the NVE should not or even must not ignore any shim header, while the transit node can do this.

Another point may need to be clarified: does "...are not aware of a given shim header..." mean that the device have to at least know that there is a shim header and how long it is so that it can skip the header to parse the next protocol? If the device can't recognize any shim header, i.e. it does not know the meaning of "0x80 to 0xFF", the packet must be dropped in this case?

Best regards,
Remy