Re: [DNSOP] "flagday" again, was Re: Wrapping up draft-ietf-dnsop-dns-tcp-requirements

2019-07-02 Thread Paul Wouters
On Wed, 3 Jul 2019, Mark Andrews wrote: Defeating fragmentation attacks requires more than a BCP. https://tools.ietf.org/html/draft-andrews-dnsop-defeat-frag-attack-00 Sure, so you have an RFC already then. great. No need for a flag day event reference, as you will have a proper RFC

Re: [DNSOP] "flagday" again, was Re: Wrapping up draft-ietf-dnsop-dns-tcp-requirements

2019-07-02 Thread Töma Gavrichenkov
Peace, On Wed, Jul 3, 2019, 7:17 AM Paul Wouters wrote: > On Wed, 3 Jul 2019, Mark Andrews wrote: > > The DNS 2019 not only had ON THE DAY changes (thanks to Google changing > > their 8.8.8.8 service on the day) > > So even pumping up the hype didn't actually help inform the people that >

Re: [DNSOP] "flagday" again, was Re: Wrapping up draft-ietf-dnsop-dns-tcp-requirements

2019-07-02 Thread Mark Andrews
> On 3 Jul 2019, at 2:16 pm, Paul Wouters wrote: > > On Wed, 3 Jul 2019, Mark Andrews wrote: > >> Defeating fragmentation attacks requires more than a BCP. >> >> https://tools.ietf.org/html/draft-andrews-dnsop-defeat-frag-attack-00 > > Sure, so you have an RFC already then. great. No need

[DNSOP] WGLC for draft-ietf-dnsop-serve-stale

