JVTeams expansive program management experience will facilitate effective identification, understanding and mitigation of the risks involved with the introduction of a new TLD. JVTeam will bring to this process a proven, systematic approach to risk mitigation along with an intimate understanding of the DNS environment.
JVTeam was formed to succeed. However, experience dictates that success depends on understanding the project in its entirety which includes determining all areas of potential risk. JVTeam will continually evaluate potential risks and proactively monitor and address issues which could impact the overall successful and uninterrupted introduction of a new TLD. This section discusses our approaches to performing risk management, identifies specific risk areas, their implications, and our proposed risk mitigation strategy. We aim to minimize risk and maximize the opportunities that will benefit registrars, end users, and the Internet community as a whole. JVTeam understands that risk management should never be static as environments constantly change. JVTeam will not restrict risk management to currently identified problems. Instead, JVTeam will implement proven procedures and mechanisms for constantly identifying new potential areas of risk.
JVTeams approach to risk management is disciplined, consistent, and iterative. We will anticipate potential risks and take preventative action, eliminating or mitigating the risk, to ensure no significant impact. Our risk management includes risk identification, risk quantification, and risk mitigation.
Risk IdentificationAs we determine which risks are likely to affect the quality of our services, we will document their characteristics. Throughout the project lifecycle, we will continue to monitor and evaluate dependency issues and actively identify potential and emerging risks.
Risk QuantificationOnce we identify a risk, we will evaluate both its impact and likelihood of occurring. This approach feeds our development of an effective means to mitigate these risks.
Risk MitigationJVTeam will analyze all risks on an ongoing basis and respond by identifying strategies to reduce or eliminate them. We will develop and document contingency plans and alternative strategies, and track all risk management activities via a process that ensures management attention and employee focus. JVTeam will also share and discuss risk mitigation strategies with ICANN as they arise.
The following tables outline risks that have been identified at this early stage and where in the proposal those risks are mitigated.
|
BUSINESS RISKS |
||
|
Risk |
Potential
Impact |
Mitigation |
|
Lower than predicted
demand for the new TLD. |
Commercial failure of the
TLD and/or the registry |
Strategic and focused market analysis. (II.2.3)
Continual assessment of actual and predicted volumes.
Phased implementation of infrastructure to grow with
demand.
Effective channel management. (II.2.1)
Stimulation of demand through an effective marketing
plan. (II.2.4)
Stimulation of demand through extended functionality made
possible by the XRP. (III.2.2) |
|
Lower than predicted
demand for TLD renewals. |
Commercial failure of the
TLD and/or the registry. |
Strategic and focused market analysis. (II.2.3)
Effective and automated technical solution to the
renewals process. (II.2.1)
Continual innovation utilizing the XRP.
Continually monitor user requirements and feed back into
registry operations. |
|
Registry is unable to
deliver services in a timely manner. |
End users will lose
confidence in the registry and/or the TLD. |
Effective project management. (IV.1)
Staff who are experienced in delivering this sort of
system on time.
Experienced management team. (II.1.6)
Use of a proven software development life cycle
management methodology. (IV.1) |
|
Failure to provide
effective customer service. |
Registrar business will
be adversely affected due to longer resolution times for customer service
issues. |
JVTeam has extensive experience in operating according to
stringent SLAs. (II.1.4)
Comprehensive customer relations management program.
(II.2.1)
Experienced, dedicated account management. (II.2.1)
Stringent escalation procedures. (II.2.1)
Extensive training and documentation. (II.2.1)
Tiered support services to ensure the right people for
the right problem. (II.2.1) |
|
Illegal or inappropriate
registrar activity. |
The registry could face
legal or other challenges resulting from the activities of registrars. |
Non-liability clause in the agreement.
Registrar non-compliance procedure.
Facilitate registrar code of conduct
Contractual indemnification of the registry and ICANN. |
|
Failure to compete with
the current TLD domain name spaces. |
Low registration volumes
and low customer acceptance. |
Strategic and focused market analysis. (II.2.3)
Continual assessment of registration volumes.
Phased implementation to grow with demand.
Effective channel management. (II.2.1)
Stimulate demand through marketing plan implementation.
(II.2.4)
Stimulate demand through extended functionality made
possible by the XRP. (III.2) |
|
Unanticipated competition
resulting from the introduction of alternative Internet naming systems. |
Introduction of new
naming systems that do not fall under ICANNs charter. |
Support the ongoing evolution of the DNS.
Maintain stability and integrity of the DNS
Ensure openness and neutrality of the DNS.
Enhance the diversity and growth of the DNS
Strategic and focused market analysis. (II.2.3)
Ensure the viability of the DNS as a globally unique
technical system
Strong relationship with ICANN to ensure the ongoing
evolution and sustainability of the DNS. |
|
Greater than predicted
demand requires additional capital expenditure. |
Inadequate internet
infrastructure may be unable to accommodate increased levels of usage. |
Phased extension of the nameserver network is
incorporated in the implementation plan.
Capital expenditure provisions are incorporated into the
project plan. (IV.2)
Identification of initial and ongoing capital resources
(II.4.4)
Strong project management and detailed work plan. (IV.1
& IV.2)
Continual reassessment of volume and growth projections,
capacity monitoring.
Effective prediction of and adequate planning to
accommodate growth. |
|
The expansion of the DNS
is restricted by national government policy.
|
Reduced registration
volumes and revenue. |
Governments policy will be closely monitored through the
Governmental Advisory Committee to ICANN. (GAC)
Registry will be sensitive to the issues raised by
national government bodies. |
|
TECHNICAL RISKS |
||
|
Risk |
Potential
Impact |
Mitigation |
|
The technical solution
cannot scale to meet demand. |
Registrars and end users
lose confidence in the registry. |
Effective project management. (IV.2)
Plan carefully to adequately accommodate growth.
Continuously monitor the growth of demand.
Constantly reevaluate projections and infrastructure
requirements.
JVTeam has extensive experience in providing highly
scalable solutions. (II.1.3, II.1.4)
Rigorous load testing of all software and hardware
products.
JVTeam has an architecture in place that allows linear
scalability simply by adding additional machines to various clusters.
(III.2.1) |
|
Security breaches. |
Registry system failure
from hacking and/or denial of service attacks. |
The firewall and routers are configured optimally to
allow restricted access. (III.2.9)
Use of security analysis software. (III.2.9)
System fail over, back-up and redundancy mechanisms.
(III.2.11)
Extensive physical and virtual security provisions
integrated into architecture. (III.2.9)
Logging of all system access to monitor user activity and
identify potential breaches. (III.2.9)
Rigid internal security procedures. (III.2.9) |
|
System hardware or
software failure. |
Loss of data. |
Regular, incremental backup and off-site data escrow
contingency procedures throughout the architecture. (III.2.7)
All system components are in clustered or load balanced
configuration allowing machines to fail and be replaced transparently.
(III.2.13)
Rigorous and structured system testing prior to moving
into production environment. (IV.2)
JVTeam has extensive experience in designing and
maintaining availability of critical systems. |
|
Violation of individuals
privacy. |
Legal disputes and loss
of confidence in the integrity of the registry. |
An opt-in system for the publication of sensitive information.
(III.2.8)
Work closely with privacy bodies in different
constituencies to proactively address changes in privacy laws.
Ensure that registrar access to and use of personal
information is governed by the registrar agreement and code of conduct. |
|
Registrar implementation
of XRP is seen as too expensive. |
Adoption of the new TLD
is slow and affects commercial viability of the TLD. |
Will provide a free integration toolkit for registrars.
Will provide integration assistance through our technical
support. (II.2.1)
Provide an open source, modified RRP client for quick
transition to XRP. (III.2.2)
Registrar community already understands the value of an enhanced
registry registrar protocol. (III.2.2)
XRP will automate domain name management and significantly
reduce costs for registrars. (III.2.2)
Registrars will reap financial rewards from enhanced functionality.
(III.2.2)
Enhanced functionality of the XRP will differentiate new
TLD, stimulate demand and foster competition. (III.2.2).
End users will enjoy enhanced security, functionality and
performance and so will generate more demand for the TLD. (III.2.2)
The XRP will reduce the cost and technical barrier to
entry for new Registrars, thereby enhancing competition. (III.2.2) |
|
Technical solution not
accepted by the registrar community. |
Slow adoption of the XRP
which affects viability of the TLD. |
XRP will be developed in consultation with registrars,
ICANN, and standards bodies. (III.2.2)
The XRP will be an open standard ensuring the integrity
of a competitive multiple registry environment. JVTeam already has support
for the XRP from a large portion of the registrar community.
Registrar community already understands the value and
need for an enhanced registry/registrar protocol. (III.2.2)
XRP will automate domain name management and
significantly reduce costs for registrars. (III.2.2)
Registrars will reap financial rewards from enhanced
functionality, providing a substantial incentive.
Enhanced functionality of the XRP will differentiate new
TLD from .com and stimulate demand. (III.2.2)
End users will enjoy enhanced security, functionality and
performance and so will generate more demand for the TLD. (III.2.2)
The XRP will reduce the cost and technical barrier for
new registrars, thereby enhancing competition and increased demand. (III.2.2) |
|
Selected vendor is not
qualified to introduce a new protocol such as XRP. |
The next generation RRP
is not quickly adopted. |
JVTeam has significant experience in developing open
standards for the administration of critical public resources.
JVTeam has an extensive history in working closely with
regulatory bodies to ensure open and neutral standards which benefit all
stake holders. |
|
New registry protocol is
perceived as a proprietary standard. |
Openness and
competitiveness of the multi-registry environment is thwarted. |
XRP will be developed in consultation with registrars,
ICANN and standards bodies.
The XRP will be an open standard ensuring the integrity
of a competitive multiple registry environment.
JVTeams mission and code of conduct ensure absolute
neutrality in registry operations, including the development of standards. |
IMPLEMENTATION RISKS |
||
|
Risk |
Potential
Impact |
Mitigation |
|
The solution cannot be
delivered within specified schedule. |
Successful introduction
of the TLD is delayed. |
JVTeam will develop a detailed project plan with a
schedule to ensure a timely
implementation of the project. (IV.2)
Ongoing project monitoring will track the progress of
individual components and identify any areas which are at risk of not meeting
the schedule. (IV.2)
Internal performance monitoring will ensure timely
delivery of components.
JVTeam will leverage its skill and experience in
effectively managing projects of this size and larger. (IV.2) |
|
The cost of the solution
exceeds the predicted budget. |
Undermines the commercial
viability of the registry. |
JVTeam will implement an ongoing systematic analysis of
the implementation costs.
Intensive budget variance analysis will be applied to all
human and capital costs.
JVTeam will leverage experience in designing, building
and delivering registry solutions within and even under specified budgets to
ensure the competitiveness of the registry. |
|
Inability to recruit
adequate and qualified human resources. |
Delivery of the solution
is delayed. |
JVTeam already has key experienced personnel. (II.1.7)
JVTeam has extensive experience in human resource
management for similar projects. (II.1.6)
JVTeam will utilize its existing human resource network
to acquire any additional staff required. (II.2.8) |
|
JVTeam is unable to
secure adequate facilities and required infrastructure. |
Delivery of the solution
is delayed. |
JVTeam will operate according to a detailed facilities
and infrastructure requirements plan. (IV.2)
JVTeam will leverage experience and existing vendor
relationships to acquire necessary infrastructure. |
|
POLICY RISKS |
||
|
Risk |
Potential
Impact |
Mitigation |
|
Untested DNS policies are
introduced for the administration and assignment of domain names. |
Creates divisiveness and
industry confusion. |
JVTeam will build on and enhance existing policies rather
than impose new ones. (I)
JVTeam will introduce evolutionary policies such as the
UCDRP that adapt to the new TLDs and the new commercial environment. (I.6)
JVTeam will work closely with ICANN, user groups, registrars
and other regulatory bodies to ensure consistency across policy development
and implementation.
JVTeam has a rich background in developing and
administering domain name policy. |
|
Policies used are
inappropriate for new TLDs. |
Dilution of the integrity
of the domain space. |
JVTeam will introduce evolutionary policies such as the
UCDRP that adapt to the new TLDs and the new commercial environment. (I.6)
JVTeam will work closely with ICANN, user groups,
registrars and regulatory bodies to
ensure consistency across policy development and implementation.
JVTeam has a rich background in developing and
administering domain name policy.
Policies have been developed in consultation with legal
and subject matter experts. |
|
Policies do not protect
the rights of intellectual property holders. |
The DNS community becomes
embroiled in expensive and divisive legal disputes. |
Implementation of an Intellectual Property Notification
Service. (II.2.1)
Policies have been developed in consultation with legal
and subject matter experts.
Enhanced UDRP goes a step further in protecting
intellectual property rights and resolving disputes through the processes of
the UDRP. (I.6)
JVTeam has been a leader in developing innovative
solutions to managing intellectual property issues. |
|
The start-up period is
not effectively managed. |
Proliferation of legal
disputes over the allocation of domain names during this period. |
The round robin solution will ensure the allocation of
domain names in an entirely impartial and evenhanded manner. (IV.4)
JVTeams strict code of neutrality will dictate fairness
and impartiality of domain name allocation.
Intellectual Property Notification Service will operate
in concert with registration agreements and the UCDRP to minimize and manage
disputes. (I.6) |
|
Biased administration of
policies. |
Undermines the fairness
of the allocation of domain names. |
JVTeam will implement a registry code of conduct to
ensure and maintain the neutral, even-handed treatment of all registrars.
JVTeam will work with ICANN and the registrar community
to develop a registrar code of conduct which further enhances the impartial
administration of domain name policies.
Registrar agreements will address the registrars
adherence to fair and impartial policy administration.
Disputes will be resolved via the UCDRP which follows the
same dispute resolution procedures as the UDRP including engagement of mutually
agreed, 3rd party arbitration.
|
|
Policies require
excessive resources to implement. |
Competitiveness of the
TLD is undermined by the expense of administering policies. |
JVTeam will use
charters which place the onus for compliance on the applicant. This
minimizes time consuming and unworkable administrative requirements.
Disputes over charter violations will be resolved through
an enhanced UDRP- the UCDRP. (I.6)
Disputes will be resolved via the UCDRP which follows the
same dispute resolution procedures as the UDRP including engagement of mutually
agreed, 3rd party arbitration.
JVTeams extensive experience in administering a
policy-restricted domain space will enhance its ability to perform this
function. (II.1.4) |
|
Intellectual property
community does not support proposed policies. |
Delayed introduction of
the TLD. Divisiveness over fairness and dispute resolution. |
JVTeam will enhance the existing policies including the
UDRP which has been developed in consultation with these communities.
JVTeam will continue to work closely with the IPC and
ICANN to achieve mutually beneficial solutions.
JVTeam acknowledges ICANNs prior work and we will
ultimately defer to ICANNs judgment in policy issues to ensure consistency
and fairness across TLDs. |
The domain name system is at an exciting turning point in its evolution. Never before and possibly never again will there exist such an opportunity to enhance the DNS at such a fundamental level. The introduction of a competitive multiple-registry environment will facilitate new and enhanced services, new applications for the DNS, and solutions to existing issues. JVTeam is committed to playing a responsible role in this process by providing neutral, next generation registry services. The table that follows is a high level view of some of the opportunities that are presented by the current program and how JVTeam will realize those opportunities for the benefit of the entire Internet community.
|
OPPORTUNITIES |
||
|
Opportunity |
Potential
Benefit |
JVTeam
Action to Realize. |
|
Solve the existing
administrative issues attached to the RRP. |
Ensure the ongoing
stability of the Internet. Reduce the administrative costs involved in
administering domains names. Increase automation and confidence for end
users. |
Introduce the non-proprietary eXtensible Registry
Protocol. (XRP)
Leverage extensive knowledge and understanding of the
existing issues.
Work closely with all stake holders to introduce XRP. |
|
Enhance security for
domain names. |
Ensure stability of the
Internet. Consumer has more confidence in the Industry and a
multiple-registry environment. |
Introduce the non-proprietary eXtensible Registry
Protocol.
Leverage extensive knowledge and understanding of the
existing security issues. |
|
Introduce a competitive
environment for registry operations. |
Greatly improved and more
diverse registry services. |
Operating as a neutral registry.
Introducing the XRP will bring additional functionality
for registrars and end users.
Targeted market research to understand market needs. |
|
Introduce innovative
domain name services. |
Expansion of the utility
of the DNS. |
Introduce the XRP.
Leverage understanding of the DNS environment to foster
its evolution. |
|
Develop effective proof
of concept for the introduction of future TLDs |
Pave the way for the
future, stable introduction of new TLDs. |
Proposing an effective solution to start-up issues.
Proposing an Intellectual Property Notification Service
Capturing and analyzing results of proposed concepts to
provide to ICANN and the Internet community. |
|
Increase consumer choice
and quality of registry services. |
Consumer will have a
choice for selecting a TLD based on the functionality and quality of service
provided by the registry. |
Introduction of additional functionality through the XRP.
New architecture design of the registry enhances the
quality of service provided. |
|
Introduce a new open
standard for registry registrar interface. |
Lower the technical
barrier to entry for new registrars and foster competition. Enhance the
stability of the Internet. Address the current issues with the existing RRP. |
Developing the standard in consultation with all relevant
stake holders.
Leveraging experience in developing open standards within
a regulated environment.
Consult with registrars to identify the new required
protocol. |
JVTeam is committed to the successful introduction of new TLDs. As part of that commitment, JVTeam will draw on its expansive knowledge of Registry operations and project management to effectively identify, assess and manage all risks and opportunities, both now and well beyond the implementation of the JVTeam solution. The JVTeam approach will ensure the measured and systematic evolution of the Domain Name System.