Using Entropy Label for Network Slice Identification in MPLS networks.
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|Authors||Bruno Decraene , Clarence Filsfils , Wim Henderickx , Tarek Saad , Vishnu Pavan Beeram , Luay Jalil|
|Last updated||2022-02-07 (Latest revision 2021-08-06)|
|Stream||Stream state||(No stream defined)|
|RFC Editor Note||(None)|
|Send notices to||(None)|
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
This document defines a solution to encode a slice identifier in MPLS in order to distinguish packets that belong to different slices, to allow enforcing per network slice policies (.e.g, Qos). The slice identification is independent of the topology. It allows for QoS/DiffServ policy on a per slice basis in addition to the per packet QoS/DiffServ policy provided by the MPLS Traffic Class field. In order to minimize the size of the MPLS stack and to ease incremental deployment the slice identifier is encoded as part of the Entropy Label. This document also extends the use of the TTL field of the Entropy Label in order to provide a flexible set of flags called the Entropy Label Control field.
Vishnu Pavan Beeram
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)