- enum-wg - mailman.ripe.net

please help us make the ENUM number range +43 780 a success
by Alexander Mayrhofer 14 Oct '05

14 Oct '05

Hi, as you probably know, Austria has a dedicated ENUM driven number range in place since May 2005: +43 780. Reachability of numbers within this range from the PSTN is good within Austria, but still a patchwork from abroad (as with all new number ranges). it is very hard to debug PSTN connectivity from the receiving end - which is why we are asking you dedicate a few minutes of time and a phone call. To collect the information we've set up a Wiki page: http://www.voip-info.org/wiki/view/43780 To help us make it better, follow these steps: - take a "conventional" phone line of your choice (PSTN, mobile - the more data points, the better) - call the test number "+43 780 004711" - if you hear the word "ENUM" followed by some elevator music, routing from your telco is ok - perfect! - if it doesn't work, take a note of what happened (announcement, error message, error indication etc.) - leave a note about your success or failure to the wiki page indicated above. If possible, add rate information. - repeat this test for any carrier you have access to. If you detect a failure, and happen to know or work for the telco - please notify the relevant person to fix the problem, it is theirs. We're happy to talk to them if you get us in touch. Thanks for your help - we really appreciate it. Feel free to forward this message to people who might contribute more data points. thanks, Alex Mayrhofer enum.at

1 0

FYI: DENIC Preparing Start of Full-Scale ENUM Operation
by Carsten Schiefner 07 Oct '05

07 Oct '05

Dear colleagues, please find DENIC's press release at: http://www.denic.de/en/denic/presse/press_72.html Best - enjoy your weekend and hope to see you all next week then: Carsten Schiefner

1 0

Draft RIPE 51 ENUM WG agenda
by Schiefner, Carsten 04 Oct '05

04 Oct '05

Dear colleagues, Your co-chairs are pleased at the apparent level of general interest in ENUM, which has led to the inclusion of several ENUM-related presentations in the plenary sessions of RIPE 51. The extended draft agenda of the ENUM WG at RIPE 51 is thus as follows: - Tue, 11 October, 14:00-15:30/90 min Marcos Sanz, DENIC (20 min) 'Reasons for (not) using EPP for ENUM' Adrian Georgescu, AG Projects (20 min) 'ENUM Tier 2 provisioning techniques' Robert Schischka, enum.at, and Bernie Hoeneisen, SWITCH (20 min) 'ENUM validation Schemes and process flow' Panel discussion with the presenters and Andrzej Bartosiewicz, NASK (30 min) - Tue, 11 October, 16:00-16:30/30 min Michael Haberler, IPA/nic.at (30 min) 'Carrier ENUM and VoIP Peering' - Thu, 13 October, 14:00-15:30/90 min A. Preliminaries (5 min) . Welcome . Scribe . Confirm agenda B. Previous Meeting (5 min) . Note and approve minutes . Note open issues, if any C. Carsten Schiefner, Deutsche Telekom (10 min) News summary: . IETF 63 . I-D/RFC watch . DENIC's ENUM day D. Axel Pawlik, RIPE NCC (15 min) Status update of ENUM at the RIPE NCC . Statistics . Tier 0 status . misc E. Jim Reid, DNS-MODA (10 min) Update on the ETSI ENUM Plugtest F. Peter Koch, DENIC (10 min) 'Walking the 9.4.e164.arpa tree: first results' G. Jim Reid, DNS-MODA (10 min) E.164 testbed numbers: per country or directly from the ITU? H. Provisioning, Carrier ENUM and VoIP Peering (10 min) . Arising from plenary . Other, if any : Y. I/O with other WGs, AOB (10 min) Z. Close (5 min) . Summarize action items . Thank scribe and participants Last, but not least: can we kindly ask the presenters to send us a better wording for the title of their respective talk if they feel that the current one (basically made up by your co- chairs) doesn't really hit the spot? Best regards, Carsten Schiefner -- Carsten Schiefner | p: +49 441 234-4571 Deutsche Telekom AG | f: +49 431 7163-3972 T-Com Zentrale TK44 | m: +49 151 14525458 Ammerländer Heerstr. 138 | mailto:Carsten.Schiefner@t-com.net D-26129 Oldenburg | http://www.t-com.de/kundendienst

1 0

Last call for comments on RIPE 50 minutes
by Schiefner, Carsten 29 Sep '05

29 Sep '05

Dear colleagues, this is the last call for comments and/or corrections you may have re. the RIPE 50 ENUM WG draft minutes. The last revision is still also the first revision, available at: http://www.ripe.net/ripe/wg/enum/minutes/r50-minutes.html The minutes will be finally approved at the RIPE 51 ENUM WG meeting - hope to see you all there. Thanks and best regards, Carsten Schiefner -- Carsten Schiefner | p: +49 441 234-4571 Deutsche Telekom AG | f: +49 431 7163-3972 T-Com Zentrale TK44 | m: +49 151 14525458 Ammerländer Heerstr. 138 | mailto:Carsten.Schiefner@t-com.net D-26129 Oldenburg | http://www.t-com.de/kundendienst

1 0

Dutch ISOC chapter to have an ENUM etc. event
by Carsten Schiefner 15 Sep '05

15 Sep '05

