I won't be on the call, but I think one question might be good to add:

"Why are the requirements described in the draft better than
centralization?"

It seems good that resolver traffic patterns are being questioned, but I
had this thought in the back of my mind.

thanks,
Rob


On Mon, Oct 28, 2019 at 3:24 AM Alexander Mayrhofer <
[email protected]> wrote:

> I've just posted the -00 individual submission version:
>
> https://tools.ietf.org/id/draft-lmo-dprive-phase2-requirements-00.txt
>
> Sorry for the delay, but i hope that people still have some time to
> look through that draft.
>
> best,
> Alex
>
> On Fri, Oct 25, 2019 at 8:59 PM Livingood, Jason
> <[email protected]> wrote:
> >
> > I just submitted my final changes to Benno and Alex and put the ball in
> their court to send something over the weekend or on Monday morning in
> Austria or the Netherlands. It is a very early -00 and so intended to
> mostly spur WG discussion.
> >
> > Jason
> >
> > On 10/25/19, 11:05 AM, "dns-privacy on behalf of Brian Haberman" <
> [email protected] on behalf of [email protected]> wrote:
> >
> >     Hi Paul,
> >
> >     On 10/25/19 10:27 AM, Paul Hoffman wrote:
> >     > On 10/25/19 6:25 AM, Brian Haberman wrote:
> >     >>
> https://datatracker.ietf.org/doc/agenda-interim-2019-dprive-01-dprive-01/
> >     >>
> >     >> On 9/25/19 10:45 AM, Brian Haberman wrote:
> >     >>> All,
> >     >>>       We are going to hold a DPRIVE virtual interim meeting on
> Oct. 29th
> >     >>> at 4:00pm CET / 11:00am EDT / 8:00am PDT. The three agenda items
> are:
> >     >>>
> >     >>> - Review updates to the BCP based on WGLC comments,
> >     >>> - Review updates to 7626bis based on WGLC comments,
> >     >>> - Discuss recursive-to-authoritative requirements (-00 draft
> forthcoming).
> >     >
> >     > Will we be able to review the forthcoming
> recursive-to-authoritative requirements draft before the interim meeting?
> >
> >     I have asked the authors to post either a -00 draft or a doc on
> GitHub
> >     before the interim.
> >
> >     Brian
> >
> >
> >
> > _______________________________________________
> > dns-privacy mailing list
> > [email protected]
> > https://www.ietf.org/mailman/listinfo/dns-privacy
>
> _______________________________________________
> dns-privacy mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/dns-privacy
>
_______________________________________________
dns-privacy mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dns-privacy

Reply via email to