September 2005 - enum-wg - mailman.ripe.net

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