Job,
On Mon, Nov 06, 2023 at 06:34:29PM +0100, Job Snijders wrote:
> The todo items I noted for myself:
[...]
> Call for working group adoption: draft-msri-grow-bmp-bgp-rib-stats
And as we discussed, we're hoping to figure out a pattern for reasonably
fast turn around on this item. We want some review here to encourage
standardizing things, but we could move faster by doing first-come,
first-served code points.
Here's a proposal for boring "this draft has nothing other than BMP code
point requests for counters":
- The call is for adoption and REVIEW of the contents. Perhaps it runs a
little longer than the normal 2-ish week cycle done for a lot of drafts -
maybe a month?
- If adoption/review succeeds, the chairs assist the authors in submitting
the code point request as part of the early allocation procedures from the
"standards required" pool.
+ Work on the semantics for the code points is then owned as a standard
WG document and follows process.
+ Code can start!
+ TBD what's the exit criteria for RFC publication? Shipping
implementation(s)? No further discussion and the WG thinks this is
"done"?
- If adoption fails, the authors can go off an request FCFS instead.
My suspicion is that in future some people will just grab FCFS and want to
"upgrade" them by documenting them in an RFC instead. The process could
largely be the same as above, where if the WG agrees on the semantics and
publishes it as an RFC, the main change is the related update to IANA to
publish the RFC as a reference point.
-- Jeff
_______________________________________________
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow
