jiebi/ids-paragraph-commentary-corpus huggingface dataset:
Draft: draft-ietf-ccamp-yang-otn-slicing

Commentary: Merging changes for IETF-115 draft submission .
Alternatively, an OTN slice may be mapped to a NRP as an overlay
abstract OTN TE topology on top of the underlay topology.  The
corresponding link resources allocated to the slice is encapsulated
in and tracked by the abstract topology, and a given link or port in
the NRP topology represents resources that are reserved in the
underlay topology.  One slice topology for a resource-based OTN slice
is typically realized by one dedicated NRP topology, and all the
resources within that NRP topology are reserved for the OTN slice.
In this case, the use of NRP eliminates the need for coloring links
in the underlay topology, and the NRP topology may be pushed directly
to the subtended MDSC or PNC by the OTN-SC.
Multiple OTN slices may be mapped to the same NRP, and a single
connectivity construct of the slice may be mapped to only one NRP, as
per I-D.ietf-teas-ietf-network-slices.
Alternatively, an OTN slice may be mapped to a NRP as an overlay
abstract OTN TE topology on top of the underlay topology.  The
corresponding link resources allocated to the slice is encapsulated
in and tracked by the abstract topology, and a given link or port in
the NRP topology represents resources that are reserved in the
underlay topology.  Multiple OTN slices may be mapped to the same
NRP, and a single connectivity construct of the slice may be mapped
to only one NRP, as per I-D.ietf-teas-ietf-network-slices.  The
resources of an NRP topology are reserved and shared by all the OTN
slices mapped to this NRP, and the NRP topology may be pushed
directly to the subtended MDSC or PNC, thus eliminating the need for
link coloring if using the underlay topology.
The performance objective for Optical Data Unit (ODU) containers
as defined in ITU-T-G.8201-Amd.1.
Bandwidth specification in the type and number of ODU containers.
Draft: draft-ietf-ccamp-yang-otn-slicing

Commentary: Co - Authored - By : aguoietf
Common attributes, which include a set of common attributes like
slice identifier, name, description and names of customers who use
the slice.
Endpoints, which represent conceptual points of connection from a
customer device to the TNS.  An endpoint is mapped to specific
physical or virtual resources of the customer and provider, and
such mapping is pre-negotiated and known to both the customer and
provider prior to the slice configuration.  The mechanism for
endpoint negotiation is outside the scope of this draft.
Network topology, which represent set of shared, reserved
resources organized as a virtual topology between all of the
endpoints.  A customer could use such network topology to define
detailed connecvitiy path traversing the topology, and allow
sharing of resources between its multiple endpoint pairs.
Connectivity matrix, which represent the intended virtual
connections between the endpoints within a TNS.  A connctivity
matrix entry could be associated with an explicit path over the
above network topology.
Service-level objectives (SLOs) associated with different objects,
including the TNS, node, link, termination point, and explicit
path, within a TNS.
The base model defines a transport network slice (TNS) with the
following constructs and attributes: - Common attributes, which
include a set of common attributes like slice identifier, name,
description and names of customers who use the slice.  - Endpoints,
which represent conceptual points of connection from a customer
device to the TNS.  An endpoint is mapped to specific physical or
virtual resources of the customer and provider, and such mapping is
pre-negotiated and known to both the customer and provider prior to
the slice configuration.  The mechanism for endpoint negotiation is
outside the scope of this draft.  - Network topology, which represent
set of shared, reserved resources organized as a virtual topology
between all of the endpoints.  A customer could use such network
topology to define detailed connecvitiy path traversing the topology,
and allow sharing of resources between its multiple endpoint pairs.
- Connectivity matrix, which represent the intended virtual
connections between the endpoints within a TNS.  A connctivity matrix
entry could be associated with an explicit path over the above
network topology.  - Service-level objectives (SLOs) associated with
different objects, including the TNS, node, link, termination point,
and explicit path, within a TNS.