ENUM Context Document(An Overview)

ENUM Working Group 1 (2003)Contact: Manager Numbering ACA

DRAFT COPY – AEDG Distribution Only

Presentation Outline

• ACA Perspective

• Overall Purpose of the Context Document

• A Guide to the Context Document

• ENUM?

• The Need for an ENUM Trial

• A Trial in Three Parts

• The Trial Lifecycle Model

• Trial Objectives (Overview Only)

• Reference Architecture

• The Bottom Line – What does it mean to be a participant in the proposed Trial?

• What is it?

• General Operation & Terminology

• Privacy and ENUM

• Example ENUM Applications?

• Business

• Regulatory

• Technical

ACA Perspective

What is the ACA’s role?

• The terms of reference of the AEDG state (in part):

• “The Australian ENUM Discussion Group is a consultative and advisory body designed to assist stakeholders in responding to the policy, regulatory, technical and commercial implications associated with the introduction of ENUM. ”

What is the ACA’s role? (continued)

• The ACA’s interest will be primarily focused on looking at the regulatory implications of the introduction of ENUM

• The ACA will facilitate the exploration of ENUM issues by bringing industry together in the AEDG

The context document

• The ‘context’ document - designed to establish an overarching framework for trials.

• It forms part of the process of developing a framework in which to test regulatory and policy issues.

• Trials are industry trials not ACA trials.

What has the working group done?

• At the last ENUM discussion group meeting on 5 June 2003 participants agreed to form a working group to develop a statement of context regarding the Tier 1 trial.

• The working group has since met 3 times and has been assisted by ACA consultant Peter Mikelaitis.

The status of the context document

• The context document is in draft form and is the product of the working group.

• The context document does not represent official ACA policy and some ACA comments are yet to be reflected in the draft document.

• The context document sets out a framework. It does not deal with issues at a micro level.

• Some issues may need to be referred to additional working groups for development (eg numbering, privacy and security).

• Over to Peter…………….

Overall Purpose of the Context Document

To establish a framework for co-operation that will allow (in a non constraining way) different groups to safely and legally develop and test new ENUM based applications, services and associated technologies.

1) A strategy for the Trial involving a three part Trial Structure

2) A “living” list of trial objectives

3) Responsibilities for making a Trial happen (Lifecycle Model)

4) A Reference Architecture with key interfaces identified and described

5) Some Trial System Design constraints (i.e. single Tier 1 with multiple Tier 2’s and use of EPP)

6) The implementation of a Base Capability (or Service) for Tier 1 and Tier 2 of the ENUM Trial System to provide a stable experimental platform

By proposing(mostly in the definitive language of a Specification)

and “keeping in front of us” the fact that we are dealing with a Trial System and not a Commercial System

A Guide to the Context Document

• Describes what ENUM is (see section 1.4)

• Why we may need a Trial Facility.

• How to make the Trial Happen.

• Who is responsible.

• What must the ENUM Trial System do.

The Reference Architecture of the ENUM Trial System (ETS)

Within the context of

The Tier 1 and Tier 2 Base Service of the Trial System

(sections 5, 6 and 7)

Identify and describe the specific Top Level Behaviour (requirements) of

• The Need for a Trial (section 1.5.1)

• Trial Objectives (section 1.5.4)- Business- Regulatory- Technical

• Strategy (section 1.5.2)

• Trial Staging (section 1.5.3)

Lifecycle Model (section 4)

To the Bottom Line?

And who bears the cost?

ENUM (The Standard)

ENUM (What is it?)

ENUM General (How to Use it?)

ENUM is a technology for mapping phone numbers to a list of other “numbers” and “addresses”… That is all it is, and it is nothing new

It’s claim to fame is that it sits within the DNS and can use this infrastructure to provide E.164 number to URI mapping in a universal way that can be rapidly deployed

• Service to support Internet/PSTN telephony

• Number portability databases

• Universal identification scheme

• ?.. One of the general goals of the Trial

Possible uses

Then why the fuss?

ENUM System

Using ENUM (General)

NetworkNetwork

Query: 613 1234 5678

Response for 613 1234 5678

- email: pm@mikl.net- sip:pm@mikl.net,- fax#,- mobile#,- web page- other..

Registrant:

RegistrantRegistrant

a

b

Anyone can query a number

And obtain the information bound to the number to “provide a service?”

c• Somebody who

“owns” a number, say ( 613 1234 5678)

• May enter information to be “bound” to that number

a

DNS

b

c

ENUM System

Using ENUM (More Detail)

NetworkNetwork

RegistrantRegistrant

a

Registrar Registry DNS DNS

DNS

DNS

Other DNS databases (anywhere)

b

c

Introducing the Terminology of the Reference Architecture

A standard interface using EPP

ENUM System

Using ENUM (Remember Privacy)

DNS

Because its based on DNS anyone can query

the ENUM System

Response- sip:pm@mikl.net,- fax#,- mobile#,- other..

NetworkNetwork

And absolutely anyone can obtain

the information bound to your

“phone” number

ENUM System

Using ENUM – Example Only (PSTN/Internet Telephony)

D# D#

D#

DNS

#

#

PSTN

Dial: 613 1234 5678

Query8.7.6.5.4.3.2.1.3.1.6.e164.arpa

#2

1

Internet Number, route to gateway G#

(contains SIP functions)

3

4

Response- email: pm@mikl.net- sip:pm@mikl.net,- fax#,- mobile#,- web page- other..

G# 5

Establish telephony session using

- sip:pm@mikl.net,

Using ENUM (Other Applications?)

Number Portability

Universal Identifier

One “phone” number can be used to access the URI’s for all services that the owner of the number “subscribes” to

The information bound to the phone number could be used to provide this service

Follow Me

Priority information indicating which service someone can be contacted at any particular time could be used as a basis for this service (across all services)

Other ?.... This is a trial objective

The Need for an ENUM Trial

ENUM technology may provide new areas of opportunity

• Registrar software and systems

• Shared Registry technologies

• Mobile Services

• Reduced infrastructure costs

• Internet telephony

• Internet/PSTN telephony

• Other…

The introduction of a national ENUM service may affect the efficiency of national industry in ways that are as yet not understood

DirectIn-direct

Heard it all before?

Then check out the detailed objectives in section 1.5.4 of the Context Document.

Or.. For a quick summary look at these slides

Business ObjectivesRegulatory ObjectivesTechnical Objectives

Strategy (A Trial in Three Parts)

Tier 1 established with a Base Service. It is allocated E.164 numbers (part of the Numbering Plan but currently unallocated). Tier 2 operators register with Tier 1 and receive E.164 numbers

Identify and solve all of the problems that may be an impediment to the testing and ultimate implementation of applications and services that require “connection” crossover between the Australian PSTN and the “internet”.

Part 1 - Limited

Part 2 – PSTN/Internet “Crossover” Studies

If appropriate extend the Part 1 trial infrastructure to include “crossover” between internet and PSTN “connections”.

Part 3 – Internet/PSTN Working

See section 1.5.3 “Trial Staging” for further detail

Lifecycle Model for the Trial

RFT Evaluation(s)RFT Evaluation(s)

ProjectStartup

SelectAT1OP

ENUM Tier 1System and OrgImplementation &

Test

RFT Evaluation(s)

0 1 2Phase 1 Phase 2 Phase 3 3 Phase 4 4 Phase 5 5 Phase 6 6 Phase 7 7 Phase 8 8 Phase 9 9

dd/mm/yy dd/mm/yy dd/mm/yy dd/mm/yy dd/mm/yy dd/mm/yy dd/mm/yy dd/mm/yy dd/mm/yydd/mm/yy

Outcomes:- Top Level Requirements Specification (Context Document)

ENUM Trial TopLevel Requirements

ENUM DetailedRequirementsSpecifications

RFT for AT1OPOutcomes- Detailed Requirements Specifications (also called Technical Specifications)

Outcomes- Request For Tender Outcomes

- RFT Responses (includes Tier 1 System Top Level & Detailed Design)

Rev 0000.02

Outcomes- AT1OP selected

Outcomes- Tier 1 organisation and processes established- Tier 1 Hardware & Software built, installed & tested

Outcomes- TBA

Outcomes- Evaluation Reports- Other (TBA)

Responsibility- ACA/AEDG

Responsibility- ACA

Responsibility- ACA/AEDG

Responsibility- ACA/AEDG

Responsibility- AT1OP ACA/AEDG

Responsibility- ACA/AEDG

Responsibility -ACA

Trial Evaluation

ENUM Australian Trial

Trial Objectives (Business)

• New Applications or services

• Business opportunities or are they strategic?

• Business Models – Finance

• Business Models – Administrative and procedural.

• Customer behaviour for the new applications

• Other….

Business Objectives

A “living” List

Trial Objectives (Regulatory)

• Service Availability

• Basic Australian ENUM Service Structure

• PSTN Aspects (e.g. “connection crossover”)

• Numbering Aspects (e.g. “ownership” of numbers)

• Privacy

• Illegal Business Operations (e.g. overseas businesses with an electronic “shopfront” in Australia)

Regulatory Objectives

A “living” List

Trial Objectives (Technical)

• General

• Tier 1 Registry Operator

• Tier 1 Registrar

• Tier 2 Operator

Technical Objectives

A “living” List (section 1.5.4)

ENUM System

Remember This? (Using ENUM)

NetworkNetwork

Query: 613 1234 5678

Response for 613 1234 5678

- email: pm@mikl.net- sip:pm@mikl.net,- fax#,- mobile#,- web page- other..

Registrant:

RegistrantRegistrant

a

b

Anyone can query a number

And obtain the information bound to the number to “provide a service?”

c• Somebody who

“owns” a number, say ( 613 1234 5678)

• May enter information to be “bound” to that number

a

DNS

b

c

AT2OP

AT1OP (Australian Tier 1 Operator)

AT2OP (Australian Tier 2 Operator)

RRO(Potential Tier 2 Operators

Register here)

AA1 (Top Level Management of AT1OP)

TT1(Management)

ACA

RIPE

Registrant-O

TT2(DNS Transfers

- TBA)

Registrant-U

RRU(Users Register here)

ENUM User

This DNS Querypath is beyond thescope of thecurrent Trialproposal

AR1(1.6.e164.arpa delegation &

Trial international issues

DN1(E.164 DNS Queries)

AEDG

Provisioningand Security

DNS Name Resolutionand Security

Operationsand Security

Registrar-T1 T1REG (Tier 1 Registry)

RT1

Registrar-T2 T2REG (Tier 1 Registry)

RT2

Trial System (Reference Architecture)

Types of Base Service Top Level Requirements (Business)

• Finance Model• Administrative and Reporting Requirements• Other (TBA)

The Tier 1 (and 2) Base Service must implement specific items in some or all of the following types of requirements

Business Requirements

Types of Base Service Top Level Requirements (Technical)

• Functional Requirements (Operations)• Administrative and Reporting Requirements• Design Requirements (Any constraints on

design)• Physical Requirements • Environmental Requirements• Security Requirements• Privacy Requirements• Performance Requirements• Reliability Requirements• Availability Requirements• Maintainability Requirements• Documentation Requirements

The Tier 1 (and 2) Base Service must implement specific items in some, or all of the following types of requirements

Technical Requirements

Types of Base Service Top Level Requirements (Other)

• To Be Advised (TBA)

Anything that doesn’t fit into Business or Technical;

Other Requirements

The Bottom Line (Part 1)

• There is one Tier 1 Operator

• The Tier 1 Operator is selected and managed by ACA

• The Tier 1 Operator must provide the Base Service (sections 5,6,7 of the Context Document) by meeting specific Business, Technical, Security and Privacy Requirements.

• The Tier 1 Operator is required to develop and test new applications, services and support infrastructure while maintaining the Base Service

• There are many Tier 2 Operators

• Both the Tier 1 and Tier 2 Operators must implement their systems so that the Registrar and Registry functions are clearly separated in accordance with the Extensible Provisioning Protocol (EPP)

• Tier 2 Operators must register (at the RRO interface) with the Tier 1 Operator

• Tier 2 Operators are required to provide periodic reports to ACA on the progress of the trial (from their perspective)…

The Bottom Line (Part 2)

• Tier 2 Operator reports shall be via the Tier 1 Operator

• Tier 2 Operators must meet all of the Security and Privacy Requirements that are specified for the Tier 1 Operator, but they may use different technologies

• Tier 2 Operators will be allocated a block of E.164 numbers for their use during the trial. These are called numBlk0 numbers

• These numbers cannot be transferred between Tier 2 Operators

• Normal users (Registrants-U) will register with Tier 2 Operators only

• Tier 2 Operators will “give” each of their Registrant-U’s one or more E.164 numbers to “own” for the trial

The Bottom Line (Part 3)

• Registrants-U will enter/edit/delete information associated with the E.164 numbers that they own (i.e. at the RRU interface). Note that use of the RRO interface is not precluded. It is just not part of the Base Service

• The Tier 1 Operator will control another block of numbers for portability studies

• These are called numBlk1 numbers

• A Tier 2 Operator will be allocated (upon request) a group of numBlk1 numbers

• For a period nominated by the Tier 1 Operator. A Registrant-U is given “ownership” of a numBlk1 number by the Tier 2 Operator initially controlling that number

• A Registrant-U “owning” a numBlk1 number can register that number with any Tier 2 Operator and enter, edit and delete the records associated with it

The Bottom Line (Part 4)

• A Registrant-U owning a registered numBlk1 number can transfer that registration to any other Tier 2 Operator

• The Tier 1 and Tier 2 Operators must determine the detail of the procedures and protocol necessary to automatically support the number transfer described above

Extra Information

The following slides contain additional information that the reader may find useful

Uniform Resource Identifier (URI)

• Uniform Resource Identifiers (URIs, aka URLs) are short strings that identify resources in the web: documents, images, downloadable files, services, electronic mailboxes, and other resources.

• They make resources available under a variety of naming schemes and access methods such as HTTP, FTP, and Internet mail addressable in the same simple way.

See http://www.w3.org/Addressing