From: "Woodworth, John R" <John.Woodworth@CenturyLink.com>
To: "'Stephane Bortzmeyer'" <bortzmeyer@nic.fr>
CC: "dnsop@ietf.org" <dnsop@ietf.org>, "Woodworth, John R"
 <John.Woodworth@CenturyLink.com>
Thread-Topic: Kindly review draft-woodworth-bulk-rr-05.txt
Thread-Index: AQHSh3MZ+ZDvSwGOnkOBz2+cOwa2X6GrAQ+A//+wojA=
Date: Tue, 28 Mar 2017 16:44:42 +0000
Message-ID: <A05B583C828C614EBAD1DA920D92866BD0717655@PODCWMBXEX501.ctl.intranet>
References: <A05B583C828C614EBAD1DA920D92866BD06DCF82@PODCWMBXEX501.ctl.intranet>
 <20170328161217.GA24741@laperouse.bortzmeyer.org>
In-Reply-To: <20170328161217.GA24741@laperouse.bortzmeyer.org>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/0uZKzlUjVLzm0Db3-zLc3Ym6Nps>
Subject: Re: [DNSOP] Kindly review draft-woodworth-bulk-rr-05.txt
Precedence: list

> -----Original Message-----
> From: Stephane Bortzmeyer [mailto:bortzmeyer@nic.fr]
>
> On Wed, Feb 15, 2017 at 10:33:50AM +0000,  Woodworth, John R <John.Woodwo=
rth@CenturyLink.com> wrote  a message of 121 lines which said:
>
> > We welcome _any_ feedback on the draft as we are hoping to have
> > it (or some incarnation) adopted by the WG soon and look to rally
> > more interest around it.
>
> > Q) Does BULK cover all RR types?
> > A) No. The draft only covers A, AAAA, PTR and CNAME RR types.
>
> Unless I'm wrong, draft-woodworth-bulk-rr-05.txt does not explain
> what to do if the QTYPE=3DANY. (Section 3.2 seems to indicate that it wil=
l
> *not* match even if there are A or AAAA records.)
>

Stephane,

First, thanks for your feedback it is very appreciated.

We attempted to handle this implicitly in section 3 --

    "The nameserver MUST query its local RR database for any "BULK"
    RRs with a matching owner, class and compatible Match Type."

However, I see now it may be better to make logic for the "ANY"
QTYPE more explicit.


BTW: We are working to remove the current QTYPE restrictions in the
next draft.

>
> Also, as I said at the mike, the part about NPN is really difficult
> to understand. The pseudo-code is much better. A high-level presentation
> of NPN would be a good idea (and a separate draft for NPN).
>

Thanks again, we will revisit this section to provide better clarity
and potentially break it into its own draft.


Thanks,
John

>
> Anyone willing to do a hackathon project in Prague on implementing BULK
> on NSD?
>
>
-- THESE ARE THE DROIDS TO WHOM I REFER:
This communication is the property of CenturyLink and may contain confident=
ial or privileged information. Unauthorized use of this communication is st=
rictly prohibited and may be unlawful. If you have received this communicat=
ion in error, please immediately notify the sender by reply e-mail and dest=
roy all copies of the communication and any attachments.