On 3 Apr 2017, at 18:02, George Michaelson wrote:
The only reference to ICANN delegation process is in an [Ed: note] which feels to me to be wrong: its a first class issue, and should be addressed directly, not as editorial.
The note says why the ICANN delegation process is *not* used. As the Abstract says, these notes will be removed before publication.
Secondly, The authors make a judgement call in this block that they feel requesting delegation is not required. I don't feel the consensus was that strong actually, but you know, I guess I could be wrong on that.
This is what WG Last Call is for. If you want to reverse what's in the current draft, you need to say so explicitly, hopefully providing text so that this WG doesn't end up with the sloppy text that the HOMENET WG got.
FWIW, I thought that the authors got this version right. The discussion didn't converge on strong use cases for delegation, and there were strong reasons against. But this is a fair time to open that again.
Thirdly the draft contains no language which actually explains why a TLD is required, rather than a deterministic string which denotes 'not in the DNS' -It may be blindingly obvious to you it has to be a TLD, but given that the entry of DNS label-strings into the DNS is through software, and given that at some point, the simple un-parsed string 'something.alt' has to be presented, I would have expected an explanation why 'alt.arpa' as a pattern match in the DNS entry can't work as well as 'alt'. Bear in mind, that the argumentative text states .ONION is a comparator, so poses the problem back on (future) s/w authors that currently seek a TLD as a pattern match, and now have to code to ONION.ALT as a pattern match (the match on ALT implies parsing it off, to denote ONION as a non-DNS label, or embedding of ALT in the non-DNS namespace) so the dots-parsing problem exists for the s/w owners *come what may*
If you have such proposed text, that would be useful to evaluate.
Lastly, I think the IAB note pretty strongly goes to 'we dont do that any more'
Please define "that". If you mean "using TLDs that are not delegated", please show in the IAB statement where you get that impression. I didn't see it, but that doesn't mean it isn't there.
and I think the draft at the bare minimum should say why this draft is special, against that letter. You make a compelling and simple case: because its specifically NOT-DNS, not public DNS, its not relevant. Ok, then say so. 'we didn't say so because it wasn't relevant' feels pretty weak to me. I can do this as a nit in the GIT if you prefer.
What you are proposing is not a "nit", but a fundamental change throughout the document.
--Paul Hoffman _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
