Re: [dhcwg] New Version Notification for draft-dhcwg-dhc-rfc8415bis-00.txt

Bernie Volz <bevolz@gmail.com> Tue, 11 October 2022 20:03 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 DE45DC14F736 for <dhcwg@ietfa.amsl.com>; Tue, 11 Oct 2022 13:03:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, 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 YzO16UgaJ7LZ for <dhcwg@ietfa.amsl.com>; Tue, 11 Oct 2022 13:02:58 -0700 (PDT)
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (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 39143C14F6E7 for <dhcwg@ietf.org>; Tue, 11 Oct 2022 13:02:58 -0700 (PDT)
Received: by mail-qk1-x732.google.com with SMTP id z30so9221749qkz.13 for <dhcwg@ietf.org>; Tue, 11 Oct 2022 13:02:58 -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=SlA0wr7F55H7WPFgDI1YxnyaZaNpFgQsy4YvNnkmjDo=; b=gxKrXDv8AFJ243UVmhVZ4axI+DrWZM6FO1NCrMloB0pR1ud9k7oHalW7QQS+GEKNi7 EH6FHH5RyPtqgBBdqLWrRw4qCdvRChMRo0gF9vJ08bRtEPcTHWlMy0fTHfqO9zMm+tbJ unsCaoQjG+NA90cdJ/Ni74wTDlND0A6FtFK0WRfvbYLBDIX2uZHOha9kryhsc3plnRjU D/DgHHdQxv6BHrE64quZDDv596lmsE5B66Em95Tgc5t44KRK93GfttlxUhkOi4oCOLd+ kKxW2xGJtRRvKq6BaQ5w2QTImwJfvMJPWkZivItvB0VoZCfT2XlWIZUvAJ+IamTY+apz wfmg==
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=SlA0wr7F55H7WPFgDI1YxnyaZaNpFgQsy4YvNnkmjDo=; b=h2iUHnI9Vb6FPHXAGRWpP5uA/JyEk5TGlBKfOsdVAlHtkULoFlrBxNrxuhapZjFqPw 9nAeGiY/q+WSj7uV621qJ8EOrNmttWXkjmx3l/qvZo+SyHzGmoW/vkz/ZdagrUuQBffz 47NbBR4sMXNZ9GbrhGuA+9Ul0qaehMaOc2yVidraKG8JcbzdHQimx7YgCtNnPqOVfBlo fi7dT1ymdEFDyYLG2p3HVre6MwH3+VLpsSnGhyydwztELTcyKXHC4dFqgRF9mXd7L3xn M4GRAF849JtgqucerNn1uKnnz3ceo9Gu/LGF17/edt6ObUYaWTNuSighJ/FdCeCSw37F VbOw==
X-Gm-Message-State: ACrzQf0R5L7YW/IDer7cMG4VRIE2bQ3O9wJJUPWfG8lNqXYjdsOhxHKO h6zITjN1czfEqjnZ8VBa+mNUrtq3ag==
X-Google-Smtp-Source: AMsMyM72Hkyjmkobw0A6eNrUVFrTAcXpZECBcTTlnElArSSqT+YeLHosXAvAUr9SCND3D1Haw0VlxQ==
X-Received: by 2002:a05:620a:2441:b0:6ce:6064:d421 with SMTP id h1-20020a05620a244100b006ce6064d421mr18021713qkn.618.1665518576886; Tue, 11 Oct 2022 13:02:56 -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 n20-20020a05620a295400b006ee8d44175esm1350742qkp.78.2022.10.11.13.02.55 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 11 Oct 2022 13:02:56 -0700 (PDT)
Content-Type: multipart/mixed; boundary="Apple-Mail-609C5C60-13AE-48D4-A6EC-62A45266959F"
Content-Transfer-Encoding: 7bit
From: Bernie Volz <bevolz@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Tue, 11 Oct 2022 16:02:55 -0400
Message-Id: <BA9AD81B-24EA-49A1-8BEA-6AC08AED0660@gmail.com>
References: <9800.1665515402@localhost>
Cc: dhcwg <dhcwg@ietf.org>
In-Reply-To: <9800.1665515402@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: iPad Mail (19G82)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/rukcHZpdlTEpZBFzYjs7RBb4YzQ>
Subject: Re: [dhcwg] New Version Notification for draft-dhcwg-dhc-rfc8415bis-00.txt
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: Tue, 11 Oct 2022 20:03:01 -0000

FYI: I don’t know why xml2rfc introduced these changes, as we used the XML file from RFC editor. Most are bullet (* vs -) and spacing differences in lists.

Maybe it has something to do with I-D vs RFC generation?

Anyway, those are fairly quick and easy to ignore.

- Bernie Volz

> On Oct 11, 2022, at 3:10 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> I used:
>  https://author-tools.ietf.org/diff?doc_1=rfc8415&doc_2=draft-dhcwg-dhc-rfc8415bis-00
> 
> 90% of the changes are, alas, gratuitous format changes.
> 
> Bernie asks:
>> 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.
> 
> which corresponds to text:
> 
>      Once the client has determined the address of a server, it may, under
>      some circumstances, send messages directly to the server using
>      unicast.
> 
> And I think this is significant, and I'd like to understand why we should
> consider this change at Internet Standard step.  Does it simplify something
> or solve some problem?
> 
> I guess maybe:
> 
>       Use of unicast may avoid delays due to the relaying of messages by
>       relay agents, as well as avoid overhead on servers due to the
>       delivery of client messages to multiple servers.  However, requiring
>       the client to relay all DHCP messages through a relay agent enables
>       the inclusion of relay agent options in all messages sent by the
>       client.  **The server should enable the use of unicast only when relay
>       agent options will not be used**
> 
> is the point.
> 
> (My server implementation never cared, as it was for a PPPoE DSLAM, and there
> were only two nodes on the PPP link)
> 
> 
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>           Sandelman Software Works Inc, Ottawa and Worldwide
> 
> 
> 
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg