denis walker wrote on 10/10/2022 21:33:
The bottom line is that we cannot make assignments optional unless we
either disregard rfc7020 or we propose to the IETF an update to
rfc7020 by removing a large proportion of the current registration
data from the goals and core requirements. In
Denis,
rfc7020 is an informational rfc, not BCP or Standards Track. I.e. it is
intended to be descriptive rather than prescriptive. If the RIPE
Community wants to change how assignments are documented, it can do this.
Nick
--
To unsubscribe from this mailing list, get a password reminder, or change your
subscription options, please visit:
https://lists.ripe.net/mailman/listinfo/address-policy-wg
