EPP Clause Samples

POPULAR SAMPLE Copied 1 times
EPP. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF) including all successor standards, modifications or additions thereto relating to the provisioning and management of domain names using the Extensible Provisioning Protocol (EPP) in conformance with RFCs 5910, 5730, 5731, 5732 (if using host objects), 5733 and 5734. If Registry Operator implements Registry Grace Period (RGP), it will comply with RFC 3915 and its successors. If Registry Operator requires the use of functionality outside the base EPP RFCs, Registry Operator must document EPP extensions in Internet-­‐Draft format following the guidelines described in RFC 3735. Registry Operator will provide and update the relevant documentation of all the EPP Objects and Extensions supported to ICANN prior to deployment.
EPP. Refers to the Extensible Provisioning Protocol as specified in ▇▇▇ ▇▇▇▇ and related RFCs.
EPP. Refers to the Extensible Provisioning Protocol as specified in RFC 5730 and related RFCs.
EPP. ▇▇▇▇▇ shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF) including all successor standards, modifications or additions thereto relating to the provisioning and management of domain names using the Extensible Provisioning Protocol (EPP) in conformance with RFCs 5910, 5730, 5731, 5732 (if using host objects), 5733 and 5734. If ▇▇▇▇▇ implements Registry Grace Period (RGP), it will comply with RFC 3915 and its successors. If ▇▇▇▇▇ requires the use of functionality outside the base EPP RFCs, ▇▇▇▇▇ must document EPP extensions in Internet-Draft format following the guidelines described in RFC 3735. ▇▇▇▇▇ will provide and update the relevant documentation of all the EPP Objects and Extensions supported to cxDA prior to deployment.
EPP. If the Registry uses EPP as a registration protocol, it shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF) including all successor standards, modifications or additions thereto relating to the provisioning and management of domain names using the Extensible Provisioning Protocol (EPP) in conformance with RFCs 5910, 5730, 5731, 5732 (if using host objects), 5733 and 5734.
EPP. During the term of the Sublease, Tenant’s and Licensees’ use of the Premises shall comply with all applicable provisions of City Council Policy 4- 6, Environmentally Preferred Procurement Policy (which policy can be found on the City’s website at the following link: ▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇▇.▇▇▇/DocumentCenter/View/3862), including: i) use of recycled and/or recyclable products in daily operations.(i.e. 30, 50, 100% PCW paper, chlorine process free; triclosan free hand cleaner, etc.), ii) use of Energy Star Compliant equipment, iii) internal waste reduction and reuse protocol(s), and iv) water and resource conservation activities, including bans on individual serving bottled water and the use of compostable food service products, etc..
EPP. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF) including all successor standards, modifications or additions thereto relating to the provisioning and management of domain names using the Extensible Provisioning Protocol (EPP) in conformance with RFCs 5910, 5730, 5731, 5732 (if using host objects), 5733 and 5734. Notwithstanding the foregoing, nothing herein shall require Registry Operator to comply with informational RFCs with respect to EPP under this Section 1.2 of Appendix 7. If Registry Operator implements Registry Grace Period (RGP), it will comply with RFC 3915 and its successors. If Registry Operator requires the use of functionality outside the base EPP RFCs, Registry Operator is not required to submit documented EPP extensions to the IETF but Registry Operator must document EPP extensions in Internet-Draft format following the guidelines described in RFC 3735. Registry Operator will provide and update the relevant documentation of all the EPP Objects and Extensions supported to ICANN prior to deployment.
EPP. Agreements the Acquirer (Apoena) has made with landowners for the processes actively working on: 866.022/2001 ▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇ ▇▇ ▇▇▇▇▇ ▇▇▇. ▇▇▇▇▇▇▇ Apoena Title received from Serra ▇▇ ▇▇▇▇▇ when ▇▇▇ assets were acquired (June’2016) - 866.276/2001 Lavrinha Guia de Utilização Faz. Paraiso Delvir Antonio Bonavigo Court agreement signed with the owner for partial use & mining (subject to royalties) Land ndenisation, already paid. 0.5% of Gold revenue as royalties 866.276/2001 Lavrinha Guia de Utilização Faz. Arco ▇▇▇▇ ▇▇▇▇▇▇ ▇▇ ▇▇▇▇▇ Leandro Contract signed with the owner for partial use & mining (subject to royalties) R$ 80k for indenisation, already paid. 0.5% of Gold revenue as royalties 866.276/2001 Lavrinha Guia de Utilização Aldison Beariz Contract signed with the owner for partial use & mining (not subject to royalties). Cession of mineral rights, from other Apoena’s area, to Aldison Beariz 866.276/2001 Lavrinha Guia de Utilização ▇▇▇▇▇ Lavrinha ▇▇▇▇▇▇ ▇▇▇▇▇▇ ▇▇▇▇▇▇ Contract signed with the owner for partial use & mining (not subject to royalties). R$ 5.2k/monthly No addition for royalties 866.148/2003 Pau-a-pique Portaria de Lavra Sitio ▇▇▇▇ do ▇▇▇▇▇/ Lagoa Azul ▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇▇ ▇▇ ▇▇▇▇▇▇▇▇ Contract signed with the owner for partial use & mining (subject to royalties) R$ 9k monthly, plus 0.5% of Gold revenue as royalties 866.148/2003 Pau-a-pique Portaria de Lavra ▇▇▇▇▇ ▇▇▇-a- pique ▇▇▇▇▇▇▇ Guimarãe s ▇▇▇▇▇▇▇▇ Contract signed with the owner for partial use & mining (subject to royalties) R$ 1.6k monthly, plus 0.5% of Gold revenue as royalties 866.032/2001 Nosde/Japonês ▇▇▇▇▇▇ de pesquisa Lidionor ▇▇▇▇ ▇▇ ▇▇▇▇▇▇▇▇ Contract signed with the owner for partial use for exploration R$ 5k monthly 866.032/2001 Nosde/Japonês ▇▇▇▇▇▇ de pesquisa ▇▇▇▇▇ Lavrinha ▇▇▇▇▇▇ ▇▇▇▇▇▇ ▇▇▇▇▇▇ Contract signed with the owner for partial use for exploration R$ 2k monthly 866.379/2000 Rio Alegre Guia de Utilização Sitio Sossego ▇▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇ Contract signed with the owner for partial use & mining (not subject to royalties) R$ 45k for indenisation of land for road R$ 5k monthly + R$ 30k while mining (during a minimum of 6 months) All DNPM processes that Apoena has rights (various stages): 866023/1989 82.43 ▇▇▇▇▇▇▇▇▇▇▇▇ ▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇ - Req Pesq/Indeferimento Art 18 Par 1 Publicado Indeferimentos 14/08/2017 Mineração ▇▇▇▇▇▇▇ Industria e Comercio Ltda 56.617.202/0001-31 866024/1989 14.77 ▇▇▇▇▇▇▇▇▇▇▇▇ ▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇ - Req Pesq/Indeferimento Art 18 Par 1 Publicado Indeferimento...
EPP 

Related to EPP

  • Mobility The ability to move indoors from room to room on level surfaces at the normal place of residence.

  • Cloud storage DSHS Confidential Information requires protections equal to or greater than those specified elsewhere within this exhibit. Cloud storage of Data is problematic as neither DSHS nor the Contractor has control of the environment in which the Data is stored. For this reason: (1) DSHS Data will not be stored in any consumer grade Cloud solution, unless all of the following conditions are met: (a) Contractor has written procedures in place governing use of the Cloud storage and Contractor attests in writing that all such procedures will be uniformly followed. (b) The Data will be Encrypted while within the Contractor network. (c) The Data will remain Encrypted during transmission to the Cloud. (d) The Data will remain Encrypted at all times while residing within the Cloud storage solution. (e) The Contractor will possess a decryption key for the Data, and the decryption key will be possessed only by the Contractor and/or DSHS. (f) The Data will not be downloaded to non-authorized systems, meaning systems that are not on either the DSHS or Contractor networks. (g) The Data will not be decrypted until downloaded onto a computer within the control of an Authorized User and within either the DSHS or Contractor’s network. (2) Data will not be stored on an Enterprise Cloud storage solution unless either: (a) The Cloud storage provider is treated as any other Sub-Contractor, and agrees in writing to all of the requirements within this exhibit; or, (b) The Cloud storage solution used is FedRAMP certified. (3) If the Data includes protected health information covered by the Health Insurance Portability and Accountability Act (HIPAA), the Cloud provider must sign a Business Associate Agreement prior to Data being stored in their Cloud solution.

  • PayPal's Seller Protection Program What’s eligible

  • Description of Vendor Entity and Vendor's Goods & Services If awarded, this description of Vendor and Vendor's goods and services will appear on the TIPS website for customer/public viewing.

  • PayPal’s Buyer Protection Program When you buy something from a seller who accepts PayPal, you may be eligible for a refund under PayPal’s Buyer Protection program. When applicable, PayPal’s Buyer Protection program entitles you to reimbursement for the full purchase price of the item plus the original shipping costs you paid, if any. PayPal determines, in its sole discretion, whether your claim is eligible for PayPal’s Buyer Protection program. PayPal’s original determination is considered final, but you may be able to file an appeal of the decision with PayPal if you have new or compelling information not available at the time of the original determination or you believe there was an error in the decision-making process. The program terms and conditions are set out in PayPal’s Buyer Protection program page and form part of this user agreement.