Re: [DNSOP] DNSOP Call for Adoption: draft-kristoff-dnsop-dns-tcp-requirements

2017-05-26 Thread tjw ietf
All The Call for Adoption ended last night, and there was consensus to adopt this document much like their was in Chicago, We will hold those volunteers to their promise to review, and we'll have the authors upload new versions of the draft. the chairs On Thu, May 11, 2017 at 6:57 AM, tjw ietf

Re: [DNSOP] DNSOP Call for Adoption: draft-kristoff-dnsop-dns-tcp-requirements

2017-05-26 Thread Sara Dickinson
> On 25 May 2017, at 18:00, John Kristoff wrote: > > >> Section 2: I think it might be useful to include a section in section >> 2 describing the fact that the lack of, or very limited >> implementation of TCP also fed the perception that it was a security >> risk. > > The references > > Che

Re: [DNSOP] DNSOP Call for Adoption: draft-kristoff-dnsop-dns-tcp-requirements

2017-05-25 Thread John Kristoff
On Tue, 23 May 2017 12:22:34 + Sara Dickinson wrote: > I’ve reviewed this draft and as stated previously support adoption as > a companion document to RFC7766. Thank you for your review. > Section 2.2: I think the argument around DNSSEC can be bolstered by > the fact that recent root ZSK an

Re: [DNSOP] DNSOP Call for Adoption: draft-kristoff-dnsop-dns-tcp-requirements

2017-05-23 Thread Sara Dickinson
> On 11 May 2017, at 11:57, tjw ietf wrote: > This starts a Call for Adoption for: draft-kristoff-dnsop-dns-tcp-requirements > > The draft is available here: > https://datatracker.ietf.org/doc/draft-kristoff-dnsop-dns-tcp-requirements/ >

Re: [DNSOP] DNSOP Call for Adoption: draft-kristoff-dnsop-dns-tcp-requirements

2017-05-12 Thread 神明達哉
At Fri, 12 May 2017 06:45:52 -0500, John Kristoff wrote: > > I've read draft-kristoff-dnsop-dns-tcp-requirements-02. > > Thank you for taking the time to read, review, and comment on it! > > > I think RFC7766 already pretty clearly states TCP is a MUST. > > IETF RFC 7766 does very explicitly decl

Re: [DNSOP] DNSOP Call for Adoption: draft-kristoff-dnsop-dns-tcp-requirements

2017-05-12 Thread 神明達哉
At Fri, 12 May 2017 11:35:26 +0100, Tony Finch wrote: > > I'm not sure if DDNS update bolsters the need for TCP. In > > my understanding DDNS update exchanges are largely done over UDP > > today (e.g., ISC's nsupdate utility uses UDP by default): > > Well, that depends on the transaction s

Re: [DNSOP] DNSOP Call for Adoption: draft-kristoff-dnsop-dns-tcp-requirements

2017-05-12 Thread John Kristoff
On Thu, 11 May 2017 23:25:13 + 神明達哉 wrote: > I've read draft-kristoff-dnsop-dns-tcp-requirements-02. Thank you for taking the time to read, review, and comment on it! > I think RFC7766 already pretty clearly states TCP is a MUST. IETF RFC 7766 does very explicitly declare TCP is a MUST in

Re: [DNSOP] DNSOP Call for Adoption: draft-kristoff-dnsop-dns-tcp-requirements

2017-05-12 Thread Tony Finch
神明達哉 wrote: > > I'm not sure if DDNS update bolsters the need for TCP. In > my understanding DDNS update exchanges are largely done over UDP > today (e.g., ISC's nsupdate utility uses UDP by default): Well, that depends on the transaction size :-) My servers fairly frequently handle update

Re: [DNSOP] DNSOP Call for Adoption: draft-kristoff-dnsop-dns-tcp-requirements

2017-05-11 Thread 神明達哉
At Thu, 11 May 2017 06:57:51 -0400, tjw ietf wrote: > There was a lot of consensus during our last meeting in Chicago that this > should move forward, so it's time that we do so. > > This starts a Call for Adoption for: > draft-kristoff-dnsop-dns-tcp-requirements > > The draft is available here:

[DNSOP] DNSOP Call for Adoption: draft-kristoff-dnsop-dns-tcp-requirements

2017-05-11 Thread tjw ietf
There was a lot of consensus during our last meeting in Chicago that this should move forward, so it's time that we do so. This starts a Call for Adoption for: draft-kristoff-dnsop-dns-tcp-requirements The draft is available here: https://datatracker.ietf.org/doc/draft-kristoff-dnsop-dns-tcp-requ