C21 Cochair event

1
BT WholesaleMulticast Condoc15th June,
2007Ryan Hardy
2

• Cautionary Statement - BT's 21st Century Network
  is still in the process of development and the
  subject of consultation. The information in this
  presentation may be subject to change

3
Multicast

• Condoc was focused on the Multicast aspects of
  the WBC Product
• 6 Responses from Customers
• The Questions asked were
• Architecture
• Use of recommended DSL TR101?
• Static or Dynamic multicasting?
• Single VC/PPPoE CPE issues?
• CPE compatibility testing
• Commercial structure
• Ability to connect to other customers content?
• Ability for other customers to connect to your
  content?
• Ideas on Pricing for multicast capability?

4
Multicast Architecture

• Question 1 - BT Use of DSL Forum TR-101
• All CPs support the recommended implementation of
  DSL Forum TR-101
• 1 CP identified that support for L2TP is required
• BTW will support L2TP and do not foresee any
  issues
• Note that reconfiguration of the Customers LNS
  may need to be considered - detailed information
  available on request
• Note that improvements to PTA solutions are being
  made to give L2TP comparable control to CPs and
  allow for further CP TOC reduction

5
Multicast Architecture

• Question 2 - Static and Dynamic Multicasting
• 3 CPs identified Dynamic Multicasting as the
  preferred solution
• 2 CPs stated that Static Multicasting is
  acceptable for as an early implementation
• BTW response - Dynamic and Static Multicasting
  are appropriate for different kinds of broadcast
  implementations
• Static is more suitable for the bulk broadcast of
  linear TV channels
• Dynamic better suits niche channel distribution.
• 1 CP raised using Multicast for Software
  distribution
• BTW response - Multicasting is intended to be
  implemented as content distribution solution and
  is therefore not limited to the transport of live
  Video streams
• BTW are giving consideration to broadcast TV
  channel aggregations, this would allow for single
  BTW ingestion of a TV channel (e.g. BBC1) to be
  made available to all CPs

6
Multicast Architecture

• Question 3 - Single VC with IPoE and PPPoE
• 4 CPs have no issues with this proposed
  architecture (though 1 CP had issues with PPPoE)
• BTW look to work with CPE vendors and CPs to
  address the issues identified
• Potential issues identified with CPE in the
  following areas
• Support for TR-101
• Support for Routing rather than Bridging
• Support for PPPoE rather than PPPoA
• Migration between IPStream 20C/21C and wBC
• The proposed implementation will not work with
  PPPoA
• BTW are committed to provide relevant testing
  facilities to mitigate against these issues
• 1 CP asked about IGMP over IPoE - BTW Update from
  Feasibility has identified that IGMP forking to
  both the IPoE and PPPoE session may be required

7
Multicast Architecture

• Question 4 CPE Support
• A very wide range of CPE from numerous
  manufacturers have been identified
• A non exhaustive list includes the following
  suppliers
• Netgear, Scientific Atlanta, Thomson, 2Wire
• Huawei, Motorola, Pirelli, Sagem, Telsey,
  Tilgin, Zyxel,
• Ambit

8
Multicasting Commercials

• Question 5 Connection to 3rd party CP Multicast
  streams
• A mixture of response
• 3 CPs positive response
• 1 CP No response
• 1 CP Not considered
• 1 CP Via direct CP to CP connection and not via
  BTW
• Question 6 Connection of your Multicast Stream
  to 3rd party CPs
• 5 CPs would like the ability for 3rd Party CPs to
  connect to their Multicast content streams
• 1 CP no comment

9
Multicasting Commercials

• Question 7 Suggestions on Pricing
• 3 CPs suggested a link to consumed bandwidth and
  footprint
• 1 CP identified charging direct to the Content
  Provider, this could be by the CP or BTW
• BTW comment - This could align with BTW acting as
  a channel aggregator
• 1 CP Should be low cost and separate from Data
  charging
• 1 CP suggested a price no higher than Best
  Efforts as an upper limit
• BTW comment - Complementary services, such as
  Unicast Content Distribution, could be considered
  in place of Dynamic Multicasting in some
  situations
• Further information available via Content Connect
  briefings
• Key message from BTW is that open discussion
  between CPs, BTW, Ofcom and potentially Content
  Providers will be required

10
Comments Other Points

• 2 CPs commented on Multicast Role out,
  availability Demand
• Currently only planned to be support on wBC
• Roll out may be constrain by 21C and wBC
  deployments
• Desire to have Dynamic Multicast available
  outside CPs LLU foot print by some CPs
• 1 CP identified potential problems with
  non-standard implementations
• Commitment from BTW to avoid proprietary
  implementations
• Implement standardised solutions to minimise
  impact to CPs e.g. TR101 RACS/TISPAN
• Work with CPs to ensure their needs are met
• Ensures maximum interoperability between vendor
  platforms for CPs

11
Whats next?

• Work with industry to create an acceptable
  pricing structure
• Open Consultation on Content Connect for Unicast
  Content distribution