RFC DRAFT (technical details, as needed, will be added)

               SIMPLE MAIL TRANFER PROTOCOL REGISTRY

                          Stephen M. Jones

                            November 2003

             SDF Public Access UNIX System, 501(c)7, inc
                  PO BOX 1270 Bellevue WA 98009-1270




1. INTRODUCTION

In 1996, I discussed the idea of an SMTP Server Registry with friends of mine
to help stop spam.  We agreed it would be a positive step in fighting
spam, but it would be difficult to convince global mail servers to adopt
the registry.  Back then, spam wasn't even the problem that it is today.

Since then, people have tried white lists and black lists (both of which
I disagree with) and are now *really* pushing recipient (mail servers) 
and user end (mail client) 'receipes' and bayesian filters to fight UCE.

I believe that these methods are not effective and that UCE will continue
to grow unless an SMTP registry is implemented.  Just as Domain Names and
Domain Name Servers are registered before propagation, SMTP Servers would
be registered before they would implemented as production MAIL servers.

The biggest problem with UCE is that anyone who has a dialup, ISDN or
DSL connection can setup outbound SMTP.   All though some ISPs have 
taken on the responsibility of disallowing this by TCP port filtering,
most have not.  Some sites have even begun rejecting email from
dialup/DSL connections.  This tells me that an SMTP registry could be a
solution and can be implemented using existing internet services.

The SMTP Server Registry will be completely open to anyone who wants to
run an SMTP server.  There would NO RESTRICTIONS other than the following
requirements need to be met:

a. The SMTP server must have a static IP address
b. The SMTP server must have a PTR and domain associated with that IP
c. Contact information (Name, Address, Email and Telephone number).

At first, RECIPIENT SMTP SERVERS would have to accept email from both
registered and non-registered SENDING SMTP SERVERS.  As the registry
membership grows, sites could choose whether or not to allow connections
from only registered servers.

The registry will make it possible to enforce already existing UCE and
child pornography/distribution of harmful matter to minor laws by making
the SENDING SMTP SERVER responsible and trackable for their content.

As the movement grows, so will its clout.  So that eventually, those who 
do not want UCE will no longer receive UCE.

Finally, while this may seem like a movement for techies or system 
administrators, it is actually a USER movement.  I do not intend to 
convince CEOs or sysadmins that this is necessary, but empower the 
USERS to convince their ISPs.

2. TECHNICAL OVERVIEW

Registry:

The current concept is to use existing DNS (Domain Name System RFC1034/1034)
methodology to propogate a distributed registry.  

Registered hosts would have a hostname within the SMTPNIC.ORG namespace based 
on the SMTP SERVER's IP address.

Example:  SMTP Server's IP:  192.168.0.36
          SMTPNIC Registry:  192-168-0-36.SMTPNIC.ORG

When an approriately configured RECIPIENT SMTP SERVER receives an 
incoming message from host 192.168.0.36, it will do a DNS lookup on
192-168-0-36.SMTPNIC.ORG to see that the host is indeed registered and
will allow the SMTP conversation to continue.

If a DNS lookup within the SMTPNIC.ORG namespace for the IP address of a
SENDING SMTP SERVER fails, the RECIPIENT SMTP SERVER can respond with either
a 250 informational message, telling the REMOTE SERVER to register with
the SMTPNIC or a 550 error message stating that communication was denied.

SMTP Servers:

Because of the use of existing DNS many SMTP servers, such as sendmail, can
easily be configured to use the registry by adding 4 or 5 lines of 'rules'
to their configuration.

3. META DATA

Using existing WHOIS (RFC954), users and members of the SMTPNIC will be
able to query stats such as when an SMTP server was registered, what 
contact information is publically available and when the record was last
updated.  

4. Distribution and Operations of the SMTP REGISTRY.

The REGISTRY will be distributed among namespace servers using multiple
A records (hosts) to serve DNS lookups for recipient SMTP servers.
              
The operation of the organisation shall be run by a volunteer board
representing the body of SMTP SERVERS registered with the SMTPNIC.