ICANN Generates First DNS Root Key to Secure Global Web Addressing

ICANN

The formal generation of the 2048-bit root key establishes a distributed cryptographic trust architecture designed to prevent domain spoofing and anchor authentication across the entire internet.

AI-assisted summary of KSK Key Signing Ceremony (16 Jun 10) — original source. Check the original for full context.

Source published: 2010-06-18

Key ideas

ICANN, Verisign, and the U.S. Department of Commerce collaborated to execute the first Key Signing Ceremony, introducing cryptographic trust to the DNS root zone. (0:00)
The root Key Signing Key (KSK)—a 2048-bit RSA key pair—was generated inside a dedicated cryptographic hardware module stored in GSA Class 5 safes equipped with seismic and interlock alarms. (1:48)
Control of root cryptographic material is distributed among at least 21 Trusted Community Representatives (TCRs), split into Crypto Officers and Recovery Key Shareholders. (3:20)
Organizers noted that beyond preventing DNS spoofing, the newly established hierarchical trust infrastructure can be purposed across the wider internet for multiple authentication needs. (5:40)

Detailed notes

## Background Published on YouTube by ICANN on June 18, 2010, this video provides highlights and an overview of the historic June 16, 2010 Key Signing Ceremony. The video documents the collaborative effort between ICANN, Verisign, and the U.S. Department of Commerce to establish cryptographic security for the DNS root.

## TL;DR To fix foundational security flaws in the Domain Name System where user requests could be maliciously misdirected, a joint initiative was established to deploy a cryptographically signed DNS root zone. The video outlines the inaugural Key Signing Ceremony, where roughly 30 to 35 observers witnessed the generation of a 2048-bit RSA Key Signing Key inside tamper-resistant hardware. Procedural control is divided among Trusted Community Representatives acting as Crypto Officers and Recovery Key Shareholders, ensuring the system can survive catastrophic disasters without concentrating unilateral power in ICANN. The ceremony concludes with the successful generation and verification of the root key, establishing a foundational trust hierarchy for the wider internet.

## Atmosphere & style The presentation blends the solemn precision of high-stakes institutional cryptography with an accessible, documentary-style explanation of complex technical procedures. An undercurrent of dry levity emerges as organizers clarify that the 'ceremony' is a strict procedural audit rather than a mystical ritual, all while operating under intense physical security involving GSA Class 5 vaults and seismic sensors. Watching the process unfold inside the secure room evokes a quiet, tense reverence for internet infrastructure, culminating in a shared sense of historic relief and applause as the key is verified.

## Bulletin - [00:00](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=0s) ICANN, Verisign, and the U.S. Department of Commerce collaborated to execute the first Key Signing Ceremony, introducing cryptographic trust to the DNS root zone. - [01:48](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=108s) The root Key Signing Key (KSK)—a 2048-bit RSA key pair—was generated inside a dedicated cryptographic hardware module stored in GSA Class 5 safes equipped with seismic and interlock alarms. - [03:20](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=200s) Control of root cryptographic material is distributed among at least 21 Trusted Community Representatives (TCRs), split into Crypto Officers and Recovery Key Shareholders. - [05:40](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=340s) Organizers noted that beyond preventing DNS spoofing, the newly established hierarchical trust infrastructure can be purposed across the wider internet for multiple authentication needs.

## Key takeaways - [00:00](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=0s) The internet lacks an inherent architectural security mechanism to verify that received information originates from the legitimate source. - [00:00](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=0s) Signing the DNS root was framed as a fundamental milestone comparable to the introduction of the World Wide Web in the early 1990s. - [00:00](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=0s) The security design was established through a joint team representing ICANN, Verisign, and the U.S. Department of Commerce. - [00:00](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=0s) Extensive international technical consultations preceded the signing, yielding strong global consensus among operators and protocol engineers. - [01:48](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=108s) The Key Signing Ceremony operates as a strictly scripted, transparent, and continuously filmed event to eliminate suspicions of impropriety. - [01:48](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=108s) Hardware is protected by federal GSA Class 5 safes featuring seismic sensors and door interlocks that prevent room exit until the safe is locked. - [01:48](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=108s) The root Key Signing Key is generated as a 2048-bit RSA key pair inside a tamper-resistant hardware security module. - [01:48](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=108s) Witnesses verify the integrity of the key generation in real time using printed cryptographic hashes displayed against public monitors. - [03:20](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=200s) Authority is divided across at least 21 Trusted Community Representatives to prevent ICANN from unilaterally accessing or activating the cryptographic system. - [03:20](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=200s) Recovery Key Shareholders retain encrypted key fragments in tamper-evident bags, requiring a minimum of five shareholders to assemble to reconstruct the master key. - [03:20](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=200s) Crypto Officers hold physical keys to safe deposit boxes housing operational smart cards rather than taking the cards off-site, preserving emergency survivability. - [03:20](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=200s) In extreme travel-disrupting disasters, ICANN retains audited and monitored drilling protocols to access safe deposit boxes to keep the system operational. - [03:20](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=200s) Between ceremonies, integrity is preserved through uninterrupted video surveillance and comprehensive audit trails. - [05:40](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=340s) The hierarchical trust infrastructure established by the root key is intended to serve broader authentication functions across the internet beyond DNS lookups.

## Detailed walkthrough ### [00:00](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=0s) Motivation, Collaboration, and DNS Root Signing

