IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 20 October 2022 01:34 UTC

Return-Path: <brian.e.carpenter@gmail.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 E2EC0C1524DF for <last-call@ietfa.amsl.com>; Wed, 19 Oct 2022 18:34:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level:
X-Spam-Status: No, score=-2.11 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham 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 qqCoLKFvIJLO for <last-call@ietfa.amsl.com>; Wed, 19 Oct 2022 18:34:14 -0700 (PDT)
Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) (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 69631C1524D0 for <last-call@ietf.org>; Wed, 19 Oct 2022 18:34:14 -0700 (PDT)
Received: by mail-pj1-x102c.google.com with SMTP id fw14so18425884pjb.3 for <last-call@ietf.org>; Wed, 19 Oct 2022 18:34:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=KzlnX5sAGZxDP7WIb+uOJ5LmHL42n4eITDAo9kCHInQ=; b=KxcM2FfX/mWLuWeuOI32TcoX+SnwoDahzU2yZTvaiX0Ax8Qga5ju/aenOsTJmVfYUP RCIb3KSxBm/tE2XxhrLfKDE8CqRnGAJf4bXapShxZgwCAQ05YJAai4wHiGhwCg/1FpTh 5htmq5wJIUPTGQhQBQ4OKfsovKIFlblhoumO4AJxTooMC7pMCo4YGQCzC9X3a5kWS1qh pdUaFh6nZNRzFU5wHUt2qQViNwL1sNdKzQZUwBKMdgq7ncvxcDWOw9Btuld/26wOfNxc Hs719WHm53so0+hb+8eBHlbpfnxF8C3cqxC5sETZgER/ThvWRTY+ZRiW9Q2LsxzEywTX 5IMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=KzlnX5sAGZxDP7WIb+uOJ5LmHL42n4eITDAo9kCHInQ=; b=tP7JqHabs7KpojYFFDlx+g7zz2Aj/1LXX+Z7X60ZOhiOLMsjwCJVRkqZHmqANP10+r SZe7tmP+Vx+m/jIfO/89yhXKHtjhKx8+UBnoYWs5IhbdFrZTk+Qjo9lxGgSXCxEaI+I5 g6Fa+4TCWOO9lZmOuUacaAe4x25Qz9GhSMmpJDH3HiU2bldFKx5gsk7p+wSnY8tbecoM U1x3bmmzkkZe5lF+NWpj+jDm2aNY0kmeW6yoZN54huMHUrazYkIbflbBeB8lTux4xfLk jDNjUoHHIszE+H9lndnyJJZnqUuu03u4Gw7GdUpsodNLxNfIlX6RPc1p7KItwcWV5Khl PNRg==
X-Gm-Message-State: ACrzQf34MYk1jmtrCYxsYgKupFz1p/IkBb0TV8dF1gnkymHB0W8qJcTz BgliRPy8SnzLaQV0kOl6AbA=
X-Google-Smtp-Source: AMsMyM4gnI/MroHZGRloPhyFSY7jaWjcWx/+UAo8wPxnTJeIa6Avw7b3Kth6BVJV92CA3OPCZxlGLA==
X-Received: by 2002:a17:90b:110c:b0:205:cfeb:cfb with SMTP id gi12-20020a17090b110c00b00205cfeb0cfbmr13151473pjb.75.1666229653880; Wed, 19 Oct 2022 18:34:13 -0700 (PDT)
Received: from ?IPV6:2406:e003:1124:9301:80b2:5c79:2266:e431? ([2406:e003:1124:9301:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id p14-20020a170902780e00b0017d7e5a9fa7sm7114119pll.92.2022.10.19.18.34.11 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 19 Oct 2022 18:34:13 -0700 (PDT)
Message-ID: <e41a14ed-80d0-5aee-7d50-2134c0f0d015@gmail.com>
Date: Thu, 20 Oct 2022 14:34:09 +1300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Scott Bradner <sob@sobco.com>
Cc: George Michaelson <ggm@algebras.org>, Toerless Eckert <tte@cs.fau.de>, last-call@ietf.org
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> <B36913F1-662D-404F-B266-68BE6BABEED2@sobco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <B36913F1-662D-404F-B266-68BE6BABEED2@sobco.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/SP20YBceJKEMeJRhx5rh1OQmD88>
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 01:34:15 -0000

On 20-Oct-22 14:05, Scott Bradner wrote:
> 
> 
>> On Oct 19, 2022, at 8:58 PM, 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.
> 
> not sure I agree with this the way it is stated - ICANN does not generally have authority over TLD subdomains
> which is what this discussion is about

What I mean is that ICANN has authority over who delegates
subdomains within a TLD. For almost all TLDs, ICANN has
delegated that authority, but as far as I know, ICANN has kept
it for itself in the case of .int.

Are you arguing that we should change the first sentence of
the Introduction in some way? That's the only sentence in
the document that doesn't directly concern the obsolete
technical sub-domains.

    Brian


> 
> Scott

v2.23.0 | Report a Bug | By Email