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

Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com> Tue, 18 June 2024 13:07 UTC

Return-Path: <rifaat.s.ietf@gmail.com>
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 48535C14F610; Tue, 18 Jun 2024 06:07:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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
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 e9OuqNeR6uvS; Tue, 18 Jun 2024 06:07:23 -0700 (PDT)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 98F34C14F6A8; Tue, 18 Jun 2024 06:07:23 -0700 (PDT)
Received: by mail-lf1-x135.google.com with SMTP id 2adb3069b0e04-52bd48cf36bso6204106e87.3; Tue, 18 Jun 2024 06:07:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718716041; x=1719320841; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=zm5lRvi9aC1fhS9Ae2GMWhEW8OjWiNIPPf4lTsxbLDc=; b=kb4FQ40j8ap/Uvu7fW44k85dL1OXJntlw/LKGURK++tiBOB4XkRJx21ZgfhfWlD88y r1jHOBSuSOD6H8dMGd/ncIpfBgjFcL67lvTkPT79ECo2wbf9aJ+Rjz+TwV1zXefj8ige wrUSTKcLC/Us3gHFFZjIS4sAXHmGTX2F9Pb/boxHzVJXOp18Udi4530TfumOZvpE8aNB ZlhD5KpTV6c5vwunlvGMKyqP80FwcrbKmjzKbBBqXuRWzmL1q2XlGwM2fCpHlv6N669G nitzIxfCfH0Lm5Zh469rZjHP/EUojL21ru/62z/pr2olzA/T0iEyadxaOmkEwcNysowa webA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718716041; x=1719320841; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=zm5lRvi9aC1fhS9Ae2GMWhEW8OjWiNIPPf4lTsxbLDc=; b=XR2LxEBzXGXxhRvWMpQIHHVkS9mhd4TXF6qeEcrIdX2fOAEEl9+iGwSIkrKwXfEfl8 8tqTClonFhrRBJ4AUuoA326xNOSQt8zuZOb9ifKyY1a6aj80dDJ6Kywy/sWYe/YCmgoA 6zPJHM5ONYc6e4xyoD19++oDKfkemJdoJbqpCuKPLVzq3i+89AnV/Ssn2IyujbGcfjui F/GpTi4qmwukmnpkP78wViqYBzPxZHS7U8SDfU/7QWd27NkdrICPSrhyO2Dd/BIqM9Bi qUJuu4ZTsDr6jiYR3lkrvs+ly/Y3BFXe9ptcUMu/vGV2k13Quj8d6Lws96kw2KwPzJrY Bmkw==
X-Forwarded-Encrypted: i=1; AJvYcCUji6RQABwCEodx06LBRqPF1RNrz33vIwthPx+YKLp8e1tszgC+F2tAzCwaOGx3KjQbP8ycsEo7RbsG/eo85y3KO+yxoj8a/yg4vA+KXC/S99w=
X-Gm-Message-State: AOJu0YwCE0IrF7JZDhR6c6uf8+ioiDZ4csy/gFWFfOu1M5Qma1+PZzI+ Z+5co82LIRM02Mj6cg9dQZzKMUw28qMuiLeQ3QeD2ArUagB0icnEWjN3gWiEQy+zbjFTY5HFDwC CIG263ZCBm45TDQMSUKaKnsKcZMnTPQ==
X-Google-Smtp-Source: AGHT+IH6X5M4aU+bilCYvvckoZ3vz0jHPYUzgnFca1isDQstuJaRmDAWJHXOO3dli9QR8yc0NsSPFTxFOCE//6X7fMA=
X-Received: by 2002:ac2:443c:0:b0:52c:9906:fa33 with SMTP id 2adb3069b0e04-52ca6e92f06mr8487400e87.43.1718716040704; Tue, 18 Jun 2024 06:07:20 -0700 (PDT)
MIME-Version: 1.0
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> <15828.1718468554@obiwan.sandelman.ca> <CAD9ie-ud19aD5LUtP4PB=tijTFRc5aQcJ6wNZvYQvoWJWT9Rvw@mail.gmail.com>
In-Reply-To: <CAD9ie-ud19aD5LUtP4PB=tijTFRc5aQcJ6wNZvYQvoWJWT9Rvw@mail.gmail.com>
From: Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com>
Date: Tue, 18 Jun 2024 09:07:09 -0400
Message-ID: <CADNypP8P1Z-MC8fxDRzsoU2EdoJrwPCwDhjp_E2aRa3sii=Reg@mail.gmail.com>
To: Dick.Hardt@gmail.com
Content-Type: multipart/alternative; boundary="000000000000137e77061b29c328"
Message-ID-Hash: IPJYINFQ74HFGOXCNNENRYBNQEIXJMFX
X-Message-ID-Hash: IPJYINFQ74HFGOXCNNENRYBNQEIXJMFX
X-MailFrom: rifaat.s.ietf@gmail.com
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
CC: Michael Richardson <mcr+ietf@sandelman.ca>, id-align@ietf.org, oauth@ietf.org
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/0Dd1J8oCKAEq9Px7FGyINlPonkE>
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>

On Mon, Jun 17, 2024 at 4:49 PM Dick Hardt <dick.hardt@gmail.com> wrote:

> ( OAuth is in the cc cuz Rifaat :)
>
> Guilty as charged :)

Regards,
 Rifaat

The objective is to reduce confusion in standards development by gathering
> the definitions for terms used in existing specifications, and to create
> awareness of the existing definitions for new work so that existing
> definitions are used, or new definitions are intentionally created.
>
> So yes, documents with new terms, and new definitions for existing terms
> would be referenced in the glossary.
>
> On Sat, Jun 15, 2024 at 9:23 AM Michael Richardson <mcr+ietf@sandelman.ca>
> wrote:
>
>>
>> {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
>>
>>
>>
>>
>> _______________________________________________
>> OAuth mailing list -- oauth@ietf.org
>> To unsubscribe send an email to oauth-leave@ietf.org
>>
> _______________________________________________
> OAuth mailing list -- oauth@ietf.org
> To unsubscribe send an email to oauth-leave@ietf.org
>