1 / 6

Framework & Requirements for an Access Node Control Mechanism in Broadband Multi-Service Networks

Framework & Requirements for an Access Node Control Mechanism in Broadband Multi-Service Networks. draft-ietf-ancp-framework-00.txt Presenter: Stefaan De Cnodder. History. Jan 2006 – L2CP BOF: draft-ooghe-l2cp-framework-00.txt May 2006 – IETF66: draft-ooghe-ancp-framework-00.txt

chiku
Download Presentation

Framework & Requirements for an Access Node Control Mechanism in Broadband Multi-Service Networks

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. Framework & Requirementsfor an Access Node Control Mechanism in Broadband Multi-Service Networks draft-ietf-ancp-framework-00.txt Presenter: Stefaan De Cnodder

  2. History • Jan 2006 – L2CP BOF: draft-ooghe-l2cp-framework-00.txt • May 2006 – IETF66: draft-ooghe-ancp-framework-00.txt • November 2006 – IETF67: draft-ietf-ancp-framework-00.txt • reworked terminology to be consistent • added requirements • Network Access Server • Management related requirements • very few of existing requirements updated • no changes in the general architecture and use cases

  3. Terminology / Definitions • Net Data Rate • defined by ITU-T • 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) • this document uses mainly Net Data Rate and not Line Rate • Line Rate • total data rate including overhead • Access Node Control Mechanism • Control Channel • previously called control connection • a bidirectional IP communication interface between the controller function (in the NAS) and the reporting/enforcement function (in the AN) • Access Node Control Session • previously called Access Node Control connection • an instantiation of ANCP running on top of the Control Channel

  4. Access Node requirements • A few requirements removed/added/updated, most important changes: • identification of AN and access port: use the same Access Circuit Identifier in ANCP, PPPoE and DHCP messages • encapsulation of ANCP over ATM is more limited: must now be according to RFC2684 routed encapsulation (IPoA)

  5. 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 • Identification • In line with TR-101 (e.g. Access-Node-Identifier atm slot/port:vpi.vci) • Message Handling • Wholesale Model • Communicate Access Loop Attributes to an LNS

  6. Next steps • Work out the multicast use case • Work out the security considerations • Simply refer to draft-moustafa-ancp-security-threats-00.txt ? • Comments • detailed comments already received from Woj on the mailing list, as discussed on the mailing list • requirements have to be reworked: more focus on protocol requirements and less focus on AN/NAS requirements • more clarifications wrt transaction oriented nature of ANCP and terminology • more comments?

More Related