-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 07/09/2015 12:53 PM, Alain Durand wrote: >
I don't think I can make it to Prague, > Here is a short list: > > - RFC6761 does not say anything wrt to coordination between IETF and I CANN > on this topic. > How did the RFC6761 reservations happen? Clarifying this process should be helpful to determine this coordination. > - RFC6761 talks about names, not TLDs. i.e. It could be use to reserve > a name under any existing TLD. Granted, this should be clarified as in: a new, inexistent TLD and/or sub-domains within this TLD. I must say I can't decide if there's a use-case for IETF to declare a sub-domain special under an existing TLD that is already delegated by IANA. My brains explodes and shows "MESS" warnings. > - RFC6761 does not say much about how to evaluate the merits of > proposals. That made the discussion on the current crop of > candidates difficult. > I would not expect an amended RFC6761 to go much beyond what's already in section 5. Using quantitative criteria is prone to error and imprecision and could well prevent a legitimate technology from growing: we already know that .alt will not solve the issue of globally-operative-name-spaces that are not suited for DNS (which is why I proposed an informational RFC for P2PNames). Nevertheless this global uniqueness of names could become a criterium, since the alternative would be covered by .alt. > I'm sure there are more issues. > - - RFC6761 does not clearly define the scope of each point in section 5. Judging from the variety of responses to the first point about "Users" and the overlap with "Application Software" on the one hand, and between "Application Software" and "Name Resolution APIs and Libraries" on the other hand, this should be clarified. The fact that the current .onion draft needs to mention "Applications (including proxies)" is symptomatic . - From my reading: 1. Users are humans-in-front-of-Application-Software 2. Application Software is a program-used-by-Users-or-other-programs 3. Name Resolution APIs and Libraries are specialized parts of a system that are concerned exclusively with *DNS* resolution, that can run inside of an Application Software (library) or independently from it (API). 4. to .7 are self-explanatory. Regards, == hk -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJVnsD9XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQ0IyNkIyRTNDNzEyMTc2OUEzNEM4ODU0 ODA2QzM2M0ZDMTg5ODNEAAoJEEgGw2P8GJg9D+EP/2o5io+Grwh1jttnDcN0NVes o+Fbo01Gpe+EX2P92tIHLVsN5yPJnHJU7Y2WQy/1l8BWrJtez3fcqMPlGeD6cwTJ xppx8FK7dLG1IWYRAmuUJNPOwPPJKaGQBqApll/mp+6BG/0Z37obOL5PspS1Fn/8 fe3L9IauVyrxEpOjqIUpo5U0/stJAbnri2vBJqmqLb/fMD9zvYIrWjCnnXuw6Vch 4LnvUEVX1agLEMnK6/6vNhuL/Zo3KZqyjn0olQShk5jM0EaBZkgcnVQ0VhyCO1F9 9lQt5Noi0oQYI2SVXc3HbQ8ob9C+by9X5X3BH2Ovx4A1Bcv23taE76fhayfOvSVi xJuzpdEmD/VF23qeZB+HiReeRvRDpUNLhyKdpyc7wgsr0w7d1iJJ6xRfm2BsXbko MEKOMOwfZxasqXVgzkEAA6jQ9O+zpSQmbcN0DSD71cIALpILk3qDKBby7kNj0L70 6xUM5mir3Ul7uRNk5dm+1DCdaDw6cAs1S6aWwtd2+BMgGrovd7U+6ApWAFv4aRM2 Ac+pSGzNWikIW9VOnaR+O/GpJAFuQ97PCqLGfaGPAWLZTOLdHqH+prXSVkweRbdt KBEckK97dtvBTlhzflMTqUjZR4TZQ9mw4jj9koU+rgjdZ8qjlFDS2XiHKyVE22Tb ntzRChorFIyluvPd6xER =qmQs -----END PGP SIGNATURE----- _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
