Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-lamps-5g-nftypes-08> for your review
John Mattsson <john.mattsson@ericsson.com> Mon, 09 January 2023 06:45 UTC
Return-Path: <john.mattsson@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 ABB28C14CEE5; Sun, 8 Jan 2023 22:45:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, 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 M-JkFqJFripS; Sun, 8 Jan 2023 22:45:13 -0800 (PST)
Received: from EUR02-VI1-obe.outbound.protection.outlook.com (mail-vi1eur02on2041.outbound.protection.outlook.com [40.107.241.41]) (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 A5A36C14F740; Sun, 8 Jan 2023 22:45:12 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RH0G0+eAsSlHFbepnhZfzA6iea6uYODMXoWp/YNZXXRlYQZhqNkhZomiYjoZuzWew+NlboAgSF8zu1jSUR1SvmmOQ841unp6aIHiUH1UzI5AEm6PGpoHugcf5KRpkVOCUMCw+zKiyMJSvU+GTuphJfR9Z2yHyRiL5UxrY83eWhwxVq1U3PJnW8yjux38MVIvARpjXuQQoIqPxd5DH5yOnX835Flou2BmU0CCSUjdfIIToRWED7qExK3sN6P4JebXT7aumyQEnwHcJYU/1+TBfcvb+fw/9Cd0+cM4GhEB6Wg3gsWtRflB/2ph/5v83ehkMeg724Cu8uiZkRvIswOv1g==
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=A9H4LxoXT+6aae7ZXZpepBEOIIuvhw4h6IV7JgzJjtg=; b=D/oTl61vfwDo+pHq//mrWlSc4Vf030aNoo987Fcqz9tKLfg8h1A6R77KduauUOGoEtKcTcjrq7e5ouxUtyvtQrLhYiAipnem9hPP/mmrXYMq83oVnywjHzz0AZO8wzkx8u/MxLwcmlTMAJZb4duAnsn2dfbepqV8TvUtZUdQXSeVM3TjqS0ggIpnsk2qpkco+pWkM4/elF4IPIwCYllAKuX7jKrF0DPufP0A1CirR547O6yzLctLe2gV408tBHVhYFU6+IDy2uRwN+7HpNG+HyeWtCQuA424p74JH26W35klHzPjYX0vyEVwh3h7a51t+xvMdp9OqY6okrfvVVQdsA==
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=A9H4LxoXT+6aae7ZXZpepBEOIIuvhw4h6IV7JgzJjtg=; b=uSJNXvKNlFGvFQ+bwMM1JJ+0EkzwU8gesFRrPo3tTXttamU/tfaHCtUCM6yhqbYdFO6vhRkeJlMBSy1/3KCtzkXuoVGam953aPUKCsBtFBb/1PKabvEyEok8bXPWsS7RXiZd+93JJHguzEvlv73UB//psk46xKmk4bqIT6kTsG8=
Received: from HE1PR0701MB3050.eurprd07.prod.outlook.com (2603:10a6:3:4b::8) by DB5PR07MB9513.eurprd07.prod.outlook.com (2603:10a6:10:48c::10) 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 06:45:07 +0000
Received: from HE1PR0701MB3050.eurprd07.prod.outlook.com ([fe80::fc77:42d2:1bc6:ec49]) by HE1PR0701MB3050.eurprd07.prod.outlook.com ([fe80::fc77:42d2:1bc6:ec49%12]) with mapi id 15.20.5986.018; Mon, 9 Jan 2023 06:45:06 +0000
From: John Mattsson <john.mattsson@ericsson.com>
To: Sandy Ginoza <sginoza@amsl.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>
Thread-Topic: AUTH48: RFC-to-be 9310 <draft-ietf-lamps-5g-nftypes-08> for your review
Thread-Index: AQHZFAk7EX+waGde9UGCV4sKoe8LT653AYEAgAA/hYCAAQfA0IAAuzkAgABxtluAANShgIAAsm5pgA2Uo4CADTE9Dg==
Date: Mon, 09 Jan 2023 06:45:06 +0000
Message-ID: <HE1PR0701MB3050CF4D537C3C1B9B16F64289FE9@HE1PR0701MB3050.eurprd07.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>
In-Reply-To: <C1347608-FE0D-4403-82E4-B1BB059BCC7D@amsl.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
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: HE1PR0701MB3050:EE_|DB5PR07MB9513:EE_
x-ms-office365-filtering-correlation-id: dcb011eb-e2c1-4a47-30ab-08daf20d0b45
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: i+grqgm0QGkNg4bh0UQUcrY83yYvssFIQRXYmtHp7Vr/rGPh9MroQQLLJgxVhHKcS/Nrwr9DX6Or3adKH2kKUWG0KalaIgSb6H/WQVFeYf2enS5fQt09fCbb4kCSzEDC4Fx9DiHBrxE12KVn6/PEi80abLjkdwpyP7X72viPS//jLknLOq9ZQLcddAxA+j1HfYxFbbM70yMmOeTdhVTToMfYKWTKs6a8o+1qG9vexceqzHM1GNJ296MyZ1ahK8MysXInCCbWLi/h3RpBWCSBDKsXhMwbP2tFuT+g8VfhveojBfCwLYpVdi30FTMjLm+74tRZnoKmhOHbWepnNYroteq1RtrU03jiQJ9CwkoIWYUQhgFiFJ1fvOXDw+WtBaI4vrsdHwh/xPzs7mn6kjsyLzRNTGB6GQPGrjWMEgqVNcr1w/oXiemcb7ilJOedpjYYspXxDh7sQhEHLotGibXKnVtVjRMGB0llClkMdUu/8pYqRjc774qH6jnh+OMylTTleayOZLA1CaQHul2clKcJFsrXUIPrxd7WSIqgqZXin6dn7Axk02OFlraKL0mOIxLjUEEK73rlJB/kH1lWLz0Xas4lPGPhUOBH5WCe4eEp5rd83uVYxy9wNH7/o1QXgSpBtrP06umyFFx1zci8Rf7aovMLYmPcWyJyQuUMPNGNOb2Ek0leayN4BhAEYDZHxVjL0iFyD2IAsw3k5LAydNpvM5vpwNtWCdeioauANDkRwzO9MMZNbh6VpGMagtO/jwBR3TmBJvECRmF/x9D+KmTZ/w==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:HE1PR0701MB3050.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230022)(4636009)(346002)(136003)(39860400002)(396003)(366004)(376002)(451199015)(99936003)(66574015)(83380400001)(122000001)(82960400001)(21615005)(166002)(86362001)(2906002)(44832011)(41300700001)(30864003)(52536014)(8936002)(5660300002)(38100700002)(55016003)(53546011)(6506007)(9686003)(478600001)(66446008)(26005)(8676002)(966005)(64756008)(6916009)(316002)(66476007)(4326008)(186003)(7696005)(66946007)(91956017)(71200400001)(54906003)(76116006)(66556008)(38070700005)(33656002); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: RD2ev40ZGcO2csJnPPcVkO0TOaofdPKauv10Sx0mwHuMTUyQolijn6gKI3ZvLB8j/NUiwkOQhOe98vGTAkSt2BhZJZxBceZcMtG/nS8pno3q8NhXi9cmcNRvHCmvMwBOJcj9ouTJYcEvjAsxWGTYEka81v71lDdbFUssdczbnzy7H3l+3YK4xXGSweJHK5L3SKVuCQz/UQiQuNgM1C8gf8ePZUOU+fSWZQ8Uy8+N8q8o5YUZqBHskGwVSTcaU1FX1RJOGoFzvNR/hXe7vo7isuyXr1V1Eucq2GPPasdQC5HFaR4OsE/J2tp7gDtZs2tgxoIqK2ZPHp9z9adhR81BcS2r2zn8Q8CM1KWHPW5uJxTEAMBnLXKm2OVkCIHSuAgPYlD7RkurVYSUaM9R1HtZXw1g9iIptW7roTH9ycTi2ipMuCb08X7RtgEv0wbuATIoqgkmK1Wm7oO3+Q60FScfA00m/q/9AZGZjjqDUMK7AVUwHfVy50LveQOuOg6fXZ+UO+yI9P0y7JskjAUm4eloS/oXA6lnFHZgy7LqrVSrpsfpiGPAHbLr01bq79rlWMCEVqJ9Xl8RLt8Nl14Np8cSoyTWsCzcuHFtkQ5UsvcfrsSARA4AF0Blhs2s7lg8Y1pvbgQTJmFKeJGkC9dXEXTH9gNdKtuv3Ec+TBm7yzge3XVjUdMlujQY4IbUiyDufVJv9ScdfFICII8qUaO9GquLjTcljcyajSnqBSaBIPG7pRFjMAepH/WsC/o3XyAfaaN8II9ApYKyfIr2prQJbqbGdp4gxty+iYhPV/lvgd31qihyEy7zlnYL6O7nR6q0hDS1JNKw9Eek7jSodyidf6nOt8jwlXpJfmuU2e84aoQlrPn+RqmagmORxQEWi7jntGqCpb0g7fR8SMTVGP2f8Rq2TVOIrp09LSkw64f6CWvzOiQyd6tLQx6sHA6iyGvLJqehuXj0UUfO8z1AH9l+6uONdeVKPb7QaEeA7rJjRDRPCyyP+Hqi3xmA4hptgrld7vDOTMZmnuqyW4ms6OW1/5mAqkzRTqp12fBZF0rOIxfi4J5Z8Ry8djYRKguhEiH7tN71sHYu78XpCrXJ0XNqfOcGFTX93eVG5wE+cDiaXJVsEdXY8naEYpxdHTdskwXno2XJU/O3AlswZRpuUs9BaTgR0KZU0YtJ7o44JneGYIm+oosidh5/14ttrt211NMlXpN23E8GqQyA0A7DJjwrd5m8e0xHW65XehMADA34vgdM9aOFp0jG9EpTLRXqIeh45+2T5WzC5Zk5P25JSnmdi8r9dTvgVRDBK/Zk5t785SXX2DOP9K3wwIsyj8KMEUrs8i24B0BTDu0ShI6EYvh6v2rLxy81/ajM2G6IiEvPNLHcK20l4nCRYrtNb2uo+EVainTT3V1Vti8nSITFnO0ZSrLhooq2bRgXpgRjh0Vp3/GwDOhFKaAhXRCTHpmRxbL5Bez7Xl9r2I5mKmYJMlsXP+zTJnBrZZfqyx1Cglj/r0CYAa+4LCfqIbwx8FwxVKWje85DF0iXTxU/ITeEVhp0yGKJgp4op/8XJQPTehMcgB0hqVsWmDlCppFiMX6xwuy1p4YZRQqKV54H/snwE/CNCoTy+VDulT4GYgDaRSQSxzkEIJE=
Content-Type: multipart/mixed; boundary="_004_HE1PR0701MB3050CF4D537C3C1B9B16F64289FE9HE1PR0701MB3050_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR0701MB3050.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: dcb011eb-e2c1-4a47-30ab-08daf20d0b45
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jan 2023 06:45:06.3458 (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: n961in+clgFUXmUu+q88PZMUTX9LN0w9DX8/ZziwycLOgIL179dYzZCN+6i/VWopZh2KW3xQI3ikBDVqpknU20bFoOG5f+huxigbOHR7acc=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR07MB9513
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/0joXrvi3MWWhQ-7WYIcVcji2U1c>
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 06:45:18 -0000
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 > > >
- [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