[MaraDNS list] How to get MaraDNS and Deadwood to talk to each other?

[JFC Morfin]

At 09:20 07/03/2012, Sam Trenholme wrote:
> > I don't think it is realistic to expect people to be around 
> forever to fix the
> > bugs their own code introduced.
>
>I don't either, but there has to be someone responsible for the bugs.
>Someone with a sign above their head saying "The buck stops here with
>MaraDNS bugs".  It can, naturally, be multiple people.
>
>If there is no longer such a person, then MaraDNS will no longer be a
>viable DNS server; I may as well make maradns.org a redirect to
>unbound.net in that case.

Sam and all,

I tried to start a fork (not a continuation) of MaraDNS as alfaDNS 
(http://alfadns.org) and I supported it with small money and I 
continue (I hope so, I am a little lost with the Flattr account I 
subscribed for that).

1. The need I have is for what I call an ML-DNS logic (fully Internet 
DNS, IDNA2008 compliant and much more, multi-layer, multi-lingual 
digital name system) prototype that I could use to explore, test and 
document NETIX as part of the Internet+ architecture. If some want to 
know the architectural framework: 
http://www.ietf.org/internet-drafts/draft-iucg-internet-plus-09.txt 
and the context: 
http://www.ietf.org/internet-drafts/draft-iucg-iutf-tasks-00.txt. An 
example of my need is CLASSes MaraDNS does not support (but several 
concurrent copies can run several CLASSes in prototype mode).

I just tell this to underline that the market is wide. The Internet+ 
is the existing Internet concepts that I made Vint Cerf to 
acknowledge (this lead to the IDNA2008 consensus which was blocked 
otherwise), that are progressively embodied in Google+. Google+ is to 
make the Internet a Google network, Internet+ is to make it a people 
centric network.

2. So, the real issue for me was to *learn* how to *build* MaraDNS 
from Sam. And to use his experience (and code parts), before 
rebuilding or extending MaraDNS. Sam has not got the time and money I 
would have like to pay him for that.

3. I was hit by health issues those last months and family load (aged 
parents who died one year ago, and aftermaths) so I am quite late. My 
project was :

     - to document the MaraDNS code. Complete reverse engineering. 
But I had not the money to buy a decent program with outputs I could 
understand (I am only a C "amator").
     - to motivate a few students to take over the maintenance of 
MaraDNS hopefully as a class task under the supervision of a teacher 
who could have related with Sam on a retainer from his school.
     - to build with former students a small development team to 
develop alfaDNS as an example, a tool-kit, people could use to adapt 
their own ML-DNS architecture after we could have enrolled Sam into 
writing a book on "how to build and port your own digital name server 
and metadata registry".

I wished to explain this because this is different from only 
maintaining it, and might motivate a community on a long range.

jfc


PS. ML-DNS was discussed and partly documented by me as a facilitator 
of the iucg at ietf.org mailing list (Internet users contributing 
group). Basically it is a multilingual and multilayer front end for 
an extended MaraDNS and Deadwood functions (plus others) system, 
operating label conversion algorithm and parser.

It should be used to support personal (private external virtual 
network) roots (multiclasses) and a very extended private IANA 
system. The target is a really distributed  fringe to fringe 
Internet+ 100% compatible and compliant with the end to end Internet. 
It only is the applications of RFC 791, 1121, 1958 and 3439 on the 
Internet architecture in including the principle of subsidiarity 
which was the fundament of the IDNA2008 consensus (local mapping 
intelligence on the fringe).

Multilayer refers to the fact that the DNS supports 65.536 CLASSes 
(and therefore root files) and that IDNA has permitted to uncover the 
supposedly missing "presentation layer" ("xn--" actually represents a 
presentation) and that domain name resolution may work with a domain 
name pile in different formats, etc. for different protocols. This is 
exactly what ICANN has suggested for the DNS in its ICP-3 policy 
statement. The market is interesting: everyone can have his own 
legitimate, RFC conformant TLD.

This is NOT open roots. This is open Internet. Actually it is 
openning the whole digital ecosystem, because digital names are not 
only bound to the Internet (my real interest lies in the Intersem, 
i.e. the semantic internet of ideas, but this is another story. Even 
if the SAS (semantic addressing system) will need a name serveur).