[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: in support of axfr-clarify



[ post by non-subscriber.  with the massive amount of spam, it is easy to miss
  and therefore delete posts by non-subscribers.  your subscription address is
  54830374684695-namedroppers@sublist.cr.yp.to, please post from it or, if you
  wish to regularly post from an address that is not subscribed to this
  mailing list, send a message to namedroppers-owner@ops.ietf.org and ask to
  have the alternate address added to the list of addresses from which
  submissions are automatically accepted. ]

Danny ``I am not and never have been an employee of ... Nominum'' Mayer,
who in other forums has identified himself as a Senior Software Engineer
at Nominum, also known as danny.mayer@nominum.com, writes:
> Noone said anything about failures. The discussion is about consistency.

So you're demanding that an implementation decision be prohibited simply
because it's different from a decision in your implementation---even
though you admit that it interoperates just fine.

Even if you don't understand how ridiculous this demand is, surely you
can understand that it violates section 6 of RFC 2119.

> whatever you do will result in someone being in nonconformance with
> the proposed spec.

That's blatantly incorrect. I already gave you an obvious example of a
useful clarification that wouldn't declare current practice to be
non-compliant. The only reason for a clarification to make such a
declaration is when there's an interoperability problem---a conflict
between implementations that has to be fixed by one side or the other.

> I have no financial interests in BIND

Liar. Is your pretense of independence part of the BIND company's
strategy for packing this standards committee, or have other BIND
company people been quietly warning you that you should fess up?

---D. J. Bernstein, Associate Professor, Department of Mathematics,
Statistics, and Computer Science, University of Illinois at Chicago



--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>