Re: IDN administrative bundling
Benoit Levac <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <[email protected]> |
Mike, I would be interested in reviewing the draft for sure. You could just send me a copy if it’s not quite ready for public review. The EPP RFCs only define the offline processing at a high level. There are some aspects that are not covered that bring up some questions. You might have experience with these since you seem to have implemented this. Does a pending status such as “pendingUpdate” imply “serverUpdateProhibited”? RFC 5731 only mentions that they cannot be combined. The issue we have to think about is that if a domain is in “pendingUpdate” status because a registrant update action is in progress, we wouldn’t want to prevent host updates for example if they are required. This is mainly why we are asking about a standard means to cancel a pending actions. Cheers, Ben From: mike [mailto:[email protected]] Sent: March-30-12 3:12 AM To: Benoit Levac Cc: [email protected] Subject: Re: [provreg] IDN administrative bundling Hi Ben, 3 – With domain transfer, there is a defined way of cancelling a pending transfer (as per section 2.9.3.4 of RFC 5730), but for a pending domain update, there is no defined way to cancel a pending operation. Any suggestions out there. We have a draft extension for cancelling pending actions on the registry, this allows the registrar to cancel a suspension, deletion, update, or deletion due to expiry by the action name. This creates some pretty complex policy handling esp. when expiry was due to non payment and cancelling that action results in billing. If you want a copy we can submit it for draft review. Kind Regards, Mike co.za _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg