This section explains what data we store for ENUM registrations, how that data is structured and the individual rules for the data we hold.

The basic data structure has an account for each ENUM registrar and the ENUMs they have registered. Each ENUM will have a VA token associated with it representing the registrant's data and its nameservers.
 



The register contains the following objects that can be processed by EPP:

• Enum Registrations. An ENUM registration represents a contiguous range of telephone numbers belonging to a single legal entity
• Nameservers. Nameserver details (name and ip addresses) are held in separate registry objects that can be referred to directly by their identifiers. Nameserver objects are specific to the registrar that the ENUM registrations that refer to them are on.
• Tokens. The token object contains the details of the validation agency token that was provided upon registration, renewal or registrar change.