ANCP Applicability to PON draft-bitar-wadhwa-ancp-pon-00.txt Update on Differences from DSL
Gap between ANCP and TR-147 Hongyu Li Nov. 2009. Introduction Background TR-147 Layer 2 Control...
-
Upload
everett-green -
Category
Documents
-
view
215 -
download
0
description
Transcript of Gap between ANCP and TR-147 Hongyu Li Nov. 2009. Introduction Background TR-147 Layer 2 Control...
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
Target: What’s required in TR-147 but missed in ANCP
Topology DiscoveryR-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”
Line ConfigurationParameters not yet supportedLayer 1 Para. AdminStatus (blocked / released)
Layer 2 Para. ATM VPI/VCI and QoS parameters (for ATM/DSL only)
Rate control
Ethernet (802.1p) queue mapping and scheduling
Port association to a unicast VLAN
Port association to a multicast VLAN
Ethernet/IP para. Access Control List
Source MAC address filter
Destination MAC address filter
Source IP address filter
Max Simultaneous Streams
MulticastR-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