Re: [dhcwg] Very late comments on WGLC for draft-ietf-dhc-rfc8415bis
Timothy Winters <tim@qacafe.com> Tue, 06 February 2024 13:46 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 CCEC0C14F602 for <dhcwg@ietfa.amsl.com>; Tue, 6 Feb 2024 05:46:33 -0800 (PST)
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, HTML_MESSAGE=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 (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 wRmSxx4YlWuI for <dhcwg@ietfa.amsl.com>; Tue, 6 Feb 2024 05:46:29 -0800 (PST)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (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 8E539C14F6EF for <dhcwg@ietf.org>; Tue, 6 Feb 2024 05:46:29 -0800 (PST)
Received: by mail-pf1-x42f.google.com with SMTP id d2e1a72fcca58-6de2f8d6fb9so4216551b3a.1 for <dhcwg@ietf.org>; Tue, 06 Feb 2024 05:46:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qacafe.com; s=google; t=1707227188; x=1707831988; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=vsApfPLt139kLOYcJvYK0lcn0fYlXf9oc7iIHbgVrl4=; b=BTf+KQD2U1vq8kmgUD/vCLzD5LjwFjXhgWt8oMXEWK1k9Qt1RTLAqBVdc5yLeq3e94 wkWvruFjvyYfw1HpLzqCLADngP+ecXaBpd1cv8aI9Q3Avmq4elUzQQpGN8NvnJZ8/Mee JnTIdZ/itHk1yooQLH5HYAGsV/F9cemGjIthU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707227188; x=1707831988; 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=vsApfPLt139kLOYcJvYK0lcn0fYlXf9oc7iIHbgVrl4=; b=tlBHViDtxm8RI86n+vpzgnyN0ZL0HqcK4EH5gyLYn/wKKq6/Va1ZTvV+cFG6crizoX hqM822L2NeDU91t/g2B/Nbiossw5NEdyVPg1bMeJ3pX7Pue/d+tCgQHIOmKw+ETx5+8o 1Ii0FIQwbwWt5G7LBDif/ZXHmaTT63czBBRZUIIEbVPhWViuc047tj4PdRL/1GtZLFKL XDfvMm4IxpH8/rI4uhOoU5gKdgq45jl4ugXUJu0Zr4trBpK3B7MK6aP2RqygnuwHWcIX jKXjQpeqx+4tKxxMwKY++KVYBf79jPTm0XDf1aq+FlV407EfHpEe9pqt6LZr08j6XkBF I1dg==
X-Gm-Message-State: AOJu0YxPYgvSI+cdaTRhUqY8OeUZ4mU86KEN+O2DZGNfrnkCv6nsem8R A1SmTmGK9Oa06wlyV/zZCxxlnLNgHc5UkxjpbGyK8nY+D+OmrfShZbOD6l7yx42WtmZjGXPWLNM fhoGHLAt05GXHvWjQDbEvXwtXT9RoqeV/+ONXsA==
X-Google-Smtp-Source: AGHT+IHeAY1GqW3mbKeZzoNyf6u7xjly7UUeGSskHLOG63+UcJqmbYqLY9XAIHqUPMSIWtEUzJjt7xegXRtd4mrVVHY=
X-Received: by 2002:a05:6a20:5497:b0:19e:9c82:3df5 with SMTP id i23-20020a056a20549700b0019e9c823df5mr728682pzk.23.1707227188534; Tue, 06 Feb 2024 05:46:28 -0800 (PST)
MIME-Version: 1.0
References: <9F07C23B-C813-47FE-876A-D35CFA531976@gmail.com> <e89579a4-b7da-4f65-bb94-70f528038d4c@gmail.com>
In-Reply-To: <e89579a4-b7da-4f65-bb94-70f528038d4c@gmail.com>
From: Timothy Winters <tim@qacafe.com>
Date: Tue, 06 Feb 2024 08:46:17 -0500
Message-ID: <CAJgLMKunSp5-51grZ0R6SAHhXx5Dt1o92p9Ay0NnzKR1yNafsw@mail.gmail.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Cc: dhcwg <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001fb1e00610b6ce3b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/ITQvDw4JF7pD_3ZWjmzyG8ZqpkM>
Subject: Re: [dhcwg] Very late comments on WGLC for draft-ietf-dhc-rfc8415bis
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, 06 Feb 2024 13:46:33 -0000
Hi Tomek, Responded in line. On Fri, Feb 2, 2024 at 9:40 AM Tomek Mrugalski <tomasz.mrugalski@gmail.com> wrote: > Hi, > > I'm not sure what's the status of the WGLC is. The deadline has long > passed, but I don't think any wrap up was posted. And the -04 was not > published yet. So perhaps it's not too late? > While we concluded WGLC isn't not too late to make modifications. > > Reviewing 130+ pages long document is not a trivial task. I have > compared 8415 text with that latest version of the draft and found no > specific issues with the draft. > > I do have a small number of editorial suggestions. > > 1. SECTION 1: Introduction > > Remove "temporary addresses" from the list of resources DHCPv6 can > allocate. > Agree. > > 2. SECTION 4.2: Terminology > > The section defines IA mentions IA_NA, IA_TA, and IA_PD. And there's > this text "New IA types may be defined in the future.". IA_LL was > defined in RFC8947. I propose to change the text to: > > "One other IA type was defined (see RFC8947) and more may be defined > in the future.". > Agree, this is good idea. > > 3. Should we add references to other DHCPv6 RFCs? > The text mentions bulk leasequery (Section 19.4), but RFC 5460 is not > referenced. Perhaps we could add a paragraph somewhere (or maybe new > section 1.3?) that mentions DHCPv6 mechanisms: leasequery, bulk > leasequery, active leasequery, IA_LL and failover. On one hand, it would > make the already huge document a tiny bit bigger. On another, we already > have lots of references, so I suspect there will be engineers out there > starting their DHCP journey with this text. > My suggestion is maybe add these to Section 6, 6.6 as it is an operational model? I agree having more information about leasequery is a good idea. > > And a follow-up question to 3: If we decide to add them, should we also > mention draft-ietf-dhc-addr-notification? Some people feel it might > become a very popular mechanism. But perhaps referencing a draft is not > something we want to do? > I think it's too early to reference that document. > > Any thoughts on this? > > With or without those minor edits, I think this document is ready to > move forward. > > Tomek > > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www.ietf.org/mailman/listinfo/dhcwg >
- [dhcwg] WGLC for draft-ietf-dhc-rfc8415bis, ends … Bernie Volz
- [dhcwg] Very late comments on WGLC for draft-ietf… Tomek Mrugalski
- Re: [dhcwg] Very late comments on WGLC for draft-… Timothy Winters
- Re: [dhcwg] Very late comments on WGLC for draft-… Bernie Volz
- Re: [dhcwg] Very late comments on WGLC for draft-… Bernie Volz