Re: [stir] current draft charter

[Hadriel Kaplan <[e-mail]>]

On Jun 13, 2013, at 10:08 AM, Brian Rosen <[e-mail]> wrote:

> So, my response is the same as I have given before: the privacy and operational issues of putting per TN information in the public DNS are overwhelming.  We have tried it, and it has failed.

The privacy issues can be avoided.

The operational issues, however, are quite significant.  But I don't see how they're not significant no matter what databases we put them in.  No matter whether it's a private database or public one: there will be new operational procedures, forms to fill out, help desk people to handle problems with it, configuration and deployment of stuff, NOC personnel to train, testing to do, monitoring systems to monitor it, etc., etc.

In short: it's a very big deal.

Luckily history has shown that some third-party service companies will make themselves available to do most of the work for carriers that don't want to do it themselves, for a fee.  It might be the number portability vendors, or CNAM vendors, or something new.  Either way, they can handle most of the heavy lifting for carriers who don't want to.  If we choose a DNS model, then those third-party vendors would then interface to the DNS admin; or maybe they start with a private federation of servers just among the third-party companies.

The reason Public ENUM failed wasn't because it was an operational nightmare - if Public ENUM had some actual useful benefit to the stakeholders, then all other issues would have gone away or been dealt with.  I.e., if the carriers *want* something, then they figure out how to get it done, how to lobby their Regulators, and how to get the ITU to go along.  If they don't want it, then every possible issue that can be raised becomes "impossible to fix".  And I'm not saying that's wrong either. (and everyone does the same thing in the IETF, regularly)


> Unlike Hadriel, you really do want to disclose domain with TN.  That has been a non-starter for many carriers.

In my defense, it's not that *I* don't want to disclose the domain of the TN - I'd be perfectly happy with it - it's that I'm pretty sure a lot of providers AND Enterprises would not, if it means you can discover all the TNs belonging to the domain.  And you don't need to go very far to find evidence of that: how many companies want to publicly disclose all their users' email addresses?  Of my current and half-dozen previous employers, none would want them exposed.

-hadriel