ietf 63 enum validation v01

ENUM validation architecture & friends: 

ENUM validation architecture andamp; friends Alex Mayrhofer enum.at / 3.4.e164.arpa alexander.mayrhofer@enum.at Bernie Höneisen SWITCH / 1.4.e164.arpa hoeneisen@switch.ch draft-mayrhofer-enum-validation-arch-00 draft-hoeneisen-enum-validation-epp-01 draft-lendl-enum-validation-token-00

Motivation & Goals: 

Motivation andamp; Goals Motivation: Solving validation is crucial for ENUM deployment Major reason why trials precede production Validation is the major difference between ENUM and 'ordinary' domain registration Validation definition and requirements currently vague Common view considered useful Major Goals: Common understanding Terminology, Processes, Roles, … Keeping entropy low Minimize number of solutions addressing same problem Prevent reinventing the wheel – foster deployment instead

validation draft orientation map: 

validation draft orientation map Requirements Role model Process andamp; trust assumptions validation data transport validation data format SOAP? IRIS? alternative formats? Other?

Disclaimer: 

Disclaimer It is out of scope of these documents how an actual validation is performed ('validation method') The documents just attempt to provide a generic framework to base validation processes and communication on.

ENUM Provisioning Model & Roles: 

ENUM Provisioning Model andamp; Roles ENUM Registry ENUM Registrar VE Registrant / Assignee NAE trust relation registration number assignment ENUM management validation Legend VE: Validation Entity NAE: Number Assignment Entity draft-mayrhofer-enum-validation-arch-00 E.164 number assignment verification

Validation Requirements: 

Validation Requirements The ENUM domain name corresponds to an assigned E.164 number The corresponding E.164 number is within a number area approved to be used with ENUM The registration of the ENUM domain name is authorized by the Assignee of the corresponding E.164 number The Registrant of the ENUM domain name is identical to the Assignee of the corresponding E.164 number draft-mayrhofer-enum-validation-arch-00

Initial vs. recurring validation: 

Initial vs. recurring validation Initial Validation Verify requirements before registration of the ENUM Domain takes place Recurring Validation (Re-Validation) Verify that requirements are still satisfied usually making use of data acquired during initial validation domain is to be removed when corresponding E.164 number is e.g. revoked

Registration process assumption: 

Registration process assumption ENUM Registry ENUM Registrar VE Registrant / Assignee NAE trust relation registration number assignment ENUM management validation E.164 number assignment verification Legend VE: Validation Entity NAE: Number Assignment Entity draft-mayrhofer-enum-validation-arch-00 2 1 3 4 5

Transport / data format extension framework: 

Transport / data format extension framework EPP domain EPP EPP validation framework draft-hoeneisen-enum-validation-epp-01 draft-lendl-enum-validation-token-00 Scott's EPP RFCs Draft-hoeneisen-enum-validation-epp-01 / draft-lendl-enum-validation-token-00

EPP transport: 

EPP transport Framework for Transport of validation information along with the EPP Domain object Elements for validation information itself are out-of-scope of this document Example for better readability included enables usage of different locally adjusted validation information elements or 'tokens' draft-hoeneisen-enum-validation-epp-01

Validation Token: 

Validation Token Conveys information about a validation E.164 Number (obviously) Contact information (in the style of EPP and E.115) Serial, validation method, validator, expiration … XML schema Optional cryptographic signature Non-repudiation Authenticity Supports trust relation between VE and registry To be embedded in transport protocols EPP (Bernie's draft, enum.at implementation) SOAP? Email? HTTPS? In productive use for 3.4.e164.arpa. Probably useful for other purposes (number porting?) draft-lendl-enum-validation-token-00

Next steps: 

Next steps How to proceed with draft-mayrhofer-enum-validation-arch ? WG item? Feedback requested on documents – in particular from folks working on ENUM provisioning implementations