The .TEL Community on the .TEL Domain Forum!

Welcome to the Tel.community.

You are invited to participate in the growing .tel
community!

To take full advantage of everything offered by
our forum, please log in if you are already a
member or join our community if you're not yet.

The registration at TelTalk.org is free and easy!

Thank you for participation!

Join the forum, it's quick and easy

The .TEL Community on the .TEL Domain Forum!

Welcome to the Tel.community.

You are invited to participate in the growing .tel
community!

To take full advantage of everything offered by
our forum, please log in if you are already a
member or join our community if you're not yet.

The registration at TelTalk.org is free and easy!

Thank you for participation!

The .TEL Community on the .TEL Domain Forum!

Would you like to react to this message? Create an account in a few clicks or log in to continue.
The .TEL Community on the .TEL Domain Forum!

Welcome to the objective forum for .tel domains! Read it first when anything is happening with .tel!

Please join the LIVE CHAT for all REGISTERED members at the bottom of our forum!

    DNS Privacy, Authorization, Special Uses, Encoding, Characters, Matching, and Root Structure: Time for Another Look?

    MWX
    MWX
    Senior Member
    Senior Member


    Join date : 2013-07-17
    Posts : 219 Points : 8740
    Reputation : 80
    Warning level : 100 %

    DNS Privacy, Authorization, Special Uses, Encoding, Characters, Matching, and Root Structure: Time for Another Look? Empty DNS Privacy, Authorization, Special Uses, Encoding, Characters, Matching, and Root Structure: Time for Another Look?

    Post by MWX 2018-03-22, 5:15 am

    The basic design of the Domain Name System was completed almost 30 years ago. The last half of that period has been characterized by significant changes in requirements and expectations, some of which either require changes to how the DNS is used or can be accommodated only poorly or not at all. This document asks the question of whether it is time to either redesign and replace the DNS to match contemporary 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 should be performed in some other way.
    https://www.rfc-editor.org/info/rfc8324

    Full memo by John Klensin: https://www.rfc-editor.org/rfc/pdfrfc/rfc8324.txt.pdf

      Current date/time is 2024-04-29, 10:36 am