[Detnet] Re: Mohamed Boucadair's No Objection on draft-ietf-detnet-controller-plane-framework-12: (with COMMENT)
mohamed.boucadair@orange.com Fri, 05 September 2025 10:09 UTC
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: detnet@mail2.ietf.org
Delivered-To: detnet@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id AD6AF5DEC769; Fri, 5 Sep 2025 03:09:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.793
X-Spam-Level:
X-Spam-Status: No, score=-2.793 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_NONE=0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K7WgQ4SP1pz3; Fri, 5 Sep 2025 03:09:23 -0700 (PDT)
Received: from smtp-out.orange.com (smtp-out.orange.com [80.12.126.236]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 3FDBA5DEC75A; Fri, 5 Sep 2025 03:09:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; i=@orange.com; q=dns/txt; s=orange002; t=1757066962; x=1788602962; h=to:cc:subject:date:message-id:references:in-reply-to: mime-version:from; bh=0dToeH8etmcHGA8WgzMZmBtEWgbMkadRkaLM817X+wg=; b=XinvLq3odXXNcCD1sRsuYpE/piuAdI/L2hoOxt/WJ9/+lpE26Xxjlpj5 gB+8IaCpSHOenz3iXZgShOFyQQM84mk+VIhCmNnGyVbob7AgxjX14cpKS T26Rvi0CeXqGSH4txVrwN56YJRGzEzRpOW8UyL2E9xCbcEU7mR0a8Wly8 MTuJk5NqnnFQ+uL6tmmmA4uLtCJrUiVytj9bVhPHHYqe9uvFuPyeLjn3F ybiVbdYOVlLSq4D1iY6RzhoDBcYoDT9vWtg+i0vioDEebKSRzl91R6XtE PzMEYwOtv8Pj4Ikog+NKSas7qcrOSxsUnkst3QVWaWIjkK9czGkG/qJeY Q==;
X-CSE-ConnectionGUID: K861ha+NRQmtXsGL+0VB9w==
X-CSE-MsgGUID: Fqw8eClQQ3mI1buT787tMw==
Received: from unknown (HELO opfedv1rlp0c.nor.fr.ftgroup) ([x.x.x.x]) by smtp-out.orange.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Sep 2025 12:09:15 +0200
Received: from unknown (HELO opzinddimail13.si.fr.intraorange) ([x.x.x.x]) by opfedv1rlp0c.nor.fr.ftgroup with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Sep 2025 12:09:14 +0200
Received: from opzinddimail13.si.fr.intraorange (unknown [127.0.0.1]) by DDEI (Postfix) with ESMTP id A23C41626012; Fri, 5 Sep 2025 12:09:13 +0200 (CEST)
Received: from opzinddimail13.si.fr.intraorange (unknown [127.0.0.1]) by DDEI (Postfix) with ESMTP id 9CAFD162572F; Fri, 5 Sep 2025 12:09:13 +0200 (CEST)
Received: from smtp-out365.orange.com (unknown [x.x.x.x]) by opzinddimail13.si.fr.intraorange (Postfix) with ESMTPS; Fri, 5 Sep 2025 12:09:13 +0200 (CEST)
Received: from mail-francesouthazlp17010021.outbound.protection.outlook.com (HELO MRZP264CU002.outbound.protection.outlook.com) ([40.93.69.21]) by smtp-out365.orange.com with ESMTP/TLS/TLS_AES_256_GCM_SHA384; 05 Sep 2025 12:09:13 +0200
Received: from PR0P264MB2885.FRAP264.PROD.OUTLOOK.COM (2603:10a6:102:1d0::19) by MR1P264MB2578.FRAP264.PROD.OUTLOOK.COM (2603:10a6:501:33::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.9094.19; Fri, 5 Sep 2025 10:09:08 +0000
Received: from PR0P264MB2885.FRAP264.PROD.OUTLOOK.COM ([fe80::d43d:e9a7:d7d8:9d33]) by PR0P264MB2885.FRAP264.PROD.OUTLOOK.COM ([fe80::d43d:e9a7:d7d8:9d33%4]) with mapi id 15.20.9094.018; Fri, 5 Sep 2025 10:09:08 +0000
From: mohamed.boucadair@orange.com
X-CSE-ConnectionGUID: ndtRrz1DSQuFMWgibpeziw==
X-CSE-MsgGUID: ZJVfF7IuSoqR6cFvjSGZyA==
X-TM-AS-ERS: 10.218.35.127-127.9.0.1
X-TM-AS-SMTP: 1.0 c210cC1vdXQzNjUub3JhbmdlLmNvbQ== bW9oYW1lZC5ib3VjYWRhaXJAb 3JhbmdlLmNvbQ==
X-DDEI-TLS-USAGE: Used
X-CSE-ConnectionGUID: hJ3a1DJpRretBmWVWbGYEQ==
X-CSE-MsgGUID: M78iXrI6R/GSZj+cnXiYnw==
Authentication-Results: smtp-in365b.orange.com; dkim=none (message not signed) header.i=none
IronPort-Data: A9a23:wzAx76kDpv76EHjk05bjzYDo5gyEIURdPkR7XQ2eYbSJt1+Wr1Gzt xJNXmqHbvjZYDeneNAiboWw90MP7ZfSz9FhTgVlqipnFy4T+ZvOCOrCIxarNUt+DCFioGGLT Sk6QoOdRCzhZiaE/n9BCpC48z8kk/vOH+OmYAL9EngZbRd+Tys8gg5Ulec8g4p56fC0GArlV ena+6UzA3f7nWckWo4ow/jb8k437ayv4GpwUmEWPpingnePzhH5M7pPfcldH1OgKqFIE+izQ fr0zb3R1gvx4xc3B9q5pa3we0sMT6S6FVDmZq1+AvXKbrBq/0Te445jXBYuQR4/Zwahxrid/ O5wWamYEm/FCEFudNM1CHG0GwkmVUFPFSSuzXKX6aR/xGWeG5fgLmkH4EweZeUlFuhL7W5m9 d5DIWkhTAi5ne+q6reEdNZmqfUOFZy+VG8fkikIITDxKMwUecqdH473vYcCmjAtmspJAPDSI dIDbiZiZwjBZBsJPUoLDJU5n6GjgXyXnz9w9ArT9PFxvTmVllUZPLvFaLI5fvSPQsVcm0uU4 GjB4m/wDhgbLvSY0zOD/X/qjejK9c/+cNNMTeDlq6Q76LGV7klMWBwmT3rlm76WsXy8GNlZG 00l/DV7+MDe82TwFYOhAHVUukWstRwWUPJRD6sn41qIjKfPiy6YC3MLZj9MdNJgs9U5LRQmz FaHg5boCCBh9bGYVXSQ6vKfqjWuIy8RKWIYIDcARA0Iptf5qYQ+kRXVTf5iHbK7yNrvFlnYz z2WqiUiwr4ThM8RzI268EzJxTW2qfDhQgMp4AjLdmOo8g0/Y5SqD6Ss41XB4vtaBIKQRF/Hu nUY8/Vy98gLBJCJ0SKXSeMGEaqu+uqFOS/YmQcwR8B5r270vXm+YYpX/TdyYl9zNdoJciPoZ 0mVvh5N4JhUPz2haqofj5+N59oCzYq7HI3JdOjudNdSSJ1OSjCN0xBDXBvFt4zyq3QEnaY6M JadVM+jC3cGFKhqpAZaoc9NgdfHIQhumgvuqYDH8vix7VaJTFCvIYrp3XOLZ+E9qa2eqQPe/ s1YKteKwgdbSLShOnCPqdRKa1cXMXI8GJb67dRNcfKOKRZnH2dnDOLNxbQmeMpumKE9egb0E pOVBxMwJLnX3COvxeC2hpZLNOuHsXFX9iNTAMDUFQz0s0XPmK72hEvlS7M5fKM86MtoxuNuQ v8Odq2oW6sSFWyeo2tBMsCs9eSOkShHYyreb0JJhxBvL/Zdq/DhpIS6ImMDCQFSUHXq75Zn+ dVMKCuCGsVdG18yZCopVB5f5wjq5yRC8A6Dd07JKcNUY0Li7MBhLDbp5sLb0OldQSgvMgCyj l7MaT9B/LGli9ZsrLHh2/rYx6/3SLEWNhQBQAHmAUOeaXOyEpyLndUYCL7gkPG0fD+cxZhOk s0OlK6tbaVawgkX22e+ep4ypZ8DCxLUj+cy5mxZ8L/jNjxH1psIzqG64PRy
IronPort-HdrOrdr: A9a23:kHlqQK/CEWaJwVzuXF5uk+FTdb1zdoMgy1knxilNoENuH/Bwxv rFoB1E73TJYW4qKQkdcdDpAsm9qADnhOVICOgqTP+ftWbdyQ+Vxe1Zg7cKhgeQYhEWldQtnp uIEZIOb+EYZGIS5aqU3OD7KadH/DDtytHKuQ6q9QYJcegcUdAD0+4WMGemO3wzYDMDKYsyFZ Ka6MYCjSGnY24rYsOyAWRAd/TfpvXQ/aiWLCIuNloC0k2jnDmo4Ln1H1yzxREFSQ5Cxr8k7C zsjxH53KO+qPu2oyWsm1M7rq4m1+cJ+OEzRfBkufJlagkETTzYJ7iJbofy8gzdZtvfqmrC3u O85ivIdP4DkU85NlvF3CcFnTOQmgrGokWStmNxjRbY0LDEbSN/BMxbiY1DdBzFr0ImodFnya pOm3mUrpxNEHr77VPADvXzJmRXf3CP0A4fuP9Wi2YaXZoVabdXo4Ba9ERJEI0YFCa/7Iw8Cu FhAMzV+f4TKDqhHjnkl3gqxMbpUmU4Hx+ATERHssuJ0yJOlHQ8y0cD3sQQknoJ6Zp4QZhZ4O bPNLhuidh1P7krRLM4AP1ETdq8C2TLTx6JOGWOIU7/HKVCIH7Jo46f2sRG2AhrQu168HIfou WwbLoDjx9NR6vHM7z+4KF2
X-Talos-CUID: 9a23:irNKZWypz5zB44GBK1TTBgUUOJssK1H/1E3KLlOSDFlXd7e6eHKprfY=
X-Talos-MUID: 9a23:JShGfwb2tsSn3OBTkmC8hQF4FZlSpIuVOkJOmpM2uviCKnkl
X-IronPort-AV: E=Sophos;i="6.18,240,1751234400"; d="scan'208,217";a="96155529"
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=CeLrF8B0pTrKhmg/zdshXclBm3SXJTvY7Yn6f7Hg2H6wTCd7P165UE46HjhM55Tc7Kkxg4BvNZ1cAIxFBd9VAPvHrdIN09BVdyTUr7X4CouSUACxcuCO1zJwpyZVLqmPO85c9PSSF4w+fr6UlTpA2ysQPsPvUk0ZdZd86tnMabOdsrrGKg0QVDf+2AyIdDAAXbyCAuip5rVjl3qcB4XTDdJuE8ErCq5SLw4Weym851xya6BCvoqaMOryUVapW+1+2a34/m68hgvqvIXvkKtoRYci1ARh0NBoZS3hx194qz0ZX8RUG4b/V4YhmwJqvA+GTDXoC7F4PI43VcmlrfN7PA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; 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=YO5tpJyTzStB94d9N3/NM2OrmU0z1HMfthg9UcrrMZw=; b=jXmj6UpSS73JkyFFme67UTCmJXGs9Rt9NDOyjbDFLuDz7mibd/3VTELnGjPJoQ/oGhKiCt+W+z+kGci+7gyv283pWaK5Y00nD7Heob/Pm1nz1SKdZ6X90/ogFCkKhSou8KIH1pk2nwQpaAZz0U99nLBpyyKCHJRuhqVZAx+wqssRCuQhYbB0rA2Kwp6B45EI6C8u6iD1ymT2AmkThI6VeyefG2HHE+qknyMOoZ7OMZbnZvhDsYkyy1Hae/Hr0IeWZ88ftnt2QUYTS8tCKXp1UoI+WQcwWD84DofcS4leZ/7IaKrfyg0XRSp3f4Tu6+YSeAe66OJew4DIWE6pKlkneA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=orange.com; dmarc=pass action=none header.from=orange.com; dkim=pass header.d=orange.com; arc=none
To: CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>
Thread-Topic: Mohamed Boucadair's No Objection on draft-ietf-detnet-controller-plane-framework-12: (with COMMENT)
Thread-Index: AQHcF3i2Y/yMaDs6lE24kr6tVIXLJrSEaR3Q
Date: Fri, 05 Sep 2025 10:09:08 +0000
Message-ID: <PR0P264MB28858C774565BCF75867EDA98803A@PR0P264MB2885.FRAP264.PROD.OUTLOOK.COM>
References: <175394606617.345955.9112895964222856531@dt-datatracker-5bd446d5fd-c47nq> <CALypLp_h6SjJeVwrnOuoTMUjWHkDFG-4xT7hfXVBZrHJkQKsfw@mail.gmail.com>
In-Reply-To: <CALypLp_h6SjJeVwrnOuoTMUjWHkDFG-4xT7hfXVBZrHJkQKsfw@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=09982f53-1639-4ac1-a2a9-cb9f31762638;MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0;MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true;MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged;MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2;MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2025-09-05T10:09:03Z;MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20;MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Tag=10, 0, 1, 1;MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_ContentBits=0;MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_Enabled=true;MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_Method=Standard;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: PR0P264MB2885:EE_|MR1P264MB2578:EE_
x-ms-office365-filtering-correlation-id: 50369b73-604c-41d2-4042-08ddec6440e4
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|376014|366016|1800799024|7053199007|13003099007|8096899003|38070700018;
x-microsoft-antispam-message-info: dP1uv6VS/jBzXdCJahcPHqvLpi5y6F9ub8nz9nI6JPJKLfPROZ6/fmLhMnEZHuoX7Ux6vNjmfL45uOzmei76SmIsX7XNujvHKnjGaeZfzWTM9UNmsuYZU6jWdssNIf9iOCvxc37LZy3cdjbr5YC5mGdt5OETYQNxLRiClPvyHsP0VE46VTYpSK6jyfkbTIr+T400ZOtdKYZGLiGVXEMLj6GtW2KAOiDGTfW9RH/CBhQ7n5WQa/7G93/i/6PtYcDocC3N7Tcpl8ufMJhzKSncftK+MXnUsNi/DIuPN5/wHCIyO5RYba8k7mTdj9gFBef2vmAySuU0FLOszOAHCXrEiYr17t2lEjLppgzkKM/Zg4/eISvs2UOS2+E9GBgf+HoKMov9fFA98uxMqb60TNJ+MxYbUhi+TSuPwz+Qk/KBXwbgasQGVJBpU2mZe0eJwOOXeGWZdVtWtL1TJH+nn07FMPvsybi/uVps7/xfAW9/L9IOyqzSoMnv3fnOfTIumXXbudez2szgUfE5BnbQpaiF0OAF3Za4EOqQeHRWSB6I2jugOXqCiYQXJwxzWP+NYDu9lpMuAMjJIt2SL4VRK+0/oEtNqUJE8UVpsqMWUeyUAvnRjFBh/qE0OUK2/ZpBM757LCqxtdELXRWDz9n2aIeY8amZJxxgrmhzJvvcqxkSA5AKnF0TiXPu64kgNSsL08I5DEEV1cf09CrbI41c99zs0mPDwk9fjLgO5J7GoX/1tmq2LUdauPKUQHdSjcrdj26+shidIv0j0bhARkG83UL34qz+hBhopaHpxr4QcCgYbGLnfRSx65D0DNQLDxf9Zh4JiXvAbKyU8rsXZtcxBeyI8YTf1TBdCP18nrws+oZVFwEerV87mNFLzu8AV9AYWMmPoKNKuvyRZEvkbBMxwybWD68qi3KTmV4vRswLAbXoMfUfeE6vlgGkm4WJxtctA8Rf8XNCqU62KLHl8SL7te4nEx3BaKhtklDhxdzY8Vqc5WSYUprFSMJq5305yqGOAVtZERhfVGas6/gFbmuAIjmBBHNX+IFl+mvm2MVaradnL5I2SLrYy66x8OT/rnQoIDTVy7UcnGEfD5d/txzzl0sCWncYjT4yWyQ1rTbqYDD0b1VqrQwRUN+2OWS2YrfKIVtQngyr6iJP6krY4kIUXxSwlUwuTGQJvNzbGKtJvQQBmtbHHNl+ABXP+9idSA902LT97RuFiTZ1OCj96LTrr+t6dBlsDVI0o6/tGl26hS0f9Sknxs9zobmsBUe4KGqULPQZuzFfiiLEsCY2MRQ5CYvZT70T1prdPvew9bEMDxSJypN9PsFKZcCVQh88OV0+Hleygo8JffjQgWG//tKvwJlBIcajmrP4QF00TOd7E9vBOS0D3eEouxG5Nl261N+PkJU4y5Lkt9YpHUBRZ+gqBYkfEQv759ywxRmEXhF1Zgx3wcp5SUDEoxvLiXOFsCRFBBKdlHI9yJOkX/P+7vZw+9JK3BTg0PhH4yAopJJ0anOEeAc=
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:PR0P264MB2885.FRAP264.PROD.OUTLOOK.COM;PTR:;CAT:NONE;SFS:(13230040)(376014)(366016)(1800799024)(7053199007)(13003099007)(8096899003)(38070700018);DIR:OUT;SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: P+x9D6NgSXPp/F3knhVkx1NFbiLD7wzDle7JpqfLULUvgG4pPqaaQkMCqlVYBvb0M6527i6P0Wa6M9T2SwYuyho5ONIJHiadPUsJrlNILaSdDd7j3X8L4rqAC5JYvUpl1GvAS1YORWgl1itAkLTPQZIOHLpAj27kJGZs3W6HXKAlQs/g2dLY4hdFOnsm4euNcRD/Yu4b05TSrxnsfu/K58zQXEoEDc4aeKEZdnPnWQkmKOO1rgb/EEEgWxjMbyboDiftFA3kXOeuOCNNnlLs28E+gmMqp1X9QFLvunlkMcL+h9TyLEA//MqTU5b5HvtZkr+KlUZCWMvc+CdfQFEV6skKqs3CqC0NAkxe7OxG/CR/yPiafAtE/JswOveN/sgn+shb928NFaiDJ3581O8881hlbzulknisTDM/Cu6LJZoKr9RZvnbyhQsKxYGvurwfoFnZF5ELbBcTABytNDyj8hYB91r3ozA6KweYG9W7QdWGcFcx8PbwI6JzSrPseBTy8YDcXauYhLKrGaF7kfamW0FSy89uUlBPjzWIIPHYYM6v0D021SKcMl19jOeiByxHgIwkFdfVvc5JbLt+8nsEeAoEWHcVJl6MyKNcalXGEkf/5BYok03hH+jrC4GK4/7fvMv+LL5Py523/aMk2jASIwf5nYGXiPyRUzUpcGpSsQa+ihEL2rSnOhVDHzNDiCyWexoQwqq/LzYDfN5jMlvDFX29Lc0/YVZOAEpFYLn2ZsfJtzo+WM4K1X5s4DT8lRLGQrje/Q/AKPnhQyoR2sLhY7ueX8FJNhxxLuS9IH+UxA0xxdQ6c9ymJtEQC00LOcKrSJ5nYc0r6+D5dqm1kbtFyUleqKULc/0OvRrJSQizUx4sEZrfebs5JqlQv8CbNtHbq9NEX1/LJu3osGzj5Gf7TmN0SWIGCFFw8EBJwjxgt8FqjTRMeqUIKsiqYQLisErvRrCVGLuI+yeYzuyTPnhRyFDRi6UD55+AD9vdQ46ya1CCdViUVIoQtnu6qnbEvY9CGWQ6jJLld2HlzwbkM7rMlcMkkDWuo6AR1pZ/2Ex1VF2ksUPQEZs6oDDZnQkmvKCWxeRCXmEDoDGuLcCiTMeWzGg5u8PBqLoNH4ChZgSIGZCjdeoDbCnxCp9MG5xk7PoMgbrqV227Esk7t1zWyBcG0lPBnVOlzmzwb6kudC60l58rxS2ddjXFzM5Q2rEnqKtZQBi3v7HYRkTzfWmvr5rOkSrk2f7OLu1Mhn5NCQX3aeTcnFHe6ZChEW+yZL2GC7kvDLVEeRBpRtefdJIXaJYHL2FZCkZeoJ/N3B5ce8T61lJl2uWaCKrrdCU1tnxPY0PFH3drtMdLpwc4PmmkOpyO3VQ8R91EuLHrMtwssVIcv34tIwpMNI7ADCr82ezH3bw9T8dFwBJG5Vbq42OTLFyMUDf+XU3+oCrp4uTLfFH04ydEOGaP6OR885yDSo+gGJ2Y2nU9OskJ0UDlqrFhzoeZEYBU2jgQy7OIV93zpYuUSVfz1ATGC4vae5Nf1sBirGl/gRJsfdGSNw2hzCN4R2Laczd76/EnPvZPX83p8gG/YpL38uJetow9amsiS94RUaXJfyv3yu18/cxu3YPa64LLvg==
Content-Type: multipart/alternative; boundary="_000_PR0P264MB28858C774565BCF75867EDA98803APR0P264MB2885FRAP_"
MIME-Version: 1.0
X-OriginatorOrg: orange.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: PR0P264MB2885.FRAP264.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 50369b73-604c-41d2-4042-08ddec6440e4
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Sep 2025 10:09:08.5797 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 90c7a20a-f34b-40bf-bc48-b9253b6f5d20
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: vbDxTtcRUbnILIiyVg/cwv1ZvAjk8lqDPauNyF0fmnJjm2mKqnwCbfxXyEWConsoL9GBmBlN6pNamycaCCCjYpF4xieKreUIVY2Z2q5Iqz0=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MR1P264MB2578
X-TM-AS-ERS: 10.218.35.127-127.9.0.1
X-TM-AS-SMTP: 1.0 c210cC1vdXQzNjUub3JhbmdlLmNvbQ== bW9oYW1lZC5ib3VjYWRhaXJAb 3JhbmdlLmNvbQ==
X-TMASE-Version: DDEI-5.1-9.1.1004-29426.007
X-TMASE-Result: 10--35.393900-10.000000
X-TMASE-MatchedRID: MZa17WpznP27REX8b2FriCbixKZRJvnJSHCU59h5KrEnhzAhgvoq550C 6WJNXTpixWMQQTjSQM1kMBdgkVMdXp+nBagEn8npdXq0qk6ABdaTic/61CL6tgVpaMh5bjedToW hlFQp0uQMHwWMhmM6VuCvRZnq77KlNUCIiMoGGlccKFYeDmCMal/ZJ0h1vLl1OhJ9m53n4aADx6 oqiF8ShkJ1AtY308ILaCzUzWqEJkt2tzv2inTHJAx6TQKWelWnlVHM/F6YkvSU1sgHARX+HtvBg CEp+AoihEzI3+mkzicvcgUibwrcmmB7doPBjWYu9ZRkVakSSW0BGmsibWGTbQgqPpbA7sp1P4H+ 2nyK0FP1Rwgk4BYHf+4IlX79RZOvxZ0dQ+CjqRPwcLpwsvX/owvBTB90+he+3SkTY86NiDh8vx8 dQICa6zb10B588b8hq9YyptElK5eRtd38GtQTd4HcC7KYYAdE2Sa33ZGXWdYBmf/gD11vZLdK2T rYyqII8AXjchdqPaD549MJKehHixXI/ECI2yJM0uQOgHtFIKqJJ72DuZB0nHFd5+Cf9M1D+cbDH fpxITXHyPVzMcsGAnvnmVPHosNGNjMuvl0LFArukHLmlxMmTj4hLE6Yiyj0mGrGwE7uWsuwxkba lTMB8/6NVYgJ2lwX7v7xSF4W67Qungnhk7eoNtfnhWZzHtFgEGOqXTRZcB+p/958oU3WcEAAtXN 5ZhBwaO0SrIU+VD/G9hRvuYMY8fDkUADG6q2p1jTI2Usp8OMiLmf+ghTG/9145+uPYzIvrQYkvY RXmky1nvFRriRfrKCZS/Gg93ibjTz4zewAVYXUMc8LI13c20bgTmf4sxQ0mkCGwliFomubKItl6 1J/yRqQeFbBnmmV4E9s12Gvf509l7H+TFQgdfnZI3fdS4AAyPif/XMJwtISHtXtF4SOhYVH0dq7 wY7up8Odl1VwpCSUTGVAhB5EbQ==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
X-TMASE-INERTIA: 0-0;;;;
X-TMASE-XGENCLOUD: ff387608-00d1-4521-98d9-ea423fd2fc13-0-0-200-0
Message-ID-Hash: JTJUFUVH7KUB44TWSITZHAGJ6REZ7OTE
X-Message-ID-Hash: JTJUFUVH7KUB44TWSITZHAGJ6REZ7OTE
X-MailFrom: mohamed.boucadair@orange.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-detnet.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: The IESG <iesg@ietf.org>, "draft-ietf-detnet-controller-plane-framework@ietf.org" <draft-ietf-detnet-controller-plane-framework@ietf.org>, "detnet-chairs@ietf.org" <detnet-chairs@ietf.org>, "detnet@ietf.org" <detnet@ietf.org>, "lberger@labn.net" <lberger@labn.net>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Detnet] Re: Mohamed Boucadair's No Objection on draft-ietf-detnet-controller-plane-framework-12: (with COMMENT)
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/0NEihG_TNRG7io9W1itF2grlywM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Owner: <mailto:detnet-owner@ietf.org>
List-Post: <mailto:detnet@ietf.org>
List-Subscribe: <mailto:detnet-join@ietf.org>
List-Unsubscribe: <mailto:detnet-leave@ietf.org>
Hi Carlos, Thanks for the follow-up and the changes made in -13. I really like the changes. One item to check is that now that we say: Therefore, this document should be considered as the authoritative reference to be considered if/when protocol work on the DetNet controller plane starts. Do we need to mark this document updating all the set of documents that include portions of the CP requirements ([RFC8655] , [RFC8938], [RFC9551], and [RFC9055])? I’m not pushing for any direction here. Cheers, Med De : CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es> Envoyé : mercredi 27 août 2025 19:33 À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com> Cc : The IESG <iesg@ietf.org>; draft-ietf-detnet-controller-plane-framework@ietf.org; detnet-chairs@ietf.org; detnet@ietf.org; lberger@labn.net Objet : Re: Mohamed Boucadair's No Objection on draft-ietf-detnet-controller-plane-framework-12: (with COMMENT) Dear Med, Thanks a lot for your review and comments and apologies for the belated reply (with the summer break it's taken longer than it should have). Please see inline our comments below. We have posted a new version that hopefully addresses your points as explained below. On Thu, Jul 31, 2025 at 9:14 AM Mohamed Boucadair via Datatracker <noreply@ietf.org<mailto:noreply@ietf.org>> wrote: Mohamed Boucadair has entered the following ballot position for draft-ietf-detnet-controller-plane-framework-12: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-detnet-controller-plane-framework/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Hi Andy, Xuesong, Mach, Balazs, and Carlos, Thank you for the effort put into this document. Also, thanks to Samier Barguil for the OPSDIR review. # Overall (1) Overlapping: The content is overlapping with what was already published in other RFCs, especially rfc8938#section 4, and DetNet Architecture, etc. Some guidance about which document(s) should be authoritative reference for these matters, should be clearly indicated here. [Carlos] We have modified the text in section 1. The updated text reads now as follows: -8-<- While the DetNet Architecture and Data Plane documents are primarily concerned with data plane operations, they do contain some requirements, and considerations for functions that would be required in order to automate DetNet service provisioning and monitoring via a DetNet controller plane (e.g., section 4 of [RFC8938]). The purpose of this document is to take these requirements and considerations into a single document and extend and discuss how various possible DetNet controller plane architectures could be used to satisfy these requirements, while not providing the protocol details for a DetNet controller plane solution. Such controller plane protocol solutions will be the subject of subsequent documents. Therefore, this document should be considered as the authoritative reference to be considered if/when protocol work on the DetNet controller plane starts. -8-<- (2) (Lack of) Friendly consistency check: The text does not help readers map the requirements in the document with their origin specs, let alone tag new ones (if any). An easy fix is to tag explicitly those that are inherited from existing specs. [Carlos] Thanks for the comment. We've added a explicit tag as you suggested. (3) (Lack of) DetNet specifics: Many of the requirements are provided in generic terms that can be applicable to any TE scheme that includes path computation, etc. Even PREOF discussion does not got into more specifics. [Carlos] The text is written assuming the DetNet framework and architecture as a starting point and actually many requirements are collected from such documents. We believe that going into more specifics will deviate from the goal of this document. # Detailed comments; major ones are marked with (*) ## At least RFC8655 is normative (*). Please double check the current classification your references. [Carlos] This is now fixed, thanks. ## This is about “a” framework, not “The” only framework that can be considered I suggest to make that clear in the document title NEW: A Framework for Deterministic Networking (DetNet) Controller Plane [Carlos] I've done that change, assuming that our AD and WG chairs are fine with that. Better, I would include “Requirements” in the title [Carlos] I prefer not to do this change as the requirements are not the main contribution of the document (many of them are actually collected from other existing documents and included for completeness) ## Introduction ### Consider citing 4.4.2 of rfc8655 for the following CURRENT; DetNet overall architecture, the controller plane includes what are more traditionally considered separate control and management planes. [Carlos] This is now done, thanks. ### Consider citing rfc6632#section-4.2 for the following CURRENT: Traditionally, the management plane is primarily involved with fault management, configuration management and performance management (sometimes accounting management and security management is also considered in the management plane, but not in the [Carlos] This is now done, thanks. ## Flow (*) CURRENT: * Support the dynamic creation, modification, and deletion of DetNet flows. I can’t parse this, given that DetNet flow is defined in rfc8655 as follows: A sequence of packets that conforms uniquely to a flow identifier ^^^^^^^^^^^^^^^^^^^^^^ and to which the DetNet service is to be provided. It includes any DetNet headers added to support the DetNet service and forwarding sub-layers. For example, what does “deletion of DetNet flow” concretely mean from a control standpoint? Do we mean required state for the flow? [Carlos] I've replaced "creation" with "instantiation", which is the word that is actually used in RFC8655 in this context, cited below: "Instantiate DetNet flows in a DetNet domain (which may, for example, include some or all of the following: explicit path determination, link bandwidth reservations, restricting flows to IEEE 802.1 TSN links, node buffer and other resource reservations, specification of required queuing disciplines along the path, ability to manage bidirectional flows, etc.) as needed for a flow." ## What about encapsulation-specific and metadata control? (*) A specific encapsulation scheme may be needed to carry some metadata, per the following from the base arch: The use of encapsulation is also required if additional information (metadata) is needed by the DetNet data plane and either (1) there is no ability to include it in the client data packet or (2) the specification of the client data plane does not permit the modification of the packet to include additional data. An example of such metadata is the inclusion of a sequence number required by PREOF. Do we need to cover explicitly: * Discovery of encapsulation capabilities of underlying nodes? * Discovery of metadata schemes supported by underlying nodes? * Means to instruct nodes which encap to put in place and companion metadata for a given flow? [Carlos] This is actually a good point. I've added a short section (4.5. Encapsulation and metadata support) to briefly reflect these considerations. 4.5. Encapsulation and metadata support To effectively manage DetNet flows, the controller plane will need have a clear understanding of the encapsulation and metadata capabilities of the underlying network nodes. This will require a control mechanism that can discover, configure, and manage these parameters for each flow. The controller plane needs to understand and manage the encapsulation and metadata capabilities of the network nodes to provision DetNet flows effectively. This process might need a discovery phase, in which the controller discovers which encapsulation types (e.g., MPLS, IP) and metadata schemes (e.g., sequencing, timestamping) each node supports. After discovery, the controller might instruct nodes on the specific encapsulation and companion metadata to apply for a given flow. This ensures that DetNet packets are handled consistently across the network. For example, the controller might instruct a node to use an MPLS header and add a sequence number for a particular flow. ## Centralized SDN Controller and Control Plane Implications (*) CURRENT: * Allow flow instantiation requests to originate in an end application (via an Application Programming Interface (API), via static provisioning, or via a dynamic control plane, such as a centralized SDN(Software-Defined Networking) I’m not sure there is a value in “characterizing” an SDN controller as “centralized” here other than opening the door for discussion about single point of failure issues, implications on the delay (which is key for detenet) when there no distributed mechanisms to react to local failure and completely rely on a controller to detect and react to failures. The base arch has the required references for SDN matters (where some of this is already discussed): This echoes the composition of Figure 1 of "Software-Defined Networking (SDN): Layers and Architecture Terminology" [RFC7426] and the ^^^^^^^^^^ controllers identified in [RFC8453] and [RFC7149]. ^^^^^^^^^^ I suggest we simply delete the “centralized” mention (and fix some few nits) NEW: * Allow flow instantiation requests to originate in an end application (via an Application Programming Interface (API), via static provisioning, or via a dynamic control plane, such as an SDN (Software-Defined Networking) [Carlos] OK, thanks for the suggestion. ## Time Synchronization CURRENT: * Support queue control techniques defined in Section 4.5 of [RFC8655] and [RFC9320] that require time synchronization among network nodes. Wonder whether we can be more specific on the time synchronization, is it only between data plane nodes, or data planes and control planes, etc. [Carlos] As per RFC8655 this is between data plane nodes. I've made this explicit. ## Scaling CURRENT: * Scale to handle the number of DetNet flows expected in a domain (which may require per-flow signaling or provisioning). “Flows expected in a domain” is deployment-specific. Not sure how this can be useful for solution design. [Carlos] If the solution is designed for a specific deployment, this is meaningful. Since we are not advocating for/designing any specific solution, we believe it is useful to reflect that depending on the deployment requirements, the solution might be different. ## Provisioning-only (*) CURRENT: * Provision flow identification information at each of the nodes along the path. Flow identification may differ depending on the location in the network and the DetNet functionality (e.g., transit node vs. relay node). Shouldn’t we also cover retrieval of installed state that would impact forwarding of a flow matching that same identifier? How conflicts are detected/mitigated? Should there be some kind of priority/tie-break in place? [Carlos] What is covered is that the control plane needs to convey that information. Ensuring that the identifier is unique, etc is more implementation dependent. A companion management question to this CP requirement is whether support means to check the outcome of provisioned rule against a test packet? [Carlos] We consider this out of the scope for the framework document. ## Scope of CC and CV (*) CURRENT: * Support DetNet flow continuity check and connectivity verification functions. What is the scope of these checks? For example, do we envision those to in be triggered from any source node (including data plane nodes) or is this restricted to a controller? Also, do we envision that partial path check are covered? [Carlos] This is partially covered in the detnet-OAM document (RFC 9551), and it can be generated by any Maintenance End Points (MEP), which I believe could be any source node. By referencing RFC 9551, we believe this point is covered. ## DetNet and no-DetNet CURRENT: * Operate in a converged network domain that contains both DetNet and non-DetNet flows. This is fair for flows. However, are there specific CP requirements for domains where some nodes are not-DetNet? Or do we assume that the document assumes that the CP/MP is for DetNet domain with **ALL** nodes compliant with DetNet? Please clarify the assumption in the document. [Carlos] the document talks about detnet and non-detnet flows, not nodes. We assume a detnet capable network as described in RFC8655, no difference here, that should support both detnet demanding flows and non-detnet flows. ## “3.2. SDN/Fully Centralized Control Plane” As indicated above, “fully centralized” has scalability, availability, reactivity to failure, etc. implications that needs to be discussed. [Carlos] Those considerations would be implementation specific. The document discusses how a controller plane framework might look like and document possible high-level approaches, but we believe that the document should stay at this level and not go into more details. ## (Restriction to) YANG 1.1 OLD: Network node configurations for DetNet flows are performed by the controller using a protocol such as NETCONF [RFC6241]/YANG [RFC6020] DetNet YANG [RFC9633] or PCE-CC [RFC8283]. NEW: Network node configurations for DetNet flows are performed by the controller using a protocol such as NETCONF [RFC6241]/YANG [RFC6020][RFC7950] DetNet YANG [RFC9633] or PCE-CC [RFC8283]. ^^^^^^^^^^ [Carlos] Thanks, we have implemented this change. ## Topology assumptions: Single/Multi-attached End Systems (*) It seems to me that the architecture assumes that an end system is always single attached (that is, packets from a host are only received by a SINGLE ingress node and will be forwarded to SINGLE egress node). For example, the document says: 3. Based on the calculation result, the Controller distributes flow path information to the ingress edge node and configures network nodes along the path with necessary DetNet information (e.g. for replication/duplicate elimination). I’m afraid this is restrictive and that we should allow for having multi-attachment cases. [Carlos] I see your point, but current DetNet architecture kind-of assumes a single ingress node, and we followed the same assumption in the document. In any case, the document does not preclude other scenarios, though they are not considered specifically. ## Distraction :-) CURRENT: As such, segment routing can be considered as a new data plane for both MPLS and IP. I don’t think we need to include such statement as there are specific variant for MPLS and IP. I suggest we delete that sentence. [Carlos] Done. # Multi-domain Matters The current text is too generic. I’m not sure it adds much. If you keep it, it might be worth reminding DetNet scope: (RFC8655) DetNet is for networks that are under a single administrative control or within a closed group of administrative control; these include campus-wide networks and private WANs. DetNet is not for large groups of domains such as the Internet. [Carlos] I disagree with the limitation to multi-domain. RFC 8655 mentions explicitly multiple domains in Figure 5 (DetNet Service Reference Model), though no work has been adopted yet in the WG to tackle multi-domain aspects. But note that this has been discussed in past meetings and there is ongoing (individual drafts) work ongoing. The multi-domain aspect was actually discussed in one meeting and adding the text was the consensus of the WG. # RAW CURRENT: domains, e.g., PCEs need to discover each other, authenticate and negotiate per-hop behaviors. Furthermore, in case of wireless domains, the per-domain RAW specific functions like the PLRs have to be also considered, e.g., in addition to the PCEs. Add a pointer to RAW arch spec. Thanks. [Carlos] This has been added, thanks. Hope this helps. [Carlos] It helped a lot indeed. Thanks a lot for all your comments. Carlos Cheers, Med ____________________________________________________________________________________________________________ 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.
- [Detnet] Mohamed Boucadair's No Objection on draf… Mohamed Boucadair via Datatracker
- [Detnet] Re: Mohamed Boucadair's No Objection on … CARLOS JESUS BERNARDOS CANO
- [Detnet] Re: Mohamed Boucadair's No Objection on … mohamed.boucadair
- [Detnet] Re: Mohamed Boucadair's No Objection on … Ketan Talaulikar
- [Detnet] Re: Mohamed Boucadair's No Objection on … CARLOS JESUS BERNARDOS CANO