Return-Path: 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 To: id-align@ietf.org, oauth@ietf.org In-Reply-To: References: <21615.1718305840@obiwan.sandelman.ca> <78125B8E-A1B6-42AE-8517-1159BEE60F12@tzi.org> 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 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: =?utf-8?q?=5BOAUTH-WG=5D_Re=3A_=5BID-align=5D_Re=3A_Re=3A_Re=3A_Fwd=3A_Inter?= =?utf-8?q?net_Terminology_Glossary?= List-Id: OAUTH WG Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable {does oauth need to remain in the CC?} Rifaat Shekh-Yusef 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 Glo= ssary? 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 high= er status. In general, I think about the many (often vastly different) definitions that one can see in, for instance, the urban dictionary (.com). =2D- Michael Richardson . o O ( IPv6 I=C3=B8T consulti= ng ) Sandelman Software Works Inc, Ottawa and Worldwide --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQFKBAEBCgA0FiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmZtv8oWHG1jcitpZXRm QHNhbmRlbG1hbi5jYQAKCRCAi3D73dDdZWBwCAC9+iiDC999LwZbOR/fzfG5JMy2 ulzLXknSYPFcdSKckYGGz1BKWxFx6FpqdouXWoAqDHm336DTPtEJUPc535VV5q/7 izMMeP4uQ8MdZHO/mlpsDf9NcXmfqqAAKmJRKNZ2WmvR6mBIC6dcNs9yxN+x+RxB 7LpCRrI/PcZsh22cUzrxbfwJUfKMQ3Ow7q/Z15zF27/74V6TMr9yMBPA8mg/oL/S nPqT/O2OB/h1leQ0r6SpluG8oDd9Xv5gGSC3gw4S2A0neaaQjewk6JiiWSfiCvpC 7WpVUpzGU4l7w+PhG1bOHdg//ot2I84iWSuq9KraK42CG2/EegqTDvpTw4p+ =9R5u -----END PGP SIGNATURE----- --=-=-=--