Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] Codenamed: MUD4TLD

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] Codenamed: MUD4TLD


Chronological Thread 
  • From: "Niels Dettenbach (Syndicat IT&Internet)" <nd AT syndicat.com>
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] Codenamed: MUD4TLD
  • Date: Sun, 10 Jun 2012 08:46:16 +0200

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



Tim Groeneveld <tim AT timgws.com.au> schrieb:

>Would it be bad for me to suggest then that before starting on the
>aptly named 'OpenNIC Remote Management Application Programming
>Interface' that we first discuss how the API system should work?
>
>This way, other operators can also look into the design and we can have
>one unified system.
>This will also allow all of us to integrate your/the same API.

There are still many commercial and self developed solutions out in the field
which are "connecting" registrars to registries in the ICANN world, IANA /
RIRs and the most i've seen around was two "quasi standards"

- - email based robots / service interfaces - working with "email templates"
- are widely spread and available on most of them i've seen until today.

- - less often: XML by HTTP(s)

Emails usually could be signed with PGP/GnuPG or MD5 hashes are sent with
them in a "auth" field.

If OpenNIC want's to be open to the existing world of domain providers,
registrars and their applications i hardly could recommend to start with a
email service interface which could be implemented as easy as typical web
services too.


cheers,


Niels.
- --
Niels Dettenbach
Syndicat IT&Internet
http://www.syndicat.com
-----BEGIN PGP SIGNATURE-----
Version: APG v1.0.8

iIEEAREIAEEFAk/UQrg6HE5pZWxzIERldHRlbmJhY2ggKFN5bmRpY2F0IElUJklu
dGVybmV0KSA8bmRAc3luZGljYXQuY29tPgAKCRBU3ERlZRyiDSOYAJ48L68C3HJW
oP9Pe9yT19F+lyglCQCfR8aKz9NJ/TXJ6H8Xj1t93v4VDDg=
=dcGL
-----END PGP SIGNATURE-----




Archive powered by MHonArc 2.6.19.

Top of Page