Re: [Teas] WG Adoption poll - draft-nsdt-teas-ns-framework-05

Gyan Mishra <> Wed, 10 February 2021 03:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0475F3A12B4; Tue, 9 Feb 2021 19:35:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Status: No, score=-2.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, 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 GmEbiXNfxIZ4; Tue, 9 Feb 2021 19:35:24 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::533]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4EB7A3A12B3; Tue, 9 Feb 2021 19:35:24 -0800 (PST)
Received: by with SMTP id o7so349538pgl.1; Tue, 09 Feb 2021 19:35:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9X3o5vRQt16Al0y1u0IYTeeYaZ8iv9G4bqQ85OLQ6kQ=; b=jBgqah1dnR4cjD8sQyr6Xm5UQME7IVGYkf3hBgvahUD5li8gvZGOHs8VhEeNCU18FQ 5oNb7fO535I0GRV8ajpeScEqMcZY/z553J+Pw7l3Y4DPBosPbQMQM2VvVrbPQR94Ck6q wZ37bJK64RgLwKRng26AIL4KrMbieZRMuYm3DXKgxg24HV6tbylvX4K7Svpya1fTlUiM pfu7kMuQTgpEAuXtyTShfUFXYZ3UHsEItuuSOoBeqyb+SCelq0PuRfJrbzYhshXN0eeC hbmUPdfIh0jarjmk98R36AcRaSG4aPHwgQufWpTSzhGkpyf0jS5ZCeB/VbV+ZqmezOO0 R66Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9X3o5vRQt16Al0y1u0IYTeeYaZ8iv9G4bqQ85OLQ6kQ=; b=fGqMTsON4k12gSTQDVEPf+TaCJiYZI65qi4PU0ibT2vqjwFkqeptcCqeM2Ft1Tlovc TKw5rXfNGbe0Pfb9IDIjbngOaNO5vYVXgDr/cAbKC3PGQh0t9l5dOEiYnIvVcUX/CYbw KWzuxX5nZTXZ67rPNQ8/CCRXtOtRoF/kNtlYAvw/9C30oXuOOHk/UZ1/8j6rjQCikkST PFwgPcxRnKskEyBD3Bhm6ex1uoQhuXF7cu/zLBf3na3ChaYDX/Ib6wOC7mI+fhgtmTpz yLKopjwL7MIpG0dqyhDo7Cqx0l7beVt6jX/oJJEqu06AkDhArUnCsPeZdFW5EGU97YPX pbow==
X-Gm-Message-State: AOAM5316G/diR9/7KRkdEGUf5WbKdhJoU30b5+cjJJrcXC7FDMvsBbVv mXwPaHNjPM4Rq7v/fT5XuqFPhGD2VPXKq/o6Wfw=
X-Google-Smtp-Source: ABdhPJyiAlnoy43g0UoVdcH/tBwgkx+/cbGBR8b2q8e/03xarSrj91JT5j2/S0FwJAkHajA7tz3I2iZL6g+8Z9agsME=
X-Received: by 2002:a65:6547:: with SMTP id a7mr1166567pgw.50.1612928123557; Tue, 09 Feb 2021 19:35:23 -0800 (PST)
MIME-Version: 1.0
References: <> <afbc5128-86c6-4e77-8b0c-7f323f2c0061@Spark>
In-Reply-To: <afbc5128-86c6-4e77-8b0c-7f323f2c0061@Spark>
From: Gyan Mishra <>
Date: Tue, 9 Feb 2021 22:35:12 -0500
Message-ID: <>
To: Jeff Tantsura <>
Cc: TEAS WG <>, TEAS WG Chairs <>, Vishnu Pavan Beeram <>
Content-Type: multipart/alternative; boundary="000000000000da5a5405baf317f5"
Archived-At: <>
Subject: Re: [Teas] WG Adoption poll - draft-nsdt-teas-ns-framework-05
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: Wed, 10 Feb 2021 03:35:29 -0000

I do feel as Jeff stated the draft is ready as-is for adoption, however the
issues Luis brought up for operators is an important issue related to inter
operator trust relationships related to slicing.  I don’t think that is a
significant issue as slicing in general is with RAN xHaul to core within
the providers network as once a soft handoff happens with wireless provider
being a internet service provider the slice framework can continue through
the service provider network.  The end to end slice framework is more
complicated and that is what Luis is alluding to which inter provider trust
and ns slice end to end.

In that regards even the basic concept of end to end QOS interoperability
does not exist between internet providers and that has been a inherent
pitfall for multicast over the internet using UDP which requires end to end
QOS.  So those same issues that exist with trust and coordination of QOS
policies that have existed Day 1 QOS  will definitely have that same trust
complexity for end to end network slicing over the internet.

>From an operators perspective what is in scope for network slicing is 3GPP
UI RAN xHaul to core within the operators network and once the packet
leaves the operators network goes from Verizon to Century link the slice
policy terminate at the tier 1 peering point.  I think the inter operator
network slicing is out of scope as that is more like a huge elephant in the
room to tackle and maybe better suited for GROW.

Kind Regards


On Mon, Feb 8, 2021 at 11:00 PM Jeff Tantsura <>

> I support the adoption, Luis brought a number of important points that
> need to be addressed, however I don’t think this should stop the adoption.
> Cheers,
> Jeff
> On Feb 4, 2021, 5:43 AM -0800, Vishnu Pavan Beeram <>om>,
> wrote:
> All,
> This is start of a *two* week poll on making
> draft-nsdt-teas-ns-framework-05 a TEAS working group document. Please
> send email to the list indicating "yes/support" or "no/do not support".
> If indicating no, please state your reservations with the document. If
> yes, please also feel free to provide comments you'd like to see
> addressed once the document is a WG document.
> The poll ends February 18th.
> Thank you,
> Pavan and Lou
> _______________________________________________
> Teas mailing list
> _______________________________________________
> Teas mailing list


*Gyan Mishra*

*Network Solutions A**rchitect *

*M 301 502-134713101 Columbia Pike *Silver Spring, MD