Re: [Teas] Decision point on scope of draft-ietf-teas-ietf-network-slices

Gyan Mishra <hayabusagsm@gmail.com> Mon, 07 March 2022 15:13 UTC

Return-Path: <hayabusagsm@gmail.com>
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 575043A094D for <teas@ietfa.amsl.com>; Mon, 7 Mar 2022 07:13:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id shPfW0IBD-kG for <teas@ietfa.amsl.com>; Mon, 7 Mar 2022 07:13:47 -0800 (PST)
Received: from mail-pg1-x52d.google.com (mail-pg1-x52d.google.com [IPv6:2607:f8b0:4864:20::52d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E50D3A094E for <teas@ietf.org>; Mon, 7 Mar 2022 07:13:47 -0800 (PST)
Received: by mail-pg1-x52d.google.com with SMTP id t187so9531654pgb.1 for <teas@ietf.org>; Mon, 07 Mar 2022 07:13:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rx9cgkx6JaDPZFjeY+tvglQ8pq1PiQrHALIuTlWeQdc=; b=UwtOD3IFA9GNRt72msd5sGOX5y4ESXavoHyCqhvMTkfeQ7qSY7jiarOqb3Ya5yFRr7 ry4sP78OQ8m7BhrC80FYJrNeqcjcH/NbYtGl5PGr22D5MXvOU+Ui79Lzu4XUkBiNSGtx Dpa0Ni5of5DcIH602G/QqDE9iuUb7wJQsEdUhVv8a1j+VtiCPLAC2S6bB2jHirrAEqvf p/PpCusgFupKiKkMjICXNDud6MuIQA1l/zrQkBpsL14DjAQLk1oQ6lliq8EWvK8qtfuC WUloTNnkGi+VNXAK4hbs+HKpwrnbTgvQy9VbHp3U4d58MdR+sl9DfwHBLpKKtNqQ+thH 0CJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rx9cgkx6JaDPZFjeY+tvglQ8pq1PiQrHALIuTlWeQdc=; b=tiINaONE2+8NP2ej5gun1fi7v2FKlpiVTRbpmE1g7AMzig83DhSE+mOoUlvDV1h8EK Ufroot/tP+Dd44bQsBChsQ410Tkiua89uPNqJc1CN+hPVXsrdb4goyW/vzFtdDOm5vKj BFO1Y1NjQDKazZQlkCnZjEB2q+LvEEYybvYv7yWT0gtuC4h6Lecaba170v6Kp+88UpmM kkRg1HTFl0DFVfmwzYD/rPGJW5Tj+GO4XCjIam1lQAgahYs/5usb8kNrbnzOpLiZxb4b mU7Ha3x7tOtQkM29g63aDcHsEtlVuZ5dkp44Y0V88zo/1EkdAS8a9V3FX3k4wILrosPf vd8Q==
X-Gm-Message-State: AOAM533gDvrcm+Km5MoRACC7BSt1ZZKjLJScDxA3Vbt/gQAuMmG2bDny dqMp85u7A4EWh+goaqRGXIC7WNrgoZN/UYh8HwQ=
X-Google-Smtp-Source: ABdhPJzkBfFy6cICW2sOutCuZcs9cLmSOqVFk5rBsFc1iEHdS8+rqkhRuljwa+oG0pqeXSJd1qjGdfPplMWJY76QYB0=
X-Received: by 2002:a05:6a00:a0f:b0:4e1:309:83c0 with SMTP id p15-20020a056a000a0f00b004e1030983c0mr13117900pfh.68.1646666026310; Mon, 07 Mar 2022 07:13:46 -0800 (PST)
MIME-Version: 1.0
References: <0eb701d83219$761839e0$6248ada0$@olddog.co.uk> <BY3PR05MB8081B7BA134CC7B0F28C06F8C7089@BY3PR05MB8081.namprd05.prod.outlook.com> <914359236.1014617.1646664962120@mail.yahoo.com>
In-Reply-To: <914359236.1014617.1646664962120@mail.yahoo.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Mon, 07 Mar 2022 10:13:35 -0500
Message-ID: <CABNhwV1W7sZ8AtvVgZQmMpqL9WsskXgrMTFy74EnMZx10+2gZw@mail.gmail.com>
To: Igor Bryskin <i_bryskin@yahoo.com>
Cc: John E Drake <jdrake=40juniper.net@dmarc.ietf.org>, TEAS WG <teas@ietf.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary="0000000000008fddd205d9a24fa0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/r3tOSYRlOsUfYelwc3mOixvVTCg>
Subject: Re: [Teas] Decision point on scope of draft-ietf-teas-ietf-network-slices
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Mar 2022 15:13:56 -0000

Hi Igor

Your main point is that as 5G has driven TEAS to develop the framework
draft, however if we hone in network slicing now that would limit
applicability to other technologies beyond 5G to only later make the
framework inclusive.  Why not make it inclusive now?

The major caveat I can see that as we develop the framework draft, we can
look at it from other use case POV perspective for VPNs with SLO today as
well as any other technology such as Optical or any other use case, so the
framework draft accommodates the immediate need for 5G but now we are also
ensuring that framework will cover other use cases.

If we limit to 5G only we would have to revisit the framework draft in the
future to add back anything that is not 5G specific.  It does seem that the
current revision 8 covers VPNs with SLO today so then why not keep it open.


Optical slicing has come up with CCAMP and there maybe other technologies
but is that a bad thing is the question?


Kind Regards

Gyan

On Mon, Mar 7, 2022 at 9:56 AM Igor Bryskin <i_bryskin=
40yahoo.com@dmarc.ietf.org> wrote:

> Hi Lou,
>
> This is exactly what I am suggesting. Let's (with open mind) focus first
> on 5G needs and after that let's see what, if anything, is missing for
> other potential clients like on-line gaming, IPTV, VPNs with SLOs, etc.
> After all, if not for 5G, we would probably not be having this
> conversation at all. As far as I know, we have not defined yet anything
> that 5G won't need, so why we don't just say that, so that, for example,
> CCAMPers will not be considered  into believing that the NS framework
> endorses the work on OTN slicing.
>
> Cheers,
> Igor
>
>
>
> Sent from Yahoo Mail on Android
> <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature>
>
> On Mon, Mar 7, 2022 at 9:17 AM, John E Drake
> <jdrake=40juniper.net@dmarc.ietf.org> wrote:
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*