IETF Logo Mail Archive

[OAUTH-WG] Re: [ID-align] Re: Re: Re: Fwd: Internet Terminology Glossary

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 15 June 2024 16:22 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F52EC14F689; Sat, 15 Jun 2024 09:22:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, RCVD_IN_DNSWL_BLOCKED=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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 7Y5QbvlgAt_Z; Sat, 15 Jun 2024 09:22:38 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 133EBC14F686; Sat, 15 Jun 2024 09:22:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 41D583898B; Sat, 15 Jun 2024 12:22:36 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1ijaqoAy0mdx; Sat, 15 Jun 2024 12:22:35 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id D9F7A38988; Sat, 15 Jun 2024 12:22:34 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1718468554; bh=JZQDVMnnstakh6rqnYERn1zg29KvADFzb0T1Onl0Wmg=; h=From:To:Subject:In-Reply-To:References:Date:From; b=Xesdu80k60D6C+/5Zdv0p4IASlJosbU0ggeoVt46n1y6iZZG7v2yu08ilKJGBOHwM SBD98pUj3DyXwJEncH+17Fk/pTFye/I8zcgY00BjmYLUgSQobVwmQAmIgk15xwO25K E8X0uz6u7HhmMfk1c08kaDZ0zWK4VTbkMKKixp9CQIkTSqyESqIln2Ial5aqbgGxEq heJDy/SetNuHE0k9nr/AnYxqNFdgtpWWMgm11gAEg3BLMujLZiIc1VJNvFYxt/jrQn c4+uT/Ku3g4VyhYKZ8c1p7cJoYm3VAZz2SawdZ7KUGxXGymCmIg21eOt3FXqev9rXv pJp09jEWeOMEA==
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D21F79DD; Sat, 15 Jun 2024 12:22:34 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: id-align@ietf.org, oauth@ietf.org
In-Reply-To: <CADNypP9Z_Jd7cj7DkP-fxO-uojU+Gm_dkEGJKFhNiSq2OQKrCA@mail.gmail.com>
References: <CADNypP-8GfC3PyLtCOc0WLAj27S4y-wqQ=PapNnG6y8D5oJBYg@mail.gmail.com> <CADNypP86iON0ZO6HGRAoC8hKrPhz1gu1FUnkhr_020jqVkG8Bg@mail.gmail.com> <PH0PR02MB7430C337BCD6B9E38040CF43B7C12@PH0PR02MB7430.namprd02.prod.outlook.com> <CADNypP_qkHHcjqzm=ooFcUCni9iZT=uqmp5uV2=Pu+L6QBiHpg@mail.gmail.com> <21615.1718305840@obiwan.sandelman.ca> <CAD9ie-unMks+Ts1Qym5Lh8tTybExk2A7610SQK7SmdoQZWCUuA@mail.gmail.com> <fb9e146b-59c0-48c3-92cf-e94529ba6020@free.fr> <CAD9ie-vYVyEfnh2=k=p_BXLk06mUAHbmH1bJK9ZwffFa-a_A4g@mail.gmail.com> <78125B8E-A1B6-42AE-8517-1159BEE60F12@tzi.org> <CADNypP9Z_Jd7cj7DkP-fxO-uojU+Gm_dkEGJKFhNiSq2OQKrCA@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sat, 15 Jun 2024 12:22:34 -0400
Message-ID: <15828.1718468554@obiwan.sandelman.ca>
Message-ID-Hash: W3VXB7EABN3FLMVNV5PI2T6BMK2MATIV
X-Message-ID-Hash: W3VXB7EABN3FLMVNV5PI2T6BMK2MATIV
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-oauth.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [OAUTH-WG] Re: [ID-align] Re: Re: Re: Fwd: Internet Terminology Glossary
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/z3mgvYpb4ZN0A_HcoMUH6-VZq0I>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Owner: <mailto:oauth-owner@ietf.org>
List-Post: <mailto:oauth@ietf.org>
List-Subscribe: <mailto:oauth-join@ietf.org>
List-Unsubscribe: <mailto:oauth-leave@ietf.org>

{does oauth need to remain in the CC?}

Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com> wrote:
    > The *draft* proposal is talking about a *live* document, with some
    > ideas borrowed from the IANA registry process.

Hmm... registration process.
It sounds like you are maybe thinking _Specification Required_?

So would documents that introduce new terms then be referenced from the Glossary?
I kind of like that, but I also think it might be too restrictive if that's
the only way to add to it.  But, perhaps different entries have different
levels of authority, and a term that comes from a Specification gets a higher
status.

In general, I think about the many (often vastly different) definitions that
one can see in, for instance, the urban dictionary (.com).

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

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