All, the Dutch ENUM chapter will hold a one day ENUM/SIP/VoIP event on Frida, 14 Oct, in The Hague, Netherlands. I am aware that this is in conflict with RIPE 51's plenary session on Friday morning - then again, it is only some 50 minutes by train: so everybody can make it at least for the afternoon... :-) You can find more information at: http://www.isoc.nl/activ/2005-ENUMSIP/ Best regards, Carsten Schiefner

1 1

Re: [enum-wg] Second call for RIPE 51 agenda topics and comments on RIPE 50 minutes
by Conroy, Lawrence (SMTP) 12 Sep '05

12 Sep '05

Hi Richard, Carsten, folks, In reference to EPP vs. SOAP/HTTP, I note the authorship of RFC3205 - given that, calling it stupid is redundant/stating the obvious. Seriously, care to expand on what you see as the differences that make the EPP (client/server) model inappropriate for provisioning? I had thought that the goal was for the Telco customer care system to act as an EPP client, whilst the core ENUM provisioning/ population system acted as the EPP server. That seemed to be the model behind the (delphic) answer when I (and others) asked on the IETF-ENUM list for clarification on why one would ever want EPP-E164, where would it be used, and between whom. On 12 Sep 2005, at 15:36, Richard Shockey wrote: > I can certainly testify to the intense interest in provisioning > issues on this side of the pond. > > In particular we're looking at SOAP/XML interfaces to the > registry. The reason for this is that EPP ( which is a fine > protocol ) was designed for the highly unique business model of > domain name registries and simply will not integrate into the kinds > of customer management systems teleco typically deploy. > > EPP was designed in the manner it is because the IETF has a really > really stupid policy ( RFC 3205 ) on the use of HTTP as a > application substrate. >

2 1

Second call for RIPE 51 agenda topics and comments on RIPE 50 minutes
by Carsten Schiefner 12 Sep '05

12 Sep '05

Dear all, this is the second call for agenda items for the ENUM WG meeting at RIPE 51 in Amsterdam. In the meantime we got some proposals that can be nicely bundled into a "Provisioning" theme. Your co-chairs are happy that such a theme is felt of being of such wide interest that the ENUM WG got a 90 min slot allotted during the plenary part of the meeting, for the presentations and a subsequent panel discussion. However, any other ideas are still very much welcome, too - as usual. :-) Please send in your suggestions and proposals. This is also the second call for comments and/or corrections you may have re. the RIPE 50 ENUM WG draft minutes. The last revision is still also the first revision, available at: http://www.ripe.net/ripe/wg/enum/minutes/r50-minutes.html Thanks and best regards, Carsten Schiefner

2 1

RIPE Policy Development Process
by Paul Rendek 01 Sep '05

01 Sep '05

Dear Colleagues We are pleased to announce that Rob Blokzijl, RIPE Chair, has published a new RIPE Document, "Policy Development Process in RIPE", (ripe-350). This document formally describes the policy development process. The updated process is operational from today, 1 September 2005. A new RIPE web page describes all the active policy proposals and their status. Each proposal has a page showing its history, status and all supporting documentation. This page can be found at: http://www.ripe.net/ripe/policies/proposals/index.html A new mailing list <policy-announce(a)ripe.net> has been created for announcing policy proposals and tracking them through the policy development process. This is not a discussion list; discussions will continue to take place on relevant RIPE Working Group lists and at RIPE Meetings. You can subscribe to the policy-announce list at: http://www.ripe.net/mailman/listinfo/policy-announce List archives are available at: http://www.ripe.net/ripe/maillists/archives/policy-announce/ Kind regards Paul Rendek Head of Member Services and Communications RIPE NCC

1 0

New ENUM software available from .nz
by Alexander Mayrhofer 27 Jul '05

27 Jul '05

There seems to be a new ENUM related open source package available at http://www.internetnz.net.nz/public/enum/index.html I haven't looked into what it provides (yet) - i've just seen from the README that it somehow interacts with Asterisk. More news as we get it - test in progress. cheers axelm

1 0

Fwd: New I/D concerning ENUM validation architecture submitted
by Bernie Hoeneisen 11 Jul '05

11 Jul '05

For those, who are not on the IETF ENUM WG Mailinglist... ---------- Forwarded message ---------- Date: Mon, 11 Jul 2005 20:21:19 +0200 (CEST) From: Bernie Hoeneisen <bhoeneis(a)switch.ch> To: enum(a)ietf.org Subject: New I/D concerning ENUM validation architecture submitted Dear ENUM WG, Axel and me have written an I/D, which we consider as the basis for the ENUM validation work currently carried out in the IETF. In this I/D we describe e.g. requirements, ENUM Provisioning Model and Roles, Validation Process Assumptions, and so on. The I/D also reflects experiences from our running implementations. This document can also be used as an introduction to ENUM domain name provisioning and in particular to ENUM validation related processes. Until it appears in the archieves, this I/D can also be downloaded from: * http://www.enum.at/ietf/draft-mayrhofer-enum-validation-arch-00.txt * http://www.enum.at/ietf/draft-mayrhofer-enum-validation-arch-00.html Abstract An ENUM domain name is tightly coupled with the underlying E.164 number. The process of verifying whether or not the Registrant of an ENUM domain name is identical to the Assignee of the corresponding E.164 number is commonly called "validation". This document describes validation requirements and a high level architecture for an ENUM validation infrastructure. cheers, Axel & Bernie

1 0