[Jwt-reg-review] [IANA #1147909] RE: Request to register claim: "at_use_nbr"

"Sabrina Tanamal via RT" <iana-prot-param@iana.org> Mon, 29 July 2019 16:32 UTC

Return-Path: <iana-shared@icann.org>
X-Original-To: jwt-reg-review@ietfa.amsl.com
Delivered-To: jwt-reg-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5EEB12021F for <jwt-reg-review@ietfa.amsl.com>; Mon, 29 Jul 2019 09:32:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level:
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FUZZY_CPILL=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dlo9H12EyjRN for <jwt-reg-review@ietfa.amsl.com>; Mon, 29 Jul 2019 09:32:29 -0700 (PDT)
Received: from smtp01.icann.org (smtp01.icann.org [192.0.33.81]) (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 1A0091200CC for <jwt-reg-review@ietf.org>; Mon, 29 Jul 2019 09:32:29 -0700 (PDT)
Received: from request4.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp01.icann.org (Postfix) with ESMTP id EA4CAE33BA; Mon, 29 Jul 2019 16:32:28 +0000 (UTC)
Received: by request4.lax.icann.org (Postfix, from userid 48) id E898720568; Mon, 29 Jul 2019 16:32:28 +0000 (UTC)
RT-Owner: sabrina.tanamal
From: "Sabrina Tanamal via RT" <iana-prot-param@iana.org>
Reply-To: iana-prot-param@iana.org
In-Reply-To: <DM6PR00MB057248744477E1F45A9E81BDF5C10@DM6PR00MB0572.namprd00.prod.outlook.com>
References: <RT-Ticket-1147909@icann.org> <7ddd8b990a544ac195b711f66bbebdba@xMail.etsihq.org> <CA+k3eCTppz+9cnbO4TUi40SPn5AJwS5TX-pfL9+x=fLN2F0-=g@mail.gmail.com> <58db505570754ef4abcc30cec50c8e43@xMail.etsihq.org> <2f55588ea3bb4bbbb66990f7ad84cdc0@xMail.etsihq.org> <BL0PR00MB02928379309A9DF0B9D80A62F5EA0@BL0PR00MB0292.namprd00.prod.outlook.com> <2c0b0a98ed534dd7885ecfc19728e9f1@xMail.etsihq.org> <MW2PR00MB0300C02270A9607EFE6D623DF5EA0@MW2PR00MB0300.namprd00.prod.outlook.com> <5877681dfc4246db8b44496f47d5acf1@xMail.etsihq.org> <DM6PR00MB057248744477E1F45A9E81BDF5C10@DM6PR00MB0572.namprd00.prod.outlook.com>
Message-ID: <rt-4.4.3-1664-1564417948-1586.1147909-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1147909
X-Managed-BY: RT 4.4.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: sabrina.tanamal@icann.org
To: Michael.Jones@microsoft.com
CC: bcampbell@pingidentity.com, jwt-reg-review@ietf.org, miguelangel.reinaortega@etsi.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Mon, 29 Jul 2019 16:32:28 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/jwt-reg-review/DO_OIm9UZCF5TGMzidvqH0IDLNo>
Subject: [Jwt-reg-review] [IANA #1147909] RE: Request to register claim: "at_use_nbr"
X-BeenThere: jwt-reg-review@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Expert review of proposed IANA registrations for JSON Web Token \(JWT\) claims." <jwt-reg-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jwt-reg-review>, <mailto:jwt-reg-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jwt-reg-review/>
List-Post: <mailto:jwt-reg-review@ietf.org>
List-Help: <mailto:jwt-reg-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jwt-reg-review>, <mailto:jwt-reg-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jul 2019 16:32:31 -0000

Hi Mike, all,

Can we register the "at_use_nbr" JWT claim now or should we wait until the document has been updated?  

Thanks,

Sabrina Tanamal
Senior IANA Services Specialist

On Thu Jul 25 21:12:50 2019, Michael.Jones@microsoft.com wrote:
> I approve of registration of the "at_use_nbr" JWT claim at
> https://www.iana.org/assignments/jwt/jwt.xhtml#claims.  (Ideally, this
> should wait until an updated draft has been sent to us that no longer
> attempts to register the "scope" claim, which has now been registered
> by https://tools.ietf.org/html/draft-ietf-oauth-token-exchange-19.)
> 
> -- Mike
> 
> From: Miguel Angel Reina Ortega <MiguelAngel.ReinaOrtega@etsi.org>;
> Sent: Tuesday, June 18, 2019 10:49 AM
> To: Mike Jones <Michael.Jones@microsoft.com>;; Brian Campbell
> <bcampbell@pingidentity.com>;
> Cc: PNNS <PNNS@etsi.org>;; jwt-reg-review@ietf.org
> Subject: RE: [Jwt-reg-review] Request to register claim: "at_use_nbr"
> 
> Dear Mike,
> 
> Then, that’s the right link to use until it gets published. And it
> will be published once different claims are registered. So, discussing
> with Brian, it was agreed to use that temporary link so that you can
> review the specification (which actually is on hold before publication
> until claims are registered) and then update the registry with the
> final link.
> 
> I hope that’s still ok.
> 
> Best regards.
> 
> -----------------------------------------------------------------------------------------------------------------
> Miguel Angel Reina Ortega – Testing Expert
> Centre for Testing and Interoperability (CTI)
> ETSI ●
> www.etsi.org<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.etsi.org%2F&data=02%7C01%7CMichael.Jones%40microsoft.com%7C811b8f37f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636964661252284876&sdata=KAuf8TA4v%2FLEXNmL%2F7Vchy3MlwJlFn71fr4bceE%2FMzU%3D&reserved=0>
> ●
> miguelangel.reinaortega@etsi.org<mailto:miguelangel.reinaortega@etsi.org>
> Phone: +33 (0)4 92 94 43 49 ● Mobile: +33 (0)6 76 73 60 99
> 
> This email may contain confidential information and is intended for
> the use of the addressee only. Any unauthorized use may be unlawful.
> If you receive this email by mistake, please advise the sender
> immediately by using the reply facility in your email software.
> Thank you for your co-operation.
> 
> From: Mike Jones
> <Michael.Jones@microsoft.com<mailto:Michael.Jones@microsoft.com>>
> Sent: 18 June 2019 15:13
> To: Miguel Angel Reina Ortega
> <MiguelAngel.ReinaOrtega@etsi.org<mailto:MiguelAngel.ReinaOrtega@etsi.org>>;
> Brian Campbell
> <bcampbell@pingidentity.com<mailto:bcampbell@pingidentity.com>>
> Cc: PNNS <PNNS@etsi.org<mailto:PNNS@etsi.org>>; jwt-reg-
> review@ietf.org<mailto:jwt-reg-review@ietf.org>
> Subject: RE: [Jwt-reg-review] Request to register claim: "at_use_nbr"
> 
> Rather than sending it to me, it would be better to place the
> normative doc at a permanent URL from which it can be directly opened.
> The IANA registration will need to refer to this URL anyway.  Any of
> docx, pdf, or txt formats should be fine.
> 
> -- Mike
> 
> From: Miguel Angel Reina Ortega
> <MiguelAngel.ReinaOrtega@etsi.org<mailto:MiguelAngel.ReinaOrtega@etsi.org>>
> Sent: Tuesday, June 18, 2019 2:54 PM
> To: Mike Jones
> <Michael.Jones@microsoft.com<mailto:Michael.Jones@microsoft.com>>;
> Brian Campbell
> <bcampbell@pingidentity.com<mailto:bcampbell@pingidentity.com>>
> Cc: PNNS <PNNS@etsi.org<mailto:PNNS@etsi.org>>; jwt-reg-
> review@ietf.org<mailto:jwt-reg-review@ietf.org>
> Subject: RE: [Jwt-reg-review] Request to register claim: "at_use_nbr"
> 
> Dear Mike,
> 
> Yes, it is still the correct doc link. I did not have any problem
> opening any of the documents.
> 
> Should I send it attached to an email for you?
> 
> Best regards.
> 
> -----------------------------------------------------------------------------------------------------------------
> Miguel Angel Reina Ortega – Testing Expert
> Centre for Testing and Interoperability (CTI)
> ETSI ●
> www.etsi.org<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.etsi.org%2F&data=02%7C01%7CMichael.Jones%40microsoft.com%7C811b8f37f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636964661252294873&sdata=AdcJngZ%2BW3ufPu3EWFmtrnfoO0cVYWCCFsRZgeIzqbg%3D&reserved=0>
> ●
> miguelangel.reinaortega@etsi.org<mailto:miguelangel.reinaortega@etsi.org>
> Phone: +33 (0)4 92 94 43 49 ● Mobile: +33 (0)6 76 73 60 99
> 
> This email may contain confidential information and is intended for
> the use of the addressee only. Any unauthorized use may be unlawful.
> If you receive this email by mistake, please advise the sender
> immediately by using the reply facility in your email software.
> Thank you for your co-operation.
> 
> From: Mike Jones
> <Michael.Jones@microsoft.com<mailto:Michael.Jones@microsoft.com>>
> Sent: 18 June 2019 12:30
> To: Miguel Angel Reina Ortega
> <MiguelAngel.ReinaOrtega@etsi.org<mailto:MiguelAngel.ReinaOrtega@etsi.org>>;
> Brian Campbell
> <bcampbell@pingidentity.com<mailto:bcampbell@pingidentity.com>>
> Cc: PNNS <PNNS@etsi.org<mailto:PNNS@etsi.org>>; jwt-reg-
> review@ietf.org<mailto:jwt-reg-review@ietf.org>
> Subject: RE: [Jwt-reg-review] Request to register claim: "at_use_nbr"
> 
> I just tried opening the docs inside the .zip file
> https://docbox.etsi.org/ISG/NFV/Open/Drafts/SEC022_API_Access_Token_Spec/NFV-
> SEC022v010.zip<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocbox.etsi.org%2FISG%2FNFV%2FOpen%2FDrafts%2FSEC022_API_Access_Token_Spec%2FNFV-
> SEC022v010.zip&data=02%7C01%7CMichael.Jones%40microsoft.com%7C811b8f37f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636964661252294873&sdata=nBTW5sf1ulDOrR7QlJehFk1l5t6P0OjMrBSqv75ter4%3D&reserved=0>
> to review the request and there were problems opening both of them.
> Is this still the correct doc link?
> 
> -- Mike
> 
> From: Jwt-reg-review <jwt-reg-review-bounces@ietf.org<mailto:jwt-reg-
> review-bounces@ietf.org>>; On Behalf Of Miguel Angel Reina Ortega
> Sent: Monday, June 17, 2019 6:21 AM
> To: Brian Campbell
> <bcampbell@pingidentity.com<mailto:bcampbell@pingidentity.com>>
> Cc: PNNS <PNNS@etsi.org<mailto:PNNS@etsi.org>>; jwt-reg-
> review@ietf.org<mailto:jwt-reg-review@ietf.org>
> Subject: Re: [Jwt-reg-review] Request to register claim: "at_use_nbr"
> 
> Dear Brian,
> 
> I still don’t see the requested claim appearing on the registry. Is
> there anything that needs to be done on my side?
> 
> Thanks in advance.
> 
> Best regards.
> 
> From: Miguel Angel Reina Ortega
> Sent: 06 June 2019 11:59
> To: Brian Campbell
> <bcampbell@pingidentity.com<mailto:bcampbell@pingidentity.com>>
> Cc: jwt-reg-review@ietf.org<mailto:jwt-reg-review@ietf.org>; PNNS
> <PNNS@etsi.org<mailto:PNNS@etsi.org>>
> Subject: RE: [Jwt-reg-review] Request to register claim: "at_use_nbr"
> 
> Dear Brian,
> 
> Thanks for the comments. The “scope” claim will be removed from there.
> 
> On the other hand, I don’t see any of those links you mention, just
> the following: http://openid.net/specs/openid-connect-core-
> 1_0.html#IDToken<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fopenid.net%2Fspecs%2Fopenid-
> connect-core-
> 1_0.html%23IDToken&data=02%7C01%7CMichael.Jones%40microsoft.com%7C811b8f37f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636964661252304870&sdata=cPVHeLCY%2B9b1RECwSKSJd6FxIeHOzwr%2FHTDlZ8dQ2xc%3D&reserved=0>.
> which seems correct to me.
> 
> Best regards.
> 
> From: Brian Campbell
> <bcampbell@pingidentity.com<mailto:bcampbell@pingidentity.com>>
> Sent: 29 May 2019 19:02
> To: Miguel Angel Reina Ortega
> <MiguelAngel.ReinaOrtega@etsi.org<mailto:MiguelAngel.ReinaOrtega@etsi.org>>
> Cc: jwt-reg-review@ietf.org<mailto:jwt-reg-review@ietf.org>; PNNS
> <PNNS@etsi.org<mailto:PNNS@etsi.org>>
> Subject: Re: [Jwt-reg-review] Request to register claim: "at_use_nbr"
> 
> In general I think that the “at_use_nbr” claim can be registered given
> how it is described in the NFV_SEC022v0-1-0-cb.docx file inside the
> zip file at the
> https://docbox.etsi.org/ISG/NFV/Open/Drafts/SEC022_API_Access_Token_Spec/NFV-
> SEC022v010.zip<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocbox.etsi.org%2FISG%2FNFV%2FOpen%2FDrafts%2FSEC022_API_Access_Token_Spec%2FNFV-
> SEC022v010.zip&data=02%7C01%7CMichael.Jones%40microsoft.com%7C811b8f37f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636964661252304870&sdata=h%2BbV4TOGWI7OclnjcoVfhxDohoCDS2ZMmP4WkhbPEd8%3D&reserved=0>
> link provided.
> 
> However, there are also links there to
> https://openid.net/specs/openid-connect-core-
> 1_0.html#StandardClaims<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopenid.net%2Fspecs%2Fopenid-
> connect-core-
> 1_0.html%23StandardClaims&data=02%7C01%7CMichael.Jones%40microsoft.com%7C811b8f37f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636964661252314858&sdata=L1aJTNTynU7sITK1GIYZ6T3TGe%2BE%2FAhfKweE8wmXP54%3D&reserved=0>
> and
> https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=54060<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fportal.etsi.org%2Fwebapp%2FWorkProgram%2FReport_WorkItem.asp%3FWKI_ID%3D54060&data=02%7C01%7CMichael.Jones%40microsoft.com%7C811b8f37f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636964661252314858&sdata=OXRk3QxdH%2BaevjV9UqRhO667tzXkCbTBISdhFvMigAc%3D&reserved=0>
> which are confusing and/or don't seem right.
> 
> Also the NFV_SEC022v0-1-0-cb.docx document also still has "scope" in
> the JSON Web Token Claims registry which needs to be removed. Because
> ultimately I think IANA works off of the specification document
> itself.
> 
> 
> 
> On Sun, May 26, 2019 at 9:36 PM Miguel Angel Reina Ortega
> <MiguelAngel.ReinaOrtega@etsi.org<mailto:MiguelAngel.ReinaOrtega@etsi.org>>
> wrote:
> Dear,
> On behalf of ETSI NFV ISG, I would like to submit the following
> registration request for the “JSON Web Token” registry:
> 
> *   Claim Name: “at_use_nbr”
> *   Claim Description: Number of API requests for which the access
> token can be used.
> *   Change Controller: ETSI (pnns@etsi.org<mailto:pnns@etsi.org>)
> *   Specification Document(s): Clause
> 5.5<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopenid.net%2Fspecs%2Fopenid-
> connect-core-
> 1_0.html%23StandardClaims&data=02%7C01%7CMichael.Jones%40microsoft.com%7C811b8f37f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636964661252324855&sdata=y%2B5vLXGsFEb7ZvAyWM8F%2BjEHhvDSP6Vk7%2F5TDFLk0wM%3D&reserved=0>
> of the present ETSI GS NFV-SEC
> 022<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fportal.etsi.org%2Fwebapp%2FWorkProgram%2FReport_WorkItem.asp%3FWKI_ID%3D54060&data=02%7C01%7CMichael.Jones%40microsoft.com%7C811b8f37f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636964661252324855&sdata=%2BbJya6z9mpjCsFj%2BsOS8Yr6I1LuNK%2BTAHP3jlzag%2FCw%3D&reserved=0>
> (https://docbox.etsi.org/ISG/NFV/Open/Drafts/SEC022_API_Access_Token_Spec/NFV-
> SEC022v010.zip<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocbox.etsi.org%2FISG%2FNFV%2FOpen%2FDrafts%2FSEC022_API_Access_Token_Spec%2FNFV-
> SEC022v010.zip&data=02%7C01%7CMichael.Jones%40microsoft.com%7C811b8f37f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636964661252334848&sdata=Hz8Ruq6%2F80zPTVUZ5Utfl%2FVT6iM0b5tXRra0U1B8Rm0%3D&reserved=0>)
> Please, note that once the specification is approved, the pointer to
> the specification will be updated.
> 
> Best regards.
> 
> -----------------------------------------------------------------------------------------------------------------
> Miguel Angel Reina Ortega – Testing Expert
> Centre for Testing and Interoperability (CTI)
> ETSI ●
> www.etsi.org<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.etsi.org%2F&data=02%7C01%7CMichael.Jones%40microsoft.com%7C811b8f37f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636964661252334848&sdata=Tm4r7phfca0Zn50tykuYD%2FgwFg4z5mTFeRDQELgvNBM%3D&reserved=0>
> ●
> miguelangel.reinaortega@etsi.org<mailto:miguelangel.reinaortega@etsi.org>
> Phone: +33 (0)4 92 94 43 49 ● Mobile: +33 (0)6 76 73 60 99
> 
> This email may contain confidential information and is intended for
> the use of the addressee only. Any unauthorized use may be unlawful.
> If you receive this email by mistake, please advise the sender
> immediately by using the reply facility in your email software.
> Thank you for your co-operation.
> 
> _______________________________________________
> Jwt-reg-review mailing list
> Jwt-reg-review@ietf.org<mailto:Jwt-reg-review@ietf.org>
> https://www.ietf.org/mailman/listinfo/jwt-reg-
> review<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fjwt-
> reg-
> review&data=02%7C01%7CMichael.Jones%40microsoft.com%7C811b8f37f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636964661252344842&sdata=Mdyegz6ObTAZWdgJjgHNzFP%2FuUc%2BO%2BoLgM06IuJO3cc%3D&reserved=0>
> 
> CONFIDENTIALITY NOTICE: This email may contain confidential and
> privileged material for the sole use of the intended recipient(s). Any
> review, use, distribution or disclosure by others is strictly
> prohibited.  If you have received this communication in error, please
> notify the sender immediately by e-mail and delete the message and any
> file attachments from your computer. Thank you.