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

David Moses <mosesster@gmail.com> Sat, 23 July 2022 08:14 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 8FCB8C14F730; Sat, 23 Jul 2022 01:14:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 tfXjbT6shJX0; Sat, 23 Jul 2022 01:14:24 -0700 (PDT)
Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (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 DFF05C14F729; Sat, 23 Jul 2022 01:14:23 -0700 (PDT)
Received: by mail-ej1-x631.google.com with SMTP id oy13so12178550ejb.1; Sat, 23 Jul 2022 01:14:23 -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=oEZ8lRnsLcBhoflJDevxr3xpoQ/GGbKESaYy7Uxx+oo=; b=Q2PGPvhoLjBfmeEK1OJvUymYz7chiIp/QCozdtiPHWd7B55WJiQEvr9Fljn7C3+uD+ R+G0WxD1OnwG3Tzkc0wmX6EDQ2xoJG43EEF8nAJsH/VrwnLlkpXYtjfWjeSjWpjA+XmJ WoHc+RDev5V0e7LRAROqcH/DoFR8y+/UfKZon0rvw+84ONaCLkyqyFclx+LsKIRP72jn +iK0d2VOEZ5tSrv6vXSo5o5tfi1q31CHf7/M4Npu/NY6hHemLcOWdu6yLZoQaE51rQGq Ai3nv0KbfRlj4YFbLkKcw5yuVuyvu3+s8POvI3JH0IQcKCV+5XAVf00p8DLOohoDvH4S E5Lg==
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=oEZ8lRnsLcBhoflJDevxr3xpoQ/GGbKESaYy7Uxx+oo=; b=oFV4R9LgNC94M+2nwJTeUVQ93zSBmWPbuAWAulS25wta+4ipISSPrybBvMuAgS6ZIJ 6LZx4qivOcMe8SwKAkJjphAgCq6SRcrE9PFQSdsRx5LbM512By8Wymd/jhQbie8CaF8C vVyRIZaxyScA9thSGtu5H99B7X+ef5+Me835S3Apl67KuYaA0YfkowRPvuhaC+TDqPaN qFlDzud6aQDrVdslcftaHRf3IpXRP2sGWFFay4fIVb5iqqyqITsDVKQCpci2nmgZWNox 6+d/rAGzDjpaaOy2GifqRiQEOrJ2/+0L55SLXvoWYzHtYhUq1HKLCzHrpXY+AzfsYvvm m7eg==
X-Gm-Message-State: AJIora/U1kVw+CJhFpbpvWufFFwmbLIZvKYiaSF3GTcFlb7O1sPMRIOu C58nMmfqDd+SuCxL/IXAv86Ekc6zG+Hmr3p4hNA=
X-Google-Smtp-Source: AGRyM1tkwYgGW7QHOj6L0UgwkeHCT3B6mm0NxUskFsG9oS1lX+s/0N4h3NAogeZxPkli9WDMtSzGDuQyt6VfaJPA1/U=
X-Received: by 2002:a17:907:2e01:b0:72b:7497:778 with SMTP id ig1-20020a1709072e0100b0072b74970778mr2668050ejc.530.1658564061962; Sat, 23 Jul 2022 01:14:21 -0700 (PDT)
MIME-Version: 1.0
References: <VI1PR0701MB6991AF12239635F6D72F87D4EBD49@VI1PR0701MB6991.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR0701MB6991AF12239635F6D72F87D4EBD49@VI1PR0701MB6991.eurprd07.prod.outlook.com>
From: David Moses <mosesster@gmail.com>
Date: Sat, 23 Jul 2022 11:13:44 +0300
Message-ID: <CA+qYZY1=Aby=Rsxcr1shMXXOCXuAf-JbHAVEHaT3EgewPegTjA@mail.gmail.com>
To: "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>
Cc: NVO3 <nvo3@ietf.org>, "nvo3-chairs@ietf.org" <nvo3-chairs@ietf.org>, "ilango.s.ganga@intel.com" <ilango.s.ganga@intel.com>, "prankajg@microsoft.com" <prankajg@microsoft.com>, Rajeev Manur <rajeev.manur@broadcom.com>, "talmi@marvell.com" <talmi@marvell.com>, "nordmark@sonic.net" <nordmark@sonic.net>, "Michael Smith (michsmit)" <michsmit@cisco.com>, Sam Aldrin <aldrin.ietf@gmail.com>, Ignas Bagdonas <ibagdona.ietf@gmail.com>, "draft-ietf-nvo3-encap@ietf.org" <draft-ietf-nvo3-encap@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c0272005e4748906"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/0blnWBlHUsKspguw0ZWLyrdnW2Q>
Subject: Re: [nvo3] WG Last Call for draft-ietf-nvo3-encap-08
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.39
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, 23 Jul 2022 08:14:24 -0000

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

On Mon, May 23, 2022 at 12:57 PM 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
>
>
>