Re: [nvo3] Second Working Group Last call for draft-ietf-nvo3-encap

Gyan Mishra <hayabusagsm@gmail.com> Sat, 03 July 2021 19:45 UTC

Return-Path: <hayabusagsm@gmail.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 292EA3A2205; Sat, 3 Jul 2021 12:45:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.087
X-Spam-Level:
X-Spam-Status: No, score=-1.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 xmZw-CYmiJOX; Sat, 3 Jul 2021 12:44:58 -0700 (PDT)
Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) (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 4D69A3A2202; Sat, 3 Jul 2021 12:44:58 -0700 (PDT)
Received: by mail-pl1-x636.google.com with SMTP id b5so7832667plg.2; Sat, 03 Jul 2021 12:44:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Q8bNy2xE2vLGkol9j3RPs5ckm8BJ3kFAPgxBnq7+6pQ=; b=FC3A3b67hk7XZjk2/bafo/ZyHnoOBLTG+FpR3fnKdoje6u4BOc5IGBkj+zxYooyOoi L7J87cyxT6+tWWuCzxugeBE6gOtlW56HhoOJquganF4Km3FzqbcFiPWf3tdEAapd5fVK +oPkOkCjEIE3iEeDeDIo4cK/XN8rGL/nd7BnoM3K02xgkkSJGdyUzwJjyohE8SW9ytdA 8FBM5NHGpuAyMhEk+uE9ihh298FHzS8YLmPXe+neaWeKp60atiNX+iJD5eJ4YHl1X5u7 Mwk3w3rCIDxsY1cCjD1ak6yZJh+R7xOjrNcHIgjjw37eq8E8KpAmDabIe7B3HqOyA1pY JZDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Q8bNy2xE2vLGkol9j3RPs5ckm8BJ3kFAPgxBnq7+6pQ=; b=kZ+7TTLFl1Hh5OzZw2O1je0hF6MU3uW3X0yd8NJpV7UBqM8zuLxx/jGw4bPy/VwpG3 93JOc+redEPKzpkK43EfPxnMiLWes0e2jyzKwc/jyKpbKCqRfzlUd75C9mK3PkeDOzfs dXWldWS/nYthlLx7Z8AvYaYcwxHHRSNxHeokQXNQ8+5S8rpQ+/cp9MvKKy2LuYrF6YBs sxJkzWr9ABKxIBDxh0mfKgyTEq1qWvhaQjs0qvcFEysSsLH7UVpATIh05sefFQyFzyzG ytim1eTS6ElGjVa9RSK2XMHg9jziU0KbVS/pjX9MgLgz2eP87cPLtwsdDkuqP/M3yv1A 7fZQ==
X-Gm-Message-State: AOAM532F8Uyu5MzBLm9nH12HprxWgAgumN8rx9ElVnxh6aVZwtiEBgvz OxZ2tg2Htto/5UO5sMEEW61brVt8we1uvxWRjLQ=
X-Google-Smtp-Source: ABdhPJxOLw6a4cvCudBCNFK59kx+vUQbFKZbIE8G/CfCjgKaEIBZplEvvvu5pvhN1OHLd2dwe4Pk4Hf94QiqLJlNT3o=
X-Received: by 2002:a17:90a:fa92:: with SMTP id cu18mr6156841pjb.215.1625341497366; Sat, 03 Jul 2021 12:44:57 -0700 (PDT)
MIME-Version: 1.0
References: <5CCE673A-C79E-4A17-9DBA-2BA7A7B16D9B@nokia.com> <202107031151312350405@zte.com.cn> <CABNhwV0D6haijGS0y_4A+0QCJD0ZFNOxs0AOeKZ0APQBDEyKvw@mail.gmail.com> <CAF4+nEHd1Ze=+Pqc2Cnourw-KYZdgAkf9Og_Ss9yN3Pi41sF+Q@mail.gmail.com>
In-Reply-To: <CAF4+nEHd1Ze=+Pqc2Cnourw-KYZdgAkf9Og_Ss9yN3Pi41sF+Q@mail.gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Sat, 03 Jul 2021 15:44:46 -0400
Message-ID: <CABNhwV3H6d8GQ_nJdT_xH3Pu2cE=AtV6rOX9PjorQ=RwfEnocA@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Cc: "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>, NVO3 <nvo3@ietf.org>, draft-ietf-nvo3-encap@ietf.org, xiao.min2@zte.com.cn
Content-Type: multipart/alternative; boundary="00000000000096ddf105c63d4ea9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/WUheySvlCw1oTrWgYf76pWRzhJY>
Subject: Re: [nvo3] Second Working Group Last call for draft-ietf-nvo3-encap
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: Sat, 03 Jul 2021 19:45:03 -0000

Thank you!

Agreed, questions for DT.

Gyan

On Sat, Jul 3, 2021 at 2:44 PM Donald Eastlake <d3e3e3@gmail.com> wrote:

> Hi Gyan,
>
> On Sat, Jul 3, 2021 at 11:25 AM Gyan Mishra <hayabusagsm@gmail.com> wrote:
> >
> > Dear Authors
> >
> > I have read the latest draft and support publication.
> >
> > This is a very important document for operators to help provide guidance
> on NVO3 directional encapsulation and what will be the eventual end all be
> all encapsulation which from the draft it sounds like GENEVE is out in
> front.
> >
> > Few comments.
> >
> > The draft mentions GUE but does not expand what GUE stands for.
>
> Sure, we can add the expansion of GUE.
>
> The questions below seem like they would be better answered by a
> member of the Design Team of which I am not.
>
> Thanks,
> Donald
> =============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  2386 Panoramic Circle, Apopka, FL 32703 USA
>  d3e3e3@gmail.com
>
> > As RFC 7348 VXLAN is the most widely of all deployments worldwide I am
> wondering why it is not listed in the NVO3 encapsulation types.
> >
> > Also RFC 7637 NVGRE as well has implementations by vendors and
> deployments by operators I wonder why that was excluded in the list of NVO3
> encapsulations examined.
> >
> > The goal of NVO3 charter is to have a single encapsulation type and
> GENEVE based on section 7 is the starting point for a proposed standard for
> NVO3 encapsulation.
> >
> > So let’s say NVO3 ends up being the chosen end all be all standard
> encapsulation type, what would vendors as well as operators do with
> existing VXLAN and NVGRE deployments and would those deployments eventually
> require software or I am guessing hardware upgrades to support GENEVE.
> >
> > It seems that out of the three encapsulation types in the draft, GENEVE
> was chosen as it builds on existing VXLAN framework with some added
> extensibility so not too difficult for operators migration in theory from
> VXLAN to GENEVE.
> >
> > Kind Regards
> >
> > Gyan
> >
> >
> > On Fri, Jul 2, 2021 at 11:51 PM <xiao.min2@zte.com.cn> wrote:
> >>
> >> Hi Matthew and Sam,
> >>
> >> I've read the latest version of this draft.
> >> I think this document is valuable and ready for publication.
> >>
> >> Best Regards,
> >> Xiao Min
> >>
> >> ------------------原始邮件------------------
> >> 发件人:Bocci,Matthew(Nokia-GB)
> >> 收件人:NVO3;
> >> 抄送人:draft-ietf-nvo3-encap@ietf.org;
> >> 日 期 :2021年07月01日 23:09
> >> 主 题 :[nvo3] Second Working Group Last call for draft-ietf-nvo3-encap
> >> _______________________________________________
> >> nvo3 mailing list
> >> nvo3@ietf.org
> >> https://www.ietf.org/mailman/listinfo/nvo3
> >>
> >> This email begins a two-week working group last call for
> draft-ietf-nvo3-encap-06.
> >> Please review the draft and post any comments to the NVO3 working group
> list. If you have read the latest version of the draft but have no comments
> and believe it is ready for publication  as an informational RFC, please
> also indicate so to the WG email list.
> >> We are also polling for knowledge of any undisclosed IPR that applies
> to this document, to ensure that IPR has been disclosed in compliance with
> IETF IPR rules (see RFCs 3979, 4879, 3669  and 5378 for more details).
> >> If you are listed as an Author or a Contributor of this document,
> please respond to this email and indicate whether or not you are aware of
> any relevant undisclosed IPR. The Document  won't progress without answers
> from all the Authors and Contributors.
> >> Currently there are no IPR disclosures against this document.
> >> If you are not listed as an Author or a Contributor, then please
> explicitly respond only if you are aware of any IPR that has not yet been
> disclosed in conformance with IETF rules.
> >> As a reminder, we are pursuing publication of this document in order to
> permanently document the experience of one working group in choosing
> between multiple proposed standards track  encapsulation drafts. The idea
> was that this would provide helpful guidance to others in the community
> going forward.
> >> This poll will run until Thursday 15th July 2021.
> >> Regards
> >> Matthew and Sam_______________________________________________
> >> nvo3 mailing list
> >> nvo3@ietf.org
> >> https://www.ietf.org/mailman/listinfo/nvo3
> >
> > --
> >
> >
> > Gyan Mishra
> >
> > Network Solutions Architect
> >
> > Email gyan.s.mishra@verizon.com
> >
> > M 301 502-1347
> >
> >
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*