Framework

1
Framework Requirementsfor an Access Node
Control Mechanism in Broadband Multi-Service
Networks ANCP WGIETF 70 Vancouver
draft-ietf-ancp-framework-04.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
• November 2006 draft-ietf-ancp-framework-00.txt
• March 2007 draft-ietf-ancp-framework-01.txt
• July 2007 draft-ietf-ancp-framework-02.txt
• October 2007 draft-ietf-ancp-framework-03.txt
• November 2007 draft-ietf-ancp-framework-04.txt
• gt 2 re-submissions since last IETF meeting

3
Main Updates in v03 and v04

• Updates in draft-ietf-ancp-framework-03.txt
• multicast
• use case worked out per IETF discussion
• Added corresponding Access Node and NAS
  requirements
• Added multicast related security considerations
• bonding
• addition of a notification to inform NAS about
  configuration changes made by EMS, only
  applicable for use case Access Loop
  Configuration
• Updates in draft-ietf-ancp-framework-04.txt
• Small terminology consistency change (net data
  rate)

4
New Sections

• Section 3. Use Cases for Access Node Control
  Mechanism
• 3.4. Multicast
• 3.4.1. Multicast Conditional Access
• 3.4.2. Multicast Admission Control
• 3.4.3. Multicast Accounting
• 3.4.4. Multicast Termination but this title has
  to be changed
• Section 4. Requirements
• 4.2. ANCP Multicast Requirements
• 4.3. ANCP Security Requirements
• 4.7. Access Node Requirements
• 4.7.6. Multicast
• 4.8. Network Access Server Requirements
• 4.8.6. Multicast
• also updates in section 1.2. Definitions with
  some new multicast related definitions

5
Reference Architecture

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


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

----- ----- Access ---------
Regional
Node --- Aggreg. --- NAS --- Network
----- ----- Node
CPE --- HGW ---
---------
----- ----- --------
----- ----------
Information Report / Admission Request
--------------------------gt
Admission Response / Control
Request
lt--------------------------
Control Response
--------------------------gt
Access Node Control Mechanism
lt-------------------------gt
PPP, DHCP, IP
lt---------gtlt-------------------------------------gt
Updated the description of all components
accordingly to include multicast and bonding
6
Use Case Multicast (1/2)

• Conditional Access
• dynamically control, at the network level, access
  to some multicast flows on a per user basis
• Option 1 AN decides based on pre-provisioned
  access information
• push model Control Request / Control Response
• Option 2 AN queries the NAS for a particular
  multicast flow or for a group of flows
• pull model Admission Request / Admission
  Response
• Admission Control
• Option 1 AN queries the NAS for CAC decision
• pull model Admission Request / Admission
  Response
• Option 2 Policy Server queries the AN (ANCP not
  required)

7
Use Case Multicast (2/2)

• Accounting
• Option 1 AN keeps track of when replication
  starts or stops, generates the time and/or volume
  accounting information and sends it to a central
  accounting system (no ANCP required)
• Option 2 AN keeps track of when replication
  starts or stops and reports this to the NAS for
  further processing
• Information Report
• Termination
• NAS can dynamically stop the replication of a
  multicast flow
• NAS sends Admission Response to AN to terminate
  replication

8
Next Steps

• All comments closed?
• conditional access
• in current draft, default behavior is querying
  the NAS
• this has to be changed into one of the following
• discard Join
• treat multicast flow as best effort
• make it mandatory to configure a catch-all
  entry in one of the lists
• terminology update grey list
• these updates are pending, to be done in v05
• after these updates are done, ready for WG LC?

9

• Backup

10
Terminology

• Line Rate
• total data rate including overhead
• Net Data Rate
• portion of the total data rate that can be used
  to transmit user information (e.g. ATM cells or
  Ethernet frames). It excludes overhead that
  pertains to the physical transmission mechanism
  (e.g. trellis coding in case of DSL)
• Control Channel
• a bidirectional IP communication interface
  between the controller function (in the NAS) and
  the reporting/enforcement function (in the AN)
• Access Node Control Adjacency
• relationship between an Access Node and a NAS for
  the purpose of exchanging ANCP messages. The
  adjacency may either be up or down, depending on
  the result of the Access Node Control Adjacency
  protocol operation.
• Multicast flow
• multicast Any Source Multicast group or multicast
  Source Specific Multicast (S,G) channel

11
Use Case - 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)

12
Use Case - 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)

13
Use Case Remote Connectivity Test

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

14
Access Node requirements

• General Architecture
• Partitioning
• Redundant controllers
• Control Channel Attributes
• Capability Negotiation Failure
• Adjacency Status Reporting
• Adjacency protocol
• Identification
• In line with TR-101 (e.g. Access-Node-Identifier
  atm slot/portvpi.vci)
• The AN MUST use the same ACI format for
  identifying the AN and access port in ANCP, PPPoE
  and DHCP messages
• Multicast
• Message Handling
• Parameter Control
• Damping
• Bundling
• Security

15
Network Access Server requirements

• General Architecture
• Partitioning
• Shaping based on Dynamic Access Loop Attributes
• Access Loop Configuration
• Remote Connectivity Test
• Control Channel Attributes
• Capability Negotiation Failure
• Adjacency Status Reporting
• Identification
• In line with TR-101 (e.g. Access-Node-Identifier
  atm slot/portvpi.vci)
• Multicast
• Message Handling
• Wholesale Model
• Communicate Access Loop Attributes to an LNS
• Security