Re: [dhcwg] Adoption Call for draft-dhcwg-dhc-rfc8415bis-00- Respond by Nov 18, 2022
Bernie Volz <bevolz@gmail.com> Fri, 02 December 2022 21:13 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 DADB4C14CE26 for <dhcwg@ietfa.amsl.com>; Fri, 2 Dec 2022 13:13:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 GQs5CmznjdJd for <dhcwg@ietfa.amsl.com>; Fri, 2 Dec 2022 13:13:33 -0800 (PST)
Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (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 B014FC14CE20 for <dhcwg@ietf.org>; Fri, 2 Dec 2022 13:13:33 -0800 (PST)
Received: by mail-qt1-x836.google.com with SMTP id r19so6960337qtx.6 for <dhcwg@ietf.org>; Fri, 02 Dec 2022 13:13:33 -0800 (PST)
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=cwt7QDQUSAnsl4OSRy0BC09e65bfVE2x1TnUalNbsXQ=; b=UWlSDj7TbXUIDtaz3ERGTIFJcbxkFNo9DuAp2Zq47moiqaN1zqeMmnsbuj89eOyNmP GvD+YjSrmGGmRJduScWm9f/MmtNTGv+bImbsunfzBV4SETmX90gUONa0DWuvF138u1sh 75tJZrbqb3yNx8o49eop1sDKibFc1gfXuA0VTy7++S965BOq3yr0CRW+yYB0F/J1ZFgR o3ijlROySbAQdR8gj7HFs07Ith0q3+qMWT6ddeOI344QaMYuu/MlDuDI4+2o1spqlANb BQCxqTQMGFO0mLTUondq/Iwnpm++2liuUhjf0Vs472R/ELE/TlV/Z8mVdyQDUDnhSgdw MlzA==
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=cwt7QDQUSAnsl4OSRy0BC09e65bfVE2x1TnUalNbsXQ=; b=uAmr9sAN0v8A4pHB+sUylNuENrfXlmvKd+ikpgm52565JaVh1gJYjc6lVX5+hl4CcI +anQ/LbZmoMUcgcDs4udiDvk9QSA5y+T0FGYEChvPwm9bKWApyDbBNM2ZLHK5TwMFbod F1d2KFKj0p1plkYAYdHbqmXpoz779hDtSBtfWX0BgTPdB+IH5+ZJxS9bI2vCb7ZIub8j 6RSEpAZzGtFtv0kqhmjMnoxwRlAuGD1ML6mbLjIMakBpECmGg4WLJxMcoeC85OIXSTlH +Y4ciB380iYC1HZzf7ciCfnWVlhVfusGkK8CVNBMetuDPTXbbF3XGPUentq2I3vhKbbG hE+A==
X-Gm-Message-State: ANoB5pkiUUB0xerbpI7PPeblYXt2n/h9ZIefxIMboG1pM+DBJVP8p5yw as2bjvWsm3cpA9BnuF0HqA==
X-Google-Smtp-Source: AA0mqf5AwhuJ1zOBi23J4hOaWIEoeJ8OgsWIq4JSOCffXocppo3kawQ52C4x9Tz3OORKr9+VJRsIqA==
X-Received: by 2002:a05:622a:1f97:b0:3a6:39c4:dc6 with SMTP id cb23-20020a05622a1f9700b003a639c40dc6mr59664063qtb.515.1670015612451; Fri, 02 Dec 2022 13:13:32 -0800 (PST)
Received: from smtpclient.apple (d-24-233-121-124.nh.cpe.atlanticbb.net. [24.233.121.124]) by smtp.gmail.com with ESMTPSA id f21-20020a05620a409500b006b953a7929csm6583373qko.73.2022.12.02.13.13.31 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 02 Dec 2022 13:13:32 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-B85E07E7-E83D-4E96-B465-D78B8712A44B"
Content-Transfer-Encoding: 7bit
From: Bernie Volz <bevolz@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Fri, 02 Dec 2022 16:13:31 -0500
Message-Id: <83EBDC3D-471A-490F-A829-DACECB0C4569@gmail.com>
References: <0B4512A7-1006-4DB2-8B46-F92B6F13E0F8@gmail.com>
Cc: dhcwg <dhcwg@ietf.org>
In-Reply-To: <0B4512A7-1006-4DB2-8B46-F92B6F13E0F8@gmail.com>
To: Timothy Winters <tim@qacafe.com>
X-Mailer: iPad Mail (19G82)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/heFqtcECyyTUrat8PO5jTYw4p2w>
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:13:35 -0000
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. 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
- [dhcwg] Adoption Call for draft-dhcwg-dhc-rfc8415… Timothy Winters
- Re: [dhcwg] Adoption Call for draft-dhcwg-dhc-rfc… Bernie Volz
- Re: [dhcwg] Adoption Call for draft-dhcwg-dhc-rfc… Sheng JIANG
- Re: [dhcwg] Adoption Call for draft-dhcwg-dhc-rfc… Bernie Volz
- Re: [dhcwg] Adoption Call for draft-dhcwg-dhc-rfc… Timothy Winters
- Re: [dhcwg] Adoption Call for draft-dhcwg-dhc-rfc… Robert Nagy
- Re: [dhcwg] Adoption Call for draft-dhcwg-dhc-rfc… Tomek Mrugalski
- Re: [dhcwg] Adoption Call for draft-dhcwg-dhc-rfc… Ted Lemon
- Re: [dhcwg] Adoption Call for draft-dhcwg-dhc-rfc… Ian Farrer
- Re: [dhcwg] Adoption Call for draft-dhcwg-dhc-rfc… rob@deepdivenetworklng.com
- Re: [dhcwg] Adoption Call for draft-dhcwg-dhc-rfc… Timothy Winters