NGNuk Execuitve Meeting - 29th March 2007

Attendees

Peter Black (NGNuk) - Chair

Peter Ryde (NGNuk)

Andy May (Cable & Wireless)

Steve Unger (Ofcom)

Phil Male (Thus)

Alireza Mahmoodshahi (Colt)

Stuart Shutt (Orange)

Andy King (Virgin Media)

Neil McArthur (Opal)

John Morden (BTW)

Apologies:      

Justin Fielder (Easynet)

Huw Saunders (Kingston)

Angus Flett (BT Wholesale)

Robyn Durie (T-Mobile)

Phil Kirby (Vodafone)

Agenda

  • Minutes and Actions from last meeting (22nd February 2007)
  • Analysis of Charging Model feedback
  • Requirements activity
  • NICC Update
  • Commercial Update
  • Programme Plan
  • AOB

Minutes and Actions of Previous Meeting (22/02/2007)

  • Minutes - No changes to the draft minutes had been received. The minutes of the last meeting were therefore accepted

  • Actions - See outstanding actions update at the end of this document

Analysis of Charging Model feedback

Richard Cadman (SPC Network) attended the Exec meeting to present back on the first phase of his work for NGNuk. This covers:

  1. Review responses from Members to identify any inconsistencies within the feedback for NGNuk to resolve
  2. Apply the feedback to existing voice services and products e.g. origination, termination, NTS and messaging ( e.g. SMS) etc. to demonstrate which charging model is most consistent with NGNuk member output for each service.

The summary the presentation indicated that member's views pointed towards:

  • maintaining the current mix of charging principles
  • that there would be some inefficiencies, but these are outweighed by
  • Consumer familiarity - no harm done
  • Ability of calling party's CP to capture value of call and so recover investments
  • NGN charging principles should not preclude any basis for new services

The following observations and comments were made:

  • The starting point for the work was that the overall impact of any change should do no harm to the Consumer and that any changes should bring benefits to the consumer through lower costs or innovation. The review looks at how the feedback supports the principle and how it might be justified through consumer benefit
  • That the definitions of each of the charge models needs to be clarified within the paper vs. other definitions that are in circulation ( for instance the definitions in the paper differ from those used by the ERG)
  • Overall feedback lends more support to CPP though this might be better interpreted as support for the status quo given use of RPP for 0800. A discussion took place regarding the need for effective regulation of termination to support any CPP implementation. It was recognised that B&K would remove such a regulatory requirement however it was felt that this assumes equal "utility" in terms of the benefits of the communication to both parties ( calling and called). This was not felt to be the case , as witnessed by SPAM over the Internet.
  • There was no real difference in feedback around CPP though feedback on RPP and B&K showed a number of principles where responses were contradictory. The Exec requested that the charts showing the impact of the principles on the service types split out in greater detail.

Action 1 - 29/03/2007 -  Richard Cadman to break out Voice in greater detail in the final version of the presentation.

  • Publication options were discussed. As the work largely details  the planning assumptions being used by NGNuk rather than NGNuk presenting these as being the "only" answer it was felt that they should be made public but in a way that did not solicit substantive responses
  • Richard anticipated the first draft of the article (for external consumption) prior to Easter

Requirements Activity

End-to-End Requirements Definition

Feedback had been received from the majority of members on the first draft . Calls had taken place with Cognos to review the responses with the authors.

An updated version had been sent out on 16th March with a request for comments by 28th March. To facilitate a response each author and programme board representative had been sent an audit trail of how their comments had been incorporated or dealt with. 3 responses had been received.

It was agreed that the E2E be put on the web site and that public comments be invited.

Interconnect Requirements Definition

A revised content listing for the Interconnect Requirements had been issued for comment on 14th March. This brings the contents into line with the E2E documentation.

The first draft of the Interconnect Requirements was issued on 26th March with responses requested by 13th April. Responses will be treated as per the E2E requirements document namely all respondents will be interviewed and will receive and audit trail of how their comments have been treated.

The Exec agreed that the Interconnect Requirements will be published for comment on the NGNuk website once they are sufficiently complete. They requirements will not have to be represented to the Exec meeting however endorsement via email will be required.

Leo Todd (Cognos) gave a brief overview of the 1st draft in terms of the underlying inputs and where he felt the requirements lacked information. He felt the key requirements missing detail were Near Real Time and Streaming

NICC Feedback

Green Release status

The TRG had reviewed the status of the Green Release against the plan and it's status had been moved to Red.

The delays had been caused by initial confusion regarding the more detailed specification of the requirements themselves, through the non availability of resources to support the requirements and due to the non availability of some international standards. In some areas NICC has draft text developed but industry has been unable to review in other areas no draft text is available

TSG007 Mandatory Requirement ID.

Summary Requirement

RAG

I

SIP for IMS, Internet and PSTN

Fixed-Mobile Interconnect Service (F-MIS)

Red

J

Bandwidth management, codec negotiation

Red

K

Different Packetisation rates for Services

Red

L

Number Admin and Routeing

 Red

M

Emergency Calls and EGTPS

 Red

N

VLA Tranche 1

 Red

O

Overload Control

 Red

P

Routed Layer 3 Transport - to be dropped

 

Q

Improved MSI Failure Detection

 Red

Additional (C21) Requirements

Summary Requirement

 

 

Overlap Signalling Best Practice Guide - NNA WG anticipated completion end January 2007

 Green

 

Voice Packet Delay Variation

 Red

 

B2B

 Green

Purple Release Further Requirements

 

 

 

Emergency Calls and EGTPS

 Green

The TSG is to meet on the 24th April to determine whether to delay or re-scope the Green Release.

The subsequent Exec discussion covered a number of points:

  • The Exec believed that NICC should follow the lead given my NGNk in terms of prioritisation

  • The Exec asked that NICC provide more detail on the status of each requirement in terms what is causing the underlying delay and what is required for completion

Action 2  - 29/03/2007 - Peter Ryde to liaise with Paul Rosbotham to provide the Exec with more detail on the status of each requirement within the Green release and specifically what is causing the underlying delay and what is required for completion

  • A discussion took place regarding the impact of non availability of standards and whether NGNuk at an industry level might be able to influence these

Commercial Update

Charging Framework

The programme plan to develop the charging framework for the priority services was presented to both the Commercial Group and the Exec at the end of Feb. The plan proposed two reviews with CP's. The first at a high level and the 2nd a more detailed evaluation based on the output of the first.

The plan showed that CP's should now be providing input as part of the initial round however, the  feedback on the initial draft of the questions was that CPs were unlikely to hold sufficiently detailed views on what might be chargeable or how these might be charged. A revised approach presented by the Secretariat created similar concerns. Final agreement was obtained at the commercial meeting on 15th March subject to a "workshop" developing some support material on what might be chargeable. This work shop was held on 26th March.

This element of the programme has therefore been delayed by a month. It may lose further time if CPs feel that further preparation work ( beyond the output of the workshop ) is required.

Interconnect locations and numbers

Following the last Exec meeting the draft paper on Interconnect Numbers and Locations was updated to reflect the Exec comments. No comments on the final paper were received from either the commercial group or the Exec so it was forwarded to BTW on 16th March.

Subsequently Viatel have expressed a concern that their requirement for a small number of interconnects was not adequately represented in the final paper.

John Morden (BTW) had provided a written summary of BTW's initial response to the NGNuk document on Interconnect numbers and locations recently sent by NGNuk

In summary:

  • BT shares the view that IP networks will require fewer, larger interconnect points
  • That in BTW view the increased need for resilience at these fewer sites places limitations on suitable sites that BTW might use <//font><//font><//font><//font><//font><//font>
  • That BTW will review the 3 substitute sites and hopes to respond by the end of April
  • The additional 10 interconnect sites suggested by NGNuk will be considered via the Consult 21 channel . These sites would not have the level of resilience of a core site
  • BT would investigate resolving the potential "SAD type" issue by withdrawing all switching from the remaining metro nodes
  • Changes to 21CN design will be via the SOR process and subsequent consultation
  • BTW cannot comment on the distance gradient and suggested that NGNuk pick this up as a specific objective to model this across industry
  • That the information requested on connectivity between Core and Metro has been published via Consult 21

Details of what product is to be available where should be made via Consult 21

The following points were raised and discussed by the Exec:

  • The issue of resilience of any additional nodes was discussed and that as part of the process resilience information would be made available
  • There was concern that the paper had been taken by BTW as a definitive position or agreement. The view of NGNuk is that it is an iterative process requiring feedback from BTW to allow NGNuk to refine it's position. The NGNuk paper is therefore more akin to a discussion document not any form of agreed position. It is however an industry view and as such should be carry the more "weight" than the views of an individual CP. The Exec therefore expressed concern that a paper seeking feedback would initiate work via the Consult 21 process. The Exec requested that NGNuk review any BTW information to refine it's position prior to any C21 consultation document's  wider release to industry and in addition BTW to respond to NGNuk before anything goes through the Consult 21 progress.

Action 3 -29/03/2007 : BTW to respond in detail regarding the NGNuk paper prior to the NGNuk paper entering the Consult 21 process.

Action 4 -29/03/2007 : Peter Ryde to write to Consult 21 to reconfirm the scope of the NGNuk paper and to seek dialogue prior to the release of any Consultation document so that NGNuk can refine it's position should this be appropriate

  • The Exec welcomed the BTW position of trying to address the potential for SAD type issues. It would await feedback from BTW.
  • The Exec noted that BTW had not stated that design decisions today would not foreclose future options for varying interconnect numbers or locations
  • The Exec stated that they expected any additional interconnect nodes to have the same level of capability and resilience as the existing 20 proposed by BTW
  • The Exec endorsed the suggestion by BTW that an industry wide cost model to analyse industry distance gradients be developed. There was some discussion regarding whether this should focus on distance or nodes ( since distance might not remain a good proxy for the elements used within a network).Andy May agreed to develop the brief for this and all agreed that the ability (and willingness) to divulge sensitive internal cost information to an agreed third party would be vital. All agreed to their organisations willingness to do this though it was felt that Board level confirmations and also stronger assurances regarding information confidentiality would be required.

Action 5 - 29/03/2007 : Andy May to develop outline consultants brief to identify industry distance gradients ( and / or nodal costs) for comment

  • The Exec noted the statement on Consult 21 providing the definitive position on what products would be interconnected where. Following receipt of these it may be appropriate to map these against what the NGNuk interconnect requirements are seeking.

Action 6 - 29/03/2207  : BTW to provide a definitive statement to NGNuk on what products and services will be interconnected where ( C-MSAN , F-MSAN, Metro and Core)

  • The requirement for Ethernet backhaul and aggregate backhaul was raised but was agreed as being outside the scope of the NGNuk interconnect paper

Programme Plan and Scope

Programme Plan

An updated Programme plan was presented to the Exec. This is appended. It was noted that the overall programme scope would be presented at the April Exec. This would necessitate a major overhaul of the programme plan as far more detailed information would be available.

The Programme Board on 3rd April will be asked to review the initial draft programme scope derived from the draft E2E and Interconnect Requirements. This and the subsequent Programme Board meeting would aim to agree the scope of the work streams, an outline of the resources, outputs and timing. It would be presented to the Exec in April for comment and endorsement. It was requested that the Exec ensure that their representatives attend the Programme Board on 3rd April.

Action 7 - 29/03/2007 -  Exec members to ensure that their representatives on the Programme Board attend the 3rd April meeting

Issues Arising from Requirements Process

As part the requirements definition process a number of issues were identified which affect the overall Programme scope. These were discussed with the Exec as follows:

Interconnect Framework

Implicit in documentation submitted by members and explicitly requested in some comments there is an implicit assumption that the framework for NGN interconnects will be based on PSTN interconnect constructs but this is not documented. Documenting this would add clarity to the work programme, gives direction to other work elements.

The Exec agreed to make the implicit assumption explicit. The existing PSTN framework will be used as the starting point for the framework for NGN Interconnections and changes should only be made where this would lead to tangible customer benefits and an improved framework.

Action 8 - 29/03/2007 - Leo Todd to incorporate within next draft of interconnect requirements.

QoS

From explicit references in requirements documentation there is a consistent requirement for QoS classes to support the end-to-end and interconnect services. QoS is at the core of the service definitions. Early agreement on the number and characteristics will provide a sound basis for future work.  

The Exec agreed to task NICC with the action to validate the choice of 4 payload QoS Classes, to define their characteristics, to demonstrate how they would support the service requirements and highlight any shortcomings.

Action 9 - 29/03/2007 - Peter Ryde to scope action regarding the validation of 4 QoS classes and pass to NICC.

Numbering and Addressing

Within the requirements there is a definite requirement for E.164 and number translation but there is no clear requirement on the wider requirements of numbering and addressing. This needs to be addressed or it will impair service portability, one of the stated aims in NGNUK.

Exec to agreed that the work programme needs to review the wider opportunity surrounding numbering and addressing in line with the principles of NGNuk and well beyond E.164. This will be addressed as part of the overall programme scope.

Multilateral Interconnects

The impact of whether services would be interconnected on a bilateral or multilateral basis will affect the scale and scope of the work programme. It was agreed that the Exec needed to decide on whether specific service types are SMP and/or are the subject of multilateral interconnects.

It was agreed that Andy King would propose a framework for how this might be reviewed.

Action 10 - 29/03/2007 - propose a framework by which the requirements of CPs for multilateral vs. bilateral interconnect can be established. Andy King.

Authentication

No authentication model is in place to mirror that implicit in legacy networks.  High level agreement on an industry wide approach to shape Interconnect Requirements and subsequent work plan is required. This would affect work on security, quality, service degradation though SPIT, SPAM and spoofing etc.

Phil Male offered to develop a framework proposal for discussion amongst the Exec.

Action 11 -29/03/2007 - Phil Male to develop a framework proposal for a high level industry wide approach to authentication.

Presence

Specific requirements exist for presence services. There is no clarity on whether presence would be part of multi-lateral interconnect scope and how (or if) it would be charged.

The longer term requirements for presence may have significant impact on service design, ubiquity and portability (cf the value and utility that presence/location creates in mobile networks). It was felt also that requirement for presence also touched on the "Net Neutrality debate"

It was agreed that Stuart Shutt would review the benefits of mandating the sharing of presence information across industry and the potential impact of making this chargeable or otherwise.

Action 12 - 29/03/2007 -  Review the benefits of mandating the sharing of presence information across industry and the potential impact of making this chargeable or otherwise. Stuart Shutt

AOB

OTA2

Peter Black discussed his email of 20th March regarding the evolution of the OTA and it's impact on NGNuk. This was largely related to shared resource around programme management and Chairmanship. The Exec were comfortable with what had been proposed.

Payment

Some invoices for 2006/7 are still outstanding whilst 2007/8 invoices will be issued shortly. The Exec were informed that an additional invoice covering VAT for 2006/7 will also be issued shortly.

ISPA letter of Concern

A letter dated 6th March had been received. This raised a concern that the interests of the wider internet community were not being fully considered at NGNuk meetings and that the transparency of NGNuk remains an ongoing concern for the ISPA council. Finally the letter enquired about the review detailed within the NGNuk constitution.

It was noted that 3 NGNuk members have representatives on the ISPA council yet no concerns had been raised by these members nor were the Exec representatives of NGNuk aware of the ISPA letter.