The initiative to secure the Domain Name System (DNS) root is framed as a monumental technological leap. A speaker reflects on the magnitude of the effort, noting: “I would compare this to the arrival of the World Wide Web in the early 1990s in terms of its enabling capability, of course we'll see whether that prediction holds up, but it's a very powerful step.” At its fundamental architectural layer, the internet has no inherent security mechanism, meaning users cannot natively verify whether information received across the network truly originated from the intended source. This vulnerability introduces severe risks, such as users attempting to navigate to their banking portal and being maliciously misdirected elsewhere. Because authenticating data is an intricate technical challenge beyond ordinary end users, an underlying framework is needed to provide cryptographic assurance.

To resolve this issue, a dedicated design team was established involving three core entities responsible for managing the root zone of the DNS: Verisign, the United States Department of Commerce, and ICANN. Their objective was to introduce robust cryptographic security while preserving the established organizational hierarchy. Over the preceding year, ICANN carried out extensive global technical consultations with network operators, protocol engineers, and DNS service providers to evaluate the architecture and identify any potential operational friction. The international consensus was exceptionally supportive, with broad enthusiasm across the technical community to see the root zone signed.

```mermaid flowchart TD accTitle: DNS Root Security Architecture accDescr: Collaboration between Verisign, Department of Commerce, and ICANN to sign the DNS root.

subgraph Governance["Governance & Design"] ICANN["ICANN"] DOC["U.S. Dept of Commerce"] VR["Verisign"] end

subgraph Implementation["Root Security"] DT["Design Team Architecture"] CONSULT["Global Technical Consultation"] ROOT["Signed DNS Root Zone"] end

ICANN --> DT DOC --> DT VR --> DT DT --> CONSULT CONSULT --> ROOT ```

[01:48](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=108s) The Ceremony, Physical Security, and Key Generation

The Key Signing Ceremony is structured as an intensely scripted, highly transparent event designed to remove any suspicion of impropriety. In a room populated by roughly 30 to 35 participants and observers, every single movement is filmed continuously. As an organizer humorously clarifies: “It's not anything where people hum or have some sort of strange, you know, ritual or anything like that, I think sometimes it gets misunderstood, it's just a very formal process.” Physical security is paramount; the hardware is housed inside GSA Class 5 safes of the type used by the federal government. These safes are equipped with seismic detectors and specialized door interlocks wired into the facility's extensive alarm network, ensuring that participants cannot exit unless the vault door is fully closed and locked.

Once the hardware is extracted, the root Key Signing Key (KSK)—a 2048-bit RSA key pair—is generated inside a dedicated cryptographic hardware module (Hardware Security Module). To confirm the validity of the process without exposing the secret key itself, printed cryptographic hashes (shorthand representations of the key) are distributed to the witnesses in the room. This enables everyone present to verify directly via public monitors that the key was generated properly and without sleight of hand.

- Total ceremony observers and participants: approximately 30 to 35 people. - Storage: Federal GSA Class 5 rated safes featuring active seismic and door sensors. - Key specification: 2048-bit RSA key pair generated inside a tamper-resistant cryptographic box. - Verification mechanism: Printed cryptographic hashes handed out to witnesses to verify the generation process visually and mathematically.

[03:20](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=200s) Trusted Community Representatives: Crypto Officers and Recovery Shareholders

To ensure that ICANN cannot unilaterally activate or access the cryptographic system, control is distributed across Trusted Community Representatives (TCRs). A pool of at least 21 TCRs is maintained, with 14 in attendance for this specific ceremony. These representatives are divided into two distinct roles: Crypto Officers and Recovery Key Shareholders. The Recovery Key Shareholders hold smart cards containing encrypted fragments of the backup key stored in tamper-evident bank bags. In the catastrophic event that both ICANN's primary East Coast and West Coast duplicate facilities are lost, a minimum of five of these shareholders must physically assemble to reconstruct the master recovery encryption key.

Crypto Officers hold physical safe deposit keys corresponding to safety deposit boxes built directly inside the safes, which house the operational smart cards. When addressing why the officers hold keys to the safe deposit boxes rather than holding the smart cards directly off-site, an official explains the absolute necessity of disaster survivability: “This system has to operate, it cannot fail. So if we have a 9/11 situation or something where these people cannot travel here, we have to be able to get at these keys.” In an extreme emergency where officers cannot physically travel, ICANN retains the capability to drill the deposit boxes under full audit and surveillance conditions. Between official ceremonies, continuous video surveillance and rigorous audit trails prove that the keys remain untouched.

```mermaid flowchart TD accTitle: Trusted Community Representative Structure accDescr: Separation of roles between Recovery Key Shareholders and Crypto Officers.

subgraph TCR["Trusted Community Representatives (21 Total)"] RKS["Recovery Key Shareholders"] CO["Crypto Officers"] end

subgraph Storage["Access Control & Safeguards"] BAGS["Tamper-Evident Bags<br/>(Encrypted Key Shares)"] BOXES["Safe Deposit Boxes<br/>(Inside GSA Class 5 Safe)"] HSM["Cryptographic Device Activation"] end

RKS -->|"Minimum 5 of 7 required"| BAGS CO -->|"Physical safe deposit keys"| BOXES BOXES --> HSM ```

[05:40](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=340s) Broader Implications and Official Key Generation

