Re: [Cellar] normative references

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 26 September 2022 18:51 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: cellar@ietfa.amsl.com
Delivered-To: cellar@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D97FC14CF1F for <cellar@ietfa.amsl.com>; Mon, 26 Sep 2022 11:51:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 EJ3k3Dnbl6lj for <cellar@ietfa.amsl.com>; Mon, 26 Sep 2022 11:51:54 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 540FEC14F72D for <cellar@ietf.org>; Mon, 26 Sep 2022 11:51:54 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [89.246.252.107]) by relay.sandelman.ca (Postfix) with ESMTPS id BB8911F489; Mon, 26 Sep 2022 18:51:52 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id EDDEC1A074B; Mon, 26 Sep 2022 20:51:51 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Moritz Bunkus <mo=40bunkus.online@dmarc.ietf.org>, cellar@ietf.org
In-reply-to: <87a66m2de4.fsf@bunkus.online>
References: <153671.1664216229@dooku> <154091.1664216436@dooku> <87a66m2de4.fsf@bunkus.online>
Comments: In-reply-to Moritz Bunkus <mo=40bunkus.online@dmarc.ietf.org> message dated "Mon, 26 Sep 2022 20:30:15 +0200."
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 27.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Mon, 26 Sep 2022 20:51:51 +0200
Message-ID: <160402.1664218311@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/qgsT8XqY2Fk9QGY55JkBJujgIi0>
Subject: Re: [Cellar] normative references
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <cellar.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cellar>, <mailto:cellar-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cellar/>
List-Post: <mailto:cellar@ietf.org>
List-Help: <mailto:cellar-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cellar>, <mailto:cellar-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Sep 2022 18:51:58 -0000

Moritz Bunkus <mo=40bunkus.online@dmarc.ietf.org> wrote:
    > thinking transitively here: we need BCP 47 as a normative reference,
    > and BCP 47 has ISO3166-1 as a normative reference. Would it really make
    > a difference for us to make our ISO3166-1 reference informative?

That's fine that BCP47 references it. (or rather, it's not our problem)
In fact, maybe that allows us to we just remove ISO3166-1 :-)
I think that wikipedia has a list of all ccTLDs, so someone writing code
could use that rather than the stupid 200CHF ISO document.
ps:  https://archive.org/details/exploringinterne00carl

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-