U.S. ENUM Implementation ENUM Forum. Scope  Specifications Document  Tier 1 Contracting Entity Options  Tier 1 Structure Alternatives.

Slides:



Advertisements
Similar presentations
GNSO goals Bruce Tonkin Chair, GNSO Council Sao Paulo, 4 Dec 2006.
Advertisements

The ICANN Experiment CainetCainet Andrew McLaughlin.
CC1 ENUM LLC Presentation to the NANC March 15, 2005 Karen Mulberry Chairman
International Telecommunication Union ENUM Issues and Solutions Houlin Zhao Director Telecommunication Standardization Bureau International Telecommunication.
2001_03_28 SG A contribution– 1 Dept of State ITAC-T Advisory Committee SG-A Ad Hoc Meeting on ENUM March 28th & 29th, 2001 ENUM CONTRIBUTION TITLE: ENUM.
SG-A Ad Hoc - ENUM Jordyn A. Buchanan Register.com February 12, 2001.
2/12/2001 ENUM Administration Penn Pfautz AT&T
Support and Transparent Process for ENUM Designated Zone implementations for the USA Before the Dept of State ITAC-T Advisory Committee SG-A AdHoc Meeting.
PwC Simplification Study for the EU Commission Jean-Marc Cambien Senior Manager ITU Conference, 5 and 6 June 2003, Geneva © 2003 PricewaterhouseCoopers.
ATC Conference Call January 10, 2008 Thank you for joining the call. We will start the call shortly. Please enter * 6 to mute your line and # 6 to unmute.
ICANN/ccTLD Agreements: Why and How Andrew McLaughlin Monday, January 21, 2002 TWNIC.
The ENUM LLC March 11, 2004 CSCN ENUM Meeting Ottawa, Ontario Karen Mulberry Senior Project Manager, Numbering.
Identity Management Based on P3P Authors: Oliver Berthold and Marit Kohntopp P3P = Platform for Privacy Preferences Project.
International Telecommunication Union ITU Perspective on ENUM Robert Shaw ITU Internet Strategy and Policy Advisor ICANN Rio de Janeiro, Brazil March 25,
P3P: Platform for Privacy Preferences Charlin Lu Sensitive Information in a Wired World November 11, 2003.
THE PROJECT TEAM TYPICAL REQUIREMENTS AND RESPONSIBILITIES OF THE PROJECT TEAM TRADITIONAL TEAM ORGANIZATION AND VARIATIONS THE OWNER’S TEAM THE DESIGN.
Chapter 15: Business Entities
August 13-14, 2002 Washington, DC Gary Richenaker Chair ENUM Forum
Purpose of the Standards
Introduction to ICANN’s new gTLD program. A practical example: the Dot Deloitte case. Jan Corstens, Partner, Deloitte WIPO Moscow, 9 Dec 2011.
Understanding Active Directory
The McLaughlin Company What is a Joint Venture? First of all, let’s consider what a joint venture is. The following definition is.
1 IETF – ENUM US Government Briefing Richard Shockey IETF ENUM Work Group Chair Senior Technical Industry Liaison NeuStar, Inc Vermont Avenue N.W.
Interim Report Review Inter-Registrar Domain Name Transfers ICANN DNSO Names Council Task Force on Transfers Public Discussion on Transfers of gTLD Names.
Internal Auditing and Outsourcing
National Smartcard Project Work Package 8 – Security Issues Report.
OSIAM4HE Proposed org structure Authored by the strategy and organization team.
The Globalization of Business and the Dispute Resolution Environment by Robert F. Ruyak Chairman and CEO.
ENUM? “ Telephone Number Mapping (ENUM or Enum, from TElephone NUmber Mapping) is a suite of protocols to unify the telephone numbering system E.164 with.
Copyright © 2006 CyberRAVE LLC. All rights reserved. 1 Virtual Private Network Service Grid A Fixed-to-Mobile Secure Communications Framework Managed Security.
CC1 ENUM LLC The MCI Perspective Karen Mulberry Sr. Project Manager, Numbering November 8, 2004.
CcTLD/ICANN Contract for Services (Draft Agreements) A Comparison.
October 2005Bell Canada Network Planning 1 ENUM (tElephone NUmber Mapping) Update CSCN Chair Presentation to ISACC Information and Communications Technology.
National Smartcard Project Work Package 8 – Corporate Structures Report.
Joint Forum of Financial Market Regulators Forum conjoint des autorités de réglementation du marché financier Guidelines for Capital Accumulation Plans.
International Telecommunication Union Global ENUM Implementation Robert Shaw ITU Internet Strategy and Policy Advisor International Telecommunication Union.
Industry Canada 1 Bob Leafloor Colman Ho Peter Chau Industry Canada January 2003 (ENUM) T E lephone NU mber M apping.
CERTIFICATION In the Electronics Recycling Industry © 2007 IAER Web Site - -
ENUM Services and their Provisioning Submitted by VeriSign, Inc and Telcordia Technologies, Inc Available at
1 ENUM’s Role in VoIP IP Telephony Conference & Expo Miami February 12, 2004 Sheri Jenkinson VeriSign Communication Services Product Manager - ENUM
International Telecommunication Union ENUM Implementation Robert Shaw ITU Internet Strategy and Policy Advisor International Telecommunication Union ICANN.
Principles of International Commercial Arbitration Allen B. Green McKenna Long & Aldridge, LLP.
IRTP Part D PDP WG Items for Review. Items for Review Policy Development Process WG Charter GNSO WG Guidelines.
1 Chapter 33 International business Copyright © Nelson Australia Pty Ltd 2003.
6bone address registry proposal Bob Fink ESnet 17 July 2002 Yokohama.
INSTRUCTOR'S MANUAL Chapter 3 ESTABLISHING A BUSINESS.
Patrik Fältström. ITU Tutorial Workshop on ENUM. Feb 8, 2002, Geneva Explanation of ENUM (RFC 2916) Patrik Fältström Area Director, Applications Area,
NATIONAL CONFERENCE Intellectual Property Policies for Universities and Innovation dr. sc. Vlatka Petrović Head, Technology Transfer Office Acting Head,
Company: Cincinnati Insurance Company Position: IT Governance Risk & Compliance Service Manager Location: Fairfield, OH About the Company : The Cincinnati.
Review of CCWG-Acct 3 rd Proposal and ALAC Issues Alan Greenberg 04 December 2015.
6 Business Structures Khaled Sharif.
State of Georgia Release Management Training
1 February 8th, 2002 ITU ENUM Tutorial Stanislas Bourgain Autorité de régulation des télécommunications Unité Internet Service Interconnexion et Nouvelles.
Connecting for Health Common Framework: the Model Contract for Health Information Exchange Gerry Hinkley com July 18, 2006 Davis Wright.
Presentation by Laura Possessky, Esq. Gura & Possessky, PLLC Washington, DC (c) 2015 Gura & Possessky, PLLC1.
Update on ITU-T ENUM Activities Steven D. Lind AT&T SG-A ENUM - Ad Hoc February 12, 2001.
International Telecommunication Union ENUM Organizational Perspectives Richard Hill, for Houlin Zhao Director Telecommunication Standardization Bureau.
ENUM Tutorial ENUM Forum June 3, 2003 Steven D. Lind, AT&T GEN0075R0.
ENF/ERO ENUM Convergence Workshop Tony Holmes Chairman ETSI SPAN11 NAR BTexact Technologies Numbering Addressing & Routeing 9-10 January 2002 Standards.
Types of Business Structures
12.2 Conduct Procurements The process of obtaining seller responses, selecting a seller and awarding the contract The team applies selection criteria.
INTERCONNECTION GUIDELINES
An Exciting New Service
ICANN’s Policy Development Activities
Surveying and Mapping Industry Council Update
Office of the Registrar General
Beneficial ownership: Data collection and publication
Christopher Wilkinson Head, GAC Secretariat
PRE-QUALIFIED AND PREFERRED SUPPLIER PROGRAM
ENUM Status of US Implementation
Presentation transcript:

U.S. ENUM Implementation ENUM Forum

Scope  Specifications Document  Tier 1 Contracting Entity Options  Tier 1 Structure Alternatives

ENUM Forum Specifications  Reference Architecture  Tier 1 Registry Operations, Security, & Admin  Tier 1 Performance Specifications  Privacy Considerations  Provisioning  Registrar Requirements  Authentication & Authorization  Tier 2 Guidelines  Conflict Resolution  Issues Out of Scope

Reference Architecture Reference Architecture Tier 1 Registry Tier 0 Root Tier 2 Provider Registrant Registrar

Reference Architecture  Registrar  Registrant  Registry  Tier 1 Registry  Tier 2 Service Provider  Interfaces  Tier 2 contains the NAPTR records or delegations  Does not address non geographic numbers  Issue:  One or More Tier 1 Providers  Delegation at Tier 0 by NPA

Tier 1 Operations  Shared Registration System (SRS)  Registry Database  Zone Information (aka zone files)  ContactInfo (aka WhoIs)  Reporting, backup, escrow & performance requirements  Security

Tier 1 Security  DNS  TSIG, DNSSec  Protocol  Physical  Network  Backup  Auditing and Reporting

Tier 1 Administrative Aspects  Registry  Contracting Entity  Registrar  Tier 0 Interaction  US Government  Dispute Resolution  Data Collection and Privacy

Tier 1 Performance Aspects  DNS Performance  Availability  Update  Performance  EPP Interfaces

Privacy Considerations  Registrant Choice  Privacy Analysis  Open Disclosure of Registrant Information in DNS  Information Handling During Registration and Provisioning  ContactInfo  Fair Information Practices

Provisioning Tier 2 Nameserver Registrar Tier 1 Registry Registrant Application Service Provider Authentication & Validation Entities

Registrar Requirements  Registrant Validation & Authentication  Dispute Resolution  Registrar Infrastructure Requirements  Interactions of the parties  Parties Requiring A & A  Recommended Practices & Requirements  Information Flows Requiring A&A  Various Scenarios

Authorization and Authentication  Parties Requiring A & A  Recommended Practices & Requirements  Information Flows Requiring A&A  Various Scenarios

Tier 2  Guidelines – NOT Requirements  Tier 2 may be self provided or from a commercial 3 rd party  Interfaces & Interactions  Performance Recommendations

Conflict Resolution Process  General Principals  Process  Initiation  Identification  Timeframe  Transfers  Remedies  Fees

Timeline  Feb 2003 – Baseline Specification released  Meetings through 2003  Dec 2003 – Release of ‘Tier 1 Contracting Entity and Architectural Alternatives’ a.k.a. 6001_1

Tier 1 Contracting Entity  Desired Attributes:  Short implementation timeframe  Light Government Oversight  Encourage Competition  Open Standards  Intellectual Property is owned by the contracting entity  Minimize procurement and operation cost

Tier 1 Contracting Entity  Concerns:  Preserve National Sovereignty  Support Competition  Promote Innovation  Protect User’s Security and Privacy  Minimize Regulation  Preserve Opportunity for Alternative Deployments  Allow Interoperability  Preserve Stability and Security

Tier 1 Contracting Entity  Contracting Considerations:  US Government interaction with Tier 0  Actual procurement process  Ownership of the intellectual property  Compliance oversight  Operational integrity  Policy development for procurement and ongoing operations

Tier 1 Contracting Entity – Alternatives Considered  Government Procurement  Industry Limited Liability Company

Option 1 – Government Procurement  Government Procurement through Simplified FAR  Accepted and understood  Precedent -.us  Can it provide the desired attributes?  Short timeframe- Unclear  Light government oversight- Unclear  Low cost- Unclear, but at least similar to.us  Competition encouraged- Yes  Intellectual property- Easily retained by USG  Open standards & best practices- Yes

Option 1 – Government Procurement - Advantages   Little or no industry cost   Anti-trust protection   Contract liability protection   Well defined and understood process

Option 1 – Government Procurement – Disadvantages   Unclear Statutory Authority   Agency Lead Unclear   Not Currently Funded   High Complexity and / or cost   Difficult to Coordinate with Industry   USG Prefers light touch with new / emerging technologies   Multinational coordination with other NANP countries is required if single or skinny Tier 1 selected

Option 2 – Industry LLC  Industry LLC  Separate and distinct legal entity  Responsible for  RFP creation, issuance, and evaluation  Contract negotiation & execution  Vendor oversight and change management  Systems and data changes  Emerging issues management

Option 2 – Industry LLC  Industry LLC  Attributes  Liability protection for members  Designated and recognized contracting entity  Level forum for joint venture for competitors  Unregulated yet authorized to conform to regulatory directives  Easy Access for new entrants  Not For Profit  Government may choose oversight role  Active  Tacit  Allows involvement of other NANP countries

Option 2 – Industry LLC  Advantages  Expect good reception from USG  Quick implementation possible  Limits industry liability  Good precedent (LNP)  Ability to insure fairness and unbiased oversight  Contractual authority with all qualified vendors  Can issue RFP, award a contract  Can designate equal terms for participants who use services from selected vendor  Operates in an open environment  Non Aligned with any market segment  May represent any of the NANP countries  Government coordination may be through the LLC or industry consortium

Option 2 – Industry LLC  Disadvantages  Members responsible for initial funding and operational costs  Fewer members, larger individual burden  Requires independent legal assistance  Initial membership operating agreements  Ongoing advice  May have issues establishing industry payment / cost recovery mechanisms

Option 2 – Industry LLC  Can an industry LLC provide the desired attributes?  Short Timeframe- Yes  Light Government Oversight- Yes  Low Cost- Yes  Competition Encouraged- Yes  Intellectual Property- Yes  Open Standards & Best Practices- Yes

Tier 1 Architecture  Two issues  Scope of Tier 1  Tier 0 Delegation Alternatives

Tier 1 Architecture  Scope of Tier 1  US Numbers registered in single Tier 1 for all of NANP  US numbers registered in single Tier 1 for US  US numbers registered in multiple Tier 1s for sets of NPAs  Tier 0 Delegation Alternatives  Delegation of 1+NPA  Delegation of all of country code 1

Tier 1 Architecture  Five Possible Solutions:  Single Tier 1 for all NANP countries  Single Tier 1 in US  With delegation from Tier 0 by 1+NPA  With delegation from Skinny Tier 1  Multiple Tier 1 operators in US  With delegation from Tier 0 by 1+NPA  With delegation from Skinny Tier 1

Single Tier 1 for NANP Countries  Assumes:  All of country code 1 is delegated to a single Tier 1  All participating NANP countries can/will form a single contracting entity Tier 0 NANP Tier 1 Tier 2

Single Tier 1 for NANP Countries  Advantages  Only country code 1 need be added to Tier 0  Only one representative for NANP countries needs to deal with tier 0  Registrars that do business in more than one NANP country only need to be certified once  Registrar interfaces with single Tier 1 for many NANP countries  May simplify non geographic number inclusion  Disadvantages  All 19 NANP countries need to agree/acquiesce on Tier 1 entity operation  All NANP countries must agree/acquiesce to selection of Tier 1 entity  Restricts business opportunity to single entity at tier 1 level  Creates risk of relying on single business entity Tier 0 Country Code 1 Tier 1 Tier 2

Single Tier 1 for US  Requires either delegation from Tier 0 by 1+NPA or Skinny Tier 1 Tier 0 US Tier 1 Tier 2 Delegation by 1+NPA Tier 0 US Tier 1 Tier 2 Delegation of country code 1 Skinny Tier 1 Delegation by NPA

Single Tier 1 for US – Delegation of US 1+NPAs from Tier 0 Tier 0 US Tier 1 Tier 2 Delegation by 1+NPA  Advantages  No distribution of US NPAs required between multiple US Tier 1 entities  US can participate in global ENUM without agreement or coordination of other NANP countries  No negotiation required on loading US NPAs into Tier 0  Disadvantages  All NPAs from the US must be entered into tier 0  Restricts business opportunity to single entity at tier 1 level  Does not resolve non geographic number inclusion  Creates risk of relying on single business entity

Single Tier 1 for US – Delegation from within a skinny tier 1 Tier 0 US Tier 1 Tier 2 Skinny Tier 1 Delegation by NPA  Advantages  No distribution of US NPAs required between multiple US Tier 1 entities  Only Country code 1 must be loaded into Tier 0  Only one representative for NANP countries needs to deal with tier 0  Individual NANP countries deal with a single tier 1 provider  MAY simplify inclusion of non geographic numbers by placing them directly in skinny tier 1  Disadvantages  Restricts business opportunity to single entity at skinny tier 1 level and at the US tier 1 level  Creates risk of relying on single business entity at skinny tier 1 and US Tier 1 levels  Does not resolve non geographic number inclusion in ENUM  All NANP countries must agree/acquiesce on using a skinny tier 1 operator  All NANP countries must agree/acquiesce on selection of skinny tier1 entity

Multiple Tier 1 Operators in the US  Assumes:  US 1+NPAs are delegated to multiple tier 1 entities from Tier 0  OR  All of country code 1 is delegated to a single skinny Tier 1 Tier 0 US Tier 1s Tier 2 Delegation by 1+NPA Tier 0 Delegation of country code 1 Skinny Tier 1 US Tier 1s Tier 2 Delegation by NPA

Multiple Tier-1 Operators in the US Direct delegation from Tier 0  Advantages  Promotes multiple business opportunities in the tier 1 registry  US can participate in global ENUM without agreement from other NANP countries  No negotiation needed to load US 1+NPAs into Tier 0.  Only one representative for NANP countries needs to deal with tier 0  Reduces risk of relying on single business entity for Tier 1  Disadvantages  1+NPAs need to be distributed among Tier 1 providers  1+NPAs for US would need to be entered into Tier 0  Introduces additional operational and administrative interfaces for Registrars and Tier 2 operators  Does not resolve non geographic number inclusion in ENUM Tier 0 US Tier 1s Tier 2 Delegation by 1+NPA

Multiple Tier-1 Operators in the US Direct delegation from skinny Tier 1  Advantages  Only Country code 1 must be loaded into Tier 0  Only one representative from NANP countries needs to deal with Tier 0  Individual NANP countries deal with a single skinny Tier 1 provider  MAY simplify inclusion of non geographic numbers by placing them directly in skinny tier 1  Promotes multiple business opportunities in Tier 1 Registry  Disadvantages  NPAs need to be distributed among Tier 1 providers  Restricts business opportunity to single entity at skinny tier 1 level  Creates risk of relying on single business entity at skinny tier 1  Does not resolve issues regarding non geographic number inclusion in ENUM  All NANP countries must agree/acquiesce on using a skinny tier 1 operator  All NANP countries must agree/acquiesce on selection of skinny tier1 entity  Introduces additional operational and administrative interfaces for Registrars and Tier 2 operators

Summary  Endorsement of support for LLC  No consensus on architectural alternatives  Any solution which involves the delegation of country code 1 from Tier 0 will require agreement from all 19 NANP countries  Delegation of US NPAs from Tier 0 may require negotiation with Tier 0  How many registries should operate for those 1+NPAs in the US?

Status  The ENUM Forum met with NTIA and the FCC on Jan 21  Supports the development of and industry LLC  Did not express a preference for either a single or multiple Tier 1 approach  Believes that decisions are best left to industry as long as the conditions and principals stated in the February 2003 letter are upheld  US Government in the process of contacting other countries in the NANP to determine if a consensus opinion can be reached  US Industry is in the process of establishing an LLC to initiative the Tier 1 procurement process

Contacts  ENUM Forum Chair Gary Richenaker Telcordia Technologies Tel:  ENUM Forum Vice Chair Steve Lind AT&T Tel:  ENUM External Communications Group Chair Bob Bownes Seiri Tel: