On 17/04/2022 20:14, Christian Huitema wrote:
This submission raises an interesting question for the IETF: how to treat anonymous (or pseudonymous) submissions?
Perhaps if the author wishes the draft to proceed they will be happy to self-identify, or perhaps not. I'd not worry too much about the general problem 'till that's clear. The text of the draft itself seems innocuous enough. While I'm not clear what useful purpose might be served by having such text in an RFC, I'd be willing to be convinced but so far remain to be convinced. Process-wise, I'd say unless this were modified to address some IETF-specific issues (such as netiquette in developing protocols) it'd likely be better targeted to the IAB or ISE streams. (That's no reason to not discuss it here though.) S.
OpenPGP_0x5AB2FAF17B172BEA.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ ietf-privacy mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf-privacy
