[Teas] Re: NRP RE: Re: Late WGLC review of draft-ietf-teas-5g-ns-ip-mpls

Krzysztof Szarkowicz <kszarkowicz@juniper.net> Wed, 29 May 2024 13:45 UTC

Return-Path: <kszarkowicz@juniper.net>
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 C1E98C151065; Wed, 29 May 2024 06:45:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.795
X-Spam-Level:
X-Spam-Status: No, score=-2.795 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=juniper.net header.b="YfwtCQ5i"; dkim=pass (1024-bit key) header.d=juniper.net header.b="EVQQsLYm"
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 WrOyEIB_o03W; Wed, 29 May 2024 06:45:25 -0700 (PDT)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 384E6C14CEFF; Wed, 29 May 2024 06:45:25 -0700 (PDT)
Received: from pps.filterd (m0108159.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 44TCuWB8032228; Wed, 29 May 2024 06:45:21 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h= cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to; s=PPS1017; bh=3mr3E9hanQs55XfTRmXxG8/iQz jL0sFbrFdjAWD46N4=; b=YfwtCQ5id1z7/BnOWimNC6h73P41ArA0zqEkvJ+Ixd B6G+mCstt7I504dlQUKHywLQ19+Y/LRlP84x0gMpcjBJXco4b5jIseY2Gxeio7Lt Zu+HhvVrtbSGdc3t0kgbW4BGwYToSdqUaAKf/qY4Mbhi/EdQOFFn57ZcYv6/KmxO 9vQ21tMYfFPct9Lt+ScVjWXCctTHq+S+jiIN/So3omYJX9zroLm0f7feU7rlYxkY A1X5BjYJQD1kBCw1ognLKfn5IhHT3oiqYzBO+MSIiyo9srqhsVUdibnc8iu315aY ZpCNrNQjmIrBO3Yvup6QmVT1I1YYNvVtJCGp8ZoOULTg==
Received: from bn1pr04cu002.outbound.protection.outlook.com (mail-eastus2azlp17012018.outbound.protection.outlook.com [40.93.12.18]) by mx0a-00273201.pphosted.com (PPS) with ESMTPS id 3ybdxrpru1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 29 May 2024 06:45:20 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=AyDGHoPwUVHBw+jPH/qleSpUNBLc7Z2bm2l5pDyF7n4dx6lNtcTnN4rhIRQ834QVsdepzcRLjEZrOpQHbWfQ7Nx/8QaKpfJeNbfM7p//QFneIscwlpGZpcXXqTUCdzY4ApyVOHYvYdJMGwFopiX5CwLqFMLND+wTXYmbT1Tp2eNW5FpM6VuFmEMIKSfpeJKOWhpmaFUugy9nf3zOBj1ByCPfOKyW/v5ZfCRFv0zCJ9ldJGCPgcTQdPAZSFejk9+cs6oNGXDy0/9WtKAkwHgs8KojW0YNuAOHU7XItNCoYdLiDhsmpSFSvPokqyzP3Egvz/me36sUse9Mpu4IfX7kvg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=3mr3E9hanQs55XfTRmXxG8/iQzjL0sFbrFdjAWD46N4=; b=bssrRgsur12g/5byKGl6aSPCRXz7FOSjUT74d6kC/9T3B5G9ZWpZGVMbo9aI5p5rhs9PTo2iFvZH1iboke9ZoEiAnvcdVwzcRseVVLAKmfs4/dY2fMVCvS9hhXUMTs8Wc04KMofpnMeGeO7Oq+H23DVGRwSOyKSiQ4UKh9KLKm3LMJbNs5NdnsUSHIfQSwluGafIlmy++qf4NcNuVTr8hZ8HSlcxs5kiTUyZo4hqYza8cweettBJsXj9csfmJ9F4eR2IWPRpKsa8HYEsOxplunnG0q8vnUVWgPbXBOZqyT6AyKtfZjjrpcbgAbn//62pONeGfAG8GFPUaOxmjqDuCg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=juniper.net; dmarc=pass action=none header.from=juniper.net; dkim=pass header.d=juniper.net; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=3mr3E9hanQs55XfTRmXxG8/iQzjL0sFbrFdjAWD46N4=; b=EVQQsLYmUeWRrc/h3T+V7Raeyo75qSDUdZXDJtqPrbWJJrmdk5H++HLisgS7pF0Ew734K8vfLbzcEcAOHM155EZDmiIgAJTo0cQPNU+WLBdfnmqRGxdVI8kKjuwQY2/tF3Q6LERi8LU1ibvTmdQfD3ISYdusPnjZ5j93CmsVe40=
Received: from IA1PR05MB9076.namprd05.prod.outlook.com (2603:10b6:208:388::11) by PH0PR05MB8903.namprd05.prod.outlook.com (2603:10b6:510:d8::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7633.19; Wed, 29 May 2024 13:45:15 +0000
Received: from IA1PR05MB9076.namprd05.prod.outlook.com ([fe80::6dc4:eb23:6203:e78e]) by IA1PR05MB9076.namprd05.prod.outlook.com ([fe80::6dc4:eb23:6203:e78e%3]) with mapi id 15.20.7611.013; Wed, 29 May 2024 13:45:15 +0000
From: Krzysztof Szarkowicz <kszarkowicz@juniper.net>
To: Adrian Farrel <adrian@olddog.co.uk>
Thread-Topic: [Teas] NRP RE: Re: Late WGLC review of draft-ietf-teas-5g-ns-ip-mpls
Thread-Index: AQHasc5vzP6LA7svvEOfjY8tx9J/vQ==
Date: Wed, 29 May 2024 13:45:15 +0000
Message-ID: <ADBA037E-4C9C-4FE8-BE5C-B603E93BDA21@juniper.net>
References: <0ac301da99b1$d7bc8b90$8735a2b0$@olddog.co.uk> <DU2PR02MB10160A2D5721B11043AB1FDA488E42@DU2PR02MB10160.eurprd02.prod.outlook.com> <75715215-BB21-435F-B046-9B1ACE84A3A4@juniper.net> <172301daa1f2$b69beac0$23d3c040$@olddog.co.uk> <DU2PR02MB10160150AAE536CDBB4BAE73D88E32@DU2PR02MB10160.eurprd02.prod.outlook.com> <CA+YzgTvViqQWUf+UE44L7FMqouLdaMn9-3k-ss2tqkBUf_tTcA@mail.gmail.com> <1edf01daa69a$d11b90b0$7352b210$@olddog.co.uk> <CH0PR02MB829175F67760F0FBAAA91700D6EC2@CH0PR02MB8291.namprd02.prod.outlook.com> <DU2PR02MB10160E11FBAD36E01EAA7D69388ED2@DU2PR02MB10160.eurprd02.prod.outlook.com> <DU2PR02MB10160598E6F883F2F44B8819388ED2@DU2PR02MB10160.eurprd02.prod.outlook.com> <048901dab14d$0c6bf210$2543d630$@olddog.co.uk> <DU2PR02MB10160866061672B4BC4CE267988F22@DU2PR02MB10160.eurprd02.prod.outlook.com> <D4BBE978-0CE0-4E16-A958-128B8FA060E9@juniper.net> <056201dab1cc$24472ce0$6cd586a0$@olddog.co.uk>
In-Reply-To: <056201dab1cc$24472ce0$6cd586a0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3731.700.6.1.1)
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: IA1PR05MB9076:EE_|PH0PR05MB8903:EE_
x-ms-office365-filtering-correlation-id: 9edf55f9-bb90-45f6-6d0d-08dc7fe591ff
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230031|1800799015|376005|366007|38070700009;
x-microsoft-antispam-message-info: r/lzNzgbFN8M4iWboQO6fuKY1QM1OeXJBHQHqvZ6xmu5HBzBB0yc+Gh74D4qH2Wn5kIroyJIq/NJkwVROpUY5ybXBQRK0zL47sKXjKnGJQ/8VmKZ07an04qpWxfT5wTqtvUgj7UTB/QERojujh8cyELAQ4Jlhh6Q3MrGHevuZc+z4rNZqLtej7th7qvnNwsdkEdh3Wx2HLaRoo39Qetln4izVYRl0fzO4cRoXgYDF3ZoUdyqHbBMsQ9rwyBTQ4kAV73qTQCQO2mlYIlsxXVd6WOqfC3cOoDqbV+oUmsDAo+aOwbwxVrtEEj/nvGWYONeAbim6FlsdddQgBirrKzzce43j5TIhsvVHgQms/bQ/WIvlGSpTCQASJmVtgWRdIvlN1xM2oZfTF7g0oEh26TB9mUY+0zm7uOqmPsD8SPyAzM3FsGJjESu/h28lj/7JB0hozIx04rFKpsi8nUcFDSPTPE3/GekClwOOk5VEuBND5sH5OZyQ/OIbKsiUsrPsqEiicGB/a/R6yAHxVsi/A0BoMk5ITv9h99RpxDB14fwd+h0auRK4SHWYFlyTIUyDBrRFQNZ+/Vi/blDhWdIZ09u39r4ZkKh8QmAataPCufQe4vFFg/bY39w3bcEfp7Cl2nUse5Ih9/Jq5InrhTZE1TZ8UqHhNFZ6iFfJVRdApK8x4TsioAbFMMwIA14HK1+j6ASsGNi8Zgo3bLvOpcLo3DI8oC+s98JtboVnaywqvLFV5YUZKTnq2zfk/G5rccu1pUBDum4dr6+DRcItfyctOwnmO0rvo9vhBiZdSekvR4QJC6Gf0llJ9h+o6rLFrpmaLQrs/qPBadrXRxG0Nhm2UHMwl05vyVWX5dNCESEZa8wYvZsiXWMsdzMqJ+VNA5D3a7rxTQYRGZZbe3qTAuxhL+OhklmYKPy75KnnxRsRjONvqCagBbzgF4YNp66grSiAc4h450ts011gXniwQJytRH3kCJyTx1UYP3k22t2zqKP1IZGHK2ZZ5knyEq9BAFg8PWRE9StQYuurOFU19OH6Iw58fiY5KzPEYMmcDJ7fOYxWHDx0ijpV8DXBqprU2lLSxyx98okm45LXACIZpYvoha7BDFXfvRvRhQh6qBMnhNXlalObH29z3jt5/3py9IJmjWzm6FOhK2pJL3tghRSK3rkPRdQCcXDhvfGgNQQnJTJwq78umpkgzi9dNW/tZ8tyVpBvHQ84akj61WGo8UWgSWdUvvqhHrPrJnGIfoG+lYpKx+7D9wyEdb2O2CYtGs4Aw98mM+5YqyiliVznY+ogKOCFg==
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:IA1PR05MB9076.namprd05.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230031)(1800799015)(376005)(366007)(38070700009);DIR:OUT;SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: wknkfIAcdHyQWNvgo7GGxK2mz5LNFBovnHO/kxsRJZiGRquF91tW45KxVMNvgNNli2NSpl3U6u3Gdurw3ytPdUzMkmZSdkxLCrQlzn4wVAHe6zw+azRAOH4HsI9B24XAtcznYBoQZRkXm9Its4+SBb8yocJrjeg0dBThVYPN0ZwxrvJj5kiVcM5bKhADSBpQVWkO9K4HIfXe0g7lK102ZI2/SLQxeGzr1xmjrmpK7/i4oUl1S5utMydqhrVwgA/5i8vV3x/n1Sy7DuBjJT/5wB1Vm9D5rCcRjy6QV/6Y0wdTDE7PlL6BujUdhph2E5iZnux3UYeihKabbnVsSmMzFFjorLZSQ2E30NIa/2BXx+OPHTIhe985eYOIDpX8XznRO6MavrK1RX7SNi5P97hUHT9MxujfOelU0JampvQ5ol9x8B1VU02o9Yls+cSdyz69QOiaFdskOgWdKIhdu0ryXtDCFItw6R0EUXI7RMGHb9c1+e+nH7RXzelb75+y9R6o6Z//hwNOapul6QOVms71YH+aCyGlMGL9DlCwuaM/JJZVYZFo5LKOLzaX4ielpLwLslHjif7i4/v92x0jCEZ9pYUJ2qYRfpZDqVtRmI/j5KOfkuuOqWHGBb2Y87ry8+yVOlPqD1tdk+g6xiIb5Wr/3zIBMuhZwjM1CxahJdcw66OcwLLqsGUrux8VV36RYhpFdR2an8GvxD3hheO5aJlSzeR6Md85JNDtDn5+x6Ve4B1TrMfBVLJFqlEcYg+Yumqt4wdC8vvdvNXuEfD7doZnD9vqjF/R5eYEm2uF1ikB7/vcpvVYLAdTIWcg1ONPIHXuD1Vw/vpbOJI/Dtw0ewIQx9s3yVmlzUY/ARYtWx5fuGscMEd3xGelgX2vTsKJiigbalezbvGeQqBQocVwSzxa7BnF8VjTt1DHppW773iHfSmzLrnUhwBIFHSj8bFkntRR6Ig45heTwrVkYo9Kbl8txnH2SiR36jMRM5cN6zFFk1nGaWDzHqWG9xlALfrgLvcYHg9T1+CRk+UtAoV0QU0osDMn6qKzBcju0uY4Idij1eMgaglnTtG2vJiWLKygDsTujUcVOamOubaBVpR7qHhL0jqPnR9L0ePmzi0sqPn9rhGFpGxte+k4sUATcMXC+MIfT12AShH6eXCUyCEuMZbezvbm6HOYQSHffT9udJNTJH3a/CMnh+bMUyTMEiOrt9o0cGDpiLwj9XQxN/sH08PUpLXx4e/tl63qUiP14BHCCKNKZ3UevURdTT5UfnywCmmFOsXwYbAGHL7aYHPTa02kAVMH/VFSTr1dK7fUwgGjVRruM/w+DX93fqCbTa/X+O4RULyCqk0Loi4RoVLGqbbI/K+a8yqgGRA5YUhVTFQp1op+vIb1LvrUbf98Y1xsVg/K3MRnpsnrfiUrIs+5aXoChM5U4ZvGvG0CtvJ8UKK5X4BY7hr+ij/CfSt2kM9aydD8ig1H/hgmrPPDXfvkERInUwHJkkODIkthT3YlcWJrKoK7i/KUU4fTox1eL8CNG8/vs6iwaZMk6IN2CrgpydlWQyylyQtTuWXaMZA2Z4AozRMWUtzknl1GybsRDY8tUS90SwsmZfk/r+9rU+xOguH0Yg==
Content-Type: multipart/alternative; boundary="_000_ADBA037E4C9C4FE8BE5CB603E93BDA21junipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: IA1PR05MB9076.namprd05.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 9edf55f9-bb90-45f6-6d0d-08dc7fe591ff
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 May 2024 13:45:15.2962 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 1o3GtcBw5mx8xnaTbFRc44o1uqLPHRADxpFzpSeqS4qIC6heq5AK7HricgNd8BUvdycz53iEkRIsBGcd7hnWTw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PH0PR05MB8903
X-Proofpoint-GUID: OszcytbEigBUvTeT-uQgsDoV9xgyCKck
X-Proofpoint-ORIG-GUID: OszcytbEigBUvTeT-uQgsDoV9xgyCKck
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1039,Hydra:6.0.650,FMLib:17.12.28.16 definitions=2024-05-29_10,2024-05-28_01,2024-05-17_01
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 bulkscore=0 phishscore=0 clxscore=1015 lowpriorityscore=0 mlxlogscore=999 suspectscore=0 spamscore=0 mlxscore=0 adultscore=0 impostorscore=0 priorityscore=1501 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2405170001 definitions=main-2405290094
Message-ID-Hash: 777YKWES66OM5CEOYXKX6ZG777CG6BNH
X-Message-ID-Hash: 777YKWES66OM5CEOYXKX6ZG777CG6BNH
X-MailFrom: kszarkowicz@juniper.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-teas.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "BRUNGARD, DEBORAH A" <db3546@att.com>, "EXT-vishnupavan@gmail.com" <vishnupavan@gmail.com>, TEAS WG <teas@ietf.org>, TEAS WG Chairs <teas-chairs@ietf.org>, "draft-ietf-teas-5g-ns-ip-mpls@ietf.org" <draft-ietf-teas-5g-ns-ip-mpls@ietf.org>, "Mr. Mohamed Boucadair" <mohamed.boucadair@orange.com>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Teas] Re: NRP RE: Re: Late WGLC review of draft-ietf-teas-5g-ns-ip-mpls
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/VQvsUiPJ8YSOzDervuoHeNDQVpA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Owner: <mailto:teas-owner@ietf.org>
List-Post: <mailto:teas@ietf.org>
List-Subscribe: <mailto:teas-join@ietf.org>
List-Unsubscribe: <mailto:teas-leave@ietf.org>

Adrian,

I am not describing network slices.  RFC 9543 definition of network slice:


IETF Network Slice:
The realization of the service in the provider's network achieved by partitioning network resources and by applying certain tools and techniques within the network (see Sections 4.1<https://datatracker.ietf.org/doc/html/rfc9543#defns> and 7<https://datatracker.ietf.org/doc/html/rfc9543#realize>)


Using different metric types for path calculation doesn’t partition network resources.

Cheers,
Krzysztof

On May 29, 2024, at 15:28, Adrian Farrel <adrian@olddog.co.uk> wrote:

I agree, Krzysztof,
You are describing network slices.
Adrian

From: Krzysztof Szarkowicz <kszarkowicz@juniper.net>
Sent: 29 May 2024 10:54
To: Adrian Farrel <adrian@olddog.co.uk>
Cc: BRUNGARD, DEBORAH A <db3546@att.com>; EXT-vishnupavan@gmail.com <vishnupavan@gmail.com>; TEAS WG <teas@ietf.org>; TEAS WG Chairs <teas-chairs@ietf.org>; draft-ietf-teas-5g-ns-ip-mpls@ietf.org; Mr. Mohamed Boucadair <mohamed.boucadair@orange.com>
Subject: Re: NRP RE: [Teas] Re: Late WGLC review of draft-ietf-teas-5g-ns-ip-mpls

