Re: [DNSOP] I-D Action: draft-ietf-dnsop-alt-tld-05.txt

On Sun, Sep 25, 2016 at 12:25 PM, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
> On Mon, Sep 12, 2016 at 04:57:05AM -0700,
>  internet-drafts@ietf.org <internet-drafts@ietf.org> wrote
>  a message of 48 lines which said:
>
>>         Title           : The ALT Special Use Top Level Domain
>>         Authors         : Warren Kumari
>>                           Andrew Sullivan
>>       Filename        : draft-ietf-dnsop-alt-tld-05.txt
>
> The previous versions were, and I think it was good, carefully
> non-normative. .ALT was presented (as it should) as a MAY, not a MUST
> or a SHOULD. Now, sentences like "This document provides a solution
> that may, in many cases, be more appropriate than [RFC6761]." are,
> IMHO, too much. I suggest "This document provides, in some cases, an
> alternative solution to [RFC6761]"

I'm fine with that[0]. Please keep in mind that this document has been
around since early 2014, and has gone through many revisions (11, 6 as
an individual, and 5 as a WG doc). Since 2015-11-17 it has been a
"Parked WG Document" ("Waiting for the 6761 design team to sort out
the bigger issues before moving this forward.").
It was started before there had been much discussion on the Special
Use Names problems (draft-adpkja-dnsop-special-names-problem and
draft-tldr-sutld-ps were not even twinkles in the author's eyes), and
so it contains much background and discussions which may no longer be
needed - I've been told that this will finally be unparked as soon as
a decision is made on the problem statement, and we'll be happy to
revise it then.

>
> Also, disparaging terms like "pseudo-TLD" should be avoided. "Non-DNS
> TLD" is sufficient.

"pseudo-TLD" was in no way intended to be disparaging -- we had
defined it as "A label that appears in a fully-qualified domain name
in the position of a TLD, but which is not registered in the global
DNS.". Again, this was started in 2014 - there hadn't been much
discussion at this point. I really don't like "Non-DNS TLD", but I
also don't really like "pseudo-TLD" -- once we are allowed to make
proper edits to it again we'll happily put in whatever the WG wants --
and, suggestions welcome....

>
>> This label is intended to be used as the final (rightmost) label
>
> No. It is rightmost only in LTR scripts. "final" is correct,
> "rightmost" isn't. Please delete it.
>
>> For example, a group wishing to create a namespace for Friends Of
>> Olaf might choose the string "foo"
>
> If this namespace uses a non-DNS protocol for resolution, it may be
> case-sensitive and therefore it should be "FoO". (Yes, this was a
> troll.)

... was it? It raises an interesting point - seeing as alternate
resolution contexts are likely to want to have their names be able to
be used anywhere where a "traditional" DNS names is used, they will
likely also be (ASCII) case insensitive, because some apps likely
flatten case before handing to a resolver system. But, this seems like
a decision that the resolution system designed could make - perhaps it
is worth mentioning (again, once unparked) in the doc.
foo.alt MAY be different to foO.alt... perhaps....

Anyway, I'm really trying to stay away from solution discussions until
a problem statement is adopted....

W
[0]: We had been asked to put in the original text, but we will (of
course) do whatever the WG wants.

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

-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf