>> There should be no register, because they should not exist. > >This appears to assume that naming systems are only developed in the >IETF or that a naming system not developed in the IETF is not >relevant/impactful. > >I don't think this is a good assumption.
To be more specific. In my opinion, the IETF should not reserve any names for for naming systems developed outside the IETF. Obviously, anybody is completely free to develop a naming system outside the IETF. And obviously any operating system can implement a name switch function that decides what names should be resolved by which naming system. However, having lived through a period where many different naming systems where use in parallel and seeing what benefits it brought to have to consider just DNS, I think a model where IETF and ICANN actively control the consistency of the internet name space is best. And with actively control I mean that any changes get planned and then designed. And obviously this planning and designing should happen within the IETF when it comes to new protocols. I have created naming systems myself. And there are many reasons to dislike DNS and do something different. But ultimately, for the stability of the internet, it is best to not do that. Write some experimental code, write a few papers and be done with it. Then, if you still care about the problem, work within the IETF to improve DNS. _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
