IETF Logo Mail Archive

Re: [Last-Call] Last Call: <draft-davies-int-historic-04.txt> (Deprecating infrastructure "int" domains) to Informational RFC

John C Klensin <john-ietf@jck.com> Thu, 20 October 2022 03:36 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 248E6C14F726 for <last-call@ietfa.amsl.com>; Wed, 19 Oct 2022 20:36:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.908
X-Spam-Level:
X-Spam-Status: No, score=-6.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 FH_PAATEORK8 for <last-call@ietfa.amsl.com>; Wed, 19 Oct 2022 20:36:53 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18083C14F724 for <last-call@ietf.org>; Wed, 19 Oct 2022 20:36:52 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1olMMR-000JNI-Nm; Wed, 19 Oct 2022 23:36:47 -0400
Date: Wed, 19 Oct 2022 23:36:42 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, George Michaelson <ggm@algebras.org>, Scott Bradner <sob@sobco.com>
cc: Toerless Eckert <tte@cs.fau.de>, last-call@ietf.org
Message-ID: <DE1C07A82F4BDA4EB39122B8@PSB>
In-Reply-To: <60a5667b-b37c-c991-0f77-e2ce4ecfa3c0@gmail.com>
References: <166621075802.44847.14382611991776479938@ietfa.amsl.com> <371922.1666215280@dyas> <Y1B7IPGPfzDcDDxE@faui48e.informatik.uni-erlangen.de> <295948c3-b116-365f-a682-6e286be69ffb@gmail.com> <Y1CCh1XOwkNFafet@faui48e.informatik.uni-erlangen.de> <CAKr6gn127iGBjtB2+Q=80Tydfp8gnU0NOsFskU96D8digL6bUQ@mail.gmail.com> <9BF773D1-DFD2-457E-8E71-5126CCB81FF4@sobco.com> <CAKr6gn3sxCmZJkagN9-fzPa_c1ssW0yGofXXEROKz3q4JtzLyg@mail.gmail.com> <60a5667b-b37c-c991-0f77-e2ce4ecfa3c0@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/8zaws9c7ADFjVRB9fpQK5MauAkI>
Subject: Re: [Last-Call] Last Call: <draft-davies-int-historic-04.txt> (Deprecating infrastructure "int" domains) to Informational RFC
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2022 03:36:55 -0000


--On Thursday, October 20, 2022 13:58 +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>...
> In terms of authority, authority over TLDs has resided with
> ICANN since 1998, except for .arpa and this tiny corner of
> .int. The IETF is now documenting what has been a fact for
> many years: this tiny corner of .int is totally obsolete.
>...

Brian,

I worked quite a bit on an earlier version of this draft and
will probably have more to say when I get my head above water on
some other issues, but, for now and on the extract above only,
please don't forget EDU, MIL, and a few others over which I
don't believe ICANN has ever claimed authority.. and suspect
that any attempt to exercise authority (especially over the
second of those) would cause an interesting situation.

That said, other than issues with INT, it appears to me that
where ICANN does or does not have or claim authority is
completely irrelevant to this document.

    john

v2.23.0 | Report a Bug | By Email