An ENUM Registry Type for the Internet Registry Information Service (IRIS)
Extracted elements (30)
Privacy label attributes (private, denied, doNotRedistribute, specialAccess) are attached to individual result fields rather than the entire response, allowing fine-grained control over which data elements may be published or redistributed based on the requestor's access level.
This registry type uses only the basic TLS server authentication method for BEEP transport as described in IRIS-BEEP (RFC 3983), and uses the default BEEP message pattern.
Any one ENUM status value MUST NOT imply other status values; for example, <reserved> does not imply that creation is prohibited — a separate <create disposition='prohibited'/> element must also be present.
For the 'e164' entity class in <lookupEntity>, clients SHOULD remove all non-digit characters between the digits of an E.164 number, and servers MUST ignore any non-digit characters between the digits (e.g., '+1 703 555 1234' is interpreted as '+17035551234').
If the <inDomain> element or domain part of <exactMatch> contain non-ASCII characters, they MUST be normalized according to the processes of RFC 3491 (Nameprep).
In a <contact> result, if phone or fax begins with a '+' character it MUST be a number defined by E.164; the E.164 format is RECOMMENDED. The <country> element SHOULD be a 2-letter ISO 3166 country code.
Privacy label boolean attributes (private, denied, doNotRedistribute, specialAccess) SHOULD be used in accordance with the level of access being granted the recipient of the data — 'private'/'denied' for anonymous/low-access users, 'doNotRedistribute'/'specialAccess' for authenticated high-access users.
The application service label (S-NAPTR) associated with this registry type MUST be 'EREG1', the abbreviated form of the URN urn:ietf:params:xml:ns:ereg1.
The dateTimePrivacyType element contents MUST be specified using the 'Z' indicator for Coordinated Universal Time (UTC).
The <hostName> element content MUST conform to RFC 1123; <ipV4Address> MUST conform to a valid IPv4 host address per RFC 791; <ipV6Address> MUST conform to a valid IPv6 host address per RFC 3513.
The <inDomain> element in the contactSearchGroup MUST only contain a valid domain name (no '@' symbol), and matching SHOULD take place only on the domain given with no partial matches on substrings or parent domains.
The <nameServer> element within an <enum> result MUST contain an entity reference to a referent of type <host>.
When a server returns the <languageNotSupported> error, it MUST list the languages from the query that are not supported using <unsupportedLanguage> child elements.
Privacy label types (dateTimePrivacyType, stringPrivacyType, normalizedStringPrivacyType, tokenPrivacyType, enumStatusType) are nillable elements that MUST have boolean attributes 'private' or 'denied' when present without content, and MAY carry 'doNotRedistribute' or 'specialAccess' when present with content.
The <communicationServiceProvider> result represents an ENUM domain service provider, carrying serviceInstance, organizationName, legalId, cspId, capability flags (line/signal/data/voice/other), and contact group references.
The <contact> result represents a contact registration, carrying contactHandle, commonName, language, type (person/organization/role/other), organization, legalId, eMail, sip, postalAddress, phone, fax, lifecycle datetime fields, and translatedContact references.
The <enum> result represents an ENUM domain assignment and includes child elements for e164Number, enumHandle, nameServer (entity references to <host>), registrant, status, registry/registrar/validationEntity references, communication service provider references, and lifecycle datetime fields.
The enumStatusType defines lifecycle statuses for ENUM domains including: reserved, create, active, inactive, dispute, delete, transfer, renew, update, addPeriod, renewPeriod, autoRenewPeriod, transferPeriod, redemptionPeriod, restore, and other; each may carry actor (registry/registrar), disposition (prohibited/pending), and subStatus attributes.
The <findEnumsByContact> query finds ENUM domains by searches on contact fields, supporting search by contactHandle or contactSearchGroup fields, with an optional <role> element to constrain by the contact's role (registrant, billingContact, technicalContact, etc.) and optional <language> hints.
The <findEnumsByE164> query finds ENUM domains by searching on prefixes of E.164 numbers, with an optional <specificity> child element that narrows the search to numbers that are either more specific (more digits) or less specific (fewer digits).
The <findEnumsByHost> query finds ENUM domains hosted by a name server, constrained by host name, host handle, IPv4 address, or IPv6 address of the name server.
The <host> result represents a nameserver registration with fields: hostHandle, hostName (MUST conform to RFC 1123), ipV4Address (MUST conform to RFC 791), ipV6Address (MUST conform to RFC 3513), hostContact entity references, and lifecycle datetime fields.
The <lookupEntity> operation supports entity classes: host-name, host-handle, e164, enum, enum-handle, contact-handle, ipv4-address, ipv6-address, registration-authority, validation-entity, csp, and validation-event; all names in these entity classes are case insensitive.
The <registrationAuthority> result represents a registry or registrar entity, carrying serviceInstance, organizationName, legalId, a role indicator (registry/registrar/other), and contact group references.
The <validationEntity> result represents an entity responsible for validating ENUM domains against E.164 registrations, carrying serviceInstance, organizationName, legalId, and contact group references.
The <validationEvent> result records a validation event for an ENUM domain, carrying serial, methodId, validationEntity reference, registrar reference, executionDateTime, and expirationDateTime.
This document registers the BEEP Profile URI 'http://iana.org/beep/iris1/ereg1' with IANA in addition to the registration provided in IRIS-BEEP (RFC 3983).
This document registers the S-NAPTR application service tag 'EREG1' with IANA, per the IANA considerations defined in IRIS (RFC 3981).
This document registers two XML namespace URNs with IANA: urn:ietf:params:xml:schema:ereg1 (the XML Schema from Section 4) and urn:ietf:params:xml:ns:ereg1 (the XML namespace), per RFC 3688.
This document introduces no new security considerations beyond those specified in IRIS (RFC 3981). Implementers should consult that document for applicable security precautions.