To:
"J-F C. (Jefsey) Morfin" <jefsey@club-internet.fr>, David Conrad <david.conrad@nominum.com>, Ed Sawicki <ed@alcpress.com>, Randy Bush <randy@psg.com>
Cc:
DNS Operations <dnsop@cafax.se>, namedroppers <namedroppers@ops.ietf.org>, <ngtrans@sunroof.eng.sun.com>, IPng <ipng@sunroof.eng.sun.com>
From:
Ólafur Gudmundsson/DNSEXT co-chair <ogud@ogud.com>
Date:
Thu, 18 Jul 2002 11:04:52 -0400
In-Reply-To:
<5.1.0.14.0.20020717113429.0247ca40@mail.club-internet.fr>
Sender:
owner-dnsop@cafax.se
Subject:
Re: (ngtrans) Re: RFC 1886 Interop Tests & Results
At 05:42 AM 7/17/2002, J-F C. (Jefsey) Morfin wrote:
>The frustration results from an uncompleted report. The target is to
>demonstrate that different thinking families can have the same reading of
>the specs and can develop from them compatible softwares. The bugs may
>results from unclear specs or from an early development phase. That we
>need to know.
>
>The name of the participants would only help knowing the X, Y, Z
>architectures, used libraries, concept affiliations, "style", etc.. To
>evaluate if the specs testing spectrum is significant enough. But the
>better, easiest and common way would be that each participant describes
>his approach in his own terms (so there is no confidentiality break). IMHO
>this is basic to any hidden testing protocol.
Just for the record, THIS interoperabilty test was performed without
any vendor participation, thus it is real hard for the report to
talk about approaches or reasons why.
The real important thing here is there are three implementations
that work. This enables the DNSEXT working group to advance RFC1886bis to
Draft Standard.
The fact that one implementation forces services (mail, NS, ..) to
use IPv4 transport when IPv6 transport is available,
is not critical as the information is available via explicit AAAA query.
Olafur