On Thu, Nov 13, 2003 at 12:15:03AM +1100, Skeeve Stevens wrote: > > Status: serverDeleteProhibited > Status: serverTransferProhibited > Status: serverUpdateProhibited This page: AusRegistry Technical Accreditation http://www.ausregistry.com.au/technical/ has a link to this: Extensible Provisioning Protocol Contact Mapping http://www.ausregistry.com.au/technical/draft-ietf-provreg-epp-contact-04.txt which says: " ... 2.2 Status Values A contact object MUST always have at least one associated status value. Status values can be set only by the client that sponsors a contact object and by the server on which the object resides. A client can change the status of a contact object using the EPP <update> command. Each status value MAY be accompanied by a string of human-readable text that describes the rationale for the status applied to the object. A client MUST NOT alter status values set by the server. A server MAY alter or override status values set by a client subject to local server policies. Status values that can be added or removed by a client are prefixed with "client". Corresponding status values that can be added or removed by a server are prefixed with "server". Status values that do not begin with either "client" or "server" are server-managed. Status Value Descriptions: clientDeleteProhibited, serverDeleteProhibited Requests to delete the object MUST be rejected. clientTransferProhibited, serverTransferProhibited Requests to transfer the object MUST be rejected. clientUpdateProhibited, serverUpdateProhibited Requests to update the object (other than to remove this status) MUST be rejected. linked The contact object has at least one active association with another object, such as a domain object. Servers SHOULD provide services to determine existing object associations. ok This is the nominal status value for an object that has no pending operations or prohibitions. pendingDelete A delete request has been received for the object, but the object has not yet been purged from the server database. pendingTransfer A transfer request has been received for the object, and completion of the request is pending. Transform commands other than <transfer> MUST be rejected while an object is in this state. "ok" status MAY only be combined with "linked" status. "linked" status MAY be combined with any status. "pendingDelete" status MUST NOT be combined with either "clientDeleteProhibited" or "serverDeleteProhibited" status. "pendingTransfer" status MUST NOT be combined with either "clientTransferProhibited" or "serverTransferProhibited" status. All other status value combinations are valid. ... " Josh -- http://josh.id.au/Received on Fri Oct 03 2003 - 00:00:00 UTC
This archive was generated by hypermail 2.3.0 : Sat Sep 09 2017 - 22:00:07 UTC