On Thu, Nov 28, 2019 at 2:52 PM Doug Barton <[email protected]> wrote:
> On 11/28/19 2:20 PM, Joe Abley wrote: > > > - has the advice to anchor a private namespace in a registered domain in > > the private namespace really been received and judged to be > > insufficient? > > Yes. > > > Or has it just not been received? Could such advice be > > delivered in a more effective way? > > The market has rejected this advice. I could bore you with examples and > reasoning, but I have never worked with a client in an enterprise larger > than a taco stand that didn't have at least one private domains set up. > > I don't think anyone doubts that you have tons of experience with lots of customers. However, there are very important differences between anecdotes and proper statistical studies. There are any number of reasons for why those might differ in meaningful ways. There could be populations which, for whatever reason, don't overlap with your set of clients, with different characteristics. There could be an inherent selection bias, in how your clients choose you or how you find your clients. Certainly, the size of your client set, is not very likely to be anywhere near large enough to be statistically significant, compared to the number of domain registrants worldwide (hundreds of millions). What folks are trying to say is, in order to build rough consensus, which is how the IETF works, it helps to have something (anything) to support your assertions, preferably something that can be easily confirmed ([citation needed]). And, does the use case you are concerned with, actually need to be at the TLD level? Would something like "internal.zz" not be just as suitable, assuming you concur with the ".zz" usability? (Substitute arpa for zz if you prefer.) Brian
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
