Olafur Gudmundsson writes: > Strictly speaking the draft was never formally submitted via IANA.
This is part of the problem with documentation. At least one natural entry point for the process, the IANA assignments page, doesn't indicate how to initiate expert review. https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-11 It does link to RFC 6891 and to RFC 3604 Errata, but that's poor usability even if those documents described how to initiate review, which they don't. > As expert I do not have any formal guidelines to tell me how to > judge options. My rule after implementing ClientSubnet is $,1r|(Bnever > again$,1r}(B allow complex type. Agreed that you have poor guidance, the closest thing is from the RFCs mentioned above, which only says: "Assignment of Option Codes should be liberal, but duplicate functionality is to be avoided." I grant that there is reason for pause because both Nominum and OpenDNS have squatted code points which have duplicate functionality. There is a larger philosophical discussion that should be had about this, though, given that it seems to encourage just totally circumventing IETF/IANA. It is ironic to me that I was trying to do the right thing, yet the process which is supposed to have made getting option code assignments easier and not require action by the working group has seemingly failed at that task. The feeling of failure is exacerbated by not being able to have expectations properly set by documentation other than "be liberal". As for whether this is a complex type, that's a whole separate discussion to have if the draft itself gets more discussion. Mostly here in this message I'm focused on process. > As Expert I do not want to write the rules for myself :-) > I will be happy to comment on any suggested rules/advise. Fair enough. Anyone else interested in working on better guidance? To be clear, I'm totally okay if the result of that is something that would have still resulted in an initial denial for this option assignment under Expert Review. It's the process I want to see improved.
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