The concerns were discussed by the Exec. The Exec agreed that the minutes published on the public web site were a fair reflection of the overall status, that individual ISPA members have the opportunity to join NGNuk, that associate membership is open to ISPA and that ISPA can raise specific concerns or provide specific inputs to via the Secretariat.

The ISPA letter made reference to section 17.3 of the constitution which makes reference to a 6 month review by Ofcom. Steve Unger stated that no member of the Exec had requested this, nor any other member. It was therefore inappropriate to initiate a review at this point in time. In addition Ofcom would also consider initiating a review if it had concerns about the programme which it felt was not being addressed. This is not the case at this time. In addition Peter Black reminded the Exec of his request for feedback on progress that was discussed at the January 2007 Exec meeting

The Secretariat would respond to the ISPA letter conveying the points discussed by the Exec.

Review

Peter Black stated that as the next Exec will review the overall programme scope and that this will coincide with the issuing of the 2007/8 invoices that he would be seeking to initiate a wider review of the commitment towards meeting these goals

Next Meeting

The next meeting will be 10.00 to 14.00 on 26th April 2007 at Riverside House.

Future scheduled meetings:

Date

Meeting

Time

31st May 2007

NGNuk Executive Meeting

10.00 - 14.00

 

Peter Ryde

NGNuk Office

07771 555 048

020 7783 4688

peter.ryde@ngnuk.org.uk

 

Outstanding Action List

Action 3 - 26/6 - Peter Black undertook with the help of Ofcom to take the necessary steps to apply for registration of the 'NGNuk' logo.27/7 - Application for registration of the NGNuk logo is in preparation by Ofcom. Steps have already been taken to secure URLs 'ngnuk.org.uk' and 'ngnuk.co.uk'. Unfortunately, 'ngnuk.com' is already reserved. 28/9 - The application was registered at the beginning of September and the trademark attorneys are now waiting for the trademark office to process it. This normally takes about 6 weeks, so we should hear something in about 2-3 weeks. 26/10 - the trademark lawyer is still waiting for the application to be processed by the trademark authority. It has taken longer than normal. 14/12 Still awaiting a response from the Trademark Authority . Update - the NGNuk trademark was published by the UK Trademark Office on 1st December 2006. The 3 month period for objections has passed without event and the trademark was confirmed on 16 March. The paperwork has yet to reach us.

NGNuk Secretariat

27/7/2006

Completed

Action 5- 25/01/2007 - Peter Ryde to progress NGNuk Requirements Scope document to Final Draft stage in readiness for formal review and agreement by the full membership by the end of February. Comments received on 2nd draft. Updated draft to be put on the NGNuk web site for public comment.

Clive Fedida

28/2/2007

Ongoing

Action 6 - 25/01/2007 - Secretariat to provide an updated Programme Plan at the end of Feb Copy included within Minutes

Secretariat

Completed

Action 7 - 25/01/2007 In discussion with NICC to identify where NICC require NGNuk commercial input to facilitate progress on the technical solutions for ENUM for discussion at the Feb Exec. No support required immediately. Activity will be addressed within overall NGNuk scope.

Secretariat

Deleted

Action 1 - 22/02/2007  - provide a more detailed listing of the products which the Charging Framework programme will address. Incorporated within the documentation in line with Exec minutes of 22nd Feb 2007

Charging Work Group

Completed

Action 2- 22/02/2007  - update Programme Plan in line with Exec comments and distribute.

Peter Ryde

Completed

Action 3 - 22/02/2007 - To update the work group recommendations on interconnect numbers and locations to reflect the views of the Exec. The updated document to be circulated to the Exec for agreement. Agreed document sent to BTW on 16th March

Peter Ryde

Completed

Action 4 - 22/02/2007 - Brief Cognos to widen the scope of draft interconnect requirements to include NGN to Legacy interconnection for voice services. Ist draft includes this.

Peter Ryde

Completed

Action 5 - 22/02/2007 - Ofcom to discuss with Professor Sir John O'Rilley NICC actions required to support the Green Release being delivered to plan.

Steve Unger

