> Status:                  serverDeleteProhibited
> Status:                  serverTransferProhibited
> Status:                  serverUpdateProhibited

Here's how we see AusRegistry use them:

serverDeleteProhibited - I've never seen this one used on any domain. Theoretically it means that
the registry (AusRegistry in this case) is not allowed to delete the domain.  No Idea why this would
be used.

serverTransferProhibited - Only really used on the promotional id.au domains.  A 'free' id.au domain
is not allowed to be transferred between registrars.  This status is removed by the registry once
the domain has been paid for.

serverUpdateProhibited - This is set when a domain expires.  As soon as the expiry date passes the
domain is no longer allowed to be updated (can't change nameservers, contacts etc).  If you initiate
a transfer or renewal of the domain, then this status is removed.

Cheers,
Sebastian.

----- Original Message -----
From: "Skeeve Stevens" <skeeve&#167;skeeve.org>
To: <dns&#167;lists.auda.org.au>
Sent: Thursday, November 13, 2003 7:43 AM
Subject: RE: [DNS] What do these each mean and how?


> So a domain that had all 3 of these... What does that mean?
> That the Registry has locked it? So it cant be moved to another
> registry?
>
> ...Skeeve
>
> -----Original Message-----
> From: Josh Rowe [mailto:josh&#167;email.nu]
> Sent: Thursday, 13 November 2003 12:56 AM
> To: dns&#167;lists.auda.org.au
> Subject: Re: [DNS] What do these each mean and how?
>
>
> 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-0
> 4.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/
>
> ------------------------------------------------------------------------
> ---
> List policy, unsubscribing and archives => http://dotau.org/ Please do
> not retransmit articles on this list without permission of the
> author, further information at the above URL.
>
>
> ========================================================================
>    This message has been scanned for spam & viruses by Mail Security.
>    To report SPAM forward the message to:    spam&#167;mailsecurity.net.au
>    Mail Security                              www.mailsecurity.net.au
> ========================================================================
>
>
> ---------------------------------------------------------------------------
> List policy, unsubscribing and archives => http://dotau.org/
> Please do not retransmit articles on this list without permission of the
> author, further information at the above URL.