Re: [auth48] AUTH48: RFC-to-be 9310 <draft-ietf-lamps-5g-nftypes-08> for your review
John Mattsson <john.mattsson@ericsson.com> Fri, 23 December 2022 07:55 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 8C850C1522C5; Thu, 22 Dec 2022 23:55:11 -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 DS9Cf2Jjw2Ag; Thu, 22 Dec 2022 23:55:07 -0800 (PST)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on2089.outbound.protection.outlook.com [40.107.13.89]) (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 7D6D5C14CF05; Thu, 22 Dec 2022 23:55:05 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hgWTfC9GrrDvk5vxH6VnGr8dn/suSrh+Fzv6cYkk7bJHba3JiYDz4eha3bszAQCqIfm0CbMmDPQt6FWKCul7Qz+nrRaBGtPnl/VzlQZ+XO8Z23izH0jZJTQbGwhulnpkw2IDdX4ZIjOskhxZjgr+SliC0MlIe3BaLVrGtBo26fq/am9tBn3rtTZtN7fuAgKQ93DJOaOiroXGMykRvZkQFn3gt/genfxnHJHnu4o3AfCf33zaU17GCzO68mn+XKluM5Cykbk3RD2dU29VqAyrxvGL37S0QGZdAQwag2Yujtf0HcLDI03r+xFDtmTyWqnfk6Fhhitf/ZOqWr1bwlG/Xw==
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=up3gI41Gmo/KtmFoxIoN+glyaEynMn2XJy8Nqkzq4iI=; b=VYiDK/Xd+T84Q5pij1beY78dHb2JuuzzlUEEvVQlKnHxtuPyOjxudGiyyAtuJIll3EPQZ6I/eSsfgWVk9qmlEPIJ8QQbV66bLtOGeaewe1b+yt2OejCI6GyVgS9urvhptynJ+quQcE/szDLsNlz3h3C2CWUrB3obrW1W/CRELtHE6H0a02cJzj2xyq5CNCo9l1LVxpQdRmlmVJWlv+/uueZPUfxpDYrUHrTY6ejeEIPRH8y/D7dy0JNTakrU/JrpZQujR275e6do7Bx3RYKYcDpWaDZ5zO1b3VRjBDAb3xQ1dc1okezrHBcHtwmnJGYMau6o4V0i6PcHGSfhriNzeg==
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=up3gI41Gmo/KtmFoxIoN+glyaEynMn2XJy8Nqkzq4iI=; b=MRwipt4BvvKMR4O8aOX7Tmlns1ut4iigJUJi7uAvUYe4xyhny2qbdhEclUwUGDni5Apmton3vYA+dj6wKh+Faffbryd6+oz6XdpYZUqvbyRQBszBUz1/ab3eBhJfgwbBQlekKWyzF+ivgUab7BrxgWoDFRyuMEAX/pTiGCSMbHU=
Received: from HE1PR0701MB3050.eurprd07.prod.outlook.com (2603:10a6:3:4b::8) by AM8PR07MB7492.eurprd07.prod.outlook.com (2603:10a6:20b:234::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5944.13; Fri, 23 Dec 2022 07:55:00 +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.5944.013; Fri, 23 Dec 2022 07:55:00 +0000
From: John Mattsson <john.mattsson@ericsson.com>
To: Russ Housley <housley@vigilsec.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>
Thread-Topic: AUTH48: RFC-to-be 9310 <draft-ietf-lamps-5g-nftypes-08> for your review
Thread-Index: AQHZFAk7EX+waGde9UGCV4sKoe8LT653AYEAgAA/hYCAAQfA0IAAuzkAgABxtluAANShgIAAsm5p
Date: Fri, 23 Dec 2022 07:55:00 +0000
Message-ID: <HE1PR0701MB3050BBA73506D92BD1D2710089E99@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>
In-Reply-To: <D5C78B9B-E186-4C96-8ED4-745CDE24954E@vigilsec.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
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_|AM8PR07MB7492:EE_
x-ms-office365-filtering-correlation-id: a40ade61-4e7a-4a0e-f4f4-08dae4bafdfc
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: a3a4maCaFdb3bFINOzn11mRJHdrtJ+9F3MQ3nE+Ygh/uJvDtHpPXm2xlrkT3fZdS0SKOAG8Hszl1eoFpHCR5lDzh1J96heaq7Om/Qo4Tve22XPzREb7xZPNTGaxwcC6CzxT8sKeUhf6GUxvBu9BfFe8SbHabaDjGsfP7RNjL1L94F6mfejcefozFFsmW3IG2qMxsd6J6nCr56PqEzNkyxxZ0tKwTKNcp3d9f8rFcOUeqlhZ/cjP6RZRMLqLlhjp4M49JxsUDFGRT8LQfmHq7kimrWwNBotoXULD8WHeHum+Ac0+kx3+QmHQGf2SAKxlyUCb9VED5KDC2gtEdo1RDFv+FH9+COdJrUqODKUCuE9G6ya1akyg+yP473fPuM46Tk/VU0/CNddj9Bet84semEHWBAUqUAgX39SUwfHLc6eWCvR6z4lCmSGYKaoYTUJqt7itim1N+Nrzqlc6nfg8m0lwRtbA4T/ErhR0CBWswgDvVaIS2kZOfeeOt2NQE92evW8UaUhWcH2vAP71vJ6jT6HAQjooXMpQv9MeuEe20HOd1K/ZwLcBbmlHL0WsPZYYTtjMUFjFDKt6FY1wg+bsGE0Wd7sbW6wt+uPhJpJOqqgUDP5yB/FriySsphjF7J2vKAPVExhawnEJR4y5cmNBum6HTJtDSvwlJAsAMsC1RLSFmB4B2I7ruWNQ9ueDnT7D84gWagCXEM1IS8BYVxOF1+H/HxmKGZvJk3l2YLvX/jl+S477tqQouKauLMy9quH3DgbEWgW0d/+PT1gbSRPED3eG0wm3CBkx57J/5nPMScvMMwfI75xYVWyyetQzj3+v7
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)(396003)(136003)(39860400002)(376002)(366004)(346002)(451199015)(82960400001)(38100700002)(8936002)(64756008)(66946007)(66476007)(66446008)(66556008)(91956017)(76116006)(166002)(122000001)(5660300002)(4326008)(8676002)(41300700001)(30864003)(21615005)(83380400001)(478600001)(53546011)(966005)(54906003)(66574015)(6916009)(316002)(2906002)(38070700005)(44832011)(186003)(71200400001)(33656002)(26005)(9686003)(52536014)(86362001)(6506007)(7696005)(55016003)(559001)(579004); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: 6MY6nLtFdIzt9tvodDy1qbtxXeTMFQouWUDFItS44zfT9pffMIGZPCCd8RqXx+0+A9xhnoUndGy4f9t1dOJ+Zu968h6P98gcjHSPif3LPa7N4QwujXEgdFKoT2cAt3tNPNtGLkLUXVZAmCb+EMn57gQvAD/NYX0WLyhgIoryJt4LNy/8owjr9BGhGtCOfuBJdOT/8OtTr9TcBuUpbgU+LWpQlLNjNUMAqenBWsxHhmX76lgX5gMb3aTiJdM6Bp7GofWbrzhmx80JcMN6EoH5e8Axz+cscBBH9w7vd4MvyISsuLcrQ52mPowxXKZedDp4GnSUrW2WJs6c2gkxZu6+jtB9Ga0MnoQv+ygefbQUtwHlFhBbZ38XnUa8u0QuSGVUCco+5Tpe1yeH40TagL+OPLsbrNbLDEffPAsOu3P2iI4i9UPp1uHWn858o4UZTy6N5yOCcuA5pkywxh3U5uyI2EhpFmMdtFrpDcBtBDsZ4TFCYd27BjRZBMI0dndSfPl8NYK8Y+yB/ez8YDAuQstMDJRysgiqKIcMftecOvgnM8Bwsl6sMrVuNzagJAJI0L0CjOxwwom3734/O0GtZBIIdU4n/93Q/khtEwBSMBD1dB4GVoa4qmB+sNop6EiveutXkqdiAEod+zbrXPQGxDis0w6jLvu5qNIO7+y26ZXNmo/UE9QCORqLSWpqHcomUf7KFsu0pqXn6v1+ZhWYWTZFpjGBpB4nNQsOM+TkjpW0K+ez6/MBi45yedgMpUE8uEWsd4r4r1nI85eeeFGhKEHe8bPqoTK/nFuPmpe1aGAqMwHWz98y2w5AShbKTWHU3qp+oMT9aV4drN6oNnHfdilNxlwtPJ5KRwOD468WniVCsXRj9LxvMeyE41jRcABjumAQEbf3XBASPYwlFiC2B1fYcKOEO65sCe311mwUXYkzJXZJ/E81KU1YYqIFyPbqrI1bW5cj+1b4T//xqfOGoAulTg/aSSY0XqWMDATYYFYu5sds0wfPhnHmTSkKS49MfNLicTN+XLC4e4lwuQG9VVsKOl8uDEOAN9oJWTuGzazutleeYu8oXQIgpulkHHQpaN06Pzts9A4Qvf/M8Ygq37IDGPABE829V2RSRnU23tFJnTeuJdLGVmXNoomYd6XhWO0O54pIaxxHa6WDeAoF2OvKTsS8mSfcgjvzajlYTg3cMLIMANcKY6K5VJdsMpLZjk1lQ2QayP0UIKaHa24TNC5ntUEa0Rmuj07PFIkxp9/9gySf8Cy+5xYEi72cJyPHeZ0XqE1scdSpI58M7/ZnokFru7N6OmoNNxNCwcytB3BFvUvr7hF5+R1W3msT9VvIhunq/oz88ebwz+VdPpWXNMfNbasZuKBeVLYw7J5b/Idf5i02nHq6BYnpAfYtg71wdXgg2gam7CQeawh6u/N2Lg6okas3rMvMeDJgxVeEzrmQPmZDQZF583lWY6xEyz72/zwGCi/QJMHt4fBJ9P7oN7uoTzszr3amiOGqfA+Ibc1KFN6wZBHQ4yXonCUMoxioBp4vE4YuyxW8XQUvyFAsI+NB3Ud2yZ9ko5uotx9YrJIsBSltKHIHCp/FxJS4VTau1FixUB4lyXQnKassmv+TLxpccoz+C4i5XNGjaqarDREISWs=
Content-Type: multipart/alternative; boundary="_000_HE1PR0701MB3050BBA73506D92BD1D2710089E99HE1PR0701MB3050_"
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: a40ade61-4e7a-4a0e-f4f4-08dae4bafdfc
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Dec 2022 07:55:00.2453 (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: NhOtzp1OFVWUQ8gxWmEbbo513K2Zoo1HRIYYShNDn6Ke7TXISA8tXVQNPs2FKi4ALgzEoh6R3HpmXVLuMhrkkxEIYwLATh5tIilIlT+EH6M=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM8PR07MB7492
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/Jm2nsGwN2y30WKtk_ouDZnUyBTA>
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: Fri, 23 Dec 2022 07:55:11 -0000
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<mailto: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<mailto:lbartholomew@amsl.com>> Date: Thursday, 22 December 2022 at 00:46 To: John Mattsson <john.mattsson@ericsson.com<mailto:john.mattsson@ericsson.com>> Cc: Russ Housley <housley@vigilsec.com<mailto:housley@vigilsec.com>>, Sean Turner <sean@sn3rd.com<mailto:sean@sn3rd.com>>, Daniel Migault <daniel.migault@ericsson.com<mailto:daniel.migault@ericsson.com>>, RFC Editor <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>>, lamps-ads@ietf.org<mailto:lamps-ads@ietf.org> <lamps-ads@ietf.org<mailto:lamps-ads@ietf.org>>, lamps-chairs@ietf.org<mailto:lamps-chairs@ietf.org> <lamps-chairs@ietf.org<mailto:lamps-chairs@ietf.org>>, tim.hollebeek@digicert.com<mailto:tim.hollebeek@digicert.com> <tim.hollebeek@digicert.com<mailto:tim.hollebeek@digicert.com>>, Roman D. Danyliw <rdd@cert.org<mailto:rdd@cert.org>>, auth48archive@rfc-editor.org<mailto:auth48archive@rfc-editor.org> <auth48archive@rfc-editor.org<mailto: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<mailto: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<mailto:lbartholomew@amsl.com>> > Date: Wednesday, 21 December 2022 at 22:47 > To: John Mattsson <john.mattsson@ericsson.com<mailto:john.mattsson@ericsson.com>> > Cc: Russ Housley <housley@vigilsec.com<mailto:housley@vigilsec.com>>, Sean Turner <sean@sn3rd.com<mailto:sean@sn3rd.com>>, Daniel Migault <daniel.migault@ericsson.com<mailto:daniel.migault@ericsson.com>>, RFC Editor <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>>, lamps-ads@ietf.org<mailto:lamps-ads@ietf.org> <lamps-ads@ietf.org<mailto:lamps-ads@ietf.org>>, lamps-chairs@ietf.org<mailto:lamps-chairs@ietf.org> <lamps-chairs@ietf.org<mailto:lamps-chairs@ietf.org>>, tim.hollebeek@digicert.com<mailto:tim.hollebeek@digicert.com> <tim.hollebeek@digicert.com<mailto:tim.hollebeek@digicert.com>>, Roman D. Danyliw <rdd@cert.org<mailto:rdd@cert.org>>, auth48archive@rfc-editor.org<mailto:auth48archive@rfc-editor.org> <auth48archive@rfc-editor.org<mailto: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<mailto: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<mailto:lbartholomew@amsl.com>> > Date: Tuesday, 20 December 2022 at 21:50 > To: Russ Housley <housley@vigilsec.com<mailto:housley@vigilsec.com>>, Sean Turner <sean@sn3rd.com<mailto:sean@sn3rd.com>>, Daniel Migault <daniel.migault@ericsson.com<mailto:daniel.migault@ericsson.com>> > Cc: RFC Editor <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>>, John Mattsson <john.mattsson@ericsson.com<mailto:john.mattsson@ericsson.com>>, lamps-ads@ietf.org<mailto:lamps-ads@ietf.org> <lamps-ads@ietf.org<mailto:lamps-ads@ietf.org>>, lamps-chairs@ietf.org<mailto:lamps-chairs@ietf.org> <lamps-chairs@ietf.org<mailto:lamps-chairs@ietf.org>>, tim.hollebeek@digicert.com<mailto:tim.hollebeek@digicert.com><tim.hollebeek@digicert.com<mailto:tim.hollebeek@digicert.com>>, Roman D. Danyliw <rdd@cert.org<mailto:rdd@cert.org>>, auth48archive@rfc-editor.org<mailto:auth48archive@rfc-editor.org> <auth48archive@rfc-editor.org<mailto: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<mailto: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<mailto:sean@sn3rd.com>> wrote: > > > > All of these seem fine to me. > > > >> On Dec 20, 2022, at 12:02, Russ Housley <housley@vigilsec.com<mailto:housley@vigilsec.com>> wrote: > > ... > > > On Dec 20, 2022, at 9:02 AM, Russ Housley <housley@vigilsec.com<mailto: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