Title: State of the IANA Nov 05
1State of the IANANov 05
- David Conrad
- Vancouver ICANN Meeting
- 11/29/05
2Overview
- Introduction
- First Impressions
- IANA Automation Efforts
- Root Zone Statistics
- Observations
- How You Can Help
- Summary
3Introduction
- IANA Were from IANA, were 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)
4Who Am I?
- Ive 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 Im new here
5What IANA Does
- Root Zone Management
- Protocol Parameter Registry Management
- Protocol numbers, port numbers, Private
Enterprise Numbers, etc. - Internet Draft Review
- IPv4,6 Address Management
- Autonomous System Number Management
- .INT Registry
6First 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
7IANA 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
8IANA Organization
9Operations
- 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
10Receive and Validate Root Zone Modification
11Sub-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
12Root Zone number of new tickets
Max 34 (Aug) Min 15 (Feb) Total new requests
for 05 220 Slightly increasing trend
AKA Feb, 05
AKA Nov, 05
13Root Zone number of completed tickets
Max 55 (Aug) Min 9 (Feb) Total completed
requests for 05 249 Trend increasing more
quickly than new tickets ? queue reduction
AKA Nov, 05
AKA Feb, 05
14Root Zone number of tickets in queue
Max queue depth 81 (Apr) Min queue depth 18
(Oct) Queue size being reduced, Queue projected
to be empty Apr 06
AKA Nov, 05
AKA Feb, 05
15Root Zone processing time in days
Max 103 days (Feb) Min 8 days (Oct) Trend
decreasing to externally constrained minimum
AKA Feb, 05
AKA Nov, 05
16Observations
- 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
17Insufficient 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
18Selected Critical Requirements
19My 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
20How You Can Help
- If you run into a problem, let me know
- mailto//iana_at_iana.org (for now)
- Soon mailto//issues_at_iana.org (ticketed)
- mailto//david.conrad_at_icann.org
- 1-310-301-3869 (my direct line)
- Help with IANA services in beta testing
- Provide feedback
- Critique existing IANA services
- Constructive critiques preferred ?
21Summary
- 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
22Questions?
?