[122852] in North American Network Operators' Group
Re: Email Portability Approved by Knesset Committee
daemon@ATHENA.MIT.EDU (Florian Weimer)
Mon Feb 22 14:05:02 2010
From: Florian Weimer <fw@deneb.enyo.de>
To: Steven Bellovin <smb@cs.columbia.edu>
Date: Mon, 22 Feb 2010 19:58:35 +0100
In-Reply-To: <3C19B274-DFDD-4D58-B236-716FD46AE271@cs.columbia.edu> (Steven
Bellovin's message of "Mon, 22 Feb 2010 13:51:32 -0500")
Cc: NANOG Operators Group <nanog@merit.edu>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
* Steven Bellovin:
> Right; I was not seriously suggesting that the DNS was the right
> spot for it. I am seriously suggesting that a redirect mechanism --
> perhaps the email equivalent of HTPP's 301/302 -- would be worth
> considering. Then, of course, there's problem of upgrading the
> $\aleph_0$ mail senders out there to comply...
There's already SMTP support for this, see RFC 5321, section 3.4.
This has been carried over from RFC 821, which already contain the
251/551 response codes.
However, this is still a public database for which you cannot charge
access, so it's not the solution we're looking for.
