Framework

1
Framework Requirementsfor an Access Node
Control Mechanism in Broadband Multi-Service
NetworksIETF 66 - ANCP WGJuly 9-14, 2006
draft-ooghe-ancp-framework-00.txt Presenter
Stefaan De Cnodder
2
History

• Jan 2006 draft-ooghe-l2cp-framework-00.txt
  submitted for L2CP BOF
• May 2006 draft-ooghe-ancp-framework-00.txt
• Additional author
• Generally reworked to be consistent with the ANCP
  charter
• Terminology
• Use case descriptions
• Added requirements
• General Protocol
• Access Node

3
Outline

• ANCP concept
• Reference architecture
• Home Gateway, Access Node, Aggregation Network,
  NAS
• ANCP transport mechanisms
• ATM gt DSL Forum TR-059
• Ethernet gt DSL Forum TR-101
• Use cases
• Dynamic Access Loop Attributes
• Access Loop Configuration
• Remote Connectivity Test
• Multicast
• Requirements
• Protocol requirements
• Access node requirements

4
Reference Architecture

--------
Policy
Server
--------


----- ----- --------
----- ---------- CPE --- HGW ---

----- ----- Access ---------
Regional
Node --- Aggreg. --- NAS --- Network
----- ----- Node
CPE --- HGW ---
---------
----- ----- --------
----- ----------
Information Reports
--------------------------gt
Control Requests
lt--------------------------
Control Responses
--------------------------gt  
Access Node Control
Mechanism
lt-------------------------gt
PPP, DHCP, IP lt---------gtlt-------
------------------------------gt
5
Use Case 1 - Dynamic Access Loop Attributes

• Communicating Access Loop attributes
• Beneficial since the Access Loop rate may change
  overtime
• NAS gains knowledge about the topology of the
  access network (e.g. for QoS scheduling)

6
Use Case 2 - Access Loop Configuration

• Change Access Loop parameters (e.g. rate) from
  the NAS
• Avoids cross-organization business-to-business
  interactions
• Allows to centralize Subscriber-related service
  data in e.g. a policy server
• The best way to change Access Loop parameters is
  by using profiles
• pre-configured on the Access Node using EMS
• Mechanism could be used for additional parameters
  (e.g. QoS)

7
Use Case 3 Remote Connectivity Test

• NAS can use ANCP to initiate an Access Loop test
  between Access Node and HGW
• Allows mixedATM/Ethernet environment
• Supports multiple Access Loop technologies (e.g.
  ATM/ADSL, Ethernet/VDSL)
• Preserve existing operational functionality

8
Use Case 4 - Multicast

• Resource efficient multicast gets increasingly
  important gt local replication!
• Assumption IGMP processing in access/aggregation
  used for replication control
• ANCP could be used to exchange information
  between Access Node and the NAS
• allow the Access Node to perform replication in
  line with the Subscriber's policy and
  configuration
• allow the NAS to follow each Subscriber's
  multicast group membership

9
Requirements

• Protocol requirements
• functional requirements
• protocol design requirements (e.g., should
  include keep-alive, ...)
• transport of ANCP over ATM/Ethernet network
• Access Node Architecture
• e.g., Partitioning, Redundant controllers
• Access Node Control Connection attributes
• e.g., processing must be timely fashion, Vlans
  for ANCP must be configurable, ...
• Capability Negotiation
• Adjacency Protocol
• Access Node Identification
• In line with TR-101 (e.g. Access-Node-Identifier
  atm slot/portvpi.vci)
• Message Handling
• Damping
• Bundling
• Access Node Parameter Control

10
Next steps

• Add NAS requirements
• Check details for multicast use case
• Work out the security considerations
• Work out element management / policy management
  section
• Use as baseline for ANCP framework WG document?