Conventions. The key words "MUST,” "MUST NOT,” "REQUIRED,” "SHALL", "SHALL NOT,” "SHOULD,” "SHOULD NOT,” "RECOMMENDED,” "MAY,” and "OPTIONAL" in this document are to be interpreted as described in IETF ▇▇▇ ▇▇▇▇.
Appears in 7 contracts
Sources: Sponsored TLD Registry Agreement, Sponsored TLD Registry Agreement, Sponsored TLD Registry Agreement
Conventions. The key words "MUST,” ", "MUST NOT,” ", "REQUIRED,” ", "SHALL", "SHALL NOT,” ", "SHOULD,” ", "SHOULD NOT,” ", "RECOMMENDED,” ", "MAY,” ", and "OPTIONAL" in this document are to be interpreted as described in IETF ▇▇▇ ▇▇▇▇RFC 2119.
Appears in 6 contracts
Sources: Data Escrow Specification, Sponsored TLD Registry Agreement, Sponsored TLD Registry Agreement
Conventions. The key words "MUST,” ", "MUST NOT,” ", "REQUIRED,” ", "SHALL", "SHALL NOT,” ", "SHOULD,” ", "SHOULD NOT,” ", "RECOMMENDED,” ", "MAY,” ", and "OPTIONAL" in this document are to be interpreted as described in IETF ▇▇▇ ▇▇▇▇.
Appears in 3 contracts
Sources: Data Escrow Specification, Data Escrow Specification, Registry Data Escrow Agreement
Conventions. The key words "MUST,” "MUST NOT,” "REQUIRED,” "SHALL", "SHALL NOT,” "SHOULD,” "SHOULD NOT,” "RECOMMENDED,” "MAY,” and "OPTIONAL" in this document are to be interpreted as described in IETF ▇▇▇ ▇▇▇▇RFC 2119.
Appears in 3 contracts
Sources: Data Escrow Agreement, Data Escrow Agreement, Data Escrow Agreement
Conventions. The key words "MUST,” "MUST NOT,” "REQUIRED,” "SHALL", "SHALL NOT,” "SHOULD,” "SHOULD NOT,” "RECOMMENDED,” "MAY,” and "OPTIONAL" in this document are to be interpreted as described in IETF ▇▇▇ ▇▇▇▇RFC 2119 .
Appears in 1 contract
Sources: Data Escrow Agreement
Conventions. The key words "MUST,” " "MUST NOT,” " "REQUIRED,” " "SHALL", "SHALL NOT,” " "SHOULD,” " "SHOULD NOT,” " "RECOMMENDED,” " "MAY,” " and "OPTIONAL" in this document are to be interpreted as described in IETF ▇▇▇ ▇▇▇▇RFC 2119.
Appears in 1 contract
Sources: Data Escrow Specification