Re: [Int-dir] [Teas] [Last-Call] Intdir telechat review of draft-ietf-teas-ietf-network-slices-21
daniele.ietf@gmail.com Sun, 23 July 2023 22:11 UTC
Return-Path: <daniele.ietf@gmail.com>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A4D7C14CE39; Sun, 23 Jul 2023 15:11:32 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5qsnpI8zj0yC; Sun, 23 Jul 2023 15:11:27 -0700 (PDT)
Received: from mail-oi1-x22c.google.com (mail-oi1-x22c.google.com [IPv6:2607:f8b0:4864:20::22c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20473C14CF1A; Sun, 23 Jul 2023 15:11:27 -0700 (PDT)
Received: by mail-oi1-x22c.google.com with SMTP id 5614622812f47-3a4875e65a3so2279756b6e.2; Sun, 23 Jul 2023 15:11:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690150286; x=1690755086; h=thread-index:content-language:content-transfer-encoding :mime-version:message-id:date:subject:in-reply-to:references:cc:to :from:from:to:cc:subject:date:message-id:reply-to; bh=MxYtSqqB/li2hfq6jU0QU0rPw63mBQKPyCl0kuubD8Y=; b=rskp9Jc6Z54KEBn5yXNHXBmqzyIQwKQp+qkTCprqYXT3PWUg7ybLrpIy1/OSpa2cmZ SQGlqYClAyz6rUdWz2RBeWxPHEBHweY0zlgBKcy7Z1vsQWbD92Epu3lQ8xWh8rl8yUO0 y0+NzLl8fdtbWmVQxzpziHgcxIThH/vdkGPeIqZUZOokTvVwS8RRxZ98od4L731jTYKx mYbmnfcf8tomtgiv+Vgml1RzF6mk8OkR/GeXuHbKVPgi+JYsRwm9hAnve4A4AfUxdqr0 kCOdMqv+flGTxfXLPYlPJr2JiL9zf7cFeDSvBp2KkbKEjx3m7qXIs6IktPz//0rie7Q1 Umlg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690150286; x=1690755086; h=thread-index:content-language:content-transfer-encoding :mime-version:message-id:date:subject:in-reply-to:references:cc:to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=MxYtSqqB/li2hfq6jU0QU0rPw63mBQKPyCl0kuubD8Y=; b=D7g993yupEyLaha2um+LXr+1jWNd7R768KDeuCMk5JsjCKnJjkaJ1T3nXEVh9suyfj UwMG75BBSCTPB21l+qOT7mhZGiOZpXPR88JClDsPdh1ENfmLrHmxcK5CT2mxVXq2WLIg AeZZ2j5vWDIZeRIDQpYNueUGNRrmrHj6Us5rhwOxqOeoakoGVIZtBHNherNrQPZf7b8f qUlYY5MVh6GSP3xMFYZEqS5JqmIsIFx/TWEtgnKedgHGca45Gkzc3zrixag8dsCYvyDi BSXuibKEN1caPN1uh2qtwuYRYH/t1+ge2YpeV0A78hy30zJER7P7HWJrRKCYi2n9p12p Nztw==
X-Gm-Message-State: ABy/qLZOSVxRty5L2apCI88Acr+whiyW82nBiwEjKei5dPmuY6NQ5vLt UlX4DkY+Od7/i5DsvgZPEys=
X-Google-Smtp-Source: APBJJlHZL8I4a4akF89yYkv+yv6QrSAR7g0OcIBuBVLFcZ4JlyhMniV7QYg59mQZh6JgboXzF2fuZg==
X-Received: by 2002:aca:1301:0:b0:3a3:b058:6cb2 with SMTP id e1-20020aca1301000000b003a3b0586cb2mr7641462oii.0.1690150286115; Sun, 23 Jul 2023 15:11:26 -0700 (PDT)
Received: from CSCOWPF4382R3 ([2001:67c:1232:144:fcba:8812:9736:2268]) by smtp.gmail.com with ESMTPSA id q12-20020a17090a2dcc00b00267eead2f16sm2624431pjm.36.2023.07.23.15.11.25 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 23 Jul 2023 15:11:25 -0700 (PDT)
From: daniele.ietf@gmail.com
To: adrian@olddog.co.uk, mohamed.boucadair@orange.com, 'Dirk Von Hugo' <dirkvhugo@gmail.com>, int-dir@ietf.org
Cc: draft-ietf-teas-ietf-network-slices.all@ietf.org, last-call@ietf.org, teas@ietf.org
References: <168995885667.9138.8800310642716850839@ietfa.amsl.com> <DU2PR02MB1016079844765959E8F267781883DA@DU2PR02MB10160.eurprd02.prod.outlook.com> <015701d9bd92$913b7c90$b3b275b0$@olddog.co.uk>
In-Reply-To: <015701d9bd92$913b7c90$b3b275b0$@olddog.co.uk>
Date: Sun, 23 Jul 2023 15:11:25 -0700
Message-ID: <000b01d9bdb2$9f876820$de963860$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-us
Thread-Index: AQDlKdRZPNvqHE6aYt2XyisbDNFEKgMlwpbeAxinnW6xfx1iAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/vmCVQcZc27bak5cbFGMOsk9wBTs>
Subject: Re: [Int-dir] [Teas] [Last-Call] Intdir telechat review of draft-ietf-teas-ietf-network-slices-21
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Jul 2023 22:11:32 -0000
+1 as CCAMP co-chair. ITU-T defines the data plane, we build the management and control plane, I see no reason why an optical (and OTN or microwave) slice couldn't be called an IETF network slice. BR, Daniele -----Original Message----- From: Teas <teas-bounces@ietf.org> On Behalf Of Adrian Farrel Sent: Sunday, July 23, 2023 11:22 AM To: mohamed.boucadair@orange.com; 'Dirk Von Hugo' <dirkvhugo@gmail.com>; int-dir@ietf.org Cc: draft-ietf-teas-ietf-network-slices.all@ietf.org; last-call@ietf.org; teas@ietf.org Subject: Re: [Teas] [Last-Call] Intdir telechat review of draft-ietf-teas-ietf-network-slices-21 I'm going to push back a little here. If there is some IETF technology involved in the network (dataplane, management plane, control plane) and that technology continues to play a part in network slice, then this an IETF network slice. Clearly, if you have an optical network without a control plane and managed using TL1, then you may slice it, but it is not an IETF network slice. We have a long history of control and management plane technologies for "transport networks" that you can find mainly in the CCAMP working group (although some work in TEAS now covers the generalisations). I think we don't need any further change for this. Cheers, Adrian -----Original Message----- From: last-call <last-call-bounces@ietf.org> On Behalf Of mohamed.boucadair@orange.com Sent: 23 July 2023 17:08 To: Dirk Von Hugo <dirkvhugo@gmail.com>; int-dir@ietf.org Cc: draft-ietf-teas-ietf-network-slices.all@ietf.org; last-call@ietf.org; teas@ietf.org Subject: Re: [Last-Call] Intdir telechat review of draft-ietf-teas-ietf-network-slices-21 Hi Dirk, > Since on p.3 scope is limited to network technologies described and > standardized by the IETF, I would omit on p.4 mentioning 'optical' and > mayde replace by L3VPN or other IETF network technology. This is a good observation, but I don't think a change is needed for this example :-) The framework intends to cover generally what is called outside the IETF "transport domain" or "transport network". Optical network are part of those. FYI, an instantiation of this framework in OTN can be for example in https://datatracker.ietf.org/doc/draft-ietf-ccamp-yang-otn-slicing/. You may then argue that then call these "IETF *"? I would agree that "IETF network slice" is a little bit misleading but is this a blocking point to digest the concept? FYI, the WG spent too many cycles on that single terminology point. I was among those in favor of avoiding calling this "IETF *" and proposed at the time "connectivity network slice", but the call of the WG was to proceed with the "IETF" in the name. I don't think that we need to reopen that discussion again. I leave this to Adrian, but if this helps we may consider the following: OLD: An IETF Network Slice is a logical partition of a network that uses IETF technology. NEW: An IETF Network Slice is a logical partition of a network that uses mainly IETF technology. Other technologies from other SDOs (e.g., IEEE, ITU) may be combined with IETF technologies for the realization Of a Network Slice. Cheers, Med > -----Message d'origine----- > De : last-call <last-call-bounces@ietf.org> De la part de Dirk Von > Hugo via Datatracker Envoyé : vendredi 21 juillet 2023 19:01 À : > int-dir@ietf.org Cc : > draft-ietf-teas-ietf-network-slices.all@ietf.org; last- call@ietf.org; > teas@ietf.org Objet : [Last-Call] Intdir telechat review of > draft-ietf-teas- > ietf-network-slices-21 > > Reviewer: Dirk Von Hugo > Review result: Ready with Nits > > Hello, > I am an assigned INT directorate reviewer for draft-ietf-teas- > ietf-network-slices. These comments were written primarily for the > benefit of the Internet Area Directors. Document editors and > shepherd(s) should treat these comments just like they would treat > comments from any other IETF contributors and resolve them along with > any other Last Call comments that have been received. For more details > on the INT Directorate, see > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2F > datatracker.ietf.org%2Fgroup%2Fintdir%2Fabout%2F&data=05%7C01%7Cmo > hamed.boucadair%40orange.com%7Cb52ac523b8d545f5840b08db8a0c18d0%7C > 90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638255556796287942%7CUn > known%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik > 1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zi3YA%2FJPQfxnjgpGdUoBG > %2FvCW8XlWC2Jpk6U2uCOigU%3D&reserved=0 > <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2 > Fdatatracker.ietf.org%2Fgroup%2Fintdir%2Fabout%2F&data=05%7C01%7Cm > ohamed.boucadair%40orange.com%7Cb52ac523b8d545f5840b08db8a0c18d0%7 > C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638255556796287942%7CU > nknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6I > k1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zi3YA%2FJPQfxnjgpGdUoB > G%2FvCW8XlWC2Jpk6U2uCOigU%3D&reserved=0> Based on my review, if I was > on the IESG I would ballot this document as NO OBJECTION. > ... > > The following are other (minor) issues I found with this document that > SHOULD be corrected before publication: > > Since on p.3 scope is limited to network technologies described and > standardized by the IETF, I would omit on p.4 mentioning 'optical' and > mayde replace by L3VPN or other IETF network technology. > ____________________________________________________________________________ ________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -- last-call mailing list last-call@ietf.org https://www.ietf.org/mailman/listinfo/last-call _______________________________________________ Teas mailing list Teas@ietf.org https://www.ietf.org/mailman/listinfo/teas
- [Int-dir] Intdir telechat review of draft-ietf-te… Dirk Von Hugo via Datatracker
- Re: [Int-dir] [Last-Call] Intdir telechat review … mohamed.boucadair
- Re: [Int-dir] [Last-Call] Intdir telechat review … Adrian Farrel
- Re: [Int-dir] [Teas] [Last-Call] Intdir telechat … daniele.ietf
- Re: [Int-dir] [Teas] [Last-Call] Intdir telechat … mohamed.boucadair
- Re: [Int-dir] [Last-Call] Intdir telechat review … Adrian Farrel
- Re: [Int-dir] [Last-Call] Intdir telechat review … Dirk Hugo
- Re: [Int-dir] [Last-Call] Intdir telechat review … Eric Vyncke (evyncke)