Fri, Jul 19, 2019 at 02:00:08PM -0500, Nico Williams: > At the IETF we _publish_ RFCs, and we _submit_ Internet-Drafts. So my > use of "publish" was short-hand "publish RFCs", but I left "RFCs" out > because part of the point of this thread was to find a way to "publish" > something more "stable" than Internet-Drafts with less process than RFC > publication requires. > > I used "publish", then, as short-hand for "more stable than an I-D, less > heavy-duty than an RFC" since we don't have a name for what that thing > would be. drafts, (iab/irtf/individual) rfcs, bcps, stds, and i suspect more that I am forgetting or am unaware of. All related, but not equal. The stable idea is Kumari's. Except for Keith's suggestion of accelerating the bcp/rfc processes, we are not suggesting changes to those processes. If a way to accelerate were agreed upon, such as review of changes only, it may still deserve a new name to make this difference clear. And it MAY not have the same review requirements - again mpov.
