Re: [Teas] WG adoption - draft-nsdt-teas-ietf-network-slice-definition

Jeff Tantsura <jefftant.ietf@gmail.com> Tue, 19 January 2021 01:12 UTC

Return-Path: <jefftant.ietf@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 19DA63A0D73; Mon, 18 Jan 2021 17:12:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.097
X-Spam-Level:
X-Spam-Status: No, score=-1.097 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 S20zZRlMCKHo; Mon, 18 Jan 2021 17:12:57 -0800 (PST)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (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 5C1793A0D78; Mon, 18 Jan 2021 17:12:57 -0800 (PST)
Received: by mail-pg1-x530.google.com with SMTP id v19so11975613pgj.12; Mon, 18 Jan 2021 17:12:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=bunZFobNcZzhyLzGqxZHM7yezvzDlNtzE2JO5A661MA=; b=sV7+spkmonKV1U6XIf3Z7cj5kC4kbaKfw1wIAHW2GOq8zsb0jWilxgKYDPnTRm5/PF lHD5ODHs5EjkD9S6XzXpiK0LcDMLlw+Mlmw3pYF9WyXIQjmXgTkjo41aWYJd58PErTGH i2hfq7xrt7Las4W3Q7BBzSrvgvO2FHF0cGh/wwOI6Ui8BEksCDq6fpS2OWKM6K4bhdBS L9OFaQcTI6QyX+whfpNSKIvxD0iKJXGdAmDDFwuu9rL/vAsoi20TgC72dGPJsTRLzSkm 9ZDBBIBRqdtvaWAjml//T8AUeOA+r8nDGtt7NW9sa2+yp/xzdnoMdSIFTXnaDG343rHh mFqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version; bh=bunZFobNcZzhyLzGqxZHM7yezvzDlNtzE2JO5A661MA=; b=TRPsdtWUt5/ho2tT6mKFGbBDARXEPcifF7SnGzpws/J5L8JtGyk02bd/5R/tPD6JkT p0KNC7VlsiTmR2B8aWNoeLTFa0q0B1CYYbsCqFhd4nJ0TiyENaJxkbIaj+sJltaPZqBe hFVaCjY1xFnu/jJmcxKncFila+Z30wjoygqLL7UOfCCsA90NEeQj1dtTLaag6PHnF/bk OM2GdGk7w79n2YlVHAMeAsUtFr/B3ddAysPy7IA85/vcWHpaOliSnyQHI8xlsK3IH5Eb NaNRuZWD5TKbHE2XTxKHH3EQP4uDxLXekUL7gTSIyci8W6ymGuiGrzJgFMi3VY50k8sD uiTg==
X-Gm-Message-State: AOAM532iRWTnsg8Q0cpl9dLXRD2gs7cPV/mH6fhwBUw7Be7zOjODi1Tb EE/83HxIGSbrMz5L3VyffYA=
X-Google-Smtp-Source: ABdhPJwNqezGkZxSH/R6VOTffFbRwh288VQFr4KuuXUwOBgQesZHQyVAIXWGb06SrHSf6LTT2SE36w==
X-Received: by 2002:aa7:8209:0:b029:19f:3002:513 with SMTP id k9-20020aa782090000b029019f30020513mr2021006pfi.49.1611018776839; Mon, 18 Jan 2021 17:12:56 -0800 (PST)
Received: from [192.168.1.3] (c-73-63-232-212.hsd1.ca.comcast.net. [73.63.232.212]) by smtp.gmail.com with ESMTPSA id y26sm11901904pgk.42.2021.01.18.17.12.55 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Jan 2021 17:12:56 -0800 (PST)
Date: Mon, 18 Jan 2021 17:12:47 -0800
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Uma Chunduri <umac.ietf@gmail.com>, Vishnu Pavan Beeram <vishnupavan@gmail.com>, "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: TEAS WG Chairs <teas-chairs@ietf.org>, TEAS WG <teas@ietf.org>
Message-ID: <86fbc3a1-45ae-4fc8-89b4-6b9644ea35e4@Spark>
In-Reply-To: <35371313-c361-e8b0-76f6-ce0a09b2ac23@joelhalpern.com>
References: <CA+YzgTuJWXENUQLHrFeYWga1XumA4cf1Gr7DgqXw74fxvz-FNQ@mail.gmail.com> <CAF18ct4=PeKYHC9qXuhDg3MpHmeu5hx-AdCOZuGU9-WdGuZKVg@mail.gmail.com> <CAF18ct7bg=2c_9Md-c58=J=v+EhjG+J7=L3_gCQGrx2i6xy+9w@mail.gmail.com> <35371313-c361-e8b0-76f6-ce0a09b2ac23@joelhalpern.com>
X-Readdle-Message-ID: 86fbc3a1-45ae-4fc8-89b4-6b9644ea35e4@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="60063214_5551b9f3_10cc4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/GbIPtKo_o47-JMnzbO9mp34REo0>
Subject: Re: [Teas] WG adoption - draft-nsdt-teas-ietf-network-slice-definition
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: Tue, 19 Jan 2021 01:12:59 -0000

We (TEAS community)have spent a number of weeks trying to reach consensus on the naming, IETF came out as the least controversial and most acceptable by far and most.
I’d rather us not reopening this discussion and spending our efforts on other, not less important topics.

Cheers,
Jeff
On Jan 18, 2021, 12:26 PM -0800, Joel M. Halpern <jmh@joelhalpern.com>om>, wrote:
> I have observed multiple conversations where the absence of a qualifier
> on "slice" or "network slice" leaves folk participating with different
> understandings.
>
> I don't care if the modifier is "IETF" as agreed. or if we agree on
> another term. folks objected to using "Transport" as the qualifier, for
> understandable reasons.
>
> Yours,
> Joel
>
> On 1/18/2021 3:15 PM, Uma Chunduri wrote:
> > I meant:
> >
> > > I personally feel we (as IETF) can distinguish this important work and
> > applicability of this work *without* being explicitly prepending 'IETF'.
> >
> > --
> > Uma C.
> >
> > On Mon, Jan 18, 2021 at 11:58 AM Uma Chunduri <umac.ietf@gmail.com
> > <mailto:umac.ietf@gmail.com>> wrote:
> >
> > Dear All,
> >
> > The definitions and scope defined in this draft can be applicable to
> > many networks in a generic fashion, where IETF technologies are
> > used  in various network segments. I see tremendous work done by the
> > Design Team with folks who participated in multi-domain slicing BoFs
> > prior to that  to get to this point.
> >
> > However, though the name "IETF Network slice" certainly
> > distinguishes the slicing work being done in many global
> > organizations (viz., ITU-T GSTR TN5G, ONF SDN, 3GPP 5G, ETSI ISGs
> > NGP & NFV, GSMA, MEF LSO to name a few) , it creates bit complexity
> > when this is being applied and being referred in E2E scenarios
> > specific to a domain. I can give examples a bit later.
> >
> > I also still see a lot of other documents in this group still refer
> > to Transport Network/Transport Network Slice. I presume the name
> > will be changed across all these documents in future.
> > I personally feel we (as IETF) can distinguish this important work
> > and applicability of this work being explicitly prepending 'IETF'. I
> > shall respond to the other thread here with my suggestion.
> >
> > Last but not least, I support this work and help further to make
> > this better.
> >
> > Cheers!
> > --
> > Uma C.
> >
> >
> > On Mon, Jan 4, 2021 at 6:02 AM Vishnu Pavan Beeram
> > <vishnupavan@gmail.com <mailto:vishnupavan@gmail.com>> wrote:
> >
> > All,
> >
> > This is start of a two week poll on making
> > draft-nsdt-teas-ietf-network-slice-definition-02 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 January 18th.
> >
> > Thanks,
> > Pavan and Lou
> > _______________________________________________
> > Teas mailing list
> > Teas@ietf.org <mailto:Teas@ietf.org>
> > https://www.ietf.org/mailman/listinfo/teas
> > <https://www.ietf.org/mailman/listinfo/teas>
> >
> >
> > _______________________________________________
> > 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