DNS Business Development Workshop Course Overview This course is designed to provide a basic understanding of the Domain Name System (DNS) industry and business drivers to enable entrepreneurs to understand potential business opportunities in this industry. The course will focus on practical issues where appropriate, with case studies and listings of available resources and vendors in the industry. Ample time will be included for networking opportunities and identifying available resources for on-going assistance after the conclusion of the course. The course will occur over a 5 day period, with an early end on the last day to accommodate travel schedules

1. ICANN’s Policy Development
David Olive
Vice President
Policy Development Support

2. What is ICANN?
• Global multi-stakeholder organization that coordinates
the Internet’s system of unique identifiers – domain
names, IP addresses and Internet Protocols – enabling a
single, interoperable Internet.
• Dedicated to preserving operational stability of the
Internet, promoting competition, through broad
representation in a bottom-up, consensus-based
process.
2

3. ICANN’s Mission
The
mission
of
The
Internet
Corpora2on
for
Assigned
Names
and
Numbers
(“ICANN”)
is
to
coordinate,
at
the
overall
level,
the
global
Internet's
systems
of
unique
iden2fiers,
and
in
par2cular
to
ensure
the
stable
and
secure
opera2on
of
the
Internet's
unique
iden2fier
systems.
3

4. ICANN’s Policy Development
• A
primary
role
of
ICANN
is
to
coordinate
policy
development
related
to
the
global
Internet’s
systems
of
unique
iden2fiers.
• ICANN's
open
and
transparent
policy
development
mechanisms
promote
well-­‐informed
decisions
based
on
expert
advice
from
a
diversity
of
views
from
our
stakeholders.
• The
ICANN
Community
works
to
improve
and
streamline
these
mechanisms
so
as
many
global
stakeholders
as
possible
can
have
par2cipate
and
have
their
voices
heard.
•
The
boLom
up,
consensus
approach
results
in
recommenda2ons
for
the
domain
name
system
(DNS)
that
are
fair,
effec2ve,
and
carefully
considered,
preserving
and
enhancing
the
security,
stability
and
resiliency
of
the
Internet.
4

5. 5

6. ICANN Supporting Organizations
• GNSO – Generic Names Supporting
Organization
• ccNSO – Country-code Names Supporting
Organization
• ASO – Address Supporting Organization
Advice provided by Advisory Committee
– ALAC – At-Large Advisory Committee
– SSAC – Security & Stability Advisory Committee
– RSSAC – Root Server System Advisory Committee
– GAC – Governmental Advisory Committee
Policy Developed at ICANN by:
6

7. 7
Supporting Organizations

8. 8
Advisory Committees

10. GNSO

14. Concept
of
“Consensus
Policies”
• ICANN
Agreements
(Registry
and
Registrar)
require
compliance
with
“Consensus
Policies”
o Follow a specific policy development process
(PDP)
• Limited
to
specific
topics
(“Picket
Fence”),
such
as:
o Technical specifications
o Security & Stability of Internet
o Domain Contact Data (WHOIS)
• Examples
of
consensus
policies
include:
Inter-­‐
Registrar
Transfer
Policy;
Uniform
Dispute
Resolu2on
Policy;
Whois
Data
Reminder
Policy

15. GNSO Policy Issues

16. • New GNSO Policy Development Process
• Inter-Registrar Transfer Policy (IRTP)
• Locking of Domain Names Subject to UDRP Proceedings
• WHOIS Directory Service
• Uniformity of Contracts
• Consumer Choice, Competition and Trust
• Cross Community Working Groups
• Protection of IOC and Red Cross names for new gTLDs
Policy issues discussed in GNSO

17. How
can
I
par2cipate
in
GNSO?
• Make a Public Comment
• Follow Mailing lists
• Join a Stakeholder Group or
Constituency
• Volunteer to Join a Working Group
• Listen to/attend GNSO Council
Meetings

18. For further information
• hLp://gnso.icann.org
• GNSO
PDP
-­‐
hLp://gnso.icann.org/en/basics/pdp-­‐
process.htm

19. ccNSO

20. What
is
ccNSO?
20
• Created
for
and
by
ccTLD
Managers
• Forum
to
meet
and
discuss
topical
issues
of
concern
to
ccTLDs
from
a
global
perspec2ve
• Also
responsible
for
ccNSO
PDP
–
limited
set
of
issues
rela2ng
to
ccTLDs
• Members
(153
out
of
250
+
ccTLD
managers)
-­‐
Council
(18
Councilors)
More information: http://
ccnso.icann.org/

21. What
does
the
ccNSO
do?
• Exchange
of
informa/on
• ccNSO
mee2ngs,
Tech
Day
and
workshops
• Networking
• ccNSO
dinner,
lunches,
working
groups,
ICANN
mee2ngs
• Represent
ccTLD
community
interests
in
ICANN
• ccNSO
Statements
and
Posi2ons
• Input
into
ICANN
Strat
and
Ops
Plan
(
SOP
WG)
• New
model
financial
contribu2on
ccTLD’s
(
Finance
WG)
• Mee2ngs
with
Board,
GAC,
GNSO
SSAC
and
others
• Policy
21

22. What
does
the
ccNSO
do?
• Policy
Development
• Limited
scope
(Annex
C
bylaws)
• Current
ccPDP
• Overall
policy
selec2on
of
IDN
ccTLD
strings
• Inclusion
of
IDN
ccTLD
in
ccNSO
• Future
PDP:
re2rement
of
(IDN)ccTLD’s
• Policy
Related
Work
• Interpreta2on
RFC
1591,
GAC
Principles
(policies
delega2on
and
re-­‐delega2on
of
ccTLD’s
• Study
use
of
country
and
territory
names
as
TLD’s
22

23.
ASO

24. Background: RIRs, NRO and the ASO
• What is an RIR?
− Regional Internet Registry. There
are five RIRs; AfriNIC, APNIC,
ARIN, LACNIC and RIPE and they
cooperate thru the NRO, the
Number Resource Organization.
• What is the ASO?
− The Address Supporting
Organization, set up through an
MoU between ICANN and the NRO.
− One major task of the ASO is to
handle Global Policy Proposals.

25. 25

26. ASO Policy Issues

27. Background: Global Policies
• What is a “Global Policy”?
– The RIRs develop many regional
addressing policies.
– Only very few policies affect IANA
and only those are called “Global
Policies”.
• Recent Global Policy Proposal:
- Recovered IPv4 Address Space,
”Post Exhaustion”
hLp://aso.icann.org/

28. Advisory
CommiLees
In
addi2on
to
SOs,
there
are
ACs
that
are
responsible
for
providing
the
ICANN
Board
with
direct
advice:
• At-­‐Large
AC
(ALAC)
• Governmental
AC
(GAC)
• Security
and
Stability
AC
(SSAC)
• Root
Server
System
AC
(RSSAC)

29. At Large

30.
ICANN’s
At-­‐Large
Advisory
CommiFee
(ALAC)
is
responsible
for
considering
and
providing
advice
on
the
ac2vi2es
of
the
Internet
Corpora2on
for
Assigned
Names
and
Numbers
(ICANN),
as
they
relate
to
the
interests
of
individual
Internet
users
(the
“At-­‐Large”
community).
More
informa2on:
hLp://atlarge.icann.org

32.
GAC

33. Overview
• The
Governmental
Advisory
CommiLee
's
key
role
is
to
provide
advice
to
ICANN
on
issues
of
public
policy,
and
especially
where
there
may
be
an
interac2on
between
ICANN's
ac2vi2es
or
policies
and
na2onal
laws
or
interna2onal
agreements.
• The
GAC
usually
meets
three
2mes
a
year
in
conjunc2on
with
ICANN
mee2ngs
• Currently
150
Members
plus
32
Observers
(IGOs).
• More
informa2on:
hLp://gacweb.icann.org

34.
SSAC

35. SSAC Activity Report
March 2012
What is the SSAC?
The Security and Stability Advisory Committee (SSAC) advises the ICANN community and Board of Directors on
matters relating to the security and integrity of the Internet's naming and address allocation systems. This includes
operational matters (e.g., matters pertaining to the correct and reliable operation of the root name system),
administrative matters (e.g., matters pertaining to address allocation and Internet number assignment), and
registration matters (e.g., matters pertaining to registry and registrar services). The SSAC engages in ongoing threat
assessment and risk analysis of the Internet naming and address allocation services to assess where the principal
threats to stability and security lie, and advises the ICANN community accordingly. See the SSAC Charter for
additional information.
Introduction
This Activity Report is divided into the following sections: Work Plan for 2012 and Work Completed in 2012.
The first section, Work Plan for 2012, presents the ideas and preliminary work to develop specific project plans.
This is perhaps the most important section of this report because it provides notice of issues on the horizon. The
Work Plan may include activities that have been carried over from the previous year.
The SSAC generates three types of work products: reports, advisories and comments. Reports examine a topic in
substantial detail. Advisories are issued in response to a problem or incident in a timely manner. Comments are
usually responses to queries from staff or to ICANN documents posted for formal response. SSAC reports,
advisories and comments are generally available for distribution to the community. Those work products that were
produced in 2012 are described in the Work Completed in 2012 section. For a list of SSAC documents see:
http://www.icann.org/en/groups/ssac/documents. For previous Work Plans and Activities see:
http://www.icann.org/en/groups/ssac/workplan-activities.
The SSAC often considers security incidents or matters disclosed in confidence to committee members (e.g., a
security vulnerability, an emerging threat to the Domain Name System (DNS), or information relating to a security
incident). Discussions and ongoing work within the SSAC are thus typically conducted in private until complete, or
until the need for confidentiality has lapsed. For information on the operation of the SSAC, see the SSAC
Operational Procedures. SSAC members participate in an individual capacity and do not represent the organizations
The
Security
and
Stability
Advisory
CommiFee
(SSAC)
is
a
body
of
the
Internet
Corpora2on
for
Assigned
Names
and
Number
(ICANN)
consis2ng
of
technical
experts
who
review
incidents,
issues,
and
topics
that
are
broadly
related
to
the
security
and
stability
of
the
Internet's
naming
and
address
alloca2on
systems.
hLps://www.icann.org/resources/pages/ssac-­‐2012-­‐02-­‐25-­‐
en?rou2ng_type=path

36. Overview
Security
and
Stability
Advisory
CommiFee
38
SSAC
Members
as
of
16
March
2012
•
Formed
in
2001-­‐2002
–
Decision
to
start:
late
2001
–
First
Opera2on:
early
2002
•
Provides
guidance
to
ICANN
Board,
Suppor2ng
Organiza2ons
and
Advisory
CommiLees,
staff
and
general
community
•
Guidance
areas
are
related
to
ICANN’s
mission,
DNS,
addressing,
etc.
SSAC Activity Report
March 2012
What is the SSAC?
The Security and Stability Advisory Committee (SSAC) advises the ICANN community and Board of Directors on
matters relating to the security and integrity of the Internet's naming and address allocation systems. This includes
operational matters (e.g., matters pertaining to the correct and reliable operation of the root name system),
administrative matters (e.g., matters pertaining to address allocation and Internet number assignment), and
registration matters (e.g., matters pertaining to registry and registrar services). The SSAC engages in ongoing threat
assessment and risk analysis of the Internet naming and address allocation services to assess where the principal
threats to stability and security lie, and advises the ICANN community accordingly. See the SSAC Charter for
additional information.
Introduction
This Activity Report is divided into the following sections: Work Plan for 2012 and Work Completed in 2012.
The first section, Work Plan for 2012, presents the ideas and preliminary work to develop specific project plans.
This is perhaps the most important section of this report because it provides notice of issues on the horizon. The
Work Plan may include activities that have been carried over from the previous year.
The SSAC generates three types of work products: reports, advisories and comments. Reports examine a topic in
substantial detail. Advisories are issued in response to a problem or incident in a timely manner. Comments are
usually responses to queries from staff or to ICANN documents posted for formal response. SSAC reports,
advisories and comments are generally available for distribution to the community. Those work products that were
produced in 2012 are described in the Work Completed in 2012 section. For a list of SSAC documents see:
http://www.icann.org/en/groups/ssac/documents. For previous Work Plans and Activities see:
http://www.icann.org/en/groups/ssac/workplan-activities.
The SSAC often considers security incidents or matters disclosed in confidence to committee members (e.g., a
security vulnerability, an emerging threat to the Domain Name System (DNS), or information relating to a security
incident). Discussions and ongoing work within the SSAC are thus typically conducted in private until complete, or
until the need for confidentiality has lapsed. For information on the operation of the SSAC, see the SSAC
Operational Procedures. SSAC members participate in an individual capacity and do not represent the organizations

37.
RSSAC

38. Overview
• RSSAC
considers
and
provides
advice
on
the
opera2onal
requirements
of
root
name
servers,
including
host
hardware
capaci2es,
opera2ng
systems
and
name
server
somware
versions,
network
connec2vity
and
physical
environment
• RSSAC
examines
and
advises
on
the
security
aspects
of
the
root
name
server
system
and
reviews
the
number,
loca2on,
and
distribu2on
of
root
name
servers
considering
the
total
system
performance,
robustness,
and
reliability
• It
includes
representa2ves
of
organiza2ons
responsible
for
opera2ng
the
world's
thirteen
root
nameservers
and
other
organiza2ons
concerned
with
stable
technical
opera2on
of
the
authorita2ve
root
server
system
• More
informa2on:
hLps://www.icann.org/resources/pages/rssac-­‐4c-­‐2012-­‐02-­‐25-­‐en?
rou2ng_type=path

39.
Prior
to
every
ICANN
mee2ng
Latest
updates
on
policy
related
developments
as
well
as
informa2on
on
events
taking
place
at
ICANN
mee2ng
See
hLp://www.icann.org/en/news/
announcements
for
further
informa2on
Subscribe to the monthly Policy Update:
http://www.icann.org/en/topics/policy/

40. Thank you