2019-07-02 Thread Suzanne Woolf
Dear colleagues, This message starts the Working Group Last Call for draft-ietf-dnsop-serve-stale (https://datatracker.ietf.org/doc/draft-ietf-dnsop-serve-stale/). Since this draft has not been recently discussed in the WG, we figure people might need to swap it back in, and we will be

Re: [DNSOP] [Ext] WGLC for draft-ietf-dnsop-serve-stale

2019-07-02 Thread Paul Hoffman
On Jul 2, 2019, at 6:36 AM, Suzanne Woolf wrote: > First, there have been several IPR disclosures against this document. The > chairs believe all have been resolved. Please clarify what "The chairs believe all have been resolved" means in this context. There are seven IPR statements on the

[DNSOP] IETF 105 Agenda and Call for Agenda Items DNSOP WG

2019-07-02 Thread Benno Overeinder
Hi all, The IETF105 Agenda is out https://datatracker.ietf.org/meeting/105/agenda.html and DNSOP has two sessions Monday 18:10-19:10 Monday Afternoon session III Tuesday 10:00-12:00 Tuesday Morning session I As with the previous IETF meeting, we are planning the shorter (1 hour),

Re: [DNSOP] Obsoleting DLV

2019-07-02 Thread Paul Wouters
On Tue, 2 Jul 2019, Matthijs Mekking wrote: So ISC plans to deprecate the feature in BIND 9. But also I think it is time to move the protocol to Historic status as a clear signal to everyone that it should no longer be implemented or deployed. I agree with moving DLV to historic. It is no

Re: [DNSOP] Obsoleting DLV

2019-07-02 Thread Jim Reid
> On 2 Jul 2019, at 19:12, Matthijs Mekking wrote: > > I think it is time to move the protocol to Historic status as a clear signal > to > everyone that it should no longer be implemented or deployed. Agreed. Kill it with fire! ___ DNSOP mailing

Re: [DNSOP] Obsoleting DLV

2019-07-02 Thread Dan York
> On Jul 2, 2019, at 3:31 PM, Jim Reid wrote: > > > >> On 2 Jul 2019, at 19:12, Matthijs Mekking wrote: >> >> I think it is time to move the protocol to Historic status as a clear signal >> to >> everyone that it should no longer be implemented or deployed. > > Agreed. Kill it with

Re: [DNSOP] Obsoleting DLV

2019-07-02 Thread Warren Kumari
On Tue, Jul 2, 2019 at 11:13 AM Matthijs Mekking wrote: > Hi, > > > A while back I was asked why BIND 9 still had code to do DLV. Good > question, and we asked our users if they would mind if we remove the > code. Almost everyone was okay with that. > > So ISC plans to deprecate the feature in

Re: [DNSOP] Obsoleting DLV

2019-07-02 Thread Joe Abley
+1 to all of that which follows! > On 2 Jul 2019, at 14:41, Paul Wouters wrote: > > On Tue, 2 Jul 2019, Matthijs Mekking wrote: > >> So ISC plans to deprecate the feature in BIND 9. But also I think it is >> time to move the protocol to Historic status as a clear signal to >> everyone that it

Re: [DNSOP] [Ext] WGLC for draft-ietf-dnsop-serve-stale

2019-07-02 Thread Suzanne Woolf
> On Jul 2, 2019, at 10:01 AM, Paul Hoffman wrote: > > On Jul 2, 2019, at 6:36 AM, Suzanne Woolf wrote: >> First, there have been several IPR disclosures against this document. The >> chairs believe all have been resolved. > > Please clarify what "The chairs believe all have been resolved"

Re: [DNSOP] Obsoleting DLV

2019-07-02 Thread Erwin Lansing
> On 2 Jul 2019, at 21.31, Jim Reid wrote: > > > >> On 2 Jul 2019, at 19:12, Matthijs Mekking wrote: >> >> I think it is time to move the protocol to Historic status as a clear signal >> to >> everyone that it should no longer be implemented or deployed. > > Agreed. Kill it with fire! >

Re: [DNSOP] Obsoleting DLV

2019-07-02 Thread Paul Vixie
fine by me. ⁣Get BlueMail for Android ​ On 2 Jul 2019, 13:11, at 13:11, Dan York wrote: > > >> On Jul 2, 2019, at 3:31 PM, Jim Reid wrote: >> >> >> >>> On 2 Jul 2019, at 19:12, Matthijs Mekking >wrote: >>> >>> I think it is time to move the protocol to Historic status as a >clear signal to

Re: [DNSOP] "flagday" again, was Re: Wrapping up draft-ietf-dnsop-dns-tcp-requirements

2019-07-02 Thread Mark Andrews
> On 3 Jul 2019, at 12:31 am, Paul Wouters wrote: > > On Tue, 2 Jul 2019, Petr Špaček wrote: > >> Let me clarify that we (as DNS flag day organizers) are not even >> touching any RFC language because all the necessary pieces are already >> standardized (madatory TCP support + mechanism to

Re: [DNSOP] Obsoleting DLV

2019-07-02 Thread David Conrad
I strongly support moving it to Historic. Regards, -drc > On Jul 2, 2019, at 11:12 AM, Matthijs Mekking wrote: > > Hi, > > > A while back I was asked why BIND 9 still had code to do DLV. Good > question, and we asked our users if they would mind if we remove the > code. Almost everyone was

Re: [DNSOP] "flagday" again, was Re: Wrapping up draft-ietf-dnsop-dns-tcp-requirements

2019-07-02 Thread Paul Wouters
On Tue, 2 Jul 2019, Petr Špaček wrote: Let me clarify that we (as DNS flag day organizers) are not even touching any RFC language because all the necessary pieces are already standardized (madatory TCP support + mechanism to handle EDNS buffer size). If there is a security issue with

[DNSOP] Obsoleting DLV

2019-07-02 Thread Matthijs Mekking
Hi, A while back I was asked why BIND 9 still had code to do DLV. Good question, and we asked our users if they would mind if we remove the code. Almost everyone was okay with that. So ISC plans to deprecate the feature in BIND 9. But also I think it is time to move the protocol to Historic