Infrastructure ENUM Options Richard Stastny Michael Haberler IETF#65 Dallas, TX.

Slides:



Advertisements
Similar presentations
International Telecommunication Union ENUM Issues and Solutions Houlin Zhao Director Telecommunication Standardization Bureau International Telecommunication.
Advertisements

Rfc4474bis-01 IETF 89 (London) STIR WG Jon & Cullen.
Carrier/Infrastructure ENUM Requirements draft-lind-infrastructure-enum-reqs-01.
Working Group ENUM, Seminar Bratislava 16th of March 2005 Proposal on ENUM Trial in the Slovak Republic Vladimir Murin Research Institute Posts and Telecommunications,
International Telecommunication Union ITU Perspective on ENUM Robert Shaw ITU Internet Strategy and Policy Advisor ICANN Rio de Janeiro, Brazil March 25,
UK ENUM Jay Daley, Nominet UK. ENUM explained Nominet and ENUM.
August 13-14, 2002 Washington, DC Gary Richenaker Chair ENUM Forum
ENUM ITU-T Status Update An SAIC Company Prepared For: ACA Industry Workshop March, 2003 Telcordia Contact: Gary Richenaker
1 IETF – ENUM US Government Briefing Richard Shockey IETF ENUM Work Group Chair Senior Technical Industry Liaison NeuStar, Inc Vermont Avenue N.W.
Draft-pfautz-lind-enum-carrier- 00.txt IETF 60 4 August 2004 Steven D. Lind.
Info Day on New Calls and Partner Café Brussels, 10 February 2011 How to apply: Legal Framework – Beneficiaries – Application and Selection Procedure.
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.
The Austrian ENUM Trial is closing down 59 th IETF Seoul, South Korea, March 3 rd, 2004 Richard STASTNY ÖFEG, Postbox 147, 1103-Vienna enum:
ISO Tor Stålhane IDI / NTNU. What is ISO ISO 9001 was developed for the production industry but has a rather general structure ISO describes.
Global 800 service through freenum.org Michael Haberler Internet Foundation Austria
AIMS Workshop Heidelberg, 9-11 March 1998 P717 & P805: SIRTE Study for Internet Roaming Throughout Europe Franco Guadagni - Telecom Italia / CSELT
PSTN – User ENUM – „Infrastructure ENUM“ An ETSI View Richard Stastny IETF60 San Diego.
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.
Industry Canada 1 Bob Leafloor Colman Ho Peter Chau Industry Canada January 2003 (ENUM) T E lephone NU mber M apping.
Japan Registry Service Copyright © 2004 JPRS A Glance at ENUM AP* Retreat Feb. 22, 2004 Hiro HOTTA.
© 2004 AT&T, All Rights Reserved. The world’s networking company SM VoIP, Portability, and the Evolution of Addressing LNPA & Future of Numbering Working.
International Telecommunication Union ENUM Implementation Robert Shaw ITU Internet Strategy and Policy Advisor International Telecommunication Union ICANN.
Registries and Registrars Dr Bruce Tonkin Chief Technology Officer Melbourne IT Ltd 3 March 03.
1January 2006Richard Stastny Developments around Infrastucture ENUM and their relevance on NGNs Workshop on NGN Interconnection and Numbering TRIS – TISPAN.
ENUM in neighbor countries: Austria (+43) Alexander Mayrhofer ENUM-Day, Prague, Sept
Peering: A Minimalist Approach Rohan Mahy IETF 66 — Speermint WG.
1 IETF 88 (Vancouver) November 6, 2013 Cullen Jennings V3.
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,
12/18/2000 ENUM Administration Penn Pfautz AT&T
8 June 2006Portland, Oregon, USAE. Sivel EASA Working Group on regulation of non-complex motor aircraft engaged in non-commercial operations E Sivel (EASA)
IETF #65 Network Discovery and Selection Problem draft-ietf-eap-netsel-problem-04 Farooq Bari Jouni Korhonen.
1 February 8th, 2002 ITU ENUM Tutorial Stanislas Bourgain Autorité de régulation des télécommunications Unité Internet Service Interconnexion et Nouvelles.
ENUM WG mini-BOF Setting the Stage Richard Shockey IETF 60 San Diego.
Enumservice VOID draft-stastny-enum-void-00 Richard Stastny Lawrence Conroy IETF60 San Diego.
Telecom Department TELECOMMUNICATIONSITRADIOPOST Status of ENUM in Sweden ITU-T Tutorial Workshop on ENUM 8 February 2002 Joakim Strålmark from.
International Telecommunication Union ITU Perspective on ENUM Robert Shaw ITU Internet Strategy and Policy Advisor ICANN Rio de Janeiro, Brazil March 25,
Update on ITU-T ENUM Activities Steven D. Lind AT&T SG-A ENUM - Ad Hoc February 12, 2001.
Multicast Routing Optimization Juan-Carlos Zúñiga Luis M. Contreras Carlos J. Bernardos Seil Jeon Younghan Kim MULTIMOB WG, July
2007/07/23IETF69 enum-combined1 draft-ietf-enum- combined IETF69 Otmar Lendl Michael Haberler Richard Stastny.
International Telecommunication Union ENUM Organizational Perspectives Richard Hill, for Houlin Zhao Director Telecommunication Standardization Bureau.
1 Introduction to ENUM Technical and operational aspects Marco Bernardi NeuStar, Inc
Considerations on ENUM from China Zhangjie RITT of MII.
ENF/ERO ENUM Convergence Workshop Tony Holmes Chairman ETSI SPAN11 NAR BTexact Technologies Numbering Addressing & Routeing 9-10 January 2002 Standards.
Carrier/Infrastructure ENUM Requirements draft-lind-infrastructure-enum-reqs-01.
Incorporating Privacy Into Systems Development Methodology Phil Moleski Director Corporate Information Technology Branch Saskatchewan Health
CLUE WG Interim Meeting San Jose, CA Sept , 2012
THIS IS THE WAY ENUM Variants Jim McEachern
XCON WG IETF-64 Meeting XCON Framework Overview & Issues
Using NPAC as the ENUM Registry
Enum dip indicator draft-stastny-iptel-tel-enumdi-00
CLUE WG Interim Meeting San Jose, CA Sept , 2012
CLUE WG Interim Meeting San Jose, CA Sept , 2012
Dovetail project update
The Domain Policy DDDS Application
GIRO usage and GSICS Lunar Observation Dataset Policy S. Wagner
SIP Identity issues John Elwell, Jonathan Rosenberg et alia
IDN Variant TLDs Program Update
IETF 64 – ENUM WG IANA Registration for an Enumservice Containing PSTN Signaling Information 8 November 2005 Co-Authors:
RFC PASSporT Construction 6.2 Verifier Behavior
ENUM: Convergence of Technology and Interests?
Implementation of ENUM on telecommunication networks
An Update on BGP Support for 4-byte ASN
Multi-server Namespace in NFSv4.x Previous and Pending Updates
X-DIS/XBRL Phase 2 Kick-Off
ETSI TC MTS TDL SC meeting Reports
Experimental Internet Resource Allocations
Multimedia Training Kit
ENUM successes – failures - alternatives
EITI - Grievance mechanisms
Presentation transcript:

