Re: [DNSOP] Working Group Last Call for: draft-ietf-dnsop-algorithm-update
Follow up on WGLC for draft-ietf-dnsop-algorithm-update: We're still looking for comments from the WG on advancing or not advancing this document through the standards process. While a percentage of the WG is at OARC (and maybe even RIPE), why not take a few moments and elicit some comments on this. thanks Tim On Tue, Oct 2, 2018 at 8:51 AM Tim Wicinski wrote: > > The chairs and the authors of this document feel that the > document is in solid shape to proceed to WGLC. > > > This starts a Working Group Last Call for draft-ietf-dnsop-algorithm-update > > Current versions of the draft is available here: > https://datatracker.ietf.org/doc/draft-ietf-dnsop-algorithm-update/ > > The Current Intended Status of this document is: Proposed Standard > > Please review the draft and offer relevant comments. > If this does not seem appropriate please speak out. > If someone feels the document is *not* ready for publication, please speak > out with your reasons. > > This starts a two week Working Group Last Call process, and ends on: 16 > October 2018 > > thanks > tim > > ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Working Group Last Call for: draft-ietf-dnsop-algorithm-update
Hi Loganaden, while I understand what you are asking for, I don’t understand how it would improve the document. IETF RFCs are static and if we include any current “numbers” they quickly become invalid. Adding figures to the document doesn’t improve readability or the content. While it would support the claims we make in the document I feel that the consensus process IETF have is just fine for giving the content enough validity, and we don’t have to support every claim we make in the document with figures. Ondrej -- Ondřej Surý ond...@isc.org > On 2 Oct 2018, at 15:40, Loganaden Velvindron wrote: > > On Tue, Oct 2, 2018 at 4:51 PM Tim Wicinski wrote: >> >> >> The chairs and the authors of this document feel that the >> document is in solid shape to proceed to WGLC. >> >> >> This starts a Working Group Last Call for draft-ietf-dnsop-algorithm-update >> >> Current versions of the draft is available here: >> https://datatracker.ietf.org/doc/draft-ietf-dnsop-algorithm-update/ >> > > Section 3.1. > > " > RSASHA1 and RSASHA1-NSEC3-SHA1 are widely deployed, although zones > deploying it are recommended to switch to ECDSAP256SHA256 as there is > an industry-wide trend to move to elliptic curve cryptography. > " > > And also this paragraph: > " > > RSASHA256 is in wide use and considered strong. > > " > > My suggestion would be to include figures or at minimum a reference. > There is a document from ISOC with 3 tables where there is an analysis > of deployment DNSSEC worldwide. > > https://www.internetsociety.org/wp-content/uploads/2017/08/ISOC-State-of-DNSSEC-Deployment-2016-v1.pdf, > Page 23 & Page 24. > > >> The Current Intended Status of this document is: Proposed Standard >> >> Please review the draft and offer relevant comments. >> If this does not seem appropriate please speak out. >> If someone feels the document is *not* ready for publication, please speak >> out with your reasons. >> >> This starts a two week Working Group Last Call process, and ends on: 16 >> October 2018 >> >> thanks >> tim >> >> ___ >> DNSOP mailing list >> DNSOP@ietf.org >> https://www.ietf.org/mailman/listinfo/dnsop > > ___ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
[DNSOP] I-D Action: draft-ietf-dnsop-algorithm-update-02.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Domain Name System Operations WG of the IETF. Title : Algorithm Implementation Requirements and Usage Guidance for DNSSEC Authors : Paul Wouters Ondrej Sury Filename: draft-ietf-dnsop-algorithm-update-02.txt Pages : 10 Date: 2018-10-14 Abstract: The DNSSEC protocol makes use of various cryptographic algorithms in order to provide authentication of DNS data and proof of non- existence. To ensure interoperability between DNS resolvers and DNS authoritative servers, it is necessary to specify a set of algorithm implementation requirements and usage guidelines to ensure that there is at least one algorithm that all implementations support. This document defines the current algorithm implementation requirements and usage guidance for DNSSEC. This document obsoletes [RFC6944]. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dnsop-algorithm-update/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-dnsop-algorithm-update-02 https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-algorithm-update-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-algorithm-update-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
[DNSOP] I-D Action: draft-ietf-dnsop-serve-stale-02.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Domain Name System Operations WG of the IETF. Title : Serving Stale Data to Improve DNS Resiliency Authors : David C Lawrence Warren Kumari Puneet Sood Filename: draft-ietf-dnsop-serve-stale-02.txt Pages : 12 Date: 2018-10-14 Abstract: This draft defines a method for recursive resolvers to use stale DNS data to avoid outages when authoritative nameservers cannot be reached to refresh expired data. It updates the definition of TTL from [RFC1034] and [RFC1035] to make it clear that data can be kept in the cache beyond the TTL expiry and used for responses when a refreshed answer is not readily available. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dnsop-serve-stale/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-dnsop-serve-stale-02 https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-serve-stale-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-serve-stale-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Working Group Last Call for: draft-ietf-dnsop-algorithm-update
Tim, I have reviewed the document and it is ready for publication Olafur On Tue, Oct 2, 2018 at 2:51 PM Tim Wicinski wrote: > > The chairs and the authors of this document feel that the > document is in solid shape to proceed to WGLC. > > > This starts a Working Group Last Call for draft-ietf-dnsop-algorithm-update > > Current versions of the draft is available here: > https://datatracker.ietf.org/doc/draft-ietf-dnsop-algorithm-update/ > > The Current Intended Status of this document is: Proposed Standard > > Please review the draft and offer relevant comments. > If this does not seem appropriate please speak out. > If someone feels the document is *not* ready for publication, please speak > out with your reasons. > > This starts a two week Working Group Last Call process, and ends on: 16 > October 2018 > > thanks > tim > > ___ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop > -- Ólafur Gudmundsson | Engineering Director www.cloudflare.com blog.cloudflare.com ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] Working Group Last Call for: draft-ietf-dnsop-algorithm-update
I've been using the document for the DNSSD Service Registration Protocol work; it's useful, and should be published. On Sun, Oct 14, 2018 at 5:55 AM Tim Wicinski wrote: > Follow up on WGLC for draft-ietf-dnsop-algorithm-update: > > We're still looking for comments from the WG on advancing or not advancing > this document through the standards process. > While a percentage of the WG is at OARC (and maybe even RIPE), why not > take a few moments and elicit some comments > on this. > > thanks > Tim > > > On Tue, Oct 2, 2018 at 8:51 AM Tim Wicinski wrote: > >> >> The chairs and the authors of this document feel that the >> document is in solid shape to proceed to WGLC. >> >> >> This starts a Working Group Last Call for >> draft-ietf-dnsop-algorithm-update >> >> Current versions of the draft is available here: >> https://datatracker.ietf.org/doc/draft-ietf-dnsop-algorithm-update/ >> >> The Current Intended Status of this document is: Proposed Standard >> >> Please review the draft and offer relevant comments. >> If this does not seem appropriate please speak out. >> If someone feels the document is *not* ready for publication, please >> speak out with your reasons. >> >> This starts a two week Working Group Last Call process, and ends on: 16 >> October 2018 >> >> thanks >> tim >> >> ___ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop > ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
Re: [DNSOP] I-D Action: draft-ietf-dnsop-algorithm-update-02.txt
Colleagues, there are no functional changes to the draft. Evan Hunt improved the language, and I added Implementation Report to the document. Ondrej -- Ondřej Surý ond...@isc.org > On 14 Oct 2018, at 14:16, internet-dra...@ietf.org wrote: > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Domain Name System Operations WG of the IETF. > >Title : Algorithm Implementation Requirements and Usage > Guidance for DNSSEC >Authors : Paul Wouters > Ondrej Sury > Filename: draft-ietf-dnsop-algorithm-update-02.txt > Pages : 10 > Date: 2018-10-14 > > Abstract: > The DNSSEC protocol makes use of various cryptographic algorithms in > order to provide authentication of DNS data and proof of non- > existence. To ensure interoperability between DNS resolvers and DNS > authoritative servers, it is necessary to specify a set of algorithm > implementation requirements and usage guidelines to ensure that there > is at least one algorithm that all implementations support. This > document defines the current algorithm implementation requirements > and usage guidance for DNSSEC. This document obsoletes [RFC6944]. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-dnsop-algorithm-update/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-dnsop-algorithm-update-02 > https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-algorithm-update-02 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-algorithm-update-02 > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > ___ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
