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

["Sabrina Tanamal via RT" <[e-mail]>]

Hi Mike, all, 

Can you confirm that we can proceed with this registration and list this document as a reference? 

Thanks,
Sabrina

On Tue Jul 30 08:21:55 2019, [e-mail] wrote:
> Hi Sabrina, all,
> 
> Please, find attached the document with the updated information as
> requested by Mike.
> 
> Best regards.
> 
> -----------------------------------------------------------------------------------------------------------------
> Miguel Angel Reina Ortega – Testing Expert
> Centre for Testing and Interoperability (CTI)
> ETSI ● www.etsi.org ● [e-mail]
> Phone: [phone] ● Mobile: [phone]
> 
> 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.
> 
> -----Original Message-----
>  From: Sabrina Tanamal via RT <[e-mail]>
> Sent: 29 July 2019 18:32
> To: [e-mail]
> Cc: [e-mail]; [e-mail]; Miguel Angel
> Reina Ortega <[e-mail]>
> Subject: [IANA #1147909] RE: [Jwt-reg-review] Request to register
> claim: "at_use_nbr"
> 
> 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, [e-mail] 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 <[e-mail]>
> > Sent: Tuesday, June 18, 2019 10:49 AM
> >  To: Mike Jones <[e-mail]>; Brian Campbell
> > <[e-mail]>
> > Cc: PNNS <[e-mail]>; [e-mail]
> > 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%7
> > C811b8f37f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7
> > C1%7C0%7C636964661252284876&sdata=KAuf8TA4v%2FLEXNmL%2F7Vchy3MlwJlFn71
> > fr4bceE%2FMzU%3D&reserved=0>
> > ●
> > [e-mail]<mailto:miguelangel.reinaortega@etsi.o
> > rg>
> > Phone: [phone] ● Mobile: [phone]
> >
> > 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
> > <[e-mail]<mailto:[e-mail]>>
> > Sent: 18 June 2019 15:13
> > To: Miguel Angel Reina Ortega
> > <[e-mail]<mailto:MiguelAngel.ReinaOrtega@etsi.
> > org>> ;
> > Brian Campbell
> > <[e-mail]<mailto:[e-mail]>>
> >  Cc: PNNS <[e-mail]<mailto:[e-mail]>>; jwt-reg-
> > [e-mail]<mailto:[e-mail]>
> > 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
> > <[e-mail]<mailto:MiguelAngel.ReinaOrtega@etsi.
> > org>>
> > Sent: Tuesday, June 18, 2019 2:54 PM
> > To: Mike Jones
> > <[e-mail]<mailto:[e-mail]>>;
> > Brian Campbell
> > <[e-mail]<mailto:[e-mail]>>
> >  Cc: PNNS <[e-mail]<mailto:[e-mail]>>; jwt-reg-
> > [e-mail]<mailto:[e-mail]>
> > 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%7
> > C811b8f37f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7
> > C1%7C0%7C636964661252294873&sdata=AdcJngZ%2BW3ufPu3EWFmtrnfoO0cVYWCCFs
> > RZgeIzqbg%3D&reserved=0>
> > ●
> > [e-mail]<mailto:miguelangel.reinaortega@etsi.o
> > rg>
> > Phone: [phone] ● Mobile: [phone]
> >
> > 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
> > <[e-mail]<mailto:[e-mail]>>
> > Sent: 18 June 2019 12:30
> > To: Miguel Angel Reina Ortega
> > <[e-mail]<mailto:MiguelAngel.ReinaOrtega@etsi.
> > org>> ;
> > Brian Campbell
> > <[e-mail]<mailto:[e-mail]>>
> >  Cc: PNNS <[e-mail]<mailto:[e-mail]>>; jwt-reg-
> > [e-mail]<mailto:[e-mail]>
> > 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_Sp
> > ec/NFV-
> > SEC022v010.zip<https://nam06.safelinks.protection.outlook.com/?url=htt
> > ps%3A%2F%2Fdocbox.etsi.org%2FISG%2FNFV%2FOpen%2FDrafts%2FSEC022_API_Ac
> >  cess_Token_Spec%2FNFV-
> > SEC022v010.zip&data=02%7C01%7CMichael.Jones%40microsoft.com%7C811b8f37
> > f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C
> > 636964661252294873&sdata=nBTW5sf1ulDOrR7QlJehFk1l5t6P0OjMrBSqv75ter4%3
> >  D&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 <[e-mail]<mailto:jwt-reg-
> > [e-mail]>> On Behalf Of Miguel Angel Reina Ortega
> > Sent: Monday, June 17, 2019 6:21 AM
> > To: Brian Campbell
> > <[e-mail]<mailto:[e-mail]>>
> >  Cc: PNNS <[e-mail]<mailto:[e-mail]>>; jwt-reg-
> > [e-mail]<mailto:[e-mail]>
> > 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
> > <[e-mail]<mailto:[e-mail]>>
> >  Cc: [e-mail]<mailto:[e-mail]>; PNNS
> > <[e-mail]<mailto:[e-mail]>>
> > 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=h
> > ttp%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
> > <[e-mail]<mailto:[e-mail]>>
> > Sent: 29 May 2019 19:02
> > To: Miguel Angel Reina Ortega
> > <[e-mail]<mailto:MiguelAngel.ReinaOrtega@etsi.
> > org>>
> > Cc: [e-mail]<mailto:[e-mail]>; PNNS
> > <[e-mail]<mailto:[e-mail]>>
> > 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_Sp
> > ec/NFV-
> > SEC022v010.zip<https://nam06.safelinks.protection.outlook.com/?url=htt
> > ps%3A%2F%2Fdocbox.etsi.org%2FISG%2FNFV%2FOpen%2FDrafts%2FSEC022_API_Ac
> > cess_Token_Spec%2FNFV-
> > SEC022v010.zip&data=02%7C01%7CMichael.Jones%40microsoft.com%7C811b8f37
> > f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C
> > 636964661252304870&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%2FA
> > hfKweE8wmXP54%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_I
> > D%3D54060&data=02%7C01%7CMichael.Jones%40microsoft.com%7C811b8f37f8254
> > cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C63696
> > 4661252314858&sdata=OXRk3QxdH%2BaevjV9UqRhO667tzXkCbTBISdhFvMigAc%3D&r
> > eserved=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
> > <[e-mail]<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 ([e-mail]<mailto:[e-mail]>)
> > *   Specification Document(s): Clause
> > 5.5<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> > openid.net%2Fspecs%2Fopenid-
> > connect-core-
> > 1_0.html%23StandardClaims&data=02%7C01%7CMichael.Jones%40microsoft.com
> > %7C811b8f37f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47
> > %7C1%7C0%7C636964661252324855&sdata=y%2B5vLXGsFEb7ZvAyWM8F%2BjEHhvDSP6
> > Vk7%2F5TDFLk0wM%3D&reserved=0>
> > of the present ETSI GS NFV-SEC
> > 022<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> > portal.etsi.org%2Fwebapp%2FWorkProgram%2FReport_WorkItem.asp%3FWKI_ID%
> > 3D54060&data=02%7C01%7CMichael.Jones%40microsoft.com%7C811b8f37f8254cc
> > 50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6369646
> > 61252324855&sdata=%2BbJya6z9mpjCsFj%2BsOS8Yr6I1LuNK%2BTAHP3jlzag%2FCw%
> > 3D&reserved=0>
> > (https://docbox.etsi.org/ISG/NFV/Open/Drafts/SEC022_API_Access_Token_S
> > pec/NFV-
> > SEC022v010.zip<https://nam06.safelinks.protection.outlook.com/?url=htt
> > ps%3A%2F%2Fdocbox.etsi.org%2FISG%2FNFV%2FOpen%2FDrafts%2FSEC022_API_Ac
> > cess_Token_Spec%2FNFV-
> > SEC022v010.zip&data=02%7C01%7CMichael.Jones%40microsoft.com%7C811b8f37
> > f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C
> > 636964661252334848&sdata=Hz8Ruq6%2F80zPTVUZ5Utfl%2FVT6iM0b5tXRra0U1B8R
> >  m0%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%7
> > C811b8f37f8254cc50b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7
> > C1%7C0%7C636964661252334848&sdata=Tm4r7phfca0Zn50tykuYD%2FgwFg4z5mTFeR
> > DQELgvNBM%3D&reserved=0>
> > ●
> > [e-mail]<mailto:miguelangel.reinaortega@etsi.o
> > rg>
> > Phone: [phone] ● Mobile: [phone]
> >
> > 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
> > [e-mail]<mailto:[e-mail]>
> > 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%7C811b8f37f8254cc5
> > 0b0c08d6f3fc0f41%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C63696466
> > 1252344842&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.
>