,
я был в полном шоке вчера... когда я...
совершенно случайно ... напоролся вот на это... >
https://tools.ietf.org/html/rfc8324 < ...
,
differences between the DNS architecture , and ,
the requirements that imply those proposals , suggest that ,
it may be time , to stop patching the ,
poor and old , DNS , or trying to extend it in small increments
instead we , SHOULD FREAKING BE , considering , moving some current or proposed functionality elsewhere
or developing ,
a new system instead of DNS , that better meets ,
todays needsand a transition strategy to it
efforts to use , very short or zero
refresh times , ( very short or zero
TTLs ) ...
inside an SOA record ...
for multiple caches in other recursive DNS serversto simulate ,
nearly simultaneous updating ...
may work up to a pointbut appear to impose ,
very heavy loads , on servers and distribution mechanisms
that ,
were not designed , to accommodate that style of working
several people have pointed out that , if we were designing a ,
next generation DNS ...
using todays technologyit just , SHOULD FREAKING BE , possible to ,
remove the technical requirement , for a ,
central authority over the DNS rootsome people have suggested that ,
blockchain approaches , would be helpful for this purpose
others believe ,
blockchain approaches just would not scale , adequately
but ,
other options instead of blockchain approaches , are possible for a ,
next generation DNSthe basic design of the DNS , was completed ,
almost 31 years ago , the last half of that period has been characterized by ,
significant changes in requirements and expectationssome of which ,
either require changes to how the DNS is used , or ,
can be accommodated only poorly , or ,
not accommodated at allthis document ,
asks the question of , whether it is time to ,
either redesign and replace the DNS , to match ,
todays requirements and expectations( rather than continuing to ,
try to design and implement incremental patches , that ,
are not fully satisfactory )
or , draw some clear lines about ,
functionality that is not really needed , or ,
that functionality , SHOULD FREAKING BE ,
performed in some other way,