IETF Logo Mail Archive

[Teas] What is a sub-slice?

Adrian Farrel <adrian@olddog.co.uk> Mon, 04 July 2022 10:16 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B5EDC159496; Mon, 4 Jul 2022 03:16:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.924
X-Spam-Level:
X-Spam-Status: No, score=-6.924 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H4GjaD94N1Tw; Mon, 4 Jul 2022 03:16:14 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07AE4C1595E6; Mon, 4 Jul 2022 03:15:41 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta6.iomartmail.com (8.14.7/8.14.7) with ESMTP id 264AFeJs025842; Mon, 4 Jul 2022 11:15:40 +0100
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 2E25B46072; Mon, 4 Jul 2022 11:15:40 +0100 (BST)
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 20E2A46071; Mon, 4 Jul 2022 11:15:40 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs2.iomartmail.com (Postfix) with ESMTPS; Mon, 4 Jul 2022 11:15:40 +0100 (BST)
Received: from LAPTOPK7AS653V (93.197.bbplus.pte-ag1.dyn.plus.net [81.174.197.93] (may be forged)) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.7/8.14.7) with ESMTP id 264AFdEV018909 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 4 Jul 2022 11:15:39 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: draft-chan-spring-srv6-sub-slice@ietf.org
Cc: 'TEAS WG' <teas@ietf.org>
Date: Mon, 04 Jul 2022 11:15:39 +0100
Organization: Old Dog Consulting
Message-ID: <038f01d88f8f$03558060$0a008120$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdiPjwGtQvxmOvRwRx6/e/MiaPFLng==
Content-Language: en-gb
X-Originating-IP: 81.174.197.93
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-26994.007
X-TM-AS-Result: No--15.257-10.0-31-10
X-imss-scan-details: No--15.257-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-26994.007
X-TMASE-Result: 10--15.257400-10.000000
X-TMASE-MatchedRID: KIePq15NjrNhVEh8hDAslwrcxrzwsv5ub5NyYlw4+HWpN11bG1ZGkugh U++ssgQWgvRaVUNx1oAxxt66gKYZIPirh+cliRUjBO00Q/2PQs8cQnDpQ6FX0z5dxKsQpy3tPqK BYD+Nk0ds/8SLplYFWTsjgioE9VSLmSuhkyegN5/ece0aRiX9Wgv/9UzFeXITK10GupkmZUuRba ihAmSwdyxx+gjFjCy1pRLQyclUfPJNfs8n85Te8v7E6GNqs6ce/lZqDVyf/BQ54tgWF1SNbnQdJ 7XfU86e4kYXbobxJbLnIzRzWS2P0w==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/qo10piyPMYf1bMDYvKLzGD-jyN4>
Subject: [Teas] What is a sub-slice?
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jul 2022 10:16:18 -0000

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 <i-d-announce-bounces@ietf.org> On Behalf Of
internet-drafts@ietf.org
Sent: 04 July 2022 03:31
To: i-d-announce@ietf.org
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://datatracker.ietf.org/doc/draft-chan-spring-srv6-sub-slice/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-chan-spring-srv6-sub-slice-00


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


_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

v2.23.0 | Report a Bug | By Email