Re: [nvo3] Poll on progressing draft-ietf-nvo3-encap with missing IPR declaration

Donald Eastlake <d3e3e3@gmail.com> Fri, 08 July 2022 18:35 UTC

Return-Path: <d3e3e3@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 70AD3C14CF16; Fri, 8 Jul 2022 11:35:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.857
X-Spam-Level:
X-Spam-Status: No, score=-1.857 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=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] 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 jMO1UvFsw7lR; Fri, 8 Jul 2022 11:35:51 -0700 (PDT)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (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 0FDFEC159486; Fri, 8 Jul 2022 11:35:51 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id a11so26880464ljb.5; Fri, 08 Jul 2022 11:35:50 -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:content-transfer-encoding; bh=CP2dl5GvY/Dlx9x4O8RPhwgG3l/D3wg9WQmoTNpaS8A=; b=BbZHoumcNyCKFb5LeTnlS7R+86e8uGNweDHYGUD/ZkVe+T8q35rWLbgmKzDS+VW5/5 kopeGCZA7HsIOJHDzE5LPtsGdtFoHs3FJji9vV9AoJn7Iu9EbOGFa29LFCAASekJi61e bdmXXZpzglpFzhd6P+38Y475EXjrg4wzf6lf0Uck5NmlZb2KWTsjj0zbME7seC+x+puX Qc70MKt2P5Hr3jQxTwf4aokP4HMOhQwbWpHQJwyCLv6/VXUKKl2dkTCXhQIebJOu7Ho0 7YhMTYGbfIXwbMH0rOfVACjKZtvdHcXedHqR0c15yqxex86MN+ZLWzHRlhosUlYY4XV/ vBcA==
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:content-transfer-encoding; bh=CP2dl5GvY/Dlx9x4O8RPhwgG3l/D3wg9WQmoTNpaS8A=; b=4YqcgNP8K+s3JZuB8knJQlOz2t7KQUKEoUS/BrrvHPompXtvuSFVMAYv/ynUnGUTpW z9ZfYzJZqTwf79KxOXB2GQImxB8Q1A2V6dFp/JkUJHFi+I/jZhJoSQW0kaDpKH5LgCpA YJTlvNHIPiYJImm6Jo9zbxopkVXhA++j9cNb4c63Jg+xmAvoRMrgD0XnxQo8gD4tSq9K d4EoNTmG9z753/Yl1Di1Z+Hbtp2y6s6OdTfD+Jeiqnnap6WKBfiCOQQrrF7dtVqEfmSn GyJ7whRotYBFzmkd3m03q2M58HCPITciizrhGAIuDdgjRgAYctT17hqzBgI/YGq5oby0 sRcg==
X-Gm-Message-State: AJIora/X0eNHcS7iJXjnBCmVwXoq0IU9TmG5zsCssOHGSf5WxmdEmYiq R96ClpCcGDool+Wk/x/9bG3hWLiQDLnioNJrPqw=
X-Google-Smtp-Source: AGRyM1stBAUSyqzLjd9UUYq6PuvNtXvZZsUWx4hResToP/WLpEgDGIkv3OPVutyln0lSON0bniJAKO0Law7tj4XVQSs=
X-Received: by 2002:a2e:83c6:0:b0:25a:d2c4:76c8 with SMTP id s6-20020a2e83c6000000b0025ad2c476c8mr2691693ljh.336.1657305349123; Fri, 08 Jul 2022 11:35:49 -0700 (PDT)
MIME-Version: 1.0
References: <VI1PR0701MB69913D5721DACB7976DA2837EB829@VI1PR0701MB6991.eurprd07.prod.outlook.com>
In-Reply-To: <VI1PR0701MB69913D5721DACB7976DA2837EB829@VI1PR0701MB6991.eurprd07.prod.outlook.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 08 Jul 2022 14:35:38 -0400
Message-ID: <CAF4+nEG1-VXy4dn4PW5vnRWFVKr_DbsLQXOjneOOmSQcGi_+6g@mail.gmail.com>
To: "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>
Cc: NVO3 <nvo3@ietf.org>, "draft-ietf-nvo3-encap@ietf.org" <draft-ietf-nvo3-encap@ietf.org>, Andrew Alston - IETF <andrew-ietf@liquid.tech>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/l7IbS1sIDTsnvD3WnwfV0AUBM_I>
Subject: Re: [nvo3] Poll on progressing draft-ietf-nvo3-encap with missing IPR declaration
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: Fri, 08 Jul 2022 18:35:51 -0000

I would like to see this document progress and, given its general
nature (mostly a statement of requirements and listing of previously
documented characteristics of alternatives), I think there is really
no chance that it has any new IPR in it.

I support option 1. I have personally sent dozens of emails over a
period of months to the non-responsive person. I received precisely
one response over a month ago in which they indicated a general lack
of interest in the document but did say they would look at it. Despite
multiple pings, I have heard nothing since. If they continue to be
non-responsive and listed as a contributor, special action will have
to be taken to get through AUTH48 also.

However, if the WG will not go with option 1, we could go with option
2. I would support that if it is the WG's choice.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com

On Fri, Jul 8, 2022 at 8:51 AM Bocci, Matthew (Nokia - GB)
<matthew.bocci@nokia.com> wrote:
>
> NVo3 WG,
>
>
>
> The chairs believe there is consensus to publish draft-ietf-nvo3-encap as an informational RFC. However, we are missing an IPR declaration from one of the co-authors listed in the Contributors section.
>
>
>
> Despite repeated attempts to contact them over several weeks through multiple channels, we have not received an IPR declaration. It is incumbent upon us to ask every author and contributor to declare whether they are aware of any IPR that may be applicable to the draft. However, since we have not been unable to contact this one co-author, we would like the working group’s input on how to proceed by responding to this poll.
>
>
>
> These are the potential options:
>
>
>
> Remove the individual’s name from the list of contributors, moving it to the acknowledgements section, and then request publication of the draft.
> Proceed with publication of the draft regardless, with no changes to the contributors list.
> Do not publish the draft until we receive a response form the individual (which may be never).
>
>
>
> Please respond to this poll by Friday 22nd July stating whether you support option (1), option (2) or option (3).
>
>
>
> Best regards,
>
>
>
> Matthew and Sam.
>
>
>
>