If you want a dynamic document, you could create a BCP. And the RFC could
indicate that it obsoletes RFC 4949.
From: Rifaat Shekh-Yusef
Sent: Thursday, June 13, 2024 10:34 AM
To: Michael Jones
Cc: oauth ; id-al...@ietf.org
Subject: Re: [OAUTH-WG] Fwd: Internet Terminology Glossary
That's wher
That's where we started, but that was deemed problematic because that
document was produced as an Independent Submission Stream, which is outside
of the IETF process.
Also, the RFC is a static document, while what we are proposing is a living
and dynamic document.
Regards,
Rifaat
On Thu, Jun 13
A BCP is not a living document.
We do not want to publish a new RFC every time there is a new term defined
somewhere.
On Thu, Jun 13, 2024 at 1:50 PM Michael Jones
wrote:
> If you want a dynamic document, you could create a BCP. And the RFC could
> indicate that it obsoletes RFC 4949.
>
>
>
>
Is this intended to replace https://www.rfc-editor.org/rfc/rfc4949.html?
From: Rifaat Shekh-Yusef
Sent: Thursday, June 13, 2024 9:14 AM
To: oauth
Subject: [OAUTH-WG] Fwd: Internet Terminology Glossary
-- Forwarded message -
From: Rifaat Shekh-Yusef
mailto:rifaat.s.i...@gmail.c
