documentation modification

[jefsey]

At 20:38 20/12/2010, Mike Sands wrote:
>Not sure if this is the proper forum but I would like to make a 
>suggestion for updating the documentation under the tutorials on maradns.org

Sam, Mike and all,

when Sam joined his new job he asked not to be sponsored anymore and 
told he could not develop for maradns anymore. So, he suggested me to 
start a fork for the particular evolution I have in mind. I 
considered it, consulted with some friends and decided to taste the 
water with a real site about a fork I named "alfaDNS" (it keeps the 
"a-a" sound). .

I was definitly blocked for a few months. Now, I can give a few (very 
few) hours a week to (discuss) this project  (http://alfaDNS.org).

My target is to support IDNA2008 (RFC 5890 to 5895) in building a 
dedicated IDNApplication. This means that:
- instead of supporting the IDN UTF/ASCII conversion at each 
application and passing the xn-- converted ASCII labels to the 
regular DNS system,
- I plan to run a single "ML-DNS" local server, accepting UTF domain 
names from any existing application and resolving them locally.

This is faster (direct local service), this is cheaper (one single 
name server), this is more secure and esier (everything including the 
root is local) and surer (there is single UTF/ASCII routine on a 
machine hich resolves to the same IP address what ever the 
application). This is free from national regulations. This is just a 
quick scketch, the discussion can be endless. However, this 
architecture IS now one of the accepted architectural reading of the 
RFCs that the IAB is now to digest (first IAB RFC on IDNA is pending).

The initial prototype changes are very limited :

1. to include a non 0-Z filter in the input and a punycode routine 
(with error as a default)
2. to inlucde a "xn--" filter in the output and a punycode routine 
(with error as a default)
3. to discuss the best way to support domain name information
4. to organize a developper's kit supporting minGW, Cygwin and Linux 
compilation for people (lead users, not necessarily experts) to test, 
discuss, imagine and document.

My first target would be to get people play with it, explore the code 
and review the architecture in its new environment. Then start 
designing an associated dn management and registration system to a 
full multilingual multi-TLD namespace in order to report the IETF 
through the iucg at ietf.org  (internet users contributing group) 
mailing list I facilitate (http://iucg.org).

jefsey morfin