Source / pinned edition
IANA Services and DNSSEC
Source of package icann.ksk_ceremony · IETF 108 IANA Services and DNSSEC presentation
- work
- urn:icann:clir:ksk-ceremony#IETF108_IANA_PRESENTATION
- number
- IETF 108 IANA Services and DNSSEC presentation
- kind
- urn:icann:clir:ksk-ceremony#doctrine
IETF108_IANA_PRESENTATION_ED
- edition
- urn:icann:clir:ksk-ceremony#IETF108_IANA_PRESENTATION_ED
- language
- en
- officiality
- official
- materialisation
- PINNED_UNOFFICIAL_COPY
- life cycle
- adopted: 2020-07-01; in_force: [object Object]
Publications
| URI | Type | documentHash | Retrieved |
|---|---|---|---|
| https://www.ietf.org/media/documents/mc-ietf108-jul2020.pdf | text/plain; charset=utf-8 | sha256:592826b8b887acf627a70ba56e24b7d47218129a6958b9a8244d565be98e6842 | 2026-08-31T00:00:00Z |
Fragments — 2
slides/5-6 · provision
en · official · sha256:5086382de6a1da17c36bbc1e14c48bb643feab0dcc37ca034ac2b0611bcfc75c
Ceremony 41 was successfully executed on 23 April 2020
• The evolving Coronavirus situation caused us to focus on developing
contingencies for this ceremony as the situation deteriorated
• Notably, the design of the Key Management Facilities is designed to enable key
operations to be performed in a disaster recovery scenario without the
minimum number of TCRs present
|6
IANA Services and DNSSEC
Ceremony 41 cont.
• Settled on an approach to perform the ceremony with minimum personnel, with
TCRs participating remotely.
§ DPS revised to clarify roles and responsibility and provide flexibility for disaster
recovery
§ Obtained ICANN Board and executive approval, community buy-in
§ Minimized the scope of the ceremony by eliminating non-essential acts
§ 4 of 7 TCRs transmitted their secure credentials to 4 surrogates in Los Angeles
§ Hold the ceremony on the time and date scheduled, but in El Segundo, not
Culpeper as originally planned with minimized attendees
§ Sign nine months of key material instead of the typical three months
§ Release signatures to Verisign in 3 month increments as usualslide/5 · provision
en · official · sha256:29225adc06dc061ea71457dffd4ab8dc9fd557cd066a622a2880370f45114b7f
Ceremony 40 was successfully executed on 16 February 2020
• An administrative ceremony took place February 11th, the day before the
originally scheduled KSK Ceremony date, to replace an aging safe dial. The last
time this safe dial would’ve ever operated, it failed to do so
• KSK Ceremony was postponed for the first time ever
• Approximately 20 hours across two days to drill into the lock assembly and
remove the bolt to allow the safe to open
• Followed by safe remediation and installation of new lock
• Complicated by triggering anti-defeat mechanisms in the lock due to novel
materials in safe constructionThe hash beside the text is the sha256 of its exact bytes. It is the check that the text shown matches the one pinned in the package: a divergence fails the oracle’s static analysis.