Re: [auth48] AUTH48: RFC-to-be 9268 <draft-ietf-6man-mtu-option-15> for your review

Bob Hinden <bob.hinden@gmail.com> Wed, 03 August 2022 15:30 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: auth48archive@ietfa.amsl.com
Delivered-To: auth48archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9025CC14CF09; Wed, 3 Aug 2022 08:30:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_DNSWL_NONE=-0.0001, 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_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 KTKYeuw2YNP8; Wed, 3 Aug 2022 08:30:49 -0700 (PDT)
Received: from mail-oa1-x33.google.com (mail-oa1-x33.google.com [IPv6:2001:4860:4864:20::33]) (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 C1EE1C147920; Wed, 3 Aug 2022 08:30:49 -0700 (PDT)
Received: by mail-oa1-x33.google.com with SMTP id 586e51a60fabf-10d845dcf92so21110854fac.12; Wed, 03 Aug 2022 08:30:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:from:to:cc; bh=oOWpZ59OgtrL1nlICfNRhfmI5trO2DwmWbyd6YyS0k0=; b=E8tjnfWzjzrFtH7kbhi9j+1HujH0S7SzTqGtw2ZM2b0itiWVSSPGFg2wmyDA5Y6N27 zur8U0dqTxs+Hy8cbleiudEos90AaY/c1KfYDlYoWz7azVYV1t+74fxF8CV77qEld72z p/YTa2DX8RNaTzGy/6NQ+zx4vMJvj/5CurbkK208RjENEv036ikOaSEucVO84MaWxXUy 42kPkKVxWljBYMWZJJbIpM6krE/U0VlIcvVNtfgz2xk2h/zPUT/8fApfDVT8tsCizYqR YGkHXeAgCz6Iipb7jOWGphPTtosQ0wQTWf8Qo0YW3gKqTZ7SAQCKNQ64Rdr6Yqqb4EFq 3XEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:x-gm-message-state:from:to:cc; bh=oOWpZ59OgtrL1nlICfNRhfmI5trO2DwmWbyd6YyS0k0=; b=zyboarknEn7yF+Jm/TbZDE7Z1sEVo1crUUsvNnjdRIxNZ/++lf5940WEZBlKgXvnj/ DgKnIs4H0ZoSzJlfjjabSlQlhEBrSPLUUgWDEOesIt4P+wskf+AAQq9K2EsArDFf4PhY Zyt1Y0itf5muvHqBgRRwGMQm9Yv44T9aCJ1r72mTlST4p4T1QwmJuWpR2LIPbjkbc7Ha 6Xtd3ot1/ssCDlm6fN8eZV7BC/kWvS1VerOAMoJIsTiCd+qj4Y64Gbh8uSW6FG0PvOzx 54O+v4J5F/xH76hSQv2aRdeWGIXV667qWxX6oLCLOht418ZNq4YUY6HVIhugal4azI1q fXZA==
X-Gm-Message-State: ACgBeo0W2L6S8q7HZHZdkin3czoZoIYUch+gp4FKbyh9RsY6qeMheu18 vAHVrAaYYTFOjQouREjbHjE=
X-Google-Smtp-Source: AA6agR41oaHCKBLJSckJX0OAt71yoPsZKP9ILefNPlFHFULy8g/X0r6VSNlopxTg/b5Muc23LkKjbg==
X-Received: by 2002:a05:6870:e997:b0:10c:66f1:8bbb with SMTP id r23-20020a056870e99700b0010c66f18bbbmr2111641oao.243.1659540648097; Wed, 03 Aug 2022 08:30:48 -0700 (PDT)
Received: from smtpclient.apple ([2600:1700:4383:c05f:2d28:dc5a:1c8e:7e7b]) by smtp.gmail.com with ESMTPSA id v16-20020a056870709000b0010d4aba3339sm4436608oae.42.2022.08.03.08.30.46 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Aug 2022 08:30:47 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_02683170-BB36-4C43-B8E8-F0BD30299F08"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <323E6ED2-7FC1-4EFF-915F-9BC79CFA69FA@amsl.com>
Date: Wed, 03 Aug 2022 08:30:45 -0700
Cc: Bob Hinden <bob.hinden@gmail.com>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, RFC Editor <rfc-editor@rfc-editor.org>, 6man-ads@ietf.org, 6man Chairs <6man-chairs@ietf.org>, Ole Trøan <otroan@employees.org>, Erik Kline <ek.ietf@gmail.com>, auth48archive@rfc-editor.org, iana@iana.org
Message-Id: <28189A1B-5042-41D1-B22E-290F99402F7F@gmail.com>
References: <20220714145855.6FBE76AA26@rfcpa.amsl.com> <5B5B0365-137E-4709-ACC5-2252C499FF71@gmail.com> <bb4df2aa-f475-fda4-88a5-ba6e99879ade@erg.abdn.ac.uk> <D302102C-963C-4591-8ACD-155E7824B4A4@amsl.com> <4BA3B35B-3A7D-4EFE-A7A8-581BCF0CFFAC@gmail.com> <323E6ED2-7FC1-4EFF-915F-9BC79CFA69FA@amsl.com>
To: Sandy Ginoza <sginoza@amsl.com>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/uQlJxref-vaIHbVqGqb2zH1UdMw>
Subject: Re: [auth48] AUTH48: RFC-to-be 9268 <draft-ietf-6man-mtu-option-15> for your review
X-BeenThere: auth48archive@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Archiving AUTH48 exchanges between the RFC Production Center, the authors, and other related parties" <auth48archive.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/auth48archive/>
List-Post: <mailto:auth48archive@rfc-editor.org>
List-Help: <mailto:auth48archive-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2022 15:30:53 -0000

Sandy,

Thanks very much, a few comments below.

Bob


> On Aug 2, 2022, at 4:15 PM, Sandy Ginoza <sginoza@amsl.com> wrote:
> 
> Hi Bob, IANA,
> 
> Just jumping in on this one — I’ve added IANA to this thread so they can chime in if we’ve misunderstood or in case anything has changed.
> 
>> On Aug 2, 2022, at 2:26 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
>> 
>>>>> 
>>>>> I note that the reference to the IANA HBH option registry was changed from:
>>>>> 
>>>>> [IANA-HBH] "Destination Options and Hop-by-Hop Options",
>>>>> 
>>>>> <https://www.iana.org/assignments/ipv6-parameters/
>>>>>            ipv6-parameters.xhtml#ipv6-parameters-2>
>>>>> .
>>>>> 
>>>>> to:
>>>>> 
>>>>> [IANA-HBH] IANA, "Destination Options and Hop-by-Hop Options",
>>>>> 
>>>>> <https://www.iana.org/assignments/ipv6-parameters/>
>>>>> .
>>>>> 
>>>>> The original reference goes directly the specific Destination Options and Hop-by-Hop Options registry, where the new one goes to the general IPv6 parameter registry.   Why the change?
>>> 
>>> We updated the reference per input from IANA. IANA recommended that RFCs point to the top-most registry since they are considered stable; they prefer that the direct URLs to specific registries on a page not be used.
>> 
>> I wasn’t aware of that.   The result is a little confusing.  The text in the reference says:
>> 
>> "Destination Options and Hop-by-Hop Options”
>> 
>> but it goes to a page titled:
>> 
>> Internet Protocol Version 6 (IPv6) Parameters
> 
> I see what you’re saying.  My hope is that a reader will search for the registry title on the main page.  Would it be more clear to add some text where the registry is cited?  For example:
> 
> IANA has registered an IPv6 Hop-by-Hop Option type in the "Destination Options and Hop-by-Hop Options" registry within the "Internet Protocol Version 6 (IPv6) Parameters” registry [IANA-HBH].)

Yes, that would help.

> 
> 
> 
>> Would something like the following be better?
>> 
>> IANA, "Destination Options and Hop-by-Hop Options”, Internet Protocol Version 6 (IPv6) Parameters, <https://www.iana.org/ assignments/ipv6-parameters/>.
> 
> The current format is based on IANA’s input.  We suggested a similar format in the past, but there was a preference not to include the top-level registry/group title as the page may/will be formatted differently in the future (e.g., the registry/group title may change or no longer appear).
> 
> Previously proposed:
> [NAME]  IANA, "Top-Level Registry Name: Registry Name", <URL to top-level registry>.
> 
> 
>> Seems to me that for IANA registries that are stable, like this one, it’s not too burdensome for IANA to have a stable link to each sub-registry.
> 
> I believe this is in the works.

That would be helpful.

> 
> Thanks,
> Sandy
> 
> 
> 
> 
>