Text. Registry Onboarding and TLD Startup
|
|
|
- Mitchell Hodges
- 10 years ago
- Views:
Transcription
1 Registry Onboarding and TLD Startup
2 Background
3 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration
4 What is Onboarding?
5 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration
6 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration Onboarding
7 What is Onboarding? Purpose Setup your Registry Account with ICANN For the needs of Ongoing Operations Before your TLD is delegated (prerequisite) Principles o o o o Starts when applicant executes the Registry Agreement Completed before Delegation Tasks can be completed in parallel Prepared, Registry Operator can move quickly through the process
8 Why Onboarding Matters? Foundation of the operational relationship between the Registry Operator and ICANN (GDD) On the critical path to delegation
9 Be Prepared
10 Be Prepared Follow instructions carefully Registry Operator Welcome Kit Customer Portal User Guide, GDD Portal Guidance Document newgtlds.icann.org for PDT, Delegation & TMDB Provide detailed technical information about Registry Systems Provide detailed contact information for 22 operational registry functions (or roles) Be ready for TMDB integration testing
11 What is TLD Startup?
12 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration Onboarding
13 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration Onboarding TLD Startup
14 What is TLD Startup? Purpose Taking the TLD to General Registration While ensuring Launch Program complies with Requirements If needed, securing approval of specific Launch Program Principles o Starts when TLD is Delegated o o Completed before registrations are accepted Activation of names must comply with Name Collision Occurrence Management Requirements
15 Question : How many of you will be going through Onboarding in the future?
16 Question 2: How many of you have never gone through Onboarding before?
17 Agenda Timeline Overview Process Walkthrough with Guidance on How To Avoid Common Challenges Onboarding Systems Recap. Latest Updates
18 Timeline Overview
19 From Registry Onboarding to TLD Launch Registry Agreement Executed 2 months to delegate into the root (RA Art. 4.3 b) Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) 6 weeks or more Step 2: Complete Pre-Delegation Testing Onboarding Step 3: Provide information for credentialing Step 4: Provide onboarding contact information Step 5: Register with TMDB Step 6: Complete TMDB Testing 2 weeks Step 7: Complete Transition to Delegation Step 8: Submit TLD Startup Information TLD Launch No-Activation Period - 20 days minimum Controlled Interruption 90 days Activation of names under Sunrise, Claims & Other LR/QLP Periods Name Collision Occurrence Management (RA Spec 6.6)
20 Process Walkthrough
21 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) TLD Launch Onboarding
22 Step - Join the gtld RySG The Registry Stakeholder Group (RySG) is a recognized entity within the GNSO The primary role of the RySG is to represent the interests of gtld Registry Operators under contract with ICANN (RySG Charter) More information at (charter, membership, registration, news ) Membership is optional
23 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) TLD Launch Onboarding
24 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) 6 weeks or more Step 2: Complete Pre-Delegation Testing TLD Launch Onboarding
25 Step 2 - Complete PDT Prerequisites o Registry Agreement Executed o ICANN invites Registry Operator to PDT o Registry has entered into a Data Escrow agreement with an approved Data Escrow Provider o Registry is prepared and has set appointment with PDT Provider Registry Operator demonstrates operational readiness When : Schedule within 9 month of RA Execution Who : Application Primary Contact Where : Customer Service Portal + PDT System
26 Step 2 - Complete PDT Customer Service Portal
27 Step 2 - Complete PDT More information at
28 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) 6 weeks or more Step 2: Complete Pre-Delegation Testing TLD Launch Onboarding
29 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) 6 weeks or more Step 2: Complete Pre-Delegation Testing Onboarding Step 3: Provide information for credentialing TLD Launch
30 Step 3 Provide information for Credentialing Prerequisites o Registry Agreement Executed o Registry has GDD Portal Credentials o Registry is prepared to provide detailed technical information Registry On-Boarding Information Request (ONBIR) Work Item When : Asap, in parallel with PDT Who : Registry Primary Contact (CIR Registry PoC ) Where : GDD Portal + CZDS
31 Step 3 Provide information for Credentialing
32 Step 3 Provide information for Credentialing
33 Step 3 Provide information for Credentialing
34 Step 3 Provide information for Credentialing Information to be provided include : o CZDS Account + Protocol details (AXFR SFTP) + Relevant Cryptographic Keys o BRDA Account + SFTP URI + PGP Keys o EPP Extensions o RRI Account Passwords + Client IPs (Registry + Escrow Agent) o URS PGP Key + Account Password o EPP Servers + SLA Monitoring Account credentials The Welcome Kit also includes instructions on ICANN IP addresses range to be whitelisted for the relevant services.
35 Step 3 Provide information for Credentialing More information o Welcome Kit o GDD Portal Guidance Document o Registry Agreement Specifications 2, 3, 4, 6 o > Resources > Registries > CZDS o
36 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) 6 weeks or more Step 2: Complete Pre-Delegation Testing Onboarding Step 3: Provide information for credentialing TLD Launch
37 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) 6 weeks or more Step 2: Complete Pre-Delegation Testing Onboarding Step 3: Provide information for credentialing Step 4: Provide onboarding contact information TLD Launch
38 Step 4 Provide On-Boarding Contact Info. Prerequisites o Registry Agreement Executed o Registry has GDD Portal Credentials o Registry is prepared to provide operation contact information Registry Contact Information Work Item Public Contact Information Work Item When : Asap, in parallel with PDT Who : Registry Primary Contact Where : GDD Portal
39 Step 4 Provide On-Boarding Contact Info.
40 Step 4 Provide On-Boarding Contact Info. Registry Contact Information Work Item Registry Primary Registry Secondary RSP Primary RSP Secondary Escrow Agent Primary Escrow Agent Secondary Technical Contact Legal Notice Contact Communications Contact Billing Primary Contact Billing Secondary Contact 24x7 Emergency Escalation 24x7 Emergency Escalation 2 24x7 Emergency Escalation 3 CZDS Primary CZDS Secondary TMDB Abuse Compliance URS Registry Operator URS Registry Serv. Provider
41 Step 4 Provide On-Boarding Contact Info. Public Contact Information Work Item
42 Step 4 Provide On-Boarding Contact Info. More information o Welcome Kit o GDD Portal Guidance Document
43 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) 6 weeks or more Step 2: Complete Pre-Delegation Testing Onboarding Step 3: Provide information for credentialing Step 4: Provide onboarding contact information TLD Launch
44 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) 6 weeks or more Step 2: Complete Pre-Delegation Testing Onboarding Step 3: Provide information for credentialing Step 4: Provide onboarding contact information Step 5: Register with TMDB TLD Launch
45 Step 5 Register with the TMDB Prerequisites o ICANN Approves Registry Contact Information (Step 4) ICANN Issues a TMDB Token Registry uses token to register with TMDB TMDB Provider issues credentials When : Asap, after Step 4 Who : TMDB Contact Where : GDD Portal Case + TMDB System
46 Step 5 Register with the TMDB Token sent through GDD Portal Case
47 Step 5 Register with the TMDB Sample content of GDD Portal Case with TMDB Token
48 Step 5 Register with the TMDB TMDB Registration Screen
49 Step 5 Register with the TMDB More information : o Welcome Kit o TMDB System User Manual (Registry) o
50 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) 6 weeks or more Step 2: Complete Pre-Delegation Testing Onboarding Step 3: Provide information for credentialing Step 4: Provide onboarding contact information Step 5: Register with TMDB TLD Launch
51 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) 6 weeks or more Step 2: Complete Pre-Delegation Testing Onboarding Step 3: Provide information for credentialing Step 4: Provide onboarding contact information Step 5: Register with TMDB Step 6: Complete TMDB Testing TLD Launch
52 Step 6 Complete TMDB Testing Prerequisites o Registry has registered with TMDB and obtained TMDB Credentials from IBM (Step 5) Registry completes testing protocol with TMDB Provider o SMD Revocation List, DNL List, Sunrise LORDN, Claims LORDN, LORDN log file TMDB Provider issues TMDB Certification Registry may qualify for exemption from Certification When : Asap, after Step 5 Who : TMDB Contact + Technical Expertise Where : TMDB System
53 Step 6 Complete TMDB Testing More information : o Welcome Kit o TMDB System User Manual (Registry) o
54 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) 6 weeks or more Step 2: Complete Pre-Delegation Testing Onboarding Step 3: Provide information for credentialing Step 4: Provide onboarding contact information Step 5: Register with TMDB Step 6: Complete TMDB Testing TLD Launch
55 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) 6 weeks or more Step 2: Complete Pre-Delegation Testing Onboarding Step 3: Provide information for credentialing Step 4: Provide onboarding contact information Step 5: Register with TMDB Step 6: Complete TMDB Testing 2 weeks Step 7: Complete Transition to Delegation TLD Launch
56 Step 7 Complete Transition to Delegation Prerequisites o Registry has completed PDT (Step 2) o Contact info. & Credentialing info. approved by ICANN (Step 3 & 4) Registry is invited to Transition to Delegation Registry Provides Delegation PoC if not on file (CIR v2) Registry logs into RZM with IANA Token IANA Completes Requirements Verification IANA Proceeds to Delegation into the Root Who : Delegation PoC Application Primary Contact Where : Customer Portal + IANA RZM When : before end of 2 months to delegate
57 From Registry Onboarding to TLD Launch Registry Agreement Executed Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) 6 weeks or more Step 2: Complete Pre-Delegation Testing Onboarding Step 3: Provide information for credentialing Step 4: Provide onboarding contact information Step 5: Register with TMDB Step 6: Complete TMDB Testing 2 weeks Step 7: Complete Transition to Delegation TLD Launch
58 From Registry Onboarding to TLD Launch Registry Agreement Executed 2 months to delegate into the root (RA Art. 4.3 b) Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) 6 weeks or more Step 2: Complete Pre-Delegation Testing Onboarding Step 3: Provide information for credentialing Step 4: Provide onboarding contact information Step 5: Register with TMDB Step 6: Complete TMDB Testing 2 weeks Step 7: Complete Transition to Delegation TLD Launch
59 Step 7 Complete Transition to Delegation Root Zone Management System (RZM)
60 Step 7 Complete Transition to Delegation IANA Delegation Tips o Delegation POC should be ready and available to consent to proceeding with Delegation o All contact addresses must respond to confirmation o Sponsoring organization must exactly match the contracted party with ICANN (Registry Operator as specified on RA) o s such as [email protected] are not allowed in RZM o Most errors during IANA s technical verifications can be resolved through direct engagement with IANA ([email protected])
61 Step 7 Complete Transition to Delegation More information : o Welcome Kit o
62 From Registry Onboarding to TLD Launch Registry Agreement Executed 2 months to delegate into the root (RA Art. 4.3 b) Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) 6 weeks or more Step 2: Complete Pre-Delegation Testing Onboarding Step 3: Provide information for credentialing Step 4: Provide onboarding contact information Step 5: Register with TMDB Step 6: Complete TMDB Testing 2 weeks Step 7: Complete Transition to Delegation TLD Launch
63 From Registry Onboarding to TLD Launch Registry Agreement Executed 2 months to delegate into the root (RA Art. 4.3 b) Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) 6 weeks or more Step 2: Complete Pre-Delegation Testing Onboarding Step 3: Provide information for credentialing Step 4: Provide onboarding contact information Step 5: Register with TMDB Step 6: Complete TMDB Testing 2 weeks Step 7: Complete Transition to Delegation Step 8: Submit TLD Startup Information TLD Launch Activation of names under Sunrise, Claims & Other LR/QLP Periods
64 Step 8 Submit TLD Startup Information Prerequisites o TLD is delegated (Step 7) o TMDB Testing is certified or exemption applies (Step 6) Registry TLD Startup Information Work Item o o o Registry Submits Sunrise + Claims + LRP Information (optional), TMDB Certificate, Registration Policies & Sunrise Dispute Resolution Procedure ICANN Reviews for completeness & compliance with RPM Requirements, Approves, and Schedules Dates with TMDB Provider When all dates are confirmed, ICANN Publishes Startup Information When : Anytime after Delegation Who : Registry Primary Contact Where : GDD Portal
65 Step 8 Submit TLD Startup Information
66 Step 8 Submit TLD Startup Information Type of Sunrise Sunrise Start & End Dates TM Claims Start & End Dates Required URL for Registry info. Required Attachments (actual documents) URL for Registrars info. - Name - Type - Start & End Date Optional Other Periods (incl. QLP)
67 Step 8 Submit TLD Startup Information Public posting page
68 Step 8 Submit TLD Startup Information More information : o Welcome Kit o RPM Requirements Document ( o o sunrise-claims-periods
69 From Registry Onboarding to TLD Launch Registry Agreement Executed 2 months to delegate into the root (RA Art. 4.3 b) Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) 6 weeks or more Step 2: Complete Pre-Delegation Testing Onboarding Step 3: Provide information for credentialing Step 4: Provide onboarding contact information Step 5: Register with TMDB Step 6: Complete TMDB Testing 2 weeks Step 7: Complete Transition to Delegation Step 8: Submit TLD Startup Information TLD Launch Activation of names under Sunrise, Claims & Other LRP/QLP Periods
70 From Registry Onboarding to TLD Launch Registry Agreement Executed 2 months to delegate into the root (RA Art. 4.3 b) Delegation General Registration Step : Join the gtld Registry Stakeholder Group (Optional) 6 weeks or more Step 2: Complete Pre-Delegation Testing Onboarding Step 3: Provide information for credentialing Step 4: Provide onboarding contact information Step 5: Register with TMDB Step 6: Complete TMDB Testing 2 weeks Step 7: Complete Transition to Delegation Step 8: Submit TLD Startup Information TLD Launch No-Activation Period - 20 days minimum Controlled Interruption 90 days Activation of names under Sunrise, Claims & Other LR/QLP Periods Name Collision Occurrence Management (RA Spec 6.6)
71 Onboarding Systems Recap.
72 From Registry Onboarding to TLD Launch 2 months to delegate into the root (RA Art. 4.3 b) Registry Agreement Executed Delegation Step : Join the gtld Registry Stakeholder Group (Optional) General Registration CSP 6 weeks PDT or more Step 2: Complete Pre-Delegation Testing Onboarding Step 3: Provide information for credentialing Step 4: Provide onboarding contact information Step 5: Register with TMDB Step 6: Complete TMDB Testing TLD Launch 2 weeks Step 8: Submit TLD Startup Info., including QLP is applicable No-Activation Period - 20 days minimum Step 7: Complete Transition to Delegation Controlled Interruption 90 days Activation of names under QLP, Sunrise, Claims & Other LR Periods Name Collision Occurrence Management (RA Spec 6.6)
73 From Registry Onboarding to TLD Launch 2 months to delegate into the root (RA Art. 4.3 b) Registry Agreement Executed Delegation Step : Join the gtld Registry Stakeholder Group (Optional) General Registration CSP 6 weeks PDT or more Step 2: Complete Pre-Delegation Testing Onboarding GDD CZDS Step 3: Provide information for credentialing Step 4: Provide onboarding contact information Step 5: Register with TMDB Step 6: Complete TMDB Testing TLD Launch 2 weeks Step 8: Submit TLD Startup Info., including QLP is applicable No-Activation Period - 20 days minimum Step 7: Complete Transition to Delegation Controlled Interruption 90 days Activation of names under QLP, Sunrise, Claims & Other LR Periods Name Collision Occurrence Management (RA Spec 6.6)
74 From Registry Onboarding to TLD Launch 2 months to delegate into the root (RA Art. 4.3 b) Registry Agreement Executed Delegation Step : Join the gtld Registry Stakeholder Group (Optional) General Registration CSP 6 weeks PDT or more Step 2: Complete Pre-Delegation Testing Onboarding GDD CZDS GDD Step 3: Provide information for credentialing Step 4: Provide onboarding contact information Step 5: Register with TMDB Step 6: Complete TMDB Testing TLD Launch 2 weeks Step 8: Submit TLD Startup Info., including QLP is applicable No-Activation Period - 20 days minimum Step 7: Complete Transition to Delegation Controlled Interruption 90 days Activation of names under QLP, Sunrise, Claims & Other LR Periods Name Collision Occurrence Management (RA Spec 6.6)
75 From Registry Onboarding to TLD Launch 2 months to delegate into the root (RA Art. 4.3 b) Registry Agreement Executed Delegation Step : Join the gtld Registry Stakeholder Group (Optional) General Registration CSP 6 weeks PDT or more Step 2: Complete Pre-Delegation Testing Onboarding GDD CZDS GDD GDD TMDB Step 3: Provide information for credentialing Step 4: Provide onboarding contact information Step 5: Register with TMDB GDD TMDB Step 6: Complete TMDB Testing TLD Launch 2 weeks Step 8: Submit TLD Startup Info., including QLP is applicable No-Activation Period - 20 days minimum Step 7: Complete Transition to Delegation Controlled Interruption 90 days Activation of names under QLP, Sunrise, Claims & Other LR Periods Name Collision Occurrence Management (RA Spec 6.6)
76 From Registry Onboarding to TLD Launch 2 months to delegate into the root (RA Art. 4.3 b) Registry Agreement Executed Delegation Step : Join the gtld Registry Stakeholder Group (Optional) General Registration CSP 6 weeks PDT or more Step 2: Complete Pre-Delegation Testing Onboarding GDD CZDS GDD GDD TMDB Step 3: Provide information for credentialing Step 4: Provide onboarding contact information Step 5: Register with TMDB GDD TMDB CSP 2 weeks RZM Step 6: Complete TMDB Testing Step 7: Complete Transition to Delegation TLD Launch Step 8: Submit TLD Startup Info., including QLP is applicable No-Activation Period - 20 days minimum Controlled Interruption 90 days Activation of names under QLP, Sunrise, Claims & Other LR Periods Name Collision Occurrence Management (RA Spec 6.6)
77 From Registry Onboarding to TLD Launch 2 months to delegate into the root (RA Art. 4.3 b) Registry Agreement Executed Delegation Step : Join the gtld Registry Stakeholder Group (Optional) General Registration CSP 6 weeks PDT or more Step 2: Complete Pre-Delegation Testing Onboarding GDD CZDS GDD GDD TMDB Step 3: Provide information for credentialing Step 4: Provide onboarding contact information Step 5: Register with TMDB GDD TMDB CSP 2 weeks RZM Step 6: Complete TMDB Testing Step 7: Complete Transition to Delegation TLD Launch Step 8: Submit TLD Startup Info., including QLP is applicable No-Activation Period - 20 days minimum GDD Controlled Interruption 90 days Activation of names under QLP, Sunrise, Claims & Other LR Periods Name Collision Occurrence Management (RA Spec 6.6)
78 GDD Portal Updates
79 GDD Portal Enhancements Discussion & Collaboration o GDD Portal User Group workshop at ICANN 5 in Los Angeles o Release notification s sent out to all users in October 204 Recent Enhancements o o o Usability: Summary case count; Sort and filter case list; Emergency contact information; Spec 3 option added to Sunrise Period Perpetual Claims Period option added Upcoming Enhancements New service requests via input forms without using cases (ex: RSEP) Option to add Exclusive Sunrise Period
80 Q&A
Version 2.4 Final. TMDB System User Manual (Registrar)
Version 2.4 Final TMDB System User Manual (Registrar) Table of contents 1. INTRODUCTION... 5 1.1. OVERVIEW OF THE TMDB SYSTEM... 5 1.2. THE INTENDED AUDIENCE FOR THIS DOCUMENT... 5 1.3. OVERVIEW OF THIS
Customer Portal User Guide: Transition to Delegation
NEW GTLD PROGRAM Customer Portal User Guide: Transition to Delegation Version 0.8 Table of Contents About this User Guide... 2 Introduction to the Customer Portal... 3 Logging in with your User Name and
Pre Delegation Testing (PDT) Frequently Asked Questions (FAQ)
Pre Delegation Testing (PDT) Frequently Asked Questions (FAQ) [Ver 1.7 2013-06- 04] List of contents General questions Who do I contact with questions about Pre- Delegation Testing?... 3 What is the process
DOMAIN NAME DAY. + Helsinki; 14 th February; 2014. + Nigel Hickson, ICANN
DOMAIN NAME DAY + Helsinki; 14 th February; 2014 + Nigel Hickson, ICANN 1 AGENDA + gtlds and all that + The European and global debate on Internet Governance 2 Internet Corporation for Assigned Names
New gtld Program Reviews and Assessments. Draft Work Plan
New gtld Program Reviews and Assessments Draft Work Plan 27 January 2015 Table of Contents 1 Introduction 3 1.1 ICANN 4 1.2 About the New gtld Program 5 1.3 About this Work Plan 9 2 Program Implementation
Policy Overview and Definitions
Overview The following policies, which govern the top level domain (TLD or Registry) indicated on Schedule A, are based on policies and best practices drawn from ICANN, WIPO, and other relevant sources,
New gtld Basics New Internet Extensions
New gtld Basics New Internet Extensions Agenda Overview about domain names, gtld timeline and the New gtld Program Why is ICANN doing this; potential impact of this initiative to businesses, governments,
.IBM TLD Registration Policy
I. Introduction These registration conditions govern the rights and obligations of the Registry Operator, International Business Machines Corporation ( Registry Operator or IBM ), and the accredited registrars,
Registrar Ramp Up Process. Prepared by Afilias
Registrar Ramp Up Process Prepared by Afilias December 2013 Contents Introduction... 2 Get Started By Having Someone Contact You... 2 Become a Registrar... 3 Step One Business and Legal Process... 3 Step
Verisign/ICANN Proposal in Response to NTIA Request
Verisign/ICANN Proposal in Response to NTIA Request Root Zone Administrator Proposal Related to the IANA Functions Stewardship Transition Introduction On March 14, 2014, NTIA announced its intent to transition
Monitoring the DNS. Gustavo Lozano Event Name XX XXXX 2015
Monitoring the DNS Gustavo Lozano Event Name XX XXXX 2015 Agenda 1 2 3 Components of the DNS Monitoring gtlds Monitoring other components of the DNS 4 5 Monitoring system Conclusion 2 Components of the
Citation and commencement 1. (1) These Regulations may be cited as the Electronic Communications (Domain Name Administration) Regulations, 2015.
LEGAL NOTICE NO OF 2014 THE ELECTRONIC COMMUNICATIONS ACT, 2013 (Act No. 9 of 2014) THE ELECTRONIC COMMUNICATIONS (DOMAIN NAME ADMINISTRATION) REGULATIONS, 2015 ARRANGEMENT OF REGULATIONS Regulation 1.
Quick Start Guide. Cerberus FTP is distributed in Canada through C&C Software. Visit us today at www.ccsoftware.ca!
Quick Start Guide Cerberus FTP is distributed in Canada through C&C Software. Visit us today at www.ccsoftware.ca! How to Setup a File Server with Cerberus FTP Server FTP and SSH SFTP are application protocols
.SANDVIK DOMAIN NAME REGISTRATION POLICIES
.SANDVIK DOMAIN NAME REGISTRATION POLICIES Page 1 of 18 TABLE OF CONTENTS CHAPTER 1. Definitions, scope of application and eligibility... 3 Article 1. Definitions... 3 Article 2. Scope of application...
.ASIA Reserved Names Policies
Prepared by: DotAsia Organisation Date: 10-Aug-2007 Reference #: N/A Status: Complete Version: 2.0 Executive Summary This document describes the Reserved Names Policies for the.asia Registry. These policies
General Launch Policy
General Launch Policy Desi Networks, LLC Version 1, March 2014 1. Introduction This policy has been developed to describe the Launch Program for the.desi gtld (Registry). The Launch Program has been designed
IETF Update on RDAP. ICANN52 Singapore CCTLD Tech Day. Marc Blanchet Viagénie [email protected]
IETF Update on RDAP ICANN52 Singapore CCTLD Tech Day Marc Blanchet Viagénie [email protected] February 9th 2015 From Whois to RDAP RDAP: Registration Data Access Protocol replacement of whois structured
Architecture, Implementations, Integrations, and Technical Overview
Architecture, Implementations, Integrations, and Technical Overview Introduction System Architecture & Infrastructure Implementation Parent Portal Medical Center Strategy Integrations SIS Immunization
Domain Name Registration Policy,
1. General a. The Registry operates and administers the generic Top Level Domain (TLD).NRW and makes possible the registration of Domain Names under this TLD. b. Registrants wishing to register one or
14. Privacy Policies. 14.1. Introduction
14. Privacy Policies 14.1. Introduction 14.2. Policy Accent Media Ltd, incorporated in England, is the Registry Operator for the Top Level Domain TLD.tickets ( the Registry ). As a company registered in
FAQ (Frequently Asked Questions)
FAQ (Frequently Asked Questions) Specific Questions about Afilias Managed DNS What is the Afilias DNS network? How long has Afilias been working within the DNS market? What are the names of the Afilias
Global Registry Services Registrar Frequently Asked Questions (FAQ) for TLDs using Afilias Technology
Global Registry Services Registrar Frequently Asked Questions (FAQ) for TLDs using Afilias Technology Prepared by Afilias November 2013 Table of Contents Foreword... 1 Non-Technical... 1 Accreditation,
Highlights ccnso Members Meeting London 22-26 June 2014
Meeting Highlights Highlights ccnso Members Meeting London 22-26 June 2014 Membership ccnso On 25 June the (Romanian) National Institute for R&D in Informatics, the manager for.ro (Romania), became member
Guidance for Preparing Domain Name Orders, Seizures & Takedowns
Guidance for Preparing Domain Name Orders, Seizures & Takedowns Abstract This thought paper offers guidance for anyone who prepares an order that seeks to seize or take down domain names. Its purpose is
ARTE TLD REGISTRATION POLICY
ARTE TLD REGISTRATION POLICY 1. ELIGIBILITY Only Association Relative à la Télévision Européenne G.E.I.E. (ARTE), its Affiliates or the Trademark Licensees could be eligible to register a Domain Name under
.AXA Domain Policy. As of March 3, 2014
.AXA Domain Policy As of March 3, 2014 The.AXA TLD, also designated as the AXA domain or dot-axa, is a generic Top Level Domain string exclusively developed for the AXA insurance group and will be therefore
Configure Backup Server for Cisco Unified Communications Manager
Configure Backup Server for Cisco Unified Communications Manager Document ID: 110309 Contents Introduction Prerequisites Requirements Components Used Conventions Configure a Backup Server for Cisco Unified
IANA Functions to cctlds Sofia, Bulgaria September 2008
IANA Functions to cctlds Sofia, Bulgaria September 2008 Kim Davies Internet Assigned Numbers Authority Internet Corporation for Assigned Names & Numbers What is IANA? Internet Assigned Numbers Authority
Year End Results for FY10 Trimester Goals Color Key: T1 T2 T3
Preserve DNS Security and Stability Root Key Signing Key (KSK) - Implement production-level root signing of KSK processes Generic Signing Infrastructure - Implement generic signing infrastructure and sign
Domain Name Registration Policies (Version 1.1 June 10, 2014)
Domain Name Registration Policies (Version 1.1 June 10, 2014) Contents Contents... 2 Definitions... 3 Introduction... 5 Purpose and Principles of the.tokyo TLD... 5 Launch Phases... 6 Chapter 1. The Sunrise
Proposed Service. Name of Proposed Service: Technical description of Proposed Service: Registry-Registrar Two-Factor Authentication Service
Print Date: 2009-06-25 23:04:33 Proposed Service Name of Proposed Service: Registry-Registrar Two-Factor Authentication Service Technical description of Proposed Service: Background: The frequency and
.Brand TLD Designation Application
.Brand TLD Designation Application Internet Corporation for Assigned Names and Numbers ( ICANN ) 12025 Waterfront Drive, Suite 300 Los Angeles, California 90094 Attention: New gtld Program Staff RE: Application
Self-Service Onboarding: Get Access to Smart Net Total Care Portal
Thanks for downloading this copy from the Smart Net Total Care Community. To ensure you have the latest information, be sure to visit the Community regularly to both update this document and download other
CTERA Agent File Sync and Share for Mac
Quick Walkthrough for Mac August 2014 Version 4.1 2014, CTERA Networks. All rights reserved. For more detailed information, refer to the for Mac User Guide, available at http://www.ctera.com/support. 1
1.3 By requesting us to register or manage a domain names or names on your behalf, you agree to:
SPECIAL TERMS AND CONDITIONS FOR DOMAIN NAME MANAGEMENT SERVICES (DOMAIN PORTFOLIO MANAGEMENT SERVICE, LOCAL PRESENCE SERVICES AND ANONYMOUS REGISTRATION SERVICES) 1. Services 1.1 These Special Terms and
ICM Registry White Paper Legal Analysis of.xxx Registry Trademark Liability. Executive Summary
ICM Registry White Paper Legal Analysis of.xxx Registry Trademark Liability As a part of the launch of the.xxx top-level domain ( TLD ), a number of questions arose regarding the protections for existing
SDNP.mw cctld DOMAIN REGISTRATION POLICY Ver 1.2 of 23 July 2015
SDNP.mw cctld DOMAIN REGISTRATION POLICY Ver 1.2 of 23 July 2015 Table of Contents 1. DEFNITIONS 2. PURPOSE AND SCOPE 3. ELIGIBILITY 4. CHOOSING A DOMAIN NAME TO REGISTER 5. SELECTING A REGISTRAR 6. REGISTERING
Evaluation Guide. Powerful & Immediate Business Web Security via the Cloud
Evaluation Guide Powerful & Immediate Business Web Security via the Cloud Contents 1 Introduction & Product highlights 2 Set up & Configuration 3 Managing your WebTitan Cloud Service 4 Reporting 5 Support
THE CITY OF NEW YORK DEPARTMENT OF INFORMATION TECHNOLOGY AND TELECOMMUNICATIONS (DOITT) (the Agency ) REQUEST FOR PROPOSALS
THE CITY OF NEW YORK DEPARTMENT OF INFORMATION TECHNOLOGY AND TELECOMMUNICATIONS (DOITT) (the Agency ) REQUEST FOR PROPOSALS TITLE: SERVICES TO OBTAIN, OPERATE, MANAGE, ADMINISTER, MAINTAIN AND MARKET
Defender 5.7 - Token Deployment System Quick Start Guide
Defender 5.7 - Token Deployment System Quick Start Guide This guide describes how to install, configure and use the Defender Token Deployment System, based on default settings and how to self register
"Branding Strategies in light of the. Kevin G. Smith Sughrue Mion, PLLC Washington, D.C.
"Branding Strategies in light of the new Top Level Domains" What Brand Owners Can do to Protect Themselves and the Mechanism of the TMCH Kevin G. Smith Sughrue Mion, PLLC Washington, D.C. [email protected]
Best Practices in Domain Name Registry Solutions Understanding the Technical Requirements of ICANN's Applicant Guidebook
Best Practices in Domain Name Registry Solutions Understanding the Technical Requirements of ICANN's Applicant Guidebook Adrian Kinderis - CEO AusRegistry International Agenda What options should
Installation Guide. SafeNet Authentication Service
SafeNet Authentication Service Installation Guide Technical Manual Template Release 1.0, PN: 000-000000-000, Rev. A, March 2013, Copyright 2013 SafeNet, Inc. All rights reserved. 1 Document Information
INUVIKA OVD SUPPORT SUPPORT SYSTEM GUIDE. Mathieu Schires Version 1.1 Published 28/04/2015
INUVIKA OVD SUPPORT SUPPORT SYSTEM GUIDE Mathieu Schires Version 1.1 Published 28/04/2015 This document describes how to use the Inuvika Support System for reporting support incidents related to Inuvika
Redelegation of Country Code Top Level Domains. February 2003
Note: This Paper was prepared by Miriam Sapiro of Summit Strategies International, LLC in May 2002 for the Center for Democracy and Technology (CDT). CDT updated it in June 2002 to reflect the cctld Redelegation
1999-2006 enom, Inc. API response codes
API response codes Introduction When you run a query against the enom API, the response includes a numeric code and a corresponding text message. This allows us to standardize our responses and make them
How to Keep One s Registered Trademark from Becoming a.xxx Domain Name
September 2011 How to Keep One s Registered Trademark from Becoming a.xxx Domain Name BY ROBERT L. SHERMAN & BRADFORD E. YOUNG After years of consideration, the Internet Corporation for Assigned Names
1 Proposed model for trademark claims. 2 Details of the proposed model
This document has been prepared by ARI Registry Services in consultation with Neustar, Verisign and Demand Media. This document has also been reviewed by the TMCH-Tech working group and is now offered
Implementing, Managing, and Maintaining a Microsoft Windows Server 2003 Network Infrastructure: Network Services (5 days)
Implementing, Managing, and Maintaining a Microsoft Windows Server 2003 Network Infrastructure: Network Services (5 days) Course 2277: Five days; Instructor-led Introduction This five-day, instructor-led
Shakambaree Technologies Pvt. Ltd.
Welcome to Support Express by Shakambaree Technologies Pvt. Ltd. Introduction: This document is our sincere effort to put in some regular issues faced by a Digital Signature and USB Token user doing on
October 11, 2013 NEUSTAR REGISTRAR REFERENCE GUIDE
October 11, 2013 NEUSTAR REGISTRAR REFERENCE GUIDE This document is for informational purposes only. NEUSTAR MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.
Password Reset PRO INSTALLATION GUIDE
Password Reset PRO INSTALLATION GUIDE This guide covers the new features and settings available in Password Reset PRO. Please read this guide completely to ensure a trouble-free installation. March 2009
API Operational Test and Evaluation Platform (API OT&E platform) User manual. Version 2.0
API Operational Test and Evaluation Platform (API OT&E platform) User manual Version 2.0 22 november 2013 TABLE OF CONTENTS 1. Introduction 3 1.1. Overview of the API OT&E platform 3 1.2. The intended
First version of the document.
First version of the document. 2.1 Access to web forms... 6 2.2 Menu... 7 2.3 Dashboard... 8 2.4 Domain names... 9 2.4.1 Create domain name... 9 2.4.2 Query domain name details...11 2.4.3 Registrar domain
DUBLIN Registration Data Access Protocol (RDAP) Implementation
DUBLIN Registration Data Access Protocol (RDAP) Implementation Wednesday, October 21, 2015 12:30 to 13:45 IST ICANN54 Dublin, Ireland UNIDTIFIED MALE: October 21, 2015. This is the Registration Data Access
Domain Names and their Role for the Net
Domain Names and their Role for the Net Hans Peter Dittler Karlsruhe 2000 H.P. Dittler - BRAINTEC Netzwerk-Consulting 27.6.2002 1 History 1962 first idea 1967 early planning for a real network 1969 ARPANET
Partner: Address: Tel. No.: Contact: Contact Title: Contact s email: Effective Date: Partner s Web Site(s):
Partner: Address: Tel. No.: Contact: Contact Title: Contact s email: Effective Date: Partner s Web Site(s): This Partner Program Agreement (the "Partner Agreement") is made and entered into between Register.com.
.INFO Agreement Appendix 1 Data Escrow Specification (22 August 2013)
.INFO Agreement Appendix 1 Data Escrow Specification (22 August 2013) Registry Operator and ICANN agree to engage in good faith negotiations to replace this Appendix with a Data Escrow Specification equivalent
Policies for.design TLD Launch, Registration, and Acceptable Use
Policies for.design TLD Launch, Registration, and Acceptable Use Jan. 22, 2015 Top Level Design LLC ( the Registry ) supports open, unrestricted Top Level Domains in the interest of the free flow of information
The Redesigned SAT. SAT Score Reporting Portal and Managing Access
The Redesigned SAT SAT Score Reporting Portal and Managing Access Agenda + The Redesigned SAT Background + Steps for Implementing the Electronic Score Report (ESR) Updates + Manage Access to the SAT Higher
Configuration Guide - OneDesk to SalesForce Connector
Configuration Guide - OneDesk to SalesForce Connector Introduction The OneDesk to SalesForce Connector allows users to capture customer feedback and issues in OneDesk without leaving their familiar SalesForce