John C Klensin <john-ietf@xxxxxxx> wrote:
> --On Friday, June 11, 2021 16:35 +1000 Lloyd W
> <lloyd.wood=40yahoo.co.uk@xxxxxxxxxxxxxx> wrote:
>> Has the IESG considered renting out @member.ietf.org or
>> @supporter.ietf.org addresses as a potential revenue stream? Throw in
>> a free github account to sweeten the deal and so that access to
>> discussion is not unnecessarily limited.
> Lloyd,
> Prior experience with people being allowed to set up IETF-provided
> mailing lists for discussions that seemed rather far out on the edges
> of IETF work, deliberate misrepresentations of Informational RFCs or
> even I-Ds as IETF standards, etc., suggests that it would be a small
> jump from troll@xxxxxxxxxxxxxxx (and what is a "Member" or the IETF
> anyway?), disrupter@xxxxxxxxxxxxxxxxxx, or even
> nutcase@xxxxxxxxxxxxxxxxxxxx from even worse misrepresentations about
> positions and authority.
I see your point, so I suggest maybe it be restricted to people with
published RFCs.
Being able to put a stable contact into an RFC seems like a good thing to me.
I know we have draft-xxx@xxxxxxxx aliases, and those can get updated via the
DT, I'm unclear if I can email rfcxxxx@xxxxxxxx to reach the authors, and
that's not what's listed in the RFC.
As for member, supporter, etc. I'd suggest "contributor.ietf.org".
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@xxxxxxxxxxxx http://www.sandelman.ca/ | ruby on rails [
--
Michael Richardson <mcr+IETF@xxxxxxxxxxxx>, Sandelman Software Works
-= IPv6 IoT consulting =-
Attachment:
signature.asc
Description: PGP signature
