Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-ippm-stamp-on-lag-06> for your review
"Rakesh Gandhi (rgandhi)" <rgandhi@cisco.com> Wed, 24 January 2024 18:17 UTC
Return-Path: <rgandhi@cisco.com>
X-Original-To: auth48archive@ietfa.amsl.com
Delivered-To: auth48archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABD49C14CEFC; Wed, 24 Jan 2024 10:17:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.603
X-Spam-Level:
X-Spam-Status: No, score=-9.603 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 N_8WjkB4IvDP; Wed, 24 Jan 2024 10:17:09 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (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 6424BC14CEFA; Wed, 24 Jan 2024 10:17:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.com; i=@cisco.com; l=80966; q=dns/txt; s=iport; t=1706120229; x=1707329829; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Z/T3tUk9m9H0t2wP97gPWZ78LPvxaeVuCo3ltrHiq84=; b=LHOBKrT+N3fi5WmoONQTrhari44idnPWaRnJlIjKE9albYN/ia0A3GyX Ahlz7xaowa8IEj+ATkAJClP1fMzU+GNp6cLRVpgv2Q+fqkCqFQPLhb3bv uxBknGSCezu94bLAdk704FU0AgWWTMRjbmBpj4RdjcYLKQBOhc4uOSAt/ 4=;
X-CSE-ConnectionGUID: FbjDxlbATgKPFDR1LVozpg==
X-CSE-MsgGUID: 788oGarlTmajjJhmYAPGWA==
X-IPAS-Result: A0ABAABSU7FlmJBdJa1aGQEBAQEBAQEBAQEBAQEBAQEBARIBAQEBAQEBAQEBAQFlgRYEAQEBAQELAYE1MSooegKBF0gxhCGDTAOETl+GRYIiA4J+iGCFYoxEFIERA1YPAQEBDQEBOwkEAQGFBgIWNAEEAQiGcQImNAkOAQIEAQEBAQMCAwEBAQEBAQEBBgEBBQEBAQIBBwUUAQEBAQEBAQEeGQUOECeFbA0IAQ4QgX2EIQEBAQEBAhIICQRHCxACAQgOAgEDAQEBASABBgMCAgIeERQJCAIEAQ0FCBpaggQBghcUAzEDARAGqhABgUACiih6fzOBAYIWBYFOQa4MDYJVgUgBh30EGgFoZgEBgWyCD4RXJxuBSUSBFUKCaD6CH0ICAQGBIQMBBAESASMVCRaDJTmCLwSBFSNcgjBqKYEYglUCb3ABhCACJYFdQwF3FIUAVHkjA10gCARcDxsQHjcREBMNAwhuHQIxPAMFAwQyChIMCyEFE0IDQAZJCwMCGgUDAwSBMAUNGgIQGgYMJgMDEkkCEBQDOAMDBgMKMTBVQQxQA2UfMgkHNQsEDBoCGxsNJyMCLEADERICFgMkFgQ2EQkLJgMqBjcCEgwGBgldJhYJBCUDCAQDVAMjdBEDBAoDFAcLB3iCEIE+BBNKEIEcA0QdQAMLbT0UIQYOGwUEgTYFlXZ5AYFMEBVMKxMmBA0aAQofAQFOAkAIRgEjAQULASYFKY0HhTYPEgg4gl8BSYsaogoKQHAKhBGMBo4XgQcBgmyDPBeEBUyMKwONOIgggl9kmFQggjGHF4QFg32ROgQShQoCBAIEBQIOAQEGgWM6a3BwFRohgjMBMwlJGQ+OLA0JgQwBCB2HOoooATx2AgEBNwIHAQoBAQMJhkgFgiEbCwZtAV8BAQ
IronPort-PHdr: A9a23:CyLXHB2OPffEgKJZsmDPYFBlVkEcU/3cJAUZ7N8gk71RN/jl9JX5N 0uZ7vJo3xfFXoTevupNkPGe87vhVmoJ/YubvTgcfYZNWR4IhYRenwEpDMOfT0yuBPXrdCc9W s9FUQwt5Gm1ZHBcA922fFjOuju35D8WFA/4MF9vKe3zFo7Tp8+2zOu1vZbUZlYAiD+0e7gnN Byttk2RrpwMjIlvIbp5xhrS931PfekXjW89LlOIlBG67cC1lKM=
IronPort-Data: A9a23:dM/P7qOeiOXjskfvrR2Cl8FynXyQoLVcMsEvi/4bfWQNrUok0jEPy zEZCG6FO6yNZmPzet8jYd+09BsB6p+GztcxGnM5pCpnJ55oRWUpJjg4wmPYZX76whjrFRo/h ykmQoCdaphyFjmF/kvF3oHJ9RFUzbuPSqf3FNnKMyVwQR4MYCo6gHqPocZh6mJTqYb/W17lV e/a+ZWFZAf8gWIsawr41orawP9RlKWq0N8nlgRWicBj5Df2i3QTBZQDEqC9R1OQrl58R7PSq 07rldlVz0uBl/sfIorNfoXTLiXmdoXv0T2m0RK6bUQNbi9q/UTe2o5jXBYVhNw+Zz+hx7idw /0V3XC8pJtA0qDkwIwgvxdk/y5WE6dE1K/DK1GDvu+r4WH8Kl/SxOd2AxRjVWEY0r4f7WBm7 /cULnUGaQqOwrLwy7OgQe4qjcMmRCXpFNpA4Tc7kneIVrB/Hcyrr6bivbe02B8qiclIEfbfT 8EYcjFoKh/HZnWjP39OV8xlwbjz2CWXnztw9wLFooU++WzvyQVz0prtNev8QvO1bJAA9qqfj jmbpzuiWE5y2Mak4TOY7nLw1ubVliP6Ro86DrOzs/NmgUGU3CoUEhJ+fUG1qry0hk+iXMh3M UIfvycirLQ17gqsVNaVYvGjiGSPshhZUN1KHqhqrgqM0aHTpQ2eAwDoUwKtdvQIvs0aVTgg/ 2OGvOvHKQY2lIOSW2qSo+L8QSyJBQAZKmoLZCkhRAQD4sX+rIxbsv4pZosyeEJSpoClcQwc0 wy3QD4Ca6L/ZPPnOo2h9lzBxjmrvJWMHkg+5x7cWSSu6QYRiG+Zi26AtwSzARVoddrxory9U J4swJj2AAcmVs7lqcB1aL9RdIxFHt7cWNEmvXZhHoM66xOm8GO5cIZb7VlWfRgxbJ5fJWG4O RGI4Gu9AaO/2lP0NcebhKrsWqwXIVTIS7wJq9iNN4UePMItHON51Hg2Ohf4M5/RfLgEyvxnZ szBLq5A/F4RCL9sy3KtVvwB3LowjiE4ziW7eHwI50rP7FZqX1bMEe1tGALXNogRtfrYyC2Lq Iw3H5XRlH1ivBjWP3O/HXg7dw5adBDWxPne9qRqSwJ0ClA4Qj95VaONkOhJlk4Mt/09q9okN 0qVAydw4FH+nnbAbw6NbxhehHnHB/6TcVpT0fQQAGuV
IronPort-HdrOrdr: A9a23:AHw2/qNKYo1YgMBcT4j255DYdb4zR+YMi2TDiHoBKiC9I/b5qy nxppUmPEfP+UgssREb9expOMG7MBXhHO1OkPgs1NaZLUXbUQSTXftfBOfZslnd8mjFh5FgPM RbAudD4b/LfCVHZK/BiWHSfadDsby6GeKT9JvjJhxWPHhXgtRbnnxE43GgYzVLrWd9dP0EPa vZzPBq4xCnfnMaZNm6AH4qY8jvzuegqLvWJTQ9K1oC8gehsROEgYSWL/Gf5HgjegIK5Y1n3X nOkgT/6Knmmeq80AXg22ja6IkTsMf9y/NYbfb8y/Q9G3HJsEKFdY5hU7qNsHQeu+e08msnl9 HKvlMJI9lz0XXMZWu4yCGdmzUIkQxeqEMK+2XoxEcLkvaJAA7SzPAxwr6xRyGpqXbIeusMlp 6jkVjp7qa/Rimw7BgVr+K4JC2C0HDE70bLVYUo/idiuUx0Us4IkaUPuExSC5sOByT89cQuF/ RvFtjV4LJMfUqddG2xhBgl/DWAZAV7Iv69eDlLhuWFlzxN2HxpxUoRw8IS2n8G6ZImUpFBo+ DJKL5hmr1CRtIfKfsVPpZNfeKnTmjWBR7cOmObJlrqUKkBJnLWspbypLE4/vujdpAExIY73J 7BTFRbv2gvfF+GM7zF4LRbthTWBGmtVzXkzc9To5B/p73nXbLudTaOTVg/+vHQ1cn3wverLM pbFKgmd8MLd1Gea7qh9zeOLqVvFQ==
X-Talos-CUID: 9a23:7lPOPG+XjmFx+W6toh2Vv2AeGOw1dnf08HjzG2GUMz9NdrqHUVDFrQ==
X-Talos-MUID: 9a23:q4DRRwXj0GjzG4vq/GC81DZNPd1s36GnCkIvkZA3kvGrCgUlbg==
X-IronPort-Anti-Spam-Filtered: true
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-6.cisco.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Jan 2024 18:17:08 +0000
Received: from rcdn-opgw-4.cisco.com (rcdn-opgw-4.cisco.com [72.163.7.165]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id 40OIH7iS004553 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 24 Jan 2024 18:17:07 GMT
X-CSE-ConnectionGUID: LqkQNphxSjWHXCa5/3XeaQ==
X-CSE-MsgGUID: Zq1AOzCtSg6FsBMPkHG2zg==
Authentication-Results: rcdn-opgw-4.cisco.com; dkim=pass (signature verified) header.i=@cisco.com; spf=Pass smtp.mailfrom=rgandhi@cisco.com; dmarc=pass (p=reject dis=none) d=cisco.com
X-IronPort-AV: E=Sophos;i="6.05,216,1701129600"; d="scan'208,217";a="25388649"
Received: from mail-sn1nam02lp2041.outbound.protection.outlook.com (HELO NAM02-SN1-obe.outbound.protection.outlook.com) ([104.47.57.41]) by rcdn-opgw-4.cisco.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Jan 2024 18:17:07 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=B+X/ggk2uOk79g/a/8zn8Tbem4+VAAyQ34Z36DoQWkdPkXw/Ita+vjEk8ZUHuwdlNEog93gbOEpWzzod/TH+BwcXTJikBilCMSmXE6kfcdG6SGvzgNHBvdKWszW3T+VilvkZF2v5aAmAOvujvEspeHtMqCpgyN6+ffjDYDzioS71F0lY4q4ff1VHofez0NPdmeEtP21T9myd6v9BO40Yxo+glzUq+nmDlQBmCn8rUtENeZfIgYo/LgT+Id3FW7a35Dj++m9rAWcatFJMChi923+ruYj94ZK/pCDj5KZA7rJe7VvOMp+9sblPrY/t4vz1MTwtS+bgyjYze1P2/0RdFQ==
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=Z/T3tUk9m9H0t2wP97gPWZ78LPvxaeVuCo3ltrHiq84=; b=lSN+LnA1Zn7V0/+Wrz9UMK2xWXXDM5qsYaPZVIs8zxrFc3cTpuQjuXfz3Okf1Ec/aCRAuCbIT1/92HWkGUUoNSIA6qBXbTJHXFD7TL7qCtl8sECKr/eh5k08BLfYnEQY5mNyXExYUJAlLtEtBk/rm3EU5R4XVKoRa6NChZjieUw9wTM5EMzJvH6qN+67dJotP0adGAoyUZalpOTqgcg3Q5frderEsTpQRf+H1Fx71j7DO4A1A+vz7dMyeAANoDT/dbIR7pbqVM+wY8TwXhlY5ZpMomRwbuUTzpGh2+YV8Ko7nCzZ76N9501na8efwDbHKraea2xwmeiXTVXOXZ1foA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
Received: from BL3PR11MB5731.namprd11.prod.outlook.com (2603:10b6:208:352::15) by BL3PR11MB5699.namprd11.prod.outlook.com (2603:10b6:208:33e::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7228.22; Wed, 24 Jan 2024 18:17:03 +0000
Received: from BL3PR11MB5731.namprd11.prod.outlook.com ([fe80::4f80:1043:5bf1:8508]) by BL3PR11MB5731.namprd11.prod.outlook.com ([fe80::4f80:1043:5bf1:8508%4]) with mapi id 15.20.7228.022; Wed, 24 Jan 2024 18:17:03 +0000
From: "Rakesh Gandhi (rgandhi)" <rgandhi@cisco.com>
To: Jean Mahoney <jmahoney@amsl.com>, "li_zhenqiang@hotmail.com" <li_zhenqiang@hotmail.com>, Tianran Zhou <zhoutianran@huawei.com>, Greg Mirsky <gregimirsky@gmail.com>, "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org>
CC: "guo.jun2@zte.com.cn" <guo.jun2@zte.com.cn>, "ippm-ads@ietf.org" <ippm-ads@ietf.org>, IPPM Chairs <ippm-chairs@ietf.org>, "marcus.ihlar" <marcus.ihlar@ericsson.com>, Martin Duke <martin.h.duke@gmail.com>, "auth48archive@rfc-editor.org" <auth48archive@rfc-editor.org>, "Zhukeyi (Kaiyin, Enterprise NE)" <zhukeyi@huawei.com>
Thread-Topic: AUTH48: RFC-to-be 9534 <draft-ietf-ippm-stamp-on-lag-06> for your review
Thread-Index: AQHaTtkCcsVKVOHmUUyZBMhD0qdYfrDpRSKn
Date: Wed, 24 Jan 2024 18:17:03 +0000
Message-ID: <BL3PR11MB5731AA5861FE5D91699D0228BF7B2@BL3PR11MB5731.namprd11.prod.outlook.com>
References: <20240123184451.AC7D6E7C65@rfcpa.amsl.com> <CA+RyBmXffX7SKnicX7w4nbW0U1s21j6pH3qyqY0pSDQqSCS_QA@mail.gmail.com> <24a6d95384c140d69fc4e47db2b5a9bd@huawei.com> <SY4P282MB2933271C11D934BD2085D365FC7B2@SY4P282MB2933.AUSP282.PROD.OUTLOOK.COM> <d560add1-1edf-4201-a88b-0d4cebab8fea@amsl.com>
In-Reply-To: <d560add1-1edf-4201-a88b-0d4cebab8fea@amsl.com>
Accept-Language: en-CA, en-US
Content-Language: en-CA
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: BL3PR11MB5731:EE_|BL3PR11MB5699:EE_
x-ms-office365-filtering-correlation-id: c4b49316-9b4f-4d68-8e6b-08dc1d08aa4c
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: qe3g5zGgcTBTJeyUIVJTWMclEpk6dCJu0uc3JOkKYdJpIB95Oz9YulyI0UjUhjXDanzFBvTqNRXmTDemLd4zL7lWGiLDoD+mLBxl5e0lqpWNQPC5ukV8bs/1T3p+BX5SKlWS+2V+2cOUaFLNBMy/ASJbg8wqF+dFYI74MqL9XEYJrscgia2Kc82iE7aXUgvAucv+9f8xEtJ6137bAG5gTudYx7xj35fy5Q0nAnoCU71+D3n6iwUOe9rxKNxvrbWzZi8z7fzF/vT0lDRDVO8uuQftEyQzdsYSd2I8wAyZbU2k6fVVv5ewa/sWUYi6AaS+9XAE+8u4KeR2u89rui0B3QiKIR3sSy1egFTVdZjdIhFqN0B981KeHP7jEK8wSd9x8rPWkKv1Mf+T+kjVz1kv8nh9lbxKcqHLeV7viKPCWH86LKkj1/WXvFEGqjga5E6BXJq/KS8XiBaCOvpxB03MAthDPYufyOaLqsiib2sLRKrk3nNHkypXgcEccg70m0obYc00siyPmRxLrAK36fvF/mQN8Ecu5yv5uONEt2U7zk1yyb42b+E6QRj4Z7Pqkd3NWQzcBg6dkOQfXhaAXYXy+8VICOl2Gz6JiN5RVbsvCOMrmsBLZ/dEWZl4TMsTE9GjERq/Ey+RQLHrF6B/aZhJwA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BL3PR11MB5731.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230031)(366004)(346002)(396003)(39860400002)(136003)(376002)(230922051799003)(1800799012)(64100799003)(186009)(451199024)(110136005)(91956017)(66476007)(316002)(66556008)(66946007)(64756008)(53546011)(26005)(66446008)(54906003)(9686003)(122000001)(478600001)(966005)(55016003)(45080400002)(38100700002)(166002)(6506007)(7696005)(71200400001)(76116006)(8936002)(21615005)(4326008)(8676002)(52536014)(5660300002)(7416002)(83380400001)(41300700001)(30864003)(86362001)(2906002)(33656002)(38070700009); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: AlW/VOPy6v91pkAO6nn9umqpvarcrDbwqFwSajdZPHV1PNyU7SMiV9je/cp1of8uXJ/ns6eNA+kP/Jf+s/lbLGRMiAQNWGmGb2uS9osU8d3srEXdw48VhkU+dFaIEo2tVGaumiWmdKNWK22SBtAUZcrdqvhZsS5D36ejx8sotkDFmo3s+4ur2xk+iX8kgVne4HPgR4f3fC7DfoJvjnbE6hjkfO1VXLCawbUhzfDtbGMNIBnNHZRBDRf3FNcnalR8y/nHg6svg3AgjFMN6W/Qiln4+EkIGWaoxEiNkq5DhOIa4X63ijDPMs7JY/hHT6ypNjM9E7KAOEBhXEB52/dO6hxwILoOgvO0hoE1+r5xjZXcHCn9h1PjrjBNjj4K+9FBjL59FEaBgWH4UMJYKdKL1WLIIodHz8snWpmxUxhDBN/hfeLVrBlNqi95zTLH0EodOSUmGFJZyEgKI3ncjr/raXIr5q5Dz1S5AH4NJIQT0pPnhvq+EXCtRXcacpOnSXNS7CTm9FYLxptrC1wyta7jamenj1b+YlviAl79F3zmgaazUmy+lZcPU+MZ4Kx8Zfl0pNI80xnk+B4nja/skPBbPuNz6XZAIjUp8vtOt4P6fnIGPAt+RkrhvZzlwdtjc678DiHESUw3ghWExyqARlun0uhRMdlXnNBcDJ3GV1cwSxwfBTTaUwWQh+ZRqKP6zg9kYPoNAVpIdymPa3qOAJOYRr5nJgyWDkyc0epapm7CSxUg0qHbhcD+dmkLPyzgnYqpDgo85fWjv2XjmNREuniuIW1BQ+zEM/uVboDOTU310D5QPbq9eKfKwugxedIeLO2kNZZJbepnbP4yXeNS098g85wFyvMl8+6tsKfxpFOK6bD15j11T6W628KTrraXIRU1nHIQepwI+wkYLLDylVRe7brcTDn0bGnnLOQ+AX0ObSJIzusrxqCfPRjfn36PDxSPVjxemdsUXA2hmiU5SgL70UZRj+4QovhybLoMuAg2XAY16Lbd7fTQ5TA6OOKjptAn6NoRyc69o6s9RguT9EMLMRn9BZzumhaxspcKV1gowhfCuCAap4Tvhl3vNk/G0aYUB04oU7t2JsFMOA9DKySH+9G1Fow84htMf2RuNZFFMP9WTmF5Tip0BYJ0g/TWF4TCIBlRfmtiyehG0S9581qaW7Y4BNuaahtmxPuVlKtQlYFduTLKv15o+Bi2nS4WyOwbgKhCIFkRZ1HYAhFFfh+/u9kVpz9FY5q8vC/UxcRuuu+znQS56Yugp8Dm4yLBTkLTq/W0xQHzPxkHqgyfKcgybS2lkiiiFBIfhZsJkSptikdpy3GxaurX0iGx5SrLmunxBIFXvcCIA3CQwJEQH5iNaVwz1U0ZXT9rBGda2fFWOQy955+hYrh5xQZ2E5sDGEeXg7VCBuxHoXTj0qrDkIOvb0Zs0lN/dZTRJQjxquGnG7jzMB4UQCAHz0bJ6sCE/DUJZkmM85/hIvZ8WYpBV+2atrjCyiu/VUlyqdhgnUvBi7Ygz6dzqv8i9Ua6BcscsuPAGsWo5aMTQrF23PWEmxqKlBt+5xWr09n+XdlSAevl61bNPPMvG4IbW2Ht3vBUbee6Uew46wMpImFHqgqzt5yWCQ==
Content-Type: multipart/alternative; boundary="_000_BL3PR11MB5731AA5861FE5D91699D0228BF7B2BL3PR11MB5731namp_"
MIME-Version: 1.0
X-OriginatorOrg: cisco.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BL3PR11MB5731.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c4b49316-9b4f-4d68-8e6b-08dc1d08aa4c
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Jan 2024 18:17:03.3694 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: qruJ77mzgVuct2bpAbkOS1abgKGbk8CRE4mv1kav0eDYNv/eXTVda8cdu02JxiS3SjnGs6y1z9olcxKUQaSIag==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL3PR11MB5699
X-Outbound-SMTP-Client: 72.163.7.165, rcdn-opgw-4.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/6goYy_sk9MbaeJ2veeijZ2ibdXs>
Subject: Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-ippm-stamp-on-lag-06> for your review
X-BeenThere: auth48archive@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Archiving AUTH48 exchanges between the RFC Production Center, the authors, and other related parties" <auth48archive.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/auth48archive/>
List-Post: <mailto:auth48archive@rfc-editor.org>
List-Help: <mailto:auth48archive-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jan 2024 18:17:14 -0000
Thanks Jean and authors for the review and edits. One minor comment: Could you please update my affiliate to - Cisco Systems, Inc. Thanks, Rakesh From: Jean Mahoney <jmahoney@amsl.com> Date: Wednesday, January 24, 2024 at 10:21 AM To: li_zhenqiang@hotmail.com <li_zhenqiang@hotmail.com>, Tianran Zhou <zhoutianran@huawei.com>, Greg Mirsky <gregimirsky@gmail.com>, rfc-editor@rfc-editor.org <rfc-editor@rfc-editor.org> Cc: guo.jun2@zte.com.cn <guo.jun2@zte.com.cn>, Rakesh Gandhi (rgandhi) <rgandhi@cisco.com>, ippm-ads@ietf.org <ippm-ads@ietf.org>, IPPM Chairs <ippm-chairs@ietf.org>, marcus.ihlar <marcus.ihlar@ericsson.com>, Martin Duke <martin.h.duke@gmail.com>, auth48archive@rfc-editor.org <auth48archive@rfc-editor.org>, Zhukeyi (Kaiyin, Enterprise NE) <zhukeyi@huawei.com> Subject: Re: AUTH48: RFC-to-be 9534 <draft-ietf-ippm-stamp-on-lag-06> for your review Zhenqiang, Greg, Tianran, Thank you for your quick responses! We have updated the document based on your feedback: https://www.rfc-editor.org/in-notes/authors/rfc9534-lastrfcdiff.html Zhenqiang, we have noted your approval on the AUTH48 status page: https://www.rfc-editor.org/auth48/rfc9534 The files have been posted here: https://www.rfc-editor.org/authors/rfc9534.txt https://www.rfc-editor.org/authors/rfc9534.pdf https://www.rfc-editor.org/authors/rfc9534.html https://www.rfc-editor.org/authors/rfc9534.xml https://www.rfc-editor.org/authors/rfc9534-diff.html (all changes) https://www.rfc-editor.org/authors/rfc9534-rfcdiff.html (all changes side by side) https://www.rfc-editor.org/authors/rfc9534-auth48diff.html https://www.rfc-editor.org/authors/rfc9534-alt-diff.html We will await further word from you and your coauthors regarding other AUTH48 changes and/or approval. Best regards, RFC Editor/jm On 1/23/24 10:13 PM, li_zhenqiang@hotmail.com wrote: > Hello Editor and coauthors, > > I have no objection on Greg's and Tianran's suggestion. > > ------------------------------------------------------------------------ > Best Regards, > Zhenqiang Li > China Mobile > li_zhenqiang@hotmail.com > > *From:* Tianran Zhou <mailto:zhoutianran@huawei.com> > *Date:* 2024-01-24 11:08 > *To:* Greg Mirsky <mailto:gregimirsky@gmail.com>; > rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org> > *CC:* li_zhenqiang@hotmail.com <mailto:li_zhenqiang@hotmail.com>; > guo.jun2@zte.com.cn <mailto:guo.jun2@zte.com.cn>; rgandhi@cisco.com > <mailto:rgandhi@cisco.com>; ippm-ads@ietf.org > <mailto:ippm-ads@ietf.org>; ippm-chairs@ietf.org > <mailto:ippm-chairs@ietf.org>; marcus.ihlar@ericsson.com > <mailto:marcus.ihlar@ericsson.com>; martin.h.duke@gmail.com > <mailto:martin.h.duke@gmail.com>; auth48archive@rfc-editor.org > <mailto:auth48archive@rfc-editor.org>; Zhukeyi(Kaiyin,Datacom > Standard&Patent) <mailto:zhukeyi@huawei.com> > *Subject:* RE: AUTH48: RFC-to-be 9534 > <draft-ietf-ippm-stamp-on-lag-06> for your review > > Hi Editor and Greg, > > I prefer Greg’s change on this. > > GIM>> Thank you for the question and proposed update. I agree that > the first occurence of "tuple" must be singular. The second, as I > think of how it works, is about modifying some elements of the > 5-tuple. I would propose the following update: > > OLD TEXT: > > One STAMP test session over the LAG can measure the performance of a > member link with fixed five tuples, or it can measure an average of > some or all member links of the LAG by varying the five tuples. > > NEW TEXT: > > A STAMP test session over the LAG can be used to measure the > performance of a > > member link using specially-constructed 5-tuple. The session can > be used to measure an average of > > some or all member links of the LAG by varying one or more > elements of that 5-tuple. > > Cheers, > > Tianran > > *From:*Greg Mirsky [mailto:gregimirsky@gmail.com] > *Sent:* Wednesday, January 24, 2024 10:53 AM > *To:* rfc-editor@rfc-editor.org > *Cc:* li_zhenqiang@hotmail.com; Tianran Zhou > <zhoutianran@huawei.com>; guo.jun2@zte.com.cn; rgandhi@cisco.com; > ippm-ads@ietf.org; ippm-chairs@ietf.org; marcus.ihlar@ericsson.com; > martin.h.duke@gmail.com; auth48archive@rfc-editor.org > *Subject:* Re: AUTH48: RFC-to-be 9534 > <draft-ietf-ippm-stamp-on-lag-06> for your review > > Dear RFC Editor, > > thank you for your thoughtful consideration of the document and > helpful suggestions to improve it. Please find my responses to your > questions below tagged by GIM>>. Please let me know if there are any > further questions or actions I should take. > > Regards, > > Greg > > On Tue, Jan 23, 2024 at 10:44 AM <rfc-editor@rfc-editor.org > <mailto:rfc-editor@rfc-editor.org>> wrote: > > Authors, > > While reviewing this document during AUTH48, please resolve (as > necessary) the following questions, which are also in the XML file. > > 1) <!-- [rfced] We have updated the title of the document by > expanding LAG. Please let us know if any changes are necessary. > > Original: > Simple Two-Way Active Measurement Protocol Extensions for > Performance > Measurement on LAG > > Current: > Simple Two-Way Active Measurement Protocol Extensions for > Performance > Measurement on a Link Aggregation Group > > GIM>> I agree with the proposed text. > > > --> > > > 2) <!-- [rfced] Please insert any keywords (beyond those that > appear in > the title) for use on https://www.rfc-editor.org/search > <https://www.rfc-editor.org/search>. --> > > > 3) <!-- [rfced] Section 1. We would like to clarify the use of > "tuple" in the sentence below: > > Current: > > One STAMP test session over the LAG can measure the > performance of a > member link with fixed five tuples, or it can measure an > average of > some or all member links of the LAG by varying the five tuples. > > Perhaps (updating "five tuple" to "5-tuple", which is more > commonly used; making the first use of "tuple" singular; and > changing "varying the five tuples" to "specifying their 5-tuples"): > > One STAMP test session over the LAG can measure the > performance of a > member link using its fixed 5-tuple, or it can measure an > average of > some or all member links of the LAG by specifying their > 5-tuples. > > GIM>> Thank you for the question and proposed update. I agree that > the first occurence of "tuple" must be singular. The second, as I > think of how it works, is about modifying some elements of the > 5-tuple. I would propose the following update: > > OLD TEXT: > > One STAMP test session over the LAG can measure the performance of a > member link with fixed five tuples, or it can measure an average of > some or all member links of the LAG by varying the five tuples. > > NEW TEXT: > > A STAMP test session over the LAG can be used to measure the > performance of a > > member link using specially-constructed 5-tuple. The session can > be used to measure an average of > > some or all member links of the LAG by varying one or more > elements of that 5-tuple. > > --> > > > 4) <!-- [rfced] [IEEE802.1AX] 802.1AX-2008 has been superseded > by 802.1AX-2014. Would you like to update the reference? > > Current: > [IEEE802.1AX] > IEEE, "IEEE Standard for Local and metropolitan area > networks - Link Aggregation", IEEE Std 802.1AX-2008, > DOI 10.1109/IEEESTD.2008.4668665, November 2008, > <https://ieeexplore.ieee.org/document/4668665 > <https://ieeexplore.ieee.org/document/4668665>>. > > GIM>> Yes, please update the reference to the latest. > > --> > > > 5) <!-- [rfced] Please review the "Inclusive Language" portion > of the online Style Guide > <https://www.rfc-editor.org/styleguide/part2/#inclusive_language > <https://www.rfc-editor.org/styleguide/part2/#inclusive_language>> > and let us know if any changes are needed. > > Note that our script did not flag any words in particular, but > this should > still be reviewed as a best practice. > > GIM>> I don't find any updates > > --> > > > 6) <!-- [rfced] FYI - We have added expansions for abbreviations > upon first use per Section 3.6 of RFC 7322 ("RFC Style Guide"). > Please review each > expansion in the document carefully to ensure correctness. > > GIM>> All expansions are correct. > > --> > > > Thank you. > > RFC Editor/jm > > On 1/23/24 12:41 PM, rfc-editor@rfc-editor.org > <mailto:rfc-editor@rfc-editor.org> wrote: > > *****IMPORTANT***** > > Updated 2024/01/23 > > RFC Author(s): > -------------- > > Instructions for Completing AUTH48 > > Your document has now entered AUTH48. Once it has been reviewed > and > approved by you and all coauthors, it will be published as an RFC. > If an author is no longer available, there are several remedies > available as listed in the FAQ (https://www.rfc-editor.org/faq/ > <https://www.rfc-editor.org/faq/>). > > You and you coauthors are responsible for engaging other parties > (e.g., Contributors or Working Group) as necessary before providing > your approval. > > Planning your review > --------------------- > > Please review the following aspects of your document: > > * RFC Editor questions > > Please review and resolve any questions raised by the RFC > Editor > that have been included in the XML file as comments marked as > follows: > > <!-- [rfced] ... --> > > These questions will also be sent in a subsequent email. > > * Changes submitted by coauthors > > Please ensure that you review any changes submitted by your > coauthors. We assume that if you do not speak up that you > agree to changes submitted by your coauthors. > > * Content > > Please review the full content of the document, as this cannot > change once the RFC is published. Please pay particular > attention to: > - IANA considerations updates (if applicable) > - contact information > - references > > * Copyright notices and legends > > Please review the copyright notice and legends as defined in > RFC 5378 and the Trust Legal Provisions > (TLP – https://trustee.ietf.org/license-info/ > <https://trustee.ietf.org/license-info/>). > > * Semantic markup > > Please review the markup in the XML file to ensure that > elements of > content are correctly tagged. For example, ensure that > <sourcecode> > and <artwork> are set correctly. See details at > <https://authors.ietf.org/rfcxml-vocabulary > <https://authors.ietf.org/rfcxml-vocabulary>>. > > * Formatted output > > Please review the PDF, HTML, and TXT files to ensure that the > formatted output, as generated from the markup in the XML > file, is > reasonable. Please note that the TXT will have formatting > limitations compared to the PDF and HTML. > > > Submitting changes > ------------------ > > To submit changes, please reply to this email using ‘REPLY ALL’ > as all > the parties CCed on this message need to see your changes. The > parties > include: > > * your coauthors > > * rfc-editor@rfc-editor.org > <mailto:rfc-editor@rfc-editor.org> (the RPC team) > > * other document participants, depending on the stream (e.g., > IETF Stream participants are your working group chairs, the > responsible ADs, and the document shepherd). > > * auth48archive@rfc-editor.org > <mailto:auth48archive@rfc-editor.org>, which is a new archival > mailing list > to preserve AUTH48 conversations; it is not an active > discussion > list: > > * More info: > https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc <https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc> > > * The archive itself: > https://mailarchive.ietf.org/arch/browse/auth48archive/ > <https://mailarchive.ietf.org/arch/browse/auth48archive/> > > * Note: If only absolutely necessary, you may temporarily > opt out > of the archiving of messages (e.g., to discuss a > sensitive matter). > If needed, please add a note at the top of the message > that you > have dropped the address. When the discussion is > concluded, > auth48archive@rfc-editor.org > <mailto:auth48archive@rfc-editor.org> will be re-added to the CC > list and > its addition will be noted at the top of the message. > > You may submit your changes in one of two ways: > > An update to the provided XML file > — OR — > An explicit list of changes in this format > > Section # (or indicate Global) > > OLD: > old text > > NEW: > new text > > You do not need to reply with both an updated XML file and an > explicit > list of changes, as either form is sufficient. > > We will ask a stream manager to review and approve any changes > that seem > beyond editorial in nature, e.g., addition of new text, deletion > of text, > and technical changes. Information about stream managers can be > found in > the FAQ. Editorial changes do not require approval from a > stream manager. > > > Approving for publication > -------------------------- > > To approve your RFC for publication, please reply to this email > stating > that you approve this RFC for publication. Please use ‘REPLY ALL’, > as all the parties CCed on this message need to see your approval. > > > Files > ----- > > The files are available here: > https://www.rfc-editor.org/authors/rfc9534.xml > <https://www.rfc-editor.org/authors/rfc9534.xml> > https://www.rfc-editor.org/authors/rfc9534.html > <https://www.rfc-editor.org/authors/rfc9534.html> > https://www.rfc-editor.org/authors/rfc9534.pdf > <https://www.rfc-editor.org/authors/rfc9534.pdf> > https://www.rfc-editor.org/authors/rfc9534.txt > <https://www.rfc-editor.org/authors/rfc9534.txt> > > Diff file of the text: > https://www.rfc-editor.org/authors/rfc9534-diff.html > <https://www.rfc-editor.org/authors/rfc9534-diff.html> > https://www.rfc-editor.org/authors/rfc9534-rfcdiff.html > <https://www.rfc-editor.org/authors/rfc9534-rfcdiff.html> (side > by side) > > For your convenience, we have also created an alt-diff file that > will > allow you to more easily view changes where text has been deleted or > moved: > http://www.rfc-editor.org/authors/rfc9534-alt-diff.html > <http://www.rfc-editor.org/authors/rfc9534-alt-diff.html> > > Diff of the XML: > https://www.rfc-editor.org/authors/rfc9534-xmldiff1.html > <https://www.rfc-editor.org/authors/rfc9534-xmldiff1.html> > > The following files are provided to facilitate creation of your own > diff files of the XML. > > Initial XMLv3 created using XMLv2 as input: > https://www.rfc-editor.org/authors/rfc9534.original.v2v3.xml > <https://www.rfc-editor.org/authors/rfc9534.original.v2v3.xml> > > XMLv3 file that is a best effort to capture v3-related format > updates > only: > https://www.rfc-editor.org/authors/rfc9534.form.xml > <https://www.rfc-editor.org/authors/rfc9534.form.xml> > > > Tracking progress > ----------------- > > The details of the AUTH48 status of your document are here: > https://www.rfc-editor.org/auth48/rfc9534 > <https://www.rfc-editor.org/auth48/rfc9534> > > Please let us know if you have any questions. > > Thank you for your cooperation, > > RFC Editor > > -------------------------------------- > RFC9534 (draft-ietf-ippm-stamp-on-lag-06) > > Title : Simple Two-Way Active Measurement Protocol > Extensions for Performance Measurement on LAG > Author(s) : Z. Li, T. Zhou, J. Guo, G. Mirsky, R. Gandhi > WG Chair(s) : Marcus Ihlar, Tommy Pauly > Area Director(s) : Martin Duke, Zaheduzzaman Sarker >
- [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-ippm-… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-i… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-i… Tianran Zhou
- Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-i… Greg Mirsky
- Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-i… Tianran Zhou
- Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-i… li_zhenqiang@hotmail.com
- Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-i… li_zhenqiang@hotmail.com
- Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-i… Jean Mahoney
- Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-i… Greg Mirsky
- Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-i… Rakesh Gandhi (rgandhi)
- Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-i… Greg Mirsky
- Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-i… Tianran Zhou
- Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-i… li_zhenqiang@hotmail.com
- Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-i… Jean Mahoney
- Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-i… Rakesh Gandhi (rgandhi)
- Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-i… Jean Mahoney
- Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-i… guo.jun2
- Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-i… Jean Mahoney