Re: [DNSOP] A quick update on draft-ietf-dnsop-attrleaf / draft-ietf-dnsop-attrleaf-fix

2018-10-18 Thread Dave Crocker
On 10/18/2018 12:04 PM, Warren Kumari wrote: Dave has stated that he is unwilling to do this work. Instead of having the WG document simply stall, Benno and I have agreed that we would split them between us. If anyone would like to volunteer to help out, we would not take it amiss. Please not

[DNSOP] A quick update on draft-ietf-dnsop-attrleaf / draft-ietf-dnsop-attrleaf-fix

2018-10-18 Thread Warren Kumari
Hi there, Dave suggested I send this out. draft-ietf-dnsop-attrleaf and draft-ietf-dnsop-attrleaf-fix have completed IESG review. Alissa is holding a DISCUSS position on draft-ietf-dnsop-attrleaf-fix - this can be seen here: https://datatracker.ietf.org/doc/draft-ietf-dnsop-attrleaf-fix/ballot/

[DNSOP] Benjamin Kaduk's No Objection on draft-ietf-dnsop-kskroll-sentinel-15: (with COMMENT)

2018-10-18 Thread Benjamin Kaduk
Benjamin Kaduk has entered the following ballot position for draft-ietf-dnsop-kskroll-sentinel-15: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please r

Re: [DNSOP] Working Group Last Call for: draft-ietf-dnsop-algorithm-update

2018-10-18 Thread Vladimír Čunát
On 10/17/18 11:18 PM, fujiw...@jprs.co.jp wrote: > 4. In my opinion, Ed25519 is best algorithm some yars later. >If the document describes both current RECOMMENDATIONS and >RECOMMENDATIONS some years later, we can plan. I agree, but the last paragraph of 3.1 seems to express that already: