Re: [auth48] [AD] AUTH48: RFC-to-be 9390 <draft-ietf-dime-group-signaling-14> for your review
"Rob Wilton (rwilton)" <rwilton@cisco.com> Thu, 20 April 2023 09:07 UTC
Return-Path: <rwilton@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 6B077C151524; Thu, 20 Apr 2023 02:07:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.594
X-Spam-Level:
X-Spam-Status: No, score=-9.594 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, 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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b="H6WGMOrK"; dkim=pass (1024-bit key) header.d=cisco.com header.b="EI8oWMA4"
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 cQK_ub1Zy3Cw; Thu, 20 Apr 2023 02:07:07 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC1BAC14CE53; Thu, 20 Apr 2023 02:07:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=35418; q=dns/txt; s=iport; t=1681981626; x=1683191226; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=BPacSwha5ZjtqXjBIo/GRKz+CUycfqqbt2jEqma43V0=; b=H6WGMOrKz+WN612EJWMuNMMhJDaAeiLFvRU5Lwo+UhGEQCKmZ5oAjroO PZsRbmP8BcDRWq/hUudjvYiv+AmCpV2tZJWyXMoyn96rpX3noUTBJPtwU 5Qnzk7MoCQdAIOQmxPLfC/7/u0egefWnNM54+PPSgQxG2dx98jm8ga7av M=;
X-IPAS-Result: A0ABAAAgAEFkmIcNJK1QChoBAQEBAQEBAQEBAwEBAQESAQEBAQICAQEBAUAlgRYFAQEBAQsBgVsqKHMCWDxGhFKDT4ROiRYDi0uFVIkrgxIUgREDVg8BAQENAQE5CwQBAYUGAhaFJgIlNAkOAQICAgEBAQEDAgMBAQEBAQEDAQEFAQEBAgEHBBQBAQEBAQEBAR4ZBRAOJ4VoDYYDAQEBAQEBARIICQQNDAEBLAsBBAcEAgEGAg4DBAEBAQICJgICAh8RFQgIAgQBDQUIGoJcAYIoAw4jAwEPBj+OR489AYE/Aoogen8zgQGCCAEBBgQFgTcBmxUNgkcJgRQtAYdHgWKIGicbgUlEgRVDgWaBAj6CIEICAYEiAwEEAQcLAQcCGoNZOYIuijKCAYJji3CBNHaBIA6BPIEEAgkCEUMogRAIaoF5QAINZAsOcYFJY0yBewQCFEQOGC43A0QdQAMLOzo9FCEGDh8FBFNrCyMkBQMLFSpHBAg4Bhs0EQIIDxIPBiZEDEI3MxMGXAEpCw4RA06BRwQvOQuBFAoCBAEmJJxlgXIBEBVGBgEqEyYEDQcTAQcDHwINEy4lCAgNCDUIBQUKFAEEAQUBBAYBHwcDjR+FMgsaCi2CWwFHoDqLPwk+bwqDfotyjgiBBoYjF4N9TIEJixEDjRqIFoJKYpcAdyCCLosFg26RIBIKD4RqAgQCBAUCDgEHgTIxOmtwcBUaIYIzATMJSRkPjiAMDQkVbwEIHYImhRSKZAFDMgIBATkCBwEKAQEDCYZLgiEsgU5fAQE
IronPort-PHdr: A9a23:iInfUhSU/ydhPtNpsixXAxio4Npso3DLVj580XJvo7tKdqLm+IztI wmEo/5sl1TOG47c7qEMh+nXtvX4UHcbqdaasX8EeYBRTRJNl8gMngIhDcLEQU32JfLndWo7S exJVURu+DewNk0GUN3maQjqq2appSUXBg25MAN0IurvHYuHldu20/y1/bXYYh5Dg3y2ZrYhZ BmzpB/a49EfmpAqar5k0wbAuHJOZ+VQyCtkJEnGmRH664b48Mto8j9bvLQq8MsobA==
IronPort-Data: A9a23:w2PLDq/VlvKJYz+0pOhVDrUDoH6TJUtcMsCJ2f8bNWPcYEJGY0x3x zdOWm/UaP2ONjehcth/O4Xl8B4G75TUydRqQVZppS5EQiMRo6IpJzg2wmQcns+2BpeeJK6yx 5xGMrEsFOhtEjmE4E3F3oHJ9RGQ74nQLlbHILOCa3EZqTNMEn970ko/wbZh2eaEvPDga++zk YKqyyHgEAfNNw5cagr4PIra9XuDFNyr0N8plgRWicJj5TcypFFJZH4rHpxdGlOjKmVi8kFWc M6YpF2x1juxEx7AkbpJmJ6jGqEBaua60QRjFhO6VoD66iWuqBDe3Y4YaL0AN3tZsg+xwcxt5 4py6JGWdQIma/ikdOQ1C3G0Egl3OalAvbTAO3X664qYzlbNdD3nxPAG4EMeZNJDvL0pRzgVs 6VDdVjhbTjb7w6y6KikS+1wgcILJ8jwN4RZsXZlpd3cJap7G8ibHfWQjTNe9BIMvJhVOMmFW 8g6OTRrKxvSWA0eMX5CXfrSm8/x1iWgLFW0smm9rLcr4zSDxRZ60LnzPfLPdNfPSMlUgkGC4 GXc8AzRGB8RcdGTyCaC6Fq2iOSKkC/6RIUIUrqi+ZZXbEa7z2gXDlgdUkG25KP/gU+lUNUZI EsRksYzkUQs3G/3CcWjYxOBmkbaogIzBOUNHssG7Q7Yn8I4/D2lLmQDSzdAbvkvu8k3WSEm2 ze1czXBWGQHXFq9FCv1y1uEkd+hEXNPfTJeOUfoWSNAsoe+8dBr5v7aZow7eJNZmOEZDt0ZL 9qigyEkg7wVgabnPI3koAib2FpASnU1JzPZCy3eWmajqwh+foPgPcqj6EPQ6rBLK4Pxori9U Josx5j2AAMmVM7leMmxrAMlR+vBCxGta2e0vLKXN8N9nwlBAlb6FWyq3BlwJV1yLuEPciLzb UnYtGt5vcEDZSrwPPctM9LvUKzGKJQM8/y4CZg4ifITPfBMmPOvp0mCmGbJhTm2yRhw+U3BE cbAL65A8kr2+Yw+nGbpGI/xIJcgxzs1wivIVIvnwhG8uYdyl1bLIYrpxGCmN7hjhIvd+V292 48GZ6OilU4FOMWgOXa/zGLmBQ1QRZTNLcqo+5U/my/qClcOJVzN/NeLm+l7J9c4zvoK/goKl 1nkMnJlJJPErSSvAS2Ba2tob/XkWpMXkJ7xFXZE0YqAs5T7XbuS0Q==
IronPort-HdrOrdr: A9a23:pbP6uqgVP6up9gwF91axRhdA73BQX2x13DAbv31ZSRFFG/FwyP rBoB1L73DJYWgqNE3IwerwRJVoIUm3yXZ0ibNhWYtKLzOWx1dAS7sSoLcKogeQUREWk9Q96U 4OSdkHNDSdNykZsS++2njELz9C+qjKzEnLv5ak854Fd2gDAMEQjDuRSDzraHGeLzM2YqbRYa Dsn/av0ADQH0j/AP7LY0XtWdKvm/T70LbdJTIWDR8u7weDyRmy7qThLhSe1hACFxtS3LYL6w H+4kLEz5Tml8v+5g7X1mfV4ZgTssDm0MF/CMuFjdVQAinwizyveJ9qV9S5zXEISaCUmRYXee v30lUd1vdImjbsl6aO0F/QMjzboXUTArnZuBilaDXY0IrErXkBerR8bMpiA2rkAgwbzZ5BOG Yh5RPAi3KRZimwxRjV9pzGUQpnmVGzpmdnmekPj2ZHWY9bc7NJq5cDlXklWavoMRiKn7zPKt Meev309bJTaxeXfnrZtm5gzJilWWkyBA6PRgwHttaO2zZbkXhlxw9ArfZv1Uso5dY4Ud1J9u 7EOqNnmPVHSdIXd7t0AKMETdGsAmLATBrQOCaZIEjhFqsAJ3XRwqSHqIkd9aWvYtgF3ZEykJ POXBdRsnMzYVvnDYmU0JhC4nn2MRGAtPTWu7RjDrRCy8/BreDQQF2+oXgV4ridn8k=
X-Talos-CUID: 9a23:dMf/VGvCDp7xM2w4CxhhkpWq6IsGLjrBkkveGnWAV3p1Z+KqFFK2xKZrxp8=
X-Talos-MUID: 9a23:t0/BCQjmlZUa4Oj11TzB88MpEftSu7+LNxsxk7ZWtc3DOj5LK2aWpWHi
X-IronPort-Anti-Spam-Filtered: true
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 20 Apr 2023 09:07:04 +0000
Received: from alln-opgw-3.cisco.com (alln-opgw-3.cisco.com [173.37.147.251]) by alln-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 33K974mw030559 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 20 Apr 2023 09:07:04 GMT
Authentication-Results: alln-opgw-3.cisco.com; dkim=pass (signature verified) header.i=@cisco.com; spf=Pass smtp.mailfrom=rwilton@cisco.com; dmarc=pass (p=quarantine dis=none) d=cisco.com
X-IronPort-AV: E=Sophos;i="5.99,212,1677542400"; d="scan'";a="409968"
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CN6V94PURbBsC1JhY8eiddpvroHNjAMJIrzWHgU9yrmCkA3A2SW4kzetYT4ZbMYzt8NaJ6nnemSiF2wPDIPcWyM9hCEoTemrXazEKa4KZjFLStcgMBBaS2r0izfkbGn8pZfn+gsCtaNNdbio7/fLFngyZPhPhkUvQVbaVwXtPniupfzqdPmv1rjH4Mm1NqLpl2lGs1aF5I8TsCBqQPYCRIIyC+tzDeREXbPZA7Rtr4mfFiEH+or6U5j3vZMWx4uY5latkwEIr5PV+Oq6uSOwBER6JmL7ZqtlqepN75vlCPyPESYDlFjeOL2PyCFeXc0NC9AG88hS55+qTmCW1trM1A==
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=BPacSwha5ZjtqXjBIo/GRKz+CUycfqqbt2jEqma43V0=; b=ZHZrrFFlrpwdwc2aizDgGoofWiAMmtediO2CMOf/ZTwEc+GvLyNx+9exJmI0V66v06tBywJBQIKHO/JZEl2H405izQ69z95AzgZV6QHxlG+4NME0QAictJ0AAju1dQENpZqR7zAriZTBKBNIFmJB5AiNh/EngFhhJZg0T042dIH3O/JWecsYkRZI90d1VN7aZ9xlr67PwrJca8ivjerQa3im/qYIsOVE278TmYbQsMWldrrXLYepdqL7PU6sgnBMTZ9YXQBv1ea5sgUwzVRn8didUcsWmMcuMcb7Ab3FVneIiWEQv4rSSTNziwWrkys0/qC8E6xLqoP39I7B0OJnHA==
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
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=BPacSwha5ZjtqXjBIo/GRKz+CUycfqqbt2jEqma43V0=; b=EI8oWMA4qrFLj7SSJCJCIA/68236lgZT1aekVca1m8urZduXjcj+MvY3UMWF+bNK4iCR+1RNuJ+FXYH+979N6zV2219nK+DcuvvAe2KzPde7oXMQmRoOPy7EoVtkrAu6+DHL+pgME9EbuAU2BrWVW7DaRJWHSlQKXjHFTExAJXQ=
Received: from BY5PR11MB4196.namprd11.prod.outlook.com (2603:10b6:a03:1ce::13) by MN0PR11MB6182.namprd11.prod.outlook.com (2603:10b6:208:3c6::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6319.22; Thu, 20 Apr 2023 09:07:00 +0000
Received: from BY5PR11MB4196.namprd11.prod.outlook.com ([fe80::ef4:1432:b69e:19b2]) by BY5PR11MB4196.namprd11.prod.outlook.com ([fe80::ef4:1432:b69e:19b2%7]) with mapi id 15.20.6319.022; Thu, 20 Apr 2023 09:07:00 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Alanna Paloma <apaloma@amsl.com>, "lionel.morand@orange.com" <lionel.morand@orange.com>, "mark@azu.ca" <mark@azu.ca>, "marco.liebsch@neclab.eu" <marco.liebsch@neclab.eu>
CC: "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org>, "dime-ads@ietf.org" <dime-ads@ietf.org>, "dime-chairs@ietf.org" <dime-chairs@ietf.org>, "jounikor@gmail.com" <jounikor@gmail.com>, "auth48archive@rfc-editor.org" <auth48archive@rfc-editor.org>
Thread-Topic: [AD] AUTH48: RFC-to-be 9390 <draft-ietf-dime-group-signaling-14> for your review
Thread-Index: AQHZXnNDLo9Nk8hcHkSkZCCxKSaJwa8l8KyAgAC9+gCAAQDjAIAAs+cAgAsd0QCAAJBk0A==
Date: Thu, 20 Apr 2023 09:07:00 +0000
Message-ID: <BY5PR11MB41966915A1F7F68B5FABC56DB5639@BY5PR11MB4196.namprd11.prod.outlook.com>
References: <20230324170823.8845E1FCF27@rfcpa.amsl.com> <5967_1681204800_64352640_5967_44_1_73da6c6449d74cc79749d0d41418ad71@orange.com> <6344C81D-60B4-4456-BD3E-B2B99D7CAB12@amsl.com> <5812_1681300763_64369D1B_5812_96_1_7b39490fddd041509b406b9970edaf99@orange.com> <82F2CB31-B904-4A7E-BD07-C00932FBB533@amsl.com> <8B62FE02-39BD-4686-BE96-64B9AD2B70D6@amsl.com>
In-Reply-To: <8B62FE02-39BD-4686-BE96-64B9AD2B70D6@amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: BY5PR11MB4196:EE_|MN0PR11MB6182:EE_
x-ms-office365-filtering-correlation-id: 05a88bee-8494-4cc1-9baa-08db417e99c2
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 2NKK4EFa3dXqL7x/N+k3cWKw052TPr18duJbXlweUhek5V+8kPlASUiagigPb66SyLS9w8RIq0dRh6ym3DFHbrOsDk5CNo4WaV7/QMGIh/xOl2M8zZt4Da9tQUact8BpyC3BNqBk5nyONn8bGL94m3uGC7wgoqL14xYcht2BN32OpgmJmdmOnRAaN3AnBCv4XoVspPXSnTubkjM3qZ6i9utGXiUbFheCYUGf+JfBTDJNtmenaLerBzUY52TVSiXO/5ZT5HJc00ZjVNSvOqcBm37qh+ptWV7knF0fMmgRuUNc0RKoyVykUzIWyys0WIWfJOHMlB0vv+NuioDUxHwuOYULHyIchHCzsswKNYxNtyqhLuHH2EVhIARC7Brou/RQdr75cOHAeAiZWbycSp1Asg2HCRFYK4BsofROSmMBEeGycMgBZt1dFV5HKxAgzJ52Y2oXrlopSLQr065iXcwlRSz8Sd/3+etzECBZpBLXg42Ova4uSe5+JczoYbQhQvtH64ceACvXQCTrp++cfboQE8TeYeowj9U5PYpOOViyE6jxlm37McsC7UVdW4/sY+CY/6PpVRfipErNk7aP3fMGY0A6h98Kb1N5pG3D5NtKsfbcruhdaNKgDDT+34xYdeFetseK+ya7uQMLCWFHkDMp7Vh9LtDN2UVhiPvxJjlrnuE=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BY5PR11MB4196.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230028)(396003)(39860400002)(376002)(136003)(366004)(346002)(451199021)(316002)(966005)(66556008)(66476007)(66446008)(64756008)(66946007)(76116006)(4326008)(86362001)(478600001)(19627235002)(110136005)(71200400001)(55016003)(7696005)(52536014)(5660300002)(8676002)(8936002)(122000001)(2906002)(30864003)(83380400001)(38100700002)(54906003)(53546011)(33656002)(26005)(41300700001)(38070700005)(186003)(9686003)(6506007)(559001)(579004)(19607625013); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: MYjKjtzYCVjs/l3nZJiza+X5zzhu7kwWMlZdd4cF2tihjx68MQ2YWXCjAQ8xIJt4FbKkJm7xzm0TsR3q3GJiullDtXNe0BMf19gmdPK70h2rrMN+3OwlL8pnlrVzaFiK6cthgQRqnQDMt+c7dH9aZHdbRZcOm3SgN+laHb/aH1k8GR5CwneR7DACAqeew0nyf6fzx92lxw/OX2NfCwUjrt5dQHyg5PNPYtsHFijhVBRrHP95c05ZA3pXn54KWKsbI451Fcs7kpJkDQD+yAmN4EZv3QXUe67vH6Qu6zeX7gcXXZPHmMW3KyXCe4ZBCBEeNnSbc73pDB+ocdxFHOpMgyxI1jDgUt19Ra+2IbPeBOgPkxhJf7OtLt2obKFOY1kgX5uW5A3m/ksEok91K1198jXc9AO8KFlxWjQYrSJ1oY9kwLcNUYB1LokB+ypHyOxxdtvq+mf/FTYy5hggZBaL3pFXVIFQV0aXJU0zfsj7vVESts6Ri6MVc/RTBufCP5DK044phosCLfaE+66jDe6AKGARHUoCXIZWY56ay8YL6/maTeW1N1+45Q+atslTqZh6OYFG6qeBrF7i9R9dkhbLlLx6AUxOxRUsW/A0vE/k3VHyHKEWqXiaJBKuNA940UoSvwmarzy84C0xOpBcXr7bK1C5K9IME3iqR1OhIUksvYydiL2xJkj4OX6sIvnWwA/a7Ypv70iAD682GG4vu7PR+zl8SCHGHDIELsT+OYn0ZtLNv6FANPMAKHS0pZ7rGQz57edke8P5VJBYcRunXs9UzDAYKC6nVjVDybhT4V4959UcvTEM7wRiYT/KKzHewdsrVWkEaJSDL+M7wCb44vwlmSNTyShy4zSvUQCIvePP+C8TWlu0J2qFAqYmaSMYDNQQ/tpn8/EWQQ0kSZ5PECPOCRxo5eSeIlOGnX2FAwD0I71kQ+LoUhS0Ag4c2e1SkikwWYjAS5SEMqxItdNJTkROPTTzXHidrvf9GPnYmrvCZcxdVSdoF4X2DI7jpPGCyf2mqRjH603rQjAz1CM54mM/l/Vszf5kpxuwoCxkX1pt4aT5/esvbP4KU89fKLfH108Lyusq2bwChf1q+janD+sr9NnIeGh1+TAWdAw4iFRg1GvANwDgpPH7yXZ8nu6oVa41Jk3MOycb0PdZd/IOMykJlHYcrreXsGe4vIZ+S/8Bv2+43tjGF7l1CYbl/E+QO2guU4boTDsa+dLZZwbrBg2jlnJ43+gu5N/J76m65N/hDYS1U4ykGZxBwboFiU0BJVG3kzFkNtHWkMBAHAx+21J67Mc5J+uG1BXdj3Xy7B16lYwagfmsEZJbPvb7ZM/KIn6JPd9WqZZGe5wv8jQUGVFFb2WVxo7VQsUkJplp/kylEPunyr0iPqAHOckPYJ8HZSjH9PkN7+yIkcCsoC6+liILpjeNBizsb74UG8hTn7gChjMUMloqPZwxU12LbeJSfqZPjH4UjTrhUtXcfbddc6YpTBkC2S/mVVpwynxGwF4tDVqsnfQ6M744dKELg7kpqUyJLNOUoOu0SIPELUNQi0PxxmM41cvFL06wlIdMn/o2WQ0=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: cisco.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BY5PR11MB4196.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 05a88bee-8494-4cc1-9baa-08db417e99c2
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Apr 2023 09:07:00.3950 (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: EtWDHr5TgExCyOwToVFRS0Ffwsl6hgA1uNRVsXZWYPaNLWD3/P5w2W5RKoXzeKR7FHID+wOtXSxWZRc0uBuaWA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN0PR11MB6182
X-Outbound-SMTP-Client: 173.37.147.251, alln-opgw-3.cisco.com
X-Outbound-Node: alln-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/cuI0MpQLxxjV7DYdShpXyGkd2Lo>
Subject: Re: [auth48] [AD] AUTH48: RFC-to-be 9390 <draft-ietf-dime-group-signaling-14> 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: Thu, 20 Apr 2023 09:07:12 -0000
Hi Alanna, The change in section 4.1.1 is fine to me, although I wonder whether "In these cases" would scan better than "In such a case", but I'll defer to your better judgement here! Regards, Rob -----Original Message----- From: Alanna Paloma <apaloma@amsl.com> Sent: 20 April 2023 01:29 To: lionel.morand@orange.com; mark@azu.ca; marco.liebsch@neclab.eu; Rob Wilton (rwilton) <rwilton@cisco.com> Cc: rfc-editor@rfc-editor.org; dime-ads@ietf.org; dime-chairs@ietf.org; jounikor@gmail.com; auth48archive@rfc-editor.org Subject: Re: [AD] AUTH48: RFC-to-be 9390 <draft-ietf-dime-group-signaling-14> for your review Authors and *Robert, This is a friendly reminder that we await your approvals prior to moving this document forward in the publication process. *Robert (AD) - Please review and approve of the updated text in Section 4.1.1 in the diff file below: https://www.rfc-editor.org/authors/rfc9390-auth48diff.html The files have been posted here (please refresh): https://www.rfc-editor.org/authors/rfc9390.xml https://www.rfc-editor.org/authors/rfc9390.txt https://www.rfc-editor.org/authors/rfc9390.html https://www.rfc-editor.org/authors/rfc9390.pdf The relevant diff files have been posted here: https://www.rfc-editor.org/authors/rfc9390-diff.html (comprehensive diff) https://www.rfc-editor.org/authors/rfc9390-auth48diff.html (AUTH48 changes) https://www.rfc-editor.org/authors/rfc9390-lastdiff.html (last version to this one) The AUTH48 status page for this document is available here: https://www.rfc-editor.org/auth48/rfc9390 Thank you, RFC Editor/ap > On Apr 12, 2023, at 3:43 PM, Alanna Paloma <apaloma@amsl.com> wrote: > > Hi Lionel, > > Thank you for your reply. We have updated the files accordingly. > > We will await any further changes you may have and approvals from each author and the AD prior to moving forward in the publication process. > > The files have been posted here (please refresh): > https://www.rfc-editor.org/authors/rfc9390.xml > https://www.rfc-editor.org/authors/rfc9390.txt > https://www.rfc-editor.org/authors/rfc9390.html > https://www.rfc-editor.org/authors/rfc9390.pdf > > The relevant diff files have been posted here: > https://www.rfc-editor.org/authors/rfc9390-diff.html (comprehensive diff) > https://www.rfc-editor.org/authors/rfc9390-auth48diff.html (AUTH48 changes) > https://www.rfc-editor.org/authors/rfc9390-lastdiff.html (last version to this one) > > The AUTH48 status page for this document is available here: > https://www.rfc-editor.org/auth48/rfc9390 > > Thank you, > RFC Editor/ap > >> On Apr 12, 2023, at 4:59 AM, lionel.morand@orange.com wrote: >> >> Dear Alana, >> >> Thank you for your quick feedback. >> Please find our response below. >> >> Regards, >> >> Lionel >> >> >> Orange Restricted >> >>> -----Message d'origine----- >>> De : Alanna Paloma <apaloma@amsl.com> >>> Envoyé : mardi 11 avril 2023 22:40 >>> À : MORAND Lionel INNOV/NET <lionel.morand@orange.com>; >>> rwilton@cisco.com >>> Cc : rfc-editor@rfc-editor.org; mark@azu.ca; marco.liebsch@neclab.eu; dime- >>> ads@ietf.org; dime-chairs@ietf.org; jounikor@gmail.com; auth48archive@rfc- >>> editor.org >>> Objet : Re: [AD] AUTH48: RFC-to-be 9390 <draft-ietf-dime-group-signaling-14> for >>> your review >>> >>> Hi Lionel and AD*, >>> >>> *Robert - As the AD, please review and approve of the updated text in Section >>> 4.1.1 in the diff file below: >>> https://www.rfc-editor.org/authors/rfc9390-auth48diff.html >>> >>> Lionel - Thank you for your reply. We have updated the files accordingly. Please >>> note that we have some additional queries: >>> >>> 1) You provided the following expansions for the listed acronyms: >>> >>>> GASR: Group-Abort-Session-Request >>>> GASA: Group-Abort-Session-Answer >>>> GSTA: Group-Session-Termination-Answer >>>> GSTR: Group-Session-Termination-Request >>> >>> We have added preceding text to introduce the acronyms. Please review and let us >>> know of any concerns. >>> >>> Current: >>> Additionally, the following acronyms are used in the tables below. >>> >>> GASR: Group-Abort-Session-Request >>> >>> GASA: Group-Abort-Session-Answer >>> >>> GSTA: Group-Session-Termination-Answer >>> >>> GSTR: Group-Session-Termination-Request >> >> [[LM]] Thank you! >> >>> >>> 2) Please clarify if “re-authorization request” or “Re-Authorization Request (RAR)” >>> should be made consistent. If so, which form should be used throughout the >>> document? >>> >>>>> 11) <!--[rfced] Throughout the text, the following terminology >>>>> appears to be used inconsistently. Please review these occurrences >>>>> and let us now if/how they may be made consistent. >>>>> >>>>> re-authorization request vs. Re-Authorization Request (RAR) >>>>> --> >>>> >>>> [[LM]] OK! >> >> [[LM]] Sorry 😊 The point is that there is no inconsistency issue. One is "service-specific re-authorization request" whereas RAR is a one these re-authorization command defined in RFC6733. But I realized that we have missed something: RAR should be "Re-Auth-Request" and RAA should "Re-Auth-Answer" in some places. >> Moreover the coma (,) should be removed in "service-specific, server-initiated request". Both changes are addressed below. >> >> 4.2.2. Removing a Session from a Session Group >> >> OLD: >> >> When the Diameter server decides to remove a session from one or multiple particular session groups or from all session groups to which the session has been assigned beforehand, the server sends a Re-Authorization Request (RAR) or a service-specific, server-initiated request to the client, indicating the session in the Session-Id AVP of the request. The client sends a Re-Authorization Answer (RAA) or a service-specific answer to respond to the server's request. >> >> NEW: >> >> When the Diameter server decides to remove a session from one or multiple particular session groups or from all session groups to which the session has been assigned beforehand, the server sends a Re-Auth-Request (RAR) or a service-specific server-initiated request to the client, indicating the session in the Session-Id AVP of the request. The client sends a Re-Auth-Answer (RAA) or a service-specific answer to respond to the server's request. >> >> 4.2.3. Mid-session Group Assignment Modifications >> >> OLD: >> >> When a Diameter server decides to update assigned groups mid-session, it sends a Re-Authorization Request (RAR) message or a service-specific request to the client identifying the session for which the session group lists are to be updated. The client responds with a Re-Authorization Answer (RAA) message or a service-specific answer. >> >> NEW: >> >> When a Diameter server decides to update assigned groups mid-session, it sends a Re-Auth-Request (RAR) message or a service-specific request to the client identifying the session for which the session group lists are to be updated. The client responds with a Re-Auth-Answer (RAA) message or a service-specific answer. >> >> >> 4.4.1. Sending Group Commands >> >> OLD: >> >> For example, when a server sends a Re-Authorization Request (RAR) or a service-specific, server-initiated request to the client, it indicates to the client to follow the request according to one of three possible procedures. >> >> NEW: >> >> For example, when a server sends a Re-Auth-Request (RAR) or a service-specific server-initiated request to the client, it indicates to the client to follow the request according to one of three possible procedures. >> >>> >>> The files have been posted here (please refresh): >>> https://www.rfc-editor.org/authors/rfc9390.xml >>> https://www.rfc-editor.org/authors/rfc9390.txt >>> https://www.rfc-editor.org/authors/rfc9390.html >>> https://www.rfc-editor.org/authors/rfc9390.pdf >>> >>> The relevant diff files have been posted here: >>> https://www.rfc-editor.org/authors/rfc9390-diff.html (comprehensive diff) >>> https://www.rfc-editor.org/authors/rfc9390-auth48diff.html (AUTH48 changes) >>> >>> Please review the document carefully and contact us with any further updates you >>> may have. Note that we do not make changes once a document is published as >>> an RFC. >>> >>> We will await any further changes you may have and approvals from each author >>> and the *AD prior to moving forward in the publication process. >>> >>> For the AUTH48 status of this document, please see: >>> https://www.rfc-editor.org/auth48/rfc9390 >>> >>> Thank you, >>> RFC Editor/ap >>> >>>> On Apr 11, 2023, at 2:19 AM, lionel.morand@orange.com wrote: >>>> >>>> Hi, >>>> >>>> Thank you for your patience. >>>> Please find below our feedback. >>>> >>>> Regards, >>>> >>>> Lionel >>>> >>>> >>>> Orange Restricted >>>> >>>>> -----Message d'origine----- >>>>> De : rfc-editor@rfc-editor.org <rfc-editor@rfc-editor.org> Envoyé : >>>>> vendredi 24 mars 2023 18:08 À : mark@azu.ca; marco.liebsch@neclab.eu; >>>>> MORAND Lionel INNOV/NET <lionel.morand@orange.com> Cc : >>>>> rfc-editor@rfc-editor.org; dime-ads@ietf.org; dime-chairs@ietf.org; >>>>> jounikor@gmail.com; rwilton@cisco.com; auth48archive@rfc-editor.org >>>>> Objet : Re: AUTH48: RFC-to-be 9390 >>>>> <draft-ietf-dime-group-signaling-14> for your review >>>>> >>>>> Authors, >>>>> >>>>> While reviewing this document during AUTH48, please resolve (as >>>>> necessary) the following questions, which are also in the XML file. >>>>> >>>>> 1) <!-- [rfced] Please insert any keywords (beyond those that appear >>>>> in the title) for use on https://www.rfc-editor.org/search. --> >>>> >>>> [[LM]] Nothing to add. >>>> >>>>> >>>>> >>>>> 2) <!--[rfced] For clarity, may we update this sentence below? >>>>> >>>>> Original: >>>>> If the Diameter server accepts the client's request for a group >>>>> assignment, the server MUST assign the new session to each of the one >>>>> or multiple identified session groups when present in the Session- >>>>> Group-Info AVP. >>>>> >>>>> Perhaps: >>>>> If the Diameter server accepts the client's request for a group >>>>> assignment, the server MUST assign the new session to each (one or more) >>>>> of the identified session groups when present in the Session- >>>>> Group-Info AVP. >>>>> --> >>>> >>>> [[LM]] We agree! >>>> >>>>> >>>>> >>>>> 3) <!--[rfced] May we update instances of "service-specific auth" to >>>>> be "service-specific authorization"? >>>>> >>>>> Original: >>>>> When sending the response to the client, e.g., a service-specific auth >>>>> response as per NASREQ AA-Answer [RFC7155], the server MUST include >>>>> all Session-Group-Info AVPs as received in the client's request. >>>>> >>>>> Perhaps: >>>>> When sending the response to the client, e.g., a service-specific authorization >>>>> response as per NASREQ AA-Answer [RFC7155], the server MUST include >>>>> all Session-Group-Info AVPs as received in the client's request. >>>>> --> >>>> >>>> [[LM]] in the present case, it can only be "authorization". And, as it is "e.g." it is >>> fine to say "service-specification authorization". >>>> >>>>> >>>>> >>>>> 4) <!-- [rfced] We are having trouble parsing the latter part of this sentence. >>>>> Please consider whether the suggested update correctly conveys the >>>>> intended meaning. >>>>> >>>>> Original: >>>>> In such case, the response to the group command MUST >>>>> NOT identify any group but identify solely the single session for >>>>> which the command has been processed. >>>>> >>>>> Suggested: >>>>> In such case, the response to the group command MUST >>>>> NOT identify any group other than the single session for >>>>> which the command has been processed. >>>>> --> >>>> >>>> [[LM]] The node can request to process a request for all sessions assigned to >>> one or multiple groups identified in the request. But the receiving node can decide >>> to treat the request only for the Session-Id included in the request. >>>> >>>> Proposed clarification: >>>> >>>> OLD: >>>> >>>> In such case, the response to the group command MUST >>>> NOT identify any group but identify solely the single session for >>>> which the command has been processed. >>>> >>>> NEW: >>>> >>>> In such case, the response to the group command MUST >>>> NOT include any group identifier but only the Session-Id identifying the >>> session for >>>> which the command has been processed. >>>> >>>>> >>>>> >>>>> 5) <!-- [rfced] Please review each artwork element in the xml file. >>>>> Specifically, should any artwork element be tagged as sourcecode or >>>>> another element? >>>>> --> >>>> >>>> [[LM]] OK. None of the artwork element should be tagged as sourcecode. >>>> >>>>> >>>>> >>>>> 6) <!-- [rfced] Is the following general guidance for future >>>>> registries, or is it guidance for IANA in setting up these two >>>>> registries and it should be removed since the registries have already been >>> created? >>>>> >>>>> Original: >>>>> The AVP names can be used as registry names >>>>> --> >>>> >>>> [[LM]] only guidance for IANA. Can be removed when processed. >>>>> >>>>> >>>>> 7) <!-- [rfced] Would you like the references to be alphabetized or >>>>> left in their current order? >>>>> --> >>>> >>>> [[LM]] no specific preference. It is actually based on the first occurrence but any >>> order would be fine for us. >>>> >>>>> >>>>> >>>>> 8) <!--[rfced] We have lowercased "Service-Specific" in the sentence >>>>> below, as there are case no occurrences of the capitalized form used in RFC >>> 6733. >>>>> Please let us know if you have any conerns. >>>>> >>>>> Original: >>>>> As in [RFC6733], the term >>>>> Service-Specific below refers to a message defined in a Diameter >>>>> application (e.g., Mobile IPv4, NASREQ). >>>>> >>>>> Perhaps: >>>>> As in [RFC6733], the term >>>>> 'service-specific' below refers to a message defined in a Diameter >>>>> application (e.g., Mobile IPv4, NASREQ). >>>>> --> >>>> >>>> [[LM]] OK! >>>> >>>>> >>>>> >>>>> 9) <!--[rfced] Should Tables 2 and 3 have titles? Please review, and >>>>> provide titles if desired. --> >>>>> >>>> [[LM]] OK! For sake of clarity: >>>> >>>> OLD: >>>> >>>> Table 2 >>>> >>>> NEW: >>>> >>>> Table 2: Group Authorization Session State Machine for Stateful Client >>>> >>>> OLD: >>>> >>>> Table 3 >>>> >>>> New: >>>> >>>> Table 3: Group Authorization Session State Machine for Stateful Server >>>> >>>>> >>>>> 10) <!--[rfced] How should the following acronyms that appear in >>>>> Tables 2 and 3 be expanded? Would it be helpful to include text that >>>>> precedes Tables 2 and 3 to define the expansions of these acronyms? >>>>> >>>>> GASR >>>>> GASA >>>>> GSTA >>>>> GSTR >>>>> --> >>>>> >>>> >>>> [[LM]] it would not arm to list all of them: >>>> >>>> GASR: Group-Abort-Session-Request >>>> GASA: Group-Abort-Session-Answer >>>> GSTA: Group-Session-Termination-Answer >>>> GSTR: Group-Session-Termination-Request >>>> >>>>> >>>>> 11) <!--[rfced] Throughout the text, the following terminology >>>>> appears to be used inconsistently. Please review these occurrences >>>>> and let us now if/how they may be made consistent. >>>>> >>>>> result code vs. Result-Code >>>> >>>> [[LM]] No inconsistency here. "result code" is a value. "Result-Code" is the AVP. >>>> >>>>> re-authorization request vs. Re-Authorization Request (RAR) >>>>> --> >>>> >>>> [[LM]] OK! >>>> >>>>> >>>>> >>>>> 12) <!-- [rfced] Please review the "Inclusive Language" portion of >>>>> the online Style Guide <https://www.rfc- >>>>> editor.org/styleguide/part2/#inclusive_language> and let us know if >>>>> any changes are needed. >>>>> >>>>> For example, please consider whether "natively" should be updated. >>>>> --> >>>> >>>> [[LM]] only one occurrence. >>>> >>>> OLD: >>>> >>>> Newly defined Diameter applications may natively support Diameter >>>> session grouping and group operations. Such applications provide >>>> intrinsic discovery for the support of session grouping capability >>>> using the assigned Application Id advertised during the capability >>>> exchange phase described in Section 5.3 of [RFC6733]. >>>> >>>> NEW: >>>> >>>> Newly defined Diameter applications may intrinsically support Diameter >>>> session grouping and group operations. In such a case, there is no need >>>> of a specific discovery mechanism for the support of session grouping >>>> capability besides the discovery of the Application Id assigned to the >>>> application advertised during the capability exchange phase described in >>>> Section 5.3 of [RFC6733]. >>>> >>>>> >>>>> >>>>> >>>>> Thank you. >>>>> >>>>> RFC Editor >>>>> >>>>> >>>>> On Mar 24, 2023, at 10:05 AM, rfc-editor@rfc-editor.org wrote: >>>>> >>>>> *****IMPORTANT***** >>>>> >>>>> Updated 2023/03/24 >>>>> >>>>> 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/). >>>>> >>>>> 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/). >>>>> >>>>> * 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>. >>>>> >>>>> * 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 (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, 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 >>>>> >>>>> * The archive itself: >>>>> 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 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/rfc9390.xml >>>>> https://www.rfc-editor.org/authors/rfc9390.html >>>>> https://www.rfc-editor.org/authors/rfc9390.pdf >>>>> https://www.rfc-editor.org/authors/rfc9390.txt >>>>> >>>>> Diff file of the text: >>>>> https://www.rfc-editor.org/authors/rfc9390-diff.html >>>>> https://www.rfc-editor.org/authors/rfc9390-rfcdiff.html (side by >>>>> side) >>>>> >>>>> Diff of the XML: >>>>> https://www.rfc-editor.org/authors/rfc9390-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/rfc9390.original.v2v3.xml >>>>> >>>>> XMLv3 file that is a best effort to capture v3-related format updates >>>>> only: >>>>> https://www.rfc-editor.org/authors/rfc9390.form.xml >>>>> >>>>> >>>>> Tracking progress >>>>> ----------------- >>>>> >>>>> The details of the AUTH48 status of your document are here: >>>>> https://www.rfc-editor.org/auth48/rfc9390 >>>>> >>>>> Please let us know if you have any questions. >>>>> >>>>> Thank you for your cooperation, >>>>> >>>>> RFC Editor >>>>> >>>>> -------------------------------------- >>>>> RFC9390 (draft-ietf-dime-group-signaling-14) >>>>> >>>>> Title : Diameter Group Signaling >>>>> Author(s) : M. Jones, M. Liebsch, L. Morand >>>>> WG Chair(s) : Jouni Korhonen, Lionel Morand >>>>> Area Director(s) : Warren Kumari, Robert Wilton >>>>> >>>> >>>> >>> ______________________________________________________________________ >>>> ___________________________________________________ >>>> >>>> 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. >
- [auth48] AUTH48: RFC-to-be 9390 <draft-ietf-dime-… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9390 <draft-ietf-d… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9390 <draft-ietf-d… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9390 <draft-ietf-d… lionel.morand
- Re: [auth48] AUTH48: RFC-to-be 9390 <draft-ietf-d… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9390 <draft-ietf-d… lionel.morand
- Re: [auth48] [AD] AUTH48: RFC-to-be 9390 <draft-i… Alanna Paloma
- Re: [auth48] [AD] AUTH48: RFC-to-be 9390 <draft-i… lionel.morand
- Re: [auth48] [AD] AUTH48: RFC-to-be 9390 <draft-i… Alanna Paloma
- Re: [auth48] [AD] AUTH48: RFC-to-be 9390 <draft-i… Alanna Paloma
- Re: [auth48] [AD] AUTH48: RFC-to-be 9390 <draft-i… lionel.morand
- Re: [auth48] [AD] AUTH48: RFC-to-be 9390 <draft-i… Rob Wilton (rwilton)
- Re: [auth48] [AD] AUTH48: RFC-to-be 9390 <draft-i… Marco Liebsch
- Re: [auth48] [AD] AUTH48: RFC-to-be 9390 <draft-i… Mark Jones
- Re: [auth48] AUTH48: RFC-to-be 9390 <draft-ietf-d… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9390 <draft-ietf-d… lionel.morand