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

Scott Bradner <sob@sobco.com> Thu, 20 October 2022 00:35 UTC

Return-Path: <sob@sobco.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 8AFD5C152581 for <last-call@ietfa.amsl.com>; Wed, 19 Oct 2022 17:35:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.127
X-Spam-Level:
X-Spam-Status: No, score=-1.127 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, RDNS_DYNAMIC=0.982, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sobco.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 1u1ZDTCOpWwk for <last-call@ietfa.amsl.com>; Wed, 19 Oct 2022 17:35:12 -0700 (PDT)
Received: from sobco.sobco.com (173-166-5-71-newengland.hfc.comcastbusiness.net [173.166.5.71]) by ietfa.amsl.com (Postfix) with ESMTP id 1CDEBC152578 for <last-call@ietf.org>; Wed, 19 Oct 2022 17:35:11 -0700 (PDT)
Received: from smtpclient.apple (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id 085CDB338FC; Wed, 19 Oct 2022 20:35:11 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/simple; d=sobco.com; s=mail; t=1666226111; bh=EEEuagBXJ4nAzTF25gjHj7cwI5s=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=AwnpWQFDYGG31gr4em+g8pXyEa71w8hbo1J8HKRvLqJFFbI11/twfQtLQnrgL7n2h WItco9kF4wmVgZoUQISzpKQzFfjaLiDvw4Ef8t9tK2ja+3TABC03EFGy9sKmUHtrLy thoCZrXIDD7GoibX3FY9yqAH0R3Jmmr2HpmNSSAw2HSgBApj9aTohpW/WpQwJIqeV0 hlxVou0HzdqwrXH9qPqMyGZ8UVz5ZkeFe4JJ0yzfpigHAkwZ6l/kx/jUHfgYXnLAVD DxRvA5JUFygVe6RRYp0y32rYfL43FOhh5+TtbLFTsEIjnU/+aEw5lB1mq6oxEaIKHE BbKe0QuMr3Lqg==
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Scott Bradner <sob@sobco.com>
In-Reply-To: <CAKr6gn127iGBjtB2+Q=80Tydfp8gnU0NOsFskU96D8digL6bUQ@mail.gmail.com>
Date: Wed, 19 Oct 2022 20:35:10 -0400
Cc: Toerless Eckert <tte@cs.fau.de>, Brian E Carpenter <brian.e.carpenter@gmail.com>, last-call@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <9BF773D1-DFD2-457E-8E71-5126CCB81FF4@sobco.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>
To: George Michaelson <ggm@algebras.org>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/Zi2iptmHr6IUZsut39TT_X9aXtY>
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 00:35:16 -0000

.int domain is in use - see, for example, itu.int

the IETF can clearly ask that any .int second level domains that were created by IETF action
(e.g. tpc.int) be removed but less clearly can the IETF ask that .int second level domains that the IETF had no
part in creating be removed

.int is run by the IANA because it has always been run by the IANA - Jon at first
then the IANA when the IANA came into existence

well prior to ICANN being formed there was talk about handing management of .int over to the ITU - 
Jon had proposed that, but told the ITU that he needed some documentation on how .int
would be run before he would do that (I was in at least two meetings between Jon and an ITU person
about the topic) - the two documents were
	1/ a clear statement on who could register in .int
	2/ a document describing how the ITU would actually operate the servers

but the ITU never produced the documents so the transfer never happened

I was not "in the room" when Jon agreed to put tpc in .int - but Marshall Rose was and 
also I assume Carl Malamud - one could ask them what their argument was

Scott

> On Oct 19, 2022, at 7:23 PM, George Michaelson <ggm@algebras.org> wrote:
> 
> I agree with what I thik Toerless is saying here.
> 
> 1) the wording in the draft appears to (re)open the door to use of the
> domain. This is despite the intent of the draft and I believe the
> organisation, to remove dependency and use of the domain. Why is this
> wording being used?
> 
> 2) why does IANA continue to "operate" the domain, if there is no
> dependency and no forseen use? The proper way to get shot of a burden,
> is to give it to somebody else. Re-delegate to ICANN and make them
> responsible for the registrar decisions about what treaty bodies are
> allowed to have state in .INT
> 
> Toerless? Is that a reasonably good take on what you said? It's what I
> think you said.
> 
> -G
> 
> -- 
> last-call mailing list
> last-call@ietf.org
> https://www.ietf.org/mailman/listinfo/last-call