ENUM Validation Architecture

Mayrhofer, Alexander; Hoeneisen, Bernie

doi:10.17487/rfc4725

Cited by 4 publications

(6 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This document reuses terms from [RFC3261], [RFC5486], use cases and requirements documented in [RFC6461], and the ENUM Validation Architecture [RFC4725].…”

Section: Terminologymentioning

confidence: 99%

“…The definition of a Registrant is based on [RFC4725]. It is the end user, person, or organization that is the "holder" of the SED being provisioned into the Registry by a Registrar.…”

Section: Registrantmentioning

confidence: 99%

“…The definition of a Registrar is based on [RFC4725]. It is an entity that performs provisioning operations on behalf of a Registrant by interacting with the Registry via SPPF operations.…”

Section: Registrantmentioning

confidence: 99%

See 2 more Smart Citations

Session Peering Provisioning Framework (SPPF)

Cartwright¹,

Bhatia²,

Ali³

et al. 2016

View full text Add to dashboard Cite

show abstract

“…This document reuses terms from [RFC3261], [RFC5486], use cases and requirements documented in [RFC6461], and the ENUM Validation Architecture [RFC4725].…”

Section: Terminologymentioning

confidence: 99%

“…The definition of a Registrant is based on [RFC4725]. It is the end user, person, or organization that is the "holder" of the SED being provisioned into the Registry by a Registrar.…”

Section: Registrantmentioning

confidence: 99%

See 1 more Smart Citation

Session Peering Provisioning Framework (SPPF)

Cartwright¹,

Bhatia²,

Ali³

et al. 2016

View full text Add to dashboard Cite

show abstract

“…As described in RFC 4725 [9], usually only the Assignee of the E.164 number (or number range) has the right to register the corresponding ENUM domain name. Therefore, an ENUM validation process has to be applied before the ENUM domain name can be inserted into the DNS.…”

Section: Hoeneisenmentioning

confidence: 99%

ENUM Validation Information Mapping for the Extensible Provisioning Protocol

Hoeneisen¹

2007

Self Cite

View full text Add to dashboard Cite

This document describes an Extensible Provisioning Protocol (EPP) extension framework for mapping information about the validation process that has been applied for the E.164 number (or number range) that the E.164 Number Mapping (ENUM) domain name is based on. Specified in the Extensible Markup Language (XML), this mapping extends the EPP domain name mapping to provide an additional feature required for the provisioning of ENUM Domain Names.

show abstract

“…In the role model described in [15], the entity that performs this check is called the Validation Entity (VE).…”

Section: Introductionmentioning

confidence: 99%