Re: [Teas] I-D Action: draft-ietf-teas-ietf-network-slices-13.txt

Adrian Farrel <> Wed, 27 July 2022 18:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 27668C14F732 for <>; Wed, 27 Jul 2022 11:28:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Status: No, score=-6.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id EkdnUzcA3ige for <>; Wed, 27 Jul 2022 11:28:10 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C07BAC14F718 for <>; Wed, 27 Jul 2022 11:28:07 -0700 (PDT)
Received: from ( []) by (8.14.7/8.14.7) with ESMTP id 26RIS4Xx017966 for <>; Wed, 27 Jul 2022 19:28:04 +0100
Received: from (unknown []) by IMSVA (Postfix) with ESMTP id BDFEF4604B for <>; Wed, 27 Jul 2022 19:28:04 +0100 (BST)
Received: from (unknown []) by IMSVA (Postfix) with ESMTP id B244C4603D for <>; Wed, 27 Jul 2022 19:28:04 +0100 (BST)
Received: from (unknown []) by (Postfix) with ESMTPS for <>; Wed, 27 Jul 2022 19:28:04 +0100 (BST)
Received: from LAPTOPK7AS653V ( []) (authenticated bits=0) by (8.14.7/8.14.7) with ESMTP id 26RIS3ZJ017866 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <>; Wed, 27 Jul 2022 19:28:04 +0100
From: Adrian Farrel <>
References: <>
In-Reply-To: <>
Date: Wed, 27 Jul 2022 19:28:02 +0100
Organization: Old Dog Consulting
Message-ID: <087401d8a1e6$9c4817b0$d4d84710$>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJ6dnfdK3+oqhBf1UAfTMd/tXLv+axO39Cw
Content-Language: en-gb
X-TM-AS-Product-Ver: IMSVA-
X-TM-AS-Result: No--28.264-10.0-31-10
X-imss-scan-details: No--28.264-10.0-31-10
X-TMASE-Result: 10--28.263600-10.000000
X-TMASE-MatchedRID: 1GZI+iG+MtfmicbHRUsaV3FPUrVDm6jt1KDIlODIu+XLj8YnEO9mWHkK 0FnHivpUat9+/v4VESUiRk4vjVyfC7sm7w5CGpRgBe3KRVyu+k3Id1+nCKlIfm47M5sxfdoIzv0 +UmYCZcOHvDxv0DC+1XHJNchwsNYc7jTtcyq422bkNIw8RlACQ/HEr8tzhXpP2hyovC6wuz0uDh oR+qZH10RzfQMv8pzzhQpUnItA8UtXRGLcUZaXR7U+IyHhkXf1T5ysQDj6eFn7fZJfDdCIXFTNq f3EQ8ox95kUtZ2hOM8O58frLU2PJZwIGOFX9Rw3bO8iLwtqcBp9LQinZ4QefL6qvLNjDYTwzz3j ehzenezN6NCcJaSBTwtuKBGekqUpIG4YlbCDECsWefvMt+drgg==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <>
Subject: Re: [Teas] I-D Action: draft-ietf-teas-ietf-network-slices-13.txt
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 27 Jul 2022 18:28:11 -0000

Hi all, 

Having had not comments on the list (that I can find), I went ahead and
implemented the change from "Filter Topology" to "Filtered Topology" and
included a few very brief examples of what might be being done in this case.


-----Original Message-----
From: Teas <> On Behalf Of
Sent: 27 July 2022 19:25
Subject: [Teas] I-D Action: draft-ietf-teas-ietf-network-slices-13.txt

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

        Title           : Framework for IETF Network Slices
        Authors         : Adrian Farrel
                          John Drake
                          Reza Rokui
                          Shunsuke Homma
                          Kiran Makhijani
                          Luis M. Contreras
                          Jeff Tantsura
  Filename        : draft-ietf-teas-ietf-network-slices-13.txt
  Pages           : 47
  Date            : 2022-07-27

   This document describes network slicing in the context of networks
   built from IETF technologies.  It defines the term "IETF Network
   Slice" and establishes the general principles of network slicing in
   the IETF context.

   The document discusses the general framework for requesting and
   operating IETF Network Slices, the characteristics of an IETF Network
   Slice, the necessary system components and interfaces, and how
   abstract requests can be mapped to more specific technologies.  The
   document also discusses related considerations with monitoring and

   This document also provides definitions of related terms to enable
   consistent usage in other IETF documents that describe or use aspects
   of IETF Network Slices.

The IETF datatracker status page for this draft is:

There is also an HTML version available at:

A diff from the previous version is available at:

Internet-Drafts are also available by rsync at

Teas mailing list