Dear wg,

We published today a new version of draft-adpkja-dnsop-special-names-problem. 
The draft has been simplified even further in an attempt to make it more 
readable.
Also, the abstract clarifies that this document is a problem statement about 
issues around RFC6761 and not a problem statement around the larger set of 
issues of special use names.

See new abstract:

Abstract

   The dominant protocol for name resolution on the Internet is the
   Domain Name System (DNS).  However, other protocols exist that are
   fundamentally different from the DNS, and may or may not share the
   same namespace.

   When an end-user triggers resolution of a name on a system that
   supports multiple, different protocols or resolution mechanisms, it
   is desirable that the protocol used is unambiguous, and that requests
   intended for one protocol are not inadvertently answered using
   another protocol.

   RFC 6761 introduced a framework by which a particular domain name
   could be acknowledged as being special.  Various challenges have
   become apparent with this application of the guidance provided in RFC
   6761.  This document focuses solely on documenting the specific
   challenges created by RFC 6761 in the form of a problem statement in
   order to facilitate further discussions of potential solutions.  In
   particular, it refrains from proposing or promoting any solution.
   Also, the current document does not focus on other general issues
   related to the use of special use domain names.


URL:            
https://www.ietf.org/internet-drafts/draft-adpkja-dnsop-special-names-problem-06.txt


Alain, on behalf of the other authors.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to