nanog mailing list archives
Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym
From: Stephane Bortzmeyer <bortzmeyer () nic fr>
Date: Thu, 13 Jan 2005 12:26:47 +0100
On Wed, Jan 12, 2005 at 10:59:43AM -0500, Steven Champeon <schampeo () hesketh com> wrote a message of 98 lines which said:
4) all domains with invalid whois data MUST be deactivated (not confiscated, just temporarily removed from the root dbs) immediately and their owners contacted.
Because there is no data protection on many databases (such as ".com" registrars who are forced to sell the data if requested), people lie when registering, because it is the only tool they have to protect their privacy. Fix the data protection problem and you'll have a better case to force people to register proper information.
5) whois data MUST be normalized and available in machine-readable form (such as a standard XML schema)
RFC 3981
Current thread:
- Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonymity" when domain exists, whois not updated yet), (continued)
- Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonymity" when domain exists, whois not updated yet) Steven Champeon (Jan 13)
- Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym Stephane Bortzmeyer (Jan 13)
- Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym Stephane Bortzmeyer (Jan 13)
- Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym Valdis . Kletnieks (Jan 13)
- Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "an Stephane Bortzmeyer (Jan 13)
- Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "an Eric Brunner-Williams in Portland Maine (Jan 13)
- Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "an Barry Shein (Jan 13)
- Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym Owen DeLong (Jan 13)
- Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym Valdis . Kletnieks (Jan 13)
- Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym Steven Champeon (Jan 13)
- Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym Stephane Bortzmeyer (Jan 13)
- /24 route propagation, how long is reasonable? Michael Airhart (Jan 13)
- Re: /24 route propagation, how long is reasonable? bmanning (Jan 13)
- Re: /24 route propagation, how long is reasonable? Jon Lewis (Jan 13)
- Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym Rich Kulawiec (Jan 13)
- Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym Eric Brunner-Williams in Portland Maine (Jan 14)
- Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym Eric Brunner-Williams in Portland Maine (Jan 14)
- Re: [eweek article] Window of "anonymity" when domain exists, whois not updated yet Owen DeLong (Jan 12)
- Re: [eweek article] Window of "anonymity" when domain exists, whois not updated yet Owen DeLong (Jan 12)
- Re: [eweek article] Window of "anonymity" when domain exists, whois not updated yet Steven Champeon (Jan 12)
- Re: [eweek article] Window of "anonymity" when domain exists, whois not updated yet Valdis . Kletnieks (Jan 12)