chairs were waiting
> for
> a revision before starting a call for adoption. That revision took a few
> months
> but it has been done and DNSOP is ready to start a call for adoption.
>
> This draft addresess the bug found in the existing RFC.
>
> This starts a Call for Adopti
On Wed, Apr 11, 2018 at 8:55 AM, Joe Abley wrote:
> Hi Bob,
>
> On Apr 11, 2018, at 08:50, Bob Harold wrote:
>
> > In various places, like 4.3. TSIG Record Format, "resolver and server"
> is used which seems a little vague to me, since I use TSIG between
Hi Bob,
On Apr 11, 2018, at 08:50, Bob Harold wrote:
> In various places, like 4.3. TSIG Record Format, "resolver and server" is
> used which seems a little vague to me, since I use TSIG between master and
> slave authoritative servers, neither of which is a resolver.
all for adoption. That revision took a few
> > months
> > but it has been done and DNSOP is ready to start a call for adoption.
> >
> > This draft addresess the bug found in the existing RFC.
> >
> > This starts a Call for Adoption for draft-dupont-dnsop-rfc2845b
dy to start a call for adoption.
>
> This draft addresess the bug found in the existing RFC.
>
> This starts a Call for Adoption for draft-dupont-dnsop-rfc2845bis
>
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-dupont-dnsop-rfc2845bis/
>
>
a Call for Adoption for draft-dupont-dnsop-rfc2845bis
The draft is available here:
https://datatracker.ietf.org/doc/draft-dupont-dnsop-rfc2845bis/
Please review this draft to see if you think it is suitable for adoption
by DNSOP, and comments to the list, clearly stating your view.
Please also