RFC8555 was published [1] 5 years ago today! Just thinking aloud, 'cos I'm curious what folks here think... At what point might it make sense to start work on an 8555-bis?
There's a fairly long list of Errata [2]: 10 Verified, 5 Reported, and 4 Held for Document Update. Would it make sense for an 8555-bis document to incorporate and obsolete any of the "add-on" RFCs / I-Ds, such as RFC8738, that have been published since RFC8555? Or, conversely, would it be preferable to not do that? With 5 years of deployment experience behind us, have any "missing" features in RFC8555 been identified that would be best addressed by updating the core specification (i.e., in an 8555-bis document) rather than by writing new "add-on" I-Ds? Or, conversely, are "add-on" I-Ds always the preferred approach? (The "missing" feature that immediately springs to my mind is "profiles" [3]). [1] https://mailarchive.ietf.org/arch/msg/rfc-dist/25pD6Za_dVkXMbJwyPhBJR6nIlo/ [2] https://www.rfc-editor.org/errata_search.php?rfc=8555 [3] https://mailarchive.ietf.org/arch/msg/acme/BLVAayrTrUCegT4s2twci3Q2BY8/ -- Rob Stradling Senior Research & Development Scientist Sectigo Limited
_______________________________________________ Acme mailing list Acme@ietf.org https://www.ietf.org/mailman/listinfo/acme