The ceremony concludes with a forward-looking perspective on the broader architectural impact of the newly established trust root. While the primary mission of the KSK ceremony is to guarantee that DNS queries return genuine IP addresses rather than spoofed records, the hierarchical trust infrastructure being put into place has far-reaching potential beyond standard domain lookups.

A speaker highlights the historical significance of the moment: “More has happened here today than meets the eye, an infrastructure has been created for a hierarchical security system which can be purposed and repurposed in a number of different ways.” He predicts that this hierarchical structure of trust will eventually underpin a wide array of systems requiring strong cryptographic authentication across the entire internet. The event culminates with the formal announcement that the 2048-bit RSA key pair has been successfully generated, met by enthusiastic applause from the room.

## Mentioned ICANN, Verisign, United States Department of Commerce, Domain Name System (DNS), World Wide Web, Key Signing Key (KSK), Hardware Security Module (HSM), Trusted Community Representatives (TCR), Crypto Officers, Recovery Key Shareholders, RSA

## Video description Highlights and a description of the June 16, 2010 Key Signing Ceremony.

[Source](https://www.youtube.com/watch?v=b9j-sfP9GUU)

中文简报

ICANN生成首个DNS根密钥以保障全球网络寻址安全 2048位根密钥的正式生成确立了分布式加密信任架构，旨在防止域名欺骗并在整个互联网上建立认证锚点。为修复域名系统中可能导致用户请求被恶意重定向的基础性安全缺陷，一项联合举措启动以部署经过加密签名的DNS根区。该视频概述了首届密钥签名仪式，约30至35名观察员见证了在防篡改硬件内生成2048位RSA密钥签名密钥的过程。程序控制权分配给担任加密官员和恢复密钥股东的受信任社区代表，以确保系统在遭遇灾难性事故时仍能维持运转，同时避免单方面权力集中于ICANN。仪式以根密钥的成功生成和验证告终，为更广泛的互联网建立了基础信任层级。 ICANN、Verisign以及美国商务部合作执行了首次密钥签名仪式，为DNS根区引入加密信任机制。 (0:00) 根密钥签名密钥（KSK）——即一个2048位的RSA密钥对——是在专用的加密硬件模块内部生成的，该模块存放在配备地震和联锁警报的GSA 5级保险箱中。 (1:48) 根加密材料的控制权分配给至少21名受信任社区代表（TCR），分为加密官员和恢复密钥股东。 (3:20) 组织者指出，除了防止DNS欺骗之外，新建立的层级信任基础设施还可应用于整个互联网，以满足多种认证需求。 (5:40)

Reading summary

ICANN, Verisign, and the U.S. Department of Commerce executed the inaugural Key Signing Ceremony to cryptographically secure the DNS root zone, generating a 2048-bit RSA key pair under strict physical and distributed controls. Organizers positioned the deployment as a critical step to eliminate DNS spoofing while laying the groundwork for a broader internet authentication hierarchy. Architectural Vulnerability and Collaborative Root Governance (0:00) The core architecture of the internet was designed without native security mechanisms to verify the authenticity of network data, exposing users to risks such as fraudulent redirection when attempting to access legitimate websites like banking portals. Because authenticating data is technically complex for ordinary end users, establishing cryptographic assurance required an underlying systemic solution. To resolve this without disrupting established operational hierarchies, a dedicated design team comprising ICANN, Verisign, and the United States Department of Commerce developed the root signing framework. Over the preceding year, ICANN conducted extensive global technical consultations with network operators, protocol engineers, and DNS service providers, securing broad technical consensus to move forward with signing the DNS root zone. Physical Containment and Auditable Key Generation (1:48) To ensure transparency and eliminate suspicion of procedural impropriety, the Key Signing Ceremony followed an intensely scripted, continuously filmed protocol witnessed by approximately 30 to 35 participants and observers. Physical containment relied on federal GSA Class 5 safes fitted with seismic sensors and specialized door interlocks wired into the facility alarm network, preventing participants from exiting until the safe door was fully closed and locked. Inside this environment, the root Key Signing Key (KSK)—a 2048-bit RSA key pair—was generated within a tamper-resistant Hardware Security Module. Rather than revealing the private key material, officials distributed printed cryptographic hashes to witnesses in the room, enabling attendees to independently verify via public monitors that the key generation was performed mathematically and without sleight of hand. Distributed Authority and Crisis Survivability (3:20) To prevent ICANN from exercising unilateral control over the cryptographic root, operational and recovery authorities are divided among a pool of at least 21 Trusted Community Representatives (TCRs), 14 of whom attended the ceremony. These representatives are divided into Recovery Key Shareholders and Crypto Officers. Recovery Key Shareholders hold smart cards storing encrypted backup fragments inside tamper-evident bank bags; should ICANN lose both its primary East Coast and West Coast duplicate facilities, a minimum of five shareholders must physically assemble to reconstruct the master recovery key. Crypto Officers hold physical keys to safe deposit boxes housed directly inside the GSA Class 5 safes, which contain operational smart cards. Officials explained that holding keys rather than keeping smart cards off-site balances distributed control with disaster survivability. In extreme scenarios where officers cannot travel—such as a major crisis akin to 9/11—ICANN retains the audited ability to drill the deposit boxes under continuous surveillance to ensure the root system never fails. Long-Term Potential of Hierarchical Trust (5:40) While the immediate objective of the ceremony was to guarantee that DNS queries return authentic IP addresses rather than spoofed records, participants emphasized the architecture's broader systemic potential. A speaker noted the magnitude of the effort by comparing its enabling capability to the emergence of the World Wide Web in the early 1990s, while qualifying that only time will confirm whether that forecast holds true. Speakers highlighted that the ceremony created a general-purpose hierarchical security infrastructure that can be purposed and repurposed. Under this forward-looking projection, the established root trust model could eventually underpin diverse systems across the internet that demand robust cryptographic authentication. The ceremony successfully concluded with the verified generation of the 2048-bit RSA key pair, establishing a baseline of trust for global DNS resolution. However, whether this hierarchical trust framework will successfully expand beyond domain name authentication into a ubiquitous identity anchor for broader internet services remains an open, long-term projection.

精炼阅读摘要

2010年6月16日，ICANN联合美国商务部与Verisign正式执行了首次DNS根区密钥签名仪式，通过生成2048位RSA根密钥签名密钥（KSK），为缺乏原生安全验证机制的互联网底层架构引入密码学信任根。底层架构缺陷与多方治理协作 (0:00) 互联网在基础架构层面上缺乏内生的安全验证机制，导致普通用户无法在底层直接核验所接收网络数据的真实来源，从而面临访问银行门户等服务时被恶意重定向的风险。针对数据认证对终端用户过于复杂的问题，ICANN、美国商务部与Verisign三方组成联合设计团队，在维持现有组织层级的前提下构建密码学安全保障方案。在方案敲定前，ICANN开展了长达一年的全球技术咨询，与网络运营商、协议工程师及DNS服务商充分评估架构，最终获得了国际技术界对签署根区的一致支持。发言人将这一根区签名举措的赋能潜力比作1990年代初万维网的诞生，但同时也指出该预测能否完全兑现仍有待后续观察。仪式透明度与严密物理安防规范 (1:48) 密钥签名仪式采取全程脚本化与高度公开的方式进行，现场约有30至35名参与者与观察员，所有操作均被全程不间断录像，以杜绝任何违规嫌疑并破除外界将其误读为神秘仪式的印象。用于存放硬件的设施采用了达到美国联邦政府标准的GSA Class 5级别保险柜，柜体配备地震感应器以及与整套报警系统联动的门禁互锁装置，唯有金库大门完全关闭并上锁，人员方能离开。在此物理防护下，专用防篡改硬件安全模块（HSM）成功生成了2048位RSA密钥对。现场向证人分发了打印出的密钥加密哈希值，供各方通过公共显示屏即时核验，确保密钥生成全过程在不泄露私钥的前提下完全公开透明且可数学验证。可信社区代表与灾难恢复机制 (3:20) 为防止ICANN单方面控制或启动密码系统，控制权被分散至至少21名可信社区代表（TCR）组成的池中，本次仪式共有14人到场。代表具体分为加密官员与恢复密钥股东两类角色：恢复密钥股东持有装在防篡改银行袋内的智能卡，内含备份密钥的加密碎片，若ICANN设于美国东海岸与西海岸的双活设施均遭毁灭性破坏，至少需要5名股东亲赴现场才能重构主恢复加密密钥；加密官员则持有特定物理钥匙，用于开启保险柜内保管运行智能卡的保管箱。官方解释指出，官员仅持有保险箱钥匙而非直接带走智能卡，是出于应对如极端突发事件下人员无法出行的灾难生存考量；若遭遇此类极端情况，ICANN在严格审计与全程监控下拥有钻开保管箱的权限，而在两次仪式之间，持续的监控录像与严密审计轨迹用于证明钥匙未被触动。分层信任架构的长远网络延伸 (5:40) 该仪式的主要任务虽然是确保DNS查询返回真实的IP地址而非被伪造的记录，但发言人强调这一建立分层安全信任体系的举措所蕴含的意义远超表面所见。演讲者预测，本次仪式所搭建的基础设施未来能够被灵活复用，并最终演进为支撑整个互联网各类强密码学认证系统的核心信任根基。首届KSK签名仪式确立了结合多方物理控制与公开监督的根区管理机制，其直接成效在于提升DNS解析的真实性；但该分层信任体系能否如发言人预期般成功扩展并承载全网更多维度的密码学认证应用，仍有待未来实践与技术演进的验证。

Detailed notes — zh

## Background 本视频由 ICANN 于 2010 年 6 月 18 日发布在 YouTube 平台上。视频简介指出，本片记录了 2010 年 6 月 16 日举行的 DNSSEC 根区密钥签名仪式（Key Signing Ceremony）的现场集锦与流程解说。 ## TL;DR 针对互联网底层缺乏原生身份验证、易遭受域名劫持与仿冒的安全缺陷，ICANN 联合 VeriSign 及美国商务部，正式启动了 DNS 根区密钥签名项目。在严密监控与透明公开的仪式现场，工程师在 GSA Class 5 级高安保保险箱与硬件安全模块（HSM）的保护下，成功生成了 2048 位 RSA 根密钥签名密钥（KSK）。为避免权力集中并兼顾极端灾难恢复，全球遴选的“受信社区代表”（TCR）分别担任密码官员与恢复密钥持有者，通过门限密码学机制实现共同制衡。这一历史性创举不仅加固了域名系统的解析信任，更为整个互联网生态奠定了层次化公钥认证的安全基石。 ## Atmosphere & style 全片充盈着一种肃穆、严谨且充满科技使命感的氛围。伴随着精密安保机制的展开与专业人士条理清晰的解说，观众能真切感受到现场近乎无菌级的透明度与仪式感，彻底破除了外界关于“神秘宗教仪式”的戏谑偏见。从防震保险箱开启时的屏息以待，到密钥成功生成后全场爆发的热烈掌声，整个叙事展现出技术先驱们在守护全球网络基础设施时的敬畏之心与自豪之情。 ## Bulletin - [00:00](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=0s) ICANN、VeriSign 与美国商务部联合实施了历史性的 DNS 根区密钥签名仪式，成功在硬件安全模块（HSM）中生成首个 2048 位 RSA 根密钥签名密钥（KSK），为互联网构建底层密码学信任链。 - [01:46](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=106s) 仪式在 GSA 5 级防震金库中进行，现场约 30 至 35 名见证人直接核对打印出的 2048 位密钥哈希指纹，全程录像并留下完整审计线索以杜绝作弊。 - [03:22](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=202s) 机制引入了全球 21 位受信社区代表（TCR）制度，ICANN 无法单方面操作私钥；在东西海岸双数据中心全毁的极端场景下，需至少 5 名恢复密钥持有者齐聚方可拼合分片重构解密密钥。 - [05:39](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=339s) 技术专家指出该仪式的意义堪比 1990 年代初期万维网的诞生，所建立的层次化信任体系未来将超越域名解析，广泛赋能整个网络空间的强身份认证。 ## Key takeaways - [00:00](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=0s) 互联网底层架构在最初设计时缺乏身份源认证能力，用户无法在传输层验证数据真实性，面临严重的 DNS 劫持与假冒站点威胁。 - [00:00](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=0s) 根区 DNSSEC 密钥签名的深远意义被发言人比作 1990 年代初万维网的问世，是互联网赋能能力的巨大飞跃。 - [00:00](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=0s) 该方案由维护根区的 VeriSign、美国商务部及 ICANN 三方设计团队协作推进，并在全球征询中获得了运营商与协议专家的压倒性支持。 - [01:46](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=106s) 密钥签名仪式是一套极度透明且严密的标准化流程，完全打破外界对于神秘“仪轨”的误解，全流程接受约 30 至 35 名代表现场监督与录像取证。 - [01:46](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=106s) 物理安保采用 GSA Class 5 联邦最高规格保险箱，集成地震与门禁传感器，具备未关门即全场锁闭防脱离的高级联动机制。 - [01:46](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=106s) 硬件加密模块（HSM）在隔离环境中生成 2048 位 RSA 密钥对，并现场打印哈希指纹供参会人员逐一比对确认无作弊风险。 - [03:22](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=202s) ICANN 设立了由全球至少 21 名代表组成的受信社区代表（TCR）架构，剥离自身单方签署密钥的权力，将信任植根于全球互联网社区。 - [03:22](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=202s) 日常操作由持有保管箱钥匙的密码官员（Crypto Officers）参与，智能卡封存于东西海岸两处数据中心内，极端灾难下允许物理钻探取卡以确保服务可用性。 - [03:22](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=202s) 容灾机制采用门限密码学分片管理，恢复密钥持有者随身携带防篡改袋中的密钥分片，需至少 5 人同时到场方能重构灾备密钥。 - [03:22](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=202s) 从设备解封、签名执行到重新锁闭，全程无死角录像并留存完整审计跟踪（audit trail），向全球提供无法篡改的公信力证明。 - [05:39](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=339s) 此次仪式不仅解决了域名解析的真实性验证，更构建了一套可复用于未来各类网络强身份认证场景的层次化安全基础设施。 ## Detailed walkthrough ### [00:00](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=0s) 互联网底层安全缺失与根区签名的多方协作在谈到根区 DNSSEC 密钥签名的深远影响时，发言人将其与互联网历史上的关键节点相提并论，指出：“I would compare this to the arrival of the World Wide Web in the early 1990s in terms of its enabling capability of course we'll see whether that prediction holds up but it's a very powerful step.”（从赋能的角度来看，我会把这比作 1990 年代初期万维网的诞生；当然我们还要看这个预言能否经得起时间检验，但这确实是非常强有力的一步。）之所以需要迈出这一步，根本原因在于互联网作为一种网络体系，其底层基础架构在设计之初就缺乏安全验证机制。当用户在网络上接收到数据时，根本无法从底层确凿证实这些信息确实来自预期的源头。这一安全漏洞直接导致了现实风险：当普通用户尝试访问银行网站时，黑客有可能通过域名篡改将其劫持到仿冒站点。尽管业界一直在部署各种控制措施以降低风险，但对于普通终端用户而言，判断所见数据是否真实是一项极其复杂的专业技术难题，现有工具往往无法提供百分之百的信任保障。为了让终端用户对所访问目标的真实性树立起充分信心，一个由管理 DNS 根区的三大核心实体组成的设计团队应运而生：负责根区维护运营的 VeriSign、美国商务部（US Department of Commerce）以及 ICANN。该团队旨在保留原有三方管理框架的同时，将现代密码学安全机制深度植入根区体系。在过去一年中，团队展开了全球范围的技术咨询，深入走访网络运营商、DNS 服务提供商及协议专家，征求各方对整体方案的反馈并排查潜在隐患。全球社区给出了压倒性的正面支持，业界普遍迫切希望根区能够尽快完成签名，并对设计方案给予了高度认可。 - 涉及机构：VeriSign、美国商务部（US Department of Commerce）、ICANN。 - 核心问题：互联网底层缺乏身份源认证能力，用户易遭受 DNS 劫持与冒充攻击。 - 解决目标：在不破坏现有根区协作架构的前提下，为 DNS 根区引入基于加密签名的信任链。 --- ### [01:46](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=106s) 严苛透明的仪式流程与物理安保机制密钥签名并非黑箱作业，而是一场旨在追求极致透明度的严谨仪式。整个过程有着如同精密戏剧般的执行脚本，每一个步骤都被详细规范，并置于聚光灯下接受全流程录像与现场监督。发言人特别澄清了外界的猎奇偏见：“It's not anything where people hum or have some sort of strange you know ritual or anything like that I think sometimes it gets misunderstood it's just a very formal process.”（这绝不是什么人们聚在一起哼唱、搞什么奇怪仪轨的事情，外界有时会产生误解，这纯粹是一个极其正式的专业流程。）现场有大约 30 到 35 人在场近距离观察，部分人员还直接承担了操作步骤。仪式的安保标准达到甚至超越了最高级别的联邦防护规格。现场设备存放在美国总务管理局（GSA）认证的 5 级（Class 5）保险箱内。这些保险箱配备了高灵敏度的地震传感器与门禁传感器；只要警报系统启动，任何未关闭并锁死保险箱门的操作都会导致整个控制区被自动锁闭，参会人员在门未安全锁定前甚至无法离开房间。整个设施布满了警报装置，任何未经授权的人员接近都会立即触发全场警报。在所有人见证下，工程师从保险箱中取出硬件安全模块（HSM）加密箱，并在其硬件隔离环境中生成根区公私钥对。随后，系统会现场打印出该 2048 位（2048-bit）RSA 密钥的哈希值（Hash，简短摘要版本），并分发给在场的每一位见证人。见证人们可以比对监视器上的生成过程与手中的哈希指纹，以亲历者的身份证明现场绝无任何作弊或偷梁换柱的行为，确认密钥完全在符合规范的受控流程中诞生。 ```mermaid flowchart TD accTitle: 根区密钥签名仪式现场流程 accDescr: 展示从金库提取设备到生成2048位密钥并进行多方审计验证的完整流程。 subgraph SEC["物理安全验证 (GSA Class 5)"] S1["地震与门禁传感器布防"] --> S2["双人审计开箱取出设备"] S2 --> S3["门禁锁死联动确保全封闭"] end subgraph GEN["硬件密码机生成"] G1["激活加密硬件模块 (HSM)"] --> G2["生成 2048-bit RSA 密钥对"] G2 --> G3["现场计算并打印密钥哈希值"] end subgraph AUDIT["透明监督与见证"] A1["30-35 名现场见证人与全程录像"] A2["比对哈希摘要以核对监视器数据"] A3["确认无袖中藏牌 (完全合规)"] end SEC --> GEN GEN --> AUDIT ``` - 现场参与规模：约 30 至 35 人全流程直击与监督。 - 物理安保级别：GSA Class 5 联邦最高安全等级保险箱，集成地震传感器与闭门防脱离锁定联动。 - 密钥规格：2048 位（2048-bit）RSA 根区密钥签名密钥（KSK）。 - 验证方式：现场计算并打印密钥哈希摘要分发给与会代表留存核对。 --- ### [03:22](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=202s) 受信社区代表制度与双重应急保障架构为了确保密钥的信任完全扎根于整个互联网社区，ICANN 引入了“受信社区代表”（Trusted Community Representatives, TCR）机制。全球共选出至少 21 位受信任的社区代表，其中 14 位出席了本次仪式。他们负责掌控开启和操作硬件加密设备所需的智能卡。这意味着从密钥生成之日起，ICANN 本身就无法单方面调用或签署密钥，任何操作都必须有互联网社区代表的实质介入与授权。整个代表体系被划分为两个核心角色群体，形成了两套既相互制约又互为备份的容灾机制： 1. **密码官员（Crypto Officers）**：他们持有存放于保险箱内保管箱的物理钥匙，保管箱内装有日常操作所需的智能卡。之所以不让他们把智能卡直接带离现场，是出于灾难应急考虑。发言人解释道，面对类似“9·11”恐怖袭击等极端突发灾难，若外部交通中断导致人员无法赶赴现场，ICANN 必须确保系统仍有能力维持运行；在最极端的恢复场景下，官方可以通过钻开保管箱（drill the safe deposit box）来强制取出卡片。 2. **恢复密钥持有者（Recovery Key Shareholders）**：用于应对美东和美西两处互备的数据中心全部覆灭的灾难性场景。这些代表各自随身持有一张封装在银行级防篡改安全袋（tamper-evident bags）中的智能卡。这些卡片存储的并不是根私钥本身，而是用于解密备份密钥的加密密钥分片。整个机制采用了门限密码学方案，唯有至少 5 位恢复密钥持有者在极端事件后齐聚一堂，才能重新拼凑并重构出解密密钥。在这种制度设计下，从设备的开启、使用到再次封存，期间每一个环节都拥有完整的监控录像与审计跟踪记录（audit trail），足以向全球任何关心网络安全的人确凿证明：根密钥自始至终处于不可篡改、无人能私自触碰的绝对安全状态。 ```mermaid flowchart LR accTitle: TCR 两级信任与应急保障机制 accDescr: 展示密码官员与恢复密钥持有者的权责划分及极端灾难下的恢复机制。 subgraph CO["日常签名授权：密码官员 (Crypto Officers)"] direction TB C1["持有金库保管箱物理钥匙"] C2["卡片封存于两处安全设施内"] C3["极端情况下允许技术强拆钻探取卡"] C1 --> C2 --> C3 end subgraph RK["终极容灾恢复：恢复密钥持有者 (TCR Shareholders)"] direction TB R1["各自随身保管防篡改袋 (Tamper-evident Bag)"] R2["卡内存储加密密钥分片 (Key Shares)"] R3["全球至少 5 人集结重构私钥"] R1 --> R2 --> R3 end CO -->|"保障高可用性 (Cannot Fail)"| SYS["DNSSEC 根密钥操作体系"] RK -->|"双数据中心全毁之极度灾难"| SYS ``` - TCR 规模：全球遴选至少 21 名受信社区代表，本次仪式到场 14 名。 - 双中心冗余：ICANN 在美国东海岸与西海岸分别部署了同等高防护级别的互备设施。 - 门限重构要求：恢复密钥持有者中必须至少有 5 人同时到场，方可拼合密钥分片重建加密私钥。 - 审计追溯：全程无盲区视频监控，具备从提取到封存的完整证据链（audit trail）。 --- ### [05:39](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=339s) 层次化信任架构的历史里程碑与未来图景在 2048 位 RSA 根密钥对成功生成的那一刻，现场响起了热烈的掌声。一位技术先驱向全场强调了这一历史时刻不仅限于域名系统本身：“More has happened here today than meets the eye; an infrastructure has been created for a hierarchical security system which can be purposed and repurposed in a number of different ways.”（今天在这里所发生的事情，其意义远超肉眼所见；我们为一个层次化的安全体系奠定了基础设施，而它未来能以各种不同的方式被赋予和重塑用途。）发言人进一步预测，虽然构建该系统的初衷仅仅是为了确保域名解析能够准确返回经过验证的真实 IP 地址、杜绝网络劫持，但在更长远的未来，这一层层递进、严密锚定的信任根基与层次化认证架构，必将被拓展迁移到网络空间中更多需要极高强身份认证（strong authentication）的核心场景中。根区密钥签名的顺利落成，标志着互联网发展史上树立起了一座里程碑：互联网正式从完全不设防的“尽力而为”基础拓扑，跨入了拥有全局可验证密码学信任锚点的新纪元。 - 里程碑成果：成功生成 2048 位 RSA 根密钥签名密钥（KSK）密钥对。 - 核心愿景：超越 DNS 查询安全本身，为整个互联网生态提供多用途的层次化公钥认证基础设施（Hierarchical Security System）。 ## Notable quotes > [05:39](https://www.youtube.com/watch?v=b9j-sfP9GUU&t=339s) More has happened here today than meets the eye; an infrastructure has been created for a hierarchical security system which can be purposed and repurposed in a number of different ways. ## Mentioned ICANN, VeriSign, 美国商务部 (US Department of Commerce), DNSSEC, KSK (Key Signing Key), HSM (Hardware Security Module), GSA (General Services Administration), TCR (Trusted Community Representatives), World Wide Web ## Video description Highlights and a description of the June 16, 2010 Key Signing Ceremony. [Source](https://www.youtube.com/watch?v=b9j-sfP9GUU)

Source quotes

[5:39] More has happened here today than meets the eye; an infrastructure has been created for a hierarchical security system which can be purposed and repurposed in a number of different ways.

Original transcript

[0:00] I would compare this to the uh arrival [0:03] of the worldwide web in the early 1990s [0:05] in terms of its enabling capability of [0:09] course we'll see whether that prediction [0:11] holds up but it's a very powerful step [0:13] the internet as a network and its [0:15] fundamental layer has no security in it [0:18] so you cannot really identify when you [0:20] receive some information across the [0:21] network that it came from the place that [0:23] you already thought it came from so this [0:26] has a couple of problems there's always [0:27] the potential that somebody who tried to [0:30] go to their Bank website will be sent [0:31] somewhere else and you try and put [0:33] controls around that to make that less [0:34] likely the trouble is for an end user [0:37] the question of whether you're seeing [0:38] authentic data is a complex technical [0:40] issue and end users need tools to be [0:42] able to identify whether it's true or [0:44] not um the tools in many cases uh don't [0:48] give 100% Assurance so what we're trying [0:51] to do is add some additional tools some [0:52] additional framework to allow that end [0:54] user to have more confidence in the [0:56] place they're going being authentic so [0:59] what we have is a collaboration between [1:01] three entities who are altogether [1:03] involved in making the root zone of the [1:05] DNS which is verine the US Department of [1:08] Commerce and Ian uh and what we did is [1:10] we formed a design team to try and build [1:12] a solution that we thought preserved [1:14] that structure with those three [1:15] organizations but added the security [1:18] aspects [1:19] in um and then what we've done since [1:22] then in the last year is a pretty wide [1:24] technical consultation um around the [1:25] world talking to protocol experts and [1:28] and operators of Networks and and DNS [1:30] services to try and get their feedback [1:32] on what our design was and to try and [1:34] find out whether there are aspects of [1:36] this that might cause problems for [1:37] anybody um the feedback we've got has [1:39] been overwhelmingly positive I think uh [1:42] the general summary I would give you is [1:43] that people are very keen for the route [1:44] to be signed and they're very happy with [1:46] the way we're doing it it's a carefully [1:48] scripted ceremony for maximum [1:49] transparency each step is carefully [1:51] lined out uh we have a room full of oh [1:55] wow about 30 35 people that'll be [1:58] watching every every part of this step [2:00] some will be participating in this [2:01] process as well the people will be [2:03] brought into into the room filming [2:06] Begins the whole the whole uh ceremony [2:08] is filmed it's not anything where people [2:11] uh hum or have some sort of strange you [2:13] know ritual or anything like that I [2:14] think sometimes it gets misunderstood [2:16] it's it's just a very formal process [2:18] then there'll be a process of actually [2:20] pulling out equipment from various safes [2:22] these are the class five GSA class 5 [2:24] safe that are used by the federal [2:27] government and they do have seismic [2:29] sensors and they also have uh door [2:31] sensors which would basically lock us [2:34] out when this uh when the alarm systems [2:36] are turned on you can't leave the room [2:38] if this door is not closed and locked [2:40] there's alarm systems in every every uh [2:43] part of this facility uh so that any uh [2:46] unauthorized Personnel immediately set [2:47] off alarms and stuff equipment's pulled [2:49] out um we we go through the steps and we [2:52] generate this key inside this [2:54] cryptographic box and then once that key [2:56] is generated uh we'll have printouts [2:58] with what is called a hash of the key a [3:00] shorthand version not the full key which [3:02] is a 2048 bit key uh but not a full but [3:05] a short version of that that we'll hand [3:06] out to the participants and they'll be [3:08] able to say we were there we saw it [3:10] generated not only that we saw that you [3:13] know there were there were no cards up [3:14] anyone's sleeves we we saw the process [3:17] we we saw it on the [3:18] monitors we we tested this being [3:20] generated properly in order to engender [3:23] trust in this process we've we've made [3:25] sure to bring in um we' we've got 21 at [3:29] least 21 trusted Community [3:30] Representatives what we call them for [3:32] this particular meeting we'll have 14 of [3:33] them uh they're involved in the process [3:36] in the sense that they will have control [3:39] over various uh smart cards that is [3:42] generated in this process that enable [3:44] this cryptographic device to operate so [3:47] once this key is generated not only were [3:49] they part of the generation but now [3:50] every time we want to use this I can by [3:53] itself cannot use this we need the [3:55] involvement of the internet Community [3:57] there are two sets of people that are [3:59] what we call crypto officers and [4:00] recovery key [4:02] shareholders in the highly unlikely [4:05] event that we lose both East Coast and [4:06] West Coast facilities I can has built [4:08] two sets um similar level of security [4:12] and and safety and backups if they all [4:14] go away we need some way to [4:17] recover um so what these recovery key [4:19] shareholders hold is a smart card which [4:22] is a piece of a key but not the not the [4:26] root key but piece of a key used to [4:28] encrypt the key in Tamp Revenant bags [4:31] standard Tamp Revenant bags that you [4:33] that that Banks use and they're [4:34] responsible for those so and we've set [4:37] it up so that we need a minimum of five [4:39] of those people to come together to [4:42] recreate that encryption key the crypto [4:45] officers on the other hand we're going [4:46] to give them physical keys to a safe [4:49] deposit box that we have built inside [4:51] one of these two safes that actually has [4:52] a smart cards in there and you know you [4:55] might ask well you know why aren't we [4:58] giving them the cards [5:00] this system has to operate it cannot [5:02] fail so if we have a 911 situation or [5:04] something where these people cannot [5:06] travel here we have to be able to get at [5:08] these keys so in the extreme case where [5:10] we need to recover this thing we can [5:13] drill so the idea is just to keep it as [5:15] as safe as we possibly can and provide [5:17] assurance that it hasn't been tampered [5:19] with that nobody has had access to it [5:21] since the last authorized event where [5:23] the key was brought out to be used um so [5:25] that's why we're very careful taking it [5:26] out and we're very careful storing it [5:28] and we make sure that that whole time [5:29] between people being in the room we have [5:31] a complete audit trail with surveillance [5:33] and everything else to be able to [5:34] demonstrate to the satisfaction of [5:36] anybody who cares to ask the question [5:38] this the secret key is safe more has [5:40] happened here today than it meets the [5:43] eye uh and infrastructure has been [5:45] created for a hierarchical security [5:48] system which can be purposed and [5:52] repurposed in a number of different ways [5:54] and so I would predict that although [5:56] we've started out putting this system [5:57] together to assure that the domain name [6:01] lookups return valid internet addresses [6:05] that in the long run this hierarchical [6:07] structure of trust will be applied to a [6:09] number of other functions that require [6:12] strong [6:13] authentication and so you will have seen [6:16] a new major milestone in the internet [6:18] story generating the 204 fit RSA key [6:22] pair okay [6:24] [Applause]