100 likes | 236 Views
Updating the TLD Root Server data in the 21 st Century. A Shared Responsibility. Project Goals. Depoliticise role of the Root Server system - Open and transparent process Decentralise Root Zone Data with info directly from TLD Registry
E N D
Updating the TLD Root Server data in the 21st Century. A Shared Responsibility
Project Goals • Depoliticise role of the Root Server system - Open and transparent process • Decentralise Root Zone Data with info directly from TLD Registry • Enhance the Accuracy, Efficiency, Security and Stability of the DNS • All members of the Registry community have equal access
Description • Enable the designated Internet registries and the respective local Internet communities (including governments) to exercise local supervision of their components in the Root Zone. FOR MORE INFO... http://www.centr.org/docs/2005/07/response-usg.html
Historical Analysis • Pre-1997 • Registries instructed the IANA to update their records; authorised changes were made within 24 hours. • In 1998 • Jon Postel (the IANA) undertook a Root Server experiment without the permission of the USG • In 1998 • USG asserted oversight over Root Server changes.
Historical Analysis, Cont. • Industry recognised USG assertion! • NTIA has provided pro-bono an excellent non-discriminatory checking function of Root changes. • Registry Community prefer US does not “authorise changes” but verifies process FOR MORE INFO... http://www.ntia.doc.gov/ntiahome/domainname/USDNSprinciples_06302005.htm (30th June 2005)
Verification Procedures • Currently system highly dependent on non-secure email • Security is human inspection – time consuming • Take existing policy/procedure and automate to improve performance FOR MORE INFO... Description: www.shared-responsibility.net/current-process.pdf
Proven Technology • Industry Authentication Standards are adopted • PGP • MD5 • x509 • Web Login-passwd • Human verification
Test-bed (open to all) • Resources allocated to this project • Funding • People • Equipment • Software trials from various locations • External evaluation Report to the Community.
Phase 1 Phase 2 Phase 3 June July Aug Sept Oct Nov Dec Jan Feb Mar Apr Schedule • Phase 1 – Evaluate existing technologies and define Test-bed • Phase 2 – Open access to Test-bed. Community beta test/review • Phase 3 – Report findings How to be involved... This is a peer-to-peer project = all participants are equal Email: Testbed@Shared-Responsibility.net
Related Documents www.Shared-Responsibility.net (coming soon!) Email: Testbed@Shared-Responsibility.net