Re: [Teas] What is a sub-slice?

[Louis Chan <[e-mail]>]

Hi Adrian,

Thanks for the question. "Sub-slice" is a bit vague and this is why I did not pose a definition here. A few examples

1. Without Flex-Algo
     "sub-slice" becomes "slice" in this case

2. With Flex-Algo in SRv6
     "sub-slice" will take the name implied, as Flex-Algo would mean the slice. But then, there are in fact two cases if we want to go deeper.

        a)      A hierarchical sub-slice, e.g.
                        Flex-Algo slice with sub-slices in hierarchical way, similar to stacked VLAN

        b)      Sub-slice could be a parallel relationship, especially in multi-level situation
                        Just like another VLAN in parallel, with the fallback to Flex-Algo slice upon failure

Usually, I would just take 2a for ease of discussion. Hope this address your question.

Rgds
Louis

-----Original Message-----
From: Adrian Farrel <[e-mail]>
Sent: Monday, July 4, 2022 6:16 PM
To: [e-mail]
Cc: 'TEAS WG' <[e-mail]>
Subject: What is a sub-slice?

[External Email. Be cautious of content]


Hi Louis,

In your new draft you describe a mechanism to support "sub-slicing" and observe that multiple levels of sub-slice might exist.

Do you have a definition of "sub-slice"? I don't see one in your draft.
Is this anything different from a hierarchical composition of slices? As the framework draft notes, slices may themselves be sliced.

Thanks,
Adrian

-----Original Message-----
From: I-D-Announce <[e-mail]> On Behalf Of [e-mail]
Sent: 04 July 2022 03:31
To: [e-mail]
Subject: I-D Action: draft-chan-spring-srv6-sub-slice-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : Sub-slicing for SRv6
        Author          : Louis Chan
  Filename        : draft-chan-spring-srv6-sub-slice-00.txt
  Pages           : 6
  Date            : 2022-07-03

Abstract:
   This document describes how to achieve further slicing or traffic engineering
   interoperability between vendors without the use of SRH.

   Slicing or traffic engineering information is encapsulated as part of the
SRv6 SID.
   Use of IP longest prefix match approach to identify the further slicing via sub-
   slice identifier.

   The traffic engineering from one end to another end is seen as segment by segment
   approach. This approach could solve the scalability of traffic engineering tunnels
   required in a huge network, which order of N^2 has be considered.


The IETF datatracker status page for this draft is:
https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-chan-spring-srv6-sub-slice/__;!!NEt6yMaO-gk!Ay6qRhv3jWnOhjWtJiLbaqc0IzoMxVMO6d4v8msTfF6wjLaiZ3P006Wwr8lUstthNjYn2RoFxo2hER99$

There is also an htmlized version available at:
https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-chan-spring-srv6-sub-slice-00__;!!NEt6yMaO-gk!Ay6qRhv3jWnOhjWtJiLbaqc0IzoMxVMO6d4v8msTfF6wjLaiZ3P006Wwr8lUstthNjYn2RoFxt6_sDsU$


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


_______________________________________________
I-D-Announce mailing list
[e-mail]
https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/i-d-announce__;!!NEt6yMaO-gk!Ay6qRhv3jWnOhjWtJiLbaqc0IzoMxVMO6d4v8msTfF6wjLaiZ3P006Wwr8lUstthNjYn2RoFxjKV7ZUr$
Internet-Draft directories: https://urldefense.com/v3/__http://www.ietf.org/shadow.html__;!!NEt6yMaO-gk!Ay6qRhv3jWnOhjWtJiLbaqc0IzoMxVMO6d4v8msTfF6wjLaiZ3P006Wwr8lUstthNjYn2RoFxgwr-OPW$
or https://urldefense.com/v3/__ftp://ftp.ietf.org/ietf/1shadow-sites.txt__;!!NEt6yMaO-gk!Ay6qRhv3jWnOhjWtJiLbaqc0IzoMxVMO6d4v8msTfF6wjLaiZ3P006Wwr8lUstthNjYn2RoFxsmjK8yU$


Juniper Business Use Only