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

Bernie Volz <bevolz@gmail.com> Wed, 02 November 2022 20:28 UTC

Return-Path: <bevolz@gmail.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 9A362C152567 for <dhcwg@ietfa.amsl.com>; Wed, 2 Nov 2022 13:28:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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, MIME_QP_LONG_LINE=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 zyNlcZ3z7H4k for <dhcwg@ietfa.amsl.com>; Wed, 2 Nov 2022 13:28:08 -0700 (PDT)
Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (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 04544C1524DE for <dhcwg@ietf.org>; Wed, 2 Nov 2022 13:28:07 -0700 (PDT)
Received: by mail-qk1-x734.google.com with SMTP id z1so6713242qkl.9 for <dhcwg@ietf.org>; Wed, 02 Nov 2022 13:28:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=5v8NXmnTsyZ60+ovFSSrmZC1ngz/aarVBWEG/QMFqjs=; b=POeTTk5bdEV1HO0t9CVvZL4OqiELh0Y+YA1MkczYVpthXWaa3p5P3xa6CGoX42HTfZ xqyZlCRZ7kE2QSC1MeggPPMo/eR1gE2WR4zS6wtNTr1MnOCPXoPwVhFcdE5Nvz1qsjHB F7aMpW9KgsQAwMnA5JEsiDORiKrwFVuzHd5Y6s9ijSeYis2P0ry+jiJznlMvaIN5X0qm ARNnkA7JJMmiR4otfVdDEzCU6r5Bd1D0ljVUf1wCNsek19KPdG+qh8wuKKeG9Csv+etF 1h8HlofQQyX5Y/WDkrgZA/mY4eF4yHhqpDhmCCPDheevLK6GX25EZNIyzBDjx0qctBCf P10w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=5v8NXmnTsyZ60+ovFSSrmZC1ngz/aarVBWEG/QMFqjs=; b=uEJIeiOoGNiwW4tmw0rSf8hJVxRjDy1Yr8xNGDK6YCXATJzkKJ3hniMn++9FIH4cPY s1uIbEDMxwL6SqL7tTDwzmjUL1Ot4OI567M31qKd0j75jvZNnNcj5B1z5zSHPZ5gxtXl ufY9pcnlGjpcRHIppllc8pUZpijuFKJZImWisEjsaTQ5FqGOjWt6k0LFsiKH0/ST0tmB nCVG8uopozqt+CnLWFvI3jDXIcJ/5mEmPrI+p97rfTddZ47yvQDGBsbWYS6IFPRNCY6S sQ0bj//UMvw0uLv+lyGKhdPf2Sf1wWY0X15VyykOKbsK8VLeys5ANk3tDkIA6qVj0Ww+ 20jA==
X-Gm-Message-State: ACrzQf1L8jBHdXFcqLgceieWrGtjqsL6ygctQCECjVgv0Y6H/PG30a/K LO19mR38DP6IPXRG/iE8ytrkLbyW6w==
X-Google-Smtp-Source: AMsMyM6+mCveklN75w0QZTyXZOo86bX12bBtLXkELnNNqfEfa7U09lW7Zo0FBwwIZYH5TrB7R7KR6g==
X-Received: by 2002:a05:620a:140d:b0:6f9:c38b:4d7 with SMTP id d13-20020a05620a140d00b006f9c38b04d7mr19502062qkj.140.1667420886550; Wed, 02 Nov 2022 13:28:06 -0700 (PDT)
Received: from smtpclient.apple (d-24-233-121-124.nh.cpe.atlanticbb.net. [24.233.121.124]) by smtp.gmail.com with ESMTPSA id g19-20020a05620a40d300b006eea4b5abcesm9336652qko.89.2022.11.02.13.28.05 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 02 Nov 2022 13:28:06 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-093F2899-13CC-4368-A37D-29B1E0A1B604"
Content-Transfer-Encoding: 7bit
From: Bernie Volz <bevolz@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Wed, 02 Nov 2022 16:28:05 -0400
Message-Id: <0B4512A7-1006-4DB2-8B46-F92B6F13E0F8@gmail.com>
References: <CAJgLMKtXL1oXyzEoVcGdY19TDxPKcuiU6o0A7yt7h0njD=9d5Q@mail.gmail.com>
Cc: dhcwg <dhcwg@ietf.org>
In-Reply-To: <CAJgLMKtXL1oXyzEoVcGdY19TDxPKcuiU6o0A7yt7h0njD=9d5Q@mail.gmail.com>
To: Timothy Winters <tim@qacafe.com>
X-Mailer: iPad Mail (19G82)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/RuHA2tygq-NEzH-ne9n-jc_nrJo>
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: Wed, 02 Nov 2022 20:28:08 -0000

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.  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