[mpls] Re: [RTG-DIR]Re: Rtgdir last call review of draft-ietf-mpls-msd-yang-07
mohamed.boucadair@orange.com Thu, 06 June 2024 07:32 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 2B3C6C1D874D; Thu, 6 Jun 2024 00:32:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 0udaN5EPWNbG; Thu, 6 Jun 2024 00:32:23 -0700 (PDT)
Received: from smtp-out.orange.com (smtp-out.orange.com [80.12.126.239]) (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 07709C1D5C4A; Thu, 6 Jun 2024 00:32:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; i=@orange.com; q=dns/txt; s=orange002; t=1717659142; x=1749195142; h=to:cc:subject:date:message-id:references:in-reply-to: mime-version:from; bh=hZVqGj2+Dh6QZOl4vHsr1NmawznIHedlWnRHIf/UFnI=; b=Zk5N8exLMwcnkTceTePpx2cd0PzBd/U++Ch+ZBoF7IuPYAf+ldB8BrvM wuefz/KEKvpq4Ek/RJYfvRIsNUy7vXTYbryH2hpjhRUxk0X47eW8LTbwp enBnGzp0JmvUSa4x5BJ9RcZr6rtO4mIin16Fsgva+ku9S+d+lmHq5KxDe jv+Npxw6Xa0BGkEacE5zBcGj6NN/RMi4vlIugTqdj7s+cNQKmZ5AUQns2 UpxLGgHWIEKY88BVNh7N8n49tmGkEaZ07+I7HjCl76LhuHGrLWkirCPVm 1c8pMQe50stzI8tFOZbMruc7YKzPKftevggz7v1HMZpBm3cSCg4W0NuPi w==;
Received: from unknown (HELO opfedv1rlp0b.nor.fr.ftgroup) ([x.x.x.x]) by smtp-out.orange.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Jun 2024 09:32:20 +0200
Received: from unknown (HELO opzinddimail5.si.fr.intraorange) ([x.x.x.x]) by opfedv1rlp0b.nor.fr.ftgroup with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Jun 2024 09:32:19 +0200
Received: from opzinddimail5.si.fr.intraorange (unknown [127.0.0.1]) by DDEI (Postfix) with SMTP id A0DCD10681B7; Thu, 6 Jun 2024 09:32:19 +0200 (CEST)
Received: from opzinddimail5.si.fr.intraorange (unknown [127.0.0.1]) by DDEI (Postfix) with ESMTP id 1A7C0106264B; Thu, 6 Jun 2024 09:23:49 +0200 (CEST)
Received: from smtp-out365.orange.com (unknown [x.x.x.x]) by opzinddimail5.si.fr.intraorange (Postfix) with ESMTPS; Thu, 6 Jun 2024 09:23:49 +0200 (CEST)
Received: from mail-db5eur01lp2050.outbound.protection.outlook.com (HELO EUR01-DB5-obe.outbound.protection.outlook.com) ([104.47.2.50]) by smtp-out365.orange.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Jun 2024 09:23:35 +0200
Received: from DU2PR02MB10160.eurprd02.prod.outlook.com (2603:10a6:10:49b::6) by AS8PR02MB8614.eurprd02.prod.outlook.com (2603:10a6:20b:54c::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7633.31; Thu, 6 Jun 2024 07:23:30 +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; Thu, 6 Jun 2024 07:23:30 +0000
From: mohamed.boucadair@orange.com
X-TM-AS-ERS: 10.218.35.129-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@EUR01-DB5-obe.outbound.protection.outlook.com
Received-SPF: Fail (smtp-in365b.orange.com: domain of mohamed.boucadair@orange.com does not designate 104.47.2.50 as permitted sender) identity=mailfrom; client-ip=104.47.2.50; 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@EUR01-DB5-obe.outbound.protection.outlook.com designates 104.47.2.50 as permitted sender) identity=helo; client-ip=104.47.2.50; receiver=smtp-in365b.orange.com; envelope-from="mohamed.boucadair@orange.com"; x-sender="postmaster@EUR01-DB5-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:7WqgRqvcTAniw3DcxZjOleS+/efnVINZMUV32f8akzHdYApBsoF/q tZmKTuFbq2LMDD2fNp/boi3p0gGv8LVz95kGQpvqno8Rn9D9ZOVVN+UEBz9bniYRiHhoOOLz Cm8hv3odp1coqr0/0/1WlTZhSAgk/vOH9IQMcacUghpXwhoVSw9vhxqnu89k+ZAjMOwa++3k YuaT/b3Zhn9i1aYDkpOs/jf8E034q2q0N8llgdWic5j7Qa2e0Y9XMp3yZGZdxPQXoRSF+imc OfPpJnRErTxpkpF5nuNy94XQ2VSKlLgFVHmZkl+AsBOtiN/Shkaic7XAha+hXB/0F1ll/gpo DlEWAfZpQ0BZsUgk8xFO/VU/r0X0aBuoNf6zXaDXcO76GT2UFzIk+tVUWI2IaNA+OEmMVBLz KlNQNwNRkjra+Oe7Y+BErApqu5+ac7hMcUYp21qyizfAbA+W5ffTq7W5NhemjAtmsRJGvWYb M0cAdZtRE2YP1sTZRFNTs9m9AurriGXnzlwrVWVrK867y7ZyxF62bTkMcD9fcaDQ8pY2E2fo woq+kylWkhEaIPEmVJp9FqUqvOfmyzndrtOM4Kc9Ll1oGesmG0qXUh+uVyT+qLj1hHWt8hkA 0AY0iYut7Us+EysQsi7VBq9yFaVvxgTSdpdFas75R2D4qXR6gedQGMDS1ZpYdcruYk3SCAk/ lCMltLtQzdotdW9U26Ss7uVtxuzNDQba2gYakcsQREM7cWmoYwvgFfKVtJ4VauugpjkEDf/h TmOqAA/iqkdy8kR2M2T+Vncn3enr5zNZg84+guRWXiqhit8fIq+T42l9Vad6uxPRLt1VXGEt XkA3sSUse0TF8nUkDTXGLhVWra0+/yCLTvQx0Z1GIUs/Cis/Hjlep1M5DZ5JwFiNcNslSLVj FH7niphx7h3bGWRMIx3f6zpCcN7/ZnlLIGwPhzLVeZmbp90fQ6B2ShhY0+Mwmzg+HTAd4lva P93lu78XB4n5bRb8dagewsK+Z4Grh3SKEvWTJH/ihitjLeDfibMTa9faAbWKOck8KmDvQPZt c5FMNeHwAleV+u4ZTTL9YkULhYBKn1T6XHKRy5/Jr/rzulOQTpJ5xrtLVUJJtANc0N9yL6gw 51FchUEoGcTfFWeQelwVlhtaan0QbF0pm8hMConMD6Agid6Ptj2tv1BK8JuJNHLEdCPK9YlF 5HpnO3QU5xypsjvp2pENvERUaQ+Kkv33lLWb0JJnhBmIMA8FlWhFiDYkvvHr3JUUnXfWToWp ryrzATARpQfDw9lFt6+VR5c5wLZgJTpo8orBxGgCoALJi3EqdE2QwSv1KNfC59Xcn3rmGDFv zt69D9D+YEhVadurYGV7U1Fxq/1e9ZD8r1yRTeAtO3mbXSCowJOA+ZoCY61QNwUb0uskI3KW Amf56inWBHbtD6mcraQEoqHCYoT2uG3/vp25FkhG3/GKVO2FrlnP3+Km9FVsbFAzaNYvg3wX V+T/t5dOvOCP8aN/Js5Ol8+duravR0LsmC60Bj3CB2SCOxLEH6vVl9bORaBzidaKdOZ9as7l Pw5tpd+BxOX1nIXDzpesh1pyg==
IronPort-HdrOrdr: A9a23:5GMoJauWBhMEnL0xNdHslZZ17skC/YMji2hC6mlwRA09TyXGra 2TdaUgvyMc1gx7ZJh5o6H5BEGBKUm9yXcH2/hrAV7CZnivhILGFvAH0WKP+VPd8mjFh5dgPM RbAuND4b/LfD9HZK/BiWHVfOrIguP3lpxA7t2urEuFODsaDp2ImD0JaDpzfHcWeCB2Qb4CUL aM7MtOoDStPV4NaN6gO3UDV+/f4/XWiZPPe3c9dlMawTjLqQntxK/xEhCe0BtbeShI260e/W /MlBG8zrm/ssu81gTX2wbonthrcZrau5R+7f63+4kowwbX+0aVjUNaKv6/VQUO0a+SAZAR4Z vxSlkbToFOAjjqDxuISFPWqnTdOXAVmjXfIBaj8ATeScCVfkNHN+NRwY1eaRfX8EwmoZV117 9KxXuQs95NAQrHhzmV3am+a/hGrDvAnZMZq59ms1VPFY8FLLNBp40W+01YVJ8GASLh8YgiVO 1jFtvV6vpaeU6TKymxhBgn/PW8GnAoWhuWSEkLvcKYlzBQgXBi1kMdgMgShG0J+p4xQ4RNo+ 7ELqNrnrdTSdJ+V9MKOM4RBc+sTmDdSxPFN2yfZVzhCaEcInrI74X65b0kjdvaCqDgDKFC66 gpfGkoxVLaIXied/Fm9Kc7gyzwfA==
X-Talos-CUID: 9a23:LS58km4N9nfbvhx93tss02ckOecBImPmkVTQP2HgC2E4eIyQcArF
X-Talos-MUID: 9a23:dVoOKw+VQK2jY4/xcYqoZDaQf/9E//SoB1wjqMkhhO2GcjNQAQjDjQ3iFw==
X-IronPort-AV: E=Sophos;i="6.08,218,1712613600"; d="scan'208,217";a="40164738"
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DtnTMCY1Q4ln8hV6KfvyZZI4fsVATLL4BFYwSaM8ftvEkcEAhZ0I8F6UHMACBW2iV+1MM4x5WJXjcYcKB7qpid5y+eARZIv3cNfja2aW9lFsbqnPG+HKq27u8zpxD98abtjllHUb8dMXBcRrpdJfELDZN/DPSUek9k/p21oPM/IeBYpVFvHXS9wQbeBRYfIzwGMWff9NFMwn6Q4iiljC8vXJXYIe/jjED8dlshjINltauHFOgWtoN+iNrUkg2s2263jogHfvACqhAMt9FxyrXwjnCkYqfS4Ulurk/kifowVVFvBAb59YHR1PuvdFU+E5aLgmGLfgek1HSegKrfWwQA==
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=fU3F+wFlpQ74p/Il+7fpkCRUsFFXw6OLz5ZOhqt874M=; b=ke7MgHRWkLNggBHjOO+vgu3DsXFivGYuctxIk6RzbaVEdoJbnEGcWvE6G3/+8nD/GCm9mEy/lf3RNboUrOi6QhGd+n/GxAwzsiGHRJa7Db9BIR/CpF9D9OWdo8V5FvtWVVVtKiE+D9a7deLA3KsWV6i+77PyO0/vb7bId6ac7QICrf35hzpFepSPYgP0UJ730PMe2Ucm48I8Kr3igAed1FitA6LkKO2jeFcynARJC+97I8mujAThXajKRybgsFK6Fcni0D4s8kE8unG0EN6mbV5pKhiIB4XHCvh5+LDICPKkNnPjwkRjidYRZYujP8zo6+eY/gTtmbGlkN+uNTj+Vw==
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: Dhruv Dhody <dd@dhruvdhody.com>
Thread-Topic: [RTG-DIR]Re: Rtgdir last call review of draft-ietf-mpls-msd-yang-07
Thread-Index: AQHat989U4RBMLcHz06vtAWxGH/6krG6UNkQ
Date: Thu, 06 Jun 2024 07:23:30 +0000
Message-ID: <DU2PR02MB10160C927F47A9063CA4BBC0C88FA2@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> <DU2PR02MB101605909EAA0561B18194E1A88F92@DU2PR02MB10160.eurprd02.prod.outlook.com> <CABY-gOOxwwAm+SmxqLZKkyDOre1rW4UT=vTO_YWFkshs3DyAyQ@mail.gmail.com> <DU2PR02MB101607B0BC82F9128AD02C35688FA2@DU2PR02MB10160.eurprd02.prod.outlook.com> <CAP7zK5aKn4N+hUYNk45He+MPROThcBSv=8ypLYKtRW3hc500XA@mail.gmail.com>
In-Reply-To: <CAP7zK5aKn4N+hUYNk45He+MPROThcBSv=8ypLYKtRW3hc500XA@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_f47c794b-e3ab-43f0-9e0f-29fc3e503192_Enabled=true;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: DU2PR02MB10160:EE_|AS8PR02MB8614:EE_
x-ms-office365-filtering-correlation-id: 5627f265-8989-4ee5-475f-08dc85f99104
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: bDlupJb4q+Tpta/I3d0tyNfsXVCuVhCdWwAnpdoF8VKd1C9PkoA/8nkAMQnWx4atnjJlJQf50Ps4I7tRDr/XP62VQ40gWVnH0AD6tVtH8Cn3NsBXDClOSso9e1YoEfeVL1+4uD3z1jB+zKGq4TBLRPZSw0jvxSXO7GSJjjQOuAEyK+Z9+CyNNbSnNABLJnrBONFX7leAfWr4xcVGV2sDnG+DmkIVTd9TY47v/jOn1tjOWfTsxpjSX1g7812lWvsiT4mzXoef+48w06vEuGiGeLVgyQtiDvNRW9UxZTPVNAvpunSRmb3dLBRARmYL7Y//xkDRNKZA1iZtindOj61zj+AhG+7PmQ/1JXBKLKePWUIqFI7cNhLGHEUqM4psihU3ZNFWTX3C5jiLzCJO+7hGK+SaKlfnHLWEMVm4mmyBeEb3AQyHch6xdc6/gMcsLJ8oGMZGqST7gkw0paMF+ZpHi8VqJVL44x8ZLmxv3SLL76Qyi/QJw2wsNi7twvhEEG8VcFCflGv7C0BVrhxrsTwVdCKXI4LKqIaql6bJEg/KlIb6wgUrMYR4fFo9sNYw4Q+T5CF9egqPTfif07br4wHwIbOGR7pWlJimAJrJgpiG16xoYKc6CohsuF4wliErsizHk6kczmlQkvW7ljpMQyvd9hcjkPKIoD0odQ+oGo4HGpBTfajQvlZfKQpipIzCf0AmkxJMNJgHEK0d72BieyaayJWQE9RdlsP9TofYjFOCu9CMXNcLDGYbizqC0YgaJ8orcmodq+mqOHL/afiyFNtPs2+RYZ+29tyU9r8yhZClmZw/eZ0f+ehePUnP1aBMRsT6BpO+YKPADMxk+uxxJPRrK/YYPWsyaKmrEZ+02B0hMbNoCjgicdxKiIzAfv73zai/fiK4FkAmgfd/EVt76Se7AOTLgH7AgDNBXFfvDLGS/3zywFuAWLLjTIyUBfOcCJ4AZ29/wvu+T/n4byK69/LkhPv2ZQMnjeFA3Bak924GOBjO6MfQSZFJ0RWHYN77pla2zDBzXxPrpkHZwn5hxyVr5CIzQo63UgDSmpjkMsJOVSHotjE6tpHEfM3XtFWpxZ14eEWcvDCQ0MgAQqbDqSnsnElrJ6pM44Tlivo+HSlGX5Qm9SCSyRI+AxO8Qzvd2wzwynBrBS1vi5q+ZQuystcbk7ySX3EbYkF5qa2QKoDKDRTQi2LjPpbZR0uR9BLvbtz1sGAY8RcgDpWySmtKxNYxtdQ9ddsXTFpV+6qym1apOn2CQewnDdBDFz9gFZfbkzuVvAi/1C5giL3N1RDzCE8dhS4XBmV8kXwu0qcPr3yD05ImqZxpx7kmQyP/rSEhUy2f
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: P0IK/WsvIqLN5ikMCGucJEoua1H5teiY216N4MoMZCgc1k2Kz6yqyd5VKsgXkygrcPFhge4YGg40tsKpG+uQozp29GuaGNm44R8OQR6aP2sZ9asWJSzvqHIvxG0+/QrS/SPxkkJLlztwXIGewTBEs65udBH+giwTW0JAi4g6Gvucn6IMWekYjnLsPB0Cwq3rnqH0OtxC3vQozOHEXOybu8en3+2MeGMT23PlWi6EVKqHexPoxQD1ZQoB3HuLSJLEgiMe9w9/fC0IRFSUKH/7RTMVyxGw/Z186xw0RvefHcO59BLE4UMPMXw4Y25/mB5zVFrUQ5j3cz6sFVnhax4H8ierrhQoumHRwCnQk9OE0Ug/vWVtUHYR+1ZFgZe3ja4067xAZUI0sieGfE7ZNzZF8q6g1tKv8FGQD4pzgUNStztp3eghBplg4kKQPMBAc9apFFszjAhsG1WofJEeMzufuOLjmoJMb58cw3I1N2omR8InrE4ug8eh083pTUZtSQkxH7CR8DW/zzRifsr/M0ED+/eC5yuiYfux6JbXzKT9WxZ1dEDs8wqVbq52fU62Aq6ky0N4nUAO/Qu6mKBQpCJZm8vD05UOxmwC26hC5WtUOa9mrRR5zG9mrvoLrkqduBQg67C7I7Z8brG9mliwBxAihiEa9X7rvNzspkSu+9B3F5nOZlXy61SSbRdAZexGAoWFnVX15vLmf3wIPycPdnJY7Zj3X5sWnaAkMU8YFARGbP3uW6BHorv6Qhp1Gt+VY+Baexm/AM0yin9ZyRE35Q+uPaMlgl50d/WLKKoZnRi2alaUmY3RnwKDasaaZ61QzBl8MzCRdUE0Y5Jn5VsfiCAtB1/1gIdsp5plVPDLqTKP1jFLrKwinbgMJKFvJDjWxS+P9JgaX8cW9z7kfs+2RUqNPf5UQuNAgv/GcYGyutgF7HTvnni4nkxsDIvGXIjaVqSrPWkPHI/vH4t0ppMRlyzZqZzehHaIwZMXozYeGfkfIaIXXuLLimgb24VZV/gkfGd9UzXHuN9k1RrHjm4yfcTlcDvSFkqDEjw3l3qaM3kYudKcmDpujF2PgNAGiWtO0hcedncPV7Mn8ZNB/LF6ahlKyvIE/CbCaoFdPYahiFiDJIMl4FlipALz1yZcNZcHOB5TvuR16uQkCrP9JH06FDpPPLyWL042UQzmY3MS3ld1soxrF1j5jxeqDRB0bJ7H+ln1jOUf5VWbCJnn7ILPEVcBnOQZ3csjtdABeCaYpdJysTHNpV5ld4d1AkGX9LJ3xOxCXc/HZ8eu5KRcqKnM8VRT9N9hSlNB1BQZxy/i91Mn6CbM38FU06PjByFg/73A91q2KQOHG7/0cEQu76Ds1B9G4r+MBOGGvlB05URpGpfkygVBMWryLmVF9Fcg4iFdFWik+cq0vGitk7k9xzX6YLtM5TcysT/lKwjFpuuhfpqWf7n7DBwEpa4r+9kvQ6mVtXFjdAvps/c9hZhVc2X0LD2MpsbmnYnwgeXg94wKrWBzK4SsGWbVzZ/goCkIWiq+I8VxmX3GjBeFy31m119tliTVtolE9sVwwRD19twooCC7Ix084OzgjIUpm6mRl636P2vB9Hq4Mtq3LVL1Dbp/MlUXkg==
Content-Type: multipart/alternative; boundary="_000_DU2PR02MB10160C927F47A9063CA4BBC0C88FA2DU2PR02MB10160eu_"
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: 5627f265-8989-4ee5-475f-08dc85f99104
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Jun 2024 07:23:30.5984 (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: mQo9yYxIr/cZECP2t0TiMDG9w8WZvRTJKDlvOFClu9z+Qk5jao18ocLKsmRjWuO+CUXirXj1Jcor3wB5B2f1ASKTWVj03DkXLxK2gBasMiI=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AS8PR02MB8614
X-TM-AS-ERS: 10.218.35.129-127.5.254.253
X-TM-AS-SMTP: 1.0 c210cC1vdXQzNjUub3JhbmdlLmNvbQ== bW9oYW1lZC5ib3VjYWRhaXJAb 3JhbmdlLmNvbQ==
X-TMASE-Version: DDEI-5.1-9.1.1004-28434.006
X-TMASE-Result: 10--46.621600-10.000000
X-TMASE-MatchedRID: DzuD87Nox6juYusHgJkgykEe5VjFzwNbWAuSz3ewb23exI8Ovi3T8OcN EBahCbxJAUvTfB6loGQuGaDI5be0fpOJz/rUIvq2fhtdWmd1EkTczjWtUbKcdxdXbAAhHf2vwPH CtmdC1J+G+04VoXgfFPL+Ycc9qBZ/jrVn4cme+w6k8yaNAmZfIY2cB1+t/hleVx7p5wWOE1kz3T JWI0hsNb1qVJYa44rGmlSCGmrTRTDece0aRiX9WnFd5+Cf9M1DFXXsIV9lgAEg2CoIqcAkwdeGA rUj9Nhs5m1tVCx23SjsZfRzVSVqXAiiidfxf4KZoa6XGnaf+WRbgyw/wjxjo/CYKqf93u4XPa5K LkuyyvnRssSdd19BsqBsdwCebZGTX9knSHW8uXUlBKvI9NWIX7wYtb0g7YwtYlFtvHlSBfYEXNC 0UxRHOXEeMGKRcl17XtsGnSgA6qqmVb+ZZJPWPdhQO8CvZj/X/8+V9Cs8XbrfaldUczBqF5Ur1i x318+/KNUhX9UR7YLV27k3uVYos9wYDj426s65UXlp1FHYSPU+hPkY+3Wpe/zxfg6IZlFl1o5UU 9ytRbsB11rlDcR0Vgs5HMdQd07AaDCzqDR7DPYbVzFi+tzvL0WazpgSzbcPFDoS5vLuMRZyMEK6 R2LbV5z1W3Nnt16o0X7fLHhLOBzRnR2eXeSWN3eztDP1UeZHV3BEeuBFxupLi750iAjLL5+xuAe 4xEJ+wfkpxVc9KOVpqyb2Ik3wwvSG/+sPtZVk+Pj9s/c5EzcydMRw9nlzSnTcKhlzcjFhvdIoLE N9rk1bwMs9T+3zjzgcoj/JqpGbGXGu0jdPFGQNsuQOB7UFW0GGpJy/q0pao8WMkQWv6iUojzu/j hRWTQKLL4Z+HVHJdR/G8OvKIg/SBVVc2BozSlkMvWAuahr8RTPcgmZKtSAJAdUDH/0mDSct2Hlc tHlOIvZ1O8ggoYCrEHfaj14Zyf+K1r6Y/VHIA/3R8k/14e0=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
X-TMASE-INERTIA: 0-0;;;;
X-TMASE-XGENCLOUD: d684fe02-d66d-96d3-bac3-8b6cc4fd77fa-0-0-200-0
Message-ID-Hash: 2ZIHHUV7RCOY7YWPOYL4NAF3XFA5WMNQ
X-Message-ID-Hash: 2ZIHHUV7RCOY7YWPOYL4NAF3XFA5WMNQ
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: "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/9PdEFWEX5t8_ohLWMOWgsMuIH7M>
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>
Hi Dhruv, Yes, that would work assuming that we will have a new column to record explicitly the data plane name for each type. Some checks are worth though: Do we foresee cases where the same type can be used by multiple “data planes”? Cheers, Med De : Dhruv Dhody <dd@dhruvdhody.com> Envoyé : jeudi 6 juin 2024 08:59 À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com> Cc : Yingzhen Qu <yingzhen.ietf@gmail.com>; Acee Lindem <acee.ietf@gmail.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, How about this I-D adds some suitable guidance for designated experts (as the IANA registry is under 'Expert Review')? We can also make this I-D update RFC8491. Could that be a way forward? Thanks! Dhruv On Thu, Jun 6, 2024 at 6:05 AM <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> wrote: Hi Yingzhen, Thank you for addressing the sec comment. I trust that you have also fixed the content mismatch between the module and the parent registry points. Thank you also for confirming that there are no such IANA considerations. The narrative text in 9352 does not change the rules set in 8491. I consider that the last comment is still valid and not addressed. Thank you. Cheers, Med De : Yingzhen Qu <yingzhen.ietf@gmail.com<mailto:yingzhen.ietf@gmail.com>> Envoyé : jeudi 6 juin 2024 01:05 À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> Cc : Acee Lindem <acee.ietf@gmail.com<mailto:acee.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]Re: Rtgdir last call review of draft-ietf-mpls-msd-yang-07 Hi Med, You're right, it is not explicitly stated in the IANA consideration section. However you can find "This document only defines one type of MSD: Base MPLS Imposition. " in the abstract of RFC 8491. And the following text is at the beginning of section 4 in RFC 9352 that defines the SRH MSDs: " [RFC8491<https://www.rfc-editor.org/rfc/rfc9352.html#RFC8491>] defines the means to advertise node-/link-specific values for MSDs of various types. Node MSDs are advertised in a sub-TLV of the Router Capability TLV [RFC7981<https://www.rfc-editor.org/rfc/rfc9352.html#RFC7981>] Link MSDs are advertised in a sub-TLV of TLVs 22, 23, 25, 141, 222, and 223.¶<https://www.rfc-editor.org/rfc/rfc9352.html#section-4-1> This document defines the relevant SRv6 MSDs and requests MSD type assignments in the "IGP MSD-Types" registry created by [RFC8491<https://www.rfc-editor.org/rfc/rfc9352.html#RFC8491>] " I've updated the security consideration in version -09. Please let us know whether this addressed your comments. Thanks, Yingzhen On Wed, Jun 5, 2024 at 9:27 AM <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> wrote: 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<mailto:yingzhen.ietf@gmail.com>> Envoyé : mercredi 5 juin 2024 18:02 À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> Cc : Acee Lindem <acee.ietf@gmail.com<mailto:acee.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 : [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. ____________________________________________________________________________________________________________ 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.
- [mpls] Rtgdir last call review of draft-ietf-mpls… Dhruv Dhody via Datatracker
- [mpls] Re: [RTG-DIR]Rtgdir last call review of dr… mohamed.boucadair
- [mpls] Re: [RTG-DIR]Rtgdir last call review of dr… Yingzhen Qu
- [mpls] Re: [RTG-DIR]Rtgdir last call review of dr… mohamed.boucadair
- [mpls] Re: [RTG-DIR]Rtgdir last call review of dr… Acee Lindem
- [mpls] Re: [RTG-DIR]Rtgdir last call review of dr… mohamed.boucadair
- [mpls] Re: [RTG-DIR]Rtgdir last call review of dr… Yingzhen Qu
- [mpls] Re: [RTG-DIR]Re: Rtgdir last call review o… mohamed.boucadair
- [mpls] Re: [RTG-DIR]Re: Rtgdir last call review o… Yingzhen Qu
- [mpls] Re: [RTG-DIR]Re: Rtgdir last call review o… mohamed.boucadair
- [mpls] Re: [RTG-DIR]Re: Rtgdir last call review o… Dhruv Dhody
- [mpls] Re: [RTG-DIR]Re: Rtgdir last call review o… mohamed.boucadair
- [mpls] Re: [RTG-DIR]Re: Rtgdir last call review o… Dhruv Dhody
- [mpls] Re: [Last-Call] Re: [RTG-DIR]Re: Rtgdir la… mohamed.boucadair
- [mpls] Re: [Last-Call] [RTG-DIR]Re: Rtgdir last c… Acee Lindem
- [mpls] Re: [Last-Call] [RTG-DIR]Re: Rtgdir last c… mohamed.boucadair
- [mpls] Re: [Ext] [Last-Call] Re: [RTG-DIR]Re: Rtg… Amanda Baber
- [mpls] Re: [Last-Call] [RTG-DIR]Re: Rtgdir last c… Yingzhen Qu
- [mpls] Re: [Last-Call] [RTG-DIR]Re: Rtgdir last c… mohamed.boucadair
- [mpls] Re: [RTG-DIR]Re: Rtgdir last call review o… Mahesh Jethanandani
- [mpls] Re: Rtgdir last call review of draft-ietf-… Yingzhen Qu
- [mpls] Re: [Last-Call] Re: Rtgdir last call revie… Dhruv Dhody