IETF Logo Mail Archive

Re: [nvo3] WG Last Call for draft-ietf-nvo3-encap-08

David Moses <mosesster@gmail.com> Sun, 29 May 2022 18:54 UTC

Return-Path: <mosesster@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 BB9E0C159480; Sun, 29 May 2022 11:54:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.088
X-Spam-Level:
X-Spam-Status: No, score=-7.088 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RZ3sawA8cqaA; Sun, 29 May 2022 11:54:22 -0700 (PDT)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE043C14EB1C; Sun, 29 May 2022 11:54:21 -0700 (PDT)
Received: by mail-ed1-x532.google.com with SMTP id fd25so11049770edb.3; Sun, 29 May 2022 11:54:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OsQio4QDpKjjcWuC3iegltTwEtU4KN/y9RJVEcCfS3U=; b=kgJtThGDJKZ9JTrt+EUsuQHQvtmraJ57oIXpwuD2zP+fxvkdK1nmKWtswUwFsSIRtu h6yJDb96+an+nF/6kA99ZYw+P+q13/QAoKf+ltOWTtZDRn71v+GPoRaDR9zY2ad4NOVE SGBSCpGvf+oRhXT/CaE3Bqd9awB0NO8zthOAf9n1uBBGuVaoe+jZ80Er0BP6Gtr2tAWf U+vfKvk36MN5Ye7wckwgSHlC2gJ3xluVYwuqTGIhn5Xg+GoyE/TGT2lUekcFcmVEKGyo F1eQlMX+tI3XBIUNVIZRv3UW/9Tx9OuZpq7OjQ5QkPbQEl8CU51PaCm0tw4EP5YqmOMW 5cGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OsQio4QDpKjjcWuC3iegltTwEtU4KN/y9RJVEcCfS3U=; b=QWhzz1dHIF5KIkd7L75KJ2OeCwEDu4g7lEQzRhtYhqwNU7aIbF0FP3aAr/5flMbPXf OjMKrxfxE+ITpyossQf5my0n2PVHMjKWh0u3VlYDlXaT91nYoSald9N1gJQPJicY72fX OCamH8uwisfI6djA62aOp6G9StvyEn0MFL9Vns95pRqJYPYVynerihXeugqeP7PH9gkK ShBciVnNTkt7uoUUkkIs+gefTUfeSFSwT/L87+Ag1Fg610BQBh2vDd3QDdTRRDr2tlmP XkurWNqYhZjfXzRD85eeFjnzFg0MVrGKUQM0GTlTE1gsCcHDfLK0fYzBhcepw3XAg8lA w4jw==
X-Gm-Message-State: AOAM532HkNogHZTZv/8cgQwv2eKC+f49YeIXhcjAt/6YQPWO/lRvq4Qw TMNM1giRT7pglVfmTIo+zjEb/vtDZ1SsZXdgHNc=
X-Google-Smtp-Source: ABdhPJwWoHJ8EbQWv7AIApED9ewgVuUo7a7/KIoROXPjJUaivwVi47ANfRZi5cxojgKxg+imv3nki+07fvWmgSSPIUU=
X-Received: by 2002:a05:6402:2712:b0:42b:476b:6c71 with SMTP id y18-20020a056402271200b0042b476b6c71mr42864525edd.413.1653850460003; Sun, 29 May 2022 11:54:20 -0700 (PDT)
MIME-Version: 1.0
References: <VI1PR0701MB6991AF12239635F6D72F87D4EBD49@VI1PR0701MB6991.eurprd07.prod.outlook.com> <CABNhwV0+-v6NFxpgvFNZ4BLmWxFXbGO7cKd+QSP9mrp=jAkdhA@mail.gmail.com>
In-Reply-To: <CABNhwV0+-v6NFxpgvFNZ4BLmWxFXbGO7cKd+QSP9mrp=jAkdhA@mail.gmail.com>
From: David Moses <mosesster@gmail.com>
Date: Sun, 29 May 2022 21:54:08 +0300
Message-ID: <CA+qYZY0V9rhXchptMxwSy2YZGNBHJ42GrirTzBOMLV0ueGhyyQ@mail.gmail.com>
To: Gyan Mishra <hayabusagsm@gmail.com>
Cc: "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>, Ignas Bagdonas <ibagdona.ietf@gmail.com>, "Michael Smith (michsmit)" <michsmit@cisco.com>, NVO3 <nvo3@ietf.org>, Rajeev Manur <rajeev.manur@broadcom.com>, Sam Aldrin <aldrin.ietf@gmail.com>, "draft-ietf-nvo3-encap@ietf.org" <draft-ietf-nvo3-encap@ietf.org>, "ilango.s.ganga@intel.com" <ilango.s.ganga@intel.com>, "nordmark@sonic.net" <nordmark@sonic.net>, "nvo3-chairs@ietf.org" <nvo3-chairs@ietf.org>, "prankajg@microsoft.com" <prankajg@microsoft.com>, "talmi@marvell.com" <talmi@marvell.com>
Content-Type: multipart/alternative; boundary="0000000000002e206f05e02b1132"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/wWpjTND7DvFuY0MvkBAakbwdJzA>
Subject: Re: [nvo3] WG Last Call for draft-ietf-nvo3-encap-08
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.34
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: Sun, 29 May 2022 18:54:25 -0000

Hi *,
I support the publication of the draft.
I am not aware of any related IPRs.
Thx
David



On Sun, May 29, 2022 at 5:24 AM Gyan Mishra <hayabusagsm@gmail.com> wrote:

>
> I support publication of this draft.
>
> Thanks
>
> Gyan
>
> On Mon, May 23, 2022 at 5:58 AM Bocci, Matthew (Nokia - GB) <
> matthew.bocci@nokia.com> wrote:
>
>> This email begins a two-week working group last call for
>> draft-ietf-nvo3-encap-08 (draft-ietf-nvo3-encap-08 - Network
>> Virtualization Overlays (NVO3) Encapsulation Considerations
>> <https://datatracker.ietf.org/doc/draft-ietf-nvo3-encap/>).
>>
>>
>>
>> We are running a new WG last call as there were a few updates made during
>> the RTG DIR review discussions. We are also missing a few IPR declarations
>> from contributors, which need to be made against the WG LC version of the
>> document. I have copied the contributors directly.
>>
>>
>>
>> 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 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 Monday 6th June 2022.
>>
>>
>>
>> Regards
>>
>>
>>
>> Matthew and Sam
>>
>>
>> _______________________________________________
>> nvo3 mailing list
>> nvo3@ietf.org
>> https://www.ietf.org/mailman/listinfo/nvo3
>>
> --
>
> <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*
>
>

v2.23.0 | Report a Bug | By Email