Re: [nvo3] Mail regarding NVO3 data plane drafts

Erik Nordmark <nordmark@sonic.net> Wed, 20 July 2016 14:20 UTC

Return-Path: <nordmark@sonic.net>
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 A5C8312D7EE for <nvo3@ietfa.amsl.com>; Wed, 20 Jul 2016 07:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.887
X-Spam-Level:
X-Spam-Status: No, score=-3.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287] 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 MyOS_N71ERWv for <nvo3@ietfa.amsl.com>; Wed, 20 Jul 2016 07:20:35 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (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 59D2012D7C8 for <nvo3@ietf.org>; Wed, 20 Jul 2016 07:20:35 -0700 (PDT)
Received: from [31.133.180.15] (dhcp-b40f.meeting.ietf.org [31.133.180.15]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id u6KEKLTJ018430 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 20 Jul 2016 07:20:22 -0700
To: Xuxiaohu <xuxiaohu@huawei.com>, "Black, David" <david.black@emc.com>, "Manish Kumar (manishkr)" <manishkr@cisco.com>, NVO3 <nvo3@ietf.org>
References: <249BBA62-FB42-4B03-B4DB-8A15ADFDD190@cisco.com> <CE03DB3D7B45C245BCA0D243277949362F5E3F4E@MX307CL04.corp.emc.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D573FE0@NKGEML515-MBX.china.huawei.com>
From: Erik Nordmark <nordmark@sonic.net>
Message-ID: <00f68a45-2aa3-e6e8-1309-c8aa6b293ac2@sonic.net>
Date: Wed, 20 Jul 2016 07:20:20 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D573FE0@NKGEML515-MBX.china.huawei.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Sonic-CAuth: UmFuZG9tSVZ7aOe7bfJpfVvtJiMa8R0+woWXta9xJ283Hcq69zsE0yxYg7QkYitZ13BgyGzeyt4WFvgqBS44qjJqWF6OiZTU
X-Sonic-ID: C;POJjF4VO5hGLKpNwxPCmMQ== M;NsASGIVO5hGLKpNwxPCmMQ==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/KFf6kCg_2Xp0HHaolLy92UxZddE>
Subject: Re: [nvo3] Mail regarding NVO3 data plane drafts
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 20 Jul 2016 14:20:40 -0000

On 7/14/16 7:03 PM, Xuxiaohu wrote:
> IETF has published two informational RFCs dedicated for NVo3 data plane encapsulation, one is RFC7348 (i.e., VXLAN) and the other is RFC7637 (i.e., NVGRE). Both of them have been implemented and deployed. Of course, each has its own flaw. The former has no protocol type field (https://www.ietf.org/mail-archive/web/nvo3/current/msg01520.html) and the latter' ECMP capability is not good enough.

Xiaohu,

A minor nit is that it was the Independent Stream Editor at the RFC Editor who published these documents, not the IETF.
In most cases that doesn't make a difference.

Regards,
    Erik

>
> If the NVo3 WG still wants to publish some RFCs on NVo3 data plane encapsulation, it seems reasonable to build on the above two approaches and fix their flaws accordingly. VXLAN-GPE is designed to fix the flaw of VXLAN although whether or not to use a different port number than VXLAN's port number is still controversial. Personally, I prefer to the approach as defined in (https://tools.ietf.org/html/draft-yong-l3vpn-nvgre-vxlan-encap-03#page-3) since it seem much simpler than the current approach as defined in (https://tools.ietf.org/html/draft-quinn-vxlan-gpe-03#page-8). GRE-in-UDP is a very good choice to fix the flow of NVGRE.
>
> Best regards,
> Xiaohu
>
>> -----Original Message-----
>> From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Black, David
>> Sent: Friday, July 15, 2016 2:42 AM
>> To: Manish Kumar (manishkr); NVO3
>> Subject: Re: [nvo3] Mail regarding NVO3 data plane drafts
>>
>>> I believe GRE(+UDP) deserves a discussion as well.
>> FYI - over in TSVWG, this GRE/UDP draft is standards track and has completed
>> WG Last Call:
>> 	https://datatracker.ietf.org/doc/draft-ietf-tsvwg-gre-in-udp-encap/
>> Thanks, --David
>>
>>> -----Original Message-----
>>> From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Manish Kumar
>>> (manishkr)
>>> Sent: Thursday, July 14, 2016 12:54 PM
>>> To: Bocci, Matthew (Nokia - GB); NVO3
>>> Subject: Re: [nvo3] Mail regarding NVO3 data plane drafts
>>>
>>> Hi Matthew,
>>>
>>> I agree this is an important aspect that’s just lingering around.
>>> Although not being adopted and not a part of the WG, if there is a
>>> discussion on pros-cons/merits- demerits, I believe GRE(+UDP) deserves
>>> a discussion as well. For that matter, it may be worth having a broader
>> discussion!
>>> Thanks,
>>> Manish
>>>
>>>
>>>
>>>
>>>
>>> On 14/07/16 9:51 pm, "nvo3 on behalf of Bocci, Matthew (Nokia - GB)"
>>> <nvo3- bounces@ietf.org on behalf of matthew.bocci@nokia.com> wrote:
>>>
>>>> WG,
>>>>
>>>> The NVO3 working group has adopted three data plane encapsulations:
>>>> -          VXLAN-GPE,
>>>> -          Geneve,
>>>> -          GUE (although the draft is moving to the Intarea WG, we
>> anticipate that
>>> NVO3 will still reference this).
>>>> We have discussed this situation with Alia and we feel that there is
>>>> little benefit
>>> to the community in publishing all three as standards track RFCs.
>>>> We would note that the discussion on the drafts has been relatively
>>>> light since
>>> their adoption. There has not been serious discussion about their
>>> relative pros/cons (if any), or about the actual usefulness of their
>>> extensibility or differentiators.
>>>> This leaves two options:
>>>>
>>>> 1) Publish all of them as informational or experimental, potentially
>>>> moving one
>>> of them to standards track in the future based on
>> implementation/deployment.
>>>> 2) Pick one now based on technical and/or implementation/deployment
>> criteria.
>>>> We would therefore like to gain a sense of what the WG would like to
>>>> do with
>>> these drafts.
>>>> Please post your comments to the list. We also have a slot to on the
>>>> NVO3
>>> agenda in Berlin where we would like to continue this discussion.
>>>> Best regards,
>>>>
>>>>
>>>> Matthew and Sam
>>>>
>>>>
>>>> _______________________________________________
>>>> nvo3 mailing list
>>>> nvo3@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/nvo3
>>> _______________________________________________
>>> nvo3 mailing list
>>> nvo3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/nvo3
>> _______________________________________________
>> nvo3 mailing list
>> nvo3@ietf.org
>> https://www.ietf.org/mailman/listinfo/nvo3
> _______________________________________________
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3
>