On May 14, 2015, at 8:13 AM, <[email protected]> <[email protected]> wrote: > > For our residential customers, should we be expected to delegate > lots of reverse zones that mostly wouldn't be populated? I can easily > see how this could lead to extra calls to customer support, extra > logging of failures on name servers, etc. In short, most likely extra > cost. Since residential service is a very low margin game, anything > which adds to the cost of providing the service is a non-starter. Not > gonna happen.
It has to be automatically negotiated or it won't work. On a practical level there is significant work to do here; the question is, if we can make it cheap to manage, is it technically the right thing to do. IMHO it is. Bear in mind that there is no cheap path. If you don't populate the zone with fake crap, which imho you should not, you might get calls. If you populate it with crap, you will see a significant cost, because that is not easy. If you delegate, that may produce calls from folks who don't ask for the delegation, and from folks who do. I think the best early experiment is to do nothing and see how that goes. As a data point, this is what Comcast is currently doing with my delegated prefix. I'd be curious to know if they are getting phone calls about this. _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
