1. Introduction

この節では DetNet Controller Plane framework の RFC 原文を保持し, requirements, control-plane architectures, PREOF, MPLS/IP/Segment Routing considerations, OAM, multi-domain behavior, IANA, security considerations を含めます.

1.  Introduction

   Deterministic Networking (DetNet) provides the ability to carry
   specified unicast or multicast data flows for real-time applications
   with extremely low packet loss rates and assured maximum end-to-end
   delivery latency.  A description of the general background and
   concepts of DetNet can be found in [RFC8655].

   The DetNet data plane is defined in the DetNet data plane framework
   [RFC8938] (and is further explained in the associated DetNet MPLS
   [RFC8964], the DetNet IP [RFC8939], and other data plane
   specifications [RFC9023] [RFC9024] [RFC9025] [RFC9037] [RFC9056]).

   Note that in the DetNet overall architecture, the controller plane
   includes what are more usually considered separate control and
   management planes (see Section 4.4.2 of [RFC8655]).  The management
   plane is primarily involved with fault management, configuration
   management, and performance management (sometimes accounting
   management and security management are also considered in the
   management plane (Section 4.2 of [RFC6632]) but they are out of the
   scope of this document).  At the same time, the control plane is
   primarily responsible for the instantiation and maintenance of flows,
   MPLS label allocation and distribution, and active in-band or out-of-
   band signaling to support DetNet functions.  In the DetNet
   architecture, all of this functionality is combined into a single
   controller plane.  See Section 4.4.2 of [RFC8655] and the aggregation
   of control and management planes in [RFC7426] for further details.

   While the DetNet architecture and data plane documents are primarily
   concerned with data plane operations, they do contain some
   requirements and considerations for functions that would be required
   in order to automate DetNet service provisioning and monitoring via a
   DetNet Controller Plane (e.g., see Section 4 of [RFC8938]).  The
   purpose of this document is to take these requirements and
   considerations into a single document and extend and discuss how
   various possible DetNet Controller Plane architectures could be used
   to satisfy these requirements, while not providing the protocol
   details for a DetNet Controller Plane solution.  Such controller
   plane protocol solutions will be the subject of subsequent documents.
   Therefore, this document should be considered as the authoritative
   reference to be considered if/when protocol work on the DetNet
   Controller Plane starts.