Open ekr opened 1 year ago
I suspect it'd be most helpful to start a separate issues list, or use a label in this one, to identify what such an effort might encompass.
+1 to @mnot. Also, I'd be willing to edit this document.
Thanks.
Please do not create a new 7991-bis type issues in this repo. If the WG decides to move forward with a -bis, we'll create a separate repo for issues.
@ekr my point is that it's chicken-and-egg; some people seem reluctant to green-light a substantive revision until we have an understanding of what its scope is, but we can't define the scope without discussing the inherent issues.
Not using this repo is fine, but can we have an RSWG issues list dedicated to the task elsewhere, without formally moving forward?
There appears to be WG interest on producing an RFC 7991 bis document that would include substantive changes.
Potential inputs to this include https://datatracker.ietf.org/doc/draft-hoffman-rfc7990-updates/ https://datatracker.ietf.org/doc/draft-iab-rfc7991bis/