1 / 8

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-01.txt Presenter: Stefaan De Cnodder. History. Jan 2006: draft-ooghe-l2cp-framework-00.txt submitted for L2CP BOF May 2006: draft-ooghe-ancp-framework-00.txt

honorato-pearson
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-01.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 • Reworked based on numerous comments at IETF67 & ANCP exploder

  3. Terminology • Access Node Control Adjacency • The relationship between an Access Node and a NAS for the purpose of exchanging Access Node Control Messages. The adjacency may either be up or down, depending on the result of the Access Node Control adjacency protocol operation. • Extra clarification in definition of Control Channel and Access Node Control Session

  4. Use Cases • The 4 use cases are still the same • Example added about Hierarchical Scheduling performed by the NAS in use case “Dynamic Access Loop Attributes” • Some editorial improvements were done • more clarification on transactional nature of ANCP • ...

  5. Requirements • Section 4.1: ANCP Functional Requirements • lots of editorial updates (transactional nature, reliability, fast-pace processing of ANCP messages) • scalability requirements (NAS must control thousands of ANs) • security requirements moved to separate subsection • new subsections introduced but this is mainly done to better group the existing requirements (e.g., new subsections on ANC Adjacency requirements, new subsections on security, ...) • Many editorial improvements for extra clarification

  6. Security Considerations • This section is now completed • Reference is made to draft-ietf-ancp-security-threats-00.txt • The requirements from draft-ietf-ancp-security-threats-00.txt are also put in the framework document

  7. Next Steps (1/2)Open Issue on Multicast Use Case • Closure on multicast use case • Current draft says: • IGMP processing in access/aggregation used for replication control using IGMP proxy/snooping • ANCP could be used to exchange information between Access Node and the NAS • e.g., allow the Access Node to perform replication in line with the Subscriber's policy and configuration, which might only be known in the NAS • Question: • Leave as is? • Drop due to insufficient detail? • Specify details?

  8. Next Steps (2/2) • Multicast Use Case? • should Node requirements be translated into protocol requirements? • when these two issues are solved, the draft looks ready for last call

More Related