[mpls] Re: [RTG-DIR]Re: Rtgdir last call review of draft-ietf-mpls-msd-yang-07

mohamed.boucadair@orange.com Wed, 05 June 2024 16:27 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41BE9C15107C; Wed, 5 Jun 2024 09:27:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 7yTb01okGXad; Wed, 5 Jun 2024 09:27:16 -0700 (PDT)
Received: from smtp-out.orange.com (smtp-out.orange.com [80.12.210.121]) (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 3AD9BC15108F; Wed, 5 Jun 2024 09:27:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; i=@orange.com; q=dns/txt; s=orange002; t=1717604835; x=1749140835; h=to:cc:subject:date:message-id:references:in-reply-to: mime-version:from; bh=BO8rJ3c6pKwpfgAkKO6lEMH9gq2vAKPctyMonW9q9cY=; b=qCJfw7j/cG2C7Mmfn/VzFIwyMkmLylprr4EC+81supsekIFGSwxaguH1 Qt1s5ngidjEBAt3SzU9Fe3pl3/sitUd2vkI4ujpmdrpDTr9Ay2ccFpqkM duBtF/6mec+50ZQdaODeKbgy9sCYYdnemiVf35K7tH7i62C4+AoXxGV6q qhEdIdbIeKANK1r/i/e7MvcIlK7i5t0vHD8Y5O6zcFvBPTFTRJA7f4nQd M8bcExNCgN/eP9xVyVCPaDDOW9KRSVD4u74I18tnAFvWVQek/rDQ5WJ8v JsLSy3b7PH2GnVuQxJSm6nmsjZ3w+79LYR89kOM6PkGACygMomWOPXtx6 Q==;
Received: from unknown (HELO opfedv1rlp0e.nor.fr.ftgroup) ([x.x.x.x]) by smtp-out.orange.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Jun 2024 18:27:13 +0200
Received: from unknown (HELO opzinddimail1.si.francetelecom.fr) ([x.x.x.x]) by opfedv1rlp0e.nor.fr.ftgroup with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Jun 2024 18:27:13 +0200
Received: from opzinddimail1.si.francetelecom.fr (unknown [127.0.0.1]) by DDEI (Postfix) with SMTP id 3D9E5DE85177; Wed, 5 Jun 2024 18:27:13 +0200 (CEST)
Received: from opzinddimail1.si.francetelecom.fr (unknown [127.0.0.1]) by DDEI (Postfix) with ESMTP id A9E9EDE813FB; Wed, 5 Jun 2024 18:26:53 +0200 (CEST)
Received: from smtp-out365.orange.com (unknown [x.x.x.x]) by opzinddimail1.si.francetelecom.fr (Postfix) with ESMTPS; Wed, 5 Jun 2024 18:26:53 +0200 (CEST)
Received: from mail-vi1eur04lp2042.outbound.protection.outlook.com (HELO EUR04-VI1-obe.outbound.protection.outlook.com) ([104.47.14.42]) by smtp-out365.orange.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Jun 2024 18:26:53 +0200
Received: from DU2PR02MB10160.eurprd02.prod.outlook.com (2603:10a6:10:49b::6) by AS8PR02MB6936.eurprd02.prod.outlook.com (2603:10a6:20b:2e6::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7633.31; Wed, 5 Jun 2024 16:26:50 +0000
Received: from DU2PR02MB10160.eurprd02.prod.outlook.com ([fe80::c9a1:d43c:e7c6:dce1]) by DU2PR02MB10160.eurprd02.prod.outlook.com ([fe80::c9a1:d43c:e7c6:dce1%6]) with mapi id 15.20.7633.021; Wed, 5 Jun 2024 16:26:50 +0000
From: mohamed.boucadair@orange.com
X-TM-AS-ERS: 10.218.35.125-127.5.254.253
X-TM-AS-SMTP: 1.0 c210cC1vdXQzNjUub3JhbmdlLmNvbQ== bW9oYW1lZC5ib3VjYWRhaXJAb 3JhbmdlLmNvbQ==
X-DDEI-TLS-USAGE: Used
Authentication-Results: smtp-out365.orange.com; dkim=none (message not signed) header.i=none; spf=Fail smtp.mailfrom=mohamed.boucadair@orange.com; spf=Pass smtp.helo=postmaster@EUR04-VI1-obe.outbound.protection.outlook.com
Received-SPF: Fail (smtp-in365b.orange.com: domain of mohamed.boucadair@orange.com does not designate 104.47.14.42 as permitted sender) identity=mailfrom; client-ip=104.47.14.42; receiver=smtp-in365b.orange.com; envelope-from="mohamed.boucadair@orange.com"; x-sender="mohamed.boucadair@orange.com"; x-conformance=spf_only; x-record-type="v=spf1"; x-record-text="v=spf1 include:spfa.orange.com include:spfb.orange.com include:spfc.orange.com include:spfd.orange.com include:spfe.orange.com include:spff.orange.com include:spf6a.orange.com include:spffed-ip.orange.com include:spffed-mm.orange.com -all"
Received-SPF: Pass (smtp-in365b.orange.com: domain of postmaster@EUR04-VI1-obe.outbound.protection.outlook.com designates 104.47.14.42 as permitted sender) identity=helo; client-ip=104.47.14.42; receiver=smtp-in365b.orange.com; envelope-from="mohamed.boucadair@orange.com"; x-sender="postmaster@EUR04-VI1-obe.outbound.protection.outlook.com"; x-conformance=spf_only; x-record-type="v=spf1"; x-record-text="v=spf1 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/14 ip4:104.47.0.0/17 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/49 ip6:2a01:111:f403:8000::/51 ip6:2a01:111:f403:c000::/51 ip6:2a01:111:f403:f000::/52 -all"
IronPort-Data: A9a23:JhUy4KhitCzO5T/xk8/TkXaFX161tRcKZh0ujC45NGQN5FlHY01je htvDGjQPPmCYjShe90kbd6z9EhUvMPUzNJkTgJs+Ho8QXsW8JqUDtmndUqhZCn6wu8v7a5EA 2fyTvGacajYm1eF/k/F3oDJ9CU6j+fRLlbFILasEjhrQgN5QzsWhxtmmuoo6qZlmtHR7zml4 bsemOWBfgf1s9JIGjhMsf7b9ksy5K+aVA4w5TTSW9ga5TcyqFFFVPrzFYnpR1PkT49dGPKNR uqr5NlVKUuAon/Bovv8+lrKWhViroz6ZGBiuVIPM0SWuSWukwRpukoN2FjwXm8M49mBt4gZJ NygLvVcQy9xVkHHsLx1vxW1j0iSMIUekIIrL0RTvuSM/0zpf13tmM9yFX41JZAq1NQwJ2xRo KlwxDAlNnhvhsqb/YjjFqxSp51mK8PmeoQCpntn0DfVS+48RozOSLnL4tke2yosgsdJHrDVY M9xhThHNUycJUEQfA5LTs5k9AurriGXnzlwrVWVrK867y7ZyxF62bTkMcD9fcaDQ8pY2E2fo woq+kylWkhBZIbBllJp9FqrttSUvX2nQbsRK6GfptJloBqMxkUcXUh+uVyT+qLj1hHWt8hkA 10V/CU8raU0sk2mUtfVUBixoXrCtRkZM/JZGOA3rgCA1qT87AOQB2xCRTlEAPQquOc6RSY3y FOJmN/4QzdotdW9U26Ss7uVtxuzNDQba2gYakcsQREM7cWmoYwvgFfKVtJ4VauugpjkEDf/h TmOqAA/iqkdy8kR2M2T+Vncn3enr5zNZg84+guRWXiqhit8fIq+T42l9Vad6uxPRLt1VXGEt XkA3tafte0TF8nRkDTXGLlXWra0+/yCLTvQx0Z1GIUs/Cis/Hjlep1M5DZ5JwFiNcNslSLVj FH7pjNQy5N1PSCQcbZIYJqsOeoYio7tCoGwPhzLVeZmbp90fQ6B2ShhY0+Mwmzg+HTAd4luY f93lu78XB4n5bRb8dagewsK+ZYXrh3SKEvWTJH/igqmiLeDfibJTa9faAfUKOck8KmDvQPZt c5FMNeHwAleV+u4ZTTL9YkULhYBKn1T6XHKRy5/KLXrzulOQTpJ5xrtLVUJJtMNc0N9yrigw 51FchUEoGcTfFWeQelwVlhtaan0QbF0pm8hMConMD6Agid6Ptv1sfZOLcJqIdHLEdCPK9YlF 5HpnO3QU5xypsjvp2pEM/ERUaQ+Kkv33lLWb0JJnhBmIMM7F1ehFiDYkvvHr3JUUnXfWToWp ryrzATARpQfDw9lFt6+VR5c5wLZgJTpo8orBxGgCoALJi3EqdE2QwSv1KNfC59Xc33rmGDFv zt69D9D+IEhVadurIKW7U1Fxq/1e9ZD8r1yRjCKtOfmaXGBowJOA+ZoCY61QNwUb0uskI3KW Amf56iU3CEv9LqLj2Z9L1qv5Y8D3YOz4oF7l0FjFniNaEm3ALR9JHXAxdNIqqBG2r5ev02xR 16L/d5Zf76OPasJ1XYPcRE9YL3rOe48w1HvATYdeC0WJxObOJKAS0xUMBTKgytYRFewGJ1w2 v8v4ab69CTj4icX3g66sx1p
IronPort-HdrOrdr: A9a23:b0KsYKG/QwJFfpjYpLqF7ZLXdLJyesId70hD6qkvc20pTiXIrb HVoB1E726OtN9IYgBppTiBUJPwMU80hqQFqrX5XI3SATUO3VHCEGgM1/qX/9SNIVyBygcZ79 YoT0FyMqyVMbEYt7en3ODbKadW/DDvysnB9IKuqQYVPHkaF9Ae0+46MHfsLqQcfng0OXNNLu vo2iMxnUvTRZ14VLXLOlA1G8L4i5ngkpXgbRQaBxghxjWvoFqTgoLSIlyz5DtbdylA74sD3A H+/jAR4J/T0YDd9vYj7Q7uBm9t9+cJNuEzZ/BkcPJ4FtwSsGiVjXlaO4GqjXQQmqWC+VwqmN 7Dr1MLJMJo8U7ceWmzvF/ExxTg+CxG0Q699XaoxV/Y5eDpTjMzDMRMwahDdAHC1kYmtNZglI pWwmOisYZNBx+oplWt2zGIbWA7qqOHmwtxrQchtQ0LbWLYUs4EkWUrxjIHLH7HJlOs1GloKp g5MCiW3ocaTbrTVQGUgkBfhPihWWkyGBCdK3Jy8PB9lQImw0yRhnFoivD2kho7hd0AYogB6O LePqtykrZSCscQcKJmHe8EBdC6E2rXXHv3QTqvyPvcZeQ60l/22tjKCY8OlbiXUY1NyIF3lI XKUVteu2J3c0XyCdeW1JkO9hzWWm2yUTnk18kbvvFCy+fBbauuNTfGREElksOmrflaCsrHW+ yrMJYTB/P4N2PhFYtAwgW7UZhPLnsVVtETp78AKgmzi9OOLpevuv3Qcf7VKraoGTE4WnnnCn 9GRzT3LNUo1DHtZpfS6CKhGk8FunaPua6YPJKqvdT7krJ9drGkmjJlymiE2g==
X-Talos-CUID: 9a23:zfJr1WOfM1zbo+5DRxlm20IyG5sfbmTiz2/NEWGKTkBkV+jA
X-Talos-MUID: 9a23:7/qyUQURUwxoNvXq/Djcv2pCaptx2qeRFGddvZom/NaEHCMlbg==
X-IronPort-AV: E=Sophos;i="6.08,217,1712613600"; d="scan'208,217";a="40138267"
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CVjmGzLPD+sb0a4tKY70IigH2KfbGdHAGnpLc69oNLLn5IXWXDZ6VwiTgMfDY/uxOCJNe7KDjZuVqju39kUum0E1MDysTFpkt1WdYFCYUXIzTrcMkr+odaDsFnHeTrhoCTiQ21OUa/H1K+7tGwzGOnBpMeUmaJ6bybpSp7zCPnkHhqFqJTu7GDffOhq+pISKML+1M+G3Ao1STgOdDJ/X7m/kuUgFGGI/6Pdf0MTVp2Cw9TezqODeD88VokW8GxtaJORHlLUzdrGWhtHA+FFcvlDlCopdAuNpFjFA8AMaakMoEnK/zbgRNuS+DF3Lgrj2pUCgq2X6fTkqdhadUXmC4A==
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=Y82rSTHVVYHAWEnuHaDBxCHXTqXJldzimP3hauiSZns=; b=QJACFX/T2R6sxLToqSZDjV3cn3utg80cP61GVcD7R8ncgpaI3jZj2FJOp/CO56AiomC74//Pt6PbJFrzGFRFG4SfBJmXNzqvQTe1hZo4GDbNtbcHx7zktMYVm96sW7P7s5TLmtjtkqG6qCji6mf5YFMGmt3/GdC2PV7rMMjMkr3moqnChKlBD+aSJQcnkJZvE1PsgEadozW3QbfTabyujDvCW9JLedU3ILS/Q0rB8NWgAcJme2Nw6j5RuKQewT69e4jL5IJudG0Y4Fiw7EhIE2lsipcwqBtuzDjstY/uw4ibauUFa2qi1MygKDtWcnGSqwSsc9ck2sQ2TnzsZCdkGA==
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: Yingzhen Qu <yingzhen.ietf@gmail.com>
Thread-Topic: [RTG-DIR]Re: Rtgdir last call review of draft-ietf-mpls-msd-yang-07
Thread-Index: AQHat2HC2HgVxbeNX0mLEpnFvCO6v7G5WjFw
Date: Wed, 05 Jun 2024 16:26:50 +0000
Message-ID: <DU2PR02MB101605909EAA0561B18194E1A88F92@DU2PR02MB10160.eurprd02.prod.outlook.com>
References: <171743797081.42914.4518891340142384843@ietfa.amsl.com> <DU2PR02MB1016077CA409CD39DB09F04E988F82@DU2PR02MB10160.eurprd02.prod.outlook.com> <CABY-gOOhPR=3nixD2qwW99i9DArYNiY3Xk-w258B2Pa4vqz2bg@mail.gmail.com> <DU2PR02MB101603134893C129D606A271288F92@DU2PR02MB10160.eurprd02.prod.outlook.com> <92571ED1-FD5F-47C6-A158-2E3BE2B2B0CB@gmail.com> <DU2PR02MB101608D94311BD0B28776344788F92@DU2PR02MB10160.eurprd02.prod.outlook.com> <CABY-gOPB=HKpTVX-nzy9HNabv0bXNU6Fz5AK4KA-8V9kfJjVvg@mail.gmail.com>
In-Reply-To: <CABY-gOPB=HKpTVX-nzy9HNabv0bXNU6Fz5AK4KA-8V9kfJjVvg@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=0d91d670-75e7-4986-b1ab-53e31d95646c;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=2024-06-05T16:26:47Z;MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20;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: DU2PR02MB10160:EE_|AS8PR02MB6936:EE_
x-ms-office365-filtering-correlation-id: c623316d-8b39-455f-e4cc-08dc857c4dda
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230031|366007|1800799015|376005|38070700009;
x-microsoft-antispam-message-info: MgKKgEETjtyaYqIiVj3jHoRjAPf5KX11s7ZWA+zcKhwQ8DRZBa61hdGTVbOLR09+Fgkxd5vBiM30AqB2yMjLJrAVQ5Znc7I0TDommrSJLg0NnH7EXRAOPDy9Aiy/gnmAtRDcTnweelMc2qMoXHuL15sPeGhFTwFerQRYY9ZB83+Ry/NMTaaybfMBPo9CGLUBAh88NuYxPFML5XKumAjqkjzsfp2LvdXApAQx9Pza7AdXOP99erDmN69uRnNj162nC2TWLsi00Xsj+1/uY5dO/BWUONj2Z/K8SQ3uIuxo3gCrxCiw9PWWFNzkm8WkOIQBcQ36f9xc3fuoi5DVfydz0x3cH9McQpw2K1JPg1yYoFcggU7KRSB3jY1CyQZojb+msDpedfWAoMqxlOfcGnPZh9QCc++mZnzA812lcx6RpkbMMYVi4ZckPxJeTCQ9EkFjIZRlvr223ckK27jXmO99VYgK9wKuGCs0caDbhDfXcAaF+ovNeIlHmQc4CHVPB+hECnZdgpk2Tds5JNfhlfDDaG51OTNFlF+75LEsIBItgNSlZjicGe1xXsUgz/bdyEbKu92RSy4Dq7/B2Z86JZmYETT85xyd+zH7Tx2BgoIREttMOzZxzonJRCZdbXudgKfDmzE0GceqUoWb9YcwAfOsSwguonnIe00P+h7id/oK9Ne+GoEIwPZgJG1YVBU2e5jmJBZHzRtsA+JqZZbanpRi/qhB4tnTVTNrGW6O81CH7X3lfExS0xv8tlakitoHrnC6KBM2mVe0sYMKycTD5oAJ6BHZiDVTHDS6MwhdwKzY3eVeKdxHt1iqnBM9jRu2/OpMpKb7ALl0CIh0tmKKq2UuDFGCQE7MJmsFGPQTVkoWBnth4PI1HwM++TIznwmhVmGjcKlW36CE38KQ2872bQo+dnP3GY2eB0XyGG9gTMsuDFZgIet0uETYDD+y7oohE6P8rIQbcQiIuw2F1lTVg22HKvzFE+E6oST79Ea0lv+nTNfCp+VkMojgkfJryndWo1RPTCjN/dGjNMZ4PIkkQBhV5ynRTG4xzTgXw6zE8rh/e/AcbddgMvvAXLJvUEu7jqlVtJnJQnG0O73lPC7fWxTB4V0eTsCRlANv9mCLTiHEDz72g6uQ173HdUC7T/yW3L+e6+EDW3BTwBtgiDFXy6yCH+ahvujXsUD8lg8Rptkg2jJeAkcmE1Xxr68PsS4WGFC/mmtda4vzkCpIPw9L95vu4C5wJaZlCGQtlhaUsO/6CLX0IULrLPg804kWEmYeywfyU/xrqgqQGeFvDke/wAD4MEaYOprHpb5R4UfEF3dIudCJSPQz2LZzCxSK4NK8XuHF
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:DU2PR02MB10160.eurprd02.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230031)(366007)(1800799015)(376005)(38070700009);DIR:OUT;SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: dbrW/LLCGuNHy4a0aIUWyZlebijH8t9NmyaCVylBjbpUFL12Um7NGdZaL+ZTHqGCk1Z5pgCcVn8Cp2cD3N4CFPcbvQ0dAtC9ExtJ/y6XbHYChMfmXe8U69Oyv66U/ohkgcZWSLDP93fo/KH42beoKJOJBMu7BLgr7xHfkox4aMPHWv+cTiDC2dTSPklEJ3HSZqeVaqTn7A2Iplixhf2hU/DwgIInIPigEiDrVyXPvUE3cC7v8zDMHsVKGFrmXWokO02KzhFdH1lWdFDQ3avrmURLVUuaoKzhWw9eWBvKUx26G0/zYg2TATgUNIA+2PBPW1bEIDIVxCdoYKyh+sXOSddx3yOBNwnTIA+hqQSKfwPQvU4IFJ9V2VsvL97UHfDbaUKhUi0FJIQXx7LJZH6UYAePXjpZa8bfDMSBp2N6uFAIVhpnprLjDdRfOIw+u96DnAGWYjib3HJyanlqQwz1cxrNBPLagiHRnO1poCtOHR6NqDAWzRdhEPnyBfebWALbIx12BFZS8LTBbnKgWCMmCGFg1XBGybDiZ6aQSM7/95KCe/C3PXsmtxbstjN49M4budw+lFy9Jw/o4gOLoH1fAmhWIoT/UjxrweBJlQaPhy4vAeg734y2lP/jgBmGmlBJ2f2qRvkkH39BtAs4dCluwSnnJCTs7vcwBCAbWBxRhet2k7sRtApjRBX5NxPaQmbt4+7dkqqAa3tXumiVFJcfqe27+g7n3iu0A0XSZ+uKikU21TtPm1Np8dbwbRMBMYctBgvKth96FwEVmhO4X3n8uXyo9neOMfv18zKISV6W4UOwYfuPJvchtEGtdh/i2scm+UP2YHEHP/N3wh14W0j/DszEPxYl84DoWeD9AeuA8XwDP2glXhX7HplEOF+vEj8hZYYIBH9ENH0qf0jMoItQc+XPtVWSQIqvvirbf6Y6w/O6vTD6cr0eSHdvMRjC8xiH0ohFY9ed9T8cQ9BrhyffSWGONRc1DfZ8/cwzAl7y4SLVRm8tQO5mUUq8HU8q81cYA9ohzm1iVrwm9rKHS9FvA9wf5seXGKk082HeHuJmy3ns3n7px1j+A2YOsy8h30+a/BkcUAOYplC56AoQZ9Q2X9Wi5SLgpaeD12SOeoAiKMF+EdYoveb2dAKLrl8os6SWQOi12w2vSGcNph4DOK2ohQnNzbTRAjticpFsu738Z8A5shiNFMPoh8aIVCvwSiGfWloqBJoUcSIa83ZELAMN6gkRgDL9LtL4jrB9dvN9+ASiycfRtN22MrNh4+B+McPHnh37TSVfvS/Qpm0FhbdX7LMkVL5VBmfJLwla+1viYyt0yjW/cAVFUIlXejpRiGbsgasVfrEolc4Y9fhyDe8JZOaXdYXUFZaNH8W1cnxIKpBsHJJ/ntR3z6gZI6NJFH4W2oPDWKJhc5J6bG/3nbiphwEoHjbCSQTCQ0xPSk0fZH6MW0dX+caoD2wyAqMn0wEKxDuCheQ/7A/0ViXQUfIcmTBekjY32pe19Qud36/+l2EYvxs9PW32YiX36fJylf6+MhmKZcimeemMpK+OitHmID9KpiFj2WgBfvvFU46eXvCqZKsXUjMUzOqOuC9frvGHRi+NB0YA9pNJ4xdTFrLcRQ==
Content-Type: multipart/alternative; boundary="_000_DU2PR02MB101605909EAA0561B18194E1A88F92DU2PR02MB10160eu_"
MIME-Version: 1.0
X-OriginatorOrg: orange.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DU2PR02MB10160.eurprd02.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c623316d-8b39-455f-e4cc-08dc857c4dda
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Jun 2024 16:26:50.7835 (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: e8giTHDkT906FBUticiRzaP5C4m3gEwXQojgA0zu/BGwSTKWMw9CCw8hsbgteiU9JHZ0apKWowRC2Rk7zNk73E1TNI77Vimayw5RO2hAE8k=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AS8PR02MB6936
X-TM-AS-ERS: 10.218.35.125-127.5.254.253
X-TM-AS-SMTP: 1.0 c210cC1vdXQzNjUub3JhbmdlLmNvbQ== bW9oYW1lZC5ib3VjYWRhaXJAb 3JhbmdlLmNvbQ==
X-TMASE-Version: DDEI-5.1-9.1.1004-28434.001
X-TMASE-Result: 10--42.276400-10.000000
X-TMASE-MatchedRID: wEyyttUyB0DuYusHgJkgylpjn692i6cImelO0IZKkZ51V0N/6ncOclol 5amyTRjed02he/pQmb5BkGNjzKcRUtyBRU/cKn697/SSebKLqswSgmfkOsgfKux8ZrLrzcv4g5o rtHq/YwwLdJYj5o/Zfa1neps1Le8BplW/mWST1j1lRzZAkKRGDcfeB9YJ7/i609g30U+SFMTnr2 V/WkjVxqj/np5YdoJT3HZHraAJFueOtWfhyZ77DvZqI0nPzd0HDO+DX+rUwfbcV/v7G+gTwXZMo aNFpAF4b8cs4d9pi0bQja2spUfLvBqkhv3OdF4DtAQ1UAnR9nemOWRsO8Mnh86gaBUoaadKfevq uc0ZTU2OQUx9FgT12fqdMWc1bp2Oxvp0tuDMx3myHEuvZQ1reByiUdPkLtYyNylek8JXQTfBlmQ lrxpww41u/JNKOSTaUMJNi8DXwslM+xVFI1xtYxxWe9Fr7D9GXvSWyok2Zx6RoR8gw+M3ziolWO AMg2fcMud51mDL3dHRft8seEs4HNGdHZ5d5JY3d7O0M/VR5kcXtciauhyIR9Tru3GzAxaS5C3ip 8z754YCABdcsis79WdvGUEuKvScIi5n/oIUxv/J5SXtoJPLyHU98taw1P0pPE5gHU8nMv44+mW+ W7YcYwlJ/ieHRHSnexJm75dx4Prx5KZMlKYS/cJWkMZBXP7DePivT7LmG6HKeRDONTyPekbIRyp x2ie+c8YT4OzcCjIv1RkxO1FzzvZOZ2c2VQUg/jYKd9VlUo4nRHJyD9RUCAoW9dJZmjf2raob30 8tFzfdzqMAs8XjZBlNN9F7oe3yDDzmS9l9fYoNsuQOB7UFW0GGpJy/q0pao8WMkQWv6iUojzu/j hRWTQKLL4Z+HVHJdR/G8OvKIg/SBVVc2BozSlkMvWAuahr8wxWsZgByNxb7vaaHPP4LSwMG6feT LjAg5eoT+CMsQaDC3mjfc0j3ZvAxRSAc0OENIuJieNVvzvp+3BndfXUhXQ==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
X-TMASE-INERTIA: 0-0;;;;
X-TMASE-XGENCLOUD: f183de30-1d14-4877-8694-d23f78677ae6-0-0-200-0
Message-ID-Hash: WT36ZBMOZ6AOJV3GOSLWHAQJ45TK5FKS
X-Message-ID-Hash: WT36ZBMOZ6AOJV3GOSLWHAQJ45TK5FKS
X-MailFrom: mohamed.boucadair@orange.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mpls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Dhruv Dhody <dd@dhruvdhody.com>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "draft-ietf-mpls-msd-yang.all@ietf.org" <draft-ietf-mpls-msd-yang.all@ietf.org>, Last Call <last-call@ietf.org>, mpls <mpls@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [mpls] Re: [RTG-DIR]Re: Rtgdir last call review of draft-ietf-mpls-msd-yang-07
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/y5R4613GVJUQw7R0TH6Ms2v6bsY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Owner: <mailto:mpls-owner@ietf.org>
List-Post: <mailto:mpls@ietf.org>
List-Subscribe: <mailto:mpls-join@ietf.org>
List-Unsubscribe: <mailto:mpls-leave@ietf.org>

Re-,

I actually checked that before making the comment. There is no such requirement for new requests in https://www.rfc-editor.org/rfc/rfc8491.html#section-6.

May be I’m not looking in the right place?!

I would appreciate if you can point me to where I can find this requirement: “the document that defines the new entry should state what the MSD is for”

Cheers,
Med

De : Yingzhen Qu <yingzhen.ietf@gmail.com>
Envoyé : mercredi 5 juin 2024 18:02
À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>
Cc : Acee Lindem <acee.ietf@gmail.com>; Dhruv Dhody <dd@dhruvdhody.com>; rtg-dir@ietf.org; draft-ietf-mpls-msd-yang.all@ietf.org; Last Call <last-call@ietf.org>; mpls <mpls@ietf.org>
Objet : [RTG-DIR]Re: Rtgdir last call review of draft-ietf-mpls-msd-yang-07


Hi Med,

When a new entry is added to the "IGP MSD-Type" registry, the document that defines the new entry should state what the MSD is for.

I'll update the security consideration.

Thanks,
Yingzhen

On Wed, Jun 5, 2024 at 7:06 AM <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> wrote:
Hi Acee,

Please see inline.

Cheers,
Med



Orange Restricted
De : Acee Lindem <acee.ietf@gmail.com<mailto:acee.ietf@gmail.com>>
Envoyé : mercredi 5 juin 2024 15:35
À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>>
Cc : Yingzhen Qu <yingzhen.ietf@gmail.com<mailto:yingzhen.ietf@gmail.com>>; Dhruv Dhody <dd@dhruvdhody.com<mailto:dd@dhruvdhody.com>>; rtg-dir@ietf.org<mailto:rtg-dir@ietf.org>; draft-ietf-mpls-msd-yang.all@ietf.org<mailto:draft-ietf-mpls-msd-yang.all@ietf.org>; Last Call <last-call@ietf.org<mailto:last-call@ietf.org>>; mpls <mpls@ietf.org<mailto:mpls@ietf.org>>
Objet : Re: [RTG-DIR]Rtgdir last call review of draft-ietf-mpls-msd-yang-07


Hi Med,

See inline.

On Jun 5, 2024, at 04:16, mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> wrote:

Hi Yingzhen,

Thanks for taking care of this. The new version looks better.

Still, I don’t see how the hierarchical identity structure can be automatically inferred from the current flat registry structure. I’m afraid that the instructions in the 3rd para of 6.2 are not sufficient as I don’t think that we can trust the presence of SRH or some magic words in the description to decide which identity to use, and more generally if “a new data plane” is used.

Both the description and references listed in the IANA module diverge from the actual content of the registry. I would avoid that. Please refer to this clarification in the 8407bis (see the last sentence, in particular):

   The content of these registries are usually available using various
   formats (e.g., plain text, XML).  However, there were some confusion
   in the past about whether the content of some registries is dependent
   on a specific representation format.  For example, Section 5 of
   [RFC8892] was published to clarify that MIB and YANG modules are
   merely additional formats in which the "Interface Types (ifType)" and
   "Tunnel Types (tunnelType)" registries are available.  The MIB
   [RFC2863] and YANG modules [RFC7224][RFC8675] are not separate
   registries, and the same values are always present in all formats of
   the same registry.

I disagree. The fact that we have a hierarchy of identities wouldn’t confuse anyone. They are all part of the
iana-msd-types.yang model and all have “msd-base” as the root identity. We are rejecting this rather
 subjective comment.

[Med] Hmm…this is not subjective :-) Let’s consider that I registered a new entry in Interior Gateway Protocol (IGP) Parameters (iana.org)<https://www.iana.org/assignments/igp-parameters/igp-parameters.xhtml>

115
My own type
[MyREF<https://www.iana.org/go/rfc8491>]

How IANA will follow the following guidance? How IANA will know this is about an existing “data plane” or a new one? How it will decide to mirror it using existing one msd-base or msd-base-srh? How to infer a data plane from a registration? Etc.

   The identities defined in the iana-msd-types YANG module are
   organized hierarchically based on the data plane.  In this initial
   version, only MPLS and SRv6 data planes are supported, hence "msd-
   base-mpls" and "msd-base-srh" are defined.  When a new data plane is
   added to the "IGP MSD-Types" registry, a new "identity" statement
   should be added to the "iana-msd-types" YANG module.  The name of the
   "identity" is the prefix "msd-base-" plus a lower-case version of the
   data plane name .  The identity statement should have the following
   sub-statements defined:


If you want to suggest further text to explain this, we’ll consider inclusion.

Some other misc. comments:

(1) “lower-case version of the data plane name”: you may also indicate that the space is replaced with “-“, not trimmed.

(2)    "description":  Replicates the description from the registry.

I guess you meant replicate the “name” from the registry. There is no description in the IGP MSD Type reg.

(3)

OLD:
      name: iana-msd-types
      namespace: urn:ietf:params:xml:ns:yang:iana-msd-types
      prefix: iana-msd-types
      reference: RFC XXXX

      name: ietf-mpls-msd
      namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-msd
      prefix: mpls-msd
     reference: RFC XXXX

NEW:
      name: iana-msd-types
      namespace: urn:ietf:params:xml:ns:yang:iana-msd-types
      prefix: iana-msd-types
      maintained by IANA? Y
      reference: RFC XXXX

      name: ietf-mpls-msd
      namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-msd
      prefix: mpls-msd
      maintained by IANA? N
     reference: RFC XXXX

(4) the security section does not follow the template + does not cover the IANA module. Please refer tohttps://datatracker.ietf.org/doc/html/draft-ietf-netmod-rfc8407bis-11#name-security-considerations-sect.

The iana-msd-types.yang modules doesn’t include any data leafs so there are no associated security considerations. We could state this.
We’ll check the latest template in the draft.

[Med] There is a para in the template for that as well.

Thanks,
Acee

Cheers,
Med

De : Yingzhen Qu <yingzhen.ietf@gmail.com<mailto:yingzhen.ietf@gmail.com>>
Envoyé : mercredi 5 juin 2024 07:55
À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>>
Cc : Dhruv Dhody <dd@dhruvdhody.com<mailto:dd@dhruvdhody.com>>; rtg-dir@ietf.org<mailto:rtg-dir@ietf.org>; draft-ietf-mpls-msd-yang.all@ietf.org<mailto:draft-ietf-mpls-msd-yang.all@ietf.org>; last-call@ietf.org<mailto:last-call@ietf.org>; mpls@ietf.org<mailto:mpls@ietf.org>
Objet : Re: [RTG-DIR]Rtgdir last call review of draft-ietf-mpls-msd-yang-07

Hi Mohamed,

Thanks for the review and pointer. I've uploaded version -08 to address your comments, please review and let me know your comments, especially about the hierarchical identities.

Thanks,
Yingzhen

On Tue, Jun 4, 2024 at 12:18 AM <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> wrote:
Hi all,

In addition to the comments raised by Dhruv, the authors may look at the guidance athttps://datatracker.ietf.org/doc/html/draft-ietf-netmod-rfc8407bis-11#name-iana-maintained-modules for the required details for IANA-maintained modules.

## Lack of the details to maintain the module

There is currently no guidance in draft-ietf-mpls-msd-yang about how the module will be maintained. For example, given that there is no label but only a description field in the authoritative IANA registry, the doc should explain how names will be echoed in the module.

## Mirror the content of the authoritative registry

The content of the IANA module does not mirror the details in the registry. For example, there are many refs that are listed in draft-ietf-mpls-msd-yang, but those are not present in the parent registry.

## Hierarchy

The IANA module defines this hierarchy, while there is no such hierarchy in the IANA registry. I understand that the authors want to structure the types, but is this really required here? Absent guidance about how new entries will be echoed from the registry, I don't think this structure is easily maintainable. Please keep in mind that registrants of new types are not even aware that an IANA-maintained module exists. So, they cannot be involved in the process of maintaining the module.

==
     identity msd-base-srh {
       base msd-base;
       description
         "Identity for MSD types for Segment Routing Header (SRH).";
     }

     identity msd-srh-max-sl {
       base msd-base-srh;
       description
         "The Maximum Segment Left MSD type.";
       reference
         "RFC 9352: IS-IS Extensions to Support Segment Routing
                    over the IPv6 Data Plane";
     }

     identity msd-srh-max-end-pop {
       base msd-base-srh;
       description
         "The Maximum End Pop MSD Type.";
       reference
         "RFC 9352: IS-IS Extensions to Support Segment Routing
                    over the IPv6 Data Plane";
     }
==

Hope this helps.

Cheers,
Med

> -----Message d'origine-----
> De : Dhruv Dhody via Datatracker <noreply@ietf.org<mailto:noreply@ietf.org>>
> Envoyé : lundi 3 juin 2024 20:06
> À : rtg-dir@ietf.org<mailto:rtg-dir@ietf.org>
> Cc : draft-ietf-mpls-msd-yang.all@ietf.org<mailto:draft-ietf-mpls-msd-yang.all@ietf.org>; last-call@ietf.org<mailto:last-call@ietf.org>;
> mpls@ietf.org<mailto:mpls@ietf.org>
> Objet : [RTG-DIR]Rtgdir last call review of draft-ietf-mpls-msd-
> yang-07
>
>
> Reviewer: Dhruv Dhody
> Review result: Has Issues
>
> Hello,
>
> I have been selected as the Routing Directorate reviewer for this
> draft. The Routing Directorate seeks to review all routing or
> routing-related drafts as they pass through the IETF last call
> and IESG review, and sometimes on special request. The purpose of
> the review is to assist the Routing ADs. For more information
> about the Routing Directorate, please see
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%252>
> Fwiki.ietf.org<http://fwiki.ietf.org/>%2Fen%2Fgroup%2Frtg%2FRtgDir&data=05%7C02%7Cmohamed
> .boucadair%40orange.com<http://40orange.com/>%7C6ecf264db0bb43052c3b08dc83f8121b%7C90c7
> a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638530348673738183%7CUnkno
> wn%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1h
> aWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=vfo%2F%2BxP9zc3YIrI1b9RjmRl
> XL3MicMrirSECkDHfM3c%3D&reserved=0
>
> Although these comments are primarily for the use of the Routing
> ADs, it would be helpful if you could consider them along with
> any other IETF Last Call comments that you receive, and strive to
> resolve them through discussion or by updating the draft.
>
> Document: draft-ietf-mpls-msd-yang-07
> Reviewer: Dhruv Dhody
> Review Date: 2024-06-03
> IETF LC End Date: 2024-06-04
> Intended Status: Proposed Standard
>
> ## Summary:
>
> * I have some minor concerns about this document that I think
> should be resolved before publication.
>
> ## Comment:
>
> * This draft defines 2 YANG models one is IANA-maintained to
> mirror the msd-type registry and the other is augmenting base
> MPLS to include MSD values.
>
> ### Major Issues:
>
> - Please remove the BCP14 boilerplate (Section 1.1) as you are
> not using any of those keywords. Also, remove from the ietf-mpls-
> msd YANG model.
>
> - You should explicitly state that this is an initial version of
> "iana-msd-types" YANG model - "This document defines the initial
> version of the IANA-maintained 'iana-msd-types' YANG module."
>
> ### Minor Issues:
>
> - Title: Please change to "A YANG Data Model for MPLS Maximum
> Segment Identifier (SID) Depth (MSD)". Also, update the reference
> in the YANG model around RFC XXXX.
>
> - The abstract suggests that only one YANG model is defined in
> this I-D.
> Consider rephrasing or adding some hints about the IANA model as
> well.
>
> - Section 1, "YANG [RFC7950] is a data definition language.."; I
> suggest changing it to data modeling as that is the term used in
> the referenced RFC.
>
> - Section 1, I am unsure about the text "The augmentation defined
> in this document requires support..."; isn't it obvious that one
> needs to support the model one is augmenting...
>
> - Section 4, please add this text in the description inside the
> YANG module - "This YANG module is maintained by IANA and
> reflects the 'IGP MSD-Types'
> registry."
>
> - identity msd-erld, should also have a reference to RFC9088.
>
> - In "ietf-mpls-msd", please remove the reference "RFC XXXX: A
> YANG Data Model for MPLS MSD." immediately after the module
> description. The revision statement is the correct place to have
> this reference.
>
> - leaf msd-value should also include text for "0 represents the
> lack of ability to support a SID stack of any depth".
>
> - I can not parse "A type of Node MSD is the smallest same type
> link MSD supported by the node.";"
>
> - RFC8340 should be normatively referenced.
>
> ### Nits:
>
> - s/(MSD) Types as the IANA the IGP MSD-Types registry/(MSD)
> Types as per the IANA IGP MSD-Types registry/
>
> - s/which itself augments [RFC8349]/which itself augments routing
> RIB data model [RFC8349]/
>
> - s/IANA maintained module/IANA-maintained module/
>
> - s/This module will be maintained by IANA if more MSD types are
> added to the registry./This module will be maintained by IANA and
> updated if and when there is any change in the registry./
>
> - s/and it is to provide support of different types of MSDs in
> MPLS data plane./and it provides support for different types of
> MSDs in the MPLS data plane./
>
> - s/read-only data decided by/read-only data as per/
>
> - Section 4, expand SID on first use in the YANG model.
>
> Thanks,
> Dhruv
>
>

____________________________________________________________________________________________________________
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.

____________________________________________________________________________________________________________

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.


____________________________________________________________________________________________________________

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.
____________________________________________________________________________________________________________
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.