Re: [dhcwg] Adoption Call for draft-dhcwg-dhc-rfc8415bis-00- Respond by Nov 18, 2022

Timothy Winters <tim@qacafe.com> Fri, 02 December 2022 21:27 UTC

Return-Path: <tim@qacafe.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82801C14CE27 for <dhcwg@ietfa.amsl.com>; Fri, 2 Dec 2022 13:27:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 (1024-bit key) header.d=qacafe.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 uxOGtaPiytIF for <dhcwg@ietfa.amsl.com>; Fri, 2 Dec 2022 13:27:16 -0800 (PST)
Received: from mail-oi1-x236.google.com (mail-oi1-x236.google.com [IPv6:2607:f8b0:4864:20::236]) (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 EA3CFC14CE20 for <dhcwg@ietf.org>; Fri, 2 Dec 2022 13:27:16 -0800 (PST)
Received: by mail-oi1-x236.google.com with SMTP id n186so6594071oih.7 for <dhcwg@ietf.org>; Fri, 02 Dec 2022 13:27:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qacafe.com; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=iYWg0MJ+UHd7ctDw/wjXQqw20qsySqZlBocpWVo7IEg=; b=DIyMNpwn3h7OXlXfLyYGDXlryVdWYzOs6aKggFNLVDhzw5bBHHURWhYjG3AycsD+Ob x7VlyE48Usf+p8/EWxanezTCIctUKGJKEscj68A9WUaJyQmLtWpSAwY6ZjuXIafrUA1A jdG3wn/jziAWescdSbeRO0N62CGWgDwygZbR4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=iYWg0MJ+UHd7ctDw/wjXQqw20qsySqZlBocpWVo7IEg=; b=Hl2GUBKVuZM7E2QGbTkTW3Vw7m9aBlqN6xdb2FpYKpB8J7ELUyYACOgtv0b2eq4aFv mNoB5XmEN9IfeTP/9jEf9YUT4PkEdOgV9U5vXoY9K29JgxXMUbDDYENuXJm5IQL+HGck b7OtKd0TmAdlmyfIUx+W/klKrZ78fG79BO0iRxagFbo1tUmxZqyYq8c8uzV+DxhwDzjR 9C0Nx2VeOXLBBB5cmUsxOshhIBagAxt9q/J8lac1uqcrmpls8ViFh7aIedBeT9nN5EY0 qGCQZXcQjQLx3hl56uD6YftA241baIefqPHmmF+/EiqF6T/CssALca19Rqk7f3CuDl1C l0zA==
X-Gm-Message-State: ANoB5pmcE4Ej9zrObil62DcnqraVDLF9/cug/5+IMnlBUL/B1yf1SWwB QckjbVS1ECr3Ltm4vGeMVoLTmOFc0SUmUr8fUgoLxg==
X-Google-Smtp-Source: AA0mqf7eRhKMwqHbocX1i53A+FoMOdYMbDUfqTDiba0vTCxJYwUJfuvdR1BGXWS4S0Dyh6/CzK6O/rzaaYIOARvvFrA=
X-Received: by 2002:a05:6808:13c5:b0:35a:1a0e:d46f with SMTP id d5-20020a05680813c500b0035a1a0ed46fmr25997457oiw.104.1670016436062; Fri, 02 Dec 2022 13:27:16 -0800 (PST)
MIME-Version: 1.0
References: <0B4512A7-1006-4DB2-8B46-F92B6F13E0F8@gmail.com> <83EBDC3D-471A-490F-A829-DACECB0C4569@gmail.com>
In-Reply-To: <83EBDC3D-471A-490F-A829-DACECB0C4569@gmail.com>
From: Timothy Winters <tim@qacafe.com>
Date: Fri, 02 Dec 2022 16:27:05 -0500
Message-ID: <CAJgLMKu06_8uBYrnX99TaxFDAL3oAompVS9OFKiN+=AqYLG37w@mail.gmail.com>
To: Bernie Volz <bevolz@gmail.com>
Cc: dhcwg <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007100d505eedf00dd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/Hb9hDVLqJqlOmxw2ny27AfaOu8Y>
Subject: Re: [dhcwg] Adoption Call for draft-dhcwg-dhc-rfc8415bis-00- Respond by Nov 18, 2022
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Dynamic Host Configuration <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Dec 2022 21:27:20 -0000

Hi Bernie,

I was thinking about this today as well, all the support for adoption came
from the authors of the document.  Let's extend the adoption call until
12/14.

 In the meeting room at IETF 114 there seemed to be general interest in
this work, but we need confirmation on the list.

Can others from the working group chime on the mailing list if they support
this for an adoption call?

~Tim

On Fri, Dec 2, 2022 at 4:13 PM Bernie Volz <bevolz@gmail.com> wrote:

> What’s the status of this adoption call?
>
> My guess is that it kind of failed as we had noone except myself comment
> to the list? But perhaps I missed some?
>
> I do think we may need to consider adding an “Implementation Status”
> section as recommended by https://authors.ietf.org/recommended-content (this
> would not end up in RFC).
>
> - Bernie Volz
>
> On Nov 2, 2022, at 4:28 PM, Bernie Volz <bevolz@gmail.com> wrote:
>
> Hi:
>
> Not sure how much it counts as I did many of the edits from RFC8415 for
> this bis draft, but I strongly support adoption by the WG of this document.
>
> It would be great to get input from others on the changes as well as the
> few areas I had pointed out when announcing publication if the draft to the
> WG:
>
> A few areas to consider during your review:
> - Should we reduce some of the background material, such as sections 1.1 and 1.2 and/or 3.
> - Should we remove all text related to even checking for unicast transmissions and even deprecate the UseMulticast status code. I think the only case that can end up with unicast at a 8415bis server would be if the server had been sending Server-Unicast option and is then upgraded as existing (pre8415bis clients) may then unicast … but likely if the upgraded server just accepted the message, there would not really be any harm. A 8415bis client that always multicasts should never run into problems (and thus get the UseMulticast status). The 8415bis server would never need to check if unicast.
> - The Acknowledgements section has XXX, as (your) names will be inserted here as work on the document continues.
>
> - Bernie Volz
>
> On Oct 20, 2022, at 4:50 AM, Timothy Winters <tim@qacafe.com> wrote:
>
> 
> Hello:
>
> We would like initiating a WG call for adoption on
> draft-dhcwg-dhc-rfc8415bis-00
> <https://datatracker.ietf.org/doc/html/draft-dhcwg-dhc-rfc8415bis>.  This
> document is an updated version of the DHCPv6 base specification with the
> intention of advancing to Internet standard.
>
> This starts the call for adoption of this document. Please respond by
> November 18, 2022.
>
> Thanks in advance for your consideration of whether the WG should or
> should not adopt this document as a work item.
>
> Thanks,
> Tim and Bernie
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
>