1 / 10

DetNet Controller Plane Framework Summary

This document discusses the DetNet Controller Plane framework, outlining the purpose, terminology, requirements, architecture considerations, and management plane requirements. It emphasizes the support for dynamic creation, modification, and deletion of DetNet flows, along with service protection, explicit paths, resource allocation, and management plane monitoring functions for maintaining network performance. The document also covers control plane architectures, considerations, and next steps for further development in the DetNet domain.

ronchera
Download Presentation

DetNet Controller Plane Framework Summary

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. DetNet Controller Plane Framework draft-malis-detnet-controller-plane-framework-04 Xuesong Geng, Huawei Technologies Andy Malis, Malis Consulting Mach Chen, Huawei Technologies Fengwei Qin, China Mobile Balazs Varga, Ericsson IETF 108

  2. Background & Purpose Background: • The DetNet Architecture defines the DetNet Controller Plane in Sec. 4.4.2: The • Controller Plane corresponds to the aggregation of the Control and Management Planes in RFC 7426 (SDN Layers and Architecture Terminology) Some DetNet drafts (such as the Data Plane Framework) include requirements • for the Controller Plane Purpose: • Compile all DetNet controller plane requirements in one place • Provide an overview of possible control plane architecture/considerations and • give guidance for following control plane work 2

  3. Update Fix the comments from WG and Chairs • Terminology: Hybrid control plane ->Combined control plane • Remove expired references • Editor modification • Add a new co-author • 3

  4. Align with : draft-ietf-detnet-data-plane-framework Section 4 Control Plane Requirements General Requirement: Support the dynamic creation, modification, and deletion of DetNet flows. • Support DetNet flow aggregation and de-aggregation • Allow flow instantiation requests to originate in an end system • Scale to handle the number of DetNet flows expected • Provision flow identification information at each of the nodes along the path • Service sub-layer Requirement: Support service protection, such as: packet replication elimination and ordering • Forwarding sub-layer Requirement: Advertise static and dynamic node and link resources • Explicit path and resource allocation • Queue control techniques • 4

  5. Management Plane Requirements Management Plane Requirements: Monitor the performance of DetNet flows and nodes to ensure that they are • meeting required objectives, both proactively and on- demand. Support DetNet flow continuity check and connectivity verification functions • Support testing and monitoring of packet replication, duplicate elimination, and • packet ordering functionality in the DetNet domain. 5

  6. Control Plane Architecture End System DetNet Node Controller Distributed Control Plane and Signaling Protocols SDN/Fully Centralized Control Plane Combined Control Plane 6

  7. Control Plane Considerations Explicit Paths • Path computation • Path establishment • Strict or loose paths • Resource Reservation • Resource Allocation • Device Configuration • PREOF Support • 7

  8. Management Plane Overview OAM for Performance Monitoring • Active PM • Passive PM • OAM for Connectivity and Fault/Defect Management (CFM) • 8

  9. Next steps Gap Analysis • WG adoption? • 9

  10. Thanks! 10

More Related