6. Multi-Domain Aspects

This section preserves the RFC text for the DetNet Controller Plane framework, including requirements, control-plane architectures, PREOF, MPLS/IP/Segment Routing considerations, OAM, multi-domain behavior, IANA, and security considerations.

6.  Multi-Domain Aspects

   When there are multiple domains involved, multiple Controller Plane
   Functions (CPFs) would have to collaborate to implement the requests
   received from the Flow Management Entity (FME) [RFC8655] as per-flow,
   per-hop behaviors installed in the DetNet nodes for each individual
   flow.  Adding multi-domain support might require some support at the
   CPF.  For example, CPFs of different domains, e.g., PCEs, need to
   discover each other and then authenticate and negotiate per-hop
   behaviors.  Furthermore, in the case of wireless domains, per-domain
   functions specific to Reliable and Available Wireless (RAW)
   [RAW-ARCH], such as Point of Local Repairs (PLRs), have to also be
   considered, e.g., in addition to the PCEs.  Depending on the multi-
   domain support provided by the application plane, the controller
   plane might be relieved from some responsibilities (e.g., if the
   application plane takes care of splitting what needs to be provided
   by each domain).