Action 6 - 22/02/2007 - Exec members to respond (to Peter Ryde) regarding the resource requirements and / or lack of support identified within resource plan provided by NICC (Paul Rosbotham) . A view of where how their vendors might better support NICC should be provided as part of this. Paul Rosbotham stated that Orange, Thus and Colt had made contact. In addition Thus stated they had approached Nortel regarding support for NICC.

Exec

02/03/2007

Ongoing

Action 7 - 22/02/2007 - Secretariat to draft letter to be sent by NGNuk to vendors to solicit greater support for NICC in the development of the Green Release and distribute to Exec for comment. Draft prepared but not yet circulated

Secretariat

Ongoing

Action 8 - 22/02/2007 - Confirm the status of the Terms of Reference covering interaction of NGNuk with NICC within NICC. These are agreed by the NGNuk Exec and are required to be endorsed by the NICC Exec in April

Peter Ryde

Ongoing

Action 9 - 22/02/2007 - Secretariat to confirm status of Nominet versus the membership criteria detailed within the constitution.  The terms of the NGNuk constitution state that " membership is open to any company that is an Electronic Communications Network or Service Provider that has a bona fide and demonstrable intention to interconnect , use or invest in NGN in the UK". Whilst it was recognised that Nominet would make a valuable contribution to the work groups they did not comply with the membership criteria. This stimulated a wider debate and the Exec felt that where non members felt they could actively contribute to a work stream they should be allowed to offer this. It would be up to the work stream leader to determine whether such assistance was required or appropriate. Two actions were placed on the Secretariat, firstly to review the constitution as to any changes required to facilitate this and secondly to develop some guidance for work stream leaders.

Secretariat

Completed

New Action List

Action 1 - 29/03/2007 -  Break out voice in greater detail in the final version of the presentation on Charge Model Analysis

Peter Ryde

Richard Cadman

Action 2  - 29/03/2007 -NGNuk to liaise with Paul Rosbotham to provide the Exec with more detail on the status of each requirement within the Green release and specifically what is causing the underlying delay and what is required for completion

Peter Ryde

Action 3 -29/03/2007 : BTW to respond in detail regarding the NGNuk paper prior to the NGNuk paper entering the Consult 21 process.

BTW

Action 4 -29/03/2007 : NGNuk to write to Consult 21 to reconfirm the scope of the NGNuk paper and to seek dialogue prior to the release of any Consultation document so that NGNuk can refine it's position should this be appropriate

Peter Ryde

Action 5 - 29/03/2007 : develop outline consultants brief to identify industry distance gradients ( and / or nodal costs) for comment

Andy May

Action 6 - 29/03/2207  : provide a definitive statement to NGNuk on what products and services will be interconnected where ( C-MSAN , F-MSAN, Metro and Core)

BTW

Action 7 - 29/03/2007 - Members to ensure that their representatives on the Programme Board attend the 3rd April meeting.

Exec

Action 8 - 29/03/2007 -Incorporate that the interconnect framework should be developed from existing voice frameworks unless positive benefits of change for the consumer are identified, This should be included within next draft of interconnect requirements

Leo Todd

Peter Ryde

Action 9 - 29/03/2007 - Scope request regarding the validation of 4 QoS classes and pass to NICC

Peter Ryde

Action 10 - 29/03/2007 - Propose a framework by which the requirements of CPs for multilateral vs. bilateral interconnect can be established.

Andy  King

Action 11 -29/03/2007 - Develop a framework proposal for a high level industry wide approach to authentication

Phil Male

Action 12 - 29/03/2007 -  Review the benefits of mandating the sharing of presence information across industry and the potential impact of making this chargeable or otherwise.

Stuart Shutt

Action 13 - 29/03/2007 -  review the constitution as to any changes required to facilitate allowing non members to participate within the work streams ( when requested to do so by a work stream leader)

Peter Ryde

Action 14 - 29/03/2007 -  Develop guidance notes for work stream leaders regarding the use of non members within a work stream.

Peter Ryde