Re: Bind 9 AXFR Modification vs AXFR Clarification

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

 



Interesting. So, they knew that standardization was necessary, the
proposed a standard, the standard wasn't accepted, so they distributed
code to users anyway, and wrote a book anyway.

I find that even more worthy of criticism.

Did they think they would force this through later? Never mind, it doesn't
matter what they thought.

As this "clarify" seems to have been dead for years, we should get on with
the business of clarifying AXFR as it was commonly interpreted. And lets
get on with the MAXFR proposal.

		--Dean

On Fri, 21 Feb 2003, Erik Nordmark wrote:

> > Apparently, you aren't even aware that your changes will make all non-bind
> > 9 servers non-compliant.  Had you been aware of that, it seems you would
> > have brought this proposal forward something like 3 years ago, before
> > releasing Bind 9, and before publishing a book on the subject.
>
> A data point.
>
> http://www.ietf.org/proceedings/00jul/I-D/dnsext-axfr-clarify-00.txt
> INTERNET-DRAFT                                      Andreas Gustafsson
> draft-ietf-dnsext-axfr-clarify-00.txt                     Nominum Inc.
>                                                             March 2000
> Seems to be 3 years ago.
>
>   Erik
>
>





[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]