Infrastructure ENUM Options Richard Stastny Michael Haberler IETF#65 Dallas, TX

March 2006Richard Stastny2 One Tree common consensus to have ONE common global public tree for Infrastructure ENUM even from people currently offering Infrastructure ENUM services in private federated ENUM trees “a common tree would be preferable (if it is mine)” Requirement 2.1. Infrastructure ENUM SHALL provide a means for a provider to populate DNS RRs in a common publicly accessible namespace for the E.164 numbering resources for which it is the carrier-of-record.

March 2006Richard Stastny3 In.arpa Infrastructure ENUM could be implemented in any domain Requirement 2.6. Infrastructure ENUM SHALL be implemented under a TLD that can support reliability and performance suitable for PSTN applications. We propose to use.arpa also for Infrastructure ENUM

March 2006Richard Stastny4 Advantages of.arpa Involvement of IETF, IAB, RIPE and ITU-T necessary Existing international and national procedures and policies may be re-used No need (and time required) to create a new governing body to define the policy framework

March 2006Richard Stastny5 Three Options in.arpa 1.Above the Country code –either „i.e164.arpa“ (or „e164i.arpa“) 2.Somewhere below the country code –e.g. carrier.3.4.e164.arpa 3.Pursue Option 1 and Option 2 in parallel All options fulfill requirement 2.8

March 2006Richard Stastny6 Option 1 Above the Country Code e.g. in i.e164.arpa –most straightforward solution –minimum impact on RFC 3761, no add. RFC needed –minimum impact on clients IETF, IAB, RIPE and eventually ITU-T involvement necessary –it has to be checked with ITU-T if the existing Interim Procedures are still valid or have to be modified –but this can only be done AFTER principal agreement by IAB and RIPE If done according to the existing Interim Procedures, opt-in into Infrastructure ENUM is also a national decision like User ENUM (and an opt-in of the CoR) These activities will require definitely some time

March 2006Richard Stastny7 Option 2 Below the Country Code e.g. in.e164.arpa –not so straightforward –no impact on RFC 3761, but add. RFC needed –more impact on clients (SP only) No IETF, IAB, RIPE and ITU-T involvement necessary a national matter only: –decision to put in the Branch Location Record (BLR) –where to put the Infrastructure ENUM tree split off at or below the CC on any other domain Can be implemented immediately (NOW!)

March 2006Richard Stastny8 Option 2 Examples The Branch Location Record (BLR) gives the following information: –where the split occurres –what the label of the split tree is –what the apex of the tree is in infra.3.4.e164.arpa –BLR 2 “infra” “e164.arpa” in 3.4.e164.arpa in carrier.a.p.n.1.e164.arpa –BLR 4 “carrier” “e164.arpa” in 1.e164.arpa in 9.4.e164.info –BLR 0 “” “e164.info” in 9.4.e164.arpa for more info and how to locate the BLR see draft-haberler-carrier-enum-02.txt

March 2006Richard Stastny9 Option 1+2 Option 1 may take some time, OTOH the need for Infrastructure ENUM is immediate (at least for trials), it is proposed to pursue Options 1 and 2 in parallel Countries using Option 2 now may choose anytime to fall back on Option 1 –by simply moving their tree over and –changing their BLR to BLR 0 “” “e164.arpa”

March 2006Richard Stastny10 Summary Proposed way forward for Infrastructure ENUM –finalize requirements –decide to use.arpa –pursue options 1 and 2 in parallel: IAB and RIPE draft RFC 3761bis RFC to define interim BLR