Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Published byDamian Foster Modified over 8 years ago

Similar presentations

Presentation on theme: "ENUM Registry architectures - Some Canadian options These architecture diagrams are submitted by TELUS to the CSCN ENUM Task Force for the purpose of discussion."— Presentation transcript:

1 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

2 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.1Delegation of multiple Canadian Tier 1s from within Tier 0 3.2Delegation of multiple Canadian Tier 1s from within Skinny Tier 1

3 Option 1 Single joint Tier 1 for Canada & US $ORIGIN e164.arpa 1 IN NS nsnanp_enum.com $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 0 ns.ripe.net Tier 1 nsnanp_enum.com Tier 2 enumopr1.ca 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 Tier 2 enumopr2.com US Tier 2s e.164.foo.net etcetera

4 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 $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 0 ns.ripe.net Tier 1 us_ns_enum.us Tier 1 ca_ns_enum.ca Tier 1 tf_ns_enum.int Tier 2 enumopr1.ca Tier 2 enumopr3.ca 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 enumopr2.com

5 Option 2.2 Delegation of single Canadian Tier 1 from within Skinny Tier 1 $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 $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 0 ns.ripe.net Tier 1 us_ns_enum.us Tier 1 ca_ns_enum.ca Tier 1 tf_ns_enum.int Tier 2 enumopr1.ca Tier 2 enumopr3.ca 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 enumopr2.com $ORIGIN e164.arpa 1 IN NS nsnanp_enum.com Skinny Tier 1 nsnanp_enum.com

6 Option 3.1 Delegation of multiple Canadian Tier 1s from within Tier 0 $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 Tier 0 ns.ripe.net Tier 1 enum_tl_comp-a.us Tier 1 enum_tl_ca_opr-2.ca Tier 1 tf_ns_enum.int Tier 2 enumopr1.ca Tier 2 enumopr3.ca 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 enumopr2.com $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 1 enum_tl_ca_opr-1.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

7 Option 3.2 Delegation of multiple Canadian Tier 1s from within Skinny Tier 1 $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 Tier 0 ns.ripe.net Tier 1 tf_ns_enum.int $ORIGIN e164.arpa 1 IN NS nsnanp_enum.com Skinny Tier 1 nsnanp_enum.com $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 Tier 1 enum_tl_ca_opr-2.ca Tier 1 tf_ns_enum.int Tier 2 enumopr1.ca Tier 2 enumopr3.ca 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 enumopr2.com Tier 1 enum_tl_ca_opr-1.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 1 enum_tl_comp-a.us etcetera

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

Similar presentations

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

CC1 ENUM LLC Presentation to the NANC March 15, 2005 Karen Mulberry Chairman
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.

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.
Submission doc.: IEEE 802.19-15/0032r0 April 2015 Sho Furuichi, SonySlide 1 The new coexistence use cases for IEEE 802.19.1 Date: 2015-04-08 Authors: Notice:

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.

ENUM Chris Wong Converging Services Branch International Training Program 7 September 2006.
August 13-14, 2002 Washington, DC Gary Richenaker Chair ENUM Forum 973 829-4305

August 13-14, 2002 Washington, DC Gary Richenaker Chair ENUM Forum
Asia Pacific ENUM Engineering Team APEET ENUM/SIP Live Trial at 9 Mar 2005 62nd IETF ENUM WG APEET Yoshiro YONEYA.

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.

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

Global 800 service through freenum.org Michael Haberler Internet Foundation Austria
Naming & Addressing ENUM, EPC, WINC overview JaeYoung Choi

Naming & Addressing ENUM, EPC, WINC overview JaeYoung Choi
CC1 ENUM LLC The MCI Perspective Karen Mulberry Sr. Project Manager, Numbering +1-972-729-7914 November 8, 2004.

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.

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 2003 14. July 2003 Richard STASTNY ÖFEG/TELEKOM AUSTRIA, Postbox 147, 1103-Vienna enum:+43 664 420 4100.

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.

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.

October 2005Bell Canada Network Planning 1 ENUM (tElephone NUmber Mapping) Update CSCN Chair Presentation to ISACC Information and Communications Technology.
12 January 2006 CDG Conference Call Integrating Existing Number Portability Solutions in Carrier-ENUM Douglas Ranalli, NetNumber, Inc.

12 January 2006 CDG Conference Call Integrating Existing Number Portability Solutions in Carrier-ENUM Douglas Ranalli, NetNumber, Inc.
Industry Canada 1 Bob Leafloor Colman Ho Peter Chau Industry Canada January 2003 (ENUM) T E lephone NU mber M apping.

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

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.

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.

© 2004 AT&T, All Rights Reserved. The world’s networking company SM VoIP, Portability, and the Evolution of Addressing LNPA & Future of Numbering Working.
21-05-0336-01-0000 IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-05-0336-01-0000 Title: Reference Model and Use-Cases for 802.21 Information Service Date.

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

Similar presentations

Ads by Google