Re: [Jwt-reg-review] Request to register claim: "at_use_nbr"

Mike Jones <> Tue, 18 June 2019 10:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 32C9512012C for <>; Tue, 18 Jun 2019 03:30:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id I46X7EY6lS9D for <>; Tue, 18 Jun 2019 03:30:11 -0700 (PDT)
Received: from ( [IPv6:2a01:111:f400:fe56::729]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8BEFD1200B1 for <>; Tue, 18 Jun 2019 03:30:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=mnao0Cy5qfJGnCvZTFugZx6AoW2zCKuhwoejtxeeB8M=; b=lg1zfeIx+0xk2tCDUHBrNtq/UjdfmkGlBvN186eQtTZFWk2KrS1nic075iCYPDb83NM+V0HyoJ1bIyRvHaNxtpA1GXHI3pPzVh37FFEE6zExmM00JLoAzpb24yBtkctGWzm0IfKaWUbcV5Dd6B5M/fzJAVUzca07L4Hlg1AioZQ=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2044.0; Tue, 18 Jun 2019 10:30:05 +0000
Received: from ([fe80::42d:554e:1c2e:14b4]) by ([fe80::42d:554e:1c2e:14b4%7]) with mapi id 15.20.2042.000; Tue, 18 Jun 2019 10:30:05 +0000
From: Mike Jones <>
To: Miguel Angel Reina Ortega <>, Brian Campbell <>
CC: PNNS <>, "" <>
Thread-Topic: [Jwt-reg-review] Request to register claim: "at_use_nbr"
Date: Tue, 18 Jun 2019 10:30:04 +0000
Message-ID: <>
References: <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=3adc1fc8-b0a7-4d82-9ad8-0000cbb42bc8; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2019-06-18T10:29:05-0800; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47;
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f343ebd3-7a89-4710-aa8d-08d6f3d7eda6
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:BL0PR00MB0323;
x-ms-traffictypediagnostic: BL0PR00MB0323:
x-ms-exchange-purlcount: 6
x-microsoft-antispam-prvs: <>
x-ms-oob-tlc-oobclassifiers: OLM:3044;
x-forefront-prvs: 007271867D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(376002)(136003)(396003)(39860400002)(366004)(51874003)(51444003)(51914003)(189003)(199004)(6506007)(53546011)(966005)(14454004)(81156014)(7696005)(76176011)(8676002)(81166006)(606006)(72206003)(8990500004)(102836004)(8936002)(99286004)(73956011)(76116006)(14444005)(10290500003)(66446008)(64756008)(110136005)(66946007)(66476007)(66556008)(5024004)(256004)(66066001)(22452003)(478600001)(316002)(54906003)(5660300002)(86362001)(52536014)(6246003)(5070765005)(186003)(25786009)(71200400001)(26005)(486006)(71190400001)(476003)(4326008)(74316002)(11346002)(446003)(33656002)(53376002)(3846002)(6436002)(790700001)(6116002)(68736007)(55016002)(229853002)(2906002)(10090500001)(7736002)(54896002)(6306002)(53936002)(236005)(9686003); DIR:OUT; SFP:1102; SCL:1; SRVR:BL0PR00MB0323;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None ( does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: n5WOPTs/WdN3+jgYP7yYpo8qVdQnyYrJRyWfgVEhDmD6VDVZUANuq23vLL/YUvNJZUgHhiC10pfja57BTTs4U4kSfCrP8GNvam3BZYtVAQXIwi4+Dv8ddDe6mkuvOxg6GrOZk8UWZhv48XFBg683HKRzgIVZIPGe/CEuhbSoqVJ1LN5rAQuI4jiGC5q+NIXWf1cUnVI4xwY/IwvV/3Xw2QlMtMKtd1x9eCTBmd+F8SoLcCo0DAvHpRtdLYx6vEajgw8D2p88+lacyWwXr/JxJQ1lkSW5JJcoCvvy6wetwyHDhmlrJ3J7l6KKhI4cd8GN6SiybZxNVnANGmiC8gHiUZjOdanSBgWWX539kOOoQLV+5yKG7Rreuk4p/XmEqqX51il0wMMWsMtDi84IB7KJTe6USui2oB3VVa4t9hN6cCk=
Content-Type: multipart/alternative; boundary="_000_BL0PR00MB02928379309A9DF0B9D80A62F5EA0BL0PR00MB0292namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: f343ebd3-7a89-4710-aa8d-08d6f3d7eda6
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Jun 2019 10:30:04.7566 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR00MB0323
Archived-At: <>
Subject: Re: [Jwt-reg-review] Request to register claim: "at_use_nbr"
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Expert review of proposed IANA registrations for JSON Web Token \(JWT\) claims." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 18 Jun 2019 10:30:16 -0000

I just tried opening the docs inside the .zip file to review the request and there were problems opening both of them.  Is this still the correct doc link?

                                           -- Mike

From: Jwt-reg-review <> On Behalf Of Miguel Angel Reina Ortega
Sent: Monday, June 17, 2019 6:21 AM
To: Brian Campbell <>
Cc: PNNS <>rg>;
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 <<>>
Cc:<>; PNNS <<>>
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:<>amp;reserved=0>. which seems correct to me.

Best regards.

From: Brian Campbell <<>>
Sent: 29 May 2019 19:02
To: Miguel Angel Reina Ortega <<>>
Cc:<>; PNNS <<>>
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<> link provided.

However, there are also links there to<> and<> 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 <<>> wrote:
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 (<>)
  *   Specification Document(s): Clause 5.5<> of the present ETSI GS NFV-SEC 022<> (<>)
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 ●<> ●<>
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<><>

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.