Re: [Teas] Network Slicing Design Team

Gyan Mishra <> Fri, 25 October 2019 00:27 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1AE3B12008B; Thu, 24 Oct 2019 17:27:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ioupsezSwbqh; Thu, 24 Oct 2019 17:27:19 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::82a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id F195B120019; Thu, 24 Oct 2019 17:27:18 -0700 (PDT)
Received: by with SMTP id e14so727963qto.1; Thu, 24 Oct 2019 17:27:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=k7RPRDHQBP5ae3UqGg1TzWDaF4rVPkBtZv23eJjHLcA=; b=oygJujbQZLQ16cgznMY8kqgSrYBST+B5GuvhDybZTAogaCPgOdSxQqlPgH8qb6YMii V95DBuH6o5moGf4yuM/K5C448RCpfLkrC8RPcTJz9T4QYvP+KMsglLSyloxlSrcTUoMg JuAlB331M9Fd+rdrXcL91POV20WNCY7UN0AsKJfgCNRqkKTEyzjuaEeBH5eLHXxLQx61 ootzDQ3SUmQZzzyaaDpnk64HqPqaaYW8iYoMbB7Jt5O0xDlu9ToZbwS6WL9sebJCv4vj WNRMaIoRVT6YJpiEOEm9qx13HldHCJv1xAIT8lNXXisK0m+I4z1I62n6NRj17sVf0B8+ ET7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=k7RPRDHQBP5ae3UqGg1TzWDaF4rVPkBtZv23eJjHLcA=; b=Obxv0LQO/X5laDSI3TThU2XqmiU6xSrhRUcQoN3IkHhWdLfSrhRkpdUbUUXrM88FjA GVHkQnXK2Jx9rdhvqJG/Jb8yEXbb8ovkEF+IsHT7KyxhiWiYheevKL6JQJiFHRs8BxLs w0/pHfPm/f4g4P03YfHVp+45M+7lz7SP154vP1wxPvit+FS7qg98RK2Zou2QplINpEde g6KVZC1mO/5OhjAzweDJz5wkDJPHDpQmoNxbsLtvSlHH6lbqrtVYOt6trCSRGUspg7H/ ozErnZF9vuxAFhbewj4rHCUeiB7S+fPFiXPhIHM6gRt3FVHQDJ21ZoaOzLD1ExZAjEVr HJrA==
X-Gm-Message-State: APjAAAXnYbbfoahpBN8sjYwV4hxAhHAmsZ4f53XRre3GXBi+RiiOKz6f /1kd/+CEoxhxqxd/9iJvN2eyRDNH
X-Google-Smtp-Source: APXvYqxLYdtLE9I9zNw4eK28kByaM6K5yNCmeBHgV387Myy2cxtfvVadNhqGojLkxPnNIBLN2l5xng==
X-Received: by 2002:ac8:3ac6:: with SMTP id x64mr476561qte.51.1571963237418; Thu, 24 Oct 2019 17:27:17 -0700 (PDT)
Received: from ?IPv6:2600:1003:b019:67eb:e145:eab7:9c:b33a? ([2600:1003:b019:67eb:e145:eab7:9c:b33a]) by with ESMTPSA id t199sm277111qke.36.2019. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Oct 2019 17:27:15 -0700 (PDT)
From: Gyan Mishra <>
X-Google-Original-From: Gyan Mishra <>
Content-Type: multipart/alternative; boundary=Apple-Mail-D4DB785E-16BF-496D-9425-793039AD9FFB
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (16G102)
In-Reply-To: <>
Date: Thu, 24 Oct 2019 20:27:14 -0400
Cc: TEAS WG <>, TEAS WG Chairs <>
Content-Transfer-Encoding: 7bit
Message-Id: <>
References: <>
To: Vishnu Pavan Beeram <>
Archived-At: <>
Subject: Re: [Teas] Network Slicing Design Team
X-Mailman-Version: 2.1.29
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: Fri, 25 Oct 2019 00:27:23 -0000

TEAS Chairs 

I am a member of the TEAS WG and I am interested in joining the Network Slicing Design Team.  I have many years of experience as a network architect with Verizon and many designs involving all aspects of TE.


Gyan S. Mishra
IT Network Engineering & Technology 
Verizon Communications Inc. (VZ)
13101 Columbia Pike FDC1 3rd Floor
Silver Spring, MD 20904
United States
Phone: 301 502-1347

Sent from my iPhone

> On Sep 18, 2019, at 12:40 PM, Vishnu Pavan Beeram <>; wrote:
> WG,
>     This message announces the formation of the TEAS Network Slicing Design Team.  The objectives and deliverables for the design team have been updated based on public and private feedback and is enclosed. There are changes from what was previously announced in (, notably calling out scope as being focused on TE technology as the basis for the DT’s work.
> We thank all who expressed interest and willingness to join the design team.  As we’re sure all will understand, it was not possible to include all who volunteered in the team.  The aim of the DT remains to produce documents that will follow the normal working process, so all will be able to participate in and contribute to this work once we have a WG document as it progresses through normal WG processing.  We do note that the objective of the DT is to produce an initial draft and there is no requirement for document authorship to be limited to or include all DT members, and as usual, we expect a WG document to reflect actual contribution to the work.
> Thank you,
> WG Chairs: Pavan, Lou
> DT Lead: Jari Arkko
> TEAS Network Slicing Design Team (Draft)
> The topic of “Slicing” has received significant industry attention due to its  role in 5G networks.  General background on slicing can be found in [1], but it is a broad topic that covers many different aspects from business roles to services and networks.
> Within the IETF the discussion has largely focused on the narrower topics of “Network Slicing” and “Service Chaining”. [2] provides a sample list of related individual contributions. Much of the IETF discussion has focused on how the combination of VPN and TE technologies can be used to deliver Network Slices. The TEAS Network Slicing Design Team (NSDT) is being formed to develop a framework for providing Network Slicing using IETF TE technologies. The expectation is for IETF technologies such as IP, MPLS and GMPLS, to  be used to create specific, isolated, and managed network instances. The use of such technology in networks and other SDOs is up to others; this work does not imply that the IETF specifies how slicing in any particular setting should be done.
> The primary goal of the design team is to determine how existing technologies can be used, but it is possible that some extensions to those technologies are needed. If such extensions relate to technology from another working group, any eventual work belongs to that group. The reuse of definitions and technologies developed by other SDOs is also in scope, although extensions to such will be done in the appropriate SDO. An important early deliverable to the working group from the design team will be a proposed refinement of what is in-scope and what is out-of-scope for the WG on this topic. 
> The design team will have the flexibility to decide on how best to develop, document and present its work. The design team will provide regular updates and reports to the TEAS working group.  It will present an update on their status and plans at IETF 106 (Singapore) - which will hopefully include an initial discussion on scope.  For  IETF 107 (Vancouver) the goal for the design team is an initial design team framework, and possibly draft, in time for discussion at the meeting.  A stable draft is targeted for discussion at IETF 108. Note authorship of design team draft(s) will be based on contribution to the work, not membership in the design team. Once the draft is accepted as a working group document, it will progress per TEAS working group normal process.  
> The design team mailing list has been set up with the membership of this list limited to the design team and the chairs, but its archive is open and any may send to this list.  Design team meetings will be announced on the list and open to all.  The specific workings, including meeting schedules, of the design team are the discretion of the team.
> The mailing list for the design team is:
> The archive can be found at:
> The members of the design team are:
>     Aijun Wang <>;
>     Belo, Sergio <>;
>     Dong Jie (Jimmy)  <>;
>     Eric Gray <>;
>     Geng Xuesong <>;
>     Jari Arkko <>;                 [Lead]
>     Jeff Tantsura <>;
>     John E Drake <>;
>     Luis M. Contreras <>;
>     Rakesh Gandhi  <>;
>     Ran Chen <>;
>     Ricard Vilalta <>;
>     Rokui, Reza <>;
>     Ron Bonica <>;
>     Tomonobu Niwa <>; 
>     Xufeng Liu <>;
> [1] Background documents defining slicing in general: and
> [2] IETF drafts related to the general topic of network slicing:
> draft-ali-spring-network-slicing-building-blocks
> draft-arkko-arch-virtualization
> draft-bryant-rtgwg-enhanced-vpn
> draft-defoy-netslices-3gpp-network-slicing
> draft-dong-lsr-sr-enhanced-vpn
> draft-dong-network-slicing-problem-statement
> draft-dong-rtgwg-enhanced-vpn-protocol
> draft-dong-spring-sr-for-enhanced-vpn
> draft-dong-teas-enhanced-vpn
> draft-drake-bess-enhanced-vpn
> draft-eastlake-bess-enhance-evpn-all-active
> draft-flinck-slicing-management
> draft-galis-netslices-revised-problem-statement
> draft-ietf-teas-enhanced-vpn
> draft-king-teas-applicability-actn-slicing
> draft-lee-rtgwg-actn-applicability-enhanced-vpn
> draft-netslices-usecases
> draft-peng-lsr-network-slicing
> draft-rokui-5g-transport-slice
> draft-qiang-coms-netslicing-information-model
> draft-xuan-dmm-multicast-mobility-slicing
> draft-zch-lsr-isis-network-slicing
> draft-zhuang-bess-enhanced-vpn-auto-discovery
> _______________________________________________
> Teas mailing list