Required Action. If the escrow deposit is older (as defined above) than the zone file, and the zone file shows the domain object is available, then the pending* status will be discarded. If the escrow deposit is newer (as defined above) than the zone file, then the pending* status will be respected. Objects in a pendingCreate status leave substantial ambiguity as to who the registrant is supposed to be. However, that ambiguity could be addressed as import rules or through dispute resolution. If the escrow deposit is older (as defined above) than the zone file, and the zone file shows the domain object is available, and the escrow deposit contains multiple instances of the same domain name in pendingCreate, then the domain object should be created with placeholder records (because we do not know who the registrant is). Dispute resolution will be required to resolve the conflict and the records need to be flagged as a potential area of discrepancy. If the escrow deposit is older (as defined above) than the zone file, and the zone file shows the domain object is available, and the escrow deposit contains only one instance the same domain name in pendingCreate, then the domain object should be created in the SRS sponsored by and registered to whomever the escrow deposit specifies. This situation should also be flagged as a potential area of discrepancy, however, and the dispute resolution process may be used if needed.
Appears in 3 contracts
Samples: Emergency Back End Registry Operator Agreement, Emergency Back End Registry Operator Agreement, Emergency Back End Registry Operator Agreement
Required Action. If the escrow deposit is older (as defined above) than the zone file, and the zone file shows the domain object is available, then the pending* status will be discarded. If the escrow deposit is newer (as defined above) than the zone file, then the pending* status will be respected; this implies that the domain name should not be included in a generated zone file. Objects in a pendingCreate status leave substantial ambiguity as to who the registrant is supposed to be. However, that ambiguity could be addressed as import rules or through dispute resolution. However, If the escrow deposit is older (as defined above) than the zone file, and the zone file shows the domain object is available, and the escrow deposit contains multiple instances of the same domain name in pendingCreate, then the domain object should be created with placeholder records (because we do not don’t know who the registrant is). Dispute resolution will be required to resolve the conflict and the records need to be flagged as a potential area of discrepancy. If the escrow deposit is older (as defined above) than the zone file, and the zone file shows the domain object is available, and the escrow deposit contains only one instance the same domain name in pendingCreate, then the domain object should be created in the SRS sponsored by and registered to whomever the escrow deposit specifies. This situation should also be flagged as a potential area of discrepancy, however, and the dispute resolution process may be used if needed.
Appears in 1 contract