IETF Logo Mail Archive

Re: [Ltru] RFC4645 to Historic status

Randy Presuhn <randy_presuhn@alumni.stanford.edu> Tue, 05 September 2023 18:16 UTC

Return-Path: <randy_presuhn@alumni.stanford.edu>
X-Original-To: ltru@ietfa.amsl.com
Delivered-To: ltru@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8693FC151995 for <ltru@ietfa.amsl.com>; Tue, 5 Sep 2023 11:16:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 E79Oa-MJQOlI for <ltru@ietfa.amsl.com>; Tue, 5 Sep 2023 11:16:15 -0700 (PDT)
Received: from mail-pl1-f181.google.com (mail-pl1-f181.google.com [209.85.214.181]) (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 85AE0C15198D for <ltru@ietf.org>; Tue, 5 Sep 2023 11:15:55 -0700 (PDT)
Received: by mail-pl1-f181.google.com with SMTP id d9443c01a7336-1c34c9cc9b9so9169955ad.3 for <ltru@ietf.org>; Tue, 05 Sep 2023 11:15:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693937755; x=1694542555; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=zWVElTgnZUREP/ZGMiUR+wtmBMnzvplQZ121J/A9HyI=; b=PTifResBonqVYSzOQGjb17L8GIO2VU3mqmuAr1cpkBbdD7euC2H1wu75g3IwUO85VI i8i5m+pMrLGzkuVP18INXlV5g4kZzWvsG/gUNHBDpKXmxvSaw+LuCao6EB96hRB0xTq9 EuW3qmosyh500HoKMDE/C6OpoxNAS14Iz9XgKUtahLAK4csUEpXVSOvgtR6jdz4c+e5h FGv6bB5jcF+X4zk1dbfjnYuIgR4z7exiBpWlNuSJuxM9K1qhOdwAiwqFyAFc1Xhci9lM ZgcPxsTeFYDFC2j4M/RblFUtY41JIYFzWn3gdHt/anyzgTs3TzqgmvsxKPSQ6n8nHYNW fFlA==
X-Gm-Message-State: AOJu0Yw6cDcLf+wUDHPseiWYoev0Bq2zM+o7P5kRJZi5tPangVmJdKdd /JfE4qJ7r+hbgVcrja/0bLmY2Q==
X-Google-Smtp-Source: AGHT+IENFOGullmHkzwM4BoiohuabiiZ2OxaKMwrs9J5/RDYHVHTBvADEKffWOyKhIkzbhRZQy3wBQ==
X-Received: by 2002:a17:903:1c8:b0:1bb:59a0:3d34 with SMTP id e8-20020a17090301c800b001bb59a03d34mr13678536plh.30.1693937754895; Tue, 05 Sep 2023 11:15:54 -0700 (PDT)
Received: from ?IPV6:2601:646:9e01:27d9:7c91:33c:386a:6a1b? ([2601:646:9e01:27d9:7c91:33c:386a:6a1b]) by smtp.gmail.com with ESMTPSA id ja19-20020a170902efd300b001b9c960ffeasm9634492plb.47.2023.09.05.11.15.54 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Sep 2023 11:15:54 -0700 (PDT)
Message-ID: <8e90694c-1cda-5c3a-68c1-e5ca1b2dcf8a@alumni.stanford.edu>
Date: Tue, 05 Sep 2023 11:15:52 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.0
To: "Murray S. Kucherawy" <superuser@gmail.com>, Doug Ewell <doug@ewellic.org>
Cc: Timothy Mcsweeney <tim@dropnumber.com>, "ltru@ietf.org" <ltru@ietf.org>, "francesca.palombini@ericsson.com" <francesca.palombini@ericsson.com>, "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org>
References: <mailman.79.1692212403.2397.ltru@ietf.org> <SJ0PR03MB6598363502C6A1BE8396FEF6CA1AA@SJ0PR03MB6598.namprd03.prod.outlook.com> <516549640.3380391.1692310263006@email.ionos.com> <SJ0PR03MB65989AA736D9D1B92161CCB0CA1AA@SJ0PR03MB6598.namprd03.prod.outlook.com> <723189438.3387115.1692312008380@email.ionos.com> <SJ0PR03MB6598D695F55085A47BC932E8CA1AA@SJ0PR03MB6598.namprd03.prod.outlook.com> <1319152096.906754.1693332108616@email.ionos.com> <SJ0PR03MB6598BF87667F15857328CC7ECAE7A@SJ0PR03MB6598.namprd03.prod.outlook.com> <CAL0qLwYovamEYRSDttam7HkEQCDXQ+F-oSr_Pi8oNpqpnH_z-Q@mail.gmail.com> <460538773.209462.1693444853594@email.ionos.com> <CAL0qLwboUWzUsdna65mR1gAg12DqiCTV1xJ4udcdsPTbOpNaZQ@mail.gmail.com> <127541546.300742.1693472589908@email.ionos.com> <fa34a2df-3a0a-29d6-b646-b82b7d41df1c@alumni.stanford.edu> <SJ0PR03MB6598DFE8FB085574FD474AD6CAE8A@SJ0PR03MB6598.namprd03.prod.outlook.com> <CAL0qLwaE=uoO6n_HGhcQ2nSJvwQ_v+M9pPEAzOssCqPei4X6=g@mail.gmail.com>
Content-Language: en-US
From: Randy Presuhn <randy_presuhn@alumni.stanford.edu>
In-Reply-To: <CAL0qLwaE=uoO6n_HGhcQ2nSJvwQ_v+M9pPEAzOssCqPei4X6=g@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ltru/ThgaPIwcL9D5Z_n6-lNTn_D6vaQ>
Subject: Re: [Ltru] RFC4645 to Historic status
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ltru/>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2023 18:16:15 -0000

Hi -

I think Doug would be the better choice to write up instructions
for IANA, since he's already worked through the details of what
would need to happen to address the issues.

Randy

On 2023-09-05 10:45 AM, Murray S. Kucherawy wrote:
> On Mon, Sep 4, 2023 at 8:55 PM Doug Ewell <doug@ewellic.org 
> <mailto:doug@ewellic.org>> wrote:
> 
>     [...]
> 
>     What *is* wrong is the presentation of items on the Protocol
>     Registries page. Items 1 and 5 above are obsolete and need to be
>     moved to a separate, clearly marked "Obsolete" section, or removed
>     altogether. But once again, and hopefully once and for all, this is
>     neither a past nor a present error in RFC 4645.
> 
>     I am willing to explain all this again to whoever at IANA is in
>     charge of maintaining that page.
> 
> 
> I'm happy to loop IANA into this directly, or turn it into an IESG 
> instruction to IANA, if this is something people think is worth doing. 
> If so then yes, Doug or Randy, please just give me a set of instructions 
> to pass on to them.
> 
> In any case, I'll reject the erratum shortly unless someone stops me.
> 
> -MSK, ART AD

v2.39.1 | Report a Bug | By Email | System Status