Good to hear.   Thank you.
I was able to show this zsk rollover as an example for the DNSSEC hands-on 
training in Ankara.
Students were not rolling from 1024 to 2048 in the lab but I did tell them they 
were witnessing history.  I could almost taste the excitement ;-)
https://www.co.tt/rootzskrolltr.png 

-Rick



-----Original Message-----
From: dnssec-deployment-boun...@dnssec-deployment.org 
[mailto:dnssec-deployment-boun...@dnssec-deployment.org] On Behalf Of Wessels, 
Duane
Sent: Thursday, September 29, 2016 6:15 PM
To: dnssec-deployment@dnssec-deployment.org
Subject: Re: [Dnssec-deployment] Root Zone DNSSEC Operational Update -- ZSK 
length change

A quick update on this change: A 2048-bit ZSK has been pre-published in the 
root zone as of September 20.  We are not aware of any issues related to the 
appearance of the larger key.

In less than 48 hours we will being publishing root zones signed with the 
2048-bit ZSK.  I will send another note once that has happened.  If you observe 
any problems related to this change, please contact Verisign's customer service 
at i...@verisign-grs.com.

Duane W.

> On Jul 28, 2016, at 3:37 PM, Wessels, Duane <dwess...@verisign.com> wrote:
> 
> As you may know, Verisign, in its role as the Root Zone Maintainer is 
> also the operator of the root zone Zone Signing Key (ZSK).  Later this 
> year, we will increase the size of the ZSK from 1024-bits to 
> 2048-bits.
> 
> The root zone ZSK is normally rolled every calendar quarter, as per 
> our “DNSSEC Practice Statement for the Root Zone ZSK operator.”[1] The 
> ZSK public keys are signed at quarterly key signing ceremonies by 
> ICANN in its role as the IANA Functions Operator.
> 
> On September 20, 2016 the 2048-bit ZSK will be pre-published in the 
> root zone, following the standard ZSK rollover procedure.  We intend 
> to begin publishing root zones signed with the first 2048-bit ZSK on 
> October 1, 2016.
> 
> Some details of the ZSK size transition have recently been presented 
> at the DNS-OARC, NANOG, RIPE, ICANN, and IETF meetings.[2]  If you 
> have any questions or concerns, please feel free to contact us at 
> z...@verisign.com.
> 
> Please feel free to forward this message to anyone who might not have 
> seen it here.
> 
> [1] https://www.verisign.com/assets/dps-zsk-operator-1532.pdf
> [2] 
> https://ripe72.ripe.net/wp-content/uploads/presentations/168-verisign-
> zsk-change.pdf
> 

Reply via email to