Re: [Teas] I-D Action: draft-bestbar-teas-ns-packet-09.txt

Hi Tarek, all,

Thanks for update. I have read the new revision and here are my comments:

"Section 4 Network Resource Partition Modes":

-          Suggest to add definition of IP/MPLS based NRP. Otherwise, it's not clear why the three modes are defined.

-          Suggest to add descriptions of which technologies can guarantee the SLO/SLE of the types of connection constructs, including P2P, P2MP, and A2A and the various combinations. NS framework draft says NRP support mapping connection constructs from slice services to ensure SLO/SLE.

-          Will this section provide all candidate NRP realization technologies? I see the reference to "SR Policy with or without Flexible Algorithm" in chapter 7 and not sure if Flexible Algorithm is also a Control Plane Network Resource Partition?

Terms alignment:
-        "NRP" or "NRP that supports a Slice-Flow Aggregate": In the draft, "NRP that supports a Slice-Flow Aggregate" are often used. Can it simply say NRP? Or can you clarify which technologies belong to NRP that does not support slice flow aggregation?
-        NRP filter topology: As described in the NS framework draft, filter topology is just one optional approach to define the NRP topology. The generic term should be NRP topology.
-        Topology Filter and filter topology are mixed up. Topology filter is just one specific realization and not generic, need to remove it or make this clear. And this is also related to the figure 4 in the NS framework draft. My understanding is the "topology filter" in the Figure 1 and the title of section 3.2 should be removed, as there is no description about topology filter in the text of section 3.2.

Thanks,
Bo

From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Tarek Saad
Sent: Friday, April 22, 2022 9:27 PM
To: teas@ietf.org
Cc: teas-chairs@ietf.org; draft-bestbar-teas-ns-packet@ietf.org
Subject: Re: [Teas] I-D Action: draft-bestbar-teas-ns-packet-09.txt

Dear WG and Chairs,

We have made changes to I-D.draft-bestbar-teas-ns-packet to address comments that were received during the working group adoption poll for the revision -08 of this draft.

The changes include:
*         Removing references to work-in-progress drafts
*         Moving status of the draft to informational
*         Adding Section 9 to record non-blocking issues raised during the WG adoption poll
*         Some editorial nits, including fixing RFC2119 language.

We welcome further review and feedback.

Regards,
Tarek (for co-authors)

From: Teas <teas-bounces@ietf.org<mailto:teas-bounces@ietf.org>> on behalf of internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Date: Thursday, April 21, 2022 at 5:56 PM
To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org> <i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>>
Cc: teas@ietf.org<mailto:teas@ietf.org> <teas@ietf.org<mailto:teas@ietf.org>>
Subject: [Teas] I-D Action: draft-bestbar-teas-ns-packet-09.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Traffic Engineering Architecture and Signaling WG of the IETF.

        Title           : Realizing Network Slices in IP/MPLS Networks
        Authors         : Tarek Saad
                          Vishnu Pavan Beeram
                          Jie Dong
                          Bin Wen
                          Daniele Ceccarelli
                          Joel Halpern
                          Shaofu Peng
                          Ran Chen
                          Xufeng Liu
                          Luis M. Contreras
                          Reza Rokui
                          Luay Jalil
        Filename        : draft-bestbar-teas-ns-packet-09.txt
        Pages           : 31
        Date            : 2022-04-21

Abstract:
   Realizing network slices may require the Service Provider to have the
   ability to partition a physical network into multiple logical
   networks of varying sizes, structures, and functions so that each
   slice can be dedicated to specific services or customers.  Multiple
   network slices can be realized on the same network while ensuring
   slice elasticity in terms of network resource allocation.  This
   document describes a scalable solution to realize network slicing in
   IP/MPLS networks by supporting multiple services on top of a single
   physical network by relying on compliant domains and nodes to provide
   forwarding treatment (scheduling, drop policy, resource usage) on to
   packets that carry identifiers that indicate the slicing service that
   is to be applied to the packets.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-bestbar-teas-ns-packet/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-bestbar-teas-ns-packet-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-bestbar-teas-ns-packet-09

Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts

_______________________________________________
Teas mailing list
Teas@ietf.org<mailto:Teas@ietf.org>
https://www.ietf.org/mailman/listinfo/teas