The document provides an overview of the IANA Department within ICANN. It discusses the IANA functions of maintaining unique internet identifiers like domain names, protocol parameters, and internet number resources. It describes the process for reviewing and approving requests to update protocol parameter registries and allocate internet number resources according to established policies. The goal of the IANA Department is to coordinate these systems globally to ensure interoperability of the internet.
Tuan Nguyen presented an update on the IPv4 address pool, IPv4 transfers and new features in MyAPNIC at btNOG 3 in Thimpu, Bhutan from 14 to 18 November 2016.
Universal Acceptance of Internationalized Domain Names (IDN), Email Addresses...APNIC
"Universal Acceptance of Internationalized Domain Names (IDN), Email Addresses (EAI) and New Top Level" by Edmon Chung.
A presentation given at the APNIC 40 Cooperation SIG on Wed 9 Sep 2015.
Presented by Paul Wilson, Director General of APNIC and Chair of APrIGF Multistakeholder Steering Group at the Asia Pacific Internet Leadership Program as part of 2016 APrIGF Taipei
Community Engagement Specialist, Sunny Chendi, provides an update of APNIC's service initiatives and activities at the second Nepal Network Operators Group meeting in Kathmandu.
Senior Training Officer, Sheryl (Shane) Hermoso, outlines the importance of securing Internet routing to prevent route hijacking and prefix mis-origination with RPKI at the recent VNIX/NOG event in Ha Noi in November 2016.
Just what does it mean to be the IANA functions operator? An approachable session aimed at outlining the scope of the role and busting a few of the myths circulating in the community. We’ll explain the types of requests the IANA department processes and the procedures used to fulfill them.
Tuan Nguyen presented an update on the IPv4 address pool, IPv4 transfers and new features in MyAPNIC at btNOG 3 in Thimpu, Bhutan from 14 to 18 November 2016.
Universal Acceptance of Internationalized Domain Names (IDN), Email Addresses...APNIC
"Universal Acceptance of Internationalized Domain Names (IDN), Email Addresses (EAI) and New Top Level" by Edmon Chung.
A presentation given at the APNIC 40 Cooperation SIG on Wed 9 Sep 2015.
Presented by Paul Wilson, Director General of APNIC and Chair of APrIGF Multistakeholder Steering Group at the Asia Pacific Internet Leadership Program as part of 2016 APrIGF Taipei
Community Engagement Specialist, Sunny Chendi, provides an update of APNIC's service initiatives and activities at the second Nepal Network Operators Group meeting in Kathmandu.
Senior Training Officer, Sheryl (Shane) Hermoso, outlines the importance of securing Internet routing to prevent route hijacking and prefix mis-origination with RPKI at the recent VNIX/NOG event in Ha Noi in November 2016.
Just what does it mean to be the IANA functions operator? An approachable session aimed at outlining the scope of the role and busting a few of the myths circulating in the community. We’ll explain the types of requests the IANA department processes and the procedures used to fulfill them.
ICANN 51: Deploying the IETF’s WHOIS ReplacementICANN
What is the future of WHOIS? It’s the Registry Data Access Program, and it’s on its way. Find out more about what this means for you and the Internet community as a whole. We’ll also provide information on how you can take part in shaping the future of registry directory services by contributing to the RDAP roadmap.
The Domain Name System (DNS) is a critical part of Internet infrastructure and the largest distributed Internet directory service. DNS translates names to IP addresses, a required process for web navigation, email delivery, and other Internet functions. However, the DNS infrastructure is not secure enough unless the security mechanisms such as Transaction Signatures (TSIG) and DNS Security Extensions (DNSSEC) are implemented. To guarantee the availability and the secure Internet services, it is important for networking professionals to understand DNS concepts, DNS Security, configurations, and operations.
This course will discuss the concept of DNS Operations in detail, mechanisms to authenticate the communication between DNS Servers, mechanisms to establish authenticity, and integrity of DNS data and mechanisms to delegate trust to public keys of third parties. Participant will be involved in Lab exercises and do configurations based on number of scenarios.
Based on practical operational experience, not all systems (e.g. browsers, spam filters, registration databases, user profiles, ISPs, etc.) work seamlessly when new TLDs are added. Users may experience failures in resolution or other issues with newer TLDs, which in turn impacts consumer trust on the DNS. The issue of the Universal Acceptance of TLDs (Top-Level Domains) is critically related to the introduction of new gTLDs, as well as the introduction of IDN ccTLDs.
Apache NiFi - Flow Based Programming MeetupJoseph Witt
These are the slides from the July 11th Meetup in Toronto for the Flow Based Programming meetup group at Lighthouse covering Enterprise Dataflow with Apache NiFi.
Interested in Internet Governance? Dig into the new Internet Governance infographic to uncover more about the Internet Ecosystem. The infographic is available in Arabic, Chinese, English, French, Russian and Spanish. Download a copy today!
A concise report on the state of your environment, with prescriptive recommendations for how you can improve performance, efficiency and security in up to 14 vital IT domains.
23rd PITA AGM and Conference: Internet number registry services - the next ge...APNIC
APNIC Director General Paul Wilson gives a presentation on the latest developments in IP address registry services, and
their importance to Internet stability and security at the 23rd Pacific Islands Telecommunications Association Annual General Meeting (PITA 23 AGM) and Annual Conference in Nadi, Fiji from 8 to 12 April 2019.
Learn the ins and outs of the Registry Services team and how it supports current and prospective gTLD Registries with their operational needs. We will cover account management, updates on key services provided to registries (e.g., RSEP, contract assignment, etc.) and information on current registry engagement activities. There will also be Q&A to close the session.
Future of Data New Jersey - HDF 3.0 Deep DiveAldrin Piri
Presentation on new features of HDF 3.0 presented on August 8, 2017 to the Future of Data: New Jersey Meetup group. This event was hosted by Honeywell in Morris Plains, NJ.
https://www.meetup.com/futureofdata-princeton/events/240972326/
Join us as we take a deep dive into the architecture of the Salesforce1 Platform, explain how multitenancy actually works, and how it affects you as a developer. Showing the technology we use and the design principles we adhere to, you'll see how our platform teams manage three major upgrades a year without causing any issues to existing development. We'll cover the performance and security implications around the platform to give you an understanding of how limits have evolved. By the end of the session, you'll have a better grasp of the architecture underpinning Force.com and understand how to get the most out of it.
Cleaning up Redundant, Obsolete and Trivial Data to Reclaim Capacity and Mana...Index Engines Inc.
Data grows at a rate of 40-60% each year, but as capacity is expanded, redundant, obsolete and trivial user data - ROT - is clogging corporate networks resulting in unnecessary risk and expense.
Depending on industry, 40-70% of this data has no business value. Harnessing ROT growth will not only control expenses by reducing or eliminate storage upgrades, but also minimize risk.
Index Engines data profiling software supports ROT analysis and data disposition that ranges from terabytes to petabytes of enterprise content. It provides search, reporting, disposition and defensible deletion of data.
http://www.indexengines.com/storage-management/solutions-for/rot-analysis
IP addressing and IPv6, presented by Paul Wilson at IETF 119APNIC
Paul Wilson, Director General of APNIC delivers a presentation on IP addressing and IPv6 to the Policymakers Program during IETF 119 in Brisbane Australia from 16 to 22 March 2024.
APNIC Foundation, presented by Ellisha Heppner at the PNG DNS Forum 2024APNIC
Ellisha Heppner, Grant Management Lead, presented an update on APNIC Foundation to the PNG DNS Forum held from 6 to 10 May, 2024 in Port Moresby, Papua New Guinea.
Registry Data Accuracy Improvements, presented by Chimi Dorji at SANOG 41 / I...APNIC
Chimi Dorji, Internet Resource Analyst at APNIC, presented on Registry Data Accuracy Improvements at SANOG 41 jointly held with INNOG 7 in Mumbai, India from 25 to 30 April 2024.
APNIC Policy Roundup, presented by Sunny Chendi at the 5th ICANN APAC-TWNIC E...APNIC
Sunny Chendi, Senior Advisor, Membership and Policy at APNIC, presents 'APNIC Policy Roundup' at the 5th ICANN APAC-TWNIC Engagement Forum and 41st TWNIC OPM in Taipei, Taiwan from 23 to 24 April.
DDoS In Oceania and the Pacific, presented by Dave Phelan at NZNOG 2024APNIC
Dave Phelan, Senior Network Analyst/Technical Trainer at APNIC, presents 'DDoS In Oceania and the Pacific' at NZNOG 2024 held in Nelson, New Zealand from 8 to 12 April 2024.
'Future Evolution of the Internet' delivered by Geoff Huston at Everything Op...APNIC
Geoff Huston, Chief Scientist at APNIC deliver keynote presentation on the 'Future Evolution of the Internet' at the Everything Open 2024 conference in Gladstone, Australia from 16 to 18 April 2024.
draft-harrison-sidrops-manifest-number-01, presented at IETF 119APNIC
Tom Harrison, Product and Delivery Manager at APNIC presents at the Registration Protocols Extensions working group during IETF 119 in Brisbane, Australia from 16-22 March 2024
Benefits of doing Internet peering and running an Internet Exchange (IX) pres...APNIC
Che-Hoo Cheng, Senior Director, Development at APNIC presents on the "Benefits of doing Internet peering and running an Internet Exchange (IX)" at the Communications Regulatory Commission of Mongolia's IPv6, IXP, Datacenter - Policy and Regulation International Trends Forum in Ulaanbaatar, Mongolia on 7 March 2024
APNIC Update and RIR Policies for ccTLDs, presented at APTLD 85APNIC
APNIC Senior Advisor, Membership and Policy, Sunny Chendi presented on APNIC updates and RIR Policies for ccTLDs at APTLD 85 in Goa, India from 19-22 February 2024.
Lao Digital Week 2024: It's time to deploy IPv6APNIC
APNIC Development Director Che-Hoo Cheng presents on the importance of deploying IPv6 at the Lao Digital Week 2024, held in Vientiane, Lao PDR from 10 to 14 January 2024.
This 7-second Brain Wave Ritual Attracts Money To You.!nirahealhty
Discover the power of a simple 7-second brain wave ritual that can attract wealth and abundance into your life. By tapping into specific brain frequencies, this technique helps you manifest financial success effortlessly. Ready to transform your financial future? Try this powerful ritual and start attracting money today!
1.Wireless Communication System_Wireless communication is a broad term that i...JeyaPerumal1
Wireless communication involves the transmission of information over a distance without the help of wires, cables or any other forms of electrical conductors.
Wireless communication is a broad term that incorporates all procedures and forms of connecting and communicating between two or more devices using a wireless signal through wireless communication technologies and devices.
Features of Wireless Communication
The evolution of wireless technology has brought many advancements with its effective features.
The transmitted distance can be anywhere between a few meters (for example, a television's remote control) and thousands of kilometers (for example, radio communication).
Wireless communication can be used for cellular telephony, wireless access to the internet, wireless home networking, and so on.
# Internet Security: Safeguarding Your Digital World
In the contemporary digital age, the internet is a cornerstone of our daily lives. It connects us to vast amounts of information, provides platforms for communication, enables commerce, and offers endless entertainment. However, with these conveniences come significant security challenges. Internet security is essential to protect our digital identities, sensitive data, and overall online experience. This comprehensive guide explores the multifaceted world of internet security, providing insights into its importance, common threats, and effective strategies to safeguard your digital world.
## Understanding Internet Security
Internet security encompasses the measures and protocols used to protect information, devices, and networks from unauthorized access, attacks, and damage. It involves a wide range of practices designed to safeguard data confidentiality, integrity, and availability. Effective internet security is crucial for individuals, businesses, and governments alike, as cyber threats continue to evolve in complexity and scale.
### Key Components of Internet Security
1. **Confidentiality**: Ensuring that information is accessible only to those authorized to access it.
2. **Integrity**: Protecting information from being altered or tampered with by unauthorized parties.
3. **Availability**: Ensuring that authorized users have reliable access to information and resources when needed.
## Common Internet Security Threats
Cyber threats are numerous and constantly evolving. Understanding these threats is the first step in protecting against them. Some of the most common internet security threats include:
### Malware
Malware, or malicious software, is designed to harm, exploit, or otherwise compromise a device, network, or service. Common types of malware include:
- **Viruses**: Programs that attach themselves to legitimate software and replicate, spreading to other programs and files.
- **Worms**: Standalone malware that replicates itself to spread to other computers.
- **Trojan Horses**: Malicious software disguised as legitimate software.
- **Ransomware**: Malware that encrypts a user's files and demands a ransom for the decryption key.
- **Spyware**: Software that secretly monitors and collects user information.
### Phishing
Phishing is a social engineering attack that aims to steal sensitive information such as usernames, passwords, and credit card details. Attackers often masquerade as trusted entities in email or other communication channels, tricking victims into providing their information.
### Man-in-the-Middle (MitM) Attacks
MitM attacks occur when an attacker intercepts and potentially alters communication between two parties without their knowledge. This can lead to the unauthorized acquisition of sensitive information.
### Denial-of-Service (DoS) and Distributed Denial-of-Service (DDoS) Attacks
Bridging the Digital Gap Brad Spiegel Macon, GA Initiative.pptxBrad Spiegel Macon GA
Brad Spiegel Macon GA’s journey exemplifies the profound impact that one individual can have on their community. Through his unwavering dedication to digital inclusion, he’s not only bridging the gap in Macon but also setting an example for others to follow.
Multi-cluster Kubernetes Networking- Patterns, Projects and GuidelinesSanjeev Rampal
Talk presented at Kubernetes Community Day, New York, May 2024.
Technical summary of Multi-Cluster Kubernetes Networking architectures with focus on 4 key topics.
1) Key patterns for Multi-cluster architectures
2) Architectural comparison of several OSS/ CNCF projects to address these patterns
3) Evolution trends for the APIs of these projects
4) Some design recommendations & guidelines for adopting/ deploying these solutions.
Multi-cluster Kubernetes Networking- Patterns, Projects and Guidelines
IANA: Who, What, Why?
1.
2. IANA: Who, What, Why?
(or, Why the IANA functions are less interesting than you thought)
Elise Gerich, Kim Davies
IANA Department
3. IANA Department — Who Are We?
Elise Kim Naela Michelle
Pearl Amanda Selina Paula
Andres Punky Marilia
4. What Are the IANA Functions?
• In 1998, ICANN was established as the steward and
operator of the IANA functions
• The IANA Department within ICANN maintains the
registries of the Internet’s unique identifiers
• The unique identifiers include protocol parameters,
Internet numbers and domain names
• The IANA Department maintains these lists according
to policies adopted by Internet names, numbers and
protocol standards communities
5. Why Does the IANA Department Exist?
• The IANA Department within ICANN coordinates the
Internet unique identifier systems needed to ensure the
Internet interoperates globally
• If computers did not use the same system of identifiers
and numbers to talk to one another, the system would
not interoperate
• The authoritative registries are used by vendors, service
providers, businesses, application developers and
others to innovate and expand the use of the Internet
8. Unique Identifiers
Internet Protocol
IP Header Flags
Port Numbers
Type-of-Service Values
MIME and Media Types
Access Types
Event Codes
Telephone Routing over IP
Address Families
Application Protocols
Attributes
Capabilities
IP Telephony Administrative
Domain Numbers
Transmission Control Protocol
Header Flags
Cryptographic Algorithms
MPTCP Handshake Algorithms
Option Kind Numbers
Media Types
Structured Syntax Suffixes
Sub-Parameter Registries
Comprehensive index of protocol parameter registries at
iana.org/protocols
9. Where do protocol parameter registries come from?
• The Internet Engineering Task Force (IETF) community
writes Internet Drafts (I-Ds)
• When approved by the leadership of the IETF, these I-Ds
become official Requests for Comments (RFCs)
• Many RFCs contain guidance to the IANA Department:
– Instructions on the creation of a unique registry for
protocol parameters
– Registration policy
– Initial registrations and reserved values
10. What is the IANA Department’s role with protocol parameter registries?
• Before RFC approval:
– Review
• After RFC approval:
– Implementation
– Maintenance
11. Reviewing Internet Drafts before RFC approval
Work closely with the IETF community to make sure the “IANA
Considerations” section of I-Ds is clear
7. IANA Considerations
7.1. Registry for the fedfsAnnotation Key Namespace
This document defines the fedfsAnnotation key in Section
4.2.1.6. The fedfsAnnotation key namespace is to be managed by
IANA. IANA is to create and maintain a new registry entitled
"FedFS Annotation Keys". The location of this registry should
be under a new heading called "Federated File System (FedFS)
Parameters". The URL address can be based off of the new
heading name, for example:
http://www.iana.org/assignments/fedfs-parameters/ ...
Future registrations are to be administered by IANA using the
"First Come First Served" policy defined in [RFC5226].
Registration requests MUST include the key (a valid UTF-8 string
of any length), a brief description of the key's purpose, and an
email contact for the registration. For viewing, the registry
should be sorted lexicographically by key. There are no initial
assignments for this registry.
12. Implementation and Maintenance for protocol
• After RFC approval:
– Creation of new registries and/or updates to
existing registries
– Maintain through accepting registration requests
from the Internet community
– Follow the registration policy for new registrations
and modification to existing registrations
– Update references
13. How many registries does the IANA Department maintain?
over
2,800
protocol parameter
registries and
sub-registries
14. Request
What type of protocol parameter
is being requested?
Registration Policy
Look at the named registry to determine
which registration policy to follow.
Defining RFC determines the policy.
Processing and Evaluation
Follow the appropriate process
according to registration policy
Consult with experts if required
Gather more information from
requester if needed
Update Registry
Make protocol parameter assignment
in registry
Notify the requester the registration
is complete
Processing Protocol Parameter Requests
15. Request for
a new
Media Type
Review request
Are all the fields
complete?
Send to
technical expert
for review
Add media
type to the
registry
My media
type registration
is complete!
Confirm request
is complete
with the
requester
Processing Protocol Parameter Requests
16. Requests per month
ICANN processes approximately 4,000 protocol
parameter requests per year
362 337 320 361 339 333 356 322 349 330 271 385
Sep Oct Nov DecJan
2014
Feb Mar Apr May Jun Jul Aug
17. Performance Targets
• Performance standards were developed collaboratively
with the IETF to supplement the existing MoU between
ICANN and the IETF
• Began reporting in 2007 on the Service Level Agreement
deliverables
• SLA is reviewed, modified and approved annually
Jan
99%
Feb
98%
Mar
99%
Apr
99%
May
100%
Jun
99%
Jul
100%
Aug
99%
SLA Met
KPIs Met
2014 Sep
100%
Oct
99%
Nov
100%
Dec
99%
20. Deterministic Decision Making
• The policies have deterministic formulas governing
when an RIR can get more and how much they
can get
• IPv4 is allocated on a schedule and not by request
• IPv6 and AS Numbers are allocated on receipt of a
justified request
• Staff validate what an RIR reports against what it
publishes via its daily stats reports
21. Allocation Types
• Formula + Request
(IPv6 and ASN allocations)
• Formula + Schedule
(IPv4 allocations)
• IETF Allocation Procedures
(Non-Unicast addresses)
22. Formula + Request
n ≤ 1 → 1 ×
n > 1 → n ×
n = (6mo usage)×18
Request
Comes from an RIR
Do they qualify?
Less than half of a /12 in reserve
Not enough to last 9 months
What do they get?
or
/12 block
/12 block
/12 block
23. Using input data from RIRs
Reserved (14676)
Assigned (0)
Available (52305)
Allocated (3951)
RIPE NCC IPv6 Pool
(As at 2015-02-03; Millions of /48 addresses)
25. Allocate and Communicate (2)
Communicate
allocation to the
operations community
Communicate
allocation to the
RIR
26. Formula + Schedule
SEP
1
MAR
Communicate results
After the formula is applied per the schedule, the results are
communicated to the RIRs and operations community, and
the IANA registry is updated
iana.org/assignments/ipv4-recovered-address-space
Use formula posted online
ICANN publishes the formula used to make selection as
open source available for anyone to inspect
github.com/icann/ipv4-recovery-algorithm
Allocate twice per year
Allocations happen on a pre-defined schedule 1
28. Performance Targets
• Formal performance standards consultation in
2012
• Have met or exceeded all targets in 15 of 16
months since public reporting began in 2013
32. Event Triggers Request
An event such as a change in TLD
operator, routine maintenance
(technical or staffing change) or a
natural disaster triggers the need
for a change request.
33. REGISTRY ENTRY FOR A TOP-LEVEL DOMAIN
Operator Recognized Company or Organization
Formal Legal Name, Physical Address
Contacts Administrative Contact
Name, Job Title,
Company, Address,
Phone, Fax, Email
Technical Contact
Name, Job Title,
Company, Address,
Phone, Fax, Email
Technical
configuration
Data that goes in the root zone
Authoritative name servers
IP addresses of name servers
DNSSEC (“DS”) records
Metadata Courtesy information not tied to operations
URL to Operator’s website, location of WHOIS
service, domain converted to A-label, language etc.
36. ☑
☑
☑
ALL GOOD!
Policy Check
ICANN checks that the change re-
quest meets policy and technical
requirements and confirms consent
from the appropriate parties. If
issues are found, ICANN clarifies
with the TLD operator. Then, ICANN
forwards the request to NTIA for
authorization to proceed.
37. Technical
Name Servers are responding
Name Servers return correct data
that matches the request
DNS data can be verified using the
supplied DNSSEC DS records
Supplied email addresses work
Consent
Existing contacts agree to change
New contacts agree to their new
responsibilities
Other impacted TLDs agree
Regulatory
Request meets legal requirements
Well-formedness
Supplied data is clear, well-formed
and consistent
Transfer of responsibility
Meets policy requirements for
transfers (differs between ccTLDs
and gTLDs)
38. CHANGE
OPERATOR!
CHANGE
OPERATOR!
ccTLDs
ALL GOOD!ALL GOOD!
CONTRACT
Change request reflects
outcome of a consensus
building process that
happened within the
country.
gTLDs
Change request reflects
outcome of an
evaluation and
contracting process
conducted elsewhere in
ICANN according to
GNSO policies.
39. + PUBLISH
VERIFIED
Implement changes
After authorization to proceed, any
technical changes to the root zone are
implemented. This includes applying a
tamper-evident seal using DNSSEC, and
distributing the updated root zone file to
root server operators. The Root Zone
Database is updated with the changes.
Verification
Changes that satisfy the policy requirements are
transmitted to NTIA for verification. NTIA reviews
the change and then gives authorization to
proceed with publishing the change.
40. The Root Key Signing Key
• As part of its root zone related functions, the
IANA Department manages the key signing
key, used to secure the DNS with the DNSSEC
protocol.
• An auditable process of performing key signing
ceremonies to use this key is conducted using
members of the community as key participants.
41. The DNSSEC root key is stored in a device
known as a hardware security module
(HSM) whose sole purpose is to securely
store cryptographic keys. The device is
designed to be tamper proof. If there is an
attempt to open it, the contents will
self-destruct.
42. Seven smart cards exist that can turn on
each device. The device is configured such
that 3 of the 7 smart cards must be present
to make it useable.
43. Each smart card is given to a different
ICANN community member, known as
a trusted community representative.
To access the key signing key, therefore,
at least three of these TCRs need to be
present.
44. The HSM is stored inside a high-security
safe, which can only be opened by a
designated person, the safe security
controller. The safe is monitored with
seismic and other sensors.
45. The safes are stored in a secure room which
can only opened jointly by two designated
persons, the ceremony administrator and
the internal witness. The room is
monitored with intrusion and motion sen-
sors.
46. The safe room is located within a larger
room where ceremonies are performed
involving the TCRs and other persons.
Ceremonies are recorded on video,
witnessed by the participants and others,
and audited by a third party audit firm.
Access to the room needs to be granted
by another designated person, the
physical access control manager, who
is not on-site.
47. US West KMF
El Segundo, California
US East KMF
Culpeper, Virginia
The ceremony rooms, known as
key management facilities, are located
within two guarded facilities, one each
on the US West and East coasts.
48. The ceremonies
• Approximately four times a year, the TCRs and others
meet to use the HSMs to sign keys to be used for the
root zone.
• The process is streamed and recorded, with external
witnesses watching every step. All materials (videos,
code, scripts, etc.) are posted online at iana.org/
dnssec
• The purpose is to ensure trust in the process.
DNSSEC only provides security if the community is
confident the HSMs have not been compromised.
50. Security at IANA
• Security at IANA is not just DNSSEC
• Dedicated workflow systems for IANA functions,
independent of broader ICANN systems
• Access limited to IANA roles
• Separation of user-facing and staff-facing
systems
• Regular third-party audits, including SOC2
audit by PwC of key IANA systems
51. Performance
Comprehensive service level performance reporting at
iana.org/performance
Jan
123
Feb
77
Mar
81
Apr
90
May
75
Jun
91
Jul
85
Aug
94
KPIs Met 84% 95% 97% 100% 100% 94% 95% 95%
SLA Met
Number
of requests
8.1 8.1 7.4 12.5 8.2 7.0 10.0 9.2Average
days
end-to-end
Sep
67
Oct
56
Nov
75
87% 88% 91%
6.8 15.3 7.3
Dec
71
96%
8.1
Number of requests refers to root zone changes in C.5.2 Root Audit report
KPI refers to Timeliness metric for Root Zone File and WHOIS Database Change Requests
SLA refers to all targets for all domain-related metrics in the C.4.4 standards report
53. How big is the job?
Request count: 1 January 2014 — 31 December 2014
TLD count: As at 1 February 2015
Domain related requests include processing .int, .arpa and other non-root related requests
Domain-related
requests
1,183
Number-related
requests
5 Protocol-related
requests
4,065 General
enquiries
1,120
Top Level Domain
Delegations
810
Number Resource
Registries
13
Protocol Parameter
Registries
2,800+
Third party
audits
2
Key signing
ceremonies
4
54. Satisfaction by customer group
IANA Functions Customer Survey 2014
http://www.iana.org/reports/2014/customer-survey-20141217.pdf
Trusted Community Representatives
Requesters of routine root zone changes
Regional Internet Registries
Requesters of .int zone changes
IESG members
Requesters of protocol parameter assignments
100%
92%
100%
92%
90%
95%
Very Satisfied &
Satisfied
Dissatisfied &
Very Dissatisfied
55. Root Processing Times
IANA Monthly Root Dashboard — January 2015
http://www.iana.org/performance/root-processing-times
Measurement period: 2014-12-16 to 2015-01-15
N/A
8.9
10
8
38
6
6
22
0
7.8
12.4
4.7
6.9
1.4
Number of requests Average processing time (days)
Nameserver (NS) records
DNSSEC (DS) records
Admin contact change
Tech contact change
Metadata change
Delegation/redelegation
Root server update
56. Create registries based on
policies from the community
The IANA Department does The IANA Department doesn’t
Create nor interpret policy
Maintain existing registries
Allocate number resources
Determine what can be a domain
name
Choose TLD managers
Publish all registries for general
public use
57. Summary
• IANA Department maintains the registries of
unique numbering systems that keep the
Internet interoperating.
• Most IANA registries are straightforward, and
are not generally known to the end-user.
• High profile, hierarchically-delegated registries
are used for the Domain Name System and
Number Resources. IANA Dept. maintains the
global “root” for these.
58. Thank you!
Website iana.org
Service level reporting iana.org/performance
Functional areas iana.org/protocols
iana.org/numbers
iana.org/domains
More background iana.org/about