Hi Adrian,

Taking the definition of NRP from RFC 9543, different sets of tunnels (established using some of available technologies, like RSVP, Flex-Algo, SR-TE), using different metric for path optimization (e.g. one set optimized based on link delay metric, another set optimized based on IGP metric derived from link bandwidth) do not create different NRPs. Therefore, they are different transport planes within the default NRP.

Cheers,
Krzysztof

On May 29, 2024, at 09:34, mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> wrote:


[External Email. Be cautious of content]


Hi Adrian,

Thank your for the follow-up and for your effort on track pending issues. Much appreciated.

I see two main open discussion points to which I will reply in separate threads to ease your review.

Let’s start with the last point in your list below: link transport planes to 9543 terms.

==Adrian===
But the document is pretty adamant that “The realization model described in this document uses a single Network Resource Partition (NRP) (Section 7.1 of [RFC9543]).  The applicability to multiple NRPs is out of scope.” So why talk about multiple transport planes?
============

RFC9543 says the following:

   An NRP is a subset of the buffer/queuing/scheduling resources and
   associated policies on each of a connected set of links in the
   underlay network (for example, as achieved in
   [RESOURCE-AWARE-SEGMENTS]).  The connected set of links could be the
   entire set of links with all of their buffer/queuing/scheduling
   resources and behaviors in the underlay network, and in this case,
  there would be just one NRP supported in the underlay network.

