State of the IANA Nov ‘05 David Conrad Vancouver ICANN Meeting 11/29/05

State of the IANANov ‘05

David ConradVancouver ICANN Meeting

11/29/05

State of the IANA, Vancouver ICANN, Nov '05

Overview

• Introduction• First Impressions• IANA Automation Efforts• Root Zone Statistics• Observations• How You Can Help• Summary


Introduction

• IANA: “We’re from IANA, we’re here to help” Bringing you Names, Numbers, and Resources since 1972(ish)

• New staff in the IANA David Conrad (IANA GM), Kim Davies (Names Liaison), Sarah Trehern (Project Specialist)

• Not new staff in the IANA Barbara Roseman (IANA Operations Manager), Michelle Cotton (Project Specialist), Naela Sarras (Project Specialist), Pearl Liang (Project Specialist)


Who Am I?

• I’ve been mucking about in the Internet since 1983… Team lead for one of the first commercial TCP/IP

Implementations for the IBM PC Joint IBM/University of Maryland project

Worked on the University of Hawaii/NASA/NSF PACCOM project Brought first Internet connectivity to AU, HK, JP , KR, NZ

Employee #7 at Internet Initiative Japan, Inc. First commercial ISP in Japan

Founder and first Director General of APNIC Executive Director of Internet Software Consortium

Led the BINDv9 development effort Founder and CTO of Nominum, Inc.

High performance name and addressing technologies Been author/co-author on several name/address RFCs & IDs

• Proviso: “I’m new here”


What IANA Does

• Root Zone Management• Protocol Parameter Registry Management Protocol numbers, port numbers, Private Enterprise Numbers, etc.

• Internet Draft Review• IPv{4,6} Address Management• Autonomous System Number Management• .INT Registry


First Impressions

• Being new at IANA (and having a bit of background in IANA related activities) I noticed a few things… Staff very dedicated and hard working Operations are relatively smooth

If less automated than desired Infrastructure lacking

Albeit usually functional

• But… “Everything is wonderful until you know something about it” – Dzoey

Much to clean up


IANA Staff

• Currently 7 full-time employees 2 Managers, 1 Liaison, 4 Project Specialists Looking to hire 1-2 more

Another Liaison and another Project Specialist

• Why so many people? More to do than you might think. Almost everything IANA does is technically trivial, but…

Conforming to policies and contractual obligations Almost all non-technical and externally constrained

Playing catch up “Mistakes were made”


IANA Organization

Kurt PritzVP, Operations

Michelle CottonProject Specialist

Naela SarrasProject Specialist

Pearl LiangProject Specialist

Sarah TrehernProject Specialist

Barbara RosemanOperations Manager, IANA

Kim DaviesNames Liaison

VacantNumbers Liaison

David ConradGeneral Manager, IANA

Paul TwomeyPresident/CEO

ICANN


Operations

• 2.5 FTE dedicated to Root Management High priority due to geo-political realities

• Internal processes reasonably well defined Many exceptions to standard processes

Most requests are unique in one way or another

• Even most simple requests have a tortuous path to take For example…


Receive and Validate Root Zone Modification


Sub-Optima

• Multiple ticketing system Request Tracker (http://bestpractical.com/rt) “All ticketing systems suck. RT sucks less’

“That Which Shall Not Be Named” Home grown, does some things better than RT

• Multiple database MySQL, MS Excel, MS Access, text files Same data in multiple places

• No consistent data collection Few metrics


Root Zone – number of new tickets

0

5

10

15

20

25

30

35

40

38383 38411 38442 38472 38502 38533 38564 38595 38625 38656

new requests Linear (new requests)

AKA Feb, ‘05 AKA Nov, ‘05

Max: 34 (Aug)Min: 15 (Feb)Total new requests for ‘05: 220Slightly increasing trend


Root Zone – number of completed tickets

0

10

20

30

40

50

60

38383 38411 38442 38472 38502 38533 38564 38595 38625 38656

completed requests Linear (completed requests)

Max: 55 (Aug)Min: 9 (Feb)Total completed requests for ‘05: 249Trend increasing more quickly than new tickets queue reduction

AKA Nov, ‘05AKA Feb, ‘05


Root Zone – number of tickets in queue

0

10

20

30

40

50

60

70

80

90

38383 38411 38442 38472 38502 38533 38564 38595 38625 38656

queue size Linear (queue size)

Max queue depth: 81 (Apr)Min queue depth: 18 (Oct)Queue size being reduced,Queue projected to be empty: Apr ‘06

AKA Nov, ‘05AKA Feb, ‘05


Root Zone – processing time in days

(Open requests projected to 18 November)

0

20

40

60

80

100

38383 38411 38442 38472 38502 38533 38564 38595 38625 38656

processing time in days (completed tickets) processing time in days (projected) Linear (processing time in days (completed tickets))

Max: 103 days (Feb)Min: 8 days (Oct)Trend decreasing to externally constrained minimum

AKA Nov, ‘05

AKA Feb, ‘05


Observations

• Data quality issues for collecting statistics Data collection improvements needed (and planned) Data presentation improvements under development

• Root Zone processing New ticket rate increasing, but processing them quickly to maintain and improve IANA service.

• Much of the delays people experience now are due to queue depth or external delays Queue being reduced Fighting history and historically driven circumstances


Insufficient Automation

• Not a very heavy load for Root Management But very, very sensitive

Politically, economically, and religiously, not technically

• Many IANA tasks require significant human intervention However not as much as is currently the case

• IANA is currently evaluating automation systems to aid Root Management E-IANA: evaluation underway

Hampered by confidentiality statements “reg-soft”: code to be delivered soon

DNSSEC focus Home grown: under development (sort of)

ICANN IT has lots of things to do

• IANA (now?) not affected by NIH Syndrome


Selected Critical Requirements

DNSSEC zone signing

External callout for validation, variable policy

Email interface with multiple authenticators

DNSSEC child delegation handling and pass-through

External audit-ability (per requester)

Web interface ideally with differentiated access

DNSSEC data validation

Internal audit-ability of everything

Local and remote programmatic APIs for special tool development


My Vision for IANA

• IANA is a service organization. Really. No, Really.• Our customers are (in alphabetic order, not

priority): IETF/IESG/IAB Regional Internet Registries TLD Registries (existing and new) International treaty organizations

• Goals Responsiveness and communication Accuracy and correctness Excellence in service

Goal Question Metric “Customer Satisfaction Survey”

“Always make new mistakes” Never repeat old ones

Restore trust in IANA


How You Can Help

• If you run into a problem, let me know mailto://[email protected] (for now)

Soon: mailto://[email protected] (ticketed) mailto://[email protected] +1-310-301-3869 (my direct line)

• Help with IANA services in beta testing Provide feedback

• Critique existing IANA services Constructive critiques preferred


Summary

• Most IANA processes improving• More automation necessary

Request validation and processing Data collection and presentation

• Mistakes were made (understaffing, wrong staffing, de-emphasis/de-prioritization) but ICANN has taken extensive steps to never repeat them Much higher priority and emphasis, new staff, increased budget, new focus on responsiveness, efficiency, and automation


Questions?

¿?

Documents

State of the IANA Nov ‘05 David Conrad Vancouver ICANN Meeting 11/29/05