Re: [Ltru] RFC4645 to Historic status
Randy Presuhn <randy_presuhn@alumni.stanford.edu> Tue, 29 August 2023 20:28 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 42761C13AE54 for <ltru@ietfa.amsl.com>; Tue, 29 Aug 2023 13:28:31 -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=unavailable 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 BrGuZSzXpjIf for <ltru@ietfa.amsl.com>; Tue, 29 Aug 2023 13:28:30 -0700 (PDT)
Received: from mail-pl1-f178.google.com (mail-pl1-f178.google.com [209.85.214.178]) (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 E6EF0C13AE4C for <ltru@ietf.org>; Tue, 29 Aug 2023 13:28:25 -0700 (PDT)
Received: by mail-pl1-f178.google.com with SMTP id d9443c01a7336-1bdc19b782aso30830485ad.0 for <ltru@ietf.org>; Tue, 29 Aug 2023 13:28:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693340905; x=1693945705; 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=rNzlLG3alJKHGV2lSp4hzS8MbC+ZxTx78SgWKGW8yEE=; b=Zh046TmU5ps1214ziEtZ36JkUDu9et1/BmbeoCdS1VBCD9fKbrrTO6S9SD4yjENNfx FOTpiHjL+dfBgjWAVNy6vFTcoWzrAbWdXCIdV/DmQMPOcNvRTWJb6N+a9Z4pbVpe6r8n uEHs9cJ0fM8xbu0w9gr8oO598Y2LxYZNvKAAfjZ91COW+V/oXnXxuZ2CK9xiDBYwIaON TCMJ9XAp3xjUrqnI81UmBlHfoX7U64dZ2BJaEHRFVLGOQ0F9LOSPZqPaOcfBQNeUMtFB c7T3t3ewzTP7g0hHIeqPABxnMo7jKfd1p3GTrArP4ARtUTbB70RdL3EpaU4YugiMrE+R P/BQ==
X-Gm-Message-State: AOJu0YzAJzfP1Lzwi66Wq1xksNPYdPzTDoFjUuATm+lff4fwNSg8Er+z lwfz0ZyydgOq0M8dZd9eG9cqmg==
X-Google-Smtp-Source: AGHT+IE69MzbPJwdtWQhPHURfVPczc1MHed8VdI9X9XZpEyr0Q5FlTySTweaNn/D0Vn7UYZwPIxtQw==
X-Received: by 2002:a17:903:124a:b0:1c0:c0af:ba59 with SMTP id u10-20020a170903124a00b001c0c0afba59mr233471plh.34.1693340905001; Tue, 29 Aug 2023 13:28:25 -0700 (PDT)
Received: from ?IPV6:2601:646:9e01:27d9:510d:8a4c:2c52:bc9b? ([2601:646:9e01:27d9:510d:8a4c:2c52:bc9b]) by smtp.gmail.com with ESMTPSA id je1-20020a170903264100b001b80d411e5bsm9791708plb.253.2023.08.29.13.28.24 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 29 Aug 2023 13:28:24 -0700 (PDT)
Message-ID: <9a44e89d-aa92-91db-6878-802f47bc687b@alumni.stanford.edu>
Date: Tue, 29 Aug 2023 13:28:22 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.14.0
Content-Language: en-US
To: "Murray S. Kucherawy" <superuser@gmail.com>, Doug Ewell <doug@ewellic.org>
Cc: "ltru@ietf.org" <ltru@ietf.org>, Timothy Mcsweeney <tim@dropnumber.com>, "randy_presuhn@mindspring.com" <randy_presuhn@mindspring.com>, "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>
From: Randy Presuhn <randy_presuhn@alumni.stanford.edu>
In-Reply-To: <CAL0qLwYovamEYRSDttam7HkEQCDXQ+F-oSr_Pi8oNpqpnH_z-Q@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/TUX0GV5sbNWGWu9CFCM03fA6uII>
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, 29 Aug 2023 20:28:31 -0000
Hi - On 2023-08-29 12:56 PM, Murray S. Kucherawy wrote: > On Tue, Aug 29, 2023 at 12:40 PM Doug Ewell <doug@ewellic.org> wrote: > >> I am still puzzled by all of the attention suddenly being paid to RFC >> 4645. It is not a reference for language tagging, and never claimed to be >> one. The document which spurred this discussion does not reference or >> mention RFC 4645. >> > > I have the same question. I've lost track: What are we trying to > accomplish here? Is it more than clarifying/adjusting an IANA page? RFC 4645's status is informational. The abstract states: "This memo defined the initial contents of the IANA Language Subtag Registry for use in forming tags for the identification of languages. Since the contents of this memo only served as a starting point for the registry, its actual contents have been removed before publication to avoid confusion. This memo provides information for the Internet community." Changing its status to historic seems inordinately pointless, and certainly not worth the process energy needed to make such a change. Randy
- Re: [Ltru] [Technical Errata Reported] RFC4645 (7… John Cowan
- [Ltru] [Technical Errata Reported] RFC4645 (7605) RFC Errata System
- Re: [Ltru] [Technical Errata Reported] RFC4645 (7… Doug Ewell
- Re: [Ltru] [Technical Errata Reported] RFC4645 (7… Timothy Mcsweeney
- Re: [Ltru] [Technical Errata Reported] RFC4645 (7… Doug Ewell
- Re: [Ltru] [Technical Errata Reported] RFC4645 (7… Doug Ewell
- Re: [Ltru] [Technical Errata Reported] RFC4645 (7… Doug Ewell
- Re: [Ltru] RFC4645 to Historic status Doug Ewell
- Re: [Ltru] RFC4645 to Historic status Murray S. Kucherawy
- Re: [Ltru] RFC4645 to Historic status Randy Presuhn
- Re: [Ltru] RFC4645 to Historic status Timothy Mcsweeney
- Re: [Ltru] RFC4645 to Historic status Murray S. Kucherawy
- Re: [Ltru] RFC4645 to Historic status Martin J. Dürst
- Re: [Ltru] RFC4645 to Historic status Timothy Mcsweeney
- Re: [Ltru] RFC4645 to Historic status Doug Ewell
- Re: [Ltru] RFC4645 to Historic status Doug Ewell
- Re: [Ltru] RFC4645 to Historic status Randy Presuhn
- Re: [Ltru] RFC4645 to Historic status Doug Ewell
- Re: [Ltru] RFC4645 to Historic status Murray S. Kucherawy
- Re: [Ltru] RFC4645 to Historic status Randy Presuhn