We are not aware of any existing implementation that allow to provide a “subset of the buffer/queuing/etc.”. Support of multiple NRPs is thus not considered in the document: because that’s not something we can fairly claim that we support with existing technologies. Hence, the single NRP mention.

Assuming a single NRP (called, based NRP in the doc), and putting QoS matters aside, different forwarding behaviors are still needed within that single NRP. Multiple transport planes is used to refer to that.

Now back to the text, I suggest to make the following changes:

(1)

OLD: A network operator can define multiple transport planes.
NEW: A network operator can define multiple transport planes within a single NRP.

(2)

NEW:
Also, transport planes may be realized using separate NRPs. However, such an approach is left out of the scope given the current state of the technology (2024).

These changes can also be tracked here: Diff: draft-ietf-teas-5g-ns-ip-mpls.txt - draft-ietf-teas-5g-ns-ip-mpls.txt<https://urldefense.com/v3/__https:/author-tools.ietf.org/api/iddiff?url_1=https:**Aboucadair.github.io*5g-slice-realization*draft-ietf-teas-5g-ns-ip-mpls.txt&url_2=https:**Aboucadair.github.io*5g-slice-realization*NRP-or-not-NRP*draft-ietf-teas-5g-ns-ip-mpls.txt__;Ly8vLy8vLy8v!!NEt6yMaO-gk!AvFSa2NUSvWb_RcuojobP59MrIH50WAD-UQf2HwPTMSyGCWwL8RKqC8uPq67QScehr0YL005kYX2jS6NvY5A54oTeIQLbuIb$>.

