Update on Teldas Topics AnneCatherine Christen Managing Director

Update on Teldas Topics Anne-Catherine Christen Managing Director Teldas 27 th January 2011

General Topics

Inet Statistics 2010

Non-Working Days 2012 01 -01 -2012 02 -01 -2012 06 -04 -2012 08 -04 -2012 09 -04 -2012 01 -05 -2012 17 -05 -2012 28 -05 -2012 01 -08 -2012 24 -12 -2012 25 -12 -2012 26 -12 -2012 31 -12 -2012 New Year's Day St. Berchtold's Day Good Friday Easter Sunday Easter Monday Labour Day Ascension Day Whit Sunday Whit Monday Swiss National Day Christmas Eve Christmas Day St. Stephen's Day New Year’s Eve

Inet Breakdown 16 -17 Dec § 14 hours (16. 12. 2010 (20: 03) – 17. 12. 2010 (10: 00)) § SAN switches issue that caused a complete breakdown of the SAN environment. § 1 st & 2 nd level teams investigated but improperly qualified the severity of the issue and did not involve 3 rd level team immediately agreed communication process not followed ! § - 3 rd level team started to investigate and to work on the issue only on the next day (17. 12. 2010 08: 15). § It has been found that similar problem should normally be corrected by implementing last version of Firmware fixes. This will have to be planned soon by HP. § Issues with timeouts? No SLA penalties should be charged during the period (tbd)

. pgp encryption HP discovered that the application is not working according to expectations / documentation : Ø only CLSN List is sent encrypted, not all e-mails from Inet. The current situation corresponds exactly to what was initially requested by the WG (and not ordered). WG thus supports the current implementation and proposes to adapt the documentation to correspond with the reality Ø All operators to implement pgp until End February (new final deadline)

INA Topics

INA Tariff Description (CR 1179) Example of new tariff descriptions ordered for implementation: TC 2145: old "4. 90 Fr. per 60 seconds” -> new “ 4. 90 Fr. drop charge every 60 seconds (not pro rata)” TC 2253: old "4. 90 Fr. per 60 seconds” -> new “ 4. 90 Fr. per 60 seconds (pro rata)” Note that the Headgroup had suggested « per minute (pro rata) instead of « per 60 seconds (pro rata) » . This was not possible, because the application would for example also allow following case: old "4. 90 Fr. per 83 seconds --> new: 4. 90 Fr. per 83 seconds (pro rata)

ONP Topics

Dummy Process & Bakom Number Bloc File Validation rules (CR 1180) § To solve an issue encountered with non-users owning an NPRN. . . Currently, it is not possible to port-in numbers from a TSP which is not an active ONP TSP on Inet and which has an NPRN allocated to him by OFCOM. Inet always checks the OFCOM Number Bloc Allocation File and if a number is included in this file, it will not permit to port this number through another NPRN (e. g. the dummy NPRN). Current process: porting must be done through the Account belonging to the Number Bloc’s NPRN we must provide to the Recipient an access to a User Account (in case it is for example only an INA User) or create a new account for this NPRN with temporary access to the Recipient. This is not a very nice situation as the Dummy Account Process should be used as described in the GUM. § To solve the issue of operators having several NPRNs. . . Another issue related to the Bakom validation file: TSPs with different NPRNs Recipient TSP doesn’t know to which Donor to send Work-Order.

Business Models for Virtual Numbers, MVNOs… Mobile Case § Give MVNOs an access to INet to act directly as Donor or as Recipient? § Routing information must be adapted, in order that the. lpn files contains the correct NPRNs of the networks on which the MVNOs are acting. § Some ideas: New field in the TSP Information to determine the Routing Network? In the INIT screens, the NPRN of the Recipient/Donor is taken for. lpw information, whereas the. lpn files are triggered by the new TSP associated field “network” no. lpn entry in case the field “Recipient network” is the same as the field “Donor network” (e. g. case of a portability from Yallo to Sunrise as Yallo is on Sunrise network). Fixed Operator Case § Vo. IP operators having own number blocs but using a wholesale partner for the routing ? § Other models?