Re: [Jwt-reg-review] Review requested: draft-ietf-sipcore-rejected

Mike Jones <> Fri, 21 June 2019 07:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1FB68120153; Fri, 21 Jun 2019 00:35:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.02
X-Spam-Status: No, score=-0.02 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, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-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 mUAdUmaqBKki; Fri, 21 Jun 2019 00:35:05 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CC71B12006F; Fri, 21 Jun 2019 00:35:04 -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=+x0PXZbqdztE5+32+x2HY4eLKmsAM23OsA32uSrGXkA=; b=oNBbUQ8qUX4RAJaL3wpRQyL2kcF/So8aYYwuhjCQ7ppLpx66QzsoqrtOTNFRCnPnVCA7WDi13KxoSAV31dD1/el2KkD//lEDa7YEPGcw7MhfQ+scEpQoikNJBfp31acPbum5r1BtJ6mwOFHsgaPH1JrwYEq6meE+dfZ3xZICvMU=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2049.0; Fri, 21 Jun 2019 07:35:01 +0000
Received: from ([fe80::ed73:9556:db4c:a610]) by ([fe80::ed73:9556:db4c:a610%8]) with mapi id 15.20.2044.000; Fri, 21 Jun 2019 07:35:01 +0000
From: Mike Jones <>
To: Brian Campbell <>, Eric Burger <>
CC: "" <>, "" <>
Thread-Topic: [Jwt-reg-review] Review requested: draft-ietf-sipcore-rejected
Thread-Index: AQHUz7KUk1C73MYC2EmoddiVIpHHc6X4S9DggAASGACAntfcgIANPp6AgAFRfoCAAJ+T0A==
Date: Fri, 21 Jun 2019 07:25:15 +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=0cae5f7f-7b1b-4911-a57a-000044af80c3; 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-21T07:24:56-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: 46fa0b3c-98a7-41f6-06e8-08d6f61af876
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(7168020)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:SN6PR00MB0351;
x-ms-traffictypediagnostic: SN6PR00MB0351:
x-ms-exchange-purlcount: 6
x-microsoft-antispam-prvs: <>
x-ms-oob-tlc-oobclassifiers: OLM:6108;
x-forefront-prvs: 0075CB064E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(366004)(39860400002)(136003)(376002)(346002)(189003)(199004)(13464003)(8936002)(22452003)(64756008)(54906003)(110136005)(7736002)(256004)(10090500001)(14454004)(71200400001)(71190400001)(26005)(66446008)(68736007)(76116006)(6116002)(66556008)(3846002)(446003)(52536014)(8676002)(55016002)(6436002)(6666004)(73956011)(10290500003)(478600001)(790700001)(66946007)(86362001)(316002)(33656002)(11346002)(966005)(606006)(8990500004)(486006)(55236004)(9686003)(81166006)(236005)(476003)(81156014)(6306002)(66476007)(54896002)(4326008)(5660300002)(7696005)(6506007)(66066001)(53936002)(74316002)(76176011)(72206003)(6246003)(5024004)(14444005)(2906002)(99286004)(53546011)(102836004)(186003)(25786009)(229853002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN6PR00MB0351;; 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: mA0RRw3uIJzScfRbcT9J2wgLD9ff/W7nxdiNqJ6icbyOeCwlIz/Ds9W/GZdc5kSadLSZlUHPMNV0HuS3NUFLol8WSwcSnngLrYa7nswcTf5TAtB6nTelJsqDdf6Amy8cyVpTOWJt3CC4AYF8AsMybQ6Tfjc3NLCQIO8ZahIJZ9hKtUSFUqVDmw8kIcT2NHNQVdOfEQvThf/XpOez2kg8SMujY0mTqx/34I3vGk4iNa52PyRm3OiUqXDpJMuUrt6lL6NxYcglIiVMWKWLt05TNpFE5EKfJRHuqHvMs7iEWvrrGpDvGhGPjCoMskv93JKoxttfI6blumQjVbcBxCmIf/qKyEw2kW01EPrRQo4fkZhmmTdnzH7ZwstvD+NegIOtasyky0Cu5E82w4bfymM/YZTCa2VQtrAU25x1lG+Bvp0=
Content-Type: multipart/alternative; boundary="_000_SN6PR00MB03012DD81580FBE90BF3488CF5E70SN6PR00MB0301namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 46fa0b3c-98a7-41f6-06e8-08d6f61af876
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jun 2019 07:25:15.1117 (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: SN6PR00MB0351
Archived-At: <>
Subject: Re: [Jwt-reg-review] Review requested: draft-ietf-sipcore-rejected
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: Fri, 21 Jun 2019 07:35:08 -0000


From: Brian Campbell <>;
Sent: Thursday, June 20, 2019 2:54 PM
To: Eric Burger <>;
Cc: Mike Jones <>;;;
Subject: Re: [Jwt-reg-review] Review requested: draft-ietf-sipcore-rejected

I think a reference is good. I was looking for or expecting just a brief statement in sec 3.3 along the lines of 'the value of the "jcard" claim is a JSON array conforming to the JSON jCard data format defined in RFC7095' or something like that.

On Wed, Jun 19, 2019 at 7:45 PM Eric Burger <<>> wrote:
Would having a reference to jCard suffice, or do we need a detailed explanation of what a jCard is?

On Jun 11, 2019, at 11:30 AM, Brian Campbell <<>> wrote:

Looking again at this and the more recent revision of the draft, I do think the jcard claim registration is okay in general.

However, the IANA Considerations registration request at<> points to<>;, which I think could do a little better job of describing what the value of the jcard claim will be - particularly for folks like myself who are unfamiliar with jCard. The link back to section-5.3 is just circular and isn't particularly helpful. So I went looking to the examples to see a jcard claim to help me understand and I noticed the JWS header in<> isn't valid JOSE/JWS, which should probably be fixed. The 'alg', 'typ', and 'x5u' header parameters should all be top level members of the JSON rather than wrapped in extra {}'s. See<> for example.

On Sat, Mar 2, 2019 at 6:48 AM Brian Campbell <<>> wrote:
also approve

On Sat, Mar 2, 2019 at 5:44 AM Mike Jones <<>> wrote:
In my role as a Designated Expert, I approve this registration request.

                                -- Mike

-----Original Message-----
From: Jwt-reg-review <<>> On Behalf Of A. Jean Mahoney
Sent: Thursday, February 28, 2019 2:11 PM
Subject: [Jwt-reg-review] Review requested: draft-ietf-sipcore-rejected

Hi JWT Registration Review Team,

Please review the JWT claim registration request found in Section 5.3 of draft-ietf-sipcore-rejected [1]. The draft has just finished WGLC.


Jean, as Doc Shepherd



 From the draft:

5.3.  JSON Web Token Claim

    This document defines the new JSON Web Token claim in the "JSON Web
    Token Claims" sub-registry created by [RFC7519].  Section 3.2.2
    defines the syntax.  The required information is:

    Claim Name:  jcard

    Claim Description:  jCard data

    Change Controller:  IESG

    Reference:  [RFCXXXX], [RFC7095]

Jwt-reg-review mailing list<><>

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.

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.