COMMUNITY REGISTRATION POLICIES Sample Clauses

COMMUNITY REGISTRATION POLICIES. Registry Operator shall implement and comply with all community registration policies described below and/or attached to this Specification 12. In the event Specification 12 conflicts with the requirements of any other provision of the Registry Agreement, such other provision shall govern.
AutoNDA by SimpleDocs
COMMUNITY REGISTRATION POLICIES. Eligibility
COMMUNITY REGISTRATION POLICIES. Registry Operator shall implement and comply with all community registration policies described below and/or attached to this Specification 12. In the event Specification 12 conflicts with the requirements of any other provision of the Registry Agreement, such other provision shall govern. Registry Operator takes its responsibilities to the global banking community seriously and it is essential that registrations only be permitted by verified members of the banking community. Therefore, registrations may initially be made by the following for-profit and not-for-profit businesses or organizations: State, regional and provincial banks that are chartered and supervised by a government regulatory authority; National banks that are chartered and supervised by a government regulatory authority; Associations whose members are primarily comprised of entities identified above in points 1, 2, or 3; Service providers that are principally owned by or predominantly supporting regulated entities identified above in points 1, 2, or 3 (if approved by the Registry Operator Board of Directors); and Government regulators of chartered and supervised banks or savings associations or organizations whose members are primarily comprised of such government regulators (if approved by the Registry Operator Board of Directors). To ensure strict compliance with its policies, Registry Operator will develop and implement a registrant eligibility criteria and evaluation process. This process requires collecting registrant information that will be used by Registry Operator or its designated third-party service provider to authenticate that the registrant is a member of the global banking community. This requirement will be hard coded into Registry Operator’s Registry-Registrar Agreement (RRA). As part of the registration process, potential registrants will be required to provide certain information to Registry Operator, or its designated third-party service provider, to verify their eligibility to register a domain name in TLD. This information may include, but is not limited to the following: Full legal name Business name Business address Business phone Business email Another proof of identity necessary to establish that the registrant is an eligible member of the banking community (e.g., business license, certificate of formation, articles of incorporation, corporate operating agreement, charter documents, attorney opinion letter, mission statement for non-profit organization): For bank...
COMMUNITY REGISTRATION POLICIES. Registry Operator shall implement and comply with all community registration policies described below and/or attached to this Specification 12. In the event this Specification 12 conflicts with the requirements of any other provision of the Registry Agreement, such other provision of the Registry Agreement shall govern. Contents Part I. TLD Charter Part II. Delegated Authority Part III. Description of Sponsored TLD Community Part IV. Selection of Registrars
COMMUNITY REGISTRATION POLICIES. Registry Operator shall implement and comply with all community registration policies described below and/or attached to this Specification 12. In the event Specification 12 conflicts with the requirements of any other provision of the Registry Agreement, such other provision shall govern. Two types of conditions must be fulfilled for the right to register a TLD name. These are: (A) community membership (bona fide presence in the Paris area) and (B) the additional requirements that: • The presence in Paris area and use of domain are generally accepted as legitimate. • The presence in Paris area and use of domain are conducive to welfare of the Paris area. • The presence in Paris area and use of domain are commensurate to role and importance of domain. • The presence in Paris area and use of domain are based on good faith at registration and thereafter. These conditions must always be fulfilled. The strength of the validation is kept in line with the importance of the underlying domain name base on the assumption that a typical user would reasonably make. Registrants are required to have an administrative contact in the Paris area. This is verified in part automatically (through the postal code in the administrative contact record and by a human eyes review pre-­‐validation or post-­‐validation. The administrative contact may be any person or entity having received and accepted the mandate to act as such for the respective domain. (The registrar may act as administrative contact.) Any communications addressed to the administrative contact are deemed to have been brought to the attention of the domain holder. Validation checks include machine and human verification of address accuracy. The validation may be assisted through pre-­‐identification of potential registrants using existing community channels, in particular through promotion codes. After the launch phase, the validation mode goes from pre-­‐validation to post-­‐validation and later to statistically targeted random validation, backed up by an ongoing enforcement program. Validation will include checks about the registered domain name actual or intended use. As far as intended use would be declared by the registrant, a false statement of intended use is an indication of bad faith and can be the basis for the suspension of the domain name. The validation and enforcement program are supported by an integrated issue tracking system. This system allows validating agents and personnel to cooperate and int...
COMMUNITY REGISTRATION POLICIES. Registry Operator shall implement and comply with all community registration policies described below and/or attached to this Specification 12.Operators will include a provision in their Registry-Registrar Agreements that requires registrars to include in their Registration Agreements a provision requiring registrants to comply with all applicable laws, including those that relate to privacy, data collection, consumer protection (including in relation to misleading and deceptive conduct), fair lending, debt collection, organic farming, disclosure of data, and financial disclosures. [Insert registration policies] Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the PICDRP. Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. Nothing in Section 4 of this Specification shall limit any obligations of Registry Operator under Sections 1, 2 and 3 of this Specification. In the event Section 4 of this Specification conflicts with the requirements of any other provision of the Registry Agreement (including any Section of this Specification), such other provision shall govern.
COMMUNITY REGISTRATION POLICIES. Registry Operator shall implement and comply with all community registration policies described below and/or attached to this Specification 12. In the event Specification 12 conflicts with the requirements of any other provision of the Registry Agreement, such other provision shall govern. [Insert registration policies] 1. Use your domain for any purposes prohibited by the laws of the jurisdiction(s) in which you do business or any other applicable law. For banking companies specifically, use your domain name for any purposes prohibited by the bank’s charter or license. 2. Use your domain for any purposes or in any manner that violates a statute, rule or law governing use of the Internet and⁄or electronic commerce (specifically including “phishing,” ʺpharming,” and⁄or distributing Internet viruses and other destructive activities).
AutoNDA by SimpleDocs
COMMUNITY REGISTRATION POLICIES. Registry Operator shall implement and comply with all community registration policies described below and/or attached to this Specification 12. In the event Specification 12 conflicts with the requirements of any other provision of the Registry Agreement, such other provision shall govern. [Insert registration policies] All registrants within this TLD will be vetted prior to registration to ensure that they meet all applicable regulatory standards, including pharmacy licensure, drug authenticity, and valid prescription requirements. Eligible registrants will demonstrate compliance with the laws of the jurisdiction in which they are based, as well as in all jurisdictions in which they conduct business. In addition, the Registry Operator will incorporate both active and passive safeguards into its operation to ensure that these registrants continue to abide by the terms and conditions set forth in their registration agreements. Registrants found to be out of compliance with these terms and conditions will be denied a TLD domain name, or will have their existing TLD domain name revoked. In the event that a domain name is denied or revoked, registrants will have access to an appeal process. Details of this appeal process have yet to be finalized but will be modeled on the appeals process used by Registry Operator for its many accreditation programs.
COMMUNITY REGISTRATION POLICIES. Registry Operator shall implement and comply with all community registration policies described below and/or attached to this Specification 12. In the event Specification 12 conflicts with the requirements of any other provision of the Registry Agreement, such other provision shall govern. According to the TLD registration policies, eligible registrants to register a second-level name in TLD are based in the countries of Austria, Germany, Liechtenstein and Switzerland and are in detail: Governments; Governmental organizations regulating the insurance industry; Organizations and individuals (sole proprietors) that are recognized and registered members of the insurance industry community; Primary insurers, reinsurers and social insurers with an authorization within the legal frameworks for the insurance industry in the respective countries; Insurance agents and insurance intermediaries with an authorization within the legal framework for the insurance industry in the respective countries; and At an official public register registered associations, educational institutions and service providers of the insurance industry. The eligibility will be determined by a validation of the owner of each registered domain name. It will be checked in the public registers of insurance intermediaries if the registrant is a member of the insurance community. The TLD has both, content and use restrictions: Content: TLD domain names must only be used for purposes solely dedicated to insurance topics. Use: The registrant must have started the use of a TLD domain name within six months after the registration in respect to the content and use restrictions of such TLD domain:
COMMUNITY REGISTRATION POLICIES. Registry Operator shall implement and comply with all community registration policies described below and/or attached to this Specification 12. In the event Specification 12 conflicts with the requirements of any other provision of the Registry Agreement, such other provision shall govern. [Insert registration policies] According to the TLD registration policies, eligible registrants to register a second-­‐level name in TLD are based in the countries of Austria, Germany, Liechtenstein and Switzerland and are in detail: a. Governments;
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!