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

Miguel Angel Reina Ortega <> Thu, 06 June 2019 09:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 198161200F8 for <>; Thu, 6 Jun 2019 02:58:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.289
X-Spam-Status: No, score=-4.289 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, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] 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 f5Mj_gJt7sop for <>; Thu, 6 Jun 2019 02:58:41 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E4A5C12009E for <>; Thu, 6 Jun 2019 02:58:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=1524829736.etsi;; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To:Content-Type: MIME-Version;; bh=I9kPRhZ/70IjbC/BvkOwWieO4GSCq5gWU+Hk657RLkY=; b=cc/PqdnZwsj8ZFDdQUK/ptx21oDJe7nBP5X/ThIIcUK9qquR6HXgQOtT7VYDN5117F5YZ2R2/P31 S/aSdTuM1Ov3DldU/xgLwjFgU+h0eJIgQlyrllTUxrtruGDcSWW+ik9evr2+lwYlOheEidTSzW8d 9VayszxjkgsvkXLrch0=
Received: from ( by id hv3ht22gvlcn for <>; Thu, 6 Jun 2019 10:58:38 +0100 (envelope-from <>)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1236.3; Thu, 6 Jun 2019 11:58:38 +0200
Received: from ([]) by ([]) with mapi id 15.00.1236.000; Thu, 6 Jun 2019 11:58:38 +0200
From: Miguel Angel Reina Ortega <>
To: Brian Campbell <>
CC: "" <>, PNNS <>
Thread-Topic: [Jwt-reg-review] Request to register claim: "at_use_nbr"
Thread-Index: AdUUPCk35WRFbawXQP2CfNV5KeT+3QB81EuAAYenrcA=
Date: Thu, 6 Jun 2019 09:58:38 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US, en-GB
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_58db505570754ef4abcc30cec50c8e43xMailetsihqorg_"
MIME-Version: 1.0
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: Thu, 06 Jun 2019 09:58:44 -0000

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: 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.