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

Re: in support of axfr-clarify

At 06:16 PM 11/27/02, Dean Anderson wrote:

On Wed, 27 Nov 2002, Kevin Darcy wrote:

A clarification should define the common way its done, the way it was
reasonably and commonly understood by readers the original document.

Right. However, if the original document is unclear then different
implementors will have implemented differently, resulting in interoperatibility
problems. By clarifying you necessarily make some of those implementations
non-compliant. You can't clarify without breaking something.
> > It seems highly inappropriate to make seemingly gratiutous changes in a
> > particular commercial product, begin distributing those changes to users,
> > and then attempt to change the standards to reflect the changes, and
> > describing those changes as a "clarification".
>
> I dispute that the changes are "gratuitous", that BIND is "a commercial product"

Vixie asserts a trademark on "BIND". Though I'm not convinced its really
valid, since it was in the public domain by UCB. Trademarks are only
valid if used in commerce. .: Bind is a commercial product.
That's an untrue statement. You can trademark anything without it being
a commercial product. I don't know if Paul has made any trademark claim
with repect to BIND, though it would be on behalf of ISC.



I guess "gratuitous" is rather vague. I should say that I think IXFR
should be changed instead of AXFR, and that I'm not convinced that any
protocol/semantic changes are really necessary to make this work. Rather
than accept these changes to AXFR, I think the implementors should give it
more thought.

You can't do IXFR unless AXFR is clear and unambiguous. Incremental
makes no sense without that. Are you going to negotiate the type of data
to be sent based on everyone else's different interpretation of the spec?

Danny


--
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/>