Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-lamps-5g-nftypes-08> for your review
Daniel Migault <daniel.migault@ericsson.com> Mon, 09 January 2023 20:41 UTC
Return-Path: <daniel.migault@ericsson.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 43820C1BE88D; Mon, 9 Jan 2023 12:41:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-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_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 qHDFOVH9CFYn; Mon, 9 Jan 2023 12:41:35 -0800 (PST)
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (mail-bn8nam12on2045.outbound.protection.outlook.com [40.107.237.45]) (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 EEB15C1BE879; Mon, 9 Jan 2023 12:41:34 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lmq5oxtbvcM0GYF0Eyyou0FU7dyhaspemNewNmAQi3Ba2eYJrDi9CopS8Acolp9Rp32+pdUgeftDnF/tk6rXQX3xq78tEMeh5nqS4lfExDqDok/HulKvKsT41HB2AEjWWGVMg6GJr4gRM3aYu1mvmIuJqJF4rlInt2bztkHi2QzjuO9UYaOHCakx1ZnmhV1By9nSUkKkCz9iPJrETuovp55DjP3ftKoR/DU9+Ljo88qfqLnuZJFGJPf80J6JjWxgKKEXv71M8hXr4CzBVfeqK4CfMSZ6kJzOd28yvSAVVG4UD4S4lgkCWlnJXqRtmla05b+/7Sec6z9t2MhfGRe1XA==
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=3BYdCwVyIISqHLEXevOHHSC2Wi/6o96KvnIZyejBdz0=; b=ams5+lhRwCBxyWV1DzZPfhv502QXdI0jK5aj7jLR9nDIW27HD5sn1J5FeMofzUYsSCcvAGyQ6b7kuDX2QgXZ7Cur219d4rZKgd7gW13xS/aUVd4NcRQiPKj4Fw5DMTiG0/ITPjTONl5guNQHlx+hVCKz5U9XYJPzj60j8HNS7H57Y/KJxxfuTEgvXuH0/CJEnUroClIxs8uXO2Hl4S8pJTWrBQLP1LLyTM6ip0FoN4dTnLzuJz2njOMuuvRKabnzT8RzldXdJbt+0zSTFaj8Op2zEHiJjw3V/53+70vxL2cvoZJYqA5A8ve1Z5BWfuaTlyLkVQygce2X3TQ+mH+Xgg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=3BYdCwVyIISqHLEXevOHHSC2Wi/6o96KvnIZyejBdz0=; b=s5Ggmc+2LEBWtijeiG4XJW5kTrEbvWwnkUuk6xDTsQjqRoyNXh79EqhJxmn21LrzosvGg17fMjinwHdM9TWGPCL/SwDOwkN/4yLWFpRf0L8QB4TghlFTY+eFXeSiDzWeu1nwvAfxrcm6PE77nIA86eDcy7mKq1EOWiF6MlMJlEU=
Received: from DM6PR15MB3689.namprd15.prod.outlook.com (2603:10b6:5:1fb::27) by SA1PR15MB5078.namprd15.prod.outlook.com (2603:10b6:806:1dd::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5986.18; Mon, 9 Jan 2023 20:41:26 +0000
Received: from DM6PR15MB3689.namprd15.prod.outlook.com ([fe80::df1c:18d9:511b:c6]) by DM6PR15MB3689.namprd15.prod.outlook.com ([fe80::df1c:18d9:511b:c6%4]) with mapi id 15.20.5986.018; Mon, 9 Jan 2023 20:41:25 +0000
From: Daniel Migault <daniel.migault@ericsson.com>
To: Lynne Bartholomew <lbartholomew@amsl.com>, John Mattsson <john.mattsson@ericsson.com>, Sean Turner <sean@sn3rd.com>, Russ Housley <housley@vigilsec.com>
CC: Roman Danyliw <rdd@cert.org>, "lamps-chairs@ietf.org" <lamps-chairs@ietf.org>, "auth48archive@rfc-editor.org" <auth48archive@rfc-editor.org>, Tim Hollebeek <tim.hollebeek@digicert.com>, "lamps-ads@ietf.org" <lamps-ads@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Thread-Topic: AUTH48: RFC-to-be 9310 <draft-ietf-lamps-5g-nftypes-08> for your review
Thread-Index: AQHZFAk91tA0Zzsi8UedhDNR10/kjq53AYEAgAA/hYCAAQrEAIAAuDQAgAByXYCAANP7gIAA1U4AgA1xw4CADTJXAIAAgFsAgABDtoCAACV1ow==
Date: Mon, 09 Jan 2023 20:41:25 +0000
Message-ID: <DM6PR15MB3689987256B2663296D09864E3FE9@DM6PR15MB3689.namprd15.prod.outlook.com>
References: <20221220002240.6268A1BA406F@rfcpa.amsl.com> <B8170B54-A720-41BE-A9D7-0AF6EE96C0BD@vigilsec.com> <0B863161-56FD-434E-A62D-71A9915D802C@amsl.com> <HE1PR0701MB30503FAA8200D8BD4653450289EB9@HE1PR0701MB3050.eurprd07.prod.outlook.com> <CF3646AE-FD26-495E-8801-65141F234401@amsl.com> <HE1PR0701MB3050A9E2D61522ED3BEF710589E89@HE1PR0701MB3050.eurprd07.prod.outlook.com> <D5C78B9B-E186-4C96-8ED4-745CDE24954E@vigilsec.com> <HE1PR0701MB3050BBA73506D92BD1D2710089E99@HE1PR0701MB3050.eurprd07.prod.outlook.com> <C1347608-FE0D-4403-82E4-B1BB059BCC7D@amsl.com> <HE1PR0701MB3050CF4D537C3C1B9B16F64289FE9@HE1PR0701MB3050.eurprd07.prod.outlook.com> <19E7C207-3523-4BFC-95BC-5D06D89CDEB4@sn3rd.com> <B5D86187-305A-40A6-BC8F-E59E64AF1461@amsl.com>
In-Reply-To: <B5D86187-305A-40A6-BC8F-E59E64AF1461@amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=ericsson.com;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: DM6PR15MB3689:EE_|SA1PR15MB5078:EE_
x-ms-office365-filtering-correlation-id: fc6c5db9-f504-4951-c8bf-08daf281e069
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: UGT/RuUI+XhAUhQsd7YGV7cDTzqcOig7w+J+Qm+YAng0B8BZypEK3IbZlK5U6xZfcKPGC4omiN5y72s44MLFDZoacE9WPjAxPwk6OD0GiEV71sREjtay93BcDRtiqCntl9DgVtY/x4aiitz8ycxDWZxhFvYh6GVUOaA2rqgyJDjBOjds4oOupbVL4Lh9M9d1aGAoTDFFO3rKixdIYC8cVv2xei580dVnrYktbYtQAVo3IQCiEUQ/EdPQNdGbN8Cqyanz9k0K0c5fC1pGBWhVeTjy4h9BUlMZjl9ZXUaWz+BXq+DsjuMzwP4/gG+iKDi2VOnLC5IWU92OlmqOb/AnowfVUvJeYoypalUHgA6eoZKzS8FhR5J1bLGBu2zutfb9yln2bp7TDpEyadRsXvFeVWjBcSylDcpivnnrEMSTY2leFsDxC7gk8f2eI1HpIzc2354XIUJsmjRUucOZd1bzxaiFznW4SO7lKqGpjN6TUlr+for4+ip6nqqUdHVOfO9ZPi8XmcGciaSSbmK22kiVL0AtpjxDJyRUjiNBZWxhCUQcU9kMtRzMVaUMXpHyfdyAhrVk/tefaQagn6ml2uLIxX3PViZn/u9TXYfx7ksDE6b8dO+MW+ESW33luUnabuLrQldpCMXxSIdTqE2a8PpVxzG1n0eoLwhb4HVK3DoBSGIYhemajQvpOHbmps2GzoFgxciTUiHAd2hwiPcYrmRyUWUMBpVzYll0HUz0rQteWtyOSxktzTXINqV+iNRf6dlI5WSqy92Ois5kGf13Ou/x6sJZvAdb/tzz8e1NzSMhcZU=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM6PR15MB3689.namprd15.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230022)(4636009)(396003)(366004)(136003)(346002)(376002)(39860400002)(451199015)(66946007)(52536014)(41300700001)(44832011)(8936002)(30864003)(5660300002)(2906002)(66574015)(8676002)(91956017)(64756008)(66446008)(66556008)(66476007)(76116006)(316002)(7696005)(110136005)(71200400001)(54906003)(966005)(33656002)(478600001)(53546011)(6506007)(9686003)(4326008)(186003)(55016003)(26005)(83380400001)(86362001)(38100700002)(82960400001)(122000001)(38070700005)(579004)(19607625013); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: 9p8Me/74zyheQelZcyl0OtJQvekq5/GWovN4L7OsL0AdcoOe0Yc6fT7k6nGTuyDLg2iSdRvnJvS0cphfKA7N7vEgaablLDGLyXgvPdO77jB0Hl9HYiKiXm2I3cXcefy5N2gtJFuPQDnMwYEbP4gC0sx2DOFpv/cRLqS+X3/Ac2UrEcl2/YPCd+eULHL8Lyo4KFhPN+yjvU+IxM5rmarKL3dtHu3kaFbI/Z4bQ95RX7+yOmvzWK7b7Kx1HKgGq8MzpH2uUyY+6UxvLt1vwJpVWsM8TAQ7tWbhVobvCBTBRehS4QEEIz5jhpC6tr37BTG91exh7VMAfnNHoNlBKDAi8zrEQGjG1ARECHEdHQYm4UxOZ7Ty94QhByfBX65CwlJdsYw/i2XVS7zvIxVuFWXmLLpVwSLSrirR2ev012NryI+P5k4cVeXYnk3f8YIpIdmkHiEos6mzsOiFFyr0anUR4+vSm9PlEHEXPqiTjxs20KDaPxDEwVziSWbM6YgSn65lZ9o84lBPoXsy1whIwbiuJgwwGN7psmft29EAje4A0m6igXtXht/PpOzAJeLd8cZhHBhUevL32HQ6ZQjXB/YHLROa5uD36YGNoD3repGoTyfM7aSDvEcjngfpDPuvLPxEV1MEWV7LKDBKGXZEUhyHyBD3qNJMcflm9KE93WUaUqoMYTLqdlKxO+KHwAITMx62ntjuLrXpk/PF9JKhbdXvQLZq2hW5ERI1+JVV21PDZqgWpKbBMjn5qEcFuz+5Vnz7FIAvmNUmxdMz+rRaV02Kp9PddGBhLFfw4boIky+gL2UhlNdXGwj/fLjLWrZWbIodH5Q8A4T1eCeVOM7Dap4eXOEzuU5GaiP7jBAGAnHKgVRq8PgzEBwpgyshNLEXD0vW9l6GRib3NdZvZ3YgasqwbTtJ1JgRz5Y5JFvKqo8toqOKpnmMhnPfkoBCuWNntUSADzTUkUtKnVQI58c1cYIceHNWSa10tdcQhPx5AeKIeHSZ9AhE72VNOzh3BzfxZd0MOQOweRFxZoN+R8mGQoFOEQgPEhTZmUTKJC63McRdvRa87weyzEGa3U2Z8xdJR9nEASRrfbS+7qyp9sZmkobZ388uiFEk+VnxCXVqg7L1YY/tl8zEU3ZfRERNvc0P8RAGlyNcFfZZQy0ZcMRczx/N12iVJ/utRNoScoVghSxXXW+EVo2uBD5hHl16FjDLwdpIFbNCr+l9zAi58o2sv1ohdUcanny5urMUMqFqk8Dl9Z6DVvYelfMy0cRId2ObXWGusaZyMKgT14kcL/+GnpKbMEUSlzLJcBtMeE0NkGzJ4AKtWuve5V6RM75/q4bvhfR1oTuRIU2lhsdi3qsDOV/tQuyxHAQ3qZh0A0mmS62duHZ5zuw553QQ9JVf8tHOFLpHuUhoDCbn0dQNvMY1s+eRpm99hnRMJrYtIIDPrGa1U+wpNUTmuYbk3UVy1xV7AXpVSVROr/CGuCu2wb12KeBJZpkgK3lFioud5Qc4hebHJKg+pKJBb0OsJBYL7VQTt0oeEmV1jwwkcQnB+LUHbOay6oiPhdorFl4nOwhp/D+qNp92jdaU2bRIFKIQVhZO0Kd/
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR15MB3689.namprd15.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: fc6c5db9-f504-4951-c8bf-08daf281e069
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jan 2023 20:41:25.5609 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: z6b0bMOvN7uJ51J7Rolp4mLX/uOWxo60T+ZlHLsHKjn/pc3A22/PLeCtrAVfgaNTHYms0UpNeg3QiHmvRQMxwc6ON7QNQF/J0gR0IpU8O3U=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SA1PR15MB5078
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/QoV_SGpvfBQ-snGUkcv8LzZxs3k>
Subject: Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-lamps-5g-nftypes-08> 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: Mon, 09 Jan 2023 20:41:40 -0000
Please proceed to publication. Apologise for the delay Yours, Daniel ________________________________________ From: Lynne Bartholomew <lbartholomew@amsl.com> Sent: Monday, January 9, 2023 1:26 PM To: John Mattsson; Sean Turner; Russ Housley Cc: Roman Danyliw; Daniel Migault; lamps-chairs@ietf.org; auth48archive@rfc-editor.org; Tim Hollebeek; lamps-ads@ietf.org; RFC Editor Subject: Re: AUTH48: RFC-to-be 9310 <draft-ietf-lamps-5g-nftypes-08> for your review Happy New Year, John, Sean, and Russ! John, thank you for the updated XML file. We downloaded 3GPP TS:33.310 V17.5.0 and see that it is dated December 2022, so we used that date accordingly. The files reflecting this latest update are posted here (please refresh your browser) *: https://www.rfc-editor.org/authors/rfc9310.txt https://www.rfc-editor.org/authors/rfc9310.pdf https://www.rfc-editor.org/authors/rfc9310.html https://www.rfc-editor.org/authors/rfc9310.xml https://www.rfc-editor.org/authors/rfc9310-diff.html https://www.rfc-editor.org/authors/rfc9310-rfcdiff.html https://www.rfc-editor.org/authors/rfc9310-auth48diff.html https://www.rfc-editor.org/authors/rfc9310-lastdiff.html https://www.rfc-editor.org/authors/rfc9310-lastrfcdiff.html https://www.rfc-editor.org/authors/rfc9310-xmldiff1.html https://www.rfc-editor.org/authors/rfc9310-xmldiff2.html * Please note that we are aware of the erroneous "RFC Publisher" entries that currently appear in the References sections; this bug has been reported. We have noted your approvals on the AUTH48 status page: https://www.rfc-editor.org/auth48/rfc9310 After we receive approval from Daniel, we will move this document forward for publication. Thanks again! RFC Editor/lb > On Jan 9, 2023, at 6:40 AM, Russ Housley <housley@vigilsec.com> wrote: > > Please proceed with publication. > > Russ > On Jan 9, 2023, at 6:24 AM, Sean Turner <sean@sn3rd.com> wrote: > > I believe this is ready for publication too. > > spt > >> On Jan 9, 2023, at 01:45, John Mattsson <john.mattsson@ericsson.com> wrote: >> >> Hi, >> >> All the best for the new year! >> >> Looks great and ready for publication. 3GPP published a new Release 17 version of 33.310. I have updated the reference in the attached xml-file. >> >> Cheers, >> John >> >> From: Sandy Ginoza <sginoza@amsl.com> >> Date: Saturday, 31 December 2022 at 22:15 >> To: John Mattsson <john.mattsson@ericsson.com> >> Cc: Russ Housley <housley@vigilsec.com>, Roman Danyliw <rdd@cert.org>, Daniel Migault <daniel.migault@ericsson.com>, lamps-chairs@ietf.org <lamps-chairs@ietf.org>, auth48archive@rfc-editor.org <auth48archive@rfc-editor.org>, tim.hollebeek@digicert.com <tim.hollebeek@digicert.com>, lamps-ads@ietf.org <lamps-ads@ietf.org>, Sean Turner <sean@sn3rd.com>, RFC Editor <rfc-editor@rfc-editor.org> >> Subject: Re: AUTH48: RFC-to-be 9310 <draft-ietf-lamps-5g-nftypes-08> for your review >> >> Hi all, >> >> Happy New Year’s Eve! >> >> If I understand correctly, the document should match what appears below. The text has been updated to reflect the order of NF Types shown below - please see the updates and let us know if any other changes are needed or if you approve the RFC for publication. >> >> The current files are available here: >> >> https://www.rfc-editor.org/authors/rfc9310.xml >> https://www.rfc-editor.org/authors/rfc9310.txt >> https://www.rfc-editor.org/authors/rfc9310.pdf >> https://www.rfc-editor.org/authors/rfc9310.html >> >> Diffs highlighting the most recent update only: >> https://www.rfc-editor.org/authors/rfc9310-lastdiff.html >> https://www.rfc-editor.org/authors/rfc9310-lastrfcdiff.html (side by side) >> >> AUTH48 diff: >> https://www.rfc-editor.org/authors/rfc9310-auth48diff.html >> >> Comprehensive diffs: >> https://www.rfc-editor.org/authors/rfc9310-diff.html >> https://www.rfc-editor.org/authors/rfc9310-rfcdiff.html (side by side) >> >> >> Thank you, >> RFC Editor/sg >> >> >> >>> On Dec 22, 2022, at 11:55 PM, John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org> wrote: >>> >>> Russ wrote: >>>> That matches the most recent version of Appendix B. >>> >>> Just to be clear. Your generated table does not match >>> https://www.rfc-editor.org/authors/rfc9310.txt >>> Your table matches the most recent version of Appendix B after the ordering error that I pointed out is fixed. The document should be updated to look like your table. >>> >>> Cheers, >>> John >>> >>> From: Russ Housley <housley@vigilsec.com> >>> Date: Thursday, 22 December 2022 at 20:12 >>> To: John Mattsson <john.mattsson@ericsson.com> >>> Cc: Lynne Bartholomew <lbartholomew@amsl.com>, Sean Turner <sean@sn3rd.com>, Daniel Migault <daniel.migault@ericsson.com>, RFC Editor <rfc-editor@rfc-editor.org>, lamps-ads@ietf.org <lamps-ads@ietf.org>, lamps-chairs@ietf.org <lamps-chairs@ietf.org>, tim.hollebeek@digicert.com <tim.hollebeek@digicert.com>, Roman D. Danyliw <rdd@cert.org>, auth48archive@rfc-editor.org <auth48archive@rfc-editor.org> >>> Subject: Re: AUTH48: RFC-to-be 9310 <draft-ietf-lamps-5g-nftypes-08> for your review >>> >>> John: >>> >>> We were asked about ordering during IESG Evaluation, so I think we should keep it. >>> >>> When I use python to sort the NF Types, I get this: >>> >>> "5G_DDNMF" "LMF" "PKMF" >>> "5G_EIR" "MBSF" "SCEF" >>> "AANF" "MBSTF" "SCP" >>> "ADRF" "MB_SMF" "SCSAS" >>> "AF" "MB_UPF" "SCSCF" >>> "AMF" "MFAF" "SEPP" >>> "AUSF" "MME" "SMF" >>> "BSF" "MNPF" "SMSF" >>> "CBCF" "N3IWF" "SMS_GMSC" >>> "CEF" "NEF" "SMS_IWMSC" >>> "CHF" "NRF" "SOR_AF" >>> "DCCF" "NSACF" "SPAF" >>> "DRA" "NSSAAF" "TSCTSF" >>> "EASDF" "NSSF" "UCMF" >>> "GBA_BSF" "NSWOF" "UDM" >>> "GMLC" "NWDAF" "UDR" >>> "HSS" "PANF" "UDSF" >>> "ICSCF" "PCF" "UPF" >>> "IMS_AS" "PCSCF" >>> >>> That matches the most recent version of Appendix B. >>> >>> Russ >>> >>> >>> On Dec 22, 2022, at 1:32 AM, John Mattsson <john.mattsson@ericsson.com> wrote: >>> >>> Thanks Lynne, >>> >>> In ASCII, underscore has the value 95 and comes after all capital letters. So the ascending lexicographic order of the four types starting with "MB" is: >>> >>> "MBSF" >>> "MBSTF" >>> "MB_SMF" >>> "MB_UPF" >>> >>> @Russ, @Sean, if the sorting is not strictly needed and only for human readers, an alternative could be to remove the MUST in the sentence on ordering. >>> >>> Cheers, >>> John >>> >>> From: Lynne Bartholomew <lbartholomew@amsl.com> >>> Date: Thursday, 22 December 2022 at 00:46 >>> To: John Mattsson <john.mattsson@ericsson.com> >>> Cc: Russ Housley <housley@vigilsec.com>, Sean Turner <sean@sn3rd.com>, Daniel Migault <daniel.migault@ericsson.com>, RFC Editor <rfc-editor@rfc-editor.org>, lamps-ads@ietf.org <lamps-ads@ietf.org>, lamps-chairs@ietf.org <lamps-chairs@ietf.org>, tim.hollebeek@digicert.com <tim.hollebeek@digicert.com>, Roman D. Danyliw <rdd@cert.org>, auth48archive@rfc-editor.org <auth48archive@rfc-editor.org> >>> Subject: Re: AUTH48: RFC-to-be 9310 <draft-ietf-lamps-5g-nftypes-08> for your review >>> >>> Hi, John. >>> >>> We have updated this document per your notes below. >>> >>> The latest files are posted here: >>> >>> https://www.rfc-editor.org/authors/rfc9310.txt >>> https://www.rfc-editor.org/authors/rfc9310.pdf >>> https://www.rfc-editor.org/authors/rfc9310.html >>> https://www.rfc-editor.org/authors/rfc9310.xml >>> https://www.rfc-editor.org/authors/rfc9310-diff.html >>> https://www.rfc-editor.org/authors/rfc9310-rfcdiff.html >>> https://www.rfc-editor.org/authors/rfc9310-auth48diff.html >>> https://www.rfc-editor.org/authors/rfc9310-lastdiff.html >>> https://www.rfc-editor.org/authors/rfc9310-lastrfcdiff.html >>> >>> https://www.rfc-editor.org/authors/rfc9310-xmldiff1.html >>> https://www.rfc-editor.org/authors/rfc9310-xmldiff2.html >>> >>> We have noted your approval on the AUTH48 status page: >>> >>> https://www.rfc-editor.org/auth48/rfc9310 >>> >>> Thank you! >>> >>> RFC Editor/lb >>> >>>> On Dec 21, 2022, at 2:31 PM, John Mattsson <john.mattsson@ericsson.com> wrote: >>>> >>>> Hi Lynne, >>>> >>>>> Please let us know if we should (1) change "49" to "56" in the Introduction >to reflect the latest version of [TS29.510] and (2) update the list in >Appendix A with the seven additional values. >>>> >>>> Yes, please do change "49" to "56" and update the appendix. Release 17 is now frozen, so 56 should be the final number of NF Types in Release 17. >>>> >>>> Cheers, >>>> John >>> >>> >>>> From: Lynne Bartholomew <lbartholomew@amsl.com> >>>> Date: Wednesday, 21 December 2022 at 22:47 >>>> To: John Mattsson <john.mattsson@ericsson.com> >>>> Cc: Russ Housley <housley@vigilsec.com>, Sean Turner <sean@sn3rd.com>, Daniel Migault <daniel.migault@ericsson.com>, RFC Editor <rfc-editor@rfc-editor.org>, lamps-ads@ietf.org <lamps-ads@ietf.org>, lamps-chairs@ietf.org <lamps-chairs@ietf.org>, tim.hollebeek@digicert.com <tim.hollebeek@digicert.com>, Roman D. Danyliw <rdd@cert.org>, auth48archive@rfc-editor.org <auth48archive@rfc-editor.org> >>>> Subject: Re: AUTH48: RFC-to-be 9310 <draft-ietf-lamps-5g-nftypes-08> for your review >>>> Hi, John. >>>> >>>> While verifying the cited information in the updated 3GPP technical specifications that you listed below, we found that there are now 56 NF Types listed in Table 6.1.6.3.3-1 of [TS29.510], in contrast to the previous 49 (as noted in the Introduction: "There are 49 NF Types defined for 3GPP Release 17; they are listed in Table 6.1.6.3.3-1 of [TS29.510]". >>>> >>>> Please let us know if we should (1) change "49" to "56" in the Introduction to reflect the latest version of [TS29.510] and (2) update the list in Appendix A with the seven additional values. >>>> >>>> We will wait to hear from you before proceeding. >>>> >>>> Thank you! >>>> >>>> RFC Editor/lb >>> >>> >>> >>>> On Dec 21, 2022, at 4:44 AM, John Mattsson <john.mattsson@ericsson.com> wrote: >>>> >>>> Thanks Lynne, >>>> I approve of the document with or without changes. >>>> I have thoroughly reviewed the document. I have three suggested changes, see below. >>>> >>>> >>>> - "the NFTypes MUST appear in ascending sort order." >>>> "listed below in alphabetical order" >>>> The sort order in the normative sentence is not defined. As it is a normative MUST I think it needs to be exactly defined. I don't think the term alphabetic order is well-defined when some of the strings contain numerals and non-letter characters such as '_' and '-'. >>>> https://en.wikipedia.org/wiki/Alphabetical_order >>>> https://en.wikipedia.org/wiki/Lexicographic_order >>>> >>>> Suggestion: >>>> >>>> OLD: the NFTypes MUST appear in ascending sort order. >>>> NEW: the NFTypes MUST appear in ascending lexigraphic order using the ASCII values. >>>> >>>> OLD: listed below in alphabetical order >>>> NEW: listed below in ascending lexigraphic order >>>> >>>> - I think it is good to specify that it is 3GPP Release 17 in some more places (Release 18 will add at least 7 more NF Types). >>>> OLD: See Appendix A for values defined in 3GPP >>>> NEW: See Appendix A for values defined in 3GPP Release 17 >>>> OLD: these enumeration values are listed below >>>> NEW: these enumeration values in 3GPP Release 17 are listed below >>>> - The 3GPP references should probably be to the latest published Release 17 versions. >>>> OLD: >>>> 17)", 3GPP TS:29.510 V17.5.0, March 2022, >>>> <https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-23a450388a88802a&q=1&e=07ebb231-8128-45b6-9f8c-6c44b3e6db50&u=https%3A%2F%2Fwww.3gpp.org%2Fftp%2FSpecs%2F >>>> archive/29_series/29.510/29510-h50.zip>. >>>> NEW: >>>> 17)", 3GPP TS:29.510 V17.8.0, December 2022, >>>> <https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-23a450388a88802a&q=1&e=07ebb231-8128-45b6-9f8c-6c44b3e6db50&u=https%3A%2F%2Fwww.3gpp.org%2Fftp%2FSpecs%2F >>>> archive/29_series/29.510/29510-h80.zip>. >>>> OLD: >>>> (Release 17)", 3GPP TS:33.310 V17.2.0, March 2022, >>>> <https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-23a450388a88802a&q=1&e=07ebb231-8128-45b6-9f8c-6c44b3e6db50&u=https%3A%2F%2Fwww.3gpp.org%2Fftp%2FSpecs%2F >>>> archive/33_series/33.310/33310-h20.zip>. >>>> NEW: >>>> (Release 17)", 3GPP TS:33.310 V17.4.0, September 2022, >>>> <https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-23a450388a88802a&q=1&e=07ebb231-8128-45b6-9f8c-6c44b3e6db50&u=https%3A%2F%2Fwww.3gpp.org%2Fftp%2FSpecs%2F >>>> archive/33_series/33.310/33310-h40.zip>. >>>> >>>> OLD: >>>> (Release 17)", 3GPP TS:29.571 V17.5.0, March 2022, >>>> <https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-23a450388a88802a&q=1&e=07ebb231-8128-45b6-9f8c-6c44b3e6db50&u=https%3A%2F%2Fwww.3gpp.org%2Fftp%2FSpecs%2F >>>> archive/29_series/29.571/29571-h50.zip>. >>>> NEW: >>>> (Release 17)", 3GPP TS:29.571 V17.8.0, December 2022, >>>> <https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-23a450388a88802a&q=1&e=07ebb231-8128-45b6-9f8c-6c44b3e6db50&u=https%3A%2F%2Fwww.3gpp.org%2Fftp%2FSpecs%2F >>>> archive/29_series/29.571/29571-h80.zip>. >>>> Cheers, >>>> John >>>> From: Lynne Bartholomew <lbartholomew@amsl.com> >>>> Date: Tuesday, 20 December 2022 at 21:50 >>>> To: Russ Housley <housley@vigilsec.com>, Sean Turner <sean@sn3rd.com>, Daniel Migault <daniel.migault@ericsson.com> >>>> Cc: RFC Editor <rfc-editor@rfc-editor.org>, John Mattsson <john.mattsson@ericsson.com>, lamps-ads@ietf.org <lamps-ads@ietf.org>, lamps-chairs@ietf.org <lamps-chairs@ietf.org>, tim.hollebeek@digicert.com<tim.hollebeek@digicert.com>, Roman D. Danyliw <rdd@cert.org>, auth48archive@rfc-editor.org <auth48archive@rfc-editor.org> >>>> Subject: Re: AUTH48: RFC-to-be 9310 <draft-ietf-lamps-5g-nftypes-08> for your review >>>> Hi, Russ, Sean, and Daniel. >>>> >>>> Thank you for your prompt replies! >>>> >>>> Russ, thank you for addressing our questions so quickly! We have updated this document per your notes below. >>>> >>>> Regarding this item: >>>> >>>>>> NF type(s) / NF Type(s) / NFType(s) (in running text, e.g., >>>>>> "each NF type", "Each NFType", "that specify the NF Types", >>>>>> "If the NFTypes contain") >>>>> >>>>> The term "NFTypes" is used to refer to the ASN.1 defined type. >>>>> >>>>> The term "NF Types" is used to refer the network function defined by 3GPP. >>>> >>>> We did not make any changes. Please let us know if we missed anything. >>>> >>>> >>>> The latest files are posted here (you may need to refresh your browser): >>>> >>>> https://www.rfc-editor.org/authors/rfc9310.txt >>>> https://www.rfc-editor.org/authors/rfc9310.pdf >>>> https://www.rfc-editor.org/authors/rfc9310.html >>>> https://www.rfc-editor.org/authors/rfc9310.xml >>>> https://www.rfc-editor.org/authors/rfc9310-diff.html >>>> https://www.rfc-editor.org/authors/rfc9310-rfcdiff.html >>>> https://www.rfc-editor.org/authors/rfc9310-auth48diff.html >>>> >>>> https://www.rfc-editor.org/authors/rfc9310-xmldiff1.html >>>> https://www.rfc-editor.org/authors/rfc9310-xmldiff2.html >>>> >>>> Please let us know whether you approve this document in its current form or additional updates are needed. >>>> >>>> Please note that I will be at work tomorrow and then will be away for the Holidays. >>>> >>>> Thanks again! >>>> >>>> RFC Editor/lb >>>> >>>>> On Dec 20, 2022, at 9:27 AM, Daniel Migault <daniel.migault=40ericsson.com@dmarc.ietf.org> wrote: >>>>> >>>>> Same for me. Thanks for handling this. >>>>> Yours, >>>>> Daniel >>>> >>>> ... >>>> >>>>> On Dec 20, 2022, at 9:26 AM, Sean Turner <sean@sn3rd.com> wrote: >>>>> >>>>> All of these seem fine to me. >>>>> >>>>>> On Dec 20, 2022, at 12:02, Russ Housley <housley@vigilsec.com> wrote: >>>> >>>> ... >>>> >>>>> On Dec 20, 2022, at 9:02 AM, Russ Housley <housley@vigilsec.com> wrote: >>>>> >>>>> >>>>>> 1) <!-- [rfced] Running (abbreviated) document title (as seen in PDF >>>>>> output): Should "5G NFType in ..." be "5G NFTypes in ..."? >>>>>> >>>>>> Original: >>>>>> 5G NFType in X.509 Certificates --> >>>>> >>>>> Please use "5G NFTypes in ..." >>>>> >>>>>> 2) <!-- [rfced] Author names: Per feedback from John Preuß Mattsson >>>>>> for RFC 9175 (and per RFC 9191), we updated John's name so that the >>>>>> listing on the first page matches those for RFCs 9175 and 9191. >>>>>> Please let us know any concerns. >>>>>> >>>>>> Original: >>>>>> J. P. Mattsson >>>>>> >>>>>> Currently: >>>>>> J. Preuß Mattsson --> >>>>> >>>>> I assume that is fine with John. That is fine with me. >>>>> >>>>>> 3) <!-- [rfced] Please insert any keywords (beyond those that appear in the >>>>>> title) for use on <https://www.rfc-editor.org/search>. --> >>>>> >>>>> Digital Certificate. >>>>> >>>>>> 4) <!-- [rfced] Section 3: Should the section title be "NFTypes >>>>>> Certificate Extension" instead of "Network Functions Certificate >>>>>> Extension"? >>>>>> >>>>>> Original: >>>>>> 3. Network Functions Certificate Extension --> >>>>> >>>>> I think it would be better to use "Network Function Types Certificate Extension" >>>>> >>>>>> 5) <!-- [rfced] Should any of the <artwork> elements in this document >>>>>> be changed to <sourcecode>? Please see >>>>>> <https://www.rfc-editor.org/materials/sourcecode-types.txt>. Also, >>>>>> if <https://www.rfc-editor.org/materials/sourcecode-types.txt> >>>>>> does not contain an applicable type, please let us know. --> >>>>> >>>>> Yes. In Section 3, the artwork is ASN.1 source code. However, it is repeated in Section 4, where it is already marked as ASN.1 source code. >>>>> >>>>> >>>>>> 6) <!-- [rfced] Normative References: [TS23.003] is not cited anywhere >>>>>> in the document. Please let us know where it should be cited. >>>>>> >>>>>> Original: >>>>>> [TS23.003] 3rd Generation Partnership Project, "Technical >>>>>> Specification Group Core Network and Terminals; Numbering, >>>>>> addressing and identification (Release 17)", 3GPP >>>>>> TS:23.003 V17.5.0 , March 2022, >>>>>> <https://protect2.fireeye.com/v1/url?k=31323334-501cfaf3-313273af-454445554331-88c49a0b61d7083d&q=1&e=2266d863-4c5f-425c-8672-663bd81b0d0a&u=https%3A%2F%2Fwww.3gpp.org%2Fftp%2FSpecs%2F >>>>>> archive/23_series/23.003/23003-h50.zip>. --> >>>>> >>>>> This can be dropped. It was previously cited, but that text was dropped from the document. >>>>> >>>>>> 7) <!-- [rfced] Appendix B: Would you like to use "id-kp-clientAuth" >>>>>> instead of "clientAuth"? We ask because all other such "OBJECT >>>>>> IDENTIFIER" entries in this section seem to match up pretty well. >>>>>> >>>>>> Original: >>>>>> 06 8: OBJECT IDENTIFIER clientAuth (1 3 6 1 5 5 7 3 2) --> >>>>> >>>>> The program that was used to "dump" the certificate uses short forms of all of the extension names. I would have to edit all of them, not just clientAuth. I think we should leave this alone. >>>>> >>>>>> 8) <!-- [rfced] Please review the "Inclusive Language" portion of the >>>>>> online Style Guide at >>>>>> <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. --> >>>>> >>>>> I do not see any language that causes concern. >>>>> >>>>>> 9) <!-- [rfced] Please let us know if any changes are needed for the >>>>>> following: >>>>>> >>>>>> a) The following terms appear to be used inconsistently in this >>>>>> document. Please let us know which form is preferred. >>>>>> >>>>>> 5G System / 5G system (in running text) >>>>> >>>>> Please use 5G System >>>>> >>>>>> ASN.1 module / ASN.1 Module (in running text) >>>>>> (e.g., "an ASN.1 module", "the ASN.1 Module") >>>>> >>>>> Please use ASN.1 Module >>>>> >>>>>> id-pe-nftype / id-pe-nftypes (We ask because the same OID value >>>>>> is shown for both spellings. Also, please note that IANA uses >>>>>> the latter form on >>>>>> <https://www.iana.org/assignments/smi-numbers/smi-numbers.txt>; >>>>>> are both forms correct?) >>>>> >>>>> In Section 3, please use "id-pe-nftype" to make it match the rest of the document. >>>>> >>>>>> Side note: We also see "id-mod-nftype" (i.e., the singular form >>>>>> "nftype".) >>>>> >>>>> The singular is correct. >>>>> >>>>>> NF type(s) / NF Type(s) / NFType(s) (in running text, e.g., >>>>>> "each NF type", "Each NFType", "that specify the NF Types", >>>>>> "If the NFTypes contain") >>>>> >>>>> The term "NFTypes" is used to refer to the ASN.1 defined type. >>>>> >>>>> The term "NF Types" is used to refer the network function defined by 3GPP. >>>>> >>>>>> NFType certificate extension (2 instances) / >>>>>> NFTypes certificate extension (11 instances) >>>>> >>>>> Please use "NFTypes certificate extension" in all places. >>>>> >>>>>> subjectAltName certificate extension / >>>>>> SubjectAltName certificate extension (running text in >>>>>> Section 1 and Appendix B) >>>>> >>>>> Please use "SubjectAltName certificate extension" in all places. >>>>> >>>>>> b) Would you like spacing before the instances of "::=" to be >>>>>> consistent? >>>>>> >>>>>> For example, >>>>>> id-pe-nftypes OBJECT IDENTIFIER ::= >>>>>> ... >>>>>> NFTypes ::= SEQUENCE SIZE >>>>>> ... --> >>>>> >>>>> One space is fine. >>>>> >>>>> Russ >>>>> >> <rfc9310-JPM.xml> >
- [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-lamps… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… Russ Housley
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… Sean Turner
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… Daniel Migault
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… Lynne Bartholomew
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… John Mattsson
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… Lynne Bartholomew
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… John Mattsson
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… Lynne Bartholomew
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… John Mattsson
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… Russ Housley
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… Russ Housley
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… John Mattsson
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… Sandy Ginoza
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… John Mattsson
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… Sean Turner
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… Russ Housley
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… Lynne Bartholomew
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… Daniel Migault
- Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-l… Lynne Bartholomew