Does this make sense? Thank you.

Cheers,
Med

De : Adrian Farrel <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>
Envoyé : mercredi 29 mai 2024 00:19
À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>>; 'BRUNGARD, DEBORAH A' <db3546@att.com<mailto:db3546@att.com>>; 'Vishnu Pavan Beeram' <vishnupavan@gmail.com<mailto:vishnupavan@gmail.com>>
Cc : 'Krzysztof Szarkowicz' <kszarkowicz@juniper.net<mailto:kszarkowicz@juniper.net>>; 'TEAS WG' <teas@ietf.org<mailto:teas@ietf.org>>; 'TEAS WG Chairs' <teas-chairs@ietf.org<mailto:teas-chairs@ietf.org>>; draft-ietf-teas-5g-ns-ip-mpls@ietf.org<mailto:draft-ietf-teas-5g-ns-ip-mpls@ietf.org>
Objet : RE: [Teas] Re: Late WGLC review of draft-ietf-teas-5g-ns-ip-mpls


Hi Med,

Sorry for the delay. Thanks for posting the updates.

I looked at the diff between -05 (which I reviewed) and -07 (that you just posted).

A lot of really good changes. Many thanks.

I hope the colour coding works. Please shout if it doesn’t and I’ll do something else.

Cheers,
Adrian

[Deborah] I agree with Adrian – it is not helpful for good SDO relationships to include in an IETF document (even as an appendix) a description of another SDO’s technology without requesting a review. While it may appear to be “process”, in the past, when another, unnamed, SDO made assumptions on an IETF technology, IETF was not happy. It became a very contentious technical argument. Recommend, either send a liaison (can be done in parallel with IESG review/request for publication) or remove (can enhance the current figures/terms if needed). While some have commented they found this Appendix helpful, I find it too detailed. With all the on-going architectural discussion in ORAN and 3GPP on these interfaces and components (and resulting presumptions on implementation), if want to keep, it should be scoped only to what is relevant to IETF.

I don’t know how we’re going to resolve this. Obviously, Deborah and I are unconvinced about including the Appendix, certainly in its current form. The chairs have called “consensus” to include the appendix. I’m a little disappointed with that call as I didn’t see the arguments in favour except “We find it helpful.”

[Deborah] Looking at the updated document on Adrian’s comments, I also find what Adrian commented as still not being clear in 3.3.3. To say in this document, that another TEAS working group document has shortcomings, is not a fair statement.
[Med] That’s not the intent of the text. We only explain why we don’t mention PBR or relying on source port numbers for slice identification purposes. There is nothing against the app I-D.
[Deborah] If don’t want to include the proposals of the other document, suggest simply delete this paragraph. The paragraph above already says this document lists a few (lists few/s/lists a few).
[Med] Let’s try that and avoid spending more cycles on this.

I’m happy with that solution.

The document could really benefit from the addition of a section
called "Scalability Considerations."

draft-ietf-teas-nrp-scalability says...

[snip]
[Med] I hear the comment even if the NRP advice does not directly apply here. We added a new section about scalability implications and added new text to remind that we inherit scalability properties of current technologies. We added pointers for readers interested in such scalability assessment.
[AF] Even your choice to have just one NRP is still an NRP, and thinking about scalability is important especially as the chosen approach does have some scaling limits. So thanks for the section.
[Med] ACK.

Your new section is nice. Thanks.

3.1

  The term "Transport Network" is used for disambiguation with
  5G network (e.g., IP, packet-based forwarding vs RAN and CN).
  Consequently, the disambiguation applies to Transport Network
  Slicing vs. 5G End-to-End Network Slicing (Section 3.2) as well the
  management domains: RAN, CN, and TN domains.

I thought I understood what was meant by TN in this document
until I reached this paragraph. The previous text in 3.1 (and in
the references) seems clear as to what a TN is. This text,
however, confuses me and I can't extract anything useful from it.
After all, haven't you just explained that:

  Appendix B provides an overview of 5G network building blocks:
  the Radio Access Network (RAN), Core Network (CN), and
  Transport Network (TN).  The Transport Network is defined by
 the 3GPP as the "part supporting connectivity within and between
 CN and RAN parts" (Section 1 of [TS-28.530]).

[Med] This is still under discussion among authors.
[Med] With the updated Intro, we do think that this text is not needed anymore. So, deleted it.

Yup. OK.

Figure 5 finally makes it clear that you are trying to
distinguish a "network slice" from a "TN slice".

[Med] Bingo, but it is unfortunate to see that readers may find that mention too late. Updated the intro to call that out early in the doc.
[AF] Excellent, but still dangling is…

In practice, I think you are trying to say that the slices of the different
domains may be combined to form an end-to-end slice in the
IP/MPLS technology. This is certainly supported by 3.4.2 and is
consistent with draft-li-teas-composite- network-slices, but you
need to work out which way you are slicing (sic)
this:

[snip]

[Med] I hope this is now better articulated with the changes.

Yes, the new mini-paragraph just before Figure 6 is good.

In 3.4.2 and with reference to Figure 5, it appears that your
realisation is based on RFC 9543 Figure 1 Type 3. That's great,
could you say so somewhere early in the document? It would help.
[Med] Added a statement that the realization is based on types 3/4.

Good.

By the time we get to Figure 6, you are talking about "slice
segments" and that is really helping because now we can
consider stitching those segments together.

[Med] Moved that figure to the introduction.

Yeah, that is a good call. Makes the reader pay attention to the architecture.

3.4.2

  In other words, the main
  focus for the enforcement of end-to-end SLOs is managed at the
  Network Slice between PE interfaces connected to the AC.

Would that be more clearly stated with reference to the SDP?
[Med] I think this is covered by the note about types 3/4.

OK

3.5

There seems to be a difference between the title of the
section...
     Mapping Schemes Between 5G Network Slices and Transport
    Network Slices
...and the first line of text
  There are multiple options for mapping 5G Network Slices to TN
  slices:
That is, the text talks about a unidirectional mapping (5G to TN)
while the title says "between".
[Med] Updated to “Mapping 5G Network Slices to Transport Network Slices” for consistency.

So far, so good…

But I think I object to the word "mapping".
While, in one
direction, the word is fine and clearly describes how one type of
slice is projected onto another type of slice, the problem is
more complicated because in the other direction (at the receiving
end of the data flow) we need to "un-map".
[Med] Why should we be concerned with that? Isn’t that part of the non-TN job?

This depends on whether you are simply tunnelling (“map” means which 5G slices will be carried by which TN slice) or if you are aggregating (“map” means that a set of 5G slices “become” a TN slice). As you exit the TN slice, you need to go back to processing the individual 5G slices, and that is easy in the tunnelling case. But it is more complicated to demux when the mapping does not preserve the identity of the 5G slice.

[snip]

Section 4 is pretty clear and helpful. Thanks. I think it is
where the real work of the draft begins (23 pages in). I wonder
whether we can do something to get here more quickly.
[AF] Seems like you’re not rising to this :-)
I wonder whether the introduction can steal a few lines from this section to set the document up a bit better.
[Med] Good suggestion. Moved some text around.

Thanks. Good.

In Section 6, have you invented the Filter Topology when you use
the term "transport plane"? I think you have, and it would be
helpful
either:
- to say "when we say transport plane, this is equivalent to the
   term Filter Topology defined in RFC 9542"
- to replace all mentions of "transport plane"

I prefer the second of these.
[Med] I'm not sure filtered topology is exactly identical to. I heard other comments that this is similar to NRP. We prefer to use a term that is close to what is currently used in deployments. For example, this is consistent with RFC9182 and several RFCs out there which include the following:

  'underlay-transport':  Describes the preference for the transport
     technology to carry the traffic of the VPN service.  This
     preference is especially useful in networks with multiple domains
     and Network-to-Network Interface (NNI) types.  The underlay
     transport can be expressed as an abstract transport instance
     (e.g., an identifier of a VPN+ instance, a virtual network
     identifier, or a network slice name) or as an ordered list of the
     actual protocols to be enabled in the network.

     A rich set of protocol identifiers that can be used to refer to an
     underlay transport are defined in [RFC9181].
[AF] Two points here:
1.       If this sounds like NRPs, then you are acknowledging multiple NRPs, which is OK but is counter to your assertion that there is a single NRP in all aspects of this document.
[Med] I wasn’t saying that I agree with that NRP comment.
2.       The quoted text from 9182 sounds exactly like filtered topology to me
[Med] Still this can be done using the same topology. We updated the text with a new text to explain the notion of “transport plane”:

NEW:
A transport plane refers to a specific forwarding behavior between PEs in order to provide packet delivery that is consistent with the corresponding SLOs.

Well, I don’t think we are converging :-(
This is a document about IETF network slices, so it should link back to the terminology in RFC 9543. It doesn’t have to use that terminology, but it should link to it.
So, keep all your text about “transport plane” if you like (noting that ITU-T people may find this a little confusing), but let’s still try to understand where this fits in the architecture and in this document.

You have: “A network operator can define multiple transport planes.”

So, does a transport plane map to:

  *   A TN slice
  *   An NRP
  *   A filtered topology

Re-reading, I see that the transport plane could be a collection of tunnels. That certainly sounds like an NRP. It is partitioning the links that might be selected by a filtered topology, so it isn’t a filtered topology. But it is providing connectivity mechanisms that could be used by multiple TN slices, so it isn’t a TN slice. Hence, NRP.
But the document is pretty adamant that “The realization model described in this document uses a single Network Resource Partition (NRP) (Section 7.1 of [RFC9543]).  The applicability to multiple NRPs is out of scope.” So why talk about multiple transport planes?

[snip]

____________________________________________________________________________________________________________

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.


_______________________________________________
Teas mailing list -- teas@ietf.org
To unsubscribe send an email to teas-leave@ietf.org