Re: [art] whois email

Ned Freed <ned.freed@mrochek.com> Fri, 27 July 2018 09:43 UTC

MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="us-ascii"; Format="flowed"; DelSp="Yes"
Cc: art@ietf.org, hernani.marques@pep.foundation
Message-id: <01QVCMU3B82S0002TJ@mauve.mrochek.com>
Date: Fri, 27 Jul 2018 02:36:29 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Thu, 26 Jul 2018 23:04:38 -0600" <20180726230438.Horde.Xg504r7eG3dtrafRNVk_0BF@box439.bluehost.com>
References: <20180726230438.Horde.Xg504r7eG3dtrafRNVk_0BF@box439.bluehost.com>
To: pradeep@explodingmoon.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/N0B11-ISYK56JeMV5s4454xdciI>
Subject: Re: [art] whois email
Precedence: list

> On 26.07.2018 17:18, Ned Freed wrote:

> > And all this was back when privacy concerns were, if anything, an
> > afterthought.
> > These days the potential liability created by new laws make this idea
> > completely impractical.
> >
> > tl;dr: This is a nonstarter.

> Especially considering that after GDPR went into effect lots of
> registries (e.g., in the US) went over to mask whois data; it would also
> create additional spam problems with data harvesting.

> How do you control SPAM then?. How do you say an email is authorised
> or a spammer in a registry that can be queried by the email
> software/protocols. Spammers can get emails from not only WWW but
> ISP's and social media like facebook twitter also.whois of email can
> have only one public field authorised or unauthorised.

This is neither the time nor the place to provide you with a tutorial
on the basics of spam control. Suffice it to say it's being done without
the benefit of your proposal.

				Ned

[art] whois email pradeep
Re: [art] whois email Ned Freed
Re: [art] whois email pradeep
Re: [art] whois email Ned Freed
Re: [art] whois email Stephane Bortzmeyer
Re: [art] whois email Dale R. Worley
Re: [art] whois email Stephane Bortzmeyer