-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- I talk of real world when you talk of the current (unsecure and
overloaded?) implementation of the current DNS architecture.
In what way overloaded? Do you have any pointers? Proof? Data?
The problem we face is an old and too large unique system with a
robust yet overloaded engine. With all the problems which come with
it. We have to split the zones of usage and risks. Either it is
planned by IETF or it is done by the users. I suggest it is done
together.
Again, overloaded engine in what way?
Then the agreed file
Agreed by whom? In what way?
You want to reduce the calls to your system, right? Let stop the
"cache" idea which is something of _your_ system ibn theirs, and
propose them an update of _their_ system - like anti-virus updates
(ever heard that anti-virus run huge 50x1G systems? And let discover
what a user system can bring more to its user owner. So when the user
has started using and enjoying _his_ system, you will obtain what you
want.
Why would I want to reduce the number of calls on my system? My system
is doing just fine...
- - kurtis -
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
iQA/AwUBQKuHjqarNKXTPFCVEQJbDQCbBgjOmqDeK5bjzlbzlCVwB+XtkrIAoIpu
7V0w8Yq6Q6qxIKy1XRwtfHuX
=863T
-----END PGP SIGNATURE-----
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf