ENUM Registry architectures - Some Canadian options

Slides:

Advertisements

Similar presentations

CC1 ENUM LLC Presentation to the NANC March 15, 2005 Karen Mulberry Chairman

Advertisements

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.

2/12/2001 ENUM Administration Penn Pfautz AT&T

1 Copyright © 2012 Telcordia Technologies, Inc All Rights Reserved Telcordia IP Interconnection ENUM Registry Solution John P. Malyar Chief Architect Adam.

Submission doc.: IEEE /0032r0 April 2015 Sho Furuichi, SonySlide 1 The new coexistence use cases for IEEE Date: Authors: Notice:

ENUM Chris Wong Converging Services Branch International Training Program 7 September 2006.

August 13-14, 2002 Washington, DC Gary Richenaker Chair ENUM Forum

Asia Pacific ENUM Engineering Team APEET ENUM/SIP Live Trial at 9 Mar nd IETF ENUM WG APEET Yoshiro YONEYA.

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.

Global 800 service through freenum.org Michael Haberler Internet Foundation Austria

Naming & Addressing ENUM, EPC, WINC overview JaeYoung Choi

CC1 ENUM LLC The MCI Perspective Karen Mulberry Sr. Project Manager, Numbering November 8, 2004.

Services COIN association Number Portability M2M Broadband Switching Access CRDB Data export B-Number shielding Fraud covenant 1.

VoIP and ENUM The Austrian Trial IETF #57 Vienna July 2003 Richard STASTNY ÖFEG/TELEKOM AUSTRIA, Postbox 147, 1103-Vienna enum:

ENUM Update for voipeer BOF Richard Shockey ENUM co-chair IETF 63 Paris.

October 2005Bell Canada Network Planning 1 ENUM (tElephone NUmber Mapping) Update CSCN Chair Presentation to ISACC Information and Communications Technology.

Industry Canada 1 Bob Leafloor Colman Ho Peter Chau Industry Canada January 2003 (ENUM) T E lephone NU mber M apping.

Slide 1 Nicklas Beijar - TRIP, ENUM and Number Portability TRIP, ENUM and Number Portability Nicklas Beijar

Bernard Turcotte President Canadian Internet Registration Authority Canada’s ccTLD ENUM CSCN Forum March 11, 2004.

© 2004 AT&T, All Rights Reserved. The world’s networking company SM VoIP, Portability, and the Evolution of Addressing LNPA & Future of Numbering Working.

Slide 1 Nicklas Beijar - TRIP, ENUM and Number Portability TRIP, ENUM and Number Portability Nicklas Beijar

Project: IEEE P Working Group for Wireless Personal Area Networks (WPANS) Submission Title: [A critical view of the proposed compromise – A marketing.

APRICOT ENUM/SIP BoF James Seng. Agenda CNNIC's status update on ENUM, CNNIC ENUM activities in Japan, JPRS ENUM Trial Status in Korea, KRNIC SIP/ENUM.

12/18/2000 ENUM Administration Penn Pfautz AT&T

1 February 8th, 2002 ITU ENUM Tutorial Stanislas Bourgain Autorité de régulation des télécommunications Unité Internet Service Interconnexion et Nouvelles.

ENUM The Status of UK Implementation Tony Holmes BTexact Technologies Numbering Addressing & Routeing Chairman UK ENUM Group ITU February 2002.

IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Reference Model and Use-Cases for Information Service Date.

ENUM Tutorial ENUM Forum June 3, 2003 Steven D. Lind, AT&T GEN0075R0.

Doc.: IEEE /099r0 Submission March 2000 Khaled Amer, AmerNetSlide 1 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)

ENUM Privacy and Security issues drafts/draft-ietf-enum-privacy- security-00.txt.

ENUM Registry architectures - Some Canadian options These architecture diagrams are submitted by TELUS to the CSCN ENUM Task Force for the purpose of discussion.

THIS IS THE WAY ENUM Variants Jim McEachern

KR ENUM Trial Status Update

Using NPAC as the ENUM Registry

Emergency Service – NS/EP Vs E-911 for IEEE m

Project: IEEE Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposals for adding a version number and for the treatment.

ATIS/SIP Forum NNI Task Force – Routing Team

Submission Title: [Add name of submission]

Doc.: IEEE /056r0 January 2001 Project: IEEE Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [WG Reflector.

March, 2003 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [WG-TG4 Opening Report Mar03] Date Submitted:

Submission Title: [Task Group 1 Opening Report]

Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Agenda for TG4z EIR t for May.

Protocol discussion Document Number: IEEE R0

<month year> doc.: IEEE < e> <March 2018>

May 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Resolution To The FCC Part

doc.: IEEE <doc#1>

doc.: IEEE <doc#>

Submission Title: [802.11n Liaison Report May 2009]

Submission Title: [Rate one over four code for TG4a]

March 2005 doc.: IEEE a March 2004 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title:

30 A 30 B 30 C 30 D 30 E 77 TOTALS ORIGINAL COUNT CURRENT COUNT

1/14/2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Moderate Rate Options for TG4a] Date Submitted:

<month year> doc.: IEEE < e> <Jan 2019>

doc.: IEEE <doc#>

May 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Resolution To The FCC Part

Submission Title: Validation and Verification Task Force Proposal

Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TG3m Closing Report for March.

doc.: IEEE <doc#>

Differentiating Levels of a Learning Progression

Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Agenda for TG4z EIR t for May.

ENUM Status of US Implementation

doc.: IEEE <doc#1>

<month year> doc.: IEEE < e> <March 2018>

Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TG4n Chinese Medical Band Closing.

Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Agenda for TG4z EIR t for May.

May 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Resolution To The FCC Part

Cases of and deaths from cervical cancer, with associated incidence and mortality (rates per women), among Canadian women (2002–2006) by age group.

July 2003 doc.: IEEE <03/242> July 2003

Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Dependable Interest Group Closing.

12/15/2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [AWGN Simulation Results] Date Submitted:

Presentation transcript:

ENUM Registry architectures - Some Canadian options These architecture diagrams are submitted by TELUS to the CSCN ENUM Task Force for the purpose of discussion only and no TELUS preference should be inferred for any of these or any other potential options. TELUS reserves the right to amend or withdraw the contents in this contribution at any time. The options are not intended to show relationships between registrars and the registry operators or name servers. Frank Norman 2004-02-09 16:00

ENUM architectures Options on the following pages are examples of Canadian options based upon the US options defined in ENUM FORUM Working Document # 6001_1_0 Options 1 Single joint Tier 1 for Canada & US 2.1 Delegation of single Canadian Tier 1 from within Tier 0 2.2 Delegation of single Canadian Tier 1 from within Skinny Tier 1 3.1 Delegation of multiple Canadian Tier 1s from within Tier 0 3.2 Delegation of multiple Canadian Tier 1s from within Skinny Tier 1

Option 1 Single joint Tier 1 for Canada & US Tier 0 Tier 1 US Tier 2s $ORIGIN e164.arpa 1 IN NS nsnanp_enum.com Tier 0 ns.ripe.net $ORIGIN 1.e164.arpa 0.0.0.1.5.5.5.8.0.9 IN NS e.164.foo.net 8.8.8.8.0.1.8.3.1.6 IN NS enumopr2.com 9.9.9.9.0.1.8.3.1.6 IN NS enumopr1.ca 4.3.2.1.0.1.6.4.0.6 IN NS enumopr1.ca 8.7.6.5.0.1.6.4.0.6 IN NS enumopr3.ca 4.3.2.1.5.5.5.0.0.8 IN NS tf_enumopr.ca 9.8.7.6.5.5.5.0.0.8 IN NS tf_enumopr.us Tier 1 nsnanp_enum.com US Tier 2s e.164.foo.net etcetera Tier 2 enumopr1.ca Tier 2 enumopr2.com Tier 2 enumopr3.ca $ORIGIN 9.9.9.9.0.1.8 3.1.6.1.e164.arpa IN NAPTR 10 100 “u” E2U+sip” “!^.*$!sip:jo@sip.xcea.ca $ORIGIN 4.3.2.1.0.1.6.4.0.6.1.e164.arpa IN NAPTR 10 100 “u” E2U+sip” “!^.*$!sip:lala@sip.bctip.com

Option 2.1 Delegation of single Canadian Tier 1 from within Tier 0 $ORIGIN e164.arpa 3.7.9.1 IN NS us_ns_enum.us 8.0.9.1 IN NS us_ns_enum.us 3.1.6.1.IN NS ca_ns_enum.ca 4.0.6.1.IN NS ca_ns_enum.ca 0.0.8.1.IN NS tf_ns_enum.int Tier 0 ns.ripe.net Tier 1 tf_ns_enum.int Tier 1 us_ns_enum.us Tier 1 ca_ns_enum.ca $ORIGIN 3.7.9.1.e164.arpa 0.0.0.1.5.5.5 IN NS us_ns_enum.us $ORIGIN 8.0.9.1.e164.arpa 4.3.2.1.IN NS ca_ns_enum.ca $ORIGIN 3.1.6.1.e164.arpa 8.8.8.8.0.1.8 IN NS enumopr2.com 9.9.9.9.0.1.8 IN NS enumopr1.ca $ORIGIN 4.0.6.1.e164.arpa 4.3.2.1.0.1.6 IN NS enumopr1.ca 8.7.6.5.0.1.6 IN NS enumopr3.ca Tier 2 enumopr3.ca Tier 2 enumopr2.com Tier 2 enumopr1.ca $ORIGIN 9.9.9.9.0.1.8 3.1.6.1.e164.arpa IN NAPTR 10 100 “u” E2U+sip” “!^.*$!sip:jo@sip.xcea.ca $ORIGIN 4.3.2.1.0.1.6.4.0.6.1.e164.arpa IN NAPTR 10 100 “u” E2U+sip” “!^.*$!sip:lala@sip.bctip.com Tier 2 enumopr1.ca

Option 2.2 Delegation of single Canadian Tier 1 from within Skinny Tier 1 Tier 0 ns.ripe.net $ORIGIN e164.arpa 1 IN NS nsnanp_enum.com $ORIGIN 1. e164.arpa 3.7.9 IN NS us_ns_enum.us 8.0.9 IN NS us_ns_enum.us 3.1.6 IN NS ca_ns_enum.ca 4.0.6 IN NS ca_ns_enum.ca 0.0.8 IN NS tf_ns_enum.int Skinny Tier 1 nsnanp_enum.com Tier 1 tf_ns_enum.int Tier 1 us_ns_enum.us Tier 1 ca_ns_enum.ca $ORIGIN 3.7.9.1.e164.arpa 0.0.0.1.5.5.5 IN NS e164.foo.net $ORIGIN 8.0.9.1.e.164.arpa 4.3.2.1.5.5.5 IN NS enum.bar.com $ORIGIN 3.1.6.1.e164.arpa 8.8.8.8.0.1.8 IN NS enumopr2.com 9.9.9.9.0.1.8 IN NS enumopr1.ca $ORIGIN 4.0.6.1.e.164.arpa 4.3.2.1.0.1.6 IN NS enumopr1.ca 8.7.6.5.0.1.6 IN NS enumopr3.ca Tier 2 enumopr3.ca Tier 2 enumopr2.com Tier 2 enumopr1.ca $ORIGIN 9.9.9.9.0.1.8 3.1.6.1.e164.arpa IN NAPTR 10 100 “u” E2U+sip” “!^.*$!sip:jo@sip.xcea.ca $ORIGIN 4.3.2.1.0.1.6.4.0.6.1.e164.arpa IN NAPTR 10 100 “u” E2U+sip” “!^.*$!sip:lala@sip.bctip.com Tier 2 enumopr1.ca

Option 3.1 Delegation of multiple Canadian Tier 1s from within Tier 0 $ORIGIN e164.arpa 3.7.9.1 IN NS enum_tl_comp-a.us 8.0.9.1 IN NS enum_tl_comp-b.us 3.1.6.1.IN NS enum_tl_ca_opr-1.ca 4.0.6.1.IN NS enum_tl_ca_opr-1.ca 0.0.8.1.IN NS tf_ns_enum.int Tier 0 ns.ripe.net Tier 1 tf_ns_enum.int Tier 1 enum_tl_comp-a.us Tier 1 enum_tl_ca_opr-1.ca Tier 1 enum_tl_ca_opr-2.ca $ORIGIN 4.0.6.1.e164.arpa 4.3.2.1.0.1.6 IN NS enumt2opr-1.ca 8.7.6.5.0.1.6 IN NS enumt2opr-3.ca $ORIGIN 3.1.6.1.e164.arpa 8.8.8.8.0.1.8 IN NS enumt2opr-2.com 9.9.9.9.0.1.8 IN NS enumot2pr-1.ca Tier 2 enumopr3.ca Tier 2 enumopr2.com Tier 2 enumopr1.ca $ORIGIN 9.9.9.9.0.1.8 3.1.6.1.e164.arpa IN NAPTR 10 100 “u” E2U+sip” “!^.*$!sip:jo@sip.xcea.ca $ORIGIN 4.3.2.1.0.1.6.4.0.6.1.e164.arpa IN NAPTR 10 100 “u” E2U+sip” “!^.*$!sip:lala@sip.bctip.com Tier 2 enumopr1.ca

Option 3.2 Delegation of multiple Canadian Tier 1s from within Skinny Tier 1 Tier 0 ns.ripe.net $ORIGIN e164.arpa 1 IN NS nsnanp_enum.com $ORIGIN 1. e164.arpa 3.7.9.1 IN NS enum_tl_comp-a.us 8.0.9.1 IN NS enum_tl_comp-b.us 3.1.6.1.IN NS enum_tl_ca_opr-1.ca 4.0.6.1.IN NS enum_tl_ca_opr-1.ca 0.0.8.1 IN NS tf_ns_enum.int Skinny Tier 1 nsnanp_enum.com Tier 1 tf_ns_enum.int Tier 1 tf_ns_enum.int Tier 1 enum_tl_comp-a.us etcetera Tier 1 enum_tl_ca_opr-1.ca Tier 1 enum_tl_ca_opr-2.ca $ORIGIN 4.0.6.1.e164.arpa 4.3.2.1.0.1.6 IN NS enumt2opr-1.ca 8.7.6.5.0.1.6 IN NS enumt2opr-3.ca $ORIGIN 3.1.6.1.e164.arpa 8.8.8.8.0.1.8 IN NS enumt2opr-2.com 9.9.9.9.0.1.8 IN NS enumot2pr-1.ca Tier 2 enumopr3.ca Tier 2 enumopr2.com Tier 2 enumopr1.ca $ORIGIN 9.9.9.9.0.1.8 3.1.6.1.e164.arpa IN NAPTR 10 100 “u” E2U+sip” “!^.*$!sip:jo@sip.xcea.ca $ORIGIN 4.3.2.1.0.1.6.4.0.6.1.e164.arpa IN NAPTR 10 100 “u” E2U+sip” “!^.*$!sip:lala@sip.bctip.com Tier 2 enumopr1.ca