Hi Patrik, Jim, folks, +1 Not an IETF thing, but ISTR that the RRR model can make pushing error reports difficult: e.g., if Registry runs tests and finds problems, the Registrar may be unhappy for an email to be sent from Registry direct to "the Registrar's" customer.
Quite apart from anything else, do delegated domain DNS validity checks figure within gTLDs? If not, then any USE of such a BCP is going to go to ICANN (and take years and years and ...), no? ISTM that the IETF isn't in a position to force its suggestions through the 'industry'. all the best, Lawrence On 11 Nov 2015, at 06:25, Patrik Fältström <p...@frobbit.se> wrote: > On 10 Nov 2015, at 22:24, Jim Reid wrote: > >>> Or perhaps we should not. >> >> +1 > > This discussion on making tests is coming back now and then. In RIPE, in > IETF, in discussions around TLDs (specifically ccTLDs). > > I have run one such initiative myself. > > Everything has so far collapsed into collision between tech people not > agreeing on what is right and wrong. It also collapses into clashes between > registry policy and the tests made. I.e. just the registration policy is > setting blocks and constraints on what tests must be made (or can not be > made). And harmonization of such rules is just impossible (we have seen). > > That said, initiatives like the one I did run did push errors (for some > definition of errors) from 22% to maybe 17% in .SE and my inspection of the > rest say that getting errors down to 15% is possible, but more is very hard. > > And, having a BCP or such that give suggestions on what can be viewed as > "correct" would not be bad, but how to use it must be up to the reader. > > I think the IETF should be careful on writing too prescriptive text, I say > being one hit by "rfc compliance" people that point at old whois related RFCs > that "require" things that in fact is illegal in Sweden. I.e. by being > compliant to Swedish law regarding privacy, I violate a very old RFC and > because of that I am black listed. > > So be careful. > > Patrik _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
