How do I participate? - ICANN

How do I participate? - ICANN
Skip to main content
Search ICANN.org
Log In
Sign Up
Get Started
About ICANN
ICANN for Beginners
Fellowship Program
NextGen@ICANN Program
History
News and Media
Announcements
Blog
Media Resources
Press Releases
Global Newsletters
ICANN News Subscriptions
Regional Reports
Policy
Develop Policy
Operational Design Phase (ODP)
Implement Policy
Community Participation Guidelines
Public Comment
Public Comment Home
Upcoming Proceedings
Open Proceedings
Closed Proceedings
About Public Comment
Other Public Consultations
Resources
Board Activities and Meetings
Accountability Mechanisms
Contracted Parties (Registry Operators and Accredited Registrars)
Domain Name Registrants
Contractual Compliance
Domain Name Security Threats
Privacy and Proxy Services
Government Engagement
Careers
Complaints Office
I Need Help
ICANN 25th Anniversary Photo Mosaic
Community
Engagement Calendar
Address Supporting Organization (ASO)
Country Code Names Supporting Organization (ccNSO)
Generic Names Supporting Organization (GNSO)
At-Large Advisory Committee (ALAC)
Governmental Advisory Committee (GAC)
Root Server System Advisory Committee (RSSAC)
Security and Stability Advisory Committee (SSAC)
Quicklinks
Board Activities and Meetings
Data Protection and Privacy
Domain Name Registrants
Engagement Calendar
IANA Services
ICANN Acronyms and Terms
ICANN Grant Program
New gTLD Program
Public Technical Identifiers (PTI)
Open Data
Question About A Domain Name?
Technology @ ICANN
WSIS+20 Outreach Network
Resources
About ICANN
Academic Engagement
Acronyms and Terms
Courses and Learning
ICANN for Beginners
Participate
What ICANN Does
Effect on the Internet
What's Going On Now
How to Participate
Fellowship Program
Committee
Terms & Conditions
NextGen@ICANN Program
President's Corner
ICANN Management Organization Chart
Staff
Careers
In Focus
ICANN Response Planning Framework
DNSSEC
Standards
IANA DNSSEC Root Information
TLD DNSSEC Report
Root Deployment
Deployment Graph
Tools
Training
Key Ceremony
News
Blog Posts
Presentations
Related Sites
GNSO Improvements
Travel Support
Media Resources
ICANN News
About ICANN
Subscribe and Follow
Contacts
Board Activities and Meetings
Accountability
Accountability Mechanisms
Reconsideration
Independent Review Process
Updating the IRP
Ombuds
About the Ombuds Office
Contact the Ombuds Office
Ombuds Office Services
Complaints About Unfairness
Complaints About Harassment
Collaborative Conflict Resolution
Request for Reconsideration
Resources for Community Members
Ombuds Office Accountability
Ombud's Blogs
Empowered Community
Empowered Community Administration
Empowered Community Administration Mailing List
Empowered Community Correspondence
Document Disclosure
Reviews
Organizational Reviews
ALAC
ASO
Board
ccNSO
GNSO
Nominating Committee
RSSAC
SSAC
Technical Liaison Group
Specific Reviews
Accountability & Transparency
Registration Directory Service
Security, Stability, and Resiliency
Competition, Consumer Trust & Consumer Choice
CCT Metrics
Expected Standards of Behavior
Employee Practices and Resources
Enhancing ICANN Accountability – Work Stream 2 Implementation
Governance
Governance Documents
Evolving ICANN’s Multistakeholder Model
Agreements
NTIA IANA Functions' Stewardship Transition
Call for Public Input: Draft Process to Develop the Proposal (8 April-8 May 2014
Process to Develop the Proposal and Next Steps
Registry
Archive
Affirmation of Commitments
AOC Tracking
ccTLD
Partnership Memorandums of Understanding
Registrar
Archive
Annual Reports
Financials
Financial Reports
Policies, Guidelines and Procedures
Annual Disclosure of Payments to Suppliers
Lobbying Disclosures & Contribution Reports
Planning
Strategic Plan
ICANN Strategic Plan for FY26-30
ICANN's Annual Strategy Review Program
ICANN Strategic Plan for FY21-25
Strategic Outlook Trends Program
ICANN Strategic Plan for FY16-20
Operating Plan
Presentations
RFPs
Litigation
Newsletter
Correspondence
2026
2025
2024
2023
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
2002
2001
2000
1999
1998
Quarterly Reports
Groups
2023 ICANN CEO Search Committee
RSSAC
Charter
SSAC
GAC
At-Large
ASO
ccNSO
GNSO
Technical Liaison Group
Technical Experts Group (TEG)
NomCom
Past NomComs
Customer Standing Committee
Root Zone Evaluation Review Committee (RZERC)
Business
Civil Society
Complaints Office
Complaints Report
Domain Name System Abuse
Contractual Compliance
About
Enforcement of DNS Abuse Obligations
Formal Enforcement Notices
Archive
Contractual Compliance Metrics
Blogs
Contractual Compliance Audit Program
Notice of Bankruptcy, Convictions and Security Breaches
Contractual Compliance Reports
Audit Reports
Enforcement of DNS Abuse Mitigation Requirements: Periodic Reviews
Contractual Compliance Monthly Reports
gTLD Registry Compliance
Accredited Registrar Compliance
General Questions
Outreach
Contracted Parties (Registry Operators and Accredited Registrars)
Domain Name Registrants
About Domain Names
ICANN Policies
Registration Data Policies
WHOIS and Registration Data Directory Services
The Domain Name Registration Process
Using Domain Name Registration Data
Keeping Registration Data Accurate
Access and the Evolution of the WHOIS System
Domain Name Industry
Registering Domain Names
Managing Domain Names
Contact Information and WDRP
Securely Managing Your Domain Name
Transferring Domain Names
Renewing Domain Names
Rights and Responsibilities
Spam, Phishing, and Website Content
Trademark Infringement
GDS Metrics
Identifier Systems Security, Stability and Resiliency (OCTO-SSR)
ccTLDs
Background Materials
Agreements
Delegation
Root Zone Database
Model MOU
Workshops
ICANN and ISO
Internationalized Domain Names
Root Zone Label Generation Rules (LGR)
Generation Panel Update
Maximal Starting Repertoire
Proposals for Root Zone Label Generation Ruleset
IDN Variant TLD Implementation
LGR Toolset
IDN ccTLD Fast Track
IDN Implementation Guidelines
Second-Level LGR Reference
Resources
Announcements and Blogs Posts
New gTLD Program
Universal Acceptance Initiative
Make your systems UA-ready
UA Training
UA Day
UA Readiness Evaluations
UA Initiatives
Announcements and Blogs Posts
Policy
Policy Mission
Policy Staff Goals
Presentations
Global Addressing
IPv6 Allocation
ASN Allocation
Post Exhaustion IPv4 Allocation
New RIRs Criteria
Review Procedures
Policy Updates
Operational Design Phase (ODP)
Implementation
Public Comment
Open
Upcoming
Archive
Root Zone KSK Rollover
Technical Functions
Tech Day Archive
ICANN Locations
Report Security Issues
PGP Keys
Certificate Authority
Registry Liaison
Ombudsman
I Need Help
Dispute Resolution
Domain Name Dispute Resolution
Charter Eligibility Dispute Resolution Policy
Providers
Rules
Eligibility Requirements Dispute Resolution Policy
Providers
Rules
Intellectual Property Defensive Registration Challenge Policy
Providers
Rules
Qualification Challenge Policy
Providers
Rules
Restrictions Dispute Resolution Policy
Providers
Rules
Transfer Dispute Resolution Policy
Providers
Uniform Domain Name Dispute Resolution Policy
Policy Document
Providers
Provider Approval Process
Rules
Principal Documents
Proceedings
Historical Documents
Timeline
Name Collision
Registrar Problems
Whois Data Correction
Independent Review Process
Request for Reconsideration
Document
How do I participate?
This page is available in:
English
العربية
Deutsch
Español
Français
Italiano
日本語
한국어
Português
Pусский
中文
In answer to the question:
What is going on now?
, a number of resources including the
public comment webpage
, ICANN
blog
, and
meetings sites
were listed.
Each of these pages also allow for direct and immediate interaction into ICANN's processes. Each public comment box provide a clickable email address where your comments will be sent straight through the public comment forum. All comments made will be reviewed by ICANN staff and included in a summary/analysis at the close of the forum. That summary will then be provided to the body in question and that body will be asked to explicitly refer to it during subsequent discussions.
The blog allows any individual to make their point in response to a posting direct to the author and the organisation - and in most cases receive a quick response. So if you wish to make a point or draw ICANN's attention to something you think it may have missed this is a direct route into the process.
If you would prefer to make your point in the real world, then the ICANN meetings are free and open to all. At each ICANN meeting, there is a Public Forum session that is specifically set aside for anyone that wishes to raise a point by walking up to the microphone and talking directly to Board members and to the rest of the ICANN Community. The vast majority of the other meetings are also open, and often welcome new and interested members.
The Fellowship Program provides a grant of support for up to 50 individuals per ICANN meeting. Successful candidates are members of the Internet community who have met the program's minimum requirements as determined by an independent committee. For more details on this program and how to apply,
go here
.
You needn't even physically be at a meeting in order to have your voice heard. Each meeting has its own interactive website that provides a separate webpage for each session during the meeting week. These pages contain the relevance links for all the remote participation services provided including presentations, audio, video streams and live transcriptions (if available). During public meetings that are also open for comments, comments and questions from remote participants are reviewed by someone in the chat room and are read out to the meeting as a whole.
Supporting organisations and advisory committees
If you wish to get more deeply involved in drawing up documents, rather than commenting on the results of others' work, the solution is to join one of ICANN's supporting organisations or advisory committees.
There are a number of organisations and committees (the
full structure is here
), and you can join whichever most relates to your input - whether as an ISP, a non-commercial company, or just a member of the public. Other members will help explain how ICANN works and how to make the most of your input.
There are three Supporting Organizations and four Advisory Committees, each is explained below with links to their websites where you can find out more about how to join:
GENERIC NAMES SUPPORTING ORGANIZATION
(GNSO)
The GNSO is the main policy-making body of ICANN and comprises of four main groups: registries (companies running generic top-level domains (gTLDs) such as VeriSign for dot-com or Afilias for dot-info); registrars (companies that sell registrations of particular domains e.g. icann.org); commercial users of the Internet; and non-commercial users of the Internet.
The GNSO is currently undergoing significant change following an extensive
independent review process
. As such the information presented below is liable to change and you should check the GNSO website for the latest information on which body is most suitable for you to join.
Commercial and Business Users Constituency
(
external site
)
The business constituency is the voice of commercial Internet users within ICANN. You can find out more about
how to join
on the constituency's website, where you can also follow its work. Membership fees apply, ranging from €160 to €1,000 in 2009.
Non-Commercial Users Constituency
(
external site
)
The Noncommercial Users Constituency is the home for civil society organizations and individuals in ICANN's GNSO. NCUC advocates positions on gTLD-related issues that protect and support noncommercial communication and activity on the Internet. Among its key areas of interest are human rights, freedom of expression, privacy, access to knowledge, diversity and consumer choice, development, and global internet governance. Membership is free of charge, and noncommercial organizations and individuals can fill in an application to join on its
website
.
Not-for-Profit Operational Concerns Constituency (NPOC)
(
external site
)
NPOC represents the operational concerns related to service delivery of not-for-profit and non-governmental organizations within ICANN. NPOC welcomes members who are not-for-profit and non-governmental organizations. These organizations can join NPOC by either completing the online Noncommercial Stakeholders Group (NCSG)
membership form
or completing the NPOC
application form
.
gTLD Registries Constituency
(
external site
)
The registries constituency represents those running gTLD registries. You have to be a registry under contract with ICANN to join and members
meet bi-weekly
.
Registrars Constituency
(
external site
)
The registrars constituency represents companies that register domains for Internet users for a fee. You have to be an ICANN-accredited registrar to join. There is annual membership fee of $500 (as of August 2009). More details on
how to join
are on the constituency's website.
Intellectual Property Constituency
(
external site
)
The IPC represents intellectual property interests within ICANN. To join you can be either an international or national intellectual property organization, a company with a demonstrated interest in intellectual property issues, or an individual with a demonstrated interest in the protection of intellectual property. Each group has its
own application form
and fees vary from $75 to $900 (as of August 2009) depending on which group you belong to.
Internet Service and Connection Providers Constituency
(
external site
)
The ISPCP represents Internet service providers and connectivity providers and you must be an ISP or connectivity provider as well as agreement to participate regularly within the ISPCP. Applicants send the secretariat an email
outlining their credentials
. Statements, notes and meeting minutes can all be found on the ISPCP's website.
AT LARGE ADVISORY COMMITTEE (
ALAC
)
The ALAC is the body that represents the interests of individual Internet users within ICANN.
Global users are represented through small self-forming groups called At Large Structures (ALSes) who are themselves part of Regional At Large Organizations (RALOs).
Any group that supports individuals' ability to share their views on ICANN issues, and that meets a few criteria can register to be an At-Large Structure. Examples include: professional societies; academic and research organizations; community networking groups; consumer advocacy groups; Internet Society chapters; Computer user organizations and Internet civil society groups. There is no application or membership fee.
More information on the
application process
, including downloadable application forms can be found on the At Large website.
The RALOs also have their own regional websites (external sites):
Africa
|
Asia-Pacific
|
Europe
|
Latin America
|
North America
COUNTRY CODE NAMES SUPPORTING ORGANIZATION (
ccNSO
)
The ccNSO represents the managers of country-code top-level domains (ccTLDs) such as Britain's dot-uk registry or Germany's dot-de registry. You have to be a ccTLD manager to join. If you are, an
online application form
is available. Membership is free. You can follow the ccNSO's work through its website, for example through its
Council minutes
.
GOVERNMENTAL ADVISORY COMMITTEE (
GAC
)
The GAC represents governments and governmental organizations. You need to be a formally acknowledged representative of a government or interational organization to become a member. You can
email the GAC's secretariat
for more information.
ADDRESS SUPPORTING ORGANIZATION (
ASO
)
The ASO represents the Regional Internet Registries (RIRs) - companies that oversee the allocation of Internet number resources in particular geographic regions. You would need to be an RIR to join the ASO, however you can follow their work online through its
mailing lists
.
SECURITY AND STABILITY ADVISORY COMMITTEE (
SSAC
)
The SSAC advises the ICANN community and Board on matters relating to the security and integrity of the Internet's naming and address allocation systems. It is an invited-members-only organization. The SSAC produces
reports and advisories
on technical aspects of the Internet's security and stability.
If you care about the Internet and how it evolves, your voice will only be heard if you get involved, so please do take advantage of the different ways there are to interact with ICANN. We look forward to seeing you.
ICANN is not responsible for profile content or verification of user details.
YouTube
Twitter
LinkedIn
Flickr
Facebook
Newsletters
Community Wiki
ICANN Blog
Who We Are
ICANN For Beginners
ICANN Learn
Participate
Groups
Board Members
CEO Corner
Staff
Careers
Public Responsibility
Contact Us
Locations
Report Security Issues
Certificate Authority
Registry Liaison
Ombuds
Complaints Office
Media Resources
Accountability And Transparency
Accountability Mechanisms
Document Disclosure
Independent Review Process
Request for Reconsideration
Empowered Community
Employee Anonymous Hotline Policy and Procedures
Governance
Governance Documents
Agreements
Organizational Reviews
Specific Reviews
Annual Report
Financials
Planning
RFPs
Litigation
Correspondence
Help
I Need Help
Dispute Resolution
Domain Name Dispute Resolution
Name Collision
ICANN Lookup
Registration Data Request Service (RDRS)
Data Protection
Data Privacy Practices
Privacy Policy
Terms of Service
Cookies Policy
© Internet Corporation for Assigned Names and Numbers.
Privacy Policy
Terms of Service
Cookies Policy
Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."

Year pattern in URL — weak evidence, not a verified publication date


RFC 1375: Suggestion for New Classes of IP Addresses | RFC Editor
Skip to content
Info
RFC
1375
:
Suggestion for New Classes of IP Addresses
P. Robinson
Informational
Network Working Group                                        P. Robinson
Request for Comments: 1375                        Tansin A. Darcos & Co.
                                                            October 1992
Suggestion for New Classes of IP Addresses
Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard.  Distribution of this memo is
   unlimited.

Abstract

   This RFC suggests a change in the method of specifying the IP address
   to add new classes of networks to be called F, G, H, and K, to reduce
   the amount of wasted address space, and to increase the available IP
   address number space, especially for smaller organizations or classes
   of connectors that do not need or do not want a full Class C IP
   address.

Table of Contents

   Introduction . . . . . . . . . . . . . . . . . . . . . . . . . .
1
Suggestion for new IP address classes  . . . . . . . . . . . . .
2
Current Class C Address . . . . . . . . . . . . . . . . . .
3
Proposed new Class C Address  . . . . . . . . . . . . . . .
4
Proposed "Class F" address  . . . . . . . . . . . . . . . .
4
Proposed "Class G" address  . . . . . . . . . . . . . . . .
4
Proposed "Class H" address  . . . . . . . . . . . . . . . .
5
Proposed "Class K" address  . . . . . . . . . . . . . . . .
5
Optional selection of routing codes by region  . . . . . . . . .
5
Summary  . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6
Notes  . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6
Security Considerations  . . . . . . . . . . . . . . . . . . . .
7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . .
7
Introduction

   Currently, IP addresses on the Internet are 32-bit quantities which
   are generally represented as four decimal numbers from 0 to 255,
   separated by periods, sometimes called a "dotted" decimal number.
   The current numbering scheme provides in general for three classes of
   networks in general use (A,B, and C), and two other classes of
   networks (D, E).

   The Class A networks assign a large address space for the particular
Robinson                                                        [Page 1]
RFC 1375
New Classes of IP Addresses           October 1992
network to allow up to 254^3 local machines [
1
].  The Class B network
   assigns a somewhat smaller address space for the particular network
   to allow up to 254^2 local machines.  The Class C network assigns a
   still smaller address space for the particular network to allow up to
   254 local machines.

   This memo proposes to assign part of the unused Class C address space
   for smaller networks than are currently available.  The term "Class
   D" is used for the "multicast" capability and addresses in "Class E"
   are reserved for future use.  Therefore, these new features for which
   capability is to be added is being referred to as classes F, G, H and
   K.

Suggestion for new IP address classes

   The most worrisome problem which appears in the literature is the
   possibility of running out of address space for IP addresses. Various
   schemes are being suggested such as subrouting, introduction of
   additional bits, and other possibilities.

   There is an even more serious matter.  In all probability, I suspect
   that eventually the Internet backbone will either become available to
   anyone who wants to use it (like public highways) and the costs paid
   for out of taxes or some other method which gets someone else to pay
   for it, or eventually the Internet will be fully commercialized and
   made available to anyone who wants to buy a permanent connection.
   With the cost of hardware and connections dropping, some Computer
   Bulletin Board Systems (BBSs) which are currently accessible via
   telephone call may become accessible via TELNET or FTP.  When a 9600
   baud connection can be obtained for around the price of a phone line,
   the demand for internet access will skyrocket.  This almost certain
   eventual availability to virtually anyone who wants a connection will
   cause an even greater demand for internet addresses, which will
   exacerbate this situation.  One problem is in the granularity of IP
   addressing, in that the smallest possible IP address one may obtain
   allows for as high as 254 IP addresses.  If someone wanted only to
   put four or five computers on the Internet, more than 240 addresses
   are wasted.

   Many smaller installations would probably be interested either in
   placing their computers and/or servers on the Internet (and perhaps
   helping to pay the cost of running it) or in being able to access the
   Internet directly, and perhaps making facilities on their machines
   available to others; the problem being that IP addresses on Internet
   are not readily available to small classes of users.  Also, the
   possibility exists of eventually placing non-computer and output-only
   devices such as printers, facsimile machines, and visual pagers
   directly on the Internet to allow people to send a message to a local
Robinson                                                        [Page 2]
RFC 1375
New Classes of IP Addresses           October 1992
device simply by directing it to a specific internet site as an E-
   Mail message.

   The scheme proposed by this paper proposes to make a slight change in
   one of the classes of network address in a manner which should not be
   a significant problem for implementing, and should not cause a
   significant hardship as the addresses to use for this purpose are not
   now allocated anyway, and may draw some of the drain which would have
   consumed Class C addresses in large quantity into quantities of Class
   F, H, or K addresses which waste less IP address space.

   This scheme I am proposing is to allow for very small networks (1 or
   2, 1-7, or 1-15, depending on the number of addresses the
   administrator of that site thinks he will need), by reconstructing
   the network address to include what is nominally part of the local
   address.  If bridges and routers (and other hardware and software) do
   not assume that only the last 8 bits make up a local address and
   permit smaller spaces for local addresses, then this method should
   not cause problems. Sites needing less than a close order of 256 IP
   addresses could simply apply for 2 or more contiguous blocks of Class
   F numbers.

   Currently, a Class C address consists of a 32-bit number in which the
   leftmost 3 bits consist of "110" [
2
]:

        The third type of address, class C, has a 21-bit network number
        and a 8-bit local address.  The three highest-order bits are set
        to 1-1-0.  This allows 2,097,152 class C networks.

                        1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |1 1 0|                    NETWORK              | Local Address |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                        Current Class C Address

   This memo proposes to change Class C addresses to be 4-bit numbers
   beginning with "1100":

   The third type of address, class C, has a 20-bit network number and a
   8-bit local address.  The four highest-order bits are set to 1-1-0-0,
   This allows 1,048,576 class C networks.
Robinson                                                        [Page 3]
RFC 1375
New Classes of IP Addresses           October 1992
1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |1 1 0 0|                  NETWORK              | Local Address |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                     Proposed new Class C Address

   This memo then proposes to add four new types of addresses, to be
   referred to as "Class F", "Class G", "Class H", and "Class K" [
3
].
   These would all use part of the "old" class C address by all using IP
   addresses that begin with the 4-bit sequence "1101".  The Class F
   addresses would begin with the binary code sequence "11010", Class G
   addresses begin with "110110", Class H addresses with "1101110", and
   Class K with "1101111".

   Class F addresses will be used for networks having from 1-15 sites
   [
4
], where the number could be expected to exceed 7.  Class F
   addresses are defined as follows:

   The sixth type of address, class F, has a 23-bit network number, and
   a 4-bit local address.  The five highest-order bits are set to 1-1-
   0-1-0.  This allows 16,777,256 class F networks.

                        1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |         |                                             | Local |
   |1 1 0 1 0|                NETWORK                      |Address|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                      Proposed "Class F" address

   Class G is to be defined as follows:

        The seventh type of address, class G, is reserved for future
        use.  The six highest-order bits are set to 1-1-0-1-1-0.

                        1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           |                                                   |
   |1 1 0 1 1 0|              Reserved                             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                      Proposed "Class G" address

   Class H is for small networks which are not expected to exceed 7
Robinson                                                        [Page 4]
RFC 1375
New Classes of IP Addresses           October 1992
connected IP addresses.  Class H is to be defined as follows:

        The eighth type of address, class H, has a 22-bit network
        number, and a 3-bit local address.  The seven highest-order bits
        are set to 1-1-0-1-1-1-0.  This allows 4,194,304 Class H
        addresses [
5
].

                        1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             |                                           |Local|
   |1 1 0 1 1 1 0|              NETWORK                      | Addr|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                      Proposed "Class H" address

   Class K is for sites which either will only have one or two connected
   addresses [
6
].  Class K is to be defined as follows:

        The eighth type of address, class K, has a 25-bit network
        number, and a 1-bit local address.  The seven highest-order bits
        are set to 1-1-0-1-1-1-1.  This allows 33,554,432 Class K
        addresses [
7
].

                        1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           |                                                 |*|
   |1 1 0 1 0 0|              NETWORK                            | |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                       * = Local Address, 1 or 0
                      Proposed "Class K" address

Optional selection of routing codes by region

   Because of the possibility of confusion, some method similar to the
   international dialing plan might be set up, in which bits 5-8 in
   Class F, bits 7-10 in Class H, and bits 6-9 in Class K could be used
   to define what part of the world the particular address is in, in a
   manner similar to the international telephone dialing system, which
   uses the first digit of the international telephone number to
   determine the region being used.  The current method for assigning
   international dialing codes is:
Robinson                                                        [Page 5]
RFC 1375
New Classes of IP Addresses           October 1992
1 North America               6 Oceania, Australia
      2 Africa                      7 Ex-Soviet Union Countries
      3 Europe                      8 Asia
      4 Europe                      9 Mideast
      5 South America and Mexico

   If a similar method is used, I would recommend assigning 0,1,10 and
   11 to North America, 8 and 12 to Asia, and leaving 13 through 15 for
   other areas as needed.  Note that this would simply make some routing
   choices easier, it is not precisely necessary that this be done,
   since currently routing is generally done using the shortest path to
   a site and IP numbers don't really relate to any specific address
   anywhere in the world.

   The number form of a class F, G, H or K address could still be listed
   in the standard form n.n.n.n, as long as it is not assumed that the
   4th chunk number alone identifies a local address and that numbers
   with the same preceding 3 chunks do not necessarily belong to the
   same network.

Summary

   In order to make the address space available, even if the method to
   implement this feature is not presently available, it is suggested
   that Class F, G, H, and K address space should be taken out of Class
   C space and reserved for the purpose of allowing smaller-sized
   networks so that this feature may be made available.  Since Class C
   addresses currently are only using the equivalent of one Class A
   number anyway, this should not cause a problem.

Notes

   [
1
] Common practice dictates that neither an address 0 nor 255 should
       be used in any "dotted" address.

   [
2
] Reynolds, J., and J. Postel, "Assigned Numbers", STD 2,
RFC 1340
,
       USC/Information Sciences Institute, July 1992.

   [
3
] To prevent confusion, no class "I" or "J" address was created by
       this memo.

   [
4
] It is expected that if the higher part of the network address
       occupying the 4-bits to the left of the Class F address are
       neither 0 nor 15, that a class F site could have 16 machines.  If
       the 4-bits to the left are all 0, the Class F site must not use
       number 0.  If the four bits are all 1, the site must not use
       number 15.
Robinson                                                        [Page 6]
RFC 1375
New Classes of IP Addresses           October 1992
[
5
] It may be that Class H numbers are more appropriate for classes
       of addresses that will not have as high a demand for access via
       Internet addresses such as facsimile machines and pagers.  (The
       end digit could be used to determine class of service, i.e., 0
       for tone only, 1 and 2 for numeric only, 3 4 and 5 for
       alphanumeric, and 6 and 7 for facsimile machines.  Or some
       combination of these according to the demand.  Remember,
       Internet won't always be just text messages and file transfers;
       we may eventually see things like voice telephone calls or voice
       data being placed to an Internet address just like calls made
       via the telephone system.  This would require a whole change in
       the way things are done, but it's always best to look at the
       future.

   [
6
] It is suggested that addresses in this range not be assigned
       where the 7 bits to the left of the local number are all the
       same (all 0 or all 1), to allow all Class K addresses to have
       two local addresses.

   [
7
] Different things can be done with different capabilities.  One
       thought was to set up some group of numbers and use them to
       indicate systems which are "gateway" systems, i.e., the top set
       of numbers in Class K could indicate that subnets are required
       after those numbers, similar to the use of an extension number on
       the switchboard of a large organization.   Another possibility is
       to assign some of the numbers to specific classes of devices,
       such as number-only pagers and electronic display devices.

Security Considerations

   Security issues are not discussed in this memo.

Author's Address

   Paul Robinson
   Tansin A. Darcos & Company
   8604 Second Avenue #104
   Silver Spring, MD 20910 USA

   Phone: 202-310-1011
   Telex:   6505066432MCI UW
   E-mail:  TDARCOS@MCIMAIL.COM

Robinson                                                        [Page 7]
RFC
1375
: Suggestion for New Classes of IP Addresses
Informational


ICANN Press Releases | 2026 - ICANN

ICANN Press Releases | 2026 - ICANN
Skip to main content
Search ICANN.org
Log In
Sign Up
Get Started
About ICANN
ICANN for Beginners
Fellowship Program
NextGen@ICANN Program
History
News and Media
Announcements
Blog
Media Resources
Press Releases
Global Newsletters
ICANN News Subscriptions
Regional Reports
Policy
Develop Policy
Operational Design Phase (ODP)
Implement Policy
Community Participation Guidelines
Public Comment
Public Comment Home
Upcoming Proceedings
Open Proceedings
Closed Proceedings
About Public Comment
Other Public Consultations
Resources
Board Activities and Meetings
Accountability Mechanisms
Contracted Parties (Registry Operators and Accredited Registrars)
Domain Name Registrants
Contractual Compliance
Domain Name Security Threats
Privacy and Proxy Services
Government Engagement
Careers
Complaints Office
I Need Help
ICANN 25th Anniversary Photo Mosaic
Community
Engagement Calendar
Address Supporting Organization (ASO)
Country Code Names Supporting Organization (ccNSO)
Generic Names Supporting Organization (GNSO)
At-Large Advisory Committee (ALAC)
Governmental Advisory Committee (GAC)
Root Server System Advisory Committee (RSSAC)
Security and Stability Advisory Committee (SSAC)
Quicklinks
Board Activities and Meetings
Data Protection and Privacy
Domain Name Registrants
Engagement Calendar
IANA Services
ICANN Acronyms and Terms
ICANN Grant Program
New gTLD Program
Public Technical Identifiers (PTI)
Open Data
Question About A Domain Name?
Technology @ ICANN
WSIS+20 Outreach Network
Resources
About ICANN
Academic Engagement
Acronyms and Terms
Courses and Learning
ICANN for Beginners
Participate
What ICANN Does
Effect on the Internet
What's Going On Now
How to Participate
Fellowship Program
Committee
Terms & Conditions
NextGen@ICANN Program
President's Corner
ICANN Management Organization Chart
Staff
Careers
In Focus
ICANN Response Planning Framework
DNSSEC
Standards
IANA DNSSEC Root Information
TLD DNSSEC Report
Root Deployment
Deployment Graph
Tools
Training
Key Ceremony
News
Blog Posts
Presentations
Related Sites
GNSO Improvements
Travel Support
Media Resources
ICANN News
About ICANN
Subscribe and Follow
Contacts
Board Activities and Meetings
Accountability
Accountability Mechanisms
Reconsideration
Independent Review Process
Updating the IRP
Ombuds
About the Ombuds Office
Contact the Ombuds Office
Ombuds Office Services
Complaints About Unfairness
Complaints About Harassment
Collaborative Conflict Resolution
Request for Reconsideration
Resources for Community Members
Ombuds Office Accountability
Ombud's Blogs
Empowered Community
Empowered Community Administration
Empowered Community Administration Mailing List
Empowered Community Correspondence
Document Disclosure
Reviews
Organizational Reviews
ALAC
ASO
Board
ccNSO
GNSO
Nominating Committee
RSSAC
SSAC
Technical Liaison Group
Specific Reviews
Accountability & Transparency
Registration Directory Service
Security, Stability, and Resiliency
Competition, Consumer Trust & Consumer Choice
CCT Metrics
Expected Standards of Behavior
Employee Practices and Resources
Enhancing ICANN Accountability – Work Stream 2 Implementation
Governance
Governance Documents
Evolving ICANN’s Multistakeholder Model
Agreements
NTIA IANA Functions' Stewardship Transition
Call for Public Input: Draft Process to Develop the Proposal (8 April-8 May 2014
Process to Develop the Proposal and Next Steps
Registry
Archive
Affirmation of Commitments
AOC Tracking
ccTLD
Partnership Memorandums of Understanding
Registrar
Archive
Annual Reports
Financials
Financial Reports
Policies, Guidelines and Procedures
Annual Disclosure of Payments to Suppliers
Lobbying Disclosures & Contribution Reports
Planning
Strategic Plan
ICANN Strategic Plan for FY26-30
ICANN's Annual Strategy Review Program
ICANN Strategic Plan for FY21-25
Strategic Outlook Trends Program
ICANN Strategic Plan for FY16-20
Operating Plan
Presentations
RFPs
Litigation
Newsletter
Correspondence
2026
2025
2024
2023
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
2002
2001
2000
1999
1998
Quarterly Reports
Groups
2023 ICANN CEO Search Committee
RSSAC
Charter
SSAC
GAC
At-Large
ASO
ccNSO
GNSO
Technical Liaison Group
Technical Experts Group (TEG)
NomCom
Past NomComs
Customer Standing Committee
Root Zone Evaluation Review Committee (RZERC)
Business
Civil Society
Complaints Office
Complaints Report
Domain Name System Abuse
Contractual Compliance
About
Enforcement of DNS Abuse Obligations
Formal Enforcement Notices
Archive
Contractual Compliance Metrics
Blogs
Contractual Compliance Audit Program
Notice of Bankruptcy, Convictions and Security Breaches
Contractual Compliance Reports
Audit Reports
Enforcement of DNS Abuse Mitigation Requirements: Periodic Reviews
Contractual Compliance Monthly Reports
gTLD Registry Compliance
Accredited Registrar Compliance
General Questions
Outreach
Contracted Parties (Registry Operators and Accredited Registrars)
Domain Name Registrants
About Domain Names
ICANN Policies
Registration Data Policies
WHOIS and Registration Data Directory Services
The Domain Name Registration Process
Using Domain Name Registration Data
Keeping Registration Data Accurate
Access and the Evolution of the WHOIS System
Domain Name Industry
Registering Domain Names
Managing Domain Names
Contact Information and WDRP
Securely Managing Your Domain Name
Transferring Domain Names
Renewing Domain Names
Rights and Responsibilities
Spam, Phishing, and Website Content
Trademark Infringement
GDS Metrics
Identifier Systems Security, Stability and Resiliency (OCTO-SSR)
ccTLDs
Background Materials
Agreements
Delegation
Root Zone Database
Model MOU
Workshops
ICANN and ISO
Internationalized Domain Names
Root Zone Label Generation Rules (LGR)
Generation Panel Update
Maximal Starting Repertoire
Proposals for Root Zone Label Generation Ruleset
IDN Variant TLD Implementation
LGR Toolset
IDN ccTLD Fast Track
IDN Implementation Guidelines
Second-Level LGR Reference
Resources
Announcements and Blogs Posts
New gTLD Program
Universal Acceptance Initiative
Make your systems UA-ready
UA Training
UA Day
UA Readiness Evaluations
UA Initiatives
Announcements and Blogs Posts
Policy
Policy Mission
Policy Staff Goals
Presentations
Global Addressing
IPv6 Allocation
ASN Allocation
Post Exhaustion IPv4 Allocation
New RIRs Criteria
Review Procedures
Policy Updates
Operational Design Phase (ODP)
Implementation
Public Comment
Open
Upcoming
Archive
Root Zone KSK Rollover
Technical Functions
Tech Day Archive
ICANN Locations
Report Security Issues
PGP Keys
Certificate Authority
Registry Liaison
Ombudsman
I Need Help
Dispute Resolution
Domain Name Dispute Resolution
Charter Eligibility Dispute Resolution Policy
Providers
Rules
Eligibility Requirements Dispute Resolution Policy
Providers
Rules
Intellectual Property Defensive Registration Challenge Policy
Providers
Rules
Qualification Challenge Policy
Providers
Rules
Restrictions Dispute Resolution Policy
Providers
Rules
Transfer Dispute Resolution Policy
Providers
Uniform Domain Name Dispute Resolution Policy
Policy Document
Providers
Provider Approval Process
Rules
Principal Documents
Proceedings
Historical Documents
Timeline
Name Collision
Registrar Problems
Whois Data Correction
Independent Review Process
Request for Reconsideration
Document
ICANN Press Releases | 2026
This page is available in:
English
العربية
Español
Français
Pусский
中文
2026
|
2025
|
2024
|
2023
|
2022
Press Release: APIGA Celebrates 10 Years of Developing the Next Generation of Internet Leaders
SINGAPORE – 27 July 2026
한국어
Press Release: ICANN86 Policy Forum Brings Global Internet Community to Seville
Brussels – 28 May 2026
Press Release: ICANN Announces Next Major Internet Security Update
Los Angeles – 20 May 2026
Press Release: ICANN Opens Application Window for New Generic Top-Level Domains
LOS ANGELES – 30 April 2026
Português
ICANN85 in Mumbai Highlights Collaboration to Strengthen a Secure and Resilient Internet
Mumbai, INDIA – 9 March 2026
ICANN Launches Universal Acceptance Curriculum Program, Facilitating a Multilingual Internet
24 February 2026
Press Release: ICANN CEO Highlights 2026 Domain Expansion Opportunities During Türkiye Visit
ISTANBUL – 19 February 2026
Türkçe
Press Release: ICANN85 in Mumbai: Strengthening the Single, Interoperable Internet for All
New Delhi, INDIA – 5 February 2026
हिंदी
Press Release: ICANN Nominating Committee Seeks Accomplished Business Leaders for ICANN Board of Directors
LOS ANGELES – 28 January 2026
Press Release: ICANN Launches Caribbean Premiere of ICANN Near You in Guyana
MONTEVIDEO – 28 January 2026
Português
ICANN is not responsible for profile content or verification of user details.
YouTube
Twitter
LinkedIn
Flickr
Facebook
Newsletters
Community Wiki
ICANN Blog
Who We Are
ICANN For Beginners
ICANN Learn
Participate
Groups
Board Members
CEO Corner
Staff
Careers
Public Responsibility
Contact Us
Locations
Report Security Issues
Certificate Authority
Registry Liaison
Ombuds
Complaints Office
Media Resources
Accountability And Transparency
Accountability Mechanisms
Document Disclosure
Independent Review Process
Request for Reconsideration
Empowered Community
Employee Anonymous Hotline Policy and Procedures
Governance
Governance Documents
Agreements
Organizational Reviews
Specific Reviews
Annual Report
Financials
Planning
RFPs
Litigation
Correspondence
Help
I Need Help
Dispute Resolution
Domain Name Dispute Resolution
Name Collision
ICANN Lookup
Registration Data Request Service (RDRS)
Data Protection
Data Privacy Practices
Privacy Policy
Terms of Service
Cookies Policy
© Internet Corporation for Assigned Names and Numbers.
Privacy Policy
Terms of Service
Cookies Policy
Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."

ICANN Press Releases | 2026 - ICANN

Year found in title: 'ICANN Press Releases | 2026 - ICANN'


Page not found - Internet Society

Page not found - Internet Society
Skip to content
About Us
Mission
Board of Trustees
Community
Team
Transparency
2026 Action Plan
Our Work
Connectivity
How the Internet Works
Internet Governance
Internet Policy
Privacy
Security
News and Insights
Blog
News
Impact Stories
Resources
Get Involved
Become an individual member
Become an organization member
Join a fellowship program
Take a free online course
Attend an event
Member login
en
en
fr
es
More languages
Search
×
♥ Donate
404: Page not found
The page you are looking for doesn’t exist or an other error occurred.
Go Home
Can't find what you are looking for?
Search
×
Latest news
Advancing a Connected Future for Indigenous Communities
Connectivity
Advancing a Connected Future for Indigenous Communities
Community-led Internet initiatives are empowering Indigenous communities worldwide through meaningful connectivity, digital inclusion, and self-determined digital futures.
How One Alum Helped Build a Community of Internet Leaders
Internet Governance
How One Alum Helped Build a Community of Internet Leaders
Amged B. Shwedhy, an Internet Society alumnus, has helped bring Internet governance discussions to Libya.
The Tribal Broadband Bootcamps Celebrate Their Five-Year Anniversary
Connectivity
The Tribal Broadband Bootcamps Celebrate Their Five-Year Anniversary
We celebrate five years of Tribal Broadband Bootcamps, which have given Indigenous people hands-on training in community networks.
Questions? Get in touch.
Contact us
Stay connected.
Get news, updates, and information about ways we can all grow and protect the Internet.
LinkedIn
This field is for validation purposes and should be left unchanged.
Email
(Required)
You may opt out at any time.
Terms and Conditions
and
Privacy Policy
.
Secondary navigation
Our Community
Member sign-in
Individual members
Chapters
Special interest groups (SIGs)
Organization members
Our Ecosystem
Internet Engineering Task Force (IETF)
Public Interest Registry (PIR)
Internet Society Foundation
Internet Society Pulse
Internet Hall of Fame
NDSS Symposium
Our Resources
About the Internet
ARPANET & the history of the Internet
Impact stories
Resource library
Newsroom
Blog
Follow Internet Society on LinkedIn
Follow Internet Society on Facebook
Follow Internet Society on Instagram
Follow Internet Society on YouTube
Internet Society RSS Feed
Corporate links navigation
© 2026 Internet Society |
Privacy Notice
|
Terms of Use
|
Legal
|
Annual Reports and Financials
|
Contact Us
|
Careers
|
Follow Us
|
Affiliated Sites


Our Work - Internet Society

Our Work - Internet Society
Skip to content
About Us
Mission
Board of Trustees
Community
Team
Transparency
2026 Action Plan
Our Work
Connectivity
How the Internet Works
Internet Governance
Internet Policy
Privacy
Security
News and Insights
Blog
News
Impact Stories
Resources
Get Involved
Become an individual member
Become an organization member
Join a fellowship program
Take a free online course
Attend an event
Member login
en
en
fr
es
More languages
Search
×
♥ Donate
Our Work
Our Work
Working for a community-driven, trustworthy Internet for everyone.
The Internet is a transformative force. But not everyone benefits from it equally. Around 2 billion people still lack connectivity. And, increasingly, our online safety is threatened by the inability to trust that our personal information is in our control. The stakes have never been higher. That’s why we partner with communities to help people overcome their unique barriers to connectivity, be they geographic, technical, regulatory, or financial.
As part of our 2030 Strategy, we are focusing on addressing two critical global challenges facing the Internet:
Lack of trust in the Internet
. Because everyone deserves an Internet experience that is safe, secure, and protects them online.
Global inequality
. Because people everywhere need to have access to affordable, reliable, and resilient Internet.
Read about our activities for the upcoming year in
our 2026 Action Plan
.
The Issues We Care About
The Issues We Care About
Connectivity
How the Internet Works
Internet Governance
Internet Policy
Privacy
Security
How We Succeed
How We Succeed
Through our Foundation, we invest in projects that advance our mission. In partnership with our global community, we build and deploy infrastructure, provide decision-makers with data to develop, maintain, and protect the Internet, help shape and advocate for policies that impact how the Internet works, and empower future Internet leaders with the skills and expertise they need to succeed.
Community
Our global community is passionate about developing the Internet’s full potential. Individual, chapter, and organization membership are just a handful of ways to be part of our community.
Advocacy
From convening policy leaders, to informing courts through Amicus Brief filings, our localized and collaborative advocacy work helps lower connectivity barriers and create a safer Internet.
Empowerment
We provide Internet leaders with the expertise they need to make decisions about and for the Internet. We offer individuals and communities trainings to help them connect and be safe online.
Investing in the Internet
Foundation grantees drive change that helps communities overcome challenges, reduce inequalities, and create a more connected world.
Measurement
On the Pulse platform, we track and measure the state of the Internet: its availability, evolution, and resilience.
Our Work in Action
Our Work in Action
19 June 2026
From Refugee to Digital Leader: How Justin Is Helping to Connect Rhino Camp
11 June 2026
Community-Centered Connectivity Initiatives Earn Viddy Awards Recognition
28 May 2026
From Email to Case Study: What We Learned About Connecting Refugee Communities in Just One Year
23 March 2026
Connecting Remote Glaciers to Protect Communities in Kyrgyzstan
29 December 2025
Encryption Making Africa Safer: Internet Society Hosts Encryption Advocacy Workshop for African Civil Society
15 December 2025
Learning to Build and Use the Internet in Rhino Refugee Camp
9 December 2025
Why the UN’s Next Decision on Internet Governance Matters for Everyone
26 November 2025
A Once-Overlooked Tool: How Community Networks Connected Haiti and the World
5 November 2025
2025 Postel Awardee David Clark, an Architect and Implementer of the Internet
14 October 2025
Our Voices Are Making a Difference in the Fight for Strong Encryption
9 September 2025
The Data Dump Dilemma: Why Public Digital Platforms Risk Failing the People They Serve
5 September 2025
Your Internet Access Is at Risk. We’re Speaking Up
18 August 2025
How to Achieve Universal Connectivity
11 August 2025
What Is Internet Resilience?
8 August 2025
The Internet of Wonder: How a Scientific Livestream Became a Cultural Phenomenon
4 August 2025
The Power of Volunteers: Connecting an Indigenous Community in Panama
1 August 2025
Is Your IXP at Risk of Becoming a “Zombie”?
25 July 2025
A UK Government Order Threatens the Privacy and Security of All Internet Users
25 July 2025
Encryption Makes Us Powerful: Internet Society Hosts Encryption Advocacy Workshop for European Civil Society
22 July 2025
How YOU Run the Internet
15 July 2025
How Standard Setters Run the Internet
8 July 2025
How the Technical Community Runs the Internet
4 July 2025
From Experience to Curiosity
2 July 2025
Dangerous US Supreme Court Decision for Online Privacy and Security
Become a part of the movement.
Become a part of the movement.
Ready to join us in our work towards a community-driven, trustworthy Internet for everyone? Become an Internet Society member today.
Join Us
Become a part of the movement.
Ready to join us in our work towards a community-driven, trustworthy Internet for everyone? Become an Internet Society member today.
Join Us
Image copyright:
© Sea Nexus Event, © Gustavo Castellanos Echazú, © Stonehouse Photographic, © Sea Nexus Event, © Sea Nexus Event, © Candice Ward/The Internet Society, © Sagar Biswas from Pixabay,
© Internet Society Zimbabwe Chapter, © Nicolas Olivier, © ITU, © Internet Society, © José Elizeche
The copyright of the items displayed in the Our Work in Action feed can be found on their respective pages.
Stay connected.
Get news, updates, and information about ways we can all grow and protect the Internet.
Phone
This field is for validation purposes and should be left unchanged.
Email
(Required)
You may opt out at any time.
Terms and Conditions
and
Privacy Policy
.
Secondary navigation
Our Community
Member sign-in
Individual members
Chapters
Special interest groups (SIGs)
Organization members
Our Ecosystem
Internet Engineering Task Force (IETF)
Public Interest Registry (PIR)
Internet Society Foundation
Internet Society Pulse
Internet Hall of Fame
NDSS Symposium
Our Resources
About the Internet
ARPANET & the history of the Internet
Impact stories
Resource library
Newsroom
Blog
Follow Internet Society on LinkedIn
Follow Internet Society on Facebook
Follow Internet Society on Instagram
Follow Internet Society on YouTube
Internet Society RSS Feed
Corporate links navigation
© 2026 Internet Society |
Privacy Notice
|
Terms of Use
|
Legal
|
Annual Reports and Financials
|
Contact Us
|
Careers
|
Follow Us
|
Affiliated Sites


ICANN Management Organization Chart (March 2026)

1
Pg.Executive Team | As of 16 M arch 2026B
oard of Directors

2
Pg.Executive Team | As of 16 M arch 2026B
oard of DirectorsE
lizabeth FieldO
mbudsK
urtis LindqvistP
resident and Chief Executive Officer

3
Pg.Executive Team | As of 16 M arch 2026K
urtis LindqvistPresident and Chief Executive OfficerC
assia OliveiraDirector, Office of the CEOG
lobal Communications and Language ServicesSally Newell CohenSVP, Global CommunicationsG
lobal Domains and StrategyTheresa SwinehartSVP, Global Domains & StrategyG
lobal Government Engagement and Contractual ComplianceJamie HedlundSVP, Global Government Engagement and ComplianceG
lobal Human ResourcesGino MarlianiSVP, Global Human ResourcesG
overnanceJohn JeffreyGeneral Counsel and SecretaryO
ffice of the CFOXavier CalvezSVP, Planning & Chief Financial Officer (CFO)O
ffice of the Chief Technology OfficerJohn CrainSVP & Chief Technology OfficerP
olicy Development SupportRuss WeinsteinSVP, Policy Development SupportS
takeholder EngagementSally CostertonSVP, Global Stakeholder Engagement


Operational Design Phase - ICANN

Operational Design Phase - ICANN
Skip to main content
Search ICANN.org
Log In
Sign Up
Get Started
About ICANN
ICANN for Beginners
Fellowship Program
NextGen@ICANN Program
History
News and Media
Announcements
Blog
Media Resources
Press Releases
Global Newsletters
ICANN News Subscriptions
Regional Reports
Policy
Develop Policy
Operational Design Phase (ODP)
Implement Policy
Community Participation Guidelines
Public Comment
Public Comment Home
Upcoming Proceedings
Open Proceedings
Closed Proceedings
About Public Comment
Other Public Consultations
Resources
Board Activities and Meetings
Accountability Mechanisms
Contracted Parties (Registry Operators and Accredited Registrars)
Domain Name Registrants
Contractual Compliance
Domain Name Security Threats
Privacy and Proxy Services
Government Engagement
Careers
Complaints Office
I Need Help
ICANN 25th Anniversary Photo Mosaic
Community
Engagement Calendar
Address Supporting Organization (ASO)
Country Code Names Supporting Organization (ccNSO)
Generic Names Supporting Organization (GNSO)
At-Large Advisory Committee (ALAC)
Governmental Advisory Committee (GAC)
Root Server System Advisory Committee (RSSAC)
Security and Stability Advisory Committee (SSAC)
Quicklinks
Board Activities and Meetings
Data Protection and Privacy
Domain Name Registrants
Engagement Calendar
IANA Services
ICANN Acronyms and Terms
ICANN Grant Program
New gTLD Program
Public Technical Identifiers (PTI)
Open Data
Question About A Domain Name?
Technology @ ICANN
WSIS+20 Outreach Network
Resources
About ICANN
Academic Engagement
Acronyms and Terms
Courses and Learning
ICANN for Beginners
Participate
What ICANN Does
Effect on the Internet
What's Going On Now
How to Participate
Fellowship Program
Committee
Terms & Conditions
NextGen@ICANN Program
President's Corner
ICANN Management Organization Chart
Staff
Careers
In Focus
ICANN Response Planning Framework
DNSSEC
Standards
IANA DNSSEC Root Information
TLD DNSSEC Report
Root Deployment
Deployment Graph
Tools
Training
Key Ceremony
News
Blog Posts
Presentations
Related Sites
GNSO Improvements
Travel Support
Media Resources
ICANN News
About ICANN
Subscribe and Follow
Contacts
Board Activities and Meetings
Accountability
Accountability Mechanisms
Reconsideration
Independent Review Process
Updating the IRP
Ombuds
About the Ombuds Office
Contact the Ombuds Office
Ombuds Office Services
Complaints About Unfairness
Complaints About Harassment
Collaborative Conflict Resolution
Request for Reconsideration
Resources for Community Members
Ombuds Office Accountability
Ombud's Blogs
Empowered Community
Empowered Community Administration
Empowered Community Administration Mailing List
Empowered Community Correspondence
Document Disclosure
Reviews
Organizational Reviews
ALAC
ASO
Board
ccNSO
GNSO
Nominating Committee
RSSAC
SSAC
Technical Liaison Group
Specific Reviews
Accountability & Transparency
Registration Directory Service
Security, Stability, and Resiliency
Competition, Consumer Trust & Consumer Choice
CCT Metrics
Expected Standards of Behavior
Employee Practices and Resources
Enhancing ICANN Accountability – Work Stream 2 Implementation
Governance
Governance Documents
Evolving ICANN’s Multistakeholder Model
Agreements
NTIA IANA Functions' Stewardship Transition
Call for Public Input: Draft Process to Develop the Proposal (8 April-8 May 2014
Process to Develop the Proposal and Next Steps
Registry
Archive
Affirmation of Commitments
AOC Tracking
ccTLD
Partnership Memorandums of Understanding
Registrar
Archive
Annual Reports
Financials
Financial Reports
Policies, Guidelines and Procedures
Annual Disclosure of Payments to Suppliers
Lobbying Disclosures & Contribution Reports
Planning
Strategic Plan
ICANN Strategic Plan for FY26-30
ICANN's Annual Strategy Review Program
ICANN Strategic Plan for FY21-25
Strategic Outlook Trends Program
ICANN Strategic Plan for FY16-20
Operating Plan
Presentations
RFPs
Litigation
Newsletter
Correspondence
2026
2025
2024
2023
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
2002
2001
2000
1999
1998
Quarterly Reports
Groups
2023 ICANN CEO Search Committee
RSSAC
Charter
SSAC
GAC
At-Large
ASO
ccNSO
GNSO
Technical Liaison Group
Technical Experts Group (TEG)
NomCom
Past NomComs
Customer Standing Committee
Root Zone Evaluation Review Committee (RZERC)
Business
Civil Society
Complaints Office
Complaints Report
Domain Name System Abuse
Contractual Compliance
About
Enforcement of DNS Abuse Obligations
Formal Enforcement Notices
Archive
Contractual Compliance Metrics
Blogs
Contractual Compliance Audit Program
Notice of Bankruptcy, Convictions and Security Breaches
Contractual Compliance Reports
Audit Reports
Enforcement of DNS Abuse Mitigation Requirements: Periodic Reviews
Contractual Compliance Monthly Reports
gTLD Registry Compliance
Accredited Registrar Compliance
General Questions
Outreach
Contracted Parties (Registry Operators and Accredited Registrars)
Domain Name Registrants
About Domain Names
ICANN Policies
Registration Data Policies
WHOIS and Registration Data Directory Services
The Domain Name Registration Process
Using Domain Name Registration Data
Keeping Registration Data Accurate
Access and the Evolution of the WHOIS System
Domain Name Industry
Registering Domain Names
Managing Domain Names
Contact Information and WDRP
Securely Managing Your Domain Name
Transferring Domain Names
Renewing Domain Names
Rights and Responsibilities
Spam, Phishing, and Website Content
Trademark Infringement
GDS Metrics
Identifier Systems Security, Stability and Resiliency (OCTO-SSR)
ccTLDs
Background Materials
Agreements
Delegation
Root Zone Database
Model MOU
Workshops
ICANN and ISO
Internationalized Domain Names
Root Zone Label Generation Rules (LGR)
Generation Panel Update
Maximal Starting Repertoire
Proposals for Root Zone Label Generation Ruleset
IDN Variant TLD Implementation
LGR Toolset
IDN ccTLD Fast Track
IDN Implementation Guidelines
Second-Level LGR Reference
Resources
Announcements and Blogs Posts
New gTLD Program
Universal Acceptance Initiative
Make your systems UA-ready
UA Training
UA Day
UA Readiness Evaluations
UA Initiatives
Announcements and Blogs Posts
Policy
Policy Mission
Policy Staff Goals
Presentations
Global Addressing
IPv6 Allocation
ASN Allocation
Post Exhaustion IPv4 Allocation
New RIRs Criteria
Review Procedures
Policy Updates
Operational Design Phase (ODP)
Implementation
Public Comment
Open
Upcoming
Archive
Root Zone KSK Rollover
Technical Functions
Tech Day Archive
ICANN Locations
Report Security Issues
PGP Keys
Certificate Authority
Registry Liaison
Ombudsman
I Need Help
Dispute Resolution
Domain Name Dispute Resolution
Charter Eligibility Dispute Resolution Policy
Providers
Rules
Eligibility Requirements Dispute Resolution Policy
Providers
Rules
Intellectual Property Defensive Registration Challenge Policy
Providers
Rules
Qualification Challenge Policy
Providers
Rules
Restrictions Dispute Resolution Policy
Providers
Rules
Transfer Dispute Resolution Policy
Providers
Uniform Domain Name Dispute Resolution Policy
Policy Document
Providers
Provider Approval Process
Rules
Principal Documents
Proceedings
Historical Documents
Timeline
Name Collision
Registrar Problems
Whois Data Correction
Independent Review Process
Request for Reconsideration
Document
Operational Design Phase
This page is available in:
English
العربية
Español
Français
Pусский
中文
About the Operational Design Phase (ODP)
Development of the Operational Design Phase (ODP)
Operational Design Phase Frequently Asked Questions (FAQs)
Active ODPs
Closed ODPs
New gTLD Subsequent Procedures Operational Design Phase
System for Standardized Access/Disclosure to Non-Public Registration Data (SSAD) PDP Recommendations
About the Operational Design Phase
Click
here
to read the Operational Design Phase process paper.
The purpose of the Operational Design Phase (ODP) is to perform an assessment of Generic Names Supporting Organization (GNSO) Council policy recommendations, or other ICANN community-provided recommendations the Board deems appropriate, in order to provide the Board with relevant information for its deliberations on whether to approve said recommendations. The ODP Process Paper, linked above, guides the ODP process. Specific to the GNSO Consensus Policy, the ODP improves upon existing processes within the
Consensus Policy Implementation Framework
(CPIF) by adding additional transparency and structure to the work the ICANN org performs to assess the operational impact of GNSO Council-approved recommendations.
An ODP will be initiated by the Board in cases where the Board identifies that the GNSO policy recommendations, based on their complexity and potential operational impact, warrant such an assessment. A Board request for an ODP directs ICANN org to perform an operational analysis of a given set of GNSO policy recommendations. The ICANN org performs its analysis based on a Board-determined scope and provides the Board with an Operational Design Assessment (ODA), the expected output of the ODP, within a specified timeframe. Once completed, the ICANN org will submit the Operational Design Assessment to the Board for its consideration. In addition to other relevant materials, such as the recommendations themselves and the Bylaws-mandated Public Comment proceeding on the recommendations, the ODA will help the Board decide whether it believes the recommendations are in the best interests of ICANN community or ICANN.
While it is ICANN org that conducts the ODP, ICANN community feedback plays an important role in the process. Throughout the ODP, ICANN org will provide periodic updates on its progress. Progress updates will be provided via a number of platforms, including the icann.org website, webinars, blogs, and dedicated sessions during ICANN meetings, to offer the ICANN community opportunities to ask questions, seek clarification, and provide general feedback. In addition to these progress updates, once ICANN org has reached relevant milestones in its ODP work, it will report its progress to the ICANN community to provide visibility and to seek input on the facts, figures, and assumptions that underpin its analysis. All updates will take place transparently to ensure the ICANN community, Board, and org are aware of the different inputs provided. It is important to note that ICANN community input — like any other part of the ODP — is not a forum to reopen questions settled during the policy development process. Should any questions that pertain to policy arise during the ODP, these will be referred to the GNSO Council, which is encouraged to appoint an ODP liaison to assist in these communications.
More information about the ODP's purpose and how it is conducted is detailed in the
Operational Design Phase - Process Paper
. While the paper is authoritative in describing the ODP process, ICANN org has also drafted a
flowchart
to illustrate how the ODP fits into the
policy implementation lifecycle
and how the community can provide feedback during the ODP process. Development of the ODP process took place in conjunction with the ICANN community over a six-month period. The steps outlining this process are explained
here
.
ICANN is not responsible for profile content or verification of user details.
YouTube
Twitter
LinkedIn
Flickr
Facebook
Newsletters
Community Wiki
ICANN Blog
Who We Are
ICANN For Beginners
ICANN Learn
Participate
Groups
Board Members
CEO Corner
Staff
Careers
Public Responsibility
Contact Us
Locations
Report Security Issues
Certificate Authority
Registry Liaison
Ombuds
Complaints Office
Media Resources
Accountability And Transparency
Accountability Mechanisms
Document Disclosure
Independent Review Process
Request for Reconsideration
Empowered Community
Employee Anonymous Hotline Policy and Procedures
Governance
Governance Documents
Agreements
Organizational Reviews
Specific Reviews
Annual Report
Financials
Planning
RFPs
Litigation
Correspondence
Help
I Need Help
Dispute Resolution
Domain Name Dispute Resolution
Name Collision
ICANN Lookup
Registration Data Request Service (RDRS)
Data Protection
Data Privacy Practices
Privacy Policy
Terms of Service
Cookies Policy
© Internet Corporation for Assigned Names and Numbers.
Privacy Policy
Terms of Service
Cookies Policy
Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."


2026 Board Activities and Meetings

2026 Board Activities and Meetings
العربية
中文
English
Français
Pусский
Español
Logo
en
Search
Search
Search
Filtered Search
Log In
Sign Up
Are you sure you want to sign out from
https://www.icann.org
?
Yes
Cancel
If you want to sign out from both
https://www.icann.org
and ICANN Account,
click here
.
ICANN
Get Started
News and Media
Policy
Public Comment
Resources
Community
Quicklinks
Get Started
News and Media
Policy
Public Comment
Resources
Community
Quicklinks
Board Activities and Meetings
View records of actions and decisions made by the ICANN Board from recent activities and meetings.
Subscribe
Board Activities and Meetings Home
About the Board
Committees
Caucuses and Working Groups
Latest Board Blogs
Board Activities and Meetings
2026
2026
2025
2024
2023
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
2002
2001
2000
1999
1998
Select year
2026
2025
2024
2023
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
2002
2001
2000
1999
1998
View guidelines
for the posting of Board Briefing materials.
Advanced Search
Select filters and click Apply to narrow your search results or click More Search Options to search for keywords within Board Activities and Meetings
Document Type
Agenda
Approved Resolutions
Board Briefing Materials
Minutes
Preliminary Report
Secretary's Notice
Committee
Audit Committee of the Board (BAC)
Board Accountability Mechanisms Committee (BAMC)
Executive Committee of the Board (BEC)
Finance Committee of the Board (BFC)
Governance Committee of the Board (BGC)
Organizational Effectiveness Committee of the Board (OEC)
Risk Committee of the Board (BRC)
Strategic Planning Committee of the Board (SPC)
Technical Committee of the Board (BTC)
Previous Committees
Board Global Relationships Committee
Board IANA Committee
New gTLD Program Committee
Public and Stakeholder Engagement Committee
Board Meeting Type
Organizational
Regular
Special
Workshops
Start Date
End Date
Apply
Clear
More Search Options
Download results to .csv file
Expand all
|
Collapse all
Upcoming
No upcoming meetings.
August 2026
No meetings this month.
July 2026
28 July 2026
Meeting of the Governance Committee of the Board (BGC)
Available Documents
Agenda
20 July 2026
Special Meeting of the ICANN Board
Available Documents
Agenda
Approved Resolutions
Preliminary Report
June 2026
30 June 2026
Meeting of the Governance Committee of the Board (BGC)
Available Documents
Agenda
Minutes
7 June 2026
ICANN Board Seville Workshop: ICANN Board – Public Engagement with GAC
Recording
Recording
7 June 2026
Regular Meeting of the ICANN Board
Available Documents
Agenda
Approved Resolutions
Minutes
Board Briefing Materials
Board Papers and Reference Materials
(pdf, 1.12 MB)
May 2026
29 May 2026
Meeting of the Risk Committee of the Board (BRC)
Available Documents
Agenda
Minutes
29 May 2026
Secretary’s Notice of Vacancy in Board Seat 9
Available Documents
Secretary's Notice
(pdf, 16.48 KB)
28 May 2026
Meeting of the Finance Committee of the Board (BFC)
Available Documents
Agenda
Minutes
28 May 2026
Meeting of the Organizational Effectiveness Committee of the Board (OEC)
Available Documents
Agenda
Minutes
19 May 2026
Meeting of the Governance Committee of the Board (BGC)
Available Documents
Agenda
Minutes
14 May 2026
Meeting of the Strategic Planning Committee of the Board (SPC)
Available Documents
Agenda
12 May 2026
Meeting of the Audit Committee of the Board (BAC)
Available Documents
Agenda
Minutes
3 May 2026
Regular Meeting of the ICANN Board
Available Documents
Agenda
Approved Resolutions
Minutes
Board Briefing Materials
Board Papers and Reference Materials
(pdf, 57.03 MB)
1 May 2026
ICANN Board Manchester Workshop: ICANN Board – Public Virtual Session: The domain industry from the Contracted Parties (CP) perspective
Recording
Recording
April 2026
29 April 2026
Meeting of the Finance Committee of the Board (BFC)
Available Documents
Agenda
Minutes
24 April 2026
Meeting of the Technical Committee of the Board (BTC)
Available Documents
Agenda
Minutes
23 April 2026
Secretary’s Notice of Designation of Board Seat 14 with Supporting Documentation
Available Documents
Secretary's Notice
(pdf, 145.3 KB)
21 April 2026
Meeting of the Finance Committee of the Board (BFC)
Available Documents
Agenda
Minutes
20 April 2026
Meeting of the Technical Committee of the Board (BTC)
14 April 2026
Meeting of the Organizational Effectiveness Committee of the Board (OEC)
March 2026
31 March 2026
Meeting of the Finance Committee of the Board (BFC)
Available Documents
Agenda
Minutes
26 March 2026
Meeting of the Governance Committee of the Board (BGC)
Available Documents
Agenda
Minutes
26 March 2026
Special Meeting of the ICANN Board
Available Documents
Agenda
Approved Resolutions
Preliminary Report
12 March 2026
Regular Meeting of the ICANN Board
Available Documents
Agenda
Approved Resolutions
Minutes
Board Briefing Materials
Board Papers and Reference Materials
(pdf, 2.79 MB)
8 March 2026
Meeting of the Governance Committee of the Board (BGC)
Available Documents
Agenda
Minutes
8 March 2026
Regular Meeting of the ICANN Board
Available Documents
Agenda
Approved Resolutions
Minutes
Board Briefing Materials
Board Papers and Reference Materials
(pdf, 2.52 MB)
February 2026
26 February 2026
Meeting of the Risk Committee of the Board (BRC)
Available Documents
Agenda
Minutes
26 February 2026
Secretary's Notice of Designation of Board Seat 15 with Supporting Documentation
Available Documents
Secretary's Notice
(pdf, 124.9 KB)
24 February 2026
Meeting of the Finance Committee of the Board (BFC)
Available Documents
Agenda
Minutes
23 February 2026
Meeting of the Finance Committee of the Board (BFC)
Available Documents
Agenda
Minutes
23 February 2026
Meeting of the Organizational Effectiveness Committee of the Board (OEC)
Available Documents
Agenda
Minutes
19 February 2026
Meeting of the Strategic Planning Committee of the Board (SPC)
Available Documents
Agenda
Minutes
12 February 2026
Meeting of the Governance Committee of the Board (BGC)
Available Documents
Agenda
Minutes
2 February 2026
Meeting of the Technical Committee of the Board (BTC)
Available Documents
Agenda
Minutes
January 2026
25 January 2026
Regular Meeting of the ICANN Board
Available Documents
Agenda
Approved Resolutions
Minutes
Board Briefing Materials
Board Papers and Reference Materials
(pdf, 4.13 MB)
Executive Session Board Papers and Reference Materials
(pdf, 92.04 KB)
23 January 2026
ICANN Board Singapore Workshop: ICANN Board – Public Engagement with APAC
Recording
Recording
16 January 2026
Meeting of the Governance Committee of the Board (BGC)
Available Documents
Agenda
Minutes
13 January 2026
Meeting of the Finance Committee of the Board (BFC)
Available Documents
Agenda
Minutes
Jump To
Upcoming
August 2026
July 2026
June 2026
May 2026
April 2026
March 2026
February 2026
January 2026
Connect with us
X
Instagram
Facebook
Youtube
LinkedIn
Flickr
Soundcloud
Explore Our Social Media Hub and Follow Us on ICANN's Official Accounts
Who We Are
ICANN For Beginners
ICANN Learn
Participate
Groups
Board Members
CEO Corner
Staff
Careers
Public Responsibility
Contact Us
Locations
Report Security Issues
Certificate Authority
Registry Liaison
Ombuds
Complaints Office
Media Resources
Accountability and Transparency
Accountability Mechanisms
Document Disclosure
Independent Review Process
Requests for Reconsideration
Empowered Community
Employee Anonymous Hotline Policy and Procedures
Governance
Governance Documents
Agreements
Organizational Reviews
Specific Reviews
Annual Report
Financials
Planning
RFPs
Litigation
Correspondence
Help
I Need Help
Dispute Resolution
Domain Name Dispute Resolution
Name Collision
ICANN Lookup
Registration Data Request Service (RDRS)
Data Protection
Data Privacy Practices
Privacy Policy
Terms of Service
Cookies Policy
© Internet Corporation for Assigned Names and Numbers
Privacy Policy
Terms of Service
Cookies Policy
Privacy Policy
Terms of Service
Cookies Policy

2026 Board Activities and Meetings

Year found in title: '2026 Board Activities and Meetings'