registry
Click on the red underlined text to get to the source
...
This document describes the specifications for the NSI Registry
Registrar Protocol (RRP) version 1.1 ...
... domains (TLDs) administered by a TLD registry. RRP is specified using
Augmented Backus-Nauer Form (ABNF ...
... RRP was developed by the Network Solutions, Inc. Registry under the
auspices of the Shared Registration System program. The protocol was
...
... Registration System with five registrars. Additional
registrars began using the protocol in July 1999. The operational
experiences of both the registry and the registrars identified
several "lessons learned" which have been documented here as "Known
Issues".
...
... reaction.
The registry stores information about registered domain names and
associated name servers. A domain name ...
... certificates. The Shared Registration System
implemented by the NSI Registry requires digital certificates issued
by a commercial certification authority ...
... certification authority for both registrar clients
and public registry RRP servers. Both the registrar client and the
...
... RRP servers. Both the registrar client and the
public registry RRP server are authenticated when establishing an SSL ...
... in multiple instances of the "NameServer" parameter. The name servers
MUST have already been registered in the registry. Implementations
MAY allow specification of name servers associated with domains
...
... attribute.
- ID of the entity (either a registrar or the registry) that last
updated the domain name in the "updated by" attribute.
...
... identity of the current sponsoring registrar (the
registrar who must approve or reject the transfer request) is known
by the registry and does not need to be known by the requesting
registrar in advance of issuing the transfer request.
...
... registrar. Only the current sponsoring registrar of a domain name may
explicitly approve or reject a requested transfer. The registry MAY
implicitly approve or reject requested transfers after a fixed amount
of time.
...
... Authorization failed
Registrars may not view or alter data associated with either the
registry or another registrar. This response code is typically
returned when a registrar attempts to view or modify data belonging
...
... response code is typically
returned when a registrar attempts to view or modify data belonging
to either the registry or another registrar. A typical situation
includes doing a STATUS command for a domain registered to another
...
... active domains. The registry MUST not allow the registrar to delete
this server. All of the domain names ...
... registrar is adding a domain name that already exists in the
registry, a server that already exists in the registry, or an IP
address that is already being used by another server in the registry ...
... domain name that already exists in the
registry, a server that already exists in the registry, or an IP
address that is already being used by another server in the registry.
...
... registry, a server that already exists in the registry, or an IP
address that is already being used by another server in the registry.
Another possibility occurs when performing domain modifications and
...
... IP address of the
name server might not be unique. The registry MUST not allow IP
addresses to be used by more than one server.
...
... trying to modify an attribute of a server or a domain name that does
not exist in the registry.
543 Final or implicit attribute cannot be updated
...
... 543 Final or implicit attribute cannot be updated
The registrar is attempting to modify an attribute that is only
modifiable by the registry. Registrars can not modify final or
implicit attribute values.
...
... status. If the HOLD status was set by the registrar, the status can
be changed using the MOD command and the requested command can be
retried. If the HOLD status was set by the registry, the registrar
must contact the registry to change the status before the command can
...
... retried. If the HOLD status was set by the registry, the registrar
must contact the registry to change the status before the command can
be successful.
...
... domain of the
name server does not exist in the registry. It also occurs when the
user is trying to add a new name server to a domain name ...
... transferring a domain name, is attempted and the registrar does not
have sufficient financial standing with the registry to complete the
operation.
...
... name
server and the parent domain for the server does not exist in the
registry.
551 Parent domain ...
... operation. This occurs when a registrar tries to modify a server
whose parent domain is flagged as LOCK or HOLD in the registry.
552 Domain ...
... delete a domain that is
flagged as LOCK or HOLD in the registry.
553 Operation not allowed. Domain ...
... RRP STATUS command and
modified using the RRP MOD command. Both the registry and the
sponsoring registrar MAY view and change the status of a domain. The
...
... sponsoring registrar MAY view and change the status of a domain. The
criteria for status changes are highly dependent on registry and
registrar business models and are thus beyond the scope of this
specification.
...
... domain name can only be in this status.
When a registrar sets a domain name to REGISTRAR-LOCK, the registry
MUST automatically remove the ACTIVE ...
... removes the REGISTRAR-LOCK and other domain statuses, the registry
MUST automatically set the domain name status to ACTIVE ...
... domain at registration time.
The registry sets the domain to this status. The domain is modifiable
...
... domain cannot be modified or deleted by the registrar. The registry
MUST remove the REGISTRY ...
... registry
MUST remove the REGISTRY-LOCK status for the registrar to modify the
domain. The domain ...
... domain cannot be modified or deleted by the registrar. The registry
MUST remove the REGISTRY ...
... registry
MUST remove the REGISTRY-HOLD status for the registrar to modify the
domain. The domain ...
... hosting other domains.
Only the registry may set this status. The domain SHALL be included
in the zone file when in this status if the domain ...
...
; ABNF specification for Registry Registrar Protocol (RRP) v1.1.0
; Note that character string literals ...
... yesno = "Yes" / "No"
domainstatus = "Active" / "Registry-Lock" / "Registry-Hold" /
"Registrar-Lock" / "Registrar-Hold" /
...
... domainstatus = "Active" / "Registry-Lock" / "Registry-Hold" /
"Registrar-Lock" / "Registrar-Hold" /
"Registry ...
... consider developing offline reporting features to provide bulk data
for registrar reporting in a fashion suitable for the given
registry-registrar operating environment.
This version ...
... RRP do not include time zone identifiers and
SHOULD be interpreted as local registry time.
The protocol does not provide features for a registrar to become
...
... means outside of the protocol, such as electronic mail and/or
registry-provided reports, to inform registrars of transfer requests
and responses.
...
... elements of a command entity block and command
options. The NSI Registry's server-side implementation of the
protocol provides the additional flexibility of allowing order
...
... identifiers to track
transactions. The NSI Registry provides registrars with daily and
weekly reports that include time stamps in local registry ...
... Registry provides registrars with daily and
weekly reports that include time stamps in local registry time to
document and synchronize data on a per-registrar basis.
...
...
Misuse of the Registry Registrar Protocol can have catastrophic
operational consequences for registrants, registrars, and registries.
...
... Misuse of the Registry Registrar Protocol can have catastrophic
operational consequences for registrants, registrars, and registries.
As such, all registrars must be authenticated prior to all
...
... As such, all registrars must be authenticated prior to all
interactions with the registry. In addition, all data exchanged
between the registrar and the registry must be protected to avoid
...
... interactions with the registry. In addition, all data exchanged
between the registrar and the registry must be protected to avoid
unintended disclosure of information.
...
... Hubbard, K., Kosters, M., Conrad, D., Karrenberg, D. and J. Postel, "Internet Registry IP Allocation Guidelines", BCP 12, RFC 2050 ...