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

regulator prohibiting current practice of use of +49 numbers for voip, update
by Chris Heinze 24 May '05

24 May '05

hi! we had that some time ago. now it's getting more concrete: http://www.heise.de/newsticker/meldung/51877 (german only again, sorry) short summary: regtp (the german regulator) now prohibits (voip) providers in general to give phonenumbers to users that do not live in the area of the respective prefix or have their company located there. this is effective from october 15th. btw: the non-regional prefix under +49 is still not in sight. so - of course :) - i have to mention the 'proposal for non-regional upts available to the general public' again. everyone interested in possible solutions to many voip-specific problems with e.164 numbers should really read this (can be found in the archive of this mailinglist). kind regards, Chris Heinze

2 3

ERG to discuss VoIP
by Carsten Schiefner 13 Feb '05

13 Feb '05

All, FYI: during its upcoming meeting, the ERG - the European Regulators Group - will also discuss VoIP related issues to come to a common position eventually. Although not 100% ENUM related, this nonetheless might be of some interest to the Working Group. Best, Carsten -------- Original Message -------- Subject: ERG's eleventh plenary meeting - agenda and debriefing session Date: Thu, 25 Nov 2004 13:04:20 +0100 From: erg(a)cec.eu.int Agenda for the eleventh plenary meeting of the European Regulators Group The agenda for the eleventh plenary meeting ("ERG11") in Brussels 2 - 3 December is now available at http://www.erg.eu.int/meetings/index_en.htm. Highlights include o New action plan and timetable for intensified work with international roaming o Draft Common Position on Voice over IP o Decision on the draft 2005 Work Programme for public consultation The ERG11 debriefing will be held on Monday, 6 December in Brussels at 10 AM. If you wish to attend this, please e-mail to erg-secretariat(a)cec.eu.int <mailto:erg@cec.eu.int> no later than close of business on Wednesday, 1 December. ________________________ European Regulators Group www.erg.eu.int

1 1

ITU-T/ENUM/NP
by Andrzej Bartosiewicz 26 Jan '05

26 Jan '05

Dear All, I would like to draw your attention to the ITU SG-2 activities regarding Number Portability. It seems that SG2 (thanks to Marco Bernardi from NeuStar) of ITU-T will be considering Infrastructure-ENUM as potential solution for Number Portability Database. I'm very glad because this is the idea I have been promoting in Poland for the last year... :) Group : itu-t title : [ D 9 ] Draft Number Portability Supplement url : http://www.itu.int/md/meetingdoc.asp?lang=e&parent=T05-SG02-050216-D-0009&ty pe=mitems Best, Andrzej.

1 0

Two ETSI drafts on ENUM approved today
by Stastny Richard 21 Jan '05

21 Jan '05

Dear all, http://voipandenum.blogspot.com/2005/01/two-etsi-drafts-on-enum-approved-to… ETSI <http://portal.etsi.org> TISPAN WG4 finished 2 drafts on User ENUM <http://enum.nic.at/documents/ETSI/Drafts/05TD142r3%20DTS_102172v020006.pdf> and on Infrastructure ENUM <http://enum.nic.at/documents/ETSI/Drafts/05TD143r4%20Draft%20TR_102055v008.…> (Carrier ENUM) this week and got workgroup and TISPAN plenary approval today. ETSI DTS 102 172 V2 <http://enum.nic.at/documents/ETSI/Drafts/05TD142r3%20DTS_102172v020006.pdf> "Minimum requirements for interoperability of ENUM implementations" contains general guidance on (User) ENUM implementations as defined in RFC3761 and in ETSI TS 102 051 "ENUM Administration in Europe" and the specification for: * The format, contents and meaning of the information in the NAPTR records that are held by the ENUM Tier 2 Nameserver providers and accessible by DNS. * The ways in which ENUM client software should interpret and act upon information obtained from NAPTR records. The document is intended to enable interoperability between ENUM implementations that are organized in different countries. This interoperability enables: * The same ENUM client software to work with NAPTR records generated by different national implementations and this in turn will enable applications that use ENUM to access details of ENUM subscribers in more than one country without additional modifications. * Organizations to function as ENUM Registrars and ENUM Tier 2 Nameserver Provider in more than one national implementation. The document will therefore add economies of scope to the ENUM implementations that will benefit ENUM subscribers, providers, application service providers and ENUM users. The present document is Version 2 of the Technical Specification (TS) and incorporates already some results obtained from trials performed in some countries. It may serve therefore also as a basis for first commercial deployments, keeping in mind that still not all enumservices are available as IETF RFCs and registered with IANA. The intention is to review this document based on the experience gained from future implementations and if necessary. ETSI DTR 102 055 <http://enum.nic.at/documents/ETSI/Drafts/05TD143r4%20Draft%20TR_102055v008.…> "Infrastructure ENUM" This document identifies a range of issues which occur if providers of communication services and networks (called Communication Service Providers (CSP) within this document) consider using the concepts developed in RFC 3761 (ENUM) for infrastructure purposes. Such an approach would result in the application of the ENUM concept to the provision of information for routeing (both internally and for the interconnection of networks - also called peering), including information for number portability, freephone and other number or address translation capabilities, SMS and MMS, etc. It considers the likely steps along the way and where possible, identifies alternative options and approaches. It will specifically identify: * issues which occur if providers of IMS-based NGNs consider peering traffic with each other via Points-of-Interconnect based on IP technology, by using E.164 numbers to address end-points they are hosting for their subscribers, * issues which occur if providers of IMS-based NGNs consider peering traffic with other providers e.g. IMS-based PLMNs and also with providers on the Internet. Out-of-scope are requirements for using Infrastructure ENUM for peering of transit traffic not targeted for end-points within the providers control. regards Richard Stastny

1 0

Re: [enum-wg] Kim's document
by Stastny Richard 21 Jan '05

21 Jan '05

Hi Kim, may I point BTW to two major errors 1. Austria is in production since Dezenber 2004 2. The request from Australia is not objected (this is also wrong on the RIPE page: http://www.ripe.net/enum/request-archives/index.html see http://www.ripe.net/maillists/ncc-archives/enum-announce/2005/msg00001.html regards Richard ________________________________ Von: enum-wg-admin(a)ripe.net im Auftrag von Andrzej Bartosiewicz Gesendet: Fr 21.01.2005 15:06 An: 'Kim Davies' Cc: enum-wg(a)ripe.net Betreff: RE: [enum-wg] Kim's document Thanks Kim. > -----Original Message----- > From: enum-wg-admin(a)ripe.net [mailto:enum-wg-admin@ripe.net] On Behalf Of > Kim Davies > Sent: Friday, January 21, 2005 2:52 PM > To: Andrzej Bartosiewicz > Cc: enum-wg(a)ripe.net > Subject: Re: [enum-wg] Kim's document > > Andrzej Bartosiewicz wrote: > > The link http://www.centr.org/kim/enum/index.html is broken. > > > > Is there anybody who has the copy of this document? > > This page is working again. Had some server difficulties a few weeks > back and didn't think to check it. > > kim

1 0

Kim's document
by Andrzej Bartosiewicz 21 Jan '05

21 Jan '05

The link http://www.centr.org/kim/enum/index.html is broken. Is there anybody who has the copy of this document? Andrzej.

2 2