Discuss mailing list

[Martin C <martin AT mchomenet.com>]

Based upon the idea of simple message passing, this API could work under 
any system that can handle the call, whether it is running MUD4TLD or 
not. It would in fact be TLD manager agnostic.

cmd:
* register/record (could be used interchangeably, or we could decide on 
just one of them) - registers a domain.
* update - sends updated information. in this instance, it would 
primarily be an updated email address for WHOIS.
* transfer - for between "registrars"/DNS providers. Could also use a 
temporary "moving key", much like how the EPP codes are used. this 
updates the user ID assigned to the domain, which in turn is a reference 
to the dataset of the list of registrars.
* delete - self explanatory. bye bye domain.
plus others that we find out we need.

user - this is the user tag (similar to a username, but is not used to 
login to the system by the registrar).

userkey - acts like a password/passkey to verify the user is a 
registrar, but is not actually used to login either.

domain - self explanatory. The domain, probably without TLD.

tld - for systems hosting mulitple TLDs via different datasets and/or 
databases. This also allows for seamless, but not necessarily 
deliberate, integration for TLD managers running MUD4TLD.

name  - the name that will appear in the WHOIS listing.

email - the email that will appear in the WHOIS listing.

ns1,ns2 - the nameservers used by the DNS providers. or we can allow DNS 
providers to designate default DNS servers to use for all registrations 
they do and we can just read from that.

For domain transfers, two additional settings could be passed, 
creatively called newuser and newuserkey.

The API in turn, could detect the IP address making the request and 
determine if the IP is authorised by the registrar to make these 
requests. This could help prevent potential malicious use.

Is this a good start?

Martin.