Re: [DNSOP] Call for Adoption: draft-bortzmeyer-rfc7816bis

2018-09-15 Thread Stephane Bortzmeyer
On Thu, Aug 09, 2018 at 04:49:18AM -0400, Tim Wicinski wrote a message of 21 lines which said: > Authors should upload a new version with the draft-ietf-dnsop-rfc7816bis  > name. Done (with a delay, sorry, I'm responsible). DNS Query Name Minimisation to Improve Privacy

Re: [DNSOP] Call for Adoption: draft-bortzmeyer-rfc7816bis

2018-08-09 Thread Tim Wicinski
All Thanks for all the comments on this draft.  The Call for Adoption is ending today but it seems that there is consensus to adopt this work in DNSOP and support this work.   The chairs thank everyone for the feedback. Authors should upload a new version with the

Re: [DNSOP] Call for Adoption: draft-bortzmeyer-rfc7816bis

2018-08-04 Thread A. Schulze
Am 24.07.2018 um 18:32 schrieb Tim Wicinski: > This starts a Call for Adoption for draft-bortzmeyer-rfc7816bis Hello WG, I do support QNAME minimisation. As some may know, we operate a medium size enterprise and ISP network. There we use UNBOUND as recursive resolver. QNAME minimisation is

Re: [DNSOP] Call for Adoption: draft-bortzmeyer-rfc7816bis

2018-08-03 Thread Sara Dickinson
rg <mailto:dnsop-boun...@ietf.org>] 代表 > Tim Wicinski > 发送时间: 2018年7月25日 0:33 > 收件人: dnsop > 主题: [DNSOP] Call for Adoption: draft-bortzmeyer-rfc7816bis > > > We discussed this and there appears to be support to adopt this, with > the caveat of addi

Re: [DNSOP] Call for Adoption: draft-bortzmeyer-rfc7816bis

2018-08-01 Thread 神明達哉
On Tue, Jul 24, 2018 at 9:33 AM Tim Wicinski wrote: >This starts a Call for Adoption for draft-bortzmeyer-rfc7816bis >The draft is available here: https://datatracker.ietf.org/doc/draft-bortzmeyer-rfc7816bis/ >Please review this draft to see if you think it is suitable for adoption

Re: [DNSOP] Call for Adoption: draft-bortzmeyer-rfc7816bis

2018-07-26 Thread Shumon Huque
On Fri, Jul 27, 2018 at 12:08 AM manu tman wrote: > On Tue, Jul 24, 2018 at 9:32 AM Tim Wicinski wrote: > >> >> We discussed this and there appears to be support to adopt this, with >> the caveat of adding more content to the section on Operational >> Considerations. >> >> >> This starts a Call

Re: [DNSOP] Call for Adoption: draft-bortzmeyer-rfc7816bis

2018-07-25 Thread Paul Ebersman
tjw> We discussed this and there appears to be support to adopt this, tjw> with the caveat of adding more content to the section on tjw> Operational Considerations. [...] tjw> Please review this draft to see if you think it is suitable for tjw> adoption by DNSOP, and comments to the list,

Re: [DNSOP] Call for Adoption: draft-bortzmeyer-rfc7816bis

2018-07-25 Thread Petr Špaček
On 24.7.2018 18:32, Tim Wicinski wrote: > > We discussed this and there appears to be support to adopt this, with > the caveat of adding more content to the section on Operational > Considerations. > > > This starts a Call for Adoption for draft-bortzmeyer-rfc7816bis > > The draft is

Re: [DNSOP] Call for Adoption: draft-bortzmeyer-rfc7816bis

2018-07-24 Thread Paul Wouters
On Tue, 24 Jul 2018, Tim Wicinski wrote: We discussed this and there appears to be support to adopt this, with the caveat of adding more content to the section on Operational Considerations. This starts a Call for Adoption for draft-bortzmeyer-rfc7816bis The draft is available here:

[DNSOP] Call for Adoption: draft-bortzmeyer-rfc7816bis

2018-07-24 Thread Tim Wicinski
We discussed this and there appears to be support to adopt this, with the caveat of adding more content to the section on Operational Considerations. This starts a Call for Adoption for draft-bortzmeyer-rfc7816bis The draft is available here: