Re: [auth48] AUTH48: RFC-to-be 9534 <draft-ietf-ippm-stamp-on-lag-06> for your review
"Rakesh Gandhi (rgandhi)" <rgandhi@cisco.com> Fri, 26 January 2024 17:59 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 CA211C1CAF35; Fri, 26 Jan 2024 09:59:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.605
X-Spam-Level:
X-Spam-Status: No, score=-14.605 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_HI=-5, 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_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 1YqVtYuOwQHR; Fri, 26 Jan 2024 09:59:20 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (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 B3A92C137367; Fri, 26 Jan 2024 09:59:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.com; i=@cisco.com; l=122978; q=dns/txt; s=iport; t=1706291959; x=1707501559; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=JJlPCzLrrzQKrlhhFP8saUIsu1RlRq6pEdvSGzqEb1M=; b=MA8Fo6rFvP7EiXL5RNPyZ+MCtbeeQdni+gkZxPu73Qg7ooqF9dJHtln0 OYak/Y4Xwv0CkUC6T4o5f1B6HHEdW8XmChmY/MOq5PSmqg1F3acevpv+s vZKtfPvVAOqpzWCqYl9URM9uc6FfP5W5e4ToFyX5xrY7MHDZO3qpiLMc6 s=;
X-CSE-ConnectionGUID: Mul1DARhQymWHfps76RGVA==
X-CSE-MsgGUID: pyVPWak+T+uqSRx0VDt7Gg==
X-IPAS-Result: A0ACAADX8bNlmJJdJa1aGQEBAQEBAQEBAQEBAQEBAQEBARIBAQEBAQEBAQEBAQFlgRYEAQEBAQELAYE1MSooegKBF0gxhCGDTAOETl+GRYIiA4J+iGCFYoxFFIERA1YPAQEBDQEBOQsEAQGFBgIWNAEEAQiGcQImNAkOAQIEAQEBAQMCAwEBAQEBAQEBBgEBBQEBAQIBBwUUAQEBAQEBAQEeGQUOECeFbA0IAQ4QgX2EIQEBAQEBAQESCAEIBEcLBQcEAgEIDgIBAwEBAQEgAQYDAgICHhEUCQgCBAENBQgagl4BghcUAw4jAwEQBqoLAYFAAoooen8zgQGCFgWBTkGuDQ2CVYFIAYgEBBoBaGYBAYFsgg+EVycbgUlEgRVCgmg+gh9CAgEBgSEDAQQBEgEjDgcJFoMlOYIvBIEXI1yCMGopgRiCVQJvcAGEHAIlgV1DAYFAFIUHVHkjA10gCARcDxsQHjcREBMNAwhuHQIxPAMFAwQyChIMCyEFE0IDQAZJCwMCGgUDAwSBMAUNGgIQGgYMJgMDEkkCEBQDOAMDBgMKMTBVQQxQA2gfMgkHNQsEDBoCGxsNJyMCLEADERACFgMiFgQ0EQkLJgMqBjcCEgwGBgZdJhYJBCUDCAQDVAMhdBEDBAoDFAcLB3iCDIE+BBNHEIE6BmADRB1AAwttPRQhBg4bBQSBNgWWP3kBgUwQFUwrEyYEDRoBChEOAQFOAkAIRgEjAQULASYFKQ+MeIU2DxIIOIJfAUmLG6IKCkBwCoQRjAaOGYEHAYJsgzwXhAVMjCsDjTiIIIJfZJhUIIIxhxeEBYN9kToEEoULAgQCBAUCDgEBBoFjOmtwcBUaIYIzATMJSRkPjiwNCYEMAQgdhzqKKAE7AXYCAQE3AgcBCgEBAwmGSAWCIRsLBm0BXwEB
IronPort-PHdr: A9a23:nbMzdBcHCb+p6TrFZqmBZowzlGM/eoqcDmcuAtIPkblCdOGk55v9e RCZ7vR2h1iPVoLeuLpIiOvT5rjpQndIoY2Av3YLbIFWWlcbhN8XkQ0tDI/NCUDyIPPwKS1vN M9DT1RiuXq8NBsdA97wMmXbuWb69jsOAlP6PAtxKP7yH9vIgM2x2+Cz05bSeA5PwjG6ZOA6I BC/tw6ErsANmsMiMvMrxxnEqWcAd+VNkGVvI1/S1xqp7car95kl+CNV088=
IronPort-Data: A9a23:2f/cEaLMicjEX30OFE+R8ZUlxSXFcZb7ZxGr2PjKsXjdYENS0jRTy DdNXWGHPv3bNGrxKN5+bdi0ox5VupCDyodmSAsd+CA2RRqmiyZq6fd1j6vUF3nPRiEWZBs/t 63yUvGZcYZsCCea/0/xWlTYhSEU/bmSQbbhA/LzNCl0RAt1IA8skhsLd9QR2uaEuvDnRVvQ0 T/Oi5eHYgP9gmQoajt8B5+r8XuDgtyj4Fv0gXRmDRx7lAe2v2UYCpsZOZawIxPQKmWDNrfnL wpr5OjRElLxp3/BOPv8+lrIWhFirorpAOS7oiE+t55OLfR1jndaPq4TbJLwYKrM4tmDt4gZJ N5l7fRcReq1V0HBsLx1bvVWL81xFYhb/ObrCEK/iN2W8G3Ia2Cznc9BMmhjaOX0+s4vaY1P3 eYTJDZIZReZiqfvmPSwS/JngYIoK8yD0IE34y47i2qGS6d9B8mfHc0m5vcAtNs0rtpBFPDSZ 8sxYjt0ZxOGaBpKUrsSIMthzL3w2CahI1W0rnqNtJQP3GHQjzAyzaHWCsqNRPCWGupayxPwS mXupDmhXUpAa7Rz0wGt+2+whrOflDnwWIMMGZWi+PUvjVGS2msJThoMWjOTu/eyz0OyWs5YM WQO9CFroKQz6EuxCN7nUHWFTGWspBUQXZ9bFPc3rVjVjKHV+A2eQGMDS1atdeDKqucTWDhz+ nazn+r4AANPvqWOFiyn2Ym9+Gba1TcuEUcOYioNTA0g6tbloZ0ugh+ncjqFOPPl5jESMWygq w1mvBQDa6MvYdnnPphXEHjdiD6q45POVANwv12RVWO+5QQ/b4mgD2BJ1bQ5xagcRGp6ZgDd1 JThpyR4xLtfZX1qvHfSKNjh5Jnzu5643MT02DaD5aUJ+TW34GKEdotN+jx4L0oBGp9bIWGzO BCP6VgOtcI70J6WgUlfPtPZ5yMCkPmIKDgZfq68gidmO8EuJFHdoEmCm2bJhz+0+KTTrU3PE czGKZn3Vyly5VVPxzutTOBVyq4w2i073ivSQ5u9pylLIpLADEN5vYwtaQPUBshgtfvsiFyMr 753aZDQoz0BC7KWX8Ui2dNJRbz8BSJlVcmeRg0+XrPrHzeK70l4U6CAnex/JtA090mX/8+Rl kyAtoZj4AOXrVXMKB6BbTZob7aHYHq1hStT0fAEVbpw50UeXA==
IronPort-HdrOrdr: A9a23:lv1n+amT6ZhgcqlIJuEBwgGI8AnpDfNliWdD5ihNYBxZY6Wkfp +V7ZcmPE7P6Ar5BktApTnZAtj/fZq9z/JICYl4B8bFYOCUghrYEGgC1/qv/9SOIVyFygcw79 YFT0E6MqyOMbEYt7e03ODbKadc/DDvysnB7omurQYJcegpUdAd0+4TMHfjLqQCfng8OXNPLu vl2iMonUvGRV0nKu6AKj0uWe/Fq9fXlJTgTyInKnccgjWmvHeD0pK/NwKX8Cs/flp0rIvK91 KrryXJooGY992rwB7V0GHeq75MnsH699dFDMuQzuAINzTFkG+TFcVccozHmApwjPCk6V4snt WJiQwnJd5P53TYeXzwiQfx2jPnzC0l5xbZuB+laDrY0I/ErQABeo98bLFiA1/kAo0bzZZBOZ dwriCkXlxsfFX9dWrGloH1vlpR5zqJSDIZ4J0uZjpkIMUjgHs7l/1FwKuTe61wRB7S+cQpFv JjA9rb4+sTeVSGb2rBtm0q29C0WG8vdy32CXTql/blmgS+pkoJh3cw1YgahDMN5Zg9Q55L66 DNNblpjqhHSosTYbhmDOkMTMOrAiiVKCi8fV66MBDiDuUKKnjNo5n47PE84/yrYoUByN83lI 7aWF1VuGYucwblCNGI3pdM7hfRKV/NFwjF24Vb/dx0q7f8TL3kPWmKT00vidKpp7EFDsjSS5 +ISeRr6j/YXBzT8KpyrnnDssNpWAsjueUuy6MGZ24=
X-Talos-CUID: 9a23:DzjFvmEJk85LuorlqmJC6UpNNukfckTMyUjwLVejVjhTZ4O8HAo=
X-Talos-MUID: 9a23:OiNjYA9FK5l3raCkPzVjwsiQf9953ZyRAUNOrdYbovK+JXROFyvCozviFw==
X-IronPort-Anti-Spam-Filtered: true
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-2.cisco.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Jan 2024 17:59:18 +0000
Received: from rcdn-opgw-4.cisco.com (rcdn-opgw-4.cisco.com [72.163.7.165]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id 40QHxHHn003166 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 26 Jan 2024 17:59:18 GMT
X-CSE-ConnectionGUID: U0c9jkLWQEq9pHgpPE2VEA==
X-CSE-MsgGUID: giHOWQ6lRMmaHJmgLtnsfw==
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="25671052"
Received: from mail-mw2nam10lp2101.outbound.protection.outlook.com (HELO NAM10-MW2-obe.outbound.protection.outlook.com) ([104.47.55.101]) by rcdn-opgw-4.cisco.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Jan 2024 17:59:16 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=I/SIY3GVpepZx4Mxgjt5t579ChdswRGEDCcw0nh9ftEZQPLRplQECJbsezF3ol6Q2137moY4a7aYfVMXkWjS752AvEkSH8/KRhJtCqlr3dtg0NCMaM7L+VrEnazsfUD8QkQguOUGPUiRReTOhe1tRfyuUJmYwBzL+He+RAQJNiwB8f3mRqjmGVycIJPW6mo8Y9vr9hCw74ZLVrdJIl70in9cv+0XEThbLj417MLgWx7nY5AZ822amhS+ClKqag1ARZnLwkTZ/ihM0G53urcD7kCPqUb8yYPOLVztcOKIZYZDS8hF4jODGHv0J4UYrbde0g8XGIZQ2nxQvkHr1ALDRw==
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=JJlPCzLrrzQKrlhhFP8saUIsu1RlRq6pEdvSGzqEb1M=; b=dLr9dmW/P44C7MVSIJkIHAhNjPu81SA3WZGRmpkwe7DJ2Ps1x9HkR4dztIvC2WITSX/bnVJdfGW/WDDXq0hoz5J/90E4DO5APoKFoc+EeSWfU/SMQuXmnaStp4AKKWII749nbckqXt2RllnhjEgRhHnavOoYLyRX6GRfdeUWD9b71eA165AZLTjvU9O8RAf9wQ9Hkr75ULDdQb2Lsi35xFP4Lby4aPIrv2ZGw01kNrPgodkA4S4tWGOeD0dJwzOnDdM6HOGaWWETVoXerHTz1UqGUxIeQD+58qlyVdrfAH9QSpXRo7bE5/6Wz3+0QsKiZIlZ4elXvJGpvT6jvsWFkA==
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 DS7PR11MB7905.namprd11.prod.outlook.com (2603:10b6:8:ed::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7228.26; Fri, 26 Jan 2024 17:59:12 +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.027; Fri, 26 Jan 2024 17:59:12 +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: AQHaUICSFfhgKf+CvEWQmtu7giGNmLDsYX49
Date: Fri, 26 Jan 2024 17:59:12 +0000
Message-ID: <BL3PR11MB573195E0ADB56A9983C1552EBF792@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> <5e6742ff01c641999bbcfaca4697fb2a@huawei.com> <MEYP282MB29429753B76DECF2E3EAE7B5FC7A2@MEYP282MB2942.AUSP282.PROD.OUTLOOK.COM> <320712c6-dcbf-4c02-9935-19b17ebd7033@amsl.com>
In-Reply-To: <320712c6-dcbf-4c02-9935-19b17ebd7033@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_|DS7PR11MB7905:EE_
x-ms-office365-filtering-correlation-id: 569394ff-e13f-4145-448e-08dc1e98809e
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: jJAo9UtFln+6AgDDfup7e0+OYaqOyBJuxiKrTOp+p7HzTnvXJXzVbcntbhxRdlk6J6yDhWdgoJLH+euNwWjGJwTnpJYjkyt7lHWhATzz5837GLwMsALa1XaBEGGypH9QEI8BGRV+l9VYIRMGRJrd7AhsJMX6fxS9D85lWrUZLGd/um23jHm4qQXLNVzUI7YBIWjKf+iwmOiRBnlzF5nb1+TSOWbt+p00xiEquBwdejedKFFWbNeMm8eXLRMnhgRMIbau7JvpGnc4aUKZvytMbW1Tvueq/CL1UMJGffpfu2cRG+DMsGLUbcb6YiT8WMJhwrL3Entd1L9EkVv9kGMNvEpfo86siyEoU781ZTGHoqbH1K/VqMBWKdfPVcs6Mh+7qOAvyZbcvsH7uaLZ6dz1CrvTMvgyQdBi4UA2cObSE86qX43IjpTIC8vJ6kL+rpTsSSg2Wga1zZ8cfct2R1eHtuQm4dRxbPxMQIdM+UGfEyIIsdShpvSgr7xiFlgu7McSvKAEtVtFMvRb+RJsYSmAyZb2aq2u47zCa1unxwn5hNvnzPH1R+R1AfmdiApoQJ/zjxNpnPYS2KuG/bfPut6KeQYAFf12DvymNcgyU3NGaCU=
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)(396003)(366004)(346002)(39860400002)(376002)(136003)(230922051799003)(1800799012)(186009)(64100799003)(451199024)(54906003)(38100700002)(66446008)(64756008)(66556008)(6506007)(7696005)(110136005)(91956017)(76116006)(478600001)(66946007)(53546011)(66476007)(316002)(8676002)(41300700001)(9686003)(8936002)(166002)(26005)(55016003)(86362001)(966005)(45080400002)(71200400001)(21615005)(52536014)(2906002)(5660300002)(122000001)(4326008)(7416002)(33656002)(83380400001)(30864003)(38070700009)(579004)(559001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: i+XNEX0RNi+cYkO/P6wdWWup0FuW+Kob7B4ot5h+4rkeoQpLbU4XjSlN2Vdea+IKQfi24DFApSexJIOwsgC3Hs9QWzJ5Pcaw1p2PG+/y9xYcWROPJOll5YGfvJ3UE0kN8Mta9hm0hZsMFm/eR+gkZDJXk+NxSN/D+aTZPRh6AUkNIcSnHu4WVNoihwjD9mQ2y759URUCHuzEKtNX74/SXUX9Ov7mYZLOvD/jkQhweER//GcOuvMdLNweG0OzQBsQ5GHrnnbSgEnO+XjzM2+qCRr/+6sysP98ggRT9/wchlPxC6chqZLUTJ5DjSg8jxuwSIIDOZfUjdBL/lXE45hf0xy6jI6Pa9cEg6sqVIjoj+YiT7qRTrfVh8D0Y1Ku5xXE7gPL2B536LbigN0aK1o2haGs+s6XlnhcTbmS1gV+1E6lAmzS2toSuKjASFjD4f9DZPPrXJ60p5y6LXs1sTWyqgrsnDDfkhdYW5ceds5k6iFaQEKkMFDEABwglF9rm+nncNKngnydSojwIQmZmUMMenWfMKaySVAt9mG4MGfXHN8Xi3ut7gSel3R8lFXU0DfrhnzkeVmmCTbvF42BydoimpHq1073CJHIAsWOiIIJ2AkVP35sgkK8bhqt9yie9QkDObH6Zf/Vt0gnHB56bLUsvI1s1lkVWFBQe8wzrZMpiQPqx2LXFPOygN+Kd2FlshoR7usxm2t5uTIf6BoBjt0KAJbpF6darejMhsGgA8Guc83PBF/2FbCHi29Po7RX9CK7OMmIX5AL2IZ8fNDgIRIYoHF7Ly+4gdCZmryR2CZLnADP2+TL5GG4BUR+IGMGXgCQJzbiE3E9P5hpgcSV0uLqEWk26Ob+9imTfP6YXO3XvpTGLXjo6cH1mu16jtFlUvqv8PIxXhwNS38jXvPMMRy8nxmCgOySyhJc1DBWbNShzpJWQ4CX1qPEM5EmuenbrgSuKtVF/5Nm//FsSznHNqQ8Gv1N8MXEvNk3FPb44S6F23eQNFr2MSfAUfzzAA/jaGsRIMVtpdmvGfWOHUKBqCHZUpejFy9jsE8Nb3/+DjaoCU+oVvUTV/UIBwzaT5q69M7i67jo8ExJNjFZ9j41nVrs8eMKMFuOVcIg/hHGTOuEdYaNcj6M/wlEWcAJhbmHTrRqiI1bgZraip+S8IAyFYn6KTSkmTYHFOJkFH1MBCAMHMhqAKy7WDQbOBqIoGp9WglHqMfxpgqQ0aPsFg1vLNK38sE1QdgQ8C2q9LW9u90zjVtga7fPsFJakFnE2VKkQjfObv3nNP+rHeRlqfxeX4BxSf3si42G0mYEPI2sej9+m/4N0l8/xgWpQC2ertXREUP+9Obnb2PL7ZOEmNl8Uwl/BNhqwNtHu06hgz4r3T/rSkgxSGNuBqTtmrk669O9eSgjD6LMVx9sIhN2cLHuNVwpTIPc+qJrVzJ6Fsopwae8EKSjTlvjOmqtQdoRwls/rAghAlt/AYgIOo1QGZ0QvRZHM1aHsyqiQk3Bfw/D5/Q8CbNfrdWFKmtteACPDwmxbx15y1+rWG6+W23I7/J/yxZobjOB5HR2o4ONcirie+WtpGnj3+gsGA/ALBu17ozEV6gzJ5Pk7GxdO43V/EGcDR0GPA==
Content-Type: multipart/alternative; boundary="_000_BL3PR11MB573195E0ADB56A9983C1552EBF792BL3PR11MB5731namp_"
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: 569394ff-e13f-4145-448e-08dc1e98809e
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jan 2024 17:59:12.1202 (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: DrRr8ErgzLdlZ+IvF8hxIkcaJIDfDoH7eTaRDOUJte65xmgF6bXf39lmQBPMCpfdxDtFkZf65yRnfLTE0M5DeQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DS7PR11MB7905
X-Outbound-SMTP-Client: 72.163.7.165, rcdn-opgw-4.cisco.com
X-Outbound-Node: rcdn-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/CYzX-mhHTkgg1kLYF3TExAVKZWg>
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: Fri, 26 Jan 2024 17:59:24 -0000
Thanks Jean and co-authors for your review and updates. Looks good to me, I approve the document. Thanks, Rakesh From: Jean Mahoney <jmahoney@amsl.com> Date: Friday, January 26, 2024 at 12:53 PM 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 Greg, Tianran, We have noted your approval on the AUTH48 status page: https://www.rfc-editor.org/auth48/rfc9534 Tianran, Rakesh, We have updated the document with your feedback: https://www.rfc-editor.org/authors/rfc9534-lastrfcdiff.html We will await further word from Rakesh and Jun regarding other AUTH48 changes and/or approval. 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 https://www.rfc-editor.org/authors/rfc9534-rfcdiff.html https://www.rfc-editor.org/authors/rfc9534-auth48diff.html https://www.rfc-editor.org/authors/rfc9534-lastdiff.html Best Regards, RFC Editor/jm On 1/24/24 10:58 PM, li_zhenqiang@hotmail.com wrote: > Dear Jean and coauthors, > > I approve the changes and Tianran's suggestion. Thanks Jean. > > ------------------------------------------------------------------------ > Best Regards, > Zhenqiang Li > China Mobile > li_zhenqiang@hotmail.com > > *From:* Tianran Zhou <mailto:zhoutianran@huawei.com> > *Date:* 2024-01-25 09:06 > *To:* Jean Mahoney <mailto:jmahoney@amsl.com>; > li_zhenqiang@hotmail.com <mailto:li_zhenqiang@hotmail.com>; Greg > Mirsky <mailto:gregimirsky@gmail.com>; rfc-editor@rfc-editor.org > <mailto:rfc-editor@rfc-editor.org> > *CC:* guo.jun2@zte.com.cn <mailto:guo.jun2@zte.com.cn>; Rakesh > Gandhi (rgandhi) <mailto:rgandhi@cisco.com>; ippm-ads@ietf.org > <mailto:ippm-ads@ietf.org>; IPPM Chairs > <mailto:ippm-chairs@ietf.org>; marcus.ihlar > <mailto:marcus.ihlar@ericsson.com>; Martin Duke > <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 Jean, > Thanks for your work. I approve the current version of the document. > One nit I want to sync with RFC-to-be 9533. > OLD TEXT: > All micro sessions of a LAG share the same Sender IP Address and > Receiver IP Address of the LAG. > NEW TEXT: > All micro sessions of a LAG share the same Sender IP Address and > Receiver IP Address. > Best, > Tianran > -----Original Message----- > From: Jean Mahoney [mailto:jmahoney@amsl.com] > Sent: Wednesday, January 24, 2024 11:20 PM > To: li_zhenqiang@hotmail.com; Tianran Zhou <zhoutianran@huawei.com>; > Greg Mirsky <gregimirsky@gmail.com>; rfc-editor@rfc-editor.org > Cc: guo.jun2@zte.com.cn; Rakesh Gandhi (rgandhi) > <rgandhi@cisco.com>; 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; > Zhukeyi(Kaiyin,Datacom Standard&Patent) <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-4Q9l2USxI > > Ae6P8O4Zc > > > <https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USx > > IAe6P8O4Zc> > > > > * 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