Keith Moore wrote:
[..]
I believe I understand how to replace DNS with a better protocol while
preserving the existing hierarchy and RRsets and DNSSEC, and allowing
graceful transition from the old to the new. However, I'm not sure that
I have enough understanding of DNS's failings to engineer something that
addresses all or most of them - I just know about the ones I've run
into. But I'd like to hear from other people who are interested in
replacing DNS, maybe we could collaborate on a proposal that shows how
DNS could be improved and how replacement of DNS is feasible.
Might I suggest that you first start doing what most sensible people
have been doing over the long long years of human existence:
- define your problem
- define what you want to solve
- define for what you want to solve it
And then after that is all done, realize that the problem you have is
very difficult.
The IETF has a simple process for all of this: write a draft.
And the alternative process is: build running code.
But afaik you already know about this. Bickering about all this is fun
of course, but it doesn't help coming to a solution, especially as the
solution doesn't have a defined problem set and what it is supposed to
solve.
Greets,
Jeroen
signature.asc
Description: OpenPGP digital signature
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf