C4 Credit Class Clause Samples
The C4 Credit Class clause defines the specific category or classification of credits that are being referenced or transacted under an agreement. In practice, this clause identifies the type of credits—such as carbon credits, renewable energy certificates, or other environmental credits—by referencing a recognized standard or registry. By clearly specifying the credit class, the clause ensures that both parties understand the nature and quality of the credits involved, thereby reducing ambiguity and preventing disputes over the eligibility or acceptability of the credits delivered.
C4 Credit Class. If Registry Operator fails to comply with C4 Credit Class category Performance Specifications, Registry Operator will credit the Registrar Community according to the following tables (C4a and C4b) (which amount will be credited to the Registrars on a proportional basis as set forth above). C4a Planned Outage Notification Example: In each instance the Registry Operator fails to meet the Performance Specifications for Notification and Timeframe related to Planned Outages and Extended Planned Outages, the Registry Operator is subject to the credit in Table C4a. For example, the Registry Operator informs the Registrar Community that it will initiate a Planned Outage of the SRS on the next calendar Sunday (five (5) days advance notice). The corresponding Registry Operator's Performance Specification is 28 days notice. From the Credit Lookup Matrix, we see the relevant SLA is found in Table C4a. This results in a credit of $500 USD to be paid to the Registrar Community.
C4 Credit Class. If Registry Operator fails to comply with C4 Credit Class category Performance Specifications, Registry Operator will credit the Registrar Community according to the following tables (C4a and C4b) (which amount will be credited to the Registrars on a proportional basis as set forth above).
C4 Credit Class. If usTLD Administrator fails to comply with C4 Credit Class category Performance Specifications, usTLD Administrator will credit the Registrar Community according to the following tables (C4a and C4b) (which amount will be credited to the Registrars on a proportional basis as set forth above). C4a Planned Outage Notification Example: In each instance the usTLD Administrator fails to meet the Performance Specifications for Notification and Timeframe related to Planned Outages and Extended Planned Outages, the usTLD Administrator is subject to the credit in Table C4a. For example, the usTLD Administrator informs the Registrar Community that it will initiate a Planned Outage of the SRS on the next calendar Sunday (five (5) days advance notice). The corresponding usTLD Administrator's Performance Specification is 28 days notice. From the Credit Lookup Matrix, we see the relevant SLA is found in Table C4a. This results in a credit of
C4 Credit Class. If ▇▇▇▇.▇▇ Administrator fails to comply with C4 Credit Class category Performance Specifications, ▇▇▇▇.▇▇ Administrator will credit the Registrar Community according to the following tables (C4a and C4b) (which amount will be credited to the Registrars on a proportional basis as set forth above). C4a Planned Outage Notification Example: In each instance the ▇▇▇▇.▇▇ Administrator fails to meet the Performance Specifications for Notification and Timeframe related to Planned Outages and Extended Planned Outages, the ▇▇▇▇.▇▇ Administrator is subject to the credit in Table C4a. For example, the ▇▇▇▇.▇▇ Administrator informs the Registrar Community that it will initiate a Planned Outage of the SRS on the next calendar Sunday (five (5) days advance notice). The corresponding ▇▇▇▇.▇▇ Administrator's Performance Specification is 28 days notice. From the Credit Lookup Matrix, we see the relevant SLA is found in Table C4a. This results in a credit of