1 / 5

Gap between ANCP and TR-147

Gap between ANCP and TR-147. Hongyu Li Nov. 2009. Introduction. Background TR-147 Layer 2 Control defines business requirements GSMP was chosen as the proper base to implement L2C ANCP was given birth Gap Analysis Method TR-147 provided requirements for ANCP but not limit ANCP.

pravat
Download Presentation

Gap between ANCP and TR-147

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Gap between ANCP and TR-147 Hongyu Li Nov. 2009

  2. Introduction • Background • TR-147 Layer 2 Control defines business requirements • GSMP was chosen as the proper base to implement L2C • ANCP was given birth • Gap Analysis Method • TR-147 provided requirements for ANCP but not limit ANCP • Target: What’s required in TR-147 but missed in ANCP

  3. Topology Discovery R-60 The Access Node SHOULD be able to wait to send a Port Status Report message until the characteristics of the access port are stable for a minimum time period. This avoids sending multiple Port Status Report messages in case of several consecutive changes in that time period (e.g. due to DSL resync). In the case where the Access Node performs this process, then such a time period MUST be configurable. R-61 The Access Node MUST send a Port Status Report message to the BNG each time the Access Port attributes change above a threshold value during the time the RG is active. This threshold SHOULD be configurable. R-62 It may happen that a DSL line becomes unstable and continues to switch between Port Up and Port Down states for a certain time period. In this case, the Access Node SHOULD inform the BNG that the line is unstable. The time period to conclude that the DSL line is unstable SHOULD be configurable. Informing the BNG about the unstable line can be done by means of a Port Status Report message. • Issue: Not mentioned in current drafts; doesn’t support noting “unstable”

  4. Line Configuration

  5. Multicast R-38 The Access Node MUST support dynamically creating and deleting the association between an access port and a set of multicast VLANs, on receipt of an L2C message containing this mapping. R-83 The BNG MUST support the ability to send an L2C message towards the AN, specifying the mapping of the Access Port’s ACI to the set of retail ISP multicast VLANs associated with the Access Port. R-84 The BNG MUST be able to send an L2C message to the AN, removing any mapping between that Access Port’s ACI and retail ISP multicast VLAN(s). • Issue: ANCP doesn’t support sending mapping of an access port and multicast VLANs R-81 The BNG MUST be capable of configuring the Access Node with the ‘maximum number of multicast streams’ allowed to be received concurrently per Access Port. • Issue: ANCP doesn’t support such configuration

More Related