Upload
others
View
9
Download
0
Embed Size (px)
Citation preview
1
REGISTRYAGREEMENT
ThisREGISTRYAGREEMENT(this“Agreement”)isenteredintoasof30June2019(the“EffectiveDate”)betweenInternetCorporationforAssignedNamesandNumbers,aCalifornianonprofitpublicbenefitcorporation(“ICANN”),andPublicInterestRegistry,aPennsylvanianon-profitcorporation(“RegistryOperator”).
ARTICLE 1.
DELEGATIONANDOPERATIONOFTOP–LEVELDOMAIN;REPRESENTATIONSANDWARRANTIES
1.1 DomainandDesignation.TheTop-LevelDomaintowhichthisAgreementappliesis.org(the“TLD”).UpontheEffectiveDateanduntiltheearlieroftheexpirationoftheTerm(asdefinedinSection4.1)ortheterminationofthisAgreementpursuanttoArticle4,ICANNdesignatesRegistryOperatorastheregistryoperatorfortheTLD,subjecttotherequirementsandnecessaryapprovalsfordelegationoftheTLDandentryintotheroot-zone.
1.2 TechnicalFeasibilityofString.WhileICANNhasencouragedandwillcontinuetoencourageuniversalacceptanceofalltop-leveldomainstringsacrosstheInternet,certaintop-leveldomainstringsmayencounterdifficultyinacceptancebyISPsandwebhostersand/orvalidationbywebapplications.RegistryOperatorshallberesponsibleforensuringtoitssatisfactionthetechnicalfeasibilityoftheTLDstringpriortoenteringintothisAgreement.
1.3 RepresentationsandWarranties.
(a) RegistryOperatorrepresentsandwarrantstoICANNasfollows:
(i) allmaterialinformationprovidedandstatementsmadeintheregistryTLDapplication,andstatementsmadeinwritingduringthenegotiationofthisAgreement,weretrueandcorrectinallmaterialrespectsatthetimemade,andsuchinformationorstatementscontinuetobetrueandcorrectinallmaterialrespectsasoftheEffectiveDateexceptasotherwisepreviouslydisclosedinwritingbyRegistryOperatortoICANN;
(ii) RegistryOperatorisdulyorganized,validlyexistingandingoodstandingunderthelawsofthejurisdictionsetforthinthepreamblehereto,andRegistryOperatorhasallrequisitepowerandauthorityandhasobtainedallnecessaryapprovalstoenterintoanddulyexecuteanddeliverthisAgreement;and
(iii) RegistryOperatorhasdeliveredtoICANNadulyexecutedinstrumentthatsecuresthefundsrequiredtoperformregistryfunctionsfortheTLDintheeventoftheterminationorexpirationofthisAgreement(the“ContinuedOperationsInstrument”),andsuchinstrumentisabinding
2
obligationofthepartiesthereto,enforceableagainstthepartiestheretoinaccordancewithitsterms.
(b) ICANNrepresentsandwarrantstoRegistryOperatorthatICANNisanonprofitpublicbenefitcorporationdulyorganized,validlyexistingandingoodstandingunderthelawsoftheStateofCalifornia,UnitedStatesofAmerica.ICANNhasallrequisitepowerandauthorityandhasobtainedallnecessarycorporateapprovalstoenterintoanddulyexecuteanddeliverthisAgreement.
ARTICLE 2.
COVENANTSOFREGISTRYOPERATOR
RegistryOperatorcovenantsandagreeswithICANNasfollows:
2.1 ApprovedServices;AdditionalServices.RegistryOperatorshallbeentitledtoprovidetheRegistryServicesdescribedinclauses(a)and(b)ofthefirstparagraphofSection2.1intheSpecification6attachedhereto(“Specification6”)andsuchotherRegistryServicessetforthonExhibitA(collectively,the“ApprovedServices”).IfRegistryOperatordesirestoprovideanyRegistryServicethatisnotanApprovedServiceorisamaterialmodificationtoanApprovedService(each,an“AdditionalService”),RegistryOperatorshallsubmitarequestforapprovalofsuchAdditionalServicepursuanttotheRegistryServicesEvaluationPolicyathttp://www.icann.org/en/registries/rsep/rsep.html,assuchpolicymaybeamendedfromtimetotimeinaccordancewiththebylawsofICANN(asamendedfromtimetotime,the“ICANNBylaws”)applicabletoConsensusPolicies(the“RSEP”).RegistryOperatormayofferAdditionalServicesonlywiththewrittenapprovalofICANN,and,uponanysuchapproval,suchAdditionalServicesshallbedeemedRegistryServicesunderthisAgreement.Initsreasonablediscretion,ICANNmayrequireanamendmenttothisAgreementreflectingtheprovisionofanyAdditionalServicewhichisapprovedpursuanttotheRSEP,whichamendmentshallbeinaformreasonablyacceptabletotheparties.
2.2 CompliancewithConsensusPoliciesandTemporaryPolicies.RegistryOperatorshallcomplywithandimplementallConsensusPoliciesandTemporaryPoliciesfoundat<http://www.icann.org/general/consensus-policies.htm>,asoftheEffectiveDateandasmayinthefuturebedevelopedandadoptedinaccordancewiththeICANNBylaws,providedsuchfutureConsensusPolicesandTemporaryPoliciesareadoptedinaccordancewiththeprocedureandrelatetothosetopicsandsubjecttothoselimitationssetforthinSpecification1attachedhereto(“Specification1”).
2.3 DataEscrow.RegistryOperatorshallcomplywiththeregistrydataescrowproceduressetforthinSpecification2attachedhereto(“Specification2”)withinfourteen(14)calendardaysafterdelegation.
2.4 MonthlyReporting.Withintwenty(20)calendardaysfollowingtheendofeachcalendarmonth,commencingwiththefirstcalendarmonthinwhichtheTLDisdelegatedintherootzone,RegistryOperatorshalldelivertoICANNreportsintheformat
3
setforthinSpecification3attachedhereto(“Specification3”);provided,however,thatiftheTLDisdelegatedintherootzoneafterthefifteenth(15th)calendardayofthecalendarmonth,RegistryOperatormaydeferthedeliveryofthereportsforsuchfirstcalendarmonthandinsteaddelivertoICANNsuchmonth’sreportsnolaterthanthetimethatRegistryOperatorisrequiredtodeliverthereportsfortheimmediatelyfollowingcalendarmonth.RegistryOperatormustincludeinthePer-RegistrarTransactionsReportanydomainnamecreatedduringpre-delegationtestingthathasnotbeendeletedasofthetimeofdelegation(notablybutnotlimitedtodomainsregisteredbyRegistrarIDs9995and/or9996).
2.5 PublicationofRegistrationData.RegistryOperatorshallprovidepublicaccesstoregistrationdatainaccordancewithSpecification4attachedhereto(“Specification4”).
2.6 ReservedNames.ExcepttotheextentthatICANNotherwiseexpresslyauthorizesinwriting,RegistryOperatorshallcomplywiththerequirementssetforthinSpecification5attachedhereto(“Specification5”).RegistryOperatormayatanytimeestablishormodifypoliciesconcerningRegistryOperator’sabilitytoreserve(i.e.,withholdfromregistrationorallocatetoRegistryOperator,butnotregistertothirdparties,delegate,use,activateintheDNSorotherwisemakeavailable)orblockadditionalcharacterstringswithintheTLDatitsdiscretion.ExceptasspecifiedinSpecification5,ifRegistryOperatoristheregistrantforanydomainnamesintheregistryTLD,suchregistrationsmustbethroughanICANNaccreditedregistrar,andwillbeconsideredTransactions(asdefinedinSection6.1)forpurposesofcalculatingtheRegistry-leveltransactionfeetobepaidtoICANNbyRegistryOperatorpursuanttoSection6.1.
2.7 RegistryInteroperabilityandContinuity.RegistryOperatorshallcomplywiththeRegistryInteroperabilityandContinuitySpecificationsassetforthinSpecification6attachedhereto(“Specification6”).
2.8 ProtectionofLegalRightsofThirdParties.RegistryOperatormustspecify,andcomplywith,theprocessesandproceduresforlaunchoftheTLDandinitialregistration-relatedandongoingprotectionofthelegalrightsofthirdpartiesassetforthSpecification7attachedhereto(“Specification7”).RegistryOperatormay,atitselection,implementadditionalprotectionsofthelegalrightsofthirdparties.AnychangesormodificationstotheprocessandproceduresrequiredbySpecification7followingtheEffectiveDatemustbeapprovedinadvancebyICANNinwriting.RegistryOperatormustcomplywithallremediesimposedbyICANNpursuanttoSection2ofSpecification7,subjecttoRegistryOperator’srighttochallengesuchremediesassetforthintheapplicableproceduredescribedtherein.RegistryOperatorshalltakereasonablestepstoinvestigateandrespondtoanyreportsfromlawenforcementandgovernmentalandquasi-governmentalagenciesofillegalconductinconnectionwiththeuseoftheTLD.Inrespondingtosuchreports,RegistryOperatorwillnotberequiredtotakeanyactionincontraventionofapplicablelaw.
4
2.9 Registrars.
(a) AlldomainnameregistrationsintheTLDmustberegisteredthroughanICANNaccreditedregistrar;provided,thatRegistryOperatorneednotusearegistrarifitregistersnamesinitsownnameinordertowithholdsuchnamesfromdelegationoruseinaccordancewithSection2.6.SubjecttotherequirementsofSpecification11,RegistryOperatormustprovidenon-discriminatoryaccesstoRegistryServicestoallICANNaccreditedregistrarsthatenterintoandareincompliancewiththeregistry-registraragreementfortheTLD;providedthatRegistryOperatormayestablishnon-discriminatorycriteriaforqualificationtoregisternamesintheTLDthatarereasonablyrelatedtotheproperfunctioningoftheTLD.RegistryOperatormustuseauniformnon-discriminatoryagreementwithallregistrarsauthorizedtoregisternamesintheTLD(the“Registry-RegistrarAgreement”).RegistryOperatormayamendtheRegistry-RegistrarAgreementfromtimetotime;provided,however,thatanymaterialrevisionstheretomustbeapprovedbyICANNbeforeanysuchrevisionsbecomeeffectiveandbindingonanyregistrar.RegistryOperatorwillprovideICANNandallregistrarsauthorizedtoregisternamesintheTLDatleastfifteen(15)calendardayswrittennoticeofanyrevisionstotheRegistry-RegistrarAgreementbeforeanysuchrevisionsbecomeeffectiveandbindingonanyregistrar.Duringsuchperiod,ICANNwilldeterminewhethersuchproposedrevisionsareimmaterial,potentiallymaterialormaterialinnature.IfICANNhasnotprovidedRegistryOperatorwithnoticeofitsdeterminationwithinsuchfifteen(15)calendar-dayperiod,ICANNshallbedeemedtohavedeterminedthatsuchproposedrevisionsareimmaterialinnature.IfICANNdetermines,orisdeemedtohavedeterminedunderthisSection2.9(a),thatsuchrevisionsareimmaterial,thenRegistryOperatormayadoptandimplementsuchrevisions.IfICANNdeterminessuchrevisionsareeithermaterialorpotentiallymaterial,ICANNwillthereafterfollowitsprocedureregardingreviewandapprovalofchangestoRegistry-RegistrarAgreementsat<http://www.icann.org/en/resources/registries/rra-amendment-procedure>,andsuchrevisionsmaynotbeadoptedandimplementeduntilapprovedbyICANN.NotwithstandingtheforegoingprovisionsofthisSection2.9(a),anychangetotheRegistry-RegistrarAgreementthatrelatesexclusivelytothefeechargedbyRegistryOperatortoregisterdomainnamesintheTLDwillnotbesubjecttothenoticeandapprovalprocessspecifiedinthisSection2.9(a),butwillbesubjecttotherequirementsinSection2.10below.
(b) IfRegistryOperator(i)becomesanAffiliateorresellerofanICANNaccreditedregistrar,or(ii)subcontractstheprovisionofanyRegistryServicestoanICANNaccreditedregistrar,registrarreselleroranyoftheirrespectiveAffiliates,then,ineithersuchcaseof(i)or(ii)above,RegistryOperatorwillgiveICANNpromptnoticeofthecontract,transactionorotherarrangementthatresultedinsuchaffiliation,resellerrelationshiporsubcontract,asapplicable,including,ifrequestedbyICANN,copiesofanycontractrelatingthereto;provided,thatICANNwilltreatsuchcontractorrelateddocumentsthatareappropriatelymarkedasconfidential(asrequiredbySection7.15)asConfidentialInformationofRegistryOperatorinaccordancewithSection7.15(exceptthatICANNmaydisclosesuchcontractandrelateddocumentstorelevantcompetitionauthorities).ICANNreservestheright,butnottheobligation,toreferanysuchcontract,
5
relateddocuments,transactionorotherarrangementtorelevantcompetitionauthoritiesintheeventthatICANNdeterminesthatsuchcontract,relateddocuments,transactionorotherarrangementmightraisesignificantcompetitionissuesunderapplicablelaw.Iffeasibleandappropriateunderthecircumstances,ICANNwillgiveRegistryOperatoradvancenoticepriortomakinganysuchreferraltoacompetitionauthority.
(c) ForthepurposesofthisAgreement:(i)“Affiliate”meansapersonorentitythat,directlyorindirectly,throughoneormoreintermediaries,orincombinationwithoneormoreotherpersonsorentities,controls,iscontrolledby,orisundercommoncontrolwith,thepersonorentityspecified,and(ii)“control”(includingtheterms“controlledby”and“undercommoncontrolwith”)meansthepossession,directlyorindirectly,ofthepowertodirectorcausethedirectionofthemanagementorpoliciesofapersonorentity,whetherthroughtheownershipofsecurities,astrusteeorexecutor,byservingasanemployeeoramemberofaboardofdirectorsorequivalentgoverningbody,bycontract,bycreditarrangementorotherwise.
2.10 PricingforRegistryServices.
(a) Withrespecttoinitialdomainnameregistrations,RegistryOperatorshallprovideeachICANNaccreditedregistrarthathasexecutedtheRegistry-RegistrarAgreementfortheTLDadvancewrittennoticeofanypriceincrease(includingasaresultoftheeliminationofanyrefunds,rebates,discounts,producttyingorotherprogramswhichhadtheeffectofreducingthepricechargedtoregistrars,unlesssuchrefunds,rebates,discounts,producttyingorotherprogramsareofalimiteddurationthatisclearlyandconspicuouslydisclosedtotheregistrarwhenoffered)ofnolessthanthirty(30)calendardays.RegistryOperatorshallofferregistrarstheoptiontoobtaininitialdomainnameregistrationsforperiodsofone(1)toten(10)yearsatthediscretionoftheregistrar,butnogreaterthanten(10)years.
(b) Withrespecttorenewalofdomainnameregistrations,RegistryOperatorshallprovideeachICANNaccreditedregistrarthathasexecutedtheRegistry-RegistrarAgreementfortheTLDadvancewrittennoticeofanypriceincrease(includingasaresultoftheeliminationofanyrefunds,rebates,discounts,producttying,QualifiedMarketingProgramsorotherprogramswhichhadtheeffectofreducingthepricechargedtoregistrars)ofnolessthanonehundredeighty(180)calendardays.Notwithstandingtheforegoingsentence,withrespecttorenewalofdomainnameregistrations:(i)RegistryOperatorneedonlyprovidethirty(30)calendardaysnoticeofanypriceincreaseiftheresultingpriceislessthanorequalto(A)fortheperiodbeginningontheEffectiveDateandendingtwelve(12)monthsfollowingtheEffectiveDate,theinitialpricechargedforregistrationsintheTLD,or(B)forsubsequentperiods,apriceforwhichRegistryOperatorprovidedanoticepursuanttothefirstsentenceofthisSection2.10(b)withinthetwelve(12)monthperiodprecedingtheeffectivedateoftheproposedpriceincrease;and(ii)RegistryOperatorneednotprovidenoticeofanypriceincreasefortheimpositionoftheVariableRegistry-LevelFeesetforthinSection6.3.RegistryOperatorshallofferregistrarstheoptiontoobtaindomainnameregistrationrenewalsatthecurrentprice(i.e.,theprice
6
inplacepriortoanynoticedincrease)forperiodsofone(1)toten(10)yearsatthediscretionoftheregistrar,butnogreaterthanten(10)years.
(c) Inaddition,RegistryOperatormusthaveuniformpricingforrenewalsofdomainnameregistrations(“RenewalPricing”).ForthepurposesofdeterminingRenewalPricing,thepriceforeachdomainregistrationrenewalmustbeidenticaltothepriceofallotherdomainnameregistrationrenewalsinplaceatthetimeofsuchrenewal,andsuchpricemusttakeintoaccountuniversalapplicationofanyrefunds,rebates,discounts,producttyingorotherprogramsinplaceatthetimeofrenewal.TheforegoingrequirementsofthisSection2.10(c)shallnotapplyfor(i)purposesofdeterminingRenewalPricingiftheregistrarhasprovidedRegistryOperatorwithdocumentationthatdemonstratesthattheapplicableregistrantexpresslyagreedinitsregistrationagreementwithregistrartohigherRenewalPricingatthetimeoftheinitialregistrationofthedomainnamefollowingclearandconspicuousdisclosureofsuchRenewalPricingtosuchregistrant,and(ii)discountedRenewalPricingpursuanttoaQualifiedMarketingProgram(asdefinedbelow).ThepartiesacknowledgethatthepurposeofthisSection2.10(c)istoprohibitabusiveand/ordiscriminatoryRenewalPricingpracticesimposedbyRegistryOperatorwithoutthewrittenconsentoftheapplicableregistrantatthetimeoftheinitialregistrationofthedomainandthisSection2.10(c)willbeinterpretedbroadlytoprohibitsuchpractices.ForpurposesofthisSection2.10(c),a“QualifiedMarketingProgram”isamarketingprogrampursuanttowhichRegistryOperatoroffersdiscountedRenewalPricing,providedthateachofthefollowingcriteriaissatisfied:(i)theprogramandrelateddiscountsareofferedforaperiodoftimenottoexceedonehundredeighty(180)calendardays(withconsecutivesubstantiallysimilarprogramsaggregatedforpurposesofdeterminingthenumberofcalendardaysoftheprogram),(ii)allICANNaccreditedregistrarsareprovidedthesameopportunitytoqualifyforsuchdiscountedRenewalPricing;and(iii)theintentoreffectoftheprogramisnottoexcludeanyparticularclass(es)ofregistrations(e.g.,registrationsheldbylargecorporations)orincreasetherenewalpriceofanyparticularclass(es)ofregistrations.NothinginthisSection2.10(c)shalllimitRegistryOperator’sobligationspursuanttoSection2.10(b).
(d) RegistryOperatorshallprovidepublicquery-basedDNSlookupservicefortheTLD(thatis,operatetheRegistryTLDzoneservers)atitssoleexpense.
2.11 ContractualandOperationalComplianceAudits.
(a) ICANNmayfromtimetotime(nottoexceedtwicepercalendaryear)conduct,orengageathirdpartytoconduct,contractualcomplianceauditstoassesscompliancebyRegistryOperatorwithitsrepresentationsandwarrantiescontainedinArticle1ofthisAgreementanditscovenantscontainedinArticle2ofthisAgreement.Suchauditsshallbetailoredtoachievethepurposeofassessingcompliance,andICANNwill(a)givereasonableadvancenoticeofanysuchaudit,whichnoticeshallspecifyinreasonabledetailthecategoriesofdocuments,dataandotherinformationrequestedbyICANN,and(b)usecommerciallyreasonableeffortstoconductsuchauditduringregularbusinesshoursandinsuchamannerastonotunreasonablydisrupttheoperationsofRegistryOperator.AspartofsuchauditanduponrequestbyICANN,RegistryOperatorshalltimely
7
provideallresponsivedocuments,dataandanyotherinformationreasonablynecessarytodemonstrateRegistryOperator’scompliancewiththisAgreement.Uponnolessthanten(10)calendardaysnotice(unlessotherwiseagreedtobyRegistryOperator),ICANNmay,aspartofanycontractualcomplianceaudit,conductsitevisitsduringregularbusinesshourstoassesscompliancebyRegistryOperatorwithitsrepresentationsandwarrantiescontainedinArticle1ofthisAgreementanditscovenantscontainedinArticle2ofthisAgreement.ICANNwilltreatanyinformationobtainedinconnectionwithsuchauditsthatisappropriatelymarkedasconfidential(asrequiredbySection7.15)asConfidentialInformationofRegistryOperatorinaccordancewithSection7.15.
(b) AnyauditconductedpursuanttoSection2.11(a)willbeatICANN’sexpense,unless(i)RegistryOperator(A)controls,iscontrolledby,isundercommoncontrolorisotherwiseAffiliatedwith,anyICANNaccreditedregistrarorregistrarreselleroranyoftheirrespectiveAffiliates,or(B)hassubcontractedtheprovisionofRegistryServicestoanICANNaccreditedregistrarorregistrarreselleroranyoftheirrespectiveAffiliates,and,ineithercaseof(A)or(B)above,theauditrelatestoRegistryOperator’scompliancewithSection2.14,inwhichcaseRegistryOperatorshallreimburseICANNforallreasonablecostsandexpensesassociatedwiththeportionoftheauditrelatedtoRegistryOperator’scompliancewithSection2.14,or(ii)theauditisrelatedtoadiscrepancyinthefeespaidbyRegistryOperatorhereunderinexcessof5%inagivenquartertoICANN’sdetriment,inwhichcaseRegistryOperatorshallreimburseICANNforallreasonablecostsandexpensesassociatedwiththeentiretyofsuchaudit.Ineithersuchcaseof(i)or(ii)above,suchreimbursementwillbepaidtogetherwiththenextRegistry-LevelFeepaymentduefollowingthedateoftransmittalofthecoststatementforsuchaudit.
(c) NotwithstandingSection2.11(a),ifRegistryOperatorisfoundnottobeincompliancewithitsrepresentationsandwarrantiescontainedinArticle1ofthisAgreementoritscovenantscontainedinArticle2ofthisAgreementintwoconsecutiveauditsconductedpursuanttothisSection2.11,ICANNmayincreasethenumberofsuchauditstoonepercalendarquarter.
(d) RegistryOperatorwillgiveICANNimmediatenoticeofRegistryOperator’sknowledgeofthecommencementofanyoftheproceedingsreferencedinSection4.3(d)ortheoccurrenceofanyofthemattersspecifiedinSection4.3(f).
2.12 ContinuedOperationsInstrument.RegistryOperatorshallcomplywiththetermsandconditionsrelatingtotheContinuedOperationsInstrumentsetforthinSpecification8attachedhereto(“Specification8”).
2.13 EmergencyTransition.RegistryOperatoragreesthat,intheeventthatanyoftheemergencythresholdsforregistryfunctionssetforthinSection6ofSpecification10isreached,ICANNmaydesignateanemergencyinterimregistryoperatoroftheregistryfortheTLD(an“EmergencyOperator”)inaccordancewithICANN’sregistrytransitionprocess(availableat<http://www.icann.org/en/resources/registries/transition-processes>)(asthesamemaybeamendedfromtimetotime,the“RegistryTransitionProcess”)untilsuch
8
timeasRegistryOperatorhasdemonstratedtoICANN’sreasonablesatisfactionthatitcanresumeoperationoftheregistryfortheTLDwithoutthereoccurrenceofsuchfailure.Followingsuchdemonstration,RegistryOperatormaytransitionbackintooperationoftheregistryfortheTLDpursuanttotheproceduressetoutintheRegistryTransitionProcess,providedthatRegistryOperatorpaysallreasonablecostsincurred(i)byICANNasaresultofthedesignationoftheEmergencyOperatorand(ii)bytheEmergencyOperatorinconnectionwiththeoperationoftheregistryfortheTLD,whichcostsshallbedocumentedinreasonabledetailinrecordsthatshallbemadeavailabletoRegistryOperator.IntheeventICANNdesignatesanEmergencyOperatorpursuanttothisSection2.13andtheRegistryTransitionProcess,RegistryOperatorshallprovideICANNoranysuchEmergencyOperatorwithalldata(includingthedataescrowedinaccordancewithSection2.3)regardingoperationsoftheregistryfortheTLDnecessarytomaintainoperationsandregistryfunctionsthatmaybereasonablyrequestedbyICANNorsuchEmergencyOperator.RegistryOperatoragreesthatICANNmaymakeanychangesitdeemsnecessarytotheIANAdatabaseforDNSandWHOISrecordswithrespecttotheTLDintheeventthatanEmergencyOperatorisdesignatedpursuanttothisSection2.13.Inaddition,intheeventofsuchfailure,ICANNshallretainandmayenforceitsrightsundertheContinuedOperationsInstrument.
2.14 RegistryCodeofConduct.InconnectionwiththeoperationoftheregistryfortheTLD,RegistryOperatorshallcomplywiththeRegistryCodeofConductassetforthinSpecification9attachedhereto(“Specification9”).
2.15 CooperationwithEconomicStudies.IfICANNinitiatesorcommissionsaneconomicstudyontheimpactorfunctioningofnewgenerictop-leveldomainsontheInternet,theDNSorrelatedmatters,RegistryOperatorshallreasonablycooperatewithsuchstudy,includingbydeliveringtoICANNoritsdesigneeconductingsuchstudyalldatarelatedtotheoperationoftheTLDreasonablynecessaryforthepurposesofsuchstudyrequestedbyICANNoritsdesignee,provided,thatRegistryOperatormaywithhold(a)anyinternalanalysesorevaluationspreparedbyRegistryOperatorwithrespecttosuchdataand(b)anydatatotheextentthatthedeliveryofsuchdatawouldbeinviolationofapplicablelaw.AnydatadeliveredtoICANNoritsdesigneepursuanttothisSection2.15thatisappropriatelymarkedasconfidential(asrequiredbySection7.15)shallbetreatedasConfidentialInformationofRegistryOperatorinaccordancewithSection7.15,providedthat,ifICANNaggregatesandmakesanonymoussuchdata,ICANNoritsdesigneemaydisclosesuchdatatoanythirdparty.FollowingcompletionofaneconomicstudyforwhichRegistryOperatorhasprovideddata,ICANNwilldestroyalldataprovidedbyRegistryOperatorthathasnotbeenaggregatedandmadeanonymous.
2.16 RegistryPerformanceSpecifications.RegistryPerformanceSpecificationsforoperationoftheTLDwillbeassetforthinSpecification10attachedhereto(“Specification10”).RegistryOperatorshallcomplywithsuchPerformanceSpecificationsand,foraperiodofatleastone(1)year,shallkeeptechnicalandoperationalrecordssufficienttoevidencecompliancewithsuchspecificationsforeachcalendaryearduringtheTerm.
9
2.17 AdditionalPublicInterestCommitments.RegistryOperatorshallcomplywiththepublicinterestcommitmentssetforthinSpecification11attachedhereto(“Specification11”).
2.18 PersonalData.RegistryOperatorshall(i)notifyeachICANN-accreditedregistrarthatisapartytotheRegistry-RegistrarAgreementfortheTLDofthepurposesforwhichdataaboutanyidentifiedoridentifiablenaturalperson(“PersonalData”)submittedtoRegistryOperatorbysuchregistrariscollectedandusedunderthisAgreementorotherwiseandtheintendedrecipients(orcategoriesofrecipients)ofsuchPersonalData,and(ii)requiresuchregistrartoobtaintheconsentofeachregistrantintheTLDforsuchcollectionanduseofPersonalData.RegistryOperatorshalltakereasonablestepstoprotectPersonalDatacollectedfromsuchregistrarfromloss,misuse,unauthorizeddisclosure,alterationordestruction.RegistryOperatorshallnotuseorauthorizetheuseofPersonalDatainawaythatisincompatiblewiththenoticeprovidedtoregistrars.
ARTICLE 3.
COVENANTSOFICANN
ICANNcovenantsandagreeswithRegistryOperatorasfollows:
3.1 OpenandTransparent.ConsistentwithICANN’sexpressedmissionandcorevalues,ICANNshalloperateinanopenandtransparentmanner.
3.2 EquitableTreatment.ICANNshallnotapplystandards,policies,proceduresorpracticesarbitrarily,unjustifiably,orinequitablyandshallnotsingleoutRegistryOperatorfordisparatetreatmentunlessjustifiedbysubstantialandreasonablecause.
3.3 TLDNameservers.ICANNwillusecommerciallyreasonableeffortstoensurethatanychangestotheTLDnameserverdesignationssubmittedtoICANNbyRegistryOperator(inaformatandwithrequiredtechnicalelementsspecifiedbyICANNathttp://www.iana.org/domains/root/willbeimplementedbyICANNwithinseven(7)calendardaysoraspromptlyasfeasiblefollowingtechnicalverifications.
3.4 Root-zoneInformationPublication.ICANN’spublicationofroot-zonecontactinformationfortheTLDwillincludeRegistryOperatoranditsadministrativeandtechnicalcontacts.AnyrequesttomodifythecontactinformationfortheRegistryOperatormustbemadeintheformatspecifiedfromtimetotimebyICANNathttp://www.iana.org/domains/root/.
3.5 AuthoritativeRootDatabase.TotheextentthatICANNisauthorizedtosetpolicywithregardtoanauthoritativerootserversystem(the“AuthoritativeRootServerSystem”),ICANNshallusecommerciallyreasonableeffortsto(a)ensurethattheauthoritativerootwillpointtothetop-leveldomainnameserversdesignatedbyRegistryOperatorfortheTLD,(b)maintainastable,secure,andauthoritativepubliclyavailabledatabaseofrelevantinformationabouttheTLD,inaccordancewithICANNpublicly
10
availablepoliciesandprocedures,and(c)coordinatetheAuthoritativeRootServerSystemsothatitisoperatedandmaintainedinastableandsecuremanner;provided,thatICANNshallnotbeinbreachofthisAgreementandICANNshallhavenoliabilityintheeventthatanythirdparty(includinganygovernmentalentityorinternetserviceprovider)blocksorrestrictsaccesstotheTLDinanyjurisdiction.
ARTICLE 4.
TERMANDTERMINATION
4.1 Term.ThetermofthisAgreementwillbeten(10)yearsfromtheEffectiveDate(assuchtermmaybeextendedpursuanttoSection4.2,the“Term”).
4.2 Renewal.
(a) ThisAgreementwillberenewedforsuccessiveperiodsoften(10)yearsupontheexpirationoftheinitialTermsetforthinSection4.1andeachsuccessiveTerm,unless:
(i) FollowingnoticebyICANNtoRegistryOperatorofafundamentalandmaterialbreachofRegistryOperator’scovenantssetforthinArticle2orbreachofitspaymentobligationsunderArticle6ofthisAgreement,whichnoticeshallincludewithspecificitythedetailsoftheallegedbreach,andsuchbreachhasnotbeencuredwithinthirty(30)calendardaysofsuchnotice,(A)anarbitratororcourtofcompetentjurisdictionhasfinallydeterminedthatRegistryOperatorhasbeeninfundamentalandmaterialbreachofsuchcovenant(s)orinbreachofitspaymentobligations,and(B)RegistryOperatorhasfailedtocomplywithsuchdeterminationandcuresuchbreachwithinten(10)calendardaysorsuchothertimeperiodasmaybedeterminedbythearbitratororcourtofcompetentjurisdiction;or
(ii) DuringthethencurrentTerm,RegistryOperatorshallhavebeenfoundbyanarbitrator(pursuanttoSection5.2ofthisAgreement)oracourtofcompetentjurisdictiononatleastthree(3)separateoccasionstohavebeenin(A)fundamentalandmaterialbreach(whetherornotcured)ofRegistryOperator’scovenantssetforthinArticle2or(B)breachofitspaymentobligationsunderArticle6ofthisAgreement.
(b) UpontheoccurrenceoftheeventssetforthinSection4.2(a)(i)or(ii),theAgreementshallterminateattheexpirationofthethen-currentTerm.
4.3 TerminationbyICANN.
(a) ICANNmay,uponnoticetoRegistryOperator,terminatethisAgreementif:(i)RegistryOperatorfailstocure(A)anyfundamentalandmaterialbreachofRegistryOperator’srepresentationsandwarrantiessetforthinArticle1orcovenants
11
setforthinArticle2,or(B)anybreachofRegistryOperator’spaymentobligationssetforthinArticle6ofthisAgreement,eachwithinthirty(30)calendardaysafterICANNgivesRegistryOperatornoticeofsuchbreach,whichnoticewillincludewithspecificitythedetailsoftheallegedbreach,(ii)anarbitratororcourtofcompetentjurisdictionhasfinallydeterminedthatRegistryOperatorisinfundamentalandmaterialbreachofsuchcovenant(s)orinbreachofitspaymentobligations,and(iii)RegistryOperatorfailstocomplywithsuchdeterminationandcuresuchbreachwithinten(10)calendardaysorsuchothertimeperiodasmaybedeterminedbythearbitratororcourtofcompetentjurisdiction.
(b) ICANNmay,uponnoticetoRegistryOperator,terminatethisAgreementifRegistryOperatorfailstocompletealltestingandprocedures(identifiedbyICANNinwritingtoRegistryOperatorpriortothedatehereof)fordelegationoftheTLDintotherootzonewithintwelve(12)monthsoftheEffectiveDate.RegistryOperatormayrequestanextensionforuptoadditionaltwelve(12)monthsfordelegationifitcandemonstrate,toICANN’sreasonablesatisfaction,thatRegistryOperatorisworkingdiligentlyandingoodfaithtowardsuccessfullycompletingthestepsnecessaryfordelegationoftheTLD.AnyfeespaidbyRegistryOperatortoICANNpriortosuchterminationdateshallberetainedbyICANNinfull.
(c) ICANNmay,uponnoticetoRegistryOperator,terminatethisAgreementif(i)RegistryOperatorfailstocureamaterialbreachofRegistryOperator’sobligationssetforthinSection2.12ofthisAgreementwithinthirty(30)calendardaysofdeliveryofnoticeofsuchbreachbyICANN,oriftheContinuedOperationsInstrumentisnotineffectforgreaterthansixty(60)consecutivecalendardaysatanytimefollowingtheEffectiveDate,(ii)anarbitratororcourtofcompetentjurisdictionhasfinallydeterminedthatRegistryOperatorisinmaterialbreachofsuchcovenant,and(iii)RegistryOperatorfailstocuresuchbreachwithinten(10)calendardaysorsuchothertimeperiodasmaybedeterminedbythearbitratororcourtofcompetentjurisdiction.
(d) ICANNmay,uponnoticetoRegistryOperator,terminatethisAgreementif(i)RegistryOperatormakesanassignmentforthebenefitofcreditorsorsimilaract,(ii)attachment,garnishmentorsimilarproceedingsarecommencedagainstRegistryOperator,whichproceedingsareamaterialthreattoRegistryOperator’sabilitytooperatetheregistryfortheTLD,andarenotdismissedwithinsixty(60)calendardaysoftheircommencement,(iii)atrustee,receiver,liquidatororequivalentisappointedinplaceofRegistryOperatorormaintainscontroloveranyofRegistryOperator’sproperty,(iv)executionislevieduponanymaterialpropertyofRegistryOperatorthat,iflevied,wouldreasonablybeexpectedtomateriallyandadverselyaffectRegistryOperator’sabilitytooperatetheregistryfortheTLD,(v)proceedingsareinstitutedbyoragainstRegistryOperatorunderanybankruptcy,insolvency,reorganizationorotherlawsrelatingtothereliefofdebtorsandsuchproceedingsarenotdismissedwithinsixty(60)calendardaysoftheircommencement(ifsuchproceedingsareinstitutedbyRegistryOperatororitsAffiliates)oronehundredandeighty(180)calendardaysoftheircommencement(ifsuchproceedingsareinstitutedbyathirdpartyagainstRegistryOperator),or(vi)RegistryOperatorfilesforprotectionundertheUnitedStatesBankruptcyCode,11U.S.C.Section
12
101,etseq.,oraforeignequivalentorliquidates,dissolvesorotherwisediscontinuesitsoperationsortheoperationoftheTLD.
(e) ICANNmay,uponthirty(30)calendardays’noticetoRegistryOperator,terminatethisAgreementpursuanttoadeterminationbyanyPDDRPpanelorRRDRPpanelunderSection2ofSpecification7oradeterminationbyanyPICDRPpanelunderSection2,Section3oranyotherapplicableSectionofSpecification11,subjecttoRegistryOperator’srighttochallengesuchterminationassetforthintheapplicableproceduredescribedtherein.
(f) ICANNmay,uponnoticetoRegistryOperator,terminatethisAgreementif(i)RegistryOperatorknowinglyemploysanyofficerwhoisconvictedofamisdemeanorrelatedtofinancialactivitiesorofanyfelony,orisjudgedbyacourtofcompetentjurisdictiontohavecommittedfraudorbreachoffiduciaryduty,oristhesubjectofajudicialdeterminationthatICANNreasonablydeemsasthesubstantiveequivalentofanyoftheforegoingandsuchofficerisnotterminatedwithinthirty(30)calendardaysofRegistryOperator’sknowledgeoftheforegoing,or(ii)anymemberofRegistryOperator’sboardofdirectorsorsimilargoverningbodyisconvictedofamisdemeanorrelatedtofinancialactivitiesorofanyfelony,orisjudgedbyacourtofcompetentjurisdictiontohavecommittedfraudorbreachoffiduciaryduty,oristhesubjectofajudicialdeterminationthatICANNreasonablydeemsasthesubstantiveequivalentofanyoftheforegoingandsuchmemberisnotremovedfromRegistryOperator’sboardofdirectorsorsimilargoverningbodywithinthirty(30)calendardaysofRegistryOperator’sknowledgeoftheforegoing.
(g) ICANNmay,uponthirty(30)calendardays’noticetoRegistryOperator,terminatethisAgreementasspecifiedinSection7.5.
4.4 TerminationbyRegistryOperator.
(a) RegistryOperatormayterminatethisAgreementuponnoticetoICANNif(i)ICANNfailstocureanyfundamentalandmaterialbreachofICANN’scovenantssetforthinArticle3,withinthirty(30)calendardaysafterRegistryOperatorgivesICANNnoticeofsuchbreach,whichnoticewillincludewithspecificitythedetailsoftheallegedbreach,(ii)anarbitratororcourtofcompetentjurisdictionhasfinallydeterminedthatICANNisinfundamentalandmaterialbreachofsuchcovenants,and(iii)ICANNfailstocomplywithsuchdeterminationandcuresuchbreachwithinten(10)calendardaysorsuchothertimeperiodasmaybedeterminedbythearbitratororcourtofcompetentjurisdiction.
(b) RegistryOperatormayterminatethisAgreementforanyreasonupononehundredeighty(180)calendardayadvancenoticetoICANN.
4.5 TransitionofRegistryuponTerminationofAgreement.UponexpirationoftheTermpursuanttoSection4.1orSection4.2oranyterminationofthisAgreementpursuanttoSection4.3orSection4.4,RegistryOperatorshallprovideICANNoranysuccessorregistryoperatorthatmaybedesignatedbyICANNfortheTLDinaccordance
13
withthisSection4.5withalldata(includingthedataescrowedinaccordancewithSection2.3)regardingoperationsoftheregistryfortheTLDnecessarytomaintainoperationsandregistryfunctionsthatmaybereasonablyrequestedbyICANNorsuchsuccessorregistryoperator.AfterconsultationwithRegistryOperator,ICANNshalldeterminewhetherornottotransitionoperationoftheTLDtoasuccessorregistryoperatorinitssolediscretionandinconformancewiththeRegistryTransitionProcess;provided,however,that(i)ICANNwilltakeintoconsiderationanyintellectualpropertyrightsofRegistryOperator(ascommunicatedtoICANNbyRegistryOperator)indeterminingwhethertotransitionoperationoftheTLDtoasuccessorregistryoperatorand(ii)ifRegistryOperatordemonstratestoICANN’sreasonablesatisfactionthat(A)alldomainnameregistrationsintheTLDareregisteredto,andmaintainedby,RegistryOperatororitsAffiliatesfortheirexclusiveuse,(B)RegistryOperatordoesnotsell,distributeortransfercontroloruseofanyregistrationsintheTLDtoanythirdpartythatisnotanAffiliateofRegistryOperator,and(C)transitioningoperationoftheTLDisnotnecessarytoprotectthepublicinterest,thenICANNmaynottransitionoperationoftheTLDtoasuccessorregistryoperatorupontheexpirationorterminationofthisAgreementwithouttheconsentofRegistryOperator(whichshallnotbeunreasonablywithheld,conditionedordelayed).Fortheavoidanceofdoubt,theforegoingsentenceshallnotprohibitICANNfromdelegatingtheTLDpursuanttoafutureapplicationprocessforthedelegationoftop-leveldomains,subjecttoanyprocessesandobjectionproceduresinstitutedbyICANNinconnectionwithsuchapplicationprocessintendedtoprotecttherightsofthirdparties.RegistryOperatoragreesthatICANNmaymakeanychangesitdeemsnecessarytotheIANAdatabaseforDNSandWHOISrecordswithrespecttotheTLDintheeventofatransitionoftheTLDpursuanttothisSection4.5.Inaddition,ICANNoritsdesigneeshallretainandmayenforceitsrightsundertheContinuedOperationsInstrumentforthemaintenanceandoperationoftheTLD,regardlessofthereasonforterminationorexpirationofthisAgreement.
4.6 EffectofTermination.UponanyexpirationoftheTermorterminationofthisAgreement,theobligationsandrightsofthepartiesheretoshallcease,providedthatsuchexpirationorterminationofthisAgreementshallnotrelievethepartiesofanyobligationorbreachofthisAgreementaccruingpriortosuchexpirationortermination,including,withoutlimitation,allaccruedpaymentobligationsarisingunderArticle6.Inaddition,Article5,Article7,Section2.12,Section4.5,andthisSection4.6shallsurvivetheexpirationorterminationofthisAgreement.Fortheavoidanceofdoubt,therightsofRegistryOperatortooperatetheregistryfortheTLDshallimmediatelyceaseuponanyexpirationoftheTermorterminationofthisAgreement.
ARTICLE 5.
DISPUTERESOLUTION
5.1 Mediation.IntheeventofanydisputearisingunderorinconnectionwiththisAgreement,beforeeitherpartymayinitiatearbitrationpursuanttoSection5.2below,ICANNandRegistryOperatormustattempttoresolvethedisputethroughmediationinaccordancewiththefollowingtermsandconditions:
14
(a) Apartyshallsubmitadisputetomediationbywrittennoticetotheotherparty.Themediationshallbeconductedbyasinglemediatorselectedbytheparties.Ifthepartiescannotagreeonamediatorwithinfifteen(15)calendardaysofdeliveryofwrittennoticepursuanttothisSection5.1,thepartieswillpromptlyselectamutuallyacceptablemediationproviderentity,whichentityshall,assoonaspracticablefollowingsuchentity’sselection,designateamediator,whoisalicensedattorneywithgeneralknowledgeofcontractlaw,hasnoongoingbusinessrelationshipwitheitherpartyand,totheextentnecessarytomediatetheparticulardispute,generalknowledgeofthedomainnamesystem.Anymediatormustconfirminwritingthatheorsheisnot,andwillnotbecomeduringthetermofthemediation,anemployee,partner,executiveofficer,director,orsecurityholderofICANNorRegistryOperator.Ifsuchconfirmationisnotprovidedbytheappointedmediator,thenareplacementmediatorshallbeappointedpursuanttothisSection5.1(a).
(b) Themediatorshallconductthemediationinaccordancewiththerulesandproceduresthatheorshedeterminesfollowingconsultationwiththeparties.Thepartiesshalldiscussthedisputeingoodfaithandattempt,withthemediator’sassistance,toreachanamicableresolutionofthedispute.Themediationshallbetreatedasasettlementdiscussionandshallthereforebeconfidentialandmaynotbeusedagainsteitherpartyinanylaterproceedingrelatingtothedispute,includinganyarbitrationpursuanttoSection5.2.Themediatormaynottestifyforeitherpartyinanylaterproceedingrelatingtothedispute.
(c) Eachpartyshallbearitsowncostsinthemediation.Thepartiesshallshareequallythefeesandexpensesofthemediator.Eachpartyshalltreatinformationreceivedfromtheotherpartypursuanttothemediationthatisappropriatelymarkedasconfidential(asrequiredbySection7.15)asConfidentialInformationofsuchotherpartyinaccordancewithSection7.15.
(d) Ifthepartieshaveengagedingoodfaithparticipationinthemediationbuthavenotresolvedthedisputeforanyreason,eitherpartyorthemediatormayterminatethemediationatanytimeandthedisputecanthenproceedtoarbitrationpursuanttoSection5.2below.Ifthepartieshavenotresolvedthedisputeforanyreasonbythedatethatisninety(90)calendardaysfollowingthedateofthenoticedeliveredpursuanttoSection5.1(a),themediationshallautomaticallyterminate(unlessextendedbyagreementoftheparties)andthedisputecanthenproceedtoarbitrationpursuanttoSection5.2below.
5.2 Arbitration.DisputesarisingunderorinconnectionwiththisAgreementthatarenotresolvedpursuanttoSection5.1,includingrequestsforspecificperformance,willberesolvedthroughbindingarbitrationconductedpursuanttotherulesoftheInternationalCourtofArbitrationoftheInternationalChamberofCommerce(the“ICC”).ThearbitrationwillbeconductedintheEnglishlanguageandwilloccurinLosAngelesCounty,California.Anyarbitrationwillbeinfrontofasinglearbitrator,unless(i)ICANNisseekingpunitiveorexemplarydamages,oroperationalsanctions,(ii)thepartiesagreeinwritingtoagreaternumberofarbitrators,or(iii)thedisputearisesunderSection7.6or
15
7.7.Inthecaseofclauses(i),(ii)or(iii)intheprecedingsentence,thearbitrationwillbeinfrontofthreearbitratorswitheachpartynominatingonearbitratorforconfirmationbytheICCandthetwoselectedarbitratorsnominatingthethirdarbitratorforconfirmationbytheICC.Foranarbitrationinfrontofasolearbitrator,RegistryOperatorandICANNmay,bymutualagreement,nominatethesolearbitratorforconfirmationbytheICC.Ifthepartiesfailtonominateasolearbitratoror,inthecaseofanarbitrationinfrontofthreearbitrators,eitherpartyfailstonominateanarbitrator,ineachcasewithinthirty(30)calendardaysfromthedatewhenaparty’srequestforarbitrationhasbeenreceivedbytheotherparty,orwithinsuchadditionaltimeasmaybeallowedbytheSecretariatoftheCourtoftheICC,thearbitrator(s)shallbeappointedbytheICC.IfanynominatedarbitratorisnotconfirmedbytheICC,thepartyorpersonsthatappointedsucharbitratorshallpromptlynominateareplacementarbitratorforconfirmationbytheICC.Inordertoexpeditethearbitrationandlimititscost,thearbitrator(s)shallestablishpagelimitsfortheparties’filingsinconjunctionwiththearbitration,andshouldthearbitrator(s)determinethatahearingisnecessary,thehearingshallbelimitedtoone(1)calendarday,providedthatinanyarbitrationinwhichICANNisseekingpunitiveorexemplarydamages,oroperationalsanctions,thehearingmaybeextendedforone(1)additionalcalendardayifagreeduponbythepartiesororderedbythearbitrator(s)basedonthearbitrator(s)independentdeterminationorthereasonablerequestofoneofthepartiesthereto.Theprevailingpartyinthearbitrationwillhavetherighttorecoveritscostsandreasonableattorneys’fees,whichthearbitrator(s)shallincludeintheawards.IntheeventthearbitratorsdeterminethatRegistryOperatorhasbeenrepeatedlyandwillfullyinfundamentalandmaterialbreachofitsobligationssetforthinArticle2,Article6orSection5.4ofthisAgreement,ICANNmayrequestthearbitratorsawardpunitiveorexemplarydamages,oroperationalsanctions(includingwithoutlimitationanordertemporarilyrestrictingRegistryOperator’srighttosellnewregistrations).Eachpartyshalltreatinformationreceivedfromtheotherpartypursuanttothearbitrationthatisappropriatelymarkedasconfidential(asrequiredbySection7.15)asConfidentialInformationofsuchotherpartyinaccordancewithSection7.15.InanylitigationinvolvingICANNconcerningthisAgreement,jurisdictionandexclusivevenueforsuchlitigationwillbeinacourtlocatedinLosAngelesCounty,California;however,thepartieswillalsohavetherighttoenforceajudgmentofsuchacourtinanycourtofcompetentjurisdiction.
5.3 LimitationofLiability.ICANN’saggregatemonetaryliabilityforviolationsofthisAgreementwillnotexceedanamountequaltotheRegistry-LevelFeespaidbyRegistryOperatortoICANNwithintheprecedingtwelve-monthperiodpursuanttothisAgreement(excludingtheVariableRegistry-LevelFeesetforthinSection6.3,ifany).RegistryOperator’saggregatemonetaryliabilitytoICANNforbreachesofthisAgreementwillbelimitedtoanamountequaltothefeespaidtoICANNduringtheprecedingtwelve-monthperiod(excludingtheVariableRegistry-LevelFeesetforthinSection6.3,ifany),andpunitiveandexemplarydamages,ifany,awardedinaccordancewithSection5.2,exceptwithrespecttoRegistryOperator’sindemnificationobligationspursuanttoSection7.1andSection7.2.Innoeventshalleitherpartybeliableforspecial,punitive,exemplaryorconsequentialdamagesarisingoutoforinconnectionwiththisAgreementortheperformanceornonperformanceofobligationsundertakeninthisAgreement,exceptasprovidedinSection5.2.ExceptasotherwiseprovidedinthisAgreement,neitherparty
16
makesanywarranty,expressorimplied,withrespecttotheservicesrenderedbyitself,itsservantsoragents,ortheresultsobtainedfromtheirwork,including,withoutlimitation,anyimpliedwarrantyofmerchantability,non-infringementorfitnessforaparticularpurpose.
5.4 SpecificPerformance.RegistryOperatorandICANNagreethatirreparabledamagecouldoccurifanyoftheprovisionsofthisAgreementwasnotperformedinaccordancewithitsspecificterms.Accordingly,thepartiesagreethattheyeachshallbeentitledtoseekfromthearbitratororcourtofcompetentjurisdictionspecificperformanceofthetermsofthisAgreement(inadditiontoanyotherremedytowhicheachpartyisentitled).
ARTICLE 6.
FEES
6.1 Registry-LevelFees.
(a) RegistryOperatorshallpayICANNaregistry-levelfeeequalto(i)theregistryfixedfeeofUS$6,250percalendarquarterand(ii)theregistry-leveltransactionfee(collectively,the“Registry-LevelFees”).Theregistry-leveltransactionfeewillbeequaltothenumberofannualincrementsofaninitialorrenewaldomainnameregistration(atoneormorelevels,andincludingrenewalsassociatedwithtransfersfromoneICANN-accreditedregistrartoanother,eacha“Transaction”),duringtheapplicablecalendarquartermultipliedbyUS$0.25;provided,howeverthattheregistry-leveltransactionfeeshallnotapplyuntilandunlessmorethan50,000TransactionshaveoccurredintheTLDduringanycalendarquarteroranyconsecutivefourcalendarquarterperiodintheaggregate(the“TransactionThreshold”)andshallapplytoeachTransactionthatoccurredduringeachquarterinwhichtheTransactionThresholdhasbeenmet,butshallnotapplytoeachquarterinwhichtheTransactionThresholdhasnotbeenmet.RegistryOperator’sobligationtopaythequarterlyregistry-levelfixedfeewillbeginonthedateonwhichtheTLDisdelegatedintheDNStoRegistryOperator.Thefirstquarterlypaymentoftheregistry-levelfixedfeewillbeproratedbasedonthenumberofcalendardaysbetweenthedelegationdateandtheendofthecalendarquarterinwhichthedelegationdatefalls.
(b) SubjecttoSection6.1(a),RegistryOperatorshallpaytheRegistry-LevelFeesonaquarterlybasistoanaccountdesignatedbyICANNwithinthirty(30)calendardaysfollowingthedateoftheinvoiceprovidedbyICANN.
6.2 CostRecoveryforRSTEP.RequestsbyRegistryOperatorfortheapprovalofAdditionalServicespursuanttoSection2.1maybereferredbyICANNtotheRegistryServicesTechnicalEvaluationPanel(“RSTEP”)pursuanttothatprocessathttp://www.icann.org/en/registries/rsep/.IntheeventthatsuchrequestsarereferredtoRSTEP,RegistryOperatorshallremittoICANNtheinvoicedcostoftheRSTEPreviewwithinfourteen(14)calendardaysofreceiptofacopyoftheRSTEPinvoicefromICANN,
17
unlessICANNdetermines,initssoleandabsolutediscretion,topayalloranyportionoftheinvoicedcostofsuchRSTEPreview.
6.3 VariableRegistry-LevelFee.
(a) IftheICANNaccreditedregistrars(accounting,intheaggregate,forpaymentoftwo-thirdsofallregistrar-levelfees(orsuchportionofICANNaccreditedregistrarsnecessarytoapprovevariableaccreditationfeesunderthethen-currentregistraraccreditationagreement),donotapprove,pursuanttothetermsoftheirregistraraccreditationagreementswithICANN,thevariableaccreditationfeesestablishedbytheICANNBoardofDirectorsforanyICANNfiscalyear,upondeliveryofnoticefromICANN,RegistryOperatorshallpaytoICANNavariableregistry-levelfee,whichshallbepaidonafiscalquarterbasis,andshallaccrueasofthebeginningofthefirstfiscalquarterofsuchICANNfiscalyear(the“VariableRegistry-LevelFee”).ThefeewillbecalculatedandinvoicedbyICANNonaquarterlybasis,andshallbepaidbyRegistryOperatorwithinsixty(60)calendardayswithrespecttothefirstquarterofsuchICANNfiscalyearandwithintwenty(20)calendardayswithrespecttoeachremainingquarterofsuchICANNfiscalyear,ofreceiptoftheinvoicedamountbyICANN.TheRegistryOperatormayinvoiceandcollecttheVariableRegistry-LevelFeesfromtheregistrarsthatarepartytoaRegistry-RegistrarAgreementwithRegistryOperator(whichagreementmayspecificallyprovideforthereimbursementofVariableRegistry-LevelFeespaidbyRegistryOperatorpursuanttothisSection6.3);provided,thatthefeesshallbeinvoicedtoallICANNaccreditedregistrarsifinvoicedtoany.TheVariableRegistry-LevelFee,ifcollectiblebyICANN,shallbeanobligationofRegistryOperatorandshallbedueandpayableasprovidedinthisSection6.3irrespectiveofRegistryOperator’sabilitytoseekandobtainreimbursementofsuchfeefromregistrars.IntheeventICANNlatercollectsvariableaccreditationfeesforwhichRegistryOperatorhaspaidICANNaVariableRegistry-LevelFee,ICANNshallreimbursetheRegistryOperatoranappropriateamountoftheVariableRegistry-LevelFee,asreasonablydeterminedbyICANN.IftheICANNaccreditedregistrars(asagroup)doapprove,pursuanttothetermsoftheirregistraraccreditationagreementswithICANN,thevariableaccreditationfeesestablishedbytheICANNBoardofDirectorsforafiscalyear,ICANNshallnotbeentitledtoaVariable-LevelFeehereunderforsuchfiscalyear,irrespectiveofwhethertheICANNaccreditedregistrarscomplywiththeirpaymentobligationstoICANNduringsuchfiscalyear.
(b) TheamountoftheVariableRegistry-LevelFeewillbespecifiedforeachregistrar,andmayincludebothaper-registrarcomponentandatransactionalcomponent.Theper-registrarcomponentoftheVariableRegistry-LevelFeeshallbespecifiedbyICANNinaccordancewiththebudgetadoptedbytheICANNBoardofDirectorsforeachICANNfiscalyear.ThetransactionalcomponentoftheVariableRegistry-LevelFeeshallbespecifiedbyICANNinaccordancewiththebudgetadoptedbytheICANNBoardofDirectorsforeachICANNfiscalyearbutshallnotexceedUS$0.25perdomainnameregistration(includingrenewalsassociatedwithtransfersfromoneICANNaccreditedregistrartoanother)peryear.
18
6.4 PassThroughFees.RegistryOperatorshallpaytoICANN(i)aone-timefeeequaltoUS$5,000foraccesstoanduseoftheTrademarkClearinghouseasdescribedinSpecification7(the“RPMAccessFee”)and(ii)US$0.25perSunriseRegistrationandClaimsRegistration(assuchtermsareusedinTrademarkClearinghouseRPMsincorporatedhereinpursuanttoSpecification7)(the“RPMRegistrationFee”).TheRPMAccessFeewillbeinvoicedasoftheEffectiveDateofthisAgreement,andRegistryOperatorshallpaysuchfeetoanaccountspecifiedbyICANNwithinthirty(30)calendardaysfollowingthedateoftheinvoice.ICANNwillinvoiceRegistryOperatorquarterlyfortheRPMRegistrationFee,whichshallbedueinaccordancewiththeinvoicingandpaymentprocedurespecifiedinSection6.1.
6.5 AdjustmentstoFees.NotwithstandinganyofthefeelimitationssetforthinthisArticle6,commencingupontheexpirationofthefirstyearofthisAgreement,andupontheexpirationofeachyearthereafterduringtheTerm,thethen-currentfeessetforthinSection6.1andSection6.3maybeadjusted,atICANN’sdiscretion,byapercentageequaltothepercentagechange,ifany,in(i)theConsumerPriceIndexforAllUrbanConsumers,U.S.CityAverage(1982-1984=100)publishedbytheUnitedStatesDepartmentofLabor,BureauofLaborStatistics,oranysuccessorindex(the“CPI”)forthemonthwhichisone(1)monthpriortothecommencementoftheapplicableyear,over(ii)theCPIpublishedforthemonthwhichisone(1)monthpriortothecommencementoftheimmediatelyprioryear.Intheeventofanysuchincrease,ICANNshallprovidenoticetoRegistryOperatorspecifyingtheamountofsuchadjustment.AnyfeeadjustmentunderthisSection6.5shallbeeffectiveasofthefirstdayofthefirstcalendarquarterfollowingatleastthirty(30)daysafterICANN’sdeliverytoRegistryOperatorofsuchfeeadjustmentnotice.
6.6 AdditionalFeeonLatePayments.Foranypaymentsthirty(30)calendardaysormoreoverdueunderthisAgreement,RegistryOperatorshallpayanadditionalfeeonlatepaymentsattherateof1.5%permonthor,ifless,themaximumratepermittedbyapplicablelaw.
6.7 FeeReductionWaiver.InICANN’ssolediscretion,ICANNmayreducetheamountofregistryfeespayablehereunderbyRegistryOperatorforanyperiodoftime(“FeeReductionWaiver”).AnysuchFeeReductionWaivermay,asdeterminedbyICANNinitssolediscretion,be(a)limitedindurationand(b)conditioneduponRegistryOperator’sacceptanceofthetermsandconditionssetforthinsuchwaiver.AFeeReductionWaivershallnotbeeffectiveunlessexecutedinwritingbyICANNascontemplatedbySection7.6(i).ICANNwillprovidenoticeofanyFeeReductionWaivertoRegistryOperatorinaccordancewithSection7.9.
ARTICLE 7.
MISCELLANEOUS
7.1 IndemnificationofICANN.
19
(a) RegistryOperatorshallindemnifyanddefendICANNanditsdirectors,officers,employees,andagents(collectively,“Indemnitees”)fromandagainstanyandallthird-partyclaims,damages,liabilities,costs,andexpenses,includingreasonablelegalfeesandexpenses,arisingoutoforrelatingtointellectualpropertyownershiprightswithrespecttotheTLD,thedelegationoftheTLDtoRegistryOperator,RegistryOperator’soperationoftheregistryfortheTLDorRegistryOperator’sprovisionofRegistryServices,providedthatRegistryOperatorshallnotbeobligatedtoindemnifyordefendanyIndemniteetotheextenttheclaim,damage,liability,costorexpensearose:(i)duetotheactionsoromissionsofICANN,itssubcontractors,panelistsorevaluatorsspecificallyrelatedtoandoccurringduringtheregistryTLDapplicationprocess(otherthanactionsoromissionsrequestedbyorforthebenefitofRegistryOperator),or(ii)duetoabreachbyICANNofanyobligationcontainedinthisAgreementoranywillfulmisconductbyICANN.ThisSectionshallnotbedeemedtorequireRegistryOperatortoreimburseorotherwiseindemnifyICANNforcostsassociatedwiththenegotiationorexecutionofthisAgreement,orwithmonitoringormanagementoftheparties’respectiveobligationshereunder.Further,thisSectionshallnotapplytoanyrequestforattorney’sfeesinconnectionwithanylitigationorarbitrationbetweenoramongtheparties,whichshallbegovernedbyArticle5orotherwiseawardedbyacourtofcompetentjurisdictionorarbitrator.
(b) ForanyclaimsbyICANNforindemnificationwherebymultipleregistryoperators(includingRegistryOperator)haveengagedinthesameactionsoromissionsthatgaverisetotheclaim,RegistryOperator’saggregateliabilitytoindemnifyICANNwithrespecttosuchclaimshallbelimitedtoapercentageofICANN’stotalclaim,calculatedbydividingthenumberoftotaldomainnamesunderregistrationwithRegistryOperatorwithintheTLD(whichnamesunderregistrationshallbecalculatedconsistentlywithArticle6hereofforanyapplicablequarter)bythetotalnumberofdomainnamesunderregistrationwithinalltopleveldomainsforwhichtheregistryoperatorsthereofareengaginginthesameactsoromissionsgivingrisetosuchclaim.ForthepurposesofreducingRegistryOperator’sliabilityunderSection7.1(a)pursuanttothisSection7.1(b),RegistryOperatorshallhavetheburdenofidentifyingtheotherregistryoperatorsthatareengagedinthesameactionsoromissionsthatgaverisetotheclaim,anddemonstrating,toICANN’sreasonablesatisfaction,suchotherregistryoperators’culpabilityforsuchactionsoromissions.Fortheavoidanceofdoubt,intheeventthataregistryoperatorisengagedinthesameactsoromissionsgivingrisetotheclaims,butsuchregistryoperator(s)donothavethesameorsimilarindemnificationobligationstoICANNassetforthinSection7.1(a)above,thenumberofdomainsundermanagementbysuchregistryoperator(s)shallnonethelessbeincludedinthecalculationintheprecedingsentence.
7.2 IndemnificationProcedures.Ifanythird-partyclaimiscommencedthatisindemnifiedunderSection7.1above,ICANNshallprovidenoticethereoftoRegistryOperatoraspromptlyaspracticable.RegistryOperatorshallbeentitled,ifitsoelects,inanoticepromptlydeliveredtoICANN,toimmediatelytakecontrolofthedefenseandinvestigationofsuchclaimandtoemployandengageattorneysreasonablyacceptabletoICANNtohandleanddefendthesame,atRegistryOperator’ssolecostandexpense,providedthatinalleventsICANNwillbeentitledtocontrolatitssolecostandexpensethelitigationofissuesconcerningthevalidityorinterpretationofICANN’spolicies,Bylawsor
20
conduct.ICANNshallcooperate,atRegistryOperator’scostandexpense,inallreasonablerespectswithRegistryOperatoranditsattorneysintheinvestigation,trial,anddefenseofsuchclaimandanyappealarisingtherefrom,andmay,atitsowncostandexpense,participate,throughitsattorneysorotherwise,insuchinvestigation,trialanddefenseofsuchclaimandanyappealarisingtherefrom.NosettlementofaclaimthatinvolvesaremedyaffectingICANNotherthanthepaymentofmoneyinanamountthatisfullyindemnifiedbyRegistryOperatorwillbeenteredintowithouttheconsentofICANN.IfRegistryOperatordoesnotassumefullcontroloverthedefenseofaclaimsubjecttosuchdefenseinaccordancewiththisSection7.2,ICANNwillhavetherighttodefendtheclaiminsuchmannerasitmaydeemappropriate,atthecostandexpenseofRegistryOperatorandRegistryOperatorshallcooperateinsuchdefense.
7.3 DefinedTerms.ForpurposesofthisAgreement,unlesssuchdefinitionsareamendedpursuanttoaConsensusPolicyatafuturedate,inwhichcasethefollowingdefinitionsshallbedeemedamendedandrestatedintheirentiretyassetforthinsuchConsensusPolicy,SecurityandStabilityshallbedefinedasfollows:
(a) ForthepurposesofthisAgreement,aneffecton“Security”shallmean(1)theunauthorizeddisclosure,alteration,insertionordestructionofregistrydata,or(2)theunauthorizedaccesstoordisclosureofinformationorresourcesontheInternetbysystemsoperatinginaccordancewithallapplicablestandards.
(b) ForpurposesofthisAgreement,aneffecton“Stability”shallreferto(1)lackofcompliancewithapplicablerelevantstandardsthatareauthoritativeandpublishedbyawell-establishedandrecognizedInternetstandardsbody,suchastherelevantStandards-TrackorBestCurrentPracticeRequestsforComments(“RFCs”)sponsoredbytheInternetEngineeringTaskForce;or(2)thecreationofaconditionthatadverselyaffectsthethroughput,responsetime,consistencyorcoherenceofresponsestoInternetserversorendsystemsoperatinginaccordancewithapplicablerelevantstandardsthatareauthoritativeandpublishedbyawell-establishedandrecognizedInternetstandardsbody,suchastherelevantStandards-TrackorBestCurrentPracticeRFCs,andrelyingonRegistryOperator’sdelegatedinformationorprovisioningofservices.
7.4 NoOffset.AllpaymentsdueunderthisAgreementwillbemadeinatimelymannerthroughouttheTermandnotwithstandingthependencyofanydispute(monetaryorotherwise)betweenRegistryOperatorandICANN.
7.5 ChangeofControl;AssignmentandSubcontracting.ExceptassetforthinthisSection7.5,neitherpartymayassignanyofitsrightsandobligationsunderthisAgreementwithoutthepriorwrittenapprovaloftheotherparty,whichapprovalwillnotbeunreasonablywithheld.ForpurposesofthisSection7.5,adirectorindirectchangeofcontrolofRegistryOperatororanysubcontractingarrangementthatrelatestoanyCriticalFunction(asidentifiedinSection6ofSpecification10)fortheTLD(a“MaterialSubcontractingArrangement”)shallbedeemedanassignment.
21
(a) RegistryOperatormustprovidenolessthanthirty(30)calendardaysadvancenoticetoICANNofanyassignmentorMaterialSubcontractingArrangement,andanyagreementtoassignorsubcontractanyportionoftheoperationsoftheTLD(whetherornotaMaterialSubcontractingArrangement)mustmandatecompliancewithallcovenants,obligationsandagreementsbyRegistryOperatorhereunder,andRegistryOperatorshallcontinuetobeboundbysuchcovenants,obligationsandagreements.RegistryOperatormustalsoprovidenolessthanthirty(30)calendardaysadvancenoticetoICANNpriortotheconsummationofanytransactionanticipatedtoresultinadirectorindirectchangeofcontrolofRegistryOperator.
(b) Withinthirty(30)calendardaysofeithersuchnotificationpursuanttoSection7.5(a),ICANNmayrequestadditionalinformationfromRegistryOperatorestablishing(i)compliancewiththisAgreementand(ii)thatthepartyacquiringsuchcontrolorenteringintosuchassignmentorMaterialSubcontractingArrangement(inanycase,the“ContractingParty”)andtheultimateparententityoftheContractingPartymeetstheICANN-adoptedspecificationorpolicyonregistryoperatorcriteriathenineffect(includingwithrespecttofinancialresourcesandoperationalandtechnicalcapabilities),inwhichcaseRegistryOperatormustsupplytherequestedinformationwithinfifteen(15)calendardays.
(c) RegistryOperatoragreesthatICANN’sconsenttoanyassignment,changeofcontrolorMaterialSubcontractingArrangementwillalsobesubjecttobackgroundchecksonanyproposedContractingParty(andsuchContractingParty’sAffiliates).
(d) IfICANNfailstoexpresslyprovideorwithholditsconsenttoanyassignment,directorindirectchangeofcontrolofRegistryOperatororanyMaterialSubcontractingArrangementwithinthirty(30)calendardaysofICANN’sreceiptofnoticeofsuchtransaction(or,ifICANNhasrequestedadditionalinformationfromRegistryOperatorassetforthabove,thirty(30)calendardaysofthereceiptofallrequestedwritteninformationregardingsuchtransaction)fromRegistryOperator,ICANNshallbedeemedtohaveconsentedtosuchtransaction.
(e) Inconnectionwithanysuchassignment,changeofcontrolorMaterialSubcontractingArrangement,RegistryOperatorshallcomplywiththeRegistryTransitionProcess.
(f) Notwithstandingtheforegoing,(i)anyconsummatedchangeofcontrolshallnotbevoidablebyICANN;provided,however,that,ifICANNreasonablydeterminestowithholditsconsenttosuchtransaction,ICANNmayterminatethisAgreementpursuanttoSection4.3(g),(ii)ICANNmayassignthisAgreementwithouttheconsentofRegistryOperatoruponapprovaloftheICANNBoardofDirectorsinconjunctionwithareorganization,reconstitutionorre-incorporationofICANNuponsuchassignee’sexpressassumptionofthetermsandconditionsofthisAgreement,(iii)RegistryOperatormayassignthisAgreementwithouttheconsentofICANNdirectlytoanAffiliatedAssignee,asthattermisdefinedhereinbelow,uponsuchAffiliatedAssignee’sexpresswritten
22
assumptionofthetermsandconditionsofthisAgreement,and(iv)ICANNshallbedeemedtohaveconsentedtoanyassignment,MaterialSubcontractingArrangementorchangeofcontroltransactioninwhichtheContractingPartyisanexistingoperatorofagenerictop-leveldomainpursuanttoaregistryagreementbetweensuchContractingPartyandICANN(providedthatsuchContractingPartyisthenincompliancewiththetermsandconditionsofsuchregistryagreementinallmaterialrespects),unlessICANNprovidestoRegistryOperatorawrittenobjectiontosuchtransactionwithinten(10)calendardaysofICANN’sreceiptofnoticeofsuchtransactionpursuanttothisSection7.5.NotwithstandingSection7.5(a),intheeventanassignmentismadepursuanttoclauses(ii)or(iii)ofthisSection7.5(f),theassigningpartywillprovidetheotherpartywithpromptnoticefollowinganysuchassignment.ForthepurposesofthisSection7.5(f),(A)“AffiliatedAssignee”meansapersonorentitythat,directlyorindirectly,throughoneormoreintermediaries,controls,iscontrolledby,orisundercommoncontrolwith,thepersonorentityspecified,and(B)“control”(includingtheterms“controlledby”and“undercommoncontrolwith”)shallhavethesamemeaningspecifiedinSection2.9(c)ofthisAgreement.
7.6 AmendmentsandWaivers.
(a) IftheICANNBoardofDirectorsdeterminesthatanamendmenttothisAgreement(includingtotheSpecificationsreferredtoherein)andallotherregistryagreementsbetweenICANNandtheApplicableRegistryOperators(the“ApplicableRegistryAgreements”)isdesirable(each,a“SpecialAmendment”),ICANNmayadoptaSpecialAmendmentpursuanttotherequirementsofandprocesssetforthinthisSection7.6;providedthataSpecialAmendmentmaynotbeaRestrictedAmendment.
(b) PriortosubmittingaSpecialAmendmentforRegistryOperatorApproval,ICANNshallfirstconsultingoodfaithwiththeWorkingGroupregardingtheformandsubstanceofsuchSpecialAmendment.ThedurationofsuchconsultationshallbereasonablydeterminedbyICANNbasedonthesubstanceoftheSpecialAmendment.Followingsuchconsultation,ICANNmayproposetheadoptionofaSpecialAmendmentbypubliclypostingsuchamendmentonitswebsitefornolessthanthirty(30)calendardays(the“PostingPeriod”)andprovidingnoticeofsuchproposedamendmenttotheApplicableRegistryOperatorsinaccordancewithSection7.9.ICANNwillconsiderthepubliccommentssubmittedonaSpecialAmendmentduringthePostingPeriod(includingcommentssubmittedbytheApplicableRegistryOperators).
(c) If,withinonehundredeighty(180)calendardaysfollowingtheexpirationofthePostingPeriod(the“ApprovalPeriod”),theICANNBoardofDirectorsapprovesaSpecialAmendment(whichmaybeinaformdifferentthansubmittedforpubliccomment,butmustaddressthesubjectmatteroftheSpecialAmendmentpostedforpubliccomment,asmodifiedtoreflectand/oraddressinputfromtheWorkingGroupandpubliccomments),ICANNshallprovidenoticeof,andsubmit,suchSpecialAmendmentforapprovalordisapprovalbytheApplicableRegistryOperators.If,duringthesixty(60)calendardayperiodfollowingthedateICANNprovidessuchnoticetotheApplicableRegistryOperators,suchSpecialAmendmentreceivesRegistryOperatorApproval,suchSpecialAmendmentshallbedeemedapproved(an“ApprovedAmendment”)bythe
23
ApplicableRegistryOperators,andshallbeeffectiveanddeemedanamendmenttothisAgreementonthedatethatissixty(60)calendardaysfollowingthedateICANNprovidednoticeoftheapprovalofsuchApprovedAmendmenttoRegistryOperator(the“AmendmentEffectiveDate”).IntheeventthataSpecialAmendmentdoesnotreceiveRegistryOperatorApproval,theSpecialAmendmentshallbedeemednotapprovedbytheApplicableRegistryOperators(a“RejectedAmendment”).ARejectedAmendmentwillhavenoeffectonthetermsandconditionsofthisAgreement,exceptassetforthbelow.
(d) IftheICANNBoardofDirectorsreasonablydeterminesthataRejectedAmendmentfallswithinthesubjectmattercategoriessetforthinSection1.2ofSpecification1,theICANNBoardofDirectorsmayadoptaresolution(thedatesuchresolutionisadoptedisreferredtohereinasthe“ResolutionAdoptionDate”)requestinganIssueReport(assuchtermisdefinedinICANN’sBylaws)bytheGenericNamesSupportingOrganization(the“GNSO”)regardingthesubstanceofsuchRejectedAmendment.ThepolicydevelopmentprocessundertakenbytheGNSOpursuanttosuchrequestedIssueReportisreferredtohereinasa“PDP.”IfsuchPDPresultsinaFinalReportsupportedbyaGNSOSupermajority(asdefinedinICANN’sBylaws)thateither(i)recommendsadoptionoftheRejectedAmendmentasConsensusPolicyor(ii)recommendsagainstadoptionoftheRejectedAmendmentasConsensusPolicy,and,inthecaseof(i)above,theBoardadoptssuchConsensusPolicy,RegistryOperatorshallcomplywithitsobligationspursuanttoSection2.2ofthisAgreement.Ineithercase,ICANNwillabandontheRejectedAmendmentanditwillhavenoeffectonthetermsandconditionsofthisAgreement.NotwithstandingtheforegoingprovisionsofthisSection7.6(d),theICANNBoardofDirectorsshallnotberequiredtoinitiateaPDPwithrespecttoaRejectedAmendmentif,atanytimeinthetwelve(12)monthperiodprecedingthesubmissionofsuchRejectedAmendmentforRegistryOperatorApprovalpursuanttoSection7.6(c),thesubjectmatterofsuchRejectedAmendmentwasthesubjectofaconcludedorotherwiseabandonedorterminatedPDPthatdidnotresultinaGNSOSupermajorityrecommendation.
(e) If(a)aRejectedAmendmentdoesnotfallwithinthesubjectmattercategoriessetforthinSection1.2ofSpecification1,(b)thesubjectmatterofaRejectedAmendmentwas,atanytimeinthetwelve(12)monthperiodprecedingthesubmissionofsuchRejectedAmendmentforRegistryOperatorApprovalpursuanttoSection7.6(c),thesubjectofaconcludedorotherwiseabandonedorterminatedPDPthatdidnotresultinaGNSOSupermajorityrecommendation,or(c)aPDPdoesnotresultinaFinalReportsupportedbyaGNSOSupermajoritythateither(A)recommendsadoptionoftheRejectedAmendmentasConsensusPolicyor(B)recommendsagainstadoptionoftheRejectedAmendmentasConsensusPolicy(orsuchPDPhasotherwisebeenabandonedorterminatedforanyreason),then,inanysuchcase,suchRejectedAmendmentmaystillbeadoptedandbecomeeffectiveinthemannerdescribedbelow.InorderfortheRejectedAmendmenttobeadopted,thefollowingrequirementsmustbesatisfied:
(i) thesubjectmatteroftheRejectedAmendmentmustbewithinthescopeofICANN’smissionandconsistentwithabalancedapplicationofitscorevalues(asdescribedinICANN’sBylaws);
24
(ii) theRejectedAmendmentmustbejustifiedbyaSubstantialandCompellingReasoninthePublicInterest,mustbelikelytopromotesuchinterest,takingintoaccountcompetingpublicandprivateintereststhatarelikelytobeaffectedbytheRejectedAmendment,andmustbenarrowlytailoredandnobroaderthanreasonablynecessarytoaddresssuchSubstantialandCompellingReasoninthePublicInterest;
(iii) totheextenttheRejectedAmendmentprohibitsorrequiresconductoractivities,imposesmaterialcostsontheApplicableRegistryOperators,and/ormateriallyreducespublicaccesstodomainnameservices,theRejectedAmendmentmustbetheleastrestrictivemeansreasonablyavailabletoaddresstheSubstantialandCompellingReasoninthePublicInterest;
(iv) theICANNBoardofDirectorsmustsubmittheRejectedAmendment,alongwithawrittenexplanationofthereasoningrelatedtoitsdeterminationthattheRejectedAmendmentmeetstherequirementssetoutinsubclauses(i)through(iii)above,forpubliccommentforaperiodofnolessthanthirty(30)calendardays;and
(v) followingsuchpubliccommentperiod,theICANNBoardofDirectorsmust(a)engageinconsultation(ordirectICANNmanagementtoengageinconsultation)withtheWorkingGroup,subjectmatterexperts,membersoftheGNSO,relevantadvisorycommitteesandotherinterestedstakeholderswithrespecttosuchRejectedAmendmentforaperiodofnolessthansixty(60)calendardays;and(b)followingsuchconsultation,reapprovetheRejectedAmendment(whichmaybeinaformdifferentthansubmittedforRegistryOperatorApproval,butmustaddressthesubjectmatteroftheRejectedAmendment,asmodifiedtoreflectand/oraddressinputfromtheWorkingGroupandpubliccomments)bytheaffirmativevoteofatleasttwo-thirdsofthemembersoftheICANNBoardofDirectorseligibletovoteonsuchmatter,takingintoaccountanyICANNpolicyaffectingsucheligibility,includingICANN’sConflictofInterestPolicy(a“BoardAmendment”).
SuchBoardAmendmentshall,subjecttoSection7.6(f),bedeemedanApprovedAmendment,andshallbeeffectiveanddeemedanamendmenttothisAgreementonthedatethatissixty(60)calendardaysfollowingthedateICANNprovidednoticeoftheapprovalofsuchBoardAmendmenttoRegistryOperator(whicheffectivedateshallbedeemedtheAmendmentEffectiveDatehereunder).Notwithstandingtheforegoing,aBoardAmendmentmaynotamendtheregistryfeeschargedbyICANNhereunder,oramendthisSection7.6.
(f) NotwithstandingtheprovisionsofSection7.6(e),aBoardAmendmentshallnotbedeemedanApprovedAmendmentif,duringthethirty(30)calendardayperiodfollowingtheapprovalbytheICANNBoardofDirectorsoftheBoardAmendment,the
25
WorkingGroup,onthebehalfoftheApplicableRegistryOperators,submitstotheICANNBoardofDirectorsanalternativetotheBoardAmendment(an“AlternativeAmendment”)thatmeetsthefollowingrequirements:
(i) setsforththeprecisetextproposedbytheWorkingGrouptoamendthisAgreementinlieuoftheBoardAmendment;
(ii) addressestheSubstantialandCompellingReasoninthePublicInterestidentifiedbytheICANNBoardofDirectorsasthejustificationfortheBoardAmendment;and
(iii) comparedtotheBoardAmendmentis:(a)morenarrowlytailoredtoaddresssuchSubstantialandCompellingReasoninthePublicInterest,and(b)totheextenttheAlternativeAmendmentprohibitsorrequiresconductoractivities,imposesmaterialcostsonAffectedRegistryOperators,ormateriallyreducesaccesstodomainnameservices,isalessrestrictivemeanstoaddresstheSubstantialandCompellingReasoninthePublicInterest.
Anyproposedamendmentthatdoesnotmeettherequirementsofsubclauses(i)through(iii)intheimmediatelyprecedingsentenceshallnotbeconsideredanAlternativeAmendmenthereunderandthereforeshallnotsupersedeordelaytheeffectivenessoftheBoardAmendment.If,followingthesubmissionoftheAlternativeAmendmenttotheICANNBoardofDirectors,theAlternativeAmendmentreceivesRegistryOperatorApproval,theAlternativeAmendmentshallsupersedetheBoardAmendmentandshallbedeemedanApprovedAmendmenthereunder(andshallbeeffectiveanddeemedanamendmenttothisAgreementonthedatethatissixty(60)calendardaysfollowingthedateICANNprovidednoticeoftheapprovalofsuchAlternativeAmendmenttoRegistryOperator,whicheffectivedateshalldeemedtheAmendmentEffectiveDatehereunder),unless,withinaperiodofsixty(60)calendardaysfollowingthedatethattheWorkingGroupnotifiestheICANNBoardofDirectorsofRegistryOperatorApprovalofsuchAlternativeAmendment(duringwhichtimeICANNshallengagewiththeWorkingGroupwithrespecttotheAlternativeAmendment),theICANNBoardofDirectorsbytheaffirmativevoteofatleasttwo-thirdsofthemembersoftheICANNBoardofDirectorseligibletovoteonsuchmatter,takingintoaccountanyICANNpolicyaffectingsucheligibility,includingICANN’sConflictofInterestPolicy,rejectstheAlternativeAmendment.If(A)theAlternativeAmendmentdoesnotreceiveRegistryOperatorApprovalwithinthirty(30)calendardaysofsubmissionofsuchAlternativeAmendmenttotheApplicableRegistryOperators(andtheWorkingGroupshallnotifyICANNofthedateofsuchsubmission),or(B)theICANNBoardofDirectorsrejectstheAlternativeAmendmentbysuchtwo-thirdsvote,theBoardAmendment(andnottheAlternativeAmendment)shallbeeffectiveanddeemedanamendmenttothisAgreementonthedatethatissixty(60)calendardaysfollowingthedateICANNprovidednoticetoRegistryOperator(whicheffectivedateshalldeemedtheAmendmentEffectiveDatehereunder).IftheICANNBoardofDirectorsrejectsanAlternativeAmendment,theboardshallpublishawrittenrationalesettingforthitsanalysisofthecriteriasetforthinSections7.6(f)(i)through7.6(f)(iii).The
26
abilityoftheICANNBoardofDirectorstorejectanAlternativeAmendmenthereunderdoesnotrelievetheBoardoftheobligationtoensurethatanyBoardAmendmentmeetsthecriteriasetforthinSection7.6(e)(i)through7.6(e)(v).
(g) IntheeventthatRegistryOperatorbelievesanApprovedAmendmentdoesnotmeetthesubstantiverequirementssetoutinthisSection7.6orhasbeenadoptedincontraventionofanyoftheproceduralprovisionsofthisSection7.6,RegistryOperatormaychallengetheadoptionofsuchSpecialAmendmentpursuanttothedisputeresolutionprovisionssetforthinArticle5,exceptthatsucharbitrationshallbeconductedbyathree-personarbitrationpanel.Anysuchchallengemustbebroughtwithinsixty(60)calendardaysfollowingthedateICANNprovidednoticetoRegistryOperatoroftheApprovedAmendment,andICANNmayconsolidateallchallengesbroughtbyregistryoperators(includingRegistryOperator)intoasingleproceeding.TheApprovedAmendmentwillbedeemednottohaveamendedthisAgreementduringthependencyofthedisputeresolutionprocess.
(h) RegistryOperatormayapplyinwritingtoICANNforanexemptionfromtheApprovedAmendment(eachsuchrequestsubmittedbyRegistryOperatorhereunder,an“ExemptionRequest”)duringthethirty(30)calendardayperiodfollowingthedateICANNprovidednoticetoRegistryOperatorofsuchApprovedAmendment.EachExemptionRequestwillsetforththebasisforsuchrequestandprovidedetailedsupportforanexemptionfromtheApprovedAmendment.AnExemptionRequestmayalsoincludeadetaileddescriptionandsupportforanyalternativesto,oravariationof,theApprovedAmendmentproposedbysuchRegistryOperator.AnExemptionRequestmayonlybegranteduponaclearandconvincingshowingbyRegistryOperatorthatcompliancewiththeApprovedAmendmentconflictswithapplicablelawsorwouldhaveamaterialadverseeffectonthelong-termfinancialconditionorresultsofoperationsofRegistryOperator.NoExemptionRequestwillbegrantedifICANNdetermines,initsreasonablediscretion,thatgrantingsuchExemptionRequestwouldbemateriallyharmfultoregistrantsorresultinthedenialofadirectbenefittoregistrants.Withinninety(90)calendardaysofICANN’sreceiptofanExemptionRequest,ICANNshalleitherapprove(whichapprovalmaybeconditionedorconsistofalternativestooravariationoftheApprovedAmendment)ordenytheExemptionRequestinwriting,duringwhichtimetheApprovedAmendmentwillnotamendthisAgreement.IftheExemptionRequestisapprovedbyICANN,theApprovedAmendmentwillnotamendthisAgreement;provided,thatanyconditions,alternativesorvariationsoftheApprovedAmendmentrequiredbyICANNshallbeeffectiveand,totheextentapplicable,willamendthisAgreementasoftheAmendmentEffectiveDate.IfsuchExemptionRequestisdeniedbyICANN,theApprovedAmendmentwillamendthisAgreementasoftheAmendmentEffectiveDate(or,ifsuchdatehaspassed,suchApprovedAmendmentshallbedeemedeffectiveimmediatelyonthedateofsuchdenial),providedthatRegistryOperatormay,withinthirty(30)calendardaysfollowingreceiptofICANN’sdetermination,appealICANN’sdecisiontodenytheExemptionRequestpursuanttothedisputeresolutionproceduressetforthinArticle5.TheApprovedAmendmentwillbedeemednottohaveamendedthisAgreementduringthependencyofthedisputeresolutionprocess.Foravoidanceofdoubt,onlyExemptionRequestssubmittedbyRegistryOperatorthatareapprovedbyICANNpursuanttothisSection7.6(j),agreedtoby
27
ICANNfollowingmediationpursuanttoSection5.1orthroughanarbitrationdecisionpursuanttoSection5.2shallexemptRegistryOperatorfromanyApprovedAmendment,andnoExemptionRequestgrantedtoanyotherApplicableRegistryOperator(whetherbyICANNorthrougharbitration)shallhaveanyeffectunderthisAgreementorexemptRegistryOperatorfromanyApprovedAmendment.
(i) ExceptassetforthinthisSection7.6,Section7.7andasotherwisesetforthinthisAgreementandtheSpecificationshereto,noamendment,supplementormodificationofthisAgreementoranyprovisionhereofshallbebindingunlessexecutedinwritingbybothparties,andnothinginthisSection7.6orSection7.7shallrestrictICANNandRegistryOperatorfromenteringintobilateralamendmentsandmodificationstothisAgreementnegotiatedsolelybetweenthetwoparties.NowaiverofanyprovisionofthisAgreementshallbebindingunlessevidencedbyawritingsignedbythepartywaivingcompliancewithsuchprovision.NowaiverofanyoftheprovisionsofthisAgreementorfailuretoenforceanyoftheprovisionshereofshallbedeemedorshallconstituteawaiverofanyotherprovisionhereof,norshallanysuchwaiverconstituteacontinuingwaiverunlessotherwiseexpresslyprovided.Fortheavoidanceofdoubt,nothinginthisSections7.6or7.7shallbedeemedtolimitRegistryOperator’sobligationtocomplywithSection2.2.
(j) ForpurposesofthisSection7.6,thefollowingtermsshallhavethefollowingmeanings:
(i) “ApplicableRegistryOperators”means,collectively,theregistryoperatorsoftop-leveldomainspartytoaregistryagreementthatcontainsaprovisionsimilartothisSection7.6,includingRegistryOperator.
(ii) “RegistryOperatorApproval”meansthereceiptofeachofthefollowing:(A)theaffirmativeapprovaloftheApplicableRegistryOperatorswhosepaymentstoICANNaccountedfortwo-thirdsofthetotalamountoffees(convertedtoU.S.dollars,ifapplicable,attheprevailingexchangeratepublishedthepriordayintheU.S.EditionoftheWallStreetJournalforthedatesuchcalculationismadebyICANN)paidtoICANNbyalltheApplicableRegistryOperatorsduringtheimmediatelypreviouscalendaryearpursuanttotheApplicableRegistryAgreements,and(B)theaffirmativeapprovalofamajorityoftheApplicableRegistryOperatorsatthetimesuchapprovalisobtained.Fortheavoidanceofdoubt,withrespecttoclause(B),eachApplicableRegistryOperatorshallhaveonevoteforeachtop-leveldomainoperatedbysuchRegistryOperatorpursuanttoanApplicableRegistryAgreement.
(iii) “RestrictedAmendment”meansthefollowing:(A)anamendmentofSpecification1,(B)excepttotheextentaddressedinSection2.10hereof,anamendmentthatspecifiesthepricechargedbyRegistryOperatortoregistrarsfordomainnameregistrations,(C)anamendmentto
28
thedefinitionofRegistryServicesassetforthinthefirstparagraphofSection2.1ofSpecification6,or(D)anamendmenttothelengthoftheTerm.
(iv) “SubstantialandCompellingReasoninthePublicInterest”meansareasonthatisjustifiedbyanimportant,specific,andarticulatedpublicinterestgoalthatiswithinICANN'smissionandconsistentwithabalancedapplicationofICANN'scorevaluesasdefinedinICANN'sBylaws.
(v) “WorkingGroup”meansrepresentativesoftheApplicableRegistryOperatorsandothermembersofthecommunitythattheRegistryStakeholdersGroupappoints,fromtimetotime,toserveasaworkinggrouptoconsultonamendmentstotheApplicableRegistryAgreements(excludingbilateralamendmentspursuanttoSection7.6(i)).
(k) NotwithstandinganythinginthisSection7.6tothecontrary,(i)ifRegistryOperatorprovidesevidencetoICANN'sreasonablesatisfactionthattheApprovedAmendmentwouldmateriallyincreasethecostofprovidingRegistryServices,thenICANNwillallowuptoone-hundredeighty(180)calendardaysforApprovedAmendmenttobecomeeffectivewithrespecttoRegistryOperator,and(ii)noApprovedAmendmentadoptedpursuanttoSection7.6shallbecomeeffectivewithrespecttoRegistryOperatorifRegistryOperatorprovidesICANNwithanirrevocablenoticeofterminationpursuanttoSection4.4(b).
7.7 NegotiationProcess.
(a) IfeithertheChiefExecutiveOfficerofICANN(“CEO”)ortheChairpersonoftheRegistryStakeholderGroup(“Chair”)desirestodiscussanyrevision(s)tothisAgreement,theCEOorChair,asapplicable,shallprovidewrittennoticetotheotherperson,whichshallsetforthinreasonabledetailtheproposedrevisionstothisAgreement(a“NegotiationNotice”).Notwithstandingtheforegoing,neithertheCEOnortheChairmay(i)proposerevisionstothisAgreementthatmodifyanyConsensusPolicythenexisting,(ii)proposerevisionstothisAgreementpursuanttothisSection7.7onorbeforeJune30,2014,or(iii)proposerevisionsorsubmitaNegotiationNoticemorethanonceduringanytwelve(12)monthperiodbeginningonJuly1,2014.
(b) FollowingreceiptoftheNegotiationNoticebyeithertheCEOortheChair,ICANNandtheWorkingGroup(asdefinedinSection7.6)shallconsultingoodfaithnegotiationsregardingtheformandsubstanceoftheproposedrevisionstothisAgreement,whichshallbeintheformofaproposedamendmenttothisAgreement(the“ProposedRevisions”),foraperiodofatleastninety(90)calendardays(unlessaresolutionisearlierreached)andattempttoreachamutuallyacceptableagreementrelatingtotheProposedRevisions(the“DiscussionPeriod”).
(c) If,followingtheconclusionoftheDiscussionPeriod,anagreementisreachedontheProposedRevisions,ICANNshallpostthemutuallyagreedProposedRevisionsonitswebsiteforpubliccommentfornolessthanthirty(30)calendardays(the“PostingPeriod”)andprovidenoticeofsuchrevisionstoallApplicableRegistryOperators
29
inaccordancewithSection7.9.ICANNandtheWorkingGroupwillconsiderthepubliccommentssubmittedontheProposedRevisionsduringthePostingPeriod(includingcommentssubmittedbytheApplicableRegistryOperators).FollowingtheconclusionofthePostingPeriod,theProposedRevisionsshallbesubmittedforRegistryOperatorApproval(asdefinedinSection7.6)andapprovalbytheICANNBoardofDirectors.Ifsuchapprovalsareobtained,theProposedRevisionsshallbedeemedanApprovedAmendment(asdefinedinSection7.6)bytheApplicableRegistryOperatorsandICANN,andshallbeeffectiveanddeemedanamendmenttothisAgreementuponsixty(60)calendardaysnoticefromICANNtoRegistryOperator.
(d) If,followingtheconclusionoftheDiscussionPeriod,anagreementisnotreachedbetweenICANNandtheWorkingGroupontheProposedRevisions,eithertheCEOortheChairmayprovidetheotherpersonwrittennotice(the“MediationNotice”)requiringeachpartytoattempttoresolvethedisagreementsrelatedtotheProposedRevisionsthroughimpartial,facilitative(non-evaluative)mediationinaccordancewiththetermsandconditionssetforthbelow.IntheeventthataMediationNoticeisprovided,ICANNandtheWorkingGroupshall,withinfifteen(15)calendardaysthereof,simultaneouslypostthetextoftheirdesiredversionoftheProposedRevisionsandapositionpaperwithrespecttheretoonICANN’swebsite.
(i) Themediationshallbeconductedbyasinglemediatorselectedbytheparties.Ifthepartiescannotagreeonamediatorwithinfifteen(15)calendardaysfollowingreceiptbytheCEOorChair,asapplicable,oftheMediationNotice,thepartieswillpromptlyselectamutuallyacceptablemediationproviderentity,whichentityshall,assoonaspracticablefollowingsuchentity’sselection,designateamediator,whoisalicensedattorneywithgeneralknowledgeofcontractlaw,whohasnoongoingbusinessrelationshipwitheitherpartyand,totheextentnecessarytomediatetheparticulardispute,generalknowledgeofthedomainnamesystem.Anymediatormustconfirminwritingthatheorsheisnot,andwillnotbecomeduringthetermofthemediation,anemployee,partner,executiveofficer,director,orsecurityholderofICANNoranApplicableRegistryOperator.Ifsuchconfirmationisnotprovidedbytheappointedmediator,thenareplacementmediatorshallbeappointedpursuanttothisSection7.7(d)(i).
(ii) Themediatorshallconductthemediationinaccordancewiththerulesandproceduresforfacilitativemediationthatheorshedeterminesfollowingconsultationwiththeparties.Thepartiesshalldiscussthedisputeingoodfaithandattempt,withthemediator’sassistance,toreachanamicableresolutionofthedispute.
(iii) Eachpartyshallbearitsowncostsinthemediation.Thepartiesshallshareequallythefeesandexpensesofthemediator.
(iv) Ifanagreementisreachedduringthemediation,ICANNshallpostthemutuallyagreedProposedRevisionsonitswebsiteforthePosting
30
PeriodandprovidenoticetoallApplicableRegistryOperatorsinaccordancewithSection7.9.ICANNandtheWorkingGroupwillconsiderthepubliccommentssubmittedontheagreedProposedRevisionsduringthePostingPeriod(includingcommentssubmittedbytheApplicableRegistryOperators).FollowingtheconclusionofthePostingPeriod,theProposedRevisionsshallbesubmittedforRegistryOperatorApprovalandapprovalbytheICANNBoardofDirectors.Ifsuchapprovalsareobtained,theProposedRevisionsshallbedeemedanApprovedAmendment(asdefinedinSection7.6)bytheApplicableRegistryOperatorsandICANN,andshallbeeffectiveanddeemedanamendmenttothisAgreementuponsixty(60)calendardaysnoticefromICANNtoRegistryOperator.
(v) Ifthepartieshavenotresolvedthedisputeforanyreasonbythedatethatisninety(90)calendardaysfollowingreceiptbytheCEOorChair,asapplicable,oftheMediationNotice,themediationshallautomaticallyterminate(unlessextendedbyagreementoftheparties).Themediatorshalldelivertothepartiesadefinitionoftheissuesthatcouldbeconsideredinfuturearbitration,ifinvoked.ThoseissuesaresubjecttothelimitationssetforthinSection7.7(e)(ii)below.
(e) If,followingmediation,ICANNandtheWorkingGrouphavenotreachedanagreementontheProposedRevisions,eithertheCEOortheChairmayprovidetheotherpersonwrittennotice(an“ArbitrationNotice”)requiringICANNandtheApplicableRegistryOperatorstoresolvethedisputethroughbindingarbitrationinaccordancewiththearbitrationprovisionsofSection5.2,subjecttotherequirementsandlimitationsofthisSection7.7(e).
(i) IfanArbitrationNoticeissent,themediator’sdefinitionofissues,alongwiththeProposedRevisions(bethosefromICANN,theWorkingGrouporboth)shallbepostedforpubliccommentonICANN’swebsiteforaperiodofnolessthanthirty(30)calendardays.ICANNandtheWorkingGroupwillconsiderthepubliccommentssubmittedontheProposedRevisionsduringthePostingPeriod(includingcommentssubmittedbytheApplicableRegistryOperators),andinformationregardingsuchcommentsandconsiderationshallbeprovidedtoathree(3)personarbitratorpanel.EachpartymaymodifyitsProposedRevisionsbeforeandafterthePostingPeriod.Thearbitrationproceedingmaynotcommencepriortotheclosingofsuchpubliccommentperiod,andICANNmayconsolidateallchallengesbroughtbyregistryoperators(includingRegistryOperator)intoasingleproceeding.ExceptassetforthinthisSection7.7,thearbitrationshallbeconductedpursuanttoSection5.2.
(ii) NodisputeregardingtheProposedRevisionsmaybesubmittedforarbitrationtotheextentthesubjectmatteroftheProposedRevisions(i)relatestoConsensusPolicy,(ii)fallswithinthesubjectmattercategoriessetforthinSection1.2ofSpecification1,or(iii)seekstoamend
31
anyofthefollowingprovisionsorSpecificationsofthisAgreement:Articles1,3and6;Sections2.1,2.2,2.5,2.7,2.9,2.10,2.16,2.17,2.19,4.1,4.2,7.3,7.6,7.7,7.8,7.10,7.11,7.12,7.13,7.14;Section2.8andSpecification7(butonlytotheextentsuchProposedRevisionsseektoimplementanRPMnotcontemplatedbySections2.8andSpecification7);ExhibitA;andSpecifications1,4,6,10and11.
(iii) ThemediatorwillbriefthearbitratorpanelregardingICANNandtheWorkingGroup’srespectiveproposalsrelatingtotheProposedRevisions.
(iv) NoamendmenttothisAgreementrelatingtotheProposedRevisionsmaybesubmittedforarbitrationbyeithertheWorkingGrouporICANN,unless,inthecaseoftheWorkingGroup,theproposedamendmenthasreceivedRegistryOperatorApprovaland,inthecaseofICANN,theproposedamendmenthasbeenapprovedbytheICANNBoardofDirectors.
(v) InorderforthearbitratorpaneltoapproveeitherICANNortheWorkingGroup’sproposedamendmentrelatingtotheProposedRevisions,thearbitratorpanelmustconcludethatsuchproposedamendmentisconsistentwithabalancedapplicationofICANN’scorevalues(asdescribedinICANN’sBylaws)andreasonableinlightofthebalancingofthecostsandbenefitstothebusinessinterestsoftheApplicableRegistryOperatorsandICANN(asapplicable),andthepublicbenefitsoughttobeachievedbytheProposedRevisionsassetforthinsuchamendment.IfthearbitratorpanelconcludesthateitherICANNortheWorkingGroup’sproposedamendmentrelatingtotheProposedRevisionsmeetstheforegoingstandard,suchamendmentshallbeeffectiveanddeemedanamendmenttothisAgreementuponsixty(60)calendardaysnoticefromICANNtoRegistryOperatoranddeemedanApprovedAmendmenthereunder.
(f) WithrespecttoanApprovedAmendmentrelatingtoanamendmentproposedbyICANN,RegistrymayapplyinwritingtoICANNforanexemptionfromsuchamendmentpursuanttotheprovisionsofSection7.6.
(g) NotwithstandinganythinginthisSection7.7tothecontrary,(a)ifRegistryOperatorprovidesevidencetoICANN'sreasonablesatisfactionthattheApprovedAmendmentwouldmateriallyincreasethecostofprovidingRegistryServices,thenICANNwillallowuptoone-hundredeighty(180)calendardaysfortheApprovedAmendmenttobecomeeffectivewithrespecttoRegistryOperator,and(b)noApprovedAmendmentadoptedpursuanttoSection7.7shallbecomeeffectivewithrespecttoRegistryOperatorifRegistryOperatorprovidesICANNwithanirrevocablenoticeofterminationpursuanttoSection4.4(b).
32
7.8 NoThird-PartyBeneficiaries.ThisAgreementwillnotbeconstruedtocreateanyobligationbyeitherICANNorRegistryOperatortoanynon-partytothisAgreement,includinganyregistrarorregisterednameholder.
7.9 GeneralNotices.ExceptfornoticespursuanttoSections7.6and7.7,allnoticestobegivenunderorinrelationtothisAgreementwillbegiveneither(i)inwritingattheaddressoftheappropriatepartyassetforthbelowor(ii)viafacsimileorelectronicmailasprovidedbelow,unlessthatpartyhasgivenanoticeofchangeofpostaloremailaddress,orfacsimilenumber,asprovidedinthisAgreement.AllnoticesunderSections7.6and7.7shallbegivenbybothpostingoftheapplicableinformationonICANN’swebsiteandtransmissionofsuchinformationtoRegistryOperatorbyelectronicmail.Anychangeinthecontactinformationfornoticebelowwillbegivenbythepartywithinthirty(30)calendardaysofsuchchange.OtherthannoticesunderSections7.6or7.7,anynoticerequiredbythisAgreementwillbedeemedtohavebeenproperlygiven(i)ifinpaperform,whendeliveredinpersonorviacourierservicewithconfirmationofreceiptor(ii)ifviafacsimileorbyelectronicmail,uponconfirmationofreceiptbytherecipient’sfacsimilemachineoremailserver,providedthatsuchnoticeviafacsimileorelectronicmailshallbefollowedbyacopysentbyregularpostalmailservicewithinthree(3)calendardays.AnynoticerequiredbySections7.6or7.7willbedeemedtohavebeengivenwhenelectronicallypostedonICANN’swebsiteanduponconfirmationofreceiptbytheemailserver.Intheeventothermeansofnoticebecomepracticallyachievable,suchasnoticeviaasecurewebsite,thepartieswillworktogethertoimplementsuchnoticemeansunderthisAgreement.
IftoICANN,addressedto:InternetCorporationforAssignedNamesandNumbers12025WaterfrontDrive,Suite300LosAngeles,CA90094-2536USATelephone:+1-310-301-5800Facsimile:+1-310-823-8649Attention:PresidentandCEOWithaRequiredCopyto:GeneralCounselEmail:(Asspecifiedfromtimetotime.)IftoRegistryOperator,addressedto:PublicInterestRegistry1775WiehleAvenue,Suite100Reston,VA20190USATelephone:+1-703-889-5778WithaRequiredCopyto:GeneralCounselEmail:(Asspecifiedfromtimetotime.)
33
7.10 EntireAgreement.ThisAgreement(includingthosespecificationsanddocumentsincorporatedbyreferencetoURLlocationswhichformapartofit)constitutestheentireagreementofthepartiesheretopertainingtotheoperationoftheTLDandsupersedesallprioragreements,understandings,negotiationsanddiscussions,whetheroralorwritten,betweenthepartiesonthatsubject.
7.11 EnglishLanguageControls.NotwithstandinganytranslatedversionofthisAgreementand/orspecificationsthatmaybeprovidedtoRegistryOperator,theEnglishlanguageversionofthisAgreementandallreferencedspecificationsaretheofficialversionsthatbindthepartieshereto.IntheeventofanyconflictordiscrepancybetweenanytranslatedversionofthisAgreementandtheEnglishlanguageversion,theEnglishlanguageversioncontrols.Notices,designations,determinations,andspecificationsmadeunderthisAgreementshallbeintheEnglishlanguage.
7.12 OwnershipRights.NothingcontainedinthisAgreementshallbeconstruedas(a)establishingorgrantingtoRegistryOperatoranypropertyownershiprightsorinterestsofRegistryOperatorintheTLDortheletters,words,symbolsorothercharactersmakinguptheTLDstring,or(b)affectinganyexistingintellectualpropertyorownershiprightsofRegistryOperator.
7.13 Severability;ConflictswithLaws.ThisAgreementshallbedeemedseverable;theinvalidityorunenforceabilityofanytermorprovisionofthisAgreementshallnotaffectthevalidityorenforceabilityofthebalanceofthisAgreementorofanyothertermhereof,whichshallremaininfullforceandeffect.Ifanyoftheprovisionshereofaredeterminedtobeinvalidorunenforceable,thepartiesshallnegotiateingoodfaithtomodifythisAgreementsoastoeffecttheoriginalintentofthepartiesascloselyaspossible.ICANNandtheWorkingGroupwillmutuallycooperatetodevelopanICANNprocedureforICANN’sreviewandconsiderationofallegedconflictsbetweenapplicablelawsandnon-WHOISrelatedprovisionsofthisAgreement.UntilsuchprocedureisdevelopedandimplementedbyICANN,ICANNwillreviewandconsiderallegedconflictsbetweenapplicablelawsandnon-WHOISrelatedprovisionsofthisAgreementinamannersimilartoICANN’sProcedureForHandlingWHOISConflictswithPrivacyLaw.
7.14 CourtOrders.ICANNwillrespectanyorderfromacourtofcompetentjurisdiction,includinganyordersfromanyjurisdictionwheretheconsentornon-objectionofthegovernmentwasarequirementforthedelegationoftheTLD.NotwithstandinganyotherprovisionofthisAgreement,ICANN’simplementationofanysuchorderwillnotbeabreachofthisAgreement
7.15 Confidentiality
(a) SubjecttoSection7.15(c),duringtheTermandforaperiodofthree(3)yearsthereafter,eachpartyshall,andshallcauseitsanditsAffiliates’officers,directors,employeesandagentsto,keepconfidentialandnotpublishorotherwisedisclosetoanythirdparty,directlyorindirectly,anyinformationthatis,andthedisclosingpartyhasmarkedas,orhasotherwisedesignatedinwritingtothereceivingpartyas,“confidential
34
tradesecret,”“confidentialcommercialinformation”or“confidentialfinancialinformation”(collectively,“ConfidentialInformation”),excepttotheextentsuchdisclosureispermittedbythetermsofthisAgreement.
(b) TheconfidentialityobligationsunderSection7.15(a)shallnotapplytoanyConfidentialInformationthat(i)isorhereafterbecomespartofthepublicdomainbypublicuse,publication,generalknowledgeorthelikethroughnofaultofthereceivingpartyinbreachofthisAgreement,(ii)canbedemonstratedbydocumentationorothercompetentprooftohavebeeninthereceivingparty’spossessionpriortodisclosurebythedisclosingpartywithoutanyobligationofconfidentialitywithrespecttosuchinformation,(iii)issubsequentlyreceivedbythereceivingpartyfromathirdpartywhoisnotboundbyanyobligationofconfidentialitywithrespecttosuchinformation,(iv)hasbeenpublishedbyathirdpartyorotherwiseentersthepublicdomainthroughnofaultofthereceivingparty,or(v)canbedemonstratedbydocumentationorothercompetentevidencetohavebeenindependentlydevelopedbyorforthereceivingpartywithoutreferencetothedisclosingparty’sConfidentialInformation.
(c) EachpartyshallhavetherighttodiscloseConfidentialInformationtotheextentthatsuchdisclosureis(i)madeinresponsetoavalidorderofacourtofcompetentjurisdictionor,ifinthereasonableopinionofthereceivingparty’slegalcounsel,suchdisclosureisotherwiserequiredbyapplicablelaw;provided,however,thatthereceivingpartyshallfirsthavegivennoticetothedisclosingpartyandgiventhedisclosingpartyareasonableopportunitytoquashsuchorderortoobtainaprotectiveorderorconfidentialtreatmentorderrequiringthattheConfidentialInformationthatisthesubjectofsuchorderorotherapplicablelawbeheldinconfidencebysuchcourtorotherthirdpartyrecipient,unlessthereceivingpartyisnotpermittedtoprovidesuchnoticeundersuchorderorapplicablelaw,or(ii)madebythereceivingpartyoranyofitsAffiliatestoitsortheirattorneys,auditors,advisors,consultants,contractorsorotherthirdpartiesforusebysuchpersonorentityasmaybenecessaryorusefulinconnectionwiththeperformanceoftheactivitiesunderthisAgreement,providedthatsuchthirdpartyisboundbyconfidentialityobligationsatleastasstringentasthosesetforthherein,eitherbywrittenagreementorthroughprofessionalresponsibilitystandards.
*****
35
INWITNESSWHEREOF,thepartiesheretohavecausedthisAgreementtobeexecutedbytheirdulyauthorizedrepresentatives.
INTERNETCORPORATIONFORASSIGNEDNAMESANDNUMBERS
By: _____________________________ CyrusNamazi SeniorVicePresident,GlobalDomainsDivision
PUBLICINTERESTREGISTRY
By: _____________________________ JonathonNevett PresidentandCEO
36
EXHIBITA
ApprovedServices
TheICANNgTLDApplicantGuidebook(locatedathttp://newgtlds.icann.org/en/applicants/agb)andtheRSEPspecifyprocessesforconsiderationofproposedregistryservices.RegistryOperatormayprovideanyservicethatisrequiredbythetermsofthisAgreement.Inaddition,thefollowingservices(ifany)arespecificallyidentifiedashavingbeenapprovedbyICANNpriortotheeffectivedateoftheAgreement,andRegistryOperatormayprovidesuchservices:
1. DNSService–TLDZoneContentsNotwithstandinganythingelseinthisAgreement,asindicatedinsection2.2.3.3ofthegTLDApplicantGuidebook,permissiblecontentsfortheTLD’sDNSserviceare:1.1. Forthe“Internet”(IN)Class:
1.1.1. ApexSOArecord
1.1.2. ApexNSrecordsandin-bailiwickgluefortheTLD’sDNSservers
1.1.3. NSrecordsandin-bailiwickglueforDNSserversofregisterednamesintheTLD
1.1.4. DSrecordsforregisterednamesintheTLD
1.1.5. RecordsassociatedwithsigningtheTLDzone(e.g.,RRSIG,DNSKEY,
NSEC,NSEC3PARAMandNSEC3)
1.1.6. ApexTXTrecordforzoneversioningpurposes
1.1.7. ApexTYPE65534recordforautomaticdnssecsigningsignaling1.2. Forthe“Chaos”(CH)Class:
1.2.1. TXTrecordsforserverversion/identification(e.g.,TXTrecordsfor“version.bind.”,“id.server.”,“authors.bind”and/or“hostname.bind.”)
(Note:Theabovelanguageeffectivelydoesnotallow,amongotherthings,theinclusionofDNSresourcerecordsthatwouldenableadotlessdomainname(e.g.,apexA,AAAA,MXrecords)intheTLDzone.)IfRegistryOperatorwishestoplaceanyDNSresourcerecordtypeorclassintoitsTLDDNSservice(otherthanthoselistedinSections1.1or1.2above),itmustdescribeindetail
37
itsproposalandsubmitaRegistryServicesEvaluationProcess(RSEP)request.ThiswillbeevaluatedperRSEPtodeterminewhethertheservicewouldcreateariskofameaningfuladverseimpactonsecurityorstabilityoftheDNS.RegistryOperatorrecognizesandacknowledgesthataservicebasedontheuseofless-commonDNSresourcerecordsand/orclassesintheTLDzone,evenifapproved,mightnotworkasintendedforallusersduetolackofsoftwaresupport.
2. Anti-Abuse
RegistryOperatormaysuspend,deleteorotherwisemakechangestodomainnamesincompliancewithitsanti-abusepolicy.
3. SearchableWhois
NotwithstandinganythingelseinthisAgreement,RegistryOperatormustofferasearchableWhoisservicecompliantwiththerequirementsdescribedinSection1.10ofSpecification4ofthisAgreement.RegistryOperatormustmakeavailabletheservicesonlytoauthenticatedusersaftertheyloggedinbysupplyingpropercredentials(e.g.,usernameandpassword).RegistryOperatormustissuesuchcredentialsexclusivelytoeligibleusersandinstitutionsthatsupplysufficientproofoftheirlegitimateinterestinthisfeature(e.g.,lawenforcementagencies).RegistryOperatorshalluserate-limitingtopreventabuseofthesearchableWhoisservice.
4. InternationalizedDomainNames(IDNs)
RegistryOperatormayofferregistrationofIDNsatthesecondandlowerlevelsprovidedthatRegistryOperatorcomplieswiththefollowingrequirements:
4.1. RegistryOperatormustofferRegistrarssupportforhandlingIDNregistrationsinEPP. 4.2. RegistryOperatormusthandlevariantIDNsasfollows:
4.2.1. VariantIDNs(asdefinedintheRegistryOperator’sIDNtablesandIDNRegistrationRules)willbeblockedfromregistration.
4.3. RegistryOperatormayofferregistrationofIDNsinthefollowinglanguages/scripts(IDNTablesandIDNRegistrationRuleswillbepublishedbytheRegistryOperatorasspecifiedintheICANNIDNImplementationGuidelines):
4.3.1Belarusianlanguage
4.3.2Bosnianlanguage
4.3.3Bulgarianlanguage
4.3.4ChineseSimplifiedlanguage
38
4.3.5ChineseTraditionallanguage
4.3.6Danishlanguage
4.3.7Germanlanguage
4.3.8Hungarianlanguage
4.3.9Icelandiclanguage
4.3.10Koreanlanguage
4.3.11Latvianlanguage
4.3.12Lithuanianlanguage
4.3.13Macedonianlanguage
4.3.14Polishlanguage
4.3.15Russianlanguage
4.3.16Serbianlanguage
4.3.17Spanishlanguage
4.3.18Swedishlanguage
4.3.19Ukrainianlanguage
5. ORGSingleandTwoCharacterPhasedAllocationProgram("PhasedAllocationProgram")
ThedomainnamesincludedwithinthescopeofthePhasedAllocationProgramshallbelimitedtosingleandtwo-character.ORGdomainnames,whichRegistryOperatormayallocate.RegistryOperatorreservestherighttoallocatelessthanallofthepreviouslyreservedsingleandtwo-character.ORGdomainnames.6. BulkTransferAfterPartialPortfolioAcquisitionBulkTransferAfterPartialPortfolioAcquisition(“BTAPPA”)isaregistryserviceavailabletoconsentingregistrarsinthecircumstancewhere(i)oneICANN-accreditedregistrarpurchases,bymeansofastockorassetpurchase,mergerorsimilartransaction,aportionbutnotall,ofanotherICANN-accreditedregistrar'sdomainnameportfoliointheTLDor(ii)anewlyaccreditedregistrar(gainingregistrar)requestsatransferofalldomainnamesfromthelosingregistrarforwhichthegainingregistrarhasservedasthereseller.Uponcompletionofthetransfer,thegainingregistraristhenewsponsoringregistrar.ThegainingregistrarmustcertifytheBTAPPAwouldnototherwisequalifyunderICANN’sTransferPolicy.
39
AtleastfifteendaysbeforecompletingaBTAPPA,thelosingregistrarmustprovidewrittennoticeofthebulkchangeofsponsorshiptoalldomainnameregistrantsfornamesinvolvedintheBTAPPA.ThenoticemustincludeanexplanationofhowtheRDDSrecordwillchangeaftertheBTAPPAoccursandcustomersupportandtechnicalcontactinformationofthegainingregistrar.
Thelosingregistrar’sexistingRegistrationAgreementwithcustomersmustpermitthetransferofdomainnamesintheeventofacquisitionbyanotherparty.AsingleBTAPPArequestmaybesubmittedfortransfersfrommultiplelosingregistrarsprovidedtheyareAffiliatedRegistrarsasdefinedbythe2013orsubsequentRegistrarAccreditationAgreement.
Theexpirationdatesoftransferredregistrationsarenotaffectedand,therefore,therearenoICANNfees.OncetheBTAPPAiscomplete,thereisnograceperiodtoreversethetransfer.DomainnamesinthefollowingEPPstatusesatthetimeoftheBTAPPAexecutionshallnotbetransferred:
• Basestatuses:pendingTransfer,pendingDelete.• RedemptionGracePeriod(“RGP”)statuses:redemptionPeriod,pendingRestore,
pendingDelete.DomainnamesthatarewithinagraceperiodwindowaresubjecttoBTAPPA,butRegistryOperatormaydeclinetoprovideacreditforthosenamesdeletedaftertheBTAPPAandpriortotheexpirationoftheapplicablegraceperiodwindow.RegistryOperatormustrejectaBTAPPArequestifthereisreasonableevidencethatatransferunderBTAPPAisbeingrequestedinordertoavoidfeesotherwiseduetoRegistryOperatororICANN.RegistryOperatorhasdiscretiontorejectaBTAPPArequestifaregistrarwithcommonownershipormanagementorbothhasalreadyrequestedBTAPPAservicewithintheprecedingsix-monthperiod.
7. RegistryLock
RegistryOperatormayoffertheRegistryLockservice,whichisaregistryservicethatallowsanauthorizedrepresentativefromthesponsoringRegistrartorequesttheactivationordeactivationofanyofthefollowingEPPstatuses:serverUpdateProhibited,serverDeleteProhibitedand/orserverTransferProhibited.
40
SPECIFICATION1
CONSENSUSPOLICIESANDTEMPORARYPOLICIESSPECIFICATION
1. ConsensusPolicies.
1.1. “ConsensusPolicies”arethosepoliciesestablished(1)pursuanttotheproceduresetforthinICANN’sBylawsanddueprocess,and(2)coveringthosetopicslistedinSection1.2ofthisSpecification.TheConsensusPolicydevelopmentprocessandproceduresetforthinICANN’sBylawsmayberevisedfromtimetotimeinaccordancewiththeprocesssetforththerein.
1.2. ConsensusPoliciesandtheproceduresbywhichtheyaredevelopedshallbedesignedtoproduce,totheextentpossible,aconsensusofInternetstakeholders,includingtheoperatorsofgTLDs.ConsensusPoliciesshallrelatetooneormoreofthefollowing:
1.2.1 issuesforwhichuniformorcoordinatedresolutionisreasonablynecessarytofacilitateinteroperability,securityand/orstabilityoftheInternetorDomainNameSystem(“DNS”);
1.2.2 functionalandperformancespecificationsfortheprovisionofRegistryServices;
1.2.3 SecurityandStabilityoftheregistrydatabasefortheTLD;
1.2.4 registrypoliciesreasonablynecessarytoimplementConsensusPoliciesrelatingtoregistryoperationsorregistrars;
1.2.5 resolutionofdisputesregardingtheregistrationofdomainnames(asopposedtotheuseofsuchdomainnames);or
1.2.6 restrictionsoncross-ownershipofregistryoperatorsandregistrarsorregistrarresellersandregulationsandrestrictionswithrespecttoregistryoperationsandtheuseofregistryandregistrardataintheeventthataregistryoperatorandaregistrarorregistrarresellerareaffiliated.
1.3. SuchcategoriesofissuesreferredtoinSection1.2ofthisSpecificationshallinclude,withoutlimitation:
1.3.1 principlesforallocationofregisterednamesintheTLD(e.g.,first-come/first-served,timelyrenewal,holdingperiodafterexpiration);
1.3.2 prohibitionsonwarehousingoforspeculationindomainnamesbyregistriesorregistrars;
41
1.3.3 reservationofregisterednamesintheTLDthatmaynotberegisteredinitiallyorthatmaynotberenewedduetoreasonsreasonablyrelatedto(i)avoidanceofconfusionamongormisleadingofusers,(ii)intellectualproperty,or(iii)thetechnicalmanagementoftheDNSortheInternet(e.g.,establishmentofreservationsofnamesfromregistration);and
1.3.4 maintenanceofandaccesstoaccurateandup-to-dateinformationconcerningdomainnameregistrations;andprocedurestoavoiddisruptionsofdomainnameregistrationsduetosuspensionorterminationofoperationsbyaregistryoperatororaregistrar,includingproceduresforallocationofresponsibilityforservingregistereddomainnamesinaTLDaffectedbysuchasuspensionortermination.
1.4. InadditiontotheotherlimitationsonConsensusPolicies,theyshallnot:
1.4.1 prescribeorlimitthepriceofRegistryServices;
1.4.2 modifythetermsorconditionsfortherenewalorterminationoftheRegistryAgreement;
1.4.3 modifythelimitationsonTemporaryPolicies(definedbelow)orConsensusPolicies;
1.4.4 modifytheprovisionsintheregistryagreementregardingfeespaidbyRegistryOperatortoICANN;or
1.4.5 modifyICANN’sobligationstoensureequitabletreatmentofregistryoperatorsandactinanopenandtransparentmanner.
2. TemporaryPolicies.RegistryOperatorshallcomplywithandimplementallspecificationsorpoliciesestablishedbytheBoardonatemporarybasis,ifadoptedbytheBoardbyavoteofatleasttwo-thirdsofitsmembers,solongastheBoardreasonablydeterminesthatsuchmodificationsoramendmentsarejustifiedandthatimmediatetemporaryestablishmentofaspecificationorpolicyonthesubjectisnecessarytomaintainthestabilityorsecurityofRegistryServicesortheDNS(“TemporaryPolicies”).
2.1. Suchproposedspecificationorpolicyshallbeasnarrowlytailoredasfeasibletoachievethoseobjectives.InestablishinganyTemporaryPolicy,theBoardshallstatetheperiodoftimeforwhichtheTemporaryPolicyisadoptedandshallimmediatelyimplementtheConsensusPolicydevelopmentprocesssetforthinICANN’sBylaws.
2.1.1 ICANNshallalsoissueanadvisorystatementcontainingadetailedexplanationofitsreasonsforadoptingtheTemporaryPolicyandwhy
42
theBoardbelievessuchTemporaryPolicyshouldreceivetheconsensussupportofInternetstakeholders.
2.1.2 IftheperiodoftimeforwhichtheTemporaryPolicyisadoptedexceedsninety(90)calendardays,theBoardshallreaffirmitstemporaryadoptioneveryninety(90)calendardaysforatotalperiodnottoexceedone(1)year,inordertomaintainsuchTemporaryPolicyineffectuntilsuchtimeasitbecomesaConsensusPolicy.Iftheone(1)yearperiodexpiresor,ifduringsuchone(1)yearperiod,theTemporaryPolicydoesnotbecomeaConsensusPolicyandisnotreaffirmedbytheBoard,RegistryOperatorshallnolongerberequiredtocomplywithorimplementsuchTemporaryPolicy.
3. NoticeandConflicts.RegistryOperatorshallbeaffordedareasonableperiodoftimefollowingnoticeoftheestablishmentofaConsensusPolicyorTemporaryPolicyinwhichtocomplywithsuchpolicyorspecification,takingintoaccountanyurgencyinvolved.IntheeventofaconflictbetweenRegistryServicesandConsensusPoliciesoranyTemporaryPolicy,theConsensusPolicesorTemporaryPolicyshallcontrol,butonlywithrespecttosubjectmatterinconflict.
43
SPECIFICATION2
DATAESCROWREQUIREMENTS
RegistryOperatorwillengageanindependententitytoactasdataescrowagent(“EscrowAgent”)fortheprovisionofdataescrowservicesrelatedtotheRegistryAgreement.ThefollowingTechnicalSpecificationssetforthinPartA,andLegalRequirementssetforthinPartB,willbeincludedinanydataescrowagreementbetweenRegistryOperatorandtheEscrowAgent,underwhichICANNmustbenamedathird-partybeneficiary.Inadditiontothefollowingrequirements,thedataescrowagreementmaycontainotherprovisionsthatarenotcontradictoryorintendedtosubverttherequiredtermsprovidedbelow.
PARTA–TECHNICALSPECIFICATIONS
1. Deposits.TherewillbetwotypesofDeposits:FullandDifferential.Forbothtypes,theuniverseofRegistryobjectstobeconsideredfordataescrowarethoseobjectsnecessaryinordertoofferalloftheapprovedRegistryServices.
1.1. “FullDeposit”willconsistofdatathatreflectsthestateoftheregistryasof00:00:00UTC(CoordinatedUniversalTime)onthedaythatsuchFullDepositissubmittedtoEscrowAgent.
1.2. “DifferentialDeposit”meansdatathatreflectsalltransactionsthatwerenotreflectedinthelastpreviousFullorDifferentialDeposit,asthecasemaybe.EachDifferentialDepositwillcontainalldatabasetransactionssincethepreviousDepositwascompletedasof00:00:00UTCofeachday,butSunday.DifferentialDepositsmustincludecompleteEscrowRecordsasspecifiedbelowthatwerenotincludedorchangedsincethemostrecentfullorDifferentialDeposit(i.e.,alladditions,modificationsorremovalsofdata).
2. ScheduleforDeposits.RegistryOperatorwillsubmitasetofescrowfilesonadailybasisasfollows:
2.1. EachSunday,aFullDepositmustbesubmittedtotheEscrowAgentby23:59UTC.
2.2. Theothersix(6)daysoftheweek,aFullDepositorthecorrespondingDifferentialDepositmustbesubmittedtoEscrowAgentby23:59UTC.
3. EscrowFormatSpecification.
3.1. Deposit’sFormat.Registryobjects,suchasdomains,contacts,nameservers,registrars,etc.willbecompiledintoafileconstructedasdescribedindraft-arias-noguchi-registry-data-escrow,seePartA,Section9,reference1ofthisSpecificationanddraft-arias-noguchi-dnrd-objects-mapping,seePartA,Section9,reference2ofthisSpecification(collectively,the“DNDESpecification”).TheDNDESpecificationdescribessomeelementsas
44
optional;RegistryOperatorwillincludethoseelementsintheDepositsiftheyareavailable.IfnotalreadyanRFC,RegistryOperatorwillusethemostrecentdraftversionoftheDNDESpecificationavailableattheEffectiveDate.RegistryOperatormayatitselectionusenewerversionsoftheDNDESpecificationaftertheEffectiveDate.OncetheDNDESpecificationispublishedasanRFC,RegistryOperatorwillimplementthatversionoftheDNDESpecification,nolaterthanonehundredeighty(180)calendardaysafter.UTF-8characterencodingwillbeused.
3.2. Extensions.IfaRegistryOperatoroffersadditionalRegistryServicesthatrequiresubmissionofadditionaldata,notincludedabove,additional“extensionschemas”shallbedefinedinacasebycasebasistorepresentthatdata.These“extensionschemas”willbespecifiedasdescribedinPartA,Section9,reference2ofthisSpecification.Datarelatedtothe“extensionsschemas”willbeincludedinthedepositfiledescribedinPartA,Section3.1ofthisSpecification.ICANNandtherespectiveRegistryOperatorshallworktogethertoagreeonsuchnewobjects’dataescrowspecifications.
4. ProcessingofDepositfiles.Theuseofcompressionisrecommendedinordertoreduceelectronicdatatransfertimes,andstoragecapacityrequirements.Dataencryptionwillbeusedtoensuretheprivacyofregistryescrowdata.FilesprocessedforcompressionandencryptionwillbeinthebinaryOpenPGPformatasperOpenPGPMessageFormat-RFC4880,seePartA,Section9,reference3ofthisSpecification.AcceptablealgorithmsforPublic-keycryptography,Symmetric-keycryptography,HashandCompressionarethoseenumeratedinRFC4880,notmarkedasdeprecatedinOpenPGPIANARegistry,seePartA,Section9,reference4ofthisSpecification,thatarealsoroyalty-free.Theprocesstofollowforthedatafileinoriginaltextformatis:
(1) TheXMLfileofthedepositasdescribedinPartA,Section9,reference1ofthisSpecificationmustbenamedasthecontainingfileasspecifiedinSection5butwiththeextensionxml.
(2) Thedatafile(s)areaggregatedinatarballfilenamedthesameas(1)butwithextensiontar.
(3) AcompressedandencryptedOpenPGPMessageiscreatedusingthetarballfileassoleinput.ThesuggestedalgorithmforcompressionisZIPasperRFC4880.Thecompresseddatawillbeencryptedusingtheescrowagent’spublickey.ThesuggestedalgorithmsforPublic-keyencryptionareElgamalandRSAasperRFC4880.ThesuggestedalgorithmsforSymmetric-keyencryptionareTripleDES,AES128andCAST5asperRFC4880.
(4) Thefilemaybesplitasnecessaryif,oncecompressedandencrypted,itislargerthanthefilesizelimitagreedwiththeescrowagent.Everypartofa
45
splitfile,orthewholefileifnotsplit,willbecalledaprocessedfileinthissection.
(5) AdigitalsignaturefilewillbegeneratedforeveryprocessedfileusingtheRegistryOperator’sprivatekey.ThedigitalsignaturefilewillbeinbinaryOpenPGPformatasperRFC4880Section9,reference3,andwillnotbecompressedorencrypted.ThesuggestedalgorithmsforDigitalsignaturesareDSAandRSAasperRFC4880.ThesuggestedalgorithmforHashesinDigitalsignaturesisSHA256.
(6) TheprocessedfilesanddigitalsignaturefileswillthenbetransferredtotheEscrowAgentthroughsecureelectronicmechanisms,suchas,SFTP,SCP,HTTPSfileupload,etc.asagreedbetweentheEscrowAgentandtheRegistryOperator.Non-electronicdeliverythroughaphysicalmediumsuchasCD-ROMs,DVD-ROMs,orUSBstoragedevicesmaybeusedifauthorizedbyICANN.
(7) TheEscrowAgentwillthenvalidateevery(processed)transferreddatafileusingtheproceduredescribedinPartA,Section8ofthisSpecification.
5. FileNamingConventions.Fileswillbenamedaccordingtothefollowingconvention:{gTLD}_{YYYY-MM-DD}_{type}_S{#}_R{rev}.{ext}where:
5.1. {gTLD}isreplacedwiththegTLDname;incaseofanIDN-TLD,theASCII-compatibleform(A-Label)mustbeused;
5.2. {YYYY-MM-DD}isreplacedbythedatecorrespondingtothetimeusedasatimelinewatermarkforthetransactions;i.e.fortheFullDepositcorrespondingto2009-08-02T00:00Z,thestringtobeusedwouldbe“2009-08-02”;
5.3. {type}isreplacedby:
(1) “full”,ifthedatarepresentsaFullDeposit;
(2) “diff”,ifthedatarepresentsaDifferentialDeposit;
(3) “thin”,ifthedatarepresentsaBulkRegistrationDataAccessfile,asspecifiedinSection3ofSpecification4;
(4) "thick-{gurid}",ifthedatarepresentThickRegistrationDatafromaspecificregistrar,asdefinedinSection3.2ofSpecification4.The{gurid}elementmustbereplacedwiththeIANARegistrarIDassociatedwiththedata.
5.4. {#}isreplacedbythepositionofthefileinaseriesoffiles,beginningwith“1”;incaseofalonefile,thismustbereplacedby“1”.
46
5.5. {rev}isreplacedbythenumberofrevision(orresend)ofthefilebeginningwith“0”:
5.6. {ext}isreplacedby“sig”ifitisadigitalsignaturefileofthequasi-homonymousfile.Otherwiseitisreplacedby“ryde”.
6. DistributionofPublicKeys.EachofRegistryOperatorandEscrowAgentwilldistributeitspublickeytotheotherparty(RegistryOperatororEscrowAgent,asthecasemaybe)viaemailtoanemailaddresstobespecified.Eachpartywillconfirmreceiptoftheotherparty’spublickeywithareplyemail,andthedistributingpartywillsubsequentlyreconfirmtheauthenticityofthekeytransmittedviaofflinemethods,likeinpersonmeeting,telephone,etc.Inthisway,publickeytransmissionisauthenticatedtoauserabletosendandreceivemailviaamailserveroperatedbythedistributingparty.EscrowAgent,RegistryOperatorandICANNwillexchangepublickeysbythesameprocedure.
7. NotificationofDeposits.AlongwiththedeliveryofeachDeposit,RegistryOperatorwilldelivertoEscrowAgentandtoICANN(usingtheAPIdescribedindraft-lozano-icann-registry-interfaces,seePartA,Section9,reference5ofthisSpecification(the“InterfaceSpecification”))awrittenstatementfromRegistryOperator(whichmaybebyauthenticatede-mail)thatincludesacopyofthereportgenerateduponcreationoftheDepositandstatesthattheDeposithasbeeninspectedbyRegistryOperatorandiscompleteandaccurate.ThepreparationandsubmissionofthisstatementmustbeperformedbytheRegistryOperatororitsdesignee,providedthatsuchdesigneemaynotbetheEscrowAgentoranyofEscrowAgent’sAffiliates.RegistryOperatorwillincludetheDeposit’s“id”and“resend”attributesinitsstatement.TheattributesareexplainedinPartA,Section9,reference1ofthisSpecification.
IfnotalreadyanRFC,RegistryOperatorwillusethemostrecentdraftversionoftheInterfaceSpecificationattheEffectiveDate.RegistryOperatormayatitselectionusenewerversionsoftheInterfaceSpecificationaftertheEffectiveDate.OncetheInterfaceSpecificationispublishedasanRFC,RegistryOperatorwillimplementthatversionoftheInterfaceSpecification,nolaterthanonehundredeighty(180)calendardaysaftersuchpublishing.
8. VerificationProcedure.
(1) Thesignaturefileofeachprocessedfileisvalidated.
(2) Ifprocessedfilesarepiecesofabiggerfile,thelatterisputtogether.
(3) Eachfileobtainedinthepreviousstepisthendecryptedanduncompressed.
(4) EachdatafilecontainedinthepreviousstepisthenvalidatedagainsttheformatdefinedinPartA,Section9,reference1ofthisSpecification.
47
(5) Thedataescrowagentextendedverificationprocess,asdefinedbelowinreference2ofPartAofthisSpecification2,aswellasanyotherdataescrowverificationprocesscontainedinsuchreference.
Ifanydiscrepancyisfoundinanyofthesteps,theDepositwillbeconsideredincomplete.
9. References.
(1) DomainNameDataEscrowSpecification(workinprogress),http://tools.ietf.org/html/draft-arias-noguchi-registry-data-escrow
(2) DomainNameRegistrationData(DNRD)ObjectsMapping,http://tools.ietf.org/html/draft-arias-noguchi-dnrd-objects-mapping
(3) OpenPGPMessageFormat,http://www.rfc-editor.org/rfc/rfc4880.txt
(4) OpenPGPparameters,http://www.iana.org/assignments/pgp-parameters/pgp-parameters.xhtml
(5) ICANNinterfacesforregistriesanddataescrowagents,http://tools.ietf.org/html/draft-lozano-icann-registry-interfaces
48
PARTB–LEGALREQUIREMENTS
1. EscrowAgent.Priortoenteringintoanescrowagreement,theRegistryOperatormustprovidenoticetoICANNastotheidentityoftheEscrowAgent,andprovideICANNwithcontactinformationandacopyoftherelevantescrowagreement,andallamendmentsthereto.Inaddition,priortoenteringintoanescrowagreement,RegistryOperatormustobtaintheconsentofICANNto(a)usethespecifiedEscrowAgent,and(b)enterintotheformofescrowagreementprovided.ICANNmustbeexpresslydesignatedasathird-partybeneficiaryoftheescrowagreement.ICANNreservestherighttowithholditsconsenttoanyEscrowAgent,escrowagreement,oranyamendmentthereto,allinitssolediscretion.
2. Fees.RegistryOperatormustpay,orhavepaidonitsbehalf,feestotheEscrowAgentdirectly.IfRegistryOperatorfailstopayanyfeebytheduedate(s),theEscrowAgentwillgiveICANNwrittennoticeofsuchnon-paymentandICANNmaypaythepast-duefee(s)withinfifteen(15)calendardaysafterreceiptofthewrittennoticefromEscrowAgent.Uponpaymentofthepast-duefeesbyICANN,ICANNshallhaveaclaimforsuchamountagainstRegistryOperator,whichRegistryOperatorshallberequiredtosubmittoICANNtogetherwiththenextfeepaymentdueundertheRegistryAgreement.
3. Ownership.OwnershipoftheDepositsduringtheeffectivetermoftheRegistryAgreementshallremainwithRegistryOperatoratalltimes.Thereafter,RegistryOperatorshallassignanysuchownershiprights(includingintellectualpropertyrights,asthecasemaybe)insuchDepositstoICANN.IntheeventthatduringthetermoftheRegistryAgreementanyDepositisreleasedfromescrowtoICANN,anyintellectualpropertyrightsheldbyRegistryOperatorintheDepositswillautomaticallybelicensedtoICANNortoapartydesignatedinwritingbyICANNonanon-exclusive,perpetual,irrevocable,royalty-free,paid-upbasis,foranyuserelatedtotheoperation,maintenanceortransitionoftheTLD.
4. IntegrityandConfidentiality.EscrowAgentwillberequiredto(i)holdandmaintaintheDepositsinasecure,locked,andenvironmentallysafefacility,whichisaccessibleonlytoauthorizedrepresentativesofEscrowAgent,(ii)protecttheintegrityandconfidentialityoftheDepositsusingcommerciallyreasonablemeasuresand(iii)keepandsafeguardeachDepositforone(1)year.ICANNandRegistryOperatorwillbeprovidedtherighttoinspectEscrowAgent’sapplicablerecordsuponreasonablepriornoticeandduringnormalbusinesshours.RegistryOperatorandICANNwillbeprovidedwiththerighttodesignateathird-partyauditortoauditEscrowAgent’scompliancewiththetechnicalspecificationsandmaintenancerequirementsofthisSpecification2fromtimetotime.
IfEscrowAgentreceivesasubpoenaoranyotherorderfromacourtorotherjudicialtribunalpertainingtothedisclosureorreleaseoftheDeposits,EscrowAgentwillpromptlynotifytheRegistryOperatorandICANNunlessprohibitedbylaw.AfternotifyingtheRegistryOperatorandICANN,EscrowAgentshallallow
49
sufficienttimeforRegistryOperatororICANNtochallengeanysuchorder,whichshallbetheresponsibilityofRegistryOperatororICANN;provided,however,thatEscrowAgentdoesnotwaiveitsrightstopresentitspositionwithrespecttoanysuchorder.EscrowAgentwillcooperatewiththeRegistryOperatororICANNtosupporteffortstoquashorlimitanysubpoena,atsuchparty’sexpense.AnypartyrequestingadditionalassistanceshallpayEscrowAgent’sstandardchargesorasquoteduponsubmissionofadetailedrequest.
5. Copies.EscrowAgentmaybepermittedtoduplicateanyDeposit,inordertocomplywiththetermsandprovisionsoftheescrowagreement.
6. ReleaseofDeposits.EscrowAgentwillmakeavailableforelectronicdownload(unlessotherwiserequested)toICANNoritsdesignee,withintwenty-four(24)hours,attheRegistryOperator’sexpense,allDepositsinEscrowAgent’spossessionintheeventthattheEscrowAgentreceivesarequestfromRegistryOperatortoeffectsuchdeliverytoICANN,orreceivesoneofthefollowingwrittennoticesbyICANNstatingthat:
6.1. theRegistryAgreementhasexpiredwithoutrenewal,orbeenterminated;or
6.2. ICANNhasnotreceivedanotificationasdescribedinPartB,Sections7.1and7.2ofthisSpecificationfromEscrowAgentwithinfive(5)calendardaysaftertheDeposit’sscheduleddeliverydate;(a)ICANNgavenoticetoEscrowAgentandRegistryOperatorofthatfailure;and(b)ICANNhasnot,withinseven(7)calendardaysaftersuchnotice,receivedthenotificationfromEscrowAgent;or
6.3. ICANNhasreceivednotificationasdescribedinPartB,Sections7.1and7.2ofthisSpecificationfromEscrowAgentoffailedverificationofthelatestescrowdepositforaspecificdateoranotificationofamissingdeposit,andthenotificationisforadepositthatshouldhavebeenmadeonSunday(i.e.,aFullDeposit);(a)ICANNgavenoticetoRegistryOperatorofthatreceipt;and(b)ICANNhasnot,withinseven(7)calendardaysaftersuchnotice,receivednotificationasdescribedinPartB,Sections7.1and7.2ofthisSpecificationfromEscrowAgentofverificationofaremediatedversionofsuchFullDeposit;or
6.4. ICANNhasreceivedfivenotificationsfromEscrowAgentwithinthelastthirty(30)calendardaysnotifyingICANNofeithermissingorfailedescrowdepositsthatshouldhavebeenmadeMondaythroughSaturday(i.e.,aDifferentialDeposit),and(x)ICANNprovidednoticetoRegistryOperatorofthereceiptofsuchnotifications;and(y)ICANNhasnot,withinseven(7)calendardaysafterdeliveryofsuchnoticetoRegistryOperator,receivednotificationfromEscrowAgentofverificationofaremediatedversionofsuchDifferentialDeposit;or
50
6.5. RegistryOperatorhas:(i)ceasedtoconductitsbusinessintheordinarycourse;or(ii)filedforbankruptcy,becomeinsolventoranythinganalogoustoanyoftheforegoingunderthelawsofanyjurisdictionanywhereintheworld;or
6.6. RegistryOperatorhasexperiencedafailureofcriticalregistryfunctionsandICANNhasasserteditsrightspursuanttoSection2.13oftheAgreement;or
6.7. acompetentcourt,arbitral,legislative,orgovernmentagencymandatesthereleaseoftheDepositstoICANN;or
6.8. pursuanttoContractualandOperationalComplianceAuditsasspecifiedunderSection2.11oftheAgreement.
UnlessEscrowAgenthaspreviouslyreleasedtheRegistryOperator’sDepositstoICANNoritsdesignee,EscrowAgentwilldeliverallDepositstoICANNuponexpirationorterminationoftheRegistryAgreementortheEscrowAgreement.
7. VerificationofDeposits.
7.1. Withintwenty-four(24)hoursafterreceivingeachDepositorcorrectedDeposit,EscrowAgentmustverifytheformatandcompletenessofeachDepositanddelivertoICANNanotificationgeneratedforeachDeposit.ReportswillbedeliveredelectronicallyusingtheAPIdescribedindraft-lozano-icann-registry-interfaces,seePartA,Section9,reference5ofthisSpecification.
7.2. IfEscrowAgentdiscoversthatanyDepositfailstheverificationproceduresorifEscrowAgentdoesnotreceiveanyscheduledDeposit,EscrowAgentmustnotifyRegistryOperatoreitherbyemail,faxorphoneandICANN(usingtheAPIdescribedindraft-lozano-icann-registry-interfaces,seePartA,Section9,reference5ofthisSpecification)ofsuchnonconformityornon-receiptwithintwenty-four(24)hoursafterreceivingthenon-conformantDepositorthedeadlineforsuchDeposit,asapplicable.Uponnotificationofsuchverificationordeliveryfailure,RegistryOperatormustbegindevelopingmodifications,updates,corrections,andotherfixesoftheDepositnecessaryfortheDeposittobedeliveredandpasstheverificationproceduresanddeliversuchfixestoEscrowAgentaspromptlyaspossible.
8. Amendments.EscrowAgentandRegistryOperatorshallamendthetermsoftheEscrowAgreementtoconformtothisSpecification2withinten(10)calendardaysofanyamendmentormodificationtothisSpecification2.IntheeventofaconflictbetweenthisSpecification2andtheEscrowAgreement,thisSpecification2shallcontrol.
9. Indemnity.EscrowAgentshallindemnifyandholdharmlessRegistryOperatorandICANN,andeachoftheirrespectivedirectors,officers,agents,employees,members,
51
andstockholders(“Indemnitees”)absolutelyandforeverfromandagainstanyandallclaims,actions,damages,suits,liabilities,obligations,costs,fees,charges,andanyotherexpenseswhatsoever,includingreasonableattorneys’feesandcosts,thatmaybeassertedbyathirdpartyagainstanyIndemniteeinconnectionwiththemisrepresentation,negligenceormisconductofEscrowAgent,itsdirectors,officers,agents,employeesandcontractors.
52
SPECIFICATION3
FORMATANDCONTENTFORREGISTRYOPERATORMONTHLYREPORTING
RegistryOperatorshallprovideonesetofmonthlyreportspergTLD,usingtheAPIdescribedindraft-lozano-icann-registry-interfaces,seeSpecification2,PartA,Section9,reference5,withthefollowingcontent.
ICANNmayrequestinthefuturethatthereportsbedeliveredbyothermeansandusingotherformats.ICANNwillusereasonablecommercialeffortstopreservetheconfidentialityoftheinformationreporteduntilthree(3)monthsaftertheendofthemonthtowhichthereportsrelate.UnlesssetforthinthisSpecification3,anyreferencetoaspecifictimereferstoCoordinatedUniversalTime(UTC).Monthlyreportsshallconsistofdatathatreflectsthestateoftheregistryattheendofthemonth(UTC).
1. Per-RegistrarTransactionsReport.Thisreportshallbecompiledinacommaseparated-valueformattedfileasspecifiedinRFC4180.Thefileshallbenamed“gTLD-transactions-yyyymm.csv”,where“gTLD”isthegTLDname;incaseofanIDN-TLD,theA-labelshallbeused;“yyyymm”istheyearandmonthbeingreported.Thefileshallcontainthefollowingfieldsperregistrar:
Field#
Fieldname Description
01 registrar-name Registrar’sfullcorporatenameasregisteredwithIANA
02 iana-id Forcaseswheretheregistryoperatoractsasregistrar(i.e.,withouttheuseofanICANNaccreditedregistrar)either9998or9999shouldbeuseddependingonregistrationtype(asdescribedinSpecification5),otherwisethesponsoringRegistrarIANAidshouldbeusedasspecifiedinhttp://www.iana.org/assignments/registrar-ids
03 total-domains totaldomainnamesundersponsorshipinanyEPPstatusbutpendingCreatethathavenotbeenpurged
04 total-nameservers totalnameservers(eitherhostobjectsornameserverhostsasdomainnameattributes)associatedwithdomainnamesregisteredfortheTLDinanyEPPstatusbutpendingCreatethathavenotbeenpurged
05 net-adds-1-yr numberofdomainssuccessfullyregistered(i.e.,notinEPPpendingCreatestatus)withaninitialtermofone(1)year(andnotdeletedwithinthe
53
addgraceperiod).Atransactionmustbereportedinthemonththeaddgraceperiodends.
06 net-adds-2-yr numberofdomainssuccessfullyregistered(i.e.,notinEPPpendingCreatestatus)withaninitialtermoftwo(2)years(andnotdeletedwithintheaddgraceperiod).Atransactionmustbereportedinthemonththeaddgraceperiodends.
07 net-adds-3-yr numberofdomainssuccessfullyregistered(i.e.,notinEPPpendingCreatestatus)withaninitialtermofthree(3)years(andnotdeletedwithintheaddgraceperiod).Atransactionmustbereportedinthemonththeaddgraceperiodends.
08 net-adds-4-yr numberofdomainssuccessfullyregistered(i.e.,notinEPPpendingCreatestatus)withaninitialtermoffour(4)years(andnotdeletedwithintheaddgraceperiod).Atransactionmustbereportedinthemonththeaddgraceperiodends.
09 net-adds-5-yr numberofdomainssuccessfullyregistered(i.e.,notinEPPpendingCreatestatus)withaninitialtermoffive(5)years(andnotdeletedwithintheaddgraceperiod).Atransactionmustbereportedinthemonththeaddgraceperiodends.
10 net-adds-6-yr numberofdomainssuccessfullyregistered(i.e.,notinEPPpendingCreatestatus)withaninitialtermofsix(6)years(andnotdeletedwithintheaddgraceperiod).Atransactionmustbereportedinthemonththeaddgraceperiodends.
11 net-adds-7-yr numberofdomainssuccessfullyregistered(i.e.,notinEPPpendingCreatestatus)withaninitialtermofseven(7)years(andnotdeletedwithintheaddgraceperiod).Atransactionmustbereportedinthemonththeaddgraceperiodends.
12 net-adds-8-yr numberofdomainssuccessfullyregistered(i.e.,notinEPPpendingCreatestatus)withaninitialtermofeight(8)years(andnotdeletedwithintheaddgraceperiod).Atransactionmustbereportedinthemonththeaddgraceperiodends.
13 net-adds-9-yr numberofdomainssuccessfullyregistered(i.e.,notinEPPpendingCreatestatus)withaninitialtermofnine(9)years(andnotdeletedwithintheaddgraceperiod).Atransactionmustbereportedinthemonththeaddgraceperiodends.
54
14 net-adds-10-yr numberofdomainssuccessfullyregistered(i.e.,notinEPPpendingCreatestatus)withaninitialtermoften(10)years(andnotdeletedwithintheaddgraceperiod).Atransactionmustbereportedinthemonththeaddgraceperiodends.
15 net-renews-1-yr numberofdomainssuccessfullyrenewed(i.e.,notinEPPpendingRenewstatus)eitherautomaticallyorbycommandwithanewrenewalperiodofone(1)year(andnotdeletedwithinthereneworauto-renewgraceperiod).Atransactionmustbereportedinthemonththereneworauto-renewgraceperiodends.
16 net-renews-2-yr numberofdomainssuccessfullyrenewed(i.e.,notinEPPpendingRenewstatus)eitherautomaticallyorbycommandwithanewrenewalperiodoftwo(2)years(andnotdeletedwithinthereneworauto-renewgraceperiod).Atransactionmustbereportedinthemonththereneworauto-renewgraceperiodends.
17 net-renews-3-yr numberofdomainssuccessfullyrenewed(i.e.,notinEPPpendingRenewstatus)eitherautomaticallyorbycommandwithanewrenewalperiodofthree(3)years(andnotdeletedwithinthereneworauto-renewgraceperiod).Atransactionmustbereportedinthemonththereneworauto-renewgraceperiodends.
18 net-renews-4-yr numberofdomainssuccessfullyrenewed(i.e.,notinEPPpendingRenewstatus)eitherautomaticallyorbycommandwithanewrenewalperiodoffour(4)years(andnotdeletedwithinthereneworauto-renewgraceperiod).Atransactionmustbereportedinthemonththereneworauto-renewgraceperiodends.
19 net-renews-5-yr numberofdomainssuccessfullyrenewed(i.e.,notinEPPpendingRenewstatus)eitherautomaticallyorbycommandwithanewrenewalperiodoffive(5)years(andnotdeletedwithinthereneworauto-renewgraceperiod).Atransactionmustbereportedinthemonththereneworauto-renewgraceperiodends.
20 net-renews-6-yr numberofdomainssuccessfullyrenewed(i.e.,notinEPPpendingRenewstatus)eitherautomaticallyorbycommandwithanewrenewalperiodofsix
55
(6)years(andnotdeletedwithinthereneworauto-renewgraceperiod).Atransactionmustbereportedinthemonththereneworauto-renewgraceperiodends.
21 net-renews-7-yr numberofdomainssuccessfullyrenewed(i.e.,notinEPPpendingRenewstatus)eitherautomaticallyorbycommandwithanewrenewalperiodofseven(7)years(andnotdeletedwithinthereneworauto-renewgraceperiod).Atransactionmustbereportedinthemonththereneworauto-renewgraceperiodends.
22 net-renews-8-yr numberofdomainssuccessfullyrenewed(i.e.,notinEPPpendingRenewstatus)eitherautomaticallyorbycommandwithanewrenewalperiodofeight(8)years(andnotdeletedwithinthereneworauto-renewgraceperiod).Atransactionmustbereportedinthemonththereneworauto-renewgraceperiodends.
23 net-renews-9-yr numberofdomainssuccessfullyrenewed(i.e.,notinEPPpendingRenewstatus)eitherautomaticallyorbycommandwithanewrenewalperiodofnine(9)years(andnotdeletedwithinthereneworauto-renewgraceperiod).Atransactionmustbereportedinthemonththereneworauto-renewgraceperiodends.
24 net-renews-10-yr numberofdomainssuccessfullyrenewed(i.e.,notinEPPpendingRenewstatus)eitherautomaticallyorbycommandwithanewrenewalperiodoften(10)years(andnotdeletedwithinthereneworauto-renewgraceperiod).Atransactionmustbereportedinthemonththereneworauto-renewgraceperiodends.
25 transfer-gaining-successful numberofdomaintransfersinitiatedbythisregistrarthatweresuccessfullycompleted(eitherexplicitlyorautomaticallyapproved)andnotdeletedwithinthetransfergraceperiod.Atransactionmustbereportedinthemonththetransfergraceperiodends.
26 transfer-gaining-nacked numberofdomaintransfersinitiatedbythisregistrarthatwererejected(e.g.,EPPtransferop="reject")bytheotherregistrar
56
27 transfer-losing-successful numberofdomaintransfersinitiatedbyanotherregistrarthatweresuccessfullycompleted(eitherexplicitlyorautomaticallyapproved)
28 transfer-losing-nacked numberofdomaintransfersinitiatedbyanotherregistrarthatthisregistrarrejected(e.g.,EPPtransferop="reject")
29 transfer-disputed-won numberoftransferdisputesinwhichthisregistrarprevailed(reportedinthemonthwherethedeterminationhappened)
30 transfer-disputed-lost numberoftransferdisputesthisregistrarlost(reportedinthemonthwherethedeterminationhappened)
31 transfer-disputed-nodecision numberoftransferdisputesinvolvingthisregistrarwithasplitornodecision(reportedinthemonthwherethedeterminationhappened)
32 deleted-domains-grace domainsdeletedwithintheaddgraceperiod(doesnotincludenamesdeletedwhileinEPPpendingCreatestatus).Adeletionmustbereportedinthemonththenameispurged.
33 deleted-domains-nograce domainsdeletedoutsidetheaddgraceperiod(doesnotincludenamesdeletedwhileinEPPpendingCreatestatus).Adeletionmustbereportedinthemonththenameispurged.
34 restored-domains domainnamesrestoredduringreportingperiod35 restored-noreport totalnumberofrestorednamesforwhicha
restorereportisrequiredbytheregistry,buttheregistrarfailedtosubmitit
36 agp-exemption-requests totalnumberofAGP(addgraceperiod)exemptionrequests
37 agp-exemptions-granted totalnumberofAGP(addgraceperiod)exemptionrequestsgranted
38 agp-exempted-domains totalnumberofnamesaffectedbygrantedAGP(addgraceperiod)exemptionrequests
39 attempted-adds numberofattempted(bothsuccessfulandfailed)domainnamecreatecommands
Thefirstlineshallincludethefieldnamesexactlyasdescribedinthetableaboveasa“headerline”asdescribedinsection2ofRFC4180.Thelastlineofeachreportshallincludetotalsforeachcolumnacrossallregistrars;thefirstfieldofthislineshallread“Totals”whilethesecondfieldshallbeleftemptyinthatline.Nootherlinesbesidestheonesdescribedaboveshallbeincluded.Linebreaksshallbe<U+000D,U+000A>asdescribedinRFC4180.
57
2. RegistryFunctionsActivityReport.Thisreportshallbecompiledinacommaseparated-valueformattedfileasspecifiedinRFC4180.Thefileshallbenamed“gTLD-activity-yyyymm.csv”,where“gTLD”isthegTLDname;incaseofanIDN-TLD,theA-labelshallbeused;“yyyymm”istheyearandmonthbeingreported.Thefileshallcontainthefollowingfields:
Field# FieldName Description
01 operational-registrars numberofoperationalregistrarsintheproductionsystemattheendofthereportingperiod
02 zfa-passwords numberofactivezonefileaccesspasswordsattheendofthereportingperiod;"CZDS"maybeusedinsteadofthenumberofactivezonefileaccesspasswords,iftheCentralizedZoneDataService(CZDS)isusedtoprovidethezonefiletotheenduser
03 whois-43-queries numberofWHOIS(port-43)queriesrespondedduringthereportingperiod
04 web-whois-queries numberofWeb-basedWhoisqueriesrespondedduringthereportingperiod,notincludingsearchableWhois
05 searchable-whois-queries numberofsearchableWhoisqueriesrespondedduringthereportingperiod,ifoffered
06 dns-udp-queries-received numberofDNSqueriesreceivedoverUDPtransportduringthereportingperiod
07 dns-udp-queries-responded numberofDNSqueriesreceivedoverUDPtransportthatwererespondedduringthereportingperiod
08 dns-tcp-queries-received numberofDNSqueriesreceivedoverTCPtransportduringthereportingperiod
09 dns-tcp-queries-responded numberofDNSqueriesreceivedoverTCPtransportthatwererespondedduringthereportingperiod
10 srs-dom-check numberofSRS(EPPandanyotherinterface)domainname“check”requestsrespondedduringthereportingperiod
11 srs-dom-create numberofSRS(EPPandanyotherinterface)domainname“create”requestsrespondedduringthereportingperiod
58
Field# FieldName Description
12 srs-dom-delete numberofSRS(EPPandanyotherinterface)domainname“delete”requestsrespondedduringthereportingperiod
13 srs-dom-info numberofSRS(EPPandanyotherinterface)domainname“info”requestsrespondedduringthereportingperiod
14 srs-dom-renew numberofSRS(EPPandanyotherinterface)domainname“renew”requestsrespondedduringthereportingperiod
15 srs-dom-rgp-restore-report numberofSRS(EPPandanyotherinterface)domainnameRGP“restore”requestsdeliveringarestorereportrespondedduringthereportingperiod
16 srs-dom-rgp-restore-request numberofSRS(EPPandanyotherinterface)domainnameRGP“restore”requestsrespondedduringthereportingperiod
17 srs-dom-transfer-approve numberofSRS(EPPandanyotherinterface)domainname“transfer”requeststoapprovetransfersrespondedduringthereportingperiod
18 srs-dom-transfer-cancel numberofSRS(EPPandanyotherinterface)domainname“transfer”requeststocanceltransfersrespondedduringthereportingperiod
19 srs-dom-transfer-query numberofSRS(EPPandanyotherinterface)domainname“transfer”requeststoqueryaboutatransferrespondedduringthereportingperiod
20 srs-dom-transfer-reject numberofSRS(EPPandanyotherinterface)domainname“transfer”requeststorejecttransfersrespondedduringthereportingperiod
21 srs-dom-transfer-request numberofSRS(EPPandanyotherinterface)domainname“transfer”requeststorequesttransfersrespondedduringthereportingperiod
22 srs-dom-update numberofSRS(EPPandanyotherinterface)domainname“update”requests(notincludingRGPrestorerequests)respondedduringthereportingperiod
59
Field# FieldName Description
23 srs-host-check numberofSRS(EPPandanyotherinterface)host“check”requestsrespondedduringthereportingperiod
24 srs-host-create numberofSRS(EPPandanyotherinterface)host“create”requestsrespondedduringthereportingperiod
25 srs-host-delete numberofSRS(EPPandanyotherinterface)host“delete”requestsrespondedduringthereportingperiod
26 srs-host-info numberofSRS(EPPandanyotherinterface)host“info”requestsrespondedduringthereportingperiod
27 srs-host-update numberofSRS(EPPandanyotherinterface)host“update”requestsrespondedduringthereportingperiod
28 srs-cont-check numberofSRS(EPPandanyotherinterface)contact“check”requestsrespondedduringthereportingperiod
29 srs-cont-create numberofSRS(EPPandanyotherinterface)contact“create”requestsrespondedduringthereportingperiod
30 srs-cont-delete numberofSRS(EPPandanyotherinterface)contact“delete”requestsrespondedduringthereportingperiod
31 srs-cont-info numberofSRS(EPPandanyotherinterface)contact“info”requestsrespondedduringthereportingperiod
32 srs-cont-transfer-approve numberofSRS(EPPandanyotherinterface)contact“transfer”requeststoapprovetransfersrespondedduringthereportingperiod
33 srs-cont-transfer-cancel numberofSRS(EPPandanyotherinterface)contact“transfer”requeststocanceltransfersrespondedduringthereportingperiod
34 srs-cont-transfer-query numberofSRS(EPPandanyotherinterface)contact“transfer”requeststoqueryaboutatransferrespondedduringthereportingperiod
35 srs-cont-transfer-reject numberofSRS(EPPandanyotherinterface)contact“transfer”requeststorejecttransfersrespondedduringthereportingperiod
60
Field# FieldName Description
36 srs-cont-transfer-request numberofSRS(EPPandanyotherinterface)contact“transfer”requeststorequesttransfersrespondedduringthereportingperiod
37 srs-cont-update numberofSRS(EPPandanyotherinterface)contact“update”requestsrespondedduringthereportingperiod
Thefirstlineshallincludethefieldnamesexactlyasdescribedinthetableaboveasa“headerline”asdescribedinsection2ofRFC4180.Nootherlinesbesidestheonesdescribedaboveshallbeincluded.Linebreaksshallbe<U+000D,U+000A>asdescribedinRFC4180.
ForgTLDsthatarepartofasingle-instanceSharedRegistrySystem,theRegistryFunctionsActivityReportmayincludethetotalcontactorhosttransactionsforallthegTLDsinthesystem.
61
SPECIFICATION4
REGISTRATIONDATAPUBLICATIONSERVICES
1. RegistrationDataDirectoryServices.UntilICANNrequiresadifferentprotocol,RegistryOperatorwilloperateaWHOISserviceavailableviaport43inaccordancewithRFC3912,andaweb-basedDirectoryServiceat<whois.nic.TLD>providingfreepublicquery-basedaccesstoatleastthefollowingelementsinthefollowingformat.ICANNreservestherighttospecifyalternativeformatsandprotocols,anduponsuchspecification,theRegistryOperatorwillimplementsuchalternativespecificationassoonasreasonablypracticable.
RegistryOperatorshallimplementanewstandardsupportingaccesstodomainnameregistrationdata(SAC051)nolaterthanonehundredthirty-five(135)daysafteritisrequestedbyICANNif:1)theIETFproducesastandard(i.e.,itispublished,atleast,asaProposedStandardRFCasspecifiedinRFC2026);and2)itsimplementationiscommerciallyreasonableinthecontextoftheoveralloperationoftheregistry.
1.1. Theformatofresponsesshallfollowasemi-freetextformatoutlinebelow,followedbyablanklineandalegaldisclaimerspecifyingtherightsofRegistryOperator,andoftheuserqueryingthedatabase.
1.2. Eachdataobjectshallberepresentedasasetofkey/valuepairs,withlinesbeginningwithkeys,followedbyacolonandaspaceasdelimiters,followedbythevalue.
1.3. Forfieldswheremorethanonevalueexists,multiplekey/valuepairswiththesamekeyshallbeallowed(forexampletolistmultiplenameservers).Thefirstkey/valuepairafterablanklineshouldbeconsideredthestartofanewrecord,andshouldbeconsideredasidentifyingthatrecord,andisusedtogroupdata,suchashostnamesandIPaddresses,oradomainnameandregistrantinformation,together.
1.4. Thefieldsspecifiedbelowsetforththeminimumoutputrequirements.RegistryOperatormayoutputdatafieldsinadditiontothosespecifiedbelow,subjecttoapprovalbyICANN,whichapprovalshallnotbeunreasonablywithheld.
1.5. DomainNameData:
1.5.1 Queryformat:whoisEXAMPLE.TLD
1.5.2 Responseformat:
DomainName:EXAMPLE.TLDDomainID:D1234567-TLD
62
WHOISServer:whois.example.tldReferralURL:http://www.example.tldUpdatedDate:2009-05-29T20:13:00ZCreationDate:2000-10-08T00:45:00ZRegistryExpiryDate:2010-10-08T00:44:59ZSponsoringRegistrar:EXAMPLEREGISTRARLLCSponsoringRegistrarIANAID:5555555DomainStatus:clientDeleteProhibitedDomainStatus:clientRenewProhibitedDomainStatus:clientTransferProhibitedDomainStatus:serverUpdateProhibitedRegistrantID:5372808-ERLRegistrantName:EXAMPLEREGISTRANTRegistrantOrganization:EXAMPLEORGANIZATIONRegistrantStreet:123EXAMPLESTREETRegistrantCity:ANYTOWNRegistrantState/Province:APRegistrantPostalCode:A1A1A1RegistrantCountry:EXRegistrantPhone:+1.5555551212RegistrantPhoneExt:1234RegistrantFax:+1.5555551213RegistrantFaxExt:4321RegistrantEmail:[email protected]:5372809-ERLAdminName:EXAMPLEREGISTRANTADMINISTRATIVEAdminOrganization:EXAMPLEREGISTRANTORGANIZATIONAdminStreet:123EXAMPLESTREETAdminCity:ANYTOWNAdminState/Province:APAdminPostalCode:A1A1A1AdminCountry:EXAdminPhone:+1.5555551212AdminPhoneExt:1234AdminFax:+1.5555551213AdminFaxExt:AdminEmail:[email protected]:5372811-ERLTechName:EXAMPLEREGISTRARTECHNICALTechOrganization:EXAMPLEREGISTRARLLCTechStreet:123EXAMPLESTREETTechCity:ANYTOWNTechState/Province:APTechPostalCode:A1A1A1TechCountry:EXTechPhone:+1.1235551234
63
TechPhoneExt:1234TechFax:+1.5555551213TechFaxExt:93TechEmail:[email protected]:NS01.EXAMPLEREGISTRAR.TLDNameServer:NS02.EXAMPLEREGISTRAR.TLDDNSSEC:signedDelegationDNSSEC:unsigned>>>LastupdateofWHOISdatabase:2009-05-29T20:15:00Z<<<
1.6. RegistrarData:
1.6.1 Queryformat:whois“registrarExampleRegistrar,Inc.”
1.6.2 Responseformat:
RegistrarName:ExampleRegistrar,Inc.Street:1234AdmiraltyWayCity:MarinadelReyState/Province:CAPostalCode:90292Country:USPhoneNumber:+1.3105551212FaxNumber:+1.3105551213Email:[email protected]:whois.example-registrar.tldReferralURL:http://www.example-registrar.tldAdminContact:JoeRegistrarPhoneNumber:+1.3105551213FaxNumber:+1.3105551213Email:[email protected]:JaneRegistrarPhoneNumber:+1.3105551214FaxNumber:+1.3105551213Email:[email protected]:JohnGeekPhoneNumber:+1.3105551215FaxNumber:+1.3105551216Email:[email protected]>>>LastupdateofWHOISdatabase:2009-05-29T20:15:00Z<<<
1.7. NameserverData:
1.7.1 Queryformat:whois“nameserver(nameservername)”,orwhois“nameserver(IPAddress).”Forexample:whois“nameserverNS1.EXAMPLE.TLD”.
64
1.7.2 Responseformat:
ServerName:NS1.EXAMPLE.TLDIPAddress:192.0.2.123IPAddress:2001:0DB8::1Registrar:ExampleRegistrar,Inc.WHOISServer:whois.example-registrar.tldReferralURL:http://www.example-registrar.tld>>>LastupdateofWHOISdatabase:2009-05-29T20:15:00Z<<<
1.8. Theformatofthefollowingdatafields:domainstatus,individualandorganizationalnames,address,street,city,state/province,postalcode,country,telephoneandfaxnumbers(theextensionwillbeprovidedasaseparatefieldasshownabove),emailaddresses,dateandtimesshouldconformtothemappingsspecifiedinEPPRFCs5730-5734sothatthedisplayofthisinformation(orvaluesreturninWHOISresponses)canbeuniformlyprocessedandunderstood.
1.9. InordertobecompatiblewithICANN’scommoninterfaceforWHOIS(InterNIC),WHOISoutputshallbeintheformatoutlineabove.
1.10. Searchability.OfferingsearchabilitycapabilitiesontheDirectoryServicesisoptionalbutifofferedbytheRegistryOperatoritshallcomplywiththespecificationdescribedinthissection.
1.10.1 RegistryOperatorwilloffersearchabilityontheweb-basedDirectoryService.
1.10.2 RegistryOperatorwillofferpartialmatchcapabilities,atleast,onthefollowingfields:domainname,contactsandregistrant’sname,andcontactandregistrant’spostaladdress,includingallthesub-fieldsdescribedinEPP(e.g.,street,city,stateorprovince,etc.).
1.10.3 RegistryOperatorwillofferexact-matchcapabilities,atleast,onthefollowingfields:RegistrarID,nameservername,andnameserver’sIPaddress(onlyappliestoIPaddressesstoredbytheregistry,i.e.,gluerecords).
1.10.4 RegistryOperatorwillofferBooleansearchcapabilitiessupporting,atleast,thefollowinglogicaloperatorstojoinasetofsearchcriteria:AND,OR,NOT.
1.10.5 Searchresultswillincludedomainnamesmatchingthesearchcriteria.
1.10.6 RegistryOperatorwill:1)implementappropriatemeasurestoavoidabuseofthisfeature(e.g.,permittingaccessonlytolegitimate
65
authorizedusers);and2)ensurethefeatureisincompliancewithanyapplicableprivacylawsorpolicies.
1.11. RegistryOperatorshallprovidealinkontheprimarywebsitefortheTLD(i.e.,thewebsiteprovidedtoICANNforpublishingontheICANNwebsite)toawebpagedesignatedbyICANNcontainingWHOISpolicyandeducationalmaterials.
2. ZoneFileAccess
2.1. Third-PartyAccess
2.1.1 ZoneFileAccessAgreement.RegistryOperatorwillenterintoanagreementwithanyInternetuser,whichwillallowsuchusertoaccessanInternethostserverorserversdesignatedbyRegistryOperatoranddownloadzonefiledata.Theagreementwillbestandardized,facilitatedandadministeredbyaCentralizedZoneDataAccessProvider,whichmaybeICANNoranICANNdesignee(the“CZDAProvider”).RegistryOperator(optionallythroughtheCZDAProvider)willprovideaccesstozonefiledataperSection2.1.3ofthisSpecificationanddosousingthefileformatdescribedinSection2.1.4ofthisSpecification.Notwithstandingtheforegoing,(a)theCZDAProvidermayrejecttherequestforaccessofanyuserthatdoesnotsatisfythecredentialingrequirementsinSection2.1.2below;(b)RegistryOperatormayrejecttherequestforaccessofanyuserthatdoesnotprovidecorrectorlegitimatecredentialsunderSection2.1.2beloworwhereRegistryOperatorreasonablybelieveswillviolatethetermsofSection2.1.5.below;and,(c)RegistryOperatormayrevokeaccessofanyuserifRegistryOperatorhasevidencetosupportthattheuserhasviolatedthetermsofSection2.1.5below.
2.1.2 CredentialingRequirements.RegistryOperator,throughthefacilitationoftheCZDAProvider,willrequesteachusertoprovideitwithinformationsufficienttocorrectlyidentifyandlocatetheuser.Suchuserinformationwillinclude,withoutlimitation,companyname,contactname,address,telephonenumber,facsimilenumber,emailaddressandIPaddress.
2.1.3 GrantofAccess.EachRegistryOperator(optionallythroughtheCZDAProvider)willprovidetheZoneFileSFTP(orotherRegistrysupported)serviceforanICANN-specifiedandmanagedURL(specifically,<TLD>.zda.icann.orgwhere<TLD>istheTLDforwhichtheregistryisresponsible)fortheusertoaccesstheRegistry’szonedataarchives.RegistryOperatorwillgranttheuseranon-exclusive,nontransferable,limitedrighttoaccessRegistryOperator’s(optionallyCZDAProvider's)ZoneFilehostingserver,andtotransfer
66
acopyofthetop-leveldomainzonefiles,andanyassociatedcryptographicchecksumfilesnomorethanonceper24hourperiodusingSFTP,orotherdatatransportandaccessprotocolsthatmaybeprescribedbyICANN.Foreveryzonefileaccessserver,thezonefilesareinthetop-leveldirectorycalled<zone>.zone.gz,with<zone>.zone.gz.md5and<zone>.zone.gz.sigtoverifydownloads.IftheRegistryOperator(ortheCZDAProvider)alsoprovideshistoricaldata,itwillusethenamingpattern<zone>-yyyymmdd.zone.gz,etc.
2.1.4 FileFormatStandard.RegistryOperator(optionallythroughtheCZDAProvider)willprovidezonefilesusingasubformatofthestandardMasterFileformatasoriginallydefinedinRFC1035,Section5,includingalltherecordspresentintheactualzoneusedinthepublicDNS.Sub-formatisasfollows:
1. Eachrecordmustincludeallfieldsinonelineas:<domain-name><TTL><class><type><RDATA>.
2. ClassandTypemustusethestandardmnemonicsandmustbeinlowercase.
3. TTLmustbepresentasadecimalinteger.
4. Useof\Xand\DDDinsidedomainnamesisallowed.
5. Alldomainnamesmustbeinlowercase.
6. Mustuseexactlyonetabasseparatoroffieldsinsidearecord.
7. Alldomainnamesmustbefullyqualified.
8. No$ORIGINdirectives.
9. Nouseof“@”todenotecurrentorigin.
10. Nouseof“blankdomainnames”atthebeginningofarecordtocontinuetheuseofthedomainnameinthepreviousrecord.
11. No$INCLUDEdirectives.
12. No$TTLdirectives.
13. Nouseofparentheses,e.g.,tocontinuethelistoffieldsinarecordacrossalineboundary.
14. Nouseofcomments.
15. Noblanklines.
67
16. TheSOArecordshouldbepresentatthetopand(duplicatedat)theendofthezonefile.
17. WiththeexceptionoftheSOArecord,alltherecordsinafilemustbeinalphabeticalorder.
18. Onezoneperfile.IfaTLDdividesitsDNSdataintomultiplezones,eachzonegoesintoaseparatefilenamedasabove,withallthefilescombinedusingtarintoafilecalled<tld>.zone.tar.
2.1.5 UseofDatabyUser.RegistryOperatorwillpermitusertousethezonefileforlawfulpurposes;providedthat(a)usertakesallreasonablestepstoprotectagainstunauthorizedaccessto,useof,anddisclosureofthedata,and(b)undernocircumstanceswillRegistryOperatorberequiredorpermittedtoallowusertousethedatato(i)allow,enableorotherwisesupportanymarketingactivitiestoentitiesotherthantheuser’sexistingcustomers,regardlessofthemediumused(suchmediaincludebutarenotlimitedtotransmissionbye-mail,telephone,facsimile,postalmail,SMS,andwirelessalertsofmassunsolicited,commercialadvertisingorsolicitationstoentities),(ii)enablehighvolume,automated,electronicprocessesthatsendqueriesordatatothesystemsofRegistryOperatororanyICANN-accreditedregistrar,or(iii)interrupt,disruptorinterfereinthenormalbusinessoperationsofanyregistrant.
2.1.6 TermofUse.RegistryOperator,throughCZDAProvider,willprovideeachuserwithaccesstothezonefileforaperiodofnotlessthanthree(3)months.RegistryOperatorwillallowuserstorenewtheirGrantofAccess.
2.1.7 NoFeeforAccess.RegistryOperatorwillprovide,andCZDAProviderwillfacilitate,accesstothezonefiletouseratnocost.
2.2. Co-operation
2.2.1 Assistance.RegistryOperatorwillco-operateandprovidereasonableassistancetoICANNandtheCZDAProvidertofacilitateandmaintaintheefficientaccessofzonefiledatabypermittedusersascontemplatedunderthisSchedule.
2.3. ICANNAccess.RegistryOperatorshallprovidebulkaccesstothezonefilesfortheTLDtoICANNoritsdesigneeonacontinuousbasisinthemannerICANNmayreasonablyspecifyfromtimetotime.Accesswillbeprovidedatleastdaily.ZonefileswillincludeSRSdatacommittedascloseaspossibleto00:00:00UTC.
68
2.4. EmergencyOperatorAccess.RegistryOperatorshallprovidebulkaccesstothezonefilesfortheTLDtotheEmergencyOperatorsdesignatedbyICANNonacontinuousbasisinthemannerICANNmayreasonablyspecifyfromtimetotime.
3. BulkRegistrationDataAccesstoICANN
3.1. PeriodicAccesstoThinRegistrationData.InordertoverifyandensuretheoperationalstabilityofRegistryServicesaswellastofacilitatecompliancechecksonaccreditedregistrars,RegistryOperatorwillprovideICANNonaweeklybasis(thedaytobedesignatedbyICANN)withup-to-dateRegistrationDataasspecifiedbelow.Datawillincludedatacommittedasof00:00:00UTConthedayprevioustotheonedesignatedforretrievalbyICANN.
3.1.1 Contents.RegistryOperatorwillprovide,atleast,thefollowingdataforallregistereddomainnames:domainname,domainnamerepositoryobjectid(roid),RegistrarID(IANAID),statuses,lastupdateddate,creationdate,expirationdate,andnameservernames.Forsponsoringregistrars,atleast,itwillprovide:registrarname,registrarid(IANAID),hostnameofregistrarWhoisserver,andURLofregistrar.
3.1.2 Format.ThedatawillbeprovidedintheformatspecifiedinSpecification2forDataEscrow(includingencryption,signing,etc.)butincludingonlythefieldsmentionedintheprevioussection,i.e.,thefilewillonlycontainDomainandRegistrarobjectswiththefieldsmentionedabove.RegistryOperatorhastheoptiontoprovideafulldepositfileinsteadasspecifiedinSpecification2.
3.1.3 Access.RegistryOperatorwillhavethefile(s)readyfordownloadasof00:00:00UTConthedaydesignatedforretrievalbyICANN.Thefile(s)willbemadeavailablefordownloadbySFTP,thoughICANNmayrequestothermeansinthefuture.
3.2. ExceptionalAccesstoThickRegistrationData.Incaseofaregistrarfailure,deaccreditation,courtorder,etc.thatpromptsthetemporaryordefinitivetransferofitsdomainnamestoanotherregistrar,attherequestofICANN,RegistryOperatorwillprovideICANNwithup-to-datedataforthedomainnamesofthelosingregistrar.ThedatawillbeprovidedintheformatspecifiedinSpecification2forDataEscrow.Thefilewillonlycontaindatarelatedtothedomainnamesofthelosingregistrar.RegistryOperatorwillprovidethedataassoonascommerciallypracticable,butinnoeventlaterthanfive(5)calendardaysfollowingICANN’srequest.UnlessotherwiseagreedbyRegistryOperatorandICANN,thefilewillbemadeavailablefor
69
downloadbyICANNinthesamemannerasthedataspecifiedinSection3.1ofthisSpecification.
70
SPECIFICATION5
SCHEDULEOFRESERVEDNAMES
ExcepttotheextentthatICANNotherwiseexpresslyauthorizesinwriting,andsubjecttothetermsandconditionsofthisSpecification,RegistryOperatorshallreservethefollowinglabelsfrominitial(i.e.,otherthanrenewal)registrationwithintheTLD.Ifusingself-allocation,theRegistryOperatormustshowtheregistrationintheRDDS.InthecaseofIDNnames(asindicatedbelow),IDNvariantswillbeidentifiedaccordingtotheregistryoperatorIDNregistrationpolicy,whereapplicable.
1. Example.TheASCIIlabel“EXAMPLE”shallbewithheldfromregistrationorallocatedtoRegistryOperatoratthesecondlevelandatallotherlevelswithintheTLDatwhichRegistryOperatoroffersregistrations(suchsecondlevelandallotherlevelsarecollectivelyreferredtohereinas,“AllLevels”).SuchlabelmaynotbeactivatedintheDNS,andmaynotbereleasedforregistrationtoanypersonorentityotherthanRegistryOperator.UponconclusionofRegistryOperator’sdesignationasoperatoroftheregistryfortheTLD,suchwithheldorallocatedlabelshallbetransferredasspecifiedbyICANN.RegistryOperatormayself-allocateandrenewsuchnamewithoutuseofanICANNaccreditedregistrar,whichwillnotbeconsideredTransactionsforpurposesofSection6.1oftheAgreement.
2. Two-characterlabels.Alltwo-characterASCIIlabelsshallbewithheldfromregistrationorallocatedtoRegistryOperatoratthesecondlevelwithintheTLD.SuchlabelsmaynotbeactivatedintheDNS,andmaynotbereleasedforregistrationtoanypersonorentityotherthanRegistryOperator,providedthatsuchtwo-characterlabelstringsmaybereleasedtotheextentthatRegistryOperatorreachesagreementwiththerelatedgovernmentandcountry-codemanagerofthestringasspecifiedintheISO3166-1alpha-2standard.TheRegistryOperatormayalsoproposethereleaseofthesereservationsbasedonitsimplementationofmeasurestoavoidconfusionwiththecorrespondingcountrycodes,subjecttoapprovalbyICANN.UponconclusionofRegistryOperator’sdesignationasoperatoroftheregistryfortheTLD,allsuchlabelsthatremainwithheldfromregistrationorallocatedtoRegistryOperatorshallbetransferredasspecifiedbyICANN.RegistryOperatormayself-allocateandrenewsuchnameswithoutuseofanICANNaccreditedregistrar,whichwillnotbeconsideredTransactionsforpurposesofSection6.1oftheAgreement.
3. ReservationsforRegistryOperations.
3.1. ThefollowingASCIIlabelsmustbewithheldfromregistrationorallocatedtoRegistryOperatoratAllLevelsforuseinconnectionwiththeoperationoftheregistryfortheTLD:WWW,RDDSandWHOIS.ThefollowingASCIIlabelmustbeallocatedtoRegistryOperatorupondelegationintotherootzoneatAllLevelsforuseinconnectionwiththeoperationoftheregistryfortheTLD:NIC.RegistryOperatormayactivateWWW,RDDSandWHOISintheDNS,
71
butmustactivateNICintheDNS,asnecessaryfortheoperationoftheTLD(inaccordancewiththeprovisionsofExhibitA,theASCIIlabelNICmustbeprovisionedintheDNSasazonecutusingNSresourcerecords).NoneofWWW,RDDS,WHOISorNICmaybereleasedorregisteredtoanyperson(otherthanRegistryOperator)orthirdparty.UponconclusionofRegistryOperator’sdesignationasoperatoroftheregistryfortheTLDallsuchwithheldorallocatednamesshallbetransferredasspecifiedbyICANN.RegistryOperatormayself-allocateandrenewsuchnameswithoutuseofanICANNaccreditedregistrar,whichwillnotbeconsideredTransactionsforpurposesofSection6.1oftheAgreement.SuchdomainsshallbeidentifiedbyRegistrarID9999.
3.1.1 IfExhibitAtotheAgreementspecificallyprovidesthatRegistryOperatormayofferregistrationofIDNs,RegistryOperatormayalsoactivatealanguage-specifictranslationortransliterationoftheterm"NIC"oranabbreviationforthetranslationoftheterm"NetworkInformationCenter"intheDNSinaccordancewithRegistryOperator’sIDNTablesandIDNRegistrationRules.Suchtranslation,transliterationorabbreviationmaybereservedbyRegistryOperatorandusedinadditiontothelabelNICtoprovideanyrequiredregistryfunctions.Fortheavoidanceofdoubt,RegistryOperatorisrequiredtoactivatetheASCIIlabelNICpursuanttoSection3.1ofthisSpecification3.
3.2. RegistryOperatormayactivateintheDNSatAllLevelsuptoonehundred(100)names(plustheirIDNvariants,whereapplicable)necessaryfortheoperationorthepromotionoftheTLD.RegistryOperatormustactastheRegisteredNameHolderofsuchnamesasthattermisdefinedinthethen-currentICANNRegistrarAccreditationAgreement(RAA).TheseactivationswillbeconsideredTransactionsforpurposesofSection6.1oftheAgreement.RegistryOperatormusteither(i)registersuchnamesthroughanICANNaccreditedregistrar;or(ii)self-allocatesuchnamesandwithrespecttothosenamessubmittoandberesponsibletoICANNforcompliancewithICANNConsensusPoliciesandtheobligationssetforthinSubsections3.7.7.1through3.7.7.12ofthethen-currentRAA(oranyotherreplacementclausesettingoutthetermsoftheregistrationagreementbetweenaregistrarandaregisterednameholder).IfRegistryOperatorchoosesoption(ii)above,itshallidentifythesetransactionsusingRegistrarID9998.AtRegistryOperator’sdiscretionandincompliancewithallothertermsofthisAgreement,includingtheRPMssetforthinSpecification7,suchnamesmaybereleasedforregistrationtoanotherpersonorentity.
3.3. RegistryOperatormaywithholdfromregistrationorallocatetoRegistryOperatornames(includingtheirIDNvariants,whereapplicable)atAllLevelsinaccordancewithSection2.6oftheAgreement.SuchnamesmaynotbeactivatedintheDNS,butmaybereleasedforregistrationtoRegistry
72
OperatororanotherpersonorentityatRegistryOperator’sdiscretion,subjecttocompliancewithallthetermsofthisAgreement,includingapplicableRPMssetforthinSpecification7.UponconclusionofRegistryOperator’sdesignationasoperatoroftheregistryfortheTLD,allsuchnamesthatremainwithheldfromregistrationorallocatedtoRegistryOperatorshallbetransferredasspecifiedbyICANN.UponICANN’srequest,RegistryOperatorshallprovidealistingofallnameswithheldorallocatedtoRegistryOperatorpursuanttoSection2.6oftheAgreement.RegistryOperatormayself-allocateandrenewsuchnameswithoutuseofanICANNaccreditedregistrar,whichwillnotbeconsideredTransactionsforpurposesofSection6.1oftheAgreement.
3.4. EffectiveupontheconclusionoftheNo-ActivationPeriodspecifiedinSection6.1ofSpecification6,RegistryOperatorshallallocatethedomainname"icann-sla-monitoring.<tld>"totheICANNtestingregistrar(assuchregistrarisdescribedinSection8.2ofSpecification10).IfsuchdomainnameisnotavailableforregistrationintheTLDorisotherwiseinconsistentwiththeregistrationpoliciesoftheTLD,RegistryOperatormayallocateadifferentdomainnametotheICANNtestingregistrarinconsultationwithICANN.TheallocationofanysuchalternativedomainnamewillbecommunicatedtoICANNfollowingsuchconsultation.Theallocationofthedomainname"icann-sla-monitoring.<tld>"totheICANNtestingregistrarwillnot(i)beconsideredaTransactionforpurposesofSection6.1oftheAgreement,(ii)counttowardstheonehundreddomainnamesavailabletoRegistryOperatorunderSection3.2ofthisSpecification5,or(iii)adverselyaffectRegistryOperator’squalificationasa.BRANDTLDpursuanttoSpecification13(.BRANDTLDProvisions)hereto(asapplicable).
4. CountryandTerritoryNames.Thecountryandterritorynames(includingtheirIDNvariants,whereapplicable)containedinthefollowinginternationallyrecognizedlistsshallbewithheldfromregistrationorallocatedtoRegistryOperatoratAllLevels:
4.1. theshortform(inEnglish)ofallcountryandterritorynamescontainedontheISO3166-1list,asupdatedfromtimetotime,includingtheEuropeanUnion,whichisexceptionallyreservedontheISO3166-1list,anditsscopeextendedinAugust1999toanyapplicationneedingtorepresentthenameEuropeanUnion<http://www.iso.org/iso/support/country_codes/iso_3166_code_lists/iso-3166-1_decoding_table.htm>;
4.2. theUnitedNationsGroupofExpertsonGeographicalNames,TechnicalReferenceManualfortheStandardizationofGeographicalNames,PartIIINamesofCountriesoftheWorld;and
73
4.3. thelistofUnitedNationsmemberstatesin6officialUnitedNationslanguagespreparedbytheWorkingGrouponCountryNamesoftheUnitedNationsConferenceontheStandardizationofGeographicalNames;
provided,thatthereservationofspecificcountryandterritorynames(includingtheirIDNvariantsaccordingtotheregistryoperatorIDNregistrationpolicy,whereapplicable)maybereleasedtotheextentthatRegistryOperatorreachesagreementwiththeapplicablegovernment(s).RegistryOperatormustnotactivatesuchnamesintheDNS;provided,thatRegistryOperatormayproposethereleaseofthesereservations,subjecttoreviewbyICANN’sGovernmentalAdvisoryCommitteeandapprovalbyICANN.UponconclusionofRegistryOperator’sdesignationasoperatoroftheregistryfortheTLD,allsuchnamesthatremainwithheldfromregistrationorallocatedtoRegistryOperatorshallbetransferredasspecifiedbyICANN.RegistryOperatormayself-allocateandrenewsuchnameswithoutuseofanICANNaccreditedregistrar,whichwillnotbeconsideredTransactionsforpurposesofSection6.1oftheAgreement.
5. InternationalOlympicCommittee;InternationalRedCrossandRedCrescentMovement.AsinstructedfromtimetotimebyICANN,thenames(includingtheirIDNvariants,whereapplicable)relatingtotheInternationalOlympicCommittee,InternationalRedCrossandRedCrescentMovementlistedathttp://www.icann.org/en/resources/registries/reservedshallbewithheldfromregistrationorallocatedtoRegistryOperatoratthesecondlevelwithintheTLD.AdditionalInternationalOlympicCommittee,InternationalRedCrossandRedCrescentMovementnames(includingtheirIDNvariants)maybeaddedtothelistuponten(10)calendardaysnoticefromICANNtoRegistryOperator.SuchnamesmaynotbeactivatedintheDNS,andmaynotbereleasedforregistrationtoanypersonorentityotherthanRegistryOperator.UponconclusionofRegistryOperator’sdesignationasoperatoroftheregistryfortheTLD,allsuchnameswithheldfromregistrationorallocatedtoRegistryOperatorshallbetransferredasspecifiedbyICANN.RegistryOperatormayself-allocateandrenewsuchnameswithoutuseofanICANNaccreditedregistrar,whichwillnotbeconsideredTransactionsforpurposesofSection6.1oftheAgreement.
6. IntergovernmentalOrganizations.AsinstructedfromtimetotimebyICANN,RegistryOperatorwillimplementtheprotectionsmechanismdeterminedbytheICANNBoardofDirectorsrelatingtotheprotectionofidentifiersforIntergovernmentalOrganizations.AlistofreservednamesforthisSection6isavailableathttp://www.icann.org/en/resources/registries/reserved.Additionalnames(includingtheirIDNvariants)maybeaddedtothelistuponten(10)calendardaysnoticefromICANNtoRegistryOperator.AnysuchprotectedidentifiersforIntergovernmentalOrganizationsmaynotbeactivatedintheDNS,andmaynotbereleasedforregistrationtoanypersonorentityotherthanRegistryOperator.UponconclusionofRegistryOperator’sdesignationasoperatoroftheregistryfortheTLD,allsuchprotectedidentifiersshallbetransferredasspecifiedbyICANN.RegistryOperatormayself-allocateandrenewsuchnameswithoutuse
74
ofanICANNaccreditedregistrar,whichwillnotbeconsideredTransactionsforpurposesofSection6.1oftheAgreement.
75
SPECIFICATION6
REGISTRYINTEROPERABILITYANDCONTINUITYSPECIFICATIONS
1. StandardsCompliance
1.1. DNS.RegistryOperatorshallcomplywithrelevantexistingRFCsandthosepublishedinthefuturebytheInternetEngineeringTaskForce(IETF),includingallsuccessorstandards,modificationsoradditionstheretorelatingtotheDNSandnameserveroperationsincludingwithoutlimitationRFCs1034,1035,1123,1982,2181,2182,3226,3596,3597,4343,5966and6891.DNSlabelsmayonlyincludehyphensinthethirdandfourthpositioniftheyrepresentvalidIDNs(asspecifiedabove)intheirASCIIencoding(e.g.,“xn--ndk061n”).
1.2. EPP.RegistryOperatorshallcomplywithrelevantexistingRFCsandthosepublishedinthefuturebytheInternetEngineeringTaskForce(IETF)includingallsuccessorstandards,modificationsoradditionstheretorelatingtotheprovisioningandmanagementofdomainnamesusingtheExtensibleProvisioningProtocol(EPP)inconformancewithRFCs5910,5730,5731,5732(ifusinghostobjects),5733and5734.IfRegistryOperatorimplementsRegistryGracePeriod(RGP),itwillcomplywithRFC3915anditssuccessors.IfRegistryOperatorrequirestheuseoffunctionalityoutsidethebaseEPPRFCs,RegistryOperatormustdocumentEPPextensionsinInternet-DraftformatfollowingtheguidelinesdescribedinRFC3735.RegistryOperatorwillprovideandupdatetherelevantdocumentationofalltheEPPObjectsandExtensionssupportedtoICANNpriortodeployment.
1.3. DNSSEC.RegistryOperatorshallsignitsTLDzonefilesimplementingDomainNameSystemSecurityExtensions(“DNSSEC”).Fortheabsenceofdoubt,RegistryOperatorshallsignthezonefileof<TLD>andzonefilesusedforin-bailiwickgluefortheTLD’sDNSservers.DuringtheTerm,RegistryOperatorshallcomplywithRFCs4033,4034,4035,4509andtheirsuccessors,andfollowthebestpracticesdescribedinRFC6781anditssuccessors.IfRegistryOperatorimplementsHashedAuthenticatedDenialofExistenceforDNSSecurityExtensions,itshallcomplywithRFC5155anditssuccessors.RegistryOperatorshallacceptpublic-keymaterialfromchilddomainnamesinasecuremanneraccordingtoindustrybestpractices.RegistryshallalsopublishinitswebsitetheDNSSECPracticeStatements(DPS)describingcriticalsecuritycontrolsandproceduresforkeymaterialstorage,accessandusageforitsownkeysandsecureacceptanceofregistrants’public-keymaterial.RegistryOperatorshallpublishitsDPSfollowingtheformatdescribedinRFC6841.DNSSECvalidationmustbeactiveandusetheIANADNSRootKeySigningKeyset(availableathttps://www.iana.org/dnssec/files)asatrustanchorforRegistryOperator’sRegistryServicesmakinguseofdataobtainedviaDNSresponses.
76
1.4. IDN.IftheRegistryOperatoroffersInternationalizedDomainNames(“IDNs”),itshallcomplywithRFCs5890,5891,5892,5893andtheirsuccessors.RegistryOperatorshallcomplywiththeICANNIDNGuidelinesat<http://www.icann.org/en/topics/idn/implementation-guidelines.htm>,astheymaybeamended,modified,orsupersededfromtimetotime.RegistryOperatorshallpublishandkeepupdateditsIDNTablesandIDNRegistrationRulesintheIANARepositoryofIDNPractices.
1.5. IPv6.RegistryOperatorshallbeabletoacceptIPv6addressesasgluerecordsinitsRegistrySystemandpublishthemintheDNS.RegistryOperatorshallofferpublicIPv6transportfor,atleast,twooftheRegistry’snameserverslistedintherootzonewiththecorrespondingIPv6addressesregisteredwithIANA.RegistryOperatorshouldfollow“DNSIPv6TransportOperationalGuidelines”asdescribedinBCP91andtherecommendationsandconsiderationsdescribedinRFC4472.RegistryOperatorshallofferpublicIPv6transportforitsRegistrationDataPublicationServicesasdefinedinSpecification4ofthisAgreement;e.g.,Whois(RFC3912),WebbasedWhois.RegistryOperatorshallofferpublicIPv6transportforitsSharedRegistrationSystem(SRS)toanyRegistrar,nolaterthansix(6)monthsafterreceivingthefirstrequestinwritingfromagTLDaccreditedRegistrarwillingtooperatewiththeSRSoverIPv6.
1.6. IANARootzoneDatabase.InordertoensurethatauthoritativeinformationabouttheTLDremainspubliclyavailable,RegistryOperatorshallsubmitachangerequesttotheIANAfunctionsoperatorupdatinganyoutdatedorinaccurateDNSorWHOISrecordsoftheTLD.RegistryOperatorshallusecommerciallyreasonableeffortstosubmitanysuchchangerequestnolaterthanseven(7)calendardaysafterthedateanysuchDNSorWHOISrecordsbecomesoutdatedorinaccurate.RegistryOperatormustsubmitallchangerequestsinaccordancewiththeproceduressetforthat<http://www.iana.org/domains/root>.
1.7. NetworkIngressFiltering.RegistryOperatorshallimplementnetworkingressfilteringchecksforitsRegistryServicesasdescribedinBCP38andBCP84,whichICANNwillalsoimplement.
2. RegistryServices
2.1. RegistryServices.“RegistryServices”are,forpurposesoftheAgreement,definedasthefollowing:(a)thoseservicesthatareoperationsoftheregistrycriticaltothefollowingtasks:thereceiptofdatafromregistrarsconcerningregistrationsofdomainnamesandnameservers;provisiontoregistrarsofstatusinformationrelatingtothezoneserversfortheTLD;disseminationofTLDzonefiles;operationoftheregistryDNSservers;anddisseminationofcontactandotherinformationconcerningdomainnameserverregistrationsintheTLDasrequiredbythisAgreement;(b)other
77
productsorservicesthattheRegistryOperatorisrequiredtoprovidebecauseoftheestablishmentofaConsensusPolicyasdefinedinSpecification1;(c)anyotherproductsorservicesthatonlyaregistryoperatoriscapableofproviding,byreasonofitsdesignationastheregistryoperator;and(d)materialchangestoanyRegistryServicewithinthescopeof(a),(b)or(c)above.
2.2. WildcardProhibition.Fordomainnameswhichareeithernotregistered,ortheregistranthasnotsuppliedvalidrecordssuchasNSrecordsforlistingintheDNSzonefile,ortheirstatusdoesnotallowthemtobepublishedintheDNS,theuseofDNSwildcardResourceRecordsasdescribedinRFCs1034and4592oranyothermethodortechnologyforsynthesizingDNSResourcesRecordsorusingredirectionwithintheDNSbytheRegistryisprohibited.Whenqueriedforsuchdomainnamestheauthoritativenameserversmustreturna“NameError”response(alsoknownasNXDOMAIN),RCODE3asdescribedinRFC1035andrelatedRFCs.ThisprovisionappliesforallDNSzonefilesatalllevelsintheDNStreeforwhichtheRegistryOperator(oranaffiliateengagedinprovidingRegistrationServices)maintainsdata,arrangesforsuchmaintenance,orderivesrevenuefromsuchmaintenance.
3. RegistryContinuity
3.1. HighAvailability.RegistryOperatorwillconductitsoperationsusingnetworkandgeographicallydiverse,redundantservers(includingnetwork-levelredundancy,end-nodelevelredundancyandtheimplementationofaloadbalancingschemewhereapplicable)toensurecontinuedoperationinthecaseoftechnicalfailure(widespreadorlocal),oranextraordinaryoccurrenceorcircumstancebeyondthecontroloftheRegistryOperator.RegistryOperator’semergencyoperationsdepartmentshallbeavailableatalltimestorespondtoextraordinaryoccurrences.
3.2. ExtraordinaryEvent.RegistryOperatorwillusecommerciallyreasonableeffortstorestorethecriticalfunctionsoftheregistrywithintwenty-four(24)hoursaftertheterminationofanextraordinaryeventbeyondthecontroloftheRegistryOperatorandrestorefullsystemfunctionalitywithinamaximumofforty-eight(48)hoursfollowingsuchevent,dependingonthetypeofcriticalfunctioninvolved.Outagesduetosuchaneventwillnotbeconsideredalackofserviceavailability.
3.3. BusinessContinuity.RegistryOperatorshallmaintainabusinesscontinuityplan,whichwillprovideforthemaintenanceofRegistryServicesintheeventofanextraordinaryeventbeyondthecontroloftheRegistryOperatororbusinessfailureofRegistryOperator,andmayincludethedesignationofaRegistryServicescontinuityprovider.IfsuchplanincludesthedesignationofaRegistryServicescontinuityprovider,RegistryOperatorshallprovide
78
thenameandcontactinformationforsuchRegistryServicescontinuityprovidertoICANN.InthecaseofanextraordinaryeventbeyondthecontroloftheRegistryOperatorwheretheRegistryOperatorcannotbecontacted,RegistryOperatorconsentsthatICANNmaycontactthedesignatedRegistryServicescontinuityprovider,ifoneexists.RegistryOperatorshallconductRegistryServicesContinuitytestingatleastonceperyear.
4. AbuseMitigation
4.1. AbuseContact.RegistryOperatorshallprovidetoICANNandpublishonitswebsiteitsaccuratecontactdetailsincludingavalidemailandmailingaddressaswellasaprimarycontactforhandlinginquiriesrelatedtomaliciousconductintheTLD,andwillprovideICANNwithpromptnoticeofanychangestosuchcontactdetails.
4.2. MaliciousUseofOrphanGlueRecords.RegistryOperatorshalltakeactiontoremoveorphangluerecords(asdefinedathttp://www.icann.org/en/committees/security/sac048.pdf)whenprovidedwithevidenceinwrittenformthatsuchrecordsarepresentinconnectionwithmaliciousconduct.
5. SupportedInitialandRenewalRegistrationPeriods
5.1. InitialRegistrationPeriods.Initialregistrationsofregisterednamesmaybemadeintheregistryinone(1)yearincrementsforuptoamaximumoften(10)years.Fortheavoidanceofdoubt,initialregistrationsofregisterednamesmaynotexceedten(10)years.
5.2. RenewalPeriods.Renewalofregisterednamesmaybemadeinone(1)yearincrementsforuptoamaximumoften(10)years.Fortheavoidanceofdoubt,renewalofregisterednamesmaynotextendtheirregistrationperiodbeyondten(10)yearsfromthetimeoftherenewal.
6. NameCollisionOccurrenceManagement
6.1. No-ActivationPeriod.RegistryOperatorshallnotactivateanynamesintheDNSzonefortheRegistryTLD(exceptfor"NIC")untilatleast120calendardaysaftertheeffectivedateofthisagreement.RegistryOperatormayallocatenames(subjecttosubsection6.2below)duringthisperiodonlyifRegistryOperatorcausesregistrantstobeclearlyinformedoftheinabilitytoactivatenamesuntiltheNo-ActivationPeriodends.
6.2. NameCollisionOccurrenceAssessment
6.2.1 RegistryOperatorshallnotactivateanynamesintheDNSzonefortheRegistryTLDexceptincompliancewithaNameCollisionOccurrenceAssessmentprovidedbyICANNregardingtheRegistryTLD.Registry
79
Operatorwilleither(A)implementthemitigationmeasuresdescribedinitsNameCollisionOccurrenceAssessmentbeforeactivatinganysecond-leveldomainname,or(B)blockthosesecond-leveldomainnamesforwhichthemitigationmeasuresasdescribedintheNameCollisionOccurrenceAssessmenthavenotbeenimplementedandproceedwithactivatingnamesthatarenotlistedintheAssessment.
6.2.2 Notwithstandingsubsection6.2.1,RegistryOperatormayproceedwithactivationofnamesintheDNSzonewithoutimplementationofthemeasuressetforthinSection6.2.1onlyif(A)ICANNdeterminesthattheRegistryTLDiseligibleforthisalternativepathtoactivationofnames;and(B)RegistryOperatorblocksallsecond-leveldomainnamesidentifiedbyICANNandsetforthat<http://newgtlds.icann.org/en/announcements-and-media/announcement-2-17nov13-en>assuchlistmaybemodifiedbyICANNfromtimetotime.RegistryOperatormayactivatenamespursuanttothissubsectionandlateractivatenamespursuanttosubsection6.2.1.
6.2.3 ThesetsofnamessubjecttomitigationorblockingpursuanttoSections6.2.1and6.2.2willbebasedonICANNanalysisofDNSinformationincluding"DayintheLifeoftheInternet"datamaintainedbytheDNSOperations,Analysis,andResearchCenter(DNS-OARC)<https://www.dns-oarc.net/oarc/data/ditl>.
6.2.4 RegistryOperatormayparticipateinthedevelopmentbytheICANNcommunityofaprocessfordeterminingwhetherandhowtheseblockednamesmaybereleased.
6.2.5 IfICANNdeterminesthattheTLDisineligibleforthealternativepathtoactivationofnames,ICANNmayelectnottodelegatetheTLDpendingcompletionofthefinalNameCollisionOccurrenceAssessmentfortheTLD,andRegistryOperator’scompletionofallrequiredmitigationmeasures.RegistryOperatorunderstandsthatthemitigationmeasuresrequiredbyICANNasaconditiontoactivationofnamesintheDNSzonefortheTLDmayinclude,withoutlimitation,mitigationmeasuressuchasthosedescribedinSection3.2oftheNewgTLDNameCollisionOccurrenceManagementPlanapprovedbytheICANNBoardNewgTLDProgramCommittee(NGPC)on7October2013asfoundat<http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-annex-1-07oct13-en.pdf>.
80
6.3. NameCollisionReportHandling
6.3.1 DuringthefirsttwoyearsafterdelegationoftheTLD,RegistryOperator’semergencyoperationsdepartmentshallbeavailabletoreceivereports,relayedbyICANN,allegingdemonstrablysevereharmfromcollisionswithoverlappinguseofthenamesoutsideoftheauthoritativeDNS.
6.3.2 RegistryOperatorshalldevelopaninternalprocessforhandlinginanexpeditedmannerreportsreceivedpursuanttosubsection6.3.1underwhichRegistryOperatormay,totheextentnecessaryandappropriate,removearecentlyactivatednamefromtheTLDzoneforaperiodofuptotwoyearsinordertoallowtheaffectedpartytomakechangestoitssystems.
81
SPECIFICATION7
MINIMUMREQUIREMENTSFORRIGHTSPROTECTIONMECHANISMS
1. RightsProtectionMechanisms.RegistryOperatorshallimplementandadheretotherightsprotectionmechanisms(“RPMs”)specifiedinthisSpecification.InadditiontosuchRPMs,RegistryOperatormaydevelopandimplementadditionalRPMsthatdiscourageorpreventregistrationofdomainnamesthatviolateorabuseanotherparty’slegalrights.RegistryOperatorwillincludeallRPMsrequiredbythisSpecification7andanyadditionalRPMsdevelopedandimplementedbyRegistryOperatorintheRegistry-RegistrarAgreemententeredintobyICANN-accreditedregistrarsauthorizedtoregisternamesintheTLD.RegistryOperatorshallimplementinaccordancewithrequirementssetforththereineachofthemandatoryRPMssetforthintheTrademarkClearinghouseasofthedatehereof,aspostedathttp://www.icann.org/en/resources/registries/tmch-requirements(the“TrademarkClearinghouseRequirements”),whichmayberevisedinimmaterialrespectsbyICANNfromtimetotime.RegistryOperatorshallnotmandatethatanyownerofapplicableintellectualpropertyrightsuseanyothertrademarkinformationaggregation,notification,orvalidationserviceinadditiontoorinsteadoftheICANN-designatedTrademarkClearinghouse.IfthereisaconflictbetweenthetermsandconditionsofthisAgreementandtheTrademarkClearinghouseRequirements,thetermsandconditionsofthisAgreementshallcontrol.RegistryOperatormustenterintoabindingandenforceableRegistry-RegistrarAgreementwithatleastoneICANNaccreditedregistrarauthorizingsuchregistrar(s)toregisterdomainnamesintheTLDasfollows:
a. ifRegistryOperatorconductsaQualifiedLaunchProgramorisauthorizedbyICANNtoconductanApprovedLaunchProgram(asthosetermsaredefinedintheTrademarkClearinghouseRequirements),RegistryOperatormustenterintoabindingandenforceableRegistry-RegistrarAgreementwithatleastoneICANNaccreditedregistrarpriortoallocatinganydomainnamespursuanttosuchQualifiedLaunchProgramorApprovedLaunchProgram,asapplicable;
b. ifRegistryOperatordoesnotconductaQualifiedLaunchProgramorisnotauthorizedbyICANNtoconductanApprovedLaunchProgram,RegistryOperatormustenterintoabindingandenforceableRegistry-RegistrarAgreementwithatleastoneICANNaccreditedregistraratleastthirty(30)calendardayspriortotheexpirationdateoftheSunrisePeriod(asdefinedintheTrademarkClearinghouseRequirements)fortheTLD;or
c. ifthisAgreementcontainsaSpecification13,RegistryOperatormustenterintoabindingandenforceableRegistry-RegistrarAgreementwithatleastoneICANNaccreditedregistrarpriortotheClaimsCommencementDate(asdefinedinSpecification13).
82
NothinginthisSpecification7shalllimitorwaiveanyotherobligationsorrequirementsofthisAgreementapplicabletoRegistryOperator,includingSection2.9(a)andSpecification9.
2. DisputeResolutionMechanisms.RegistryOperatorwillcomplywiththefollowingdisputeresolutionmechanismsastheymayberevisedfromtimetotime:
a. theTrademarkPost-DelegationDisputeResolutionProcedure(PDDRP)andtheRegistrationRestrictionDisputeResolutionProcedure(RRDRP)adoptedbyICANN(postedathttp://www.icann.org/en/resources/registries/pddrpandhttp://www.icann.org/en/resources/registries/rrdrp,respectively).RegistryOperatoragreestoimplementandadheretoanyremediesICANNimposes(whichmayincludeanyreasonableremedy,includingfortheavoidanceofdoubt,theterminationoftheRegistryAgreementpursuanttoSection4.3(e)oftheAgreement)followingadeterminationbyanyPDDRPorRRDRPpanelandtobeboundbyanysuchdetermination;and
b. theUniformRapidSuspensionsystem(“URS”)adoptedbyICANN(postedathttp://www.icann.org/en/resources/registries/urs),includingtheimplementationofdeterminationsissuedbyURSexaminers.
83
SPECIFICATION8
CONTINUEDOPERATIONSINSTRUMENT
1. TheContinuedOperationsInstrumentshall(a)provideforsufficientfinancialresourcestoensurethecontinuedoperationofthecriticalregistryfunctionsrelatedtotheTLDsetforthinSection6ofSpecification10tothisAgreementforaperiodofthree(3)yearsfollowinganyterminationofthisAgreementonorpriortothefifthanniversaryoftheEffectiveDateorforaperiodofone(1)yearfollowinganyterminationofthisAgreementafterthefifthanniversaryoftheEffectiveDatebutpriortooronthesixth(6th)anniversaryoftheEffectiveDate,and(b)beintheformofeither(i)anirrevocablestandbyletterofcredit,or(ii)anirrevocablecashescrowdeposit,eachmeetingtherequirementssetforthinitem50(b)ofAttachmenttoModule2–EvaluationQuestionsandCriteria–ofthegTLDApplicantGuidebook,aspublishedandsupplementedbyICANNpriortothedatehereof(whichisherebyincorporatedbyreferenceintothisSpecification8).RegistryOperatorshalluseitsbesteffortstotakeallactionsnecessaryoradvisabletomaintainineffecttheContinuedOperationsInstrumentforaperiodofsix(6)yearsfromtheEffectiveDate,andtomaintainICANNasathirdpartybeneficiarythereof.IfRegistryOperatorelectstoobtainanirrevocablestandbyletterofcreditbutthetermrequiredaboveisunobtainable,RegistryOperatormayobtainaletterofcreditwithaone-yeartermandan“evergreenprovision,”providingforannualextensions,withoutamendment,foranindefinitenumberofadditionalperiodsuntiltheissuingbankinformsICANNofitsfinalexpirationoruntilICANNreleasestheletterofcreditasevidencedinwriting,iftheletterofcreditotherwisemeetstherequirementssetforthinitem50(b)ofAttachmenttoModule2–EvaluationQuestionsandCriteria–ofthegTLDApplicantGuidebook,aspublishedandsupplementedbyICANNpriortothedatehereof;provided,however,thatiftheissuingbankinformsICANNoftheexpirationofsuchletterofcreditpriortothesixth(6th)anniversaryoftheEffectiveDate,suchletterofcreditmustprovidethatICANNisentitledtodrawthefundssecuredbytheletterofcreditpriortosuchexpiration.TheletterofcreditmustrequiretheissuingbanktogiveICANNatleastthirty(30)calendardays’noticeofanysuchexpirationornon-renewal.Iftheletterofcreditexpiresoristerminatedatanytimepriortothesixth(6th)anniversaryoftheEffectiveDate,RegistryOperatorwillberequiredtoobtainareplacementContinuedOperationsInstrument.ICANNmaydrawthefundsundertheoriginalletterofcredit,ifthereplacementContinuedOperationsInstrumentisnotinplacepriortotheexpirationoftheoriginalletterofcredit.RegistryOperatorshallprovidetoICANNcopiesofallfinaldocumentsrelatingtotheContinuedOperationsInstrumentandshallkeepICANNreasonablyinformedofmaterialdevelopmentsrelatingtotheContinuedOperationsInstrument.RegistryOperatorshallnotagreeto,orpermit,anyamendmentof,orwaiverunder,theContinuedOperationsInstrumentorotherdocumentationrelatingtheretowithoutthepriorwrittenconsentofICANN(suchconsentnottobeunreasonablywithheld).
84
2. If,notwithstandingtheuseofbesteffortsbyRegistryOperatortosatisfyitsobligationsundertheprecedingparagraph,theContinuedOperationsInstrumentexpiresoristerminatedbyanotherpartythereto,inwholeorinpart,foranyreason,priortothesixthanniversaryoftheEffectiveDate,RegistryOperatorshallpromptly(i)notifyICANNofsuchexpirationorterminationandthereasonsthereforand(ii)arrangeforanalternativeinstrumentthatprovidesforsufficientfinancialresourcestoensurethecontinuedoperationofthecriticalregistryfunctionsrelatedtotheTLDsetforthinSection6ofSpecification10tothisAgreementforaperiodofthree(3)yearsfollowinganyterminationofthisAgreementonorpriortothefifthanniversaryoftheEffectiveDateorforaperiodofone(1)yearfollowinganyterminationofthisAgreementafterthefifthanniversaryoftheEffectiveDatebutpriortooronthesixth(6)anniversaryoftheEffectiveDate(an“AlternativeInstrument”).AnysuchAlternativeInstrumentshallbeontermsnolessfavorabletoICANNthantheContinuedOperationsInstrumentandshallotherwisebeinformandsubstancereasonablyacceptabletoICANN.
3. NotwithstandinganythingtothecontrarycontainedinthisSpecification8,atanytime,RegistryOperatormayreplacetheContinuedOperationsInstrumentwithanAlternativeInstrumentthat(i)providesforsufficientfinancialresourcestoensurethecontinuedoperationofthecriticalregistryfunctionsrelatedtotheTLDsetforthinSection6ofSpecification10tothisAgreementforaperiodofthree(3)yearsfollowinganyterminationofthisAgreementonorpriortothefifthanniversaryoftheEffectiveDateorforaperiodone(1)yearfollowinganyterminationofthisAgreementafterthefifthanniversaryoftheEffectiveDatebutpriortooronthesixth(6)anniversaryoftheEffectiveDate,and(ii)containstermsnolessfavorabletoICANNthantheContinuedOperationsInstrumentandisotherwiseinformandsubstancereasonablyacceptabletoICANN.IntheeventRegistryOperatorreplacestheContinuedOperationsInstrumenteitherpursuanttoparagraph2orthisparagraph3,thetermsofthisSpecification8shallnolongerapplywithrespecttotheoriginalContinuingOperationsInstrument,butshallthereafterapplywithrespecttosuchAlternativeInstrument(s),andsuchinstrumentshallthereafterbeconsideredtheContinuedOperationsInstrumentforpurposesofthisAgreement.
85
SPECIFICATION9
REGISTRYOPERATORCODEOFCONDUCT
1. InconnectionwiththeoperationoftheregistryfortheTLD,RegistryOperatorwillnot,andwillnotallowanyparent,subsidiary,Affiliate,subcontractororotherrelatedentity,totheextentsuchpartyisengagedintheprovisionofRegistryServiceswithrespecttotheTLD(each,a“RegistryRelatedParty”),to:
a. directlyorindirectlyshowanypreferenceorprovideanyspecialconsiderationtoanyregistrarwithrespecttooperationalaccesstoregistrysystemsandrelatedregistryservices,unlesscomparableopportunitiestoqualifyforsuchpreferencesorconsiderationsaremadeavailabletoallregistrarsonsubstantiallysimilartermsandsubjecttosubstantiallysimilarconditions;
b. registerdomainnamesinitsownright,exceptfornamesregisteredthroughanICANNaccreditedregistrar;provided,however,thatRegistryOperatormay(a)reservenamesfromregistrationpursuanttoSection2.6oftheAgreementand(b)maywithholdfromregistrationorallocatetoRegistryOperatoruptoonehundred(100)namespursuanttoSection3.2ofSpecification5;
c. registernamesintheTLDorsub-domainsoftheTLDbaseduponproprietaryaccesstoinformationaboutsearchesorresolutionrequestsbyconsumersfordomainnamesnotyetregistered(commonlyknownas,“front-running”);or
d. allowanyAffiliatedregistrartodisclosePersonalDataaboutregistrantstoRegistryOperatororanyRegistryRelatedParty,exceptasreasonablynecessaryforthemanagementandoperationsoftheTLD,unlessallunrelatedthirdparties(includingotherregistryoperators)aregivenequivalentaccesstosuchuserdataonsubstantiallysimilartermsandsubjecttosubstantiallysimilarconditions.
2. IfRegistryOperatororaRegistryRelatedPartyalsooperatesasaproviderofregistrarorregistrar-resellerservices,RegistryOperatorwill,orwillcausesuchRegistryRelatedPartyto,ensurethatsuchservicesareofferedthroughalegalentityseparatefromRegistryOperator,andmaintainseparatebooksofaccountswithrespecttoitsregistrarorregistrar-reselleroperations.
3. IfRegistryOperatororaRegistryRelatedPartyalsooperatesasaproviderofregistrarorregistrar-resellerservices,RegistryOperatorwillconductinternalreviewsatleastoncepercalendaryeartoensurecompliancewiththisCodeofConduct.Withintwenty(20)calendardaysfollowingtheendofeachcalendaryear,RegistryOperatorwillprovidetheresultsoftheinternalreview,alongwithacertificationexecutedbyanexecutiveofficerofRegistryOperatorcertifyingasto
86
RegistryOperator’scompliancewiththisCodeofConduct,viaemailtoanaddresstobeprovidedbyICANN.(ICANNmayspecifyinthefuturetheformandcontentsofsuchreportsorthatthereportsbedeliveredbyotherreasonablemeans.)RegistryOperatoragreesthatICANNmaypubliclypostsuchresultsandcertification;provided,however,ICANNshallnotdiscloseConfidentialInformationcontainedinsuchresultsexceptinaccordancewithSection7.15oftheAgreement.
4. Nothingsetforthhereinshall:(i)limitICANNfromconductinginvestigationsofclaimsofRegistryOperator’snon-compliancewiththisCodeofConduct;or(ii)providegroundsforRegistryOperatortorefusetocooperatewithICANNinvestigationsofclaimsofRegistryOperator’snon-compliancewiththisCodeofConduct.
5. NothingsetforthhereinshalllimittheabilityofRegistryOperatororanyRegistryRelatedParty,toenterintoarms-lengthtransactionsintheordinarycourseofbusinesswitharegistrarorresellerwithrespecttoproductsandservicesunrelatedinallrespectstotheTLD.
6. RegistryOperatormayrequestanexemptiontothisCodeofConduct,andsuchexemptionmaybegrantedbyICANNinICANN’sreasonablediscretion,ifRegistryOperatordemonstratestoICANN’sreasonablesatisfactionthat(i)alldomainnameregistrationsintheTLDareregisteredto,andmaintainedby,RegistryOperatorfortheexclusiveuseofRegistryOperatororitsAffiliates,(ii)RegistryOperatordoesnotsell,distributeortransfercontroloruseofanyregistrationsintheTLDtoanythirdpartythatisnotanAffiliateofRegistryOperator,and(iii)applicationofthisCodeofConducttotheTLDisnotnecessarytoprotectthepublicinterest.
87
SPECIFICATION10
REGISTRYPERFORMANCESPECIFICATIONS
1. Definitions
1.1. DNS.ReferstotheDomainNameSystemasspecifiedinRFCs1034,1035,andrelatedRFCs.
1.2. DNSSECproperresolution.ThereisavalidDNSSECchainoftrustfromtheroottrustanchortoaparticulardomainname,e.g.,aTLD,adomainnameregisteredunderaTLD,etc.
1.3. EPP.ReferstotheExtensibleProvisioningProtocolasspecifiedinRFC5730andrelatedRFCs.
1.4. IPaddress.ReferstoIPv4orIPv6addresseswithoutmakinganydistinctionbetweenthetwo.Whenthereisneedtomakeadistinction,IPv4orIPv6isused.
1.5. Probes.Networkhostsusedtoperform(DNS,EPP,etc.)tests(seebelow)thatarelocatedatvariousgloballocations.
1.6. RDDS.RegistrationDataDirectoryServicesreferstothecollectiveofWHOISandWeb-basedWHOISservicesasdefinedinSpecification4ofthisAgreement.
1.7. RTT.Round-TripTimeorRTTreferstothetimemeasuredfromthesendingofthefirstbitofthefirstpacketofthesequenceofpacketsneededtomakearequestuntilthereceptionofthelastbitofthelastpacketofthesequenceneededtoreceivetheresponse.Iftheclientdoesnotreceivethewholesequenceofpacketsneededtoconsidertheresponseasreceived,therequestwillbeconsideredunanswered.
1.8. SLR.ServiceLevelRequirementisthelevelofserviceexpectedforacertainparameterbeingmeasuredinaServiceLevelAgreement(SLA).
2. ServiceLevelAgreementMatrix
Parameter SLR(monthlybasis)DNS DNSserviceavailability 0mindowntime=100%availability DNSnameserveravailability £432minofdowntime(»99%) TCPDNSresolutionRTT £1500ms,foratleast95%ofthequeries UDPDNSresolutionRTT £500ms,foratleast95%ofthequeries DNSupdatetime £60min,foratleast95%oftheprobesRDDS RDDSavailability £864minofdowntime(»98%)
88
RDDSqueryRTT £2000ms,foratleast95%ofthequeries RDDSupdatetime £60min,foratleast95%oftheprobesEPP EPPserviceavailability £864minofdowntime(»98%) EPPsession-commandRTT £4000ms,foratleast90%ofthecommands EPPquery-commandRTT £2000ms,foratleast90%ofthecommands EPPtransform-commandRTT £4000ms,foratleast90%ofthecommandsRegistryOperatorisencouragedtodomaintenanceforthedifferentservicesatthetimesanddatesofstatisticallylowertrafficforeachservice.However,notethatthereisnoprovisionforplannedoutagesorsimilarperiodsofunavailableorslowservice;anydowntime,beitformaintenanceorduetosystemfailures,willbenotedsimplyasdowntimeandcountedforSLApurposes.
3. DNS
3.1. DNSserviceavailability.Referstotheabilityofthegroupoflisted-as-authoritativenameserversofaparticulardomainname(e.g.,aTLD),toanswerDNSqueriesfromDNSprobes.Fortheservicetobeconsideredavailableataparticularmoment,atleast,twoofthedelegatednameserversregisteredintheDNSmusthavesuccessfulresultsfrom“DNStests”toeachoftheirpublic-DNSregistered“IPaddresses”towhichthenameserverresolves.If51%ormoreoftheDNStestingprobesseetheserviceasunavailableduringagiventime,theDNSservicewillbeconsideredunavailable.
3.2. DNSnameserveravailability.Referstotheabilityofapublic-DNSregistered“IPaddress”ofaparticularnameserverlistedasauthoritativeforadomainname,toanswerDNSqueriesfromanInternetuser.AllthepublicDNS-registered“IPaddress”ofallnameserversofthedomainnamebeingmonitoredshallbetestedindividually.If51%ormoreoftheDNStestingprobesgetundefined/unansweredresultsfrom“DNStests”toanameserver“IPaddress”duringagiventime,thenameserver“IPaddress”willbeconsideredunavailable.
3.3. UDPDNSresolutionRTT.ReferstotheRTTofthesequenceoftwopackets,theUDPDNSqueryandthecorrespondingUDPDNSresponse.IftheRTTis5timesgreaterthanthetimespecifiedintherelevantSLR,theRTTwillbeconsideredundefined.
3.4. TCPDNSresolutionRTT.ReferstotheRTTofthesequenceofpacketsfromthestartoftheTCPconnectiontoitsend,includingthereceptionoftheDNSresponseforonlyoneDNSquery.IftheRTTis5timesgreaterthanthetimespecifiedintherelevantSLR,theRTTwillbeconsideredundefined.
3.5. DNSresolutionRTT.Referstoeither“UDPDNSresolutionRTT”or“TCPDNSresolutionRTT”.
89
3.6. DNSupdatetime.ReferstothetimemeasuredfromthereceptionofanEPPconfirmationtoatransformcommandonadomainname,untilthenameserversoftheparentdomainnameanswer“DNSqueries”withdataconsistentwiththechangemade.ThisonlyappliesforchangestoDNSinformation.
3.7. DNStest.Meansonenon-recursiveDNSquerysenttoaparticular“IPaddress”(viaUDPorTCP).IfDNSSECisofferedinthequeriedDNSzone,foraquerytobeconsideredanswered,thesignaturesmustbepositivelyverifiedagainstacorrespondingDSrecordpublishedintheparentzoneor,iftheparentisnotsigned,againstastaticallyconfiguredTrustAnchor.TheanswertothequerymustcontainthecorrespondinginformationfromtheRegistrySystem,otherwisethequerywillbeconsideredunanswered.Aquerywitha“DNSresolutionRTT”5timeshigherthanthecorrespondingSLR,willbeconsideredunanswered.ThepossibleresultstoaDNStestare:anumberinmillisecondscorrespondingtothe“DNSresolutionRTT”or,undefined/unanswered.
3.8. MeasuringDNSparameters.Everyminute,everyDNSprobewillmakeanUDPorTCP“DNStest”toeachofthepublic-DNSregistered“IPaddresses”ofthenameserversofthedomainnamebeingmonitored.Ifa“DNStest”resultisundefined/unanswered,thetestedIPwillbeconsideredunavailablefromthatprobeuntilitistimetomakeanewtest.
3.9. CollatingtheresultsfromDNSprobes.Theminimumnumberofactivetestingprobestoconsiderameasurementvalidis20atanygivenmeasurementperiod,otherwisethemeasurementswillbediscardedandwillbeconsideredinconclusive;duringthissituationnofaultwillbeflaggedagainsttheSLRs.
3.10. DistributionofUDPandTCPqueries.DNSprobeswillsendUDPorTCP“DNStest”approximatingthedistributionofthesequeries.
3.11. PlacementofDNSprobes.ProbesformeasuringDNSparametersshallbeplacedasnearaspossibletotheDNSresolversonthenetworkswiththemostusersacrossthedifferentgeographicregions;careshallbetakennottodeployprobesbehindhighpropagation-delaylinks,suchassatellitelinks.
4. RDDS
4.1. RDDSavailability.ReferstotheabilityofalltheRDDSservicesfortheTLD,torespondtoqueriesfromanInternetuserwithappropriatedatafromtherelevantRegistrySystem.If51%ormoreoftheRDDStestingprobesseeanyoftheRDDSservicesasunavailableduringagiventime,theRDDSwillbeconsideredunavailable.
90
4.2. WHOISqueryRTT.ReferstotheRTTofthesequenceofpacketsfromthestartoftheTCPconnectiontoitsend,includingthereceptionoftheWHOISresponse.IftheRTTis5-timesormorethecorrespondingSLR,theRTTwillbeconsideredundefined.
4.3. Web-based-WHOISqueryRTT.ReferstotheRTTofthesequenceofpacketsfromthestartoftheTCPconnectiontoitsend,includingthereceptionoftheHTTPresponseforonlyoneHTTPrequest.IfRegistryOperatorimplementsamultiple-stepprocesstogettotheinformation,onlythelaststepshallbemeasured.IftheRTTis5-timesormorethecorrespondingSLR,theRTTwillbeconsideredundefined.
4.4. RDDSqueryRTT.Referstothecollectiveof“WHOISqueryRTT”and“Web-based-WHOISqueryRTT”.
4.5. RDDSupdatetime.ReferstothetimemeasuredfromthereceptionofanEPPconfirmationtoatransformcommandonadomainname,hostorcontact,upuntiltheserversoftheRDDSservicesreflectthechangesmade.
4.6. RDDStest.Meansonequerysenttoaparticular“IPaddress”ofoneoftheserversofoneoftheRDDSservices.QueriesshallbeaboutexistingobjectsintheRegistrySystemandtheresponsesmustcontainthecorrespondinginformationotherwisethequerywillbeconsideredunanswered.QuerieswithanRTT5timeshigherthanthecorrespondingSLRwillbeconsideredasunanswered.ThepossibleresultstoanRDDStestare:anumberinmillisecondscorrespondingtotheRTTorundefined/unanswered.
4.7. MeasuringRDDSparameters.Every5minutes,RDDSprobeswillselectoneIPaddressfromallthepublic-DNSregistered“IPaddresses”oftheserversforeachRDDSserviceoftheTLDbeingmonitoredandmakean“RDDStest”toeachone.Ifan“RDDStest”resultisundefined/unanswered,thecorrespondingRDDSservicewillbeconsideredasunavailablefromthatprobeuntilitistimetomakeanewtest.
4.8. CollatingtheresultsfromRDDSprobes.Theminimumnumberofactivetestingprobestoconsiderameasurementvalidis10atanygivenmeasurementperiod,otherwisethemeasurementswillbediscardedandwillbeconsideredinconclusive;duringthissituationnofaultwillbeflaggedagainsttheSLRs.
4.9. PlacementofRDDSprobes.ProbesformeasuringRDDSparametersshallbeplacedinsidethenetworkswiththemostusersacrossthedifferentgeographicregions;careshallbetakennottodeployprobesbehindhighpropagation-delaylinks,suchassatellitelinks.
91
5. EPP
5.1. EPPserviceavailability.ReferstotheabilityoftheTLDEPPserversasagroup,torespondtocommandsfromtheRegistryaccreditedRegistrars,whoalreadyhavecredentialstotheservers.TheresponseshallincludeappropriatedatafromtheRegistrySystem.AnEPPcommandwith“EPPcommandRTT”5timeshigherthanthecorrespondingSLRwillbeconsideredasunanswered.If51%ormoreoftheEPPtestingprobesseetheEPPserviceasunavailableduringagiventime,theEPPservicewillbeconsideredunavailable.
5.2. EPPsession-commandRTT.ReferstotheRTTofthesequenceofpacketsthatincludesthesendingofasessioncommandplusthereceptionoftheEPPresponseforonlyoneEPPsessioncommand.ForthelogincommanditwillincludepacketsneededforstartingtheTCPsession.ForthelogoutcommanditwillincludepacketsneededforclosingtheTCPsession.EPPsessioncommandsarethosedescribedinsection2.9.1ofEPPRFC5730.IftheRTTis5timesormorethecorrespondingSLR,theRTTwillbeconsideredundefined.
5.3. EPPquery-commandRTT.ReferstotheRTTofthesequenceofpacketsthatincludesthesendingofaquerycommandplusthereceptionoftheEPPresponseforonlyoneEPPquerycommand.ItdoesnotincludepacketsneededforthestartorcloseofeithertheEPPortheTCPsession.EPPquerycommandsarethosedescribedinsection2.9.2ofEPPRFC5730.IftheRTTis5-timesormorethecorrespondingSLR,theRTTwillbeconsideredundefined.
5.4. EPPtransform-commandRTT.ReferstotheRTTofthesequenceofpacketsthatincludesthesendingofatransformcommandplusthereceptionoftheEPPresponseforonlyoneEPPtransformcommand.ItdoesnotincludepacketsneededforthestartorcloseofeithertheEPPortheTCPsession.EPPtransformcommandsarethosedescribedinsection2.9.3ofEPPRFC5730.IftheRTTis5timesormorethecorrespondingSLR,theRTTwillbeconsideredundefined.
5.5. EPPcommandRTT.Refersto“EPPsession-commandRTT”,“EPPquery-commandRTT”or“EPPtransform-commandRTT”.
5.6. EPPtest.MeansoneEPPcommandsenttoaparticular“IPaddress”foroneoftheEPPservers.Queryandtransformcommands,withtheexceptionof“create”,shallbeaboutexistingobjectsintheRegistrySystem.TheresponseshallincludeappropriatedatafromtheRegistrySystem.ThepossibleresultstoanEPPtestare:anumberinmillisecondscorrespondingtothe“EPPcommandRTT”orundefined/unanswered.
92
5.7. MeasuringEPPparameters.Every5minutes,EPPprobeswillselectone“IPaddress”oftheEPPserversoftheTLDbeingmonitoredandmakean“EPPtest”;everytimetheyshouldalternatebetweenthe3differenttypesofcommandsandbetweenthecommandsinsideeachcategory.Ifan“EPPtest”resultisundefined/unanswered,theEPPservicewillbeconsideredasunavailablefromthatprobeuntilitistimetomakeanewtest.
5.8. CollatingtheresultsfromEPPprobes.Theminimumnumberofactivetestingprobestoconsiderameasurementvalidis5atanygivenmeasurementperiod,otherwisethemeasurementswillbediscardedandwillbeconsideredinconclusive;duringthissituationnofaultwillbeflaggedagainsttheSLRs.
5.9. PlacementofEPPprobes.ProbesformeasuringEPPparametersshallbeplacedinsideorclosetoRegistrarspointsofaccesstotheInternetacrossthedifferentgeographicregions;careshallbetakennottodeployprobesbehindhighpropagation-delaylinks,suchassatellitelinks.
6. EmergencyThresholds
Thefollowingmatrixpresentstheemergencythresholdsthat,ifreachedbyanyoftheservicesmentionedaboveforaTLD,wouldcausetheemergencytransitionoftheRegistryfortheTLDasspecifiedinSection2.13ofthisAgreement.
CriticalFunction EmergencyThreshold
DNSService 4-hourtotaldowntime/weekDNSSECproperresolution 4-hourtotaldowntime/week
EPP 24-hourtotaldowntime/weekRDDS 24-hourtotaldowntime/week
DataEscrowReachinganyofthecriteriaforthereleaseofdepositsdescribedinSpecification2,PartB,Section6.2throughSection6.6.
7. EmergencyEscalation
Escalationisstrictlyforpurposesofnotifyingandinvestigatingpossibleorpotentialissuesinrelationtomonitoredservices.Theinitiationofanyescalationandthesubsequentcooperativeinvestigationsdonotinthemselvesimplythatamonitoredservicehasfaileditsperformancerequirements.
EscalationsshallbecarriedoutbetweenICANNandRegistryOperators,RegistrarsandRegistryOperator,andRegistrarsandICANN.RegistryOperatorsandICANNmustprovidesaidemergencyoperationsdepartments.Currentcontactsmustbemaintainedbetween
93
ICANNandRegistryOperatorsandpublishedtoRegistrars,whererelevanttotheirroleinescalations,priortoanyprocessingofanEmergencyEscalationbyallrelatedparties,andkeptcurrentatalltimes.
7.1. EmergencyEscalationinitiatedbyICANN
Uponreaching10%oftheEmergencythresholdsasdescribedinSection6ofthisSpecification,ICANN’semergencyoperationswillinitiateanEmergencyEscalationwiththerelevantRegistryOperator.AnEmergencyEscalationconsistsofthefollowingminimumelements:electronic(i.e.,emailorSMS)and/orvoicecontactnotificationtotheRegistryOperator’semergencyoperationsdepartmentwithdetailedinformationconcerningtheissuebeingescalated,includingevidenceofmonitoringfailures,cooperativetrouble-shootingofthemonitoringfailurebetweenICANNstaffandtheRegistryOperator,andthecommitmenttobegintheprocessofrectifyingissueswitheitherthemonitoringserviceortheservicebeingmonitoring.
7.2. EmergencyEscalationinitiatedbyRegistrars
RegistryOperatorwillmaintainanemergencyoperationsdepartmentpreparedtohandleemergencyrequestsfromregistrars.IntheeventthataregistrarisunabletoconductEPPtransactionswiththeregistryfortheTLDbecauseofafaultwiththeRegistryServiceandisunabletoeithercontact(throughICANNmandatedmethodsofcommunication)theRegistryOperator,ortheRegistryOperatorisunableorunwillingtoaddressthefault,theregistrarmayinitiateanemergencyescalationtotheemergencyoperationsdepartmentofICANN.ICANNthenmayinitiateanemergencyescalationwiththeRegistryOperatorasexplainedabove.
7.3. NotificationsofOutagesandMaintenance
IntheeventthataRegistryOperatorplansmaintenance,itwillprovidenoticetotheICANNemergencyoperationsdepartment,atleast,twenty-four(24)hoursaheadofthatmaintenance.ICANN’semergencyoperationsdepartmentwillnoteplannedmaintenancetimes,andsuspendEmergencyEscalationservicesforthemonitoredservicesduringtheexpectedmaintenanceoutageperiod.
IfRegistryOperatordeclaresanoutage,asperitscontractualobligationswithICANN,onservicesunderaservicelevelagreementandperformancerequirements,itwillnotifytheICANNemergencyoperationsdepartment.Duringthatdeclaredoutage,ICANN’semergencyoperationsdepartmentwillnoteandsuspendemergencyescalationservicesforthemonitoredservicesinvolved.
8. CovenantsofPerformanceMeasurement
8.1. Nointerference.RegistryOperatorshallnotinterferewithmeasurementProbes,includinganyformofpreferentialtreatmentoftherequestsforthemonitoredservices.RegistryOperatorshallrespondtothemeasurement
94
testsdescribedinthisSpecificationasitwouldtoanyotherrequestfromanInternetuser(forDNSandRDDS)orregistrar(forEPP).
8.2. ICANNtestingregistrar.RegistryOperatoragreesthatICANNwillhaveatestingregistrarusedforpurposesofmeasuringtheSLRsdescribedabove.RegistryOperatoragreestonotprovideanydifferentiatedtreatmentforthetestingregistrarotherthannobillingofthetransactions.ICANNshallnotusetheregistrarforregisteringdomainnames(orotherregistryobjects)foritselforothers,exceptforthepurposesofverifyingcontractualcompliancewiththeconditionsdescribedinthisAgreement.RegistryOperatorshallidentifythesetransactionsusingRegistrarID9997.
95
SPECIFICATION11
PUBLICINTERESTCOMMITMENTS
1. RegistryOperatorwilluseonlyICANNaccreditedregistrarsthatarepartytotheRegistrarAccreditationAgreementapprovedbytheICANNBoardofDirectorson27June2013inregisteringdomainnames.AlistofsuchregistrarsshallbemaintainedbyICANNonICANN’swebsite.
2. (Intentionallyomitted.)
3. RegistryOperatoragreestoperformthefollowingspecificpublicinterest
commitments,whichcommitmentsshallbeenforceablebyICANNandthroughthePublicInterestCommitmentDisputeResolutionProcessestablishedbyICANN(postedathttp://www.icann.org/en/resources/registries/picdrp),whichmayberevisedinimmaterialrespectsbyICANNfromtimetotime(the“PICDRP”).RegistryOperatorshallcomplywiththePICDRP.RegistryOperatoragreestoimplementandadheretoanyremediesICANNimposes(whichmayincludeanyreasonableremedy,includingfortheavoidanceofdoubt,theterminationoftheRegistryAgreementpursuanttoSection4.3(e)oftheAgreement)followingadeterminationbyanyPICDRPpanelandtobeboundbyanysuchdetermination.
a. RegistryOperatorwillincludeaprovisioninitsRegistry-Registrar
AgreementthatrequiresRegistrarstoincludeintheirRegistrationAgreementsaprovisionprohibitingRegisteredNameHoldersfromdistributingmalware,abusivelyoperatingbotnets,phishing,piracy,trademarkorcopyrightinfringement,fraudulentordeceptivepractices,counterfeitingorotherwiseengaginginactivitycontrarytoapplicablelaw,andproviding(consistentwithapplicablelawandanyrelatedprocedures)consequencesforsuchactivitiesincludingsuspensionofthedomainname.
b. RegistryOperatorwillperiodicallyconductatechnicalanalysisto
assesswhetherdomainsintheTLDarebeingusedtoperpetratesecuritythreats,suchaspharming,phishing,malware,andbotnets.RegistryOperatorwillmaintainstatisticalreportsonthenumberofsecuritythreatsidentifiedandtheactionstakenasaresultoftheperiodicsecuritychecks.RegistryOperatorwillmaintainthesereportsforthetermoftheAgreementunlessashorterperiodisrequiredbylaworapprovedbyICANN,andwillprovidethemtoICANNuponrequest.
c. RegistryOperatorwilloperatetheTLDinatransparentmanner
consistentwithgeneralprinciplesofopennessandnon-
96
discriminationbyestablishing,publishingandadheringtoclearregistrationpolicies.
d. RegistryOperatorofa“GenericString”TLDmaynotimposeeligibility
criteriaforregisteringnamesintheTLDthatlimitregistrationsexclusivelytoasinglepersonorentityand/orthatperson’sorentity’s“Affiliates”(asdefinedinSection2.9(c)oftheRegistryAgreement).“GenericString”meansastringconsistingofawordortermthatdenominatesordescribesageneralclassofgoods,services,groups,organizationsorthings,asopposedtodistinguishingaspecificbrandofgoods,services,groups,organizationsorthingsfromthoseofothers.