Re: [Teas] Slice as a Service : Response of IETF Network slice coauthors to TEAS mailing list

Gyan Mishra <hayabusagsm@gmail.com> Fri, 05 March 2021 23:06 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 8DD913A119E for <teas@ietfa.amsl.com>; Fri, 5 Mar 2021 15:06:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
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, RCVD_IN_DNSWL_NONE=-0.0001, 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: 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 XE7MS-e94pEE for <teas@ietfa.amsl.com>; Fri, 5 Mar 2021 15:06:37 -0800 (PST)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (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 BCB103A119B for <teas@ietf.org>; Fri, 5 Mar 2021 15:06:37 -0800 (PST)
Received: by mail-pf1-x434.google.com with SMTP id q204so3097487pfq.10 for <teas@ietf.org>; Fri, 05 Mar 2021 15:06:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Yht6v0tJK9MfLeoMPUGbZP7ZwUiUSM+eX+TeRzeOTXg=; b=LSl7VK9o0Y8pxeqMz0+8GAlPeY/7rlFxjYjLIsnQzjUCJGhQvk2p3A9AFUhXG/mvvl 8AJ6+T5eNxJZd2+rmMbsyDSMWwMXqY/TxerN+MEnmtmMv5ePFLpXgjzFdMiTDo3uoi7V umT9l/3zKZuQJVk7FAagcJr1oat5d0paPYrRXCzjO+6x1IaCJ8aq40OTp+ygeHAD4C22 cI2g0A3P7mHXlHa05m87i84X5pYHAWbFKKg7Z9TD0S3s6QYjPqPEQI+wUxU0hGGYgFFr maSXlBf06tkZsDD3IJD5tAwsI1Vp4XEt8erV3uu8538dbaJfofJ97Vp3BSotD3ODzr+/ oAcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Yht6v0tJK9MfLeoMPUGbZP7ZwUiUSM+eX+TeRzeOTXg=; b=WHtbf8LuAHlr9JcOYsmO/Kxsf9Ho5UXOof2ap8WsrhckefW/r4pTyzlW8auscxSKub q7NrB3p5w0A6cLIGBoKJhuMDWQlK/Wg2hdAbb8C3b5dLHDI8RxN+X4y1USeIYVr9jvq7 TW1HpXvl90M3wTaq2FiYzsVB3/SLwErRnAqh+F5M+z+a2x+6LlueaLXJCk4xuDJQ3wTL RY7Rdzj5GmwXRqjGx4ZjGxS3IqCALDmBWl2QadWZ677ooHW9019VVtAYVM4c9JgHSBWw B+QVmWic4TYCP7z8YkYW1nczdJix4VsRONWCBWQYEzYYtJaMQv1cY4Bf3799WpOThcUC 0Qgg==
X-Gm-Message-State: AOAM533Iv++XSYrNWmpeHUNUs5xaLVfY3VL0gqX3zH3ykTz1XUJ8ladw j3kY8HN2XBtHnUCtOsS3xoq+QsQ+Tserul83IZ4=
X-Google-Smtp-Source: ABdhPJxlom2z3zeTSQ8PEl0Z16oLGpOjhDll+TN8nPIKZylpe+6DRxAQ4Pawbkc5DOwcsZaGVK2WHXbSTvy1U5sdVcc=
X-Received: by 2002:a63:1524:: with SMTP id v36mr10632463pgl.383.1614985596628; Fri, 05 Mar 2021 15:06:36 -0800 (PST)
MIME-Version: 1.0
References: <00b201d71122$dd464850$97d2d8f0$@olddog.co.uk> <MN2PR05MB66236D56C1A9AF5F7570FC02C7979@MN2PR05MB6623.namprd05.prod.outlook.com>
In-Reply-To: <MN2PR05MB66236D56C1A9AF5F7570FC02C7979@MN2PR05MB6623.namprd05.prod.outlook.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Fri, 5 Mar 2021 16:11:21 -0500
Message-ID: <CABNhwV1_jbnwXnbrEgnZu2EsNee_=MSnbXskbdZRjdsApnZ9=A@mail.gmail.com>
To: John E Drake <jdrake=40juniper.net@dmarc.ietf.org>
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, TEAS WG <teas@ietf.org>, Shunsuke Homma <s.homma0718@gmail.com>, Jeff Tantsura <jefftant.ietf@gmail.com>, Kiran Makhijani <kiranm@futurewei.com>, "Luis M. Contreras" <contreras.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000cdf0a905bcd22267"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/NmSuE5ZS0oZqCLNzofI2sB2w96I>
Subject: Re: [Teas] Slice as a Service : Response of IETF Network slice coauthors to TEAS mailing list
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: Fri, 05 Mar 2021 23:06:40 -0000

+1

Kind Regards

Gyan

On Thu, Mar 4, 2021 at 2:59 PM John E Drake <jdrake=
40juniper.net@dmarc.ietf.org> wrote:

> Exactly.  And the channel for sending data between a network slice service
> endpoint, aka a CE, and a network slice endpoint, aka a PE, is an
> attachment circuit.  Why is this hard?
>
>
>
> Yours Irrespectively,
>
>
>
> John
>
>
>
>
>
> Juniper Business Use Only
>
> *From:* Teas <teas-bounces@ietf.org> *On Behalf Of *Adrian Farrel
> *Sent:* Thursday, March 4, 2021 1:19 PM
> *To:* 'TEAS WG' <teas@ietf.org>
> *Cc:* 'Shunsuke Homma' <s.homma0718@gmail.com>om>; 'Jeff Tantsura' <
> jefftant.ietf@gmail.com>gt;; 'Kiran Makhijani' <kiranm@futurewei.com>om>; 'Luis
> M. Contreras' <contreras.ietf@gmail.com>
> *Subject:* [Teas] Slice as a Service : Response of IETF Network slice
> coauthors to TEAS mailing list
>
>
>
> *[External Email. Be cautious of content]*
>
>
>
> Thanks to the pen-holders for trying to progress this discussion.
>
>
>
> I wonder whether we should separate the discussions into separate threads?
> As we discuss the different points it’ll get messy unless we do that.
>
>
>
> I’ve changed the subject line for the issue I want to call out.
>
>
>
> > *IETF network slice as a Service*
>
> > The co-authors agree with the mailing list suggestion to treat the IETF
> network
>
> > slice as  a service.
>
> > In summary, an IETF Network Slice Service contains multiple endpoints
> (see
>
> > discussion below for endpoint), multiple connections and multiple SLOs.
>
> > This is aligned with the mailing list. In consequence we propose to add
>
> > “Service” to the text  in the draft defining what an IETF network slice
> is.
>
>
>
> I don’t think this is an either/or. I think we have “a slice as perceived
> by the consumer/customer” and “a slice as operated by the operator of the
> underlay network”. This is very similar to how VPNs are discussed.
>
>
>
> So, yes, lets have a description of a “network slice service”. But I think
> we have to start with a general description of a “network slice”. The
> former is how the consumer/customer perceives the slice. The latter is what
> is really going on: the resources and capabilities of the operator’s
> network are being selectively partitioned to provide the service.
>
>
>
> Cheers,
>
> Adrian
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>


-- 

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

*Gyan Mishra*

*Network Solutions A**rchitect *



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