Re: [OAUTH-WG] AD review of draft-ietf-oauth-proof-of-possession

Mike Jones <> Tue, 01 December 2015 19:39 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 1E4E21B2F7E for <>; Tue, 1 Dec 2015 11:39:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id zW1a008LFGBz for <>; Tue, 1 Dec 2015 11:39:32 -0800 (PST)
Received: from ( [IPv6:2a01:111:f400:fc10::794]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 546D31B2F71 for <>; Tue, 1 Dec 2015 11:39:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=QBXDQXo6zmatoshQydUnfL62A9Qoc5jjQ10RAKNFdUw=; b=fe5Q5dioQb5NDaTM2jQ1+TEbok9rl2Z+02elgIgiSPjmZWsKpuyHsUm7rJ7kOIREidhXPdlDvF41XiWmuuYH+0FRIu/G0IEnxpPu1Rb60lcrHVDB08JFVs0pBcvKAed8VCNzC+dLO9KnErtY03ApZUhZhxKofFKFHA0sHMNrAQ8=
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.1.331.20; Tue, 1 Dec 2015 19:39:13 +0000
Received: from ([]) by ([]) with mapi id 15.01.0331.023; Tue, 1 Dec 2015 19:39:13 +0000
From: Mike Jones <>
To: Kathleen Moriarty <>
Thread-Topic: [OAUTH-WG] AD review of draft-ietf-oauth-proof-of-possession
Thread-Index: AQHRJt++kWDp0FqlfEmPEzc+Ih7voJ6r6UxQgAAee4CAAAb2QIAAAjcAgAAA9fCAALluAIAJxh2g
Date: Tue, 01 Dec 2015 19:39:13 +0000
Message-ID: <>
References: <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-microsoft-exchange-diagnostics: 1; BY2PR03MB443; 5:vYfuGWYw8bzEHCvjbeDJlKwodJbSEXGaIk/NSmaMn/Fo0z4ghD2BZb5tjCvvLTr6bGReWAuHfct/I/nXNBgLLmB7d6Vk9PBIcpKURvAjtBGnLb7nISBm2ykT4XrKH0SiioCmGJP7Pd0HelvUNun4bA==; 24:keJH76s9nmDAlx6VYdm7QcBPXsmY5zXCeFsKGrAeIsxRlMXkgcnEQ38La8/8LIoK5q7RqjymT88Il14/BMDLngoM/WFuHVpVEVkTYfebYsA=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY2PR03MB443;
x-o365ent-eop-header: Message processed by - O365_ENT: Allow from ranges (Engineering ONLY)
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:(108003899814671);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(601004)(2401047)(8121501046)(520078)(5005006)(10201501046)(3002001)(61426038)(61427038); SRVR:BY2PR03MB443; BCL:0; PCL:0; RULEID:; SRVR:BY2PR03MB443;
x-forefront-prvs: 07778E4001
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(43784003)(164054003)(13464003)(377454003)(189002)(51914003)(199003)(87936001)(8990500004)(5003600100002)(5002640100001)(2900100001)(5005710100001)(105586002)(50986999)(10400500002)(15975445007)(33656002)(106356001)(74316001)(5004730100002)(99286002)(40100003)(77096005)(5003630100001)(5008740100001)(122556002)(2950100001)(230783001)(10290500002)(86362001)(106116001)(66066001)(102836003)(81156007)(92566002)(76176999)(54356999)(76576001)(110136002)(189998001)(19580395003)(86612001)(586003)(19580405001)(1220700001)(93886004)(11100500001)(3846002)(6116002)(1096002)(10090500001)(101416001)(5001960100002)(97736004); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR03MB443;; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None ( does not designate permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Dec 2015 19:39:13.2571 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR03MB443
Archived-At: <>
Cc: "" <>
Subject: Re: [OAUTH-WG] AD review of draft-ietf-oauth-proof-of-possession
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OAUTH WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 01 Dec 2015 19:39:38 -0000

Hi Kathleen,

As you saw, I posted draft -08 yesterday with the additional security considerations John, you, and I had discussed.  I wanted to check in with you and see if that addresses the point you were going to make in your ballot or whether there is more you'd like us to do before the IETF review.

				Best wishes,
				-- Mike

-----Original Message-----
From: Kathleen Moriarty [] 
Sent: Wednesday, November 25, 2015 6:21 AM
To: Mike Jones <>
Subject: Re: [OAUTH-WG] AD review of draft-ietf-oauth-proof-of-possession

Hi Mike,

If the working group is okay with the current text, leave it.  What you proposed is exactly the same as what is there.  I'll note this point in my ballot as I think you are leaving ambiguity that is not necessary.

After getting far enough on this, I think it was Pete who discussed this with you and he gave up and remained in disagreement.


Sent from my iPhone

> On Nov 24, 2015, at 10:25 PM, Mike Jones <> wrote:
> Rather than elaborating, having looked at the text we're discussing again, I'm going to counter-propose that we instead simplify - sticking only to the point that the paragraph is intending to get across.  Would it work for you to simplify the current text:
>    "A recipient might not understand the cnf claim, in which case it will typically be ignored. Unless this is acceptable behavior, applications that need the proof-of-possession keys communicated with it to be understood and processed must require that the parts of this specification that they use be implemented."
> to this simpler text?
>    "A recipient might not understand the cnf claim.  Applications that need the proof-of-possession keys communicated with it to be understood and processed must require that the parts of this specification that they use be implemented."
> The "must ignore" topic is already addressed in the second paragraph of 3.1 (and with exactly the semantics as the rest of JWT), and so doesn't have to be re-raised here, as it currently is.  Re-raising it is clearly a point of distraction.
> For what it's worth, I don't remember any DISCUSSes on this topic (although it's possible that your memory is better than mine on this point).
>                Best wishes,
>                -- Mike
> -----Original Message-----
> From: Kathleen Moriarty []
> Sent: Tuesday, November 24, 2015 7:14 PM
> To: Mike Jones <>
> Cc:
> Subject: Re: [OAUTH-WG] AD review of 
> draft-ietf-oauth-proof-of-possession
>> On Tue, Nov 24, 2015 at 10:10 PM, Mike Jones <> wrote:
>> Fair question about the use of "typically".  The reason it's there is that this language in JWT [RFC 7519] Section 4 does permit applications to require that JWTs with not-understood claims be rejected, rather than ignored, even though that's not the default behavior:
>>   The set of claims that a JWT must contain to be considered valid is
>>   context dependent and is outside the scope of this specification.
>>   Specific applications of JWTs will require implementations to
>>   understand and process some claims in particular ways.  However, in
>>   the absence of such requirements, all claims that are not understood
>>   by implementations MUST be ignored.
>> So when not understood, "cnf" would typically be ignored, but might not be.
> I find that confusing and am now thinking this came up in a discuss as well during the review for 7519, didn't it?  Can you elaborate int eh security considerations section a bit more, otherwise this text appears to be conflicting and even with what you intend, it's confusing for implementers and will lead to issues with interoperability.
> Thanks,
> Kathleen
>>                                -- Mike
>> -----Original Message-----
>> From: Kathleen Moriarty []
>> Sent: Tuesday, November 24, 2015 6:41 PM
>> To: Mike Jones <>
>> Cc:
>> Subject: Re: [OAUTH-WG] AD review of 
>> draft-ietf-oauth-proof-of-possession
>> Hi Mike,
>> Thanks for the quick turn-around.  Just one more comment on my comments.
>>> On Tue, Nov 24, 2015 at 9:10 PM, Mike Jones <> wrote:
>>> Thanks for your review comments, Kathleen.  Responses are inline below...
>>>> -----Original Message-----
>>>> From: OAuth [] On Behalf Of Kathleen 
>>>> Moriarty
>>>> Sent: Tuesday, November 24, 2015 9:44 AM
>>>> To:
>>>> Subject: [OAUTH-WG] AD review of
>>>> draft-ietf-oauth-proof-of-possession
>>>> Hi,
>>>> Thank you all for your work on this draft!  I just have a few questions:
>>>> 1. Security considerations section says:
>>>> "All of the normal security issues, especially in relationship to
>>>>   comparing URIs and dealing with unrecognized values, that are
>>>>   discussed in JWT [JWT] also apply here."
>>>> I find that to be odd phrasing that would likely be picked up in 
>>>> subsequent reviews.  Please remove the word "normal" so that all of 
>>>> the security issues discusses in JWT are included.  Are there other 
>>>> 'normal considerations in addition to those in JWT that need to be 
>>>> listed?  The phrasing reads as if that may the case and would be 
>>>> better to include them all or pointers or change the phrasing.
>>> You're right.  I removed this awkward wording.
>>>> 2. Also in the security considerations section,
>>>>   "A recipient may not understand the newly introduced "cnf" claim and
>>>>   may consequently treat it as a bearer token."
>>>> What is the proper handling requirement when an unknown claim is 
>>>> present?  Section 3.1 says:
>>>>  "When a recipient receives a "cnf" claim with a
>>>>   member that it does not understand, it MUST ignore that member."
>>>> Is this why it is treated as a bearer token rather than being 
>>>> rejected?  Is this really the action you want to see with cnf?  Why 
>>>> isn't there an error and a resend as a bearer token so that parties 
>>>> understand (or have an opportunity to understand) that there were issues?
>>>> Then the following text in the security section says:
>>>>  "While this is a
>>>>   legitimate concern, it is outside the scope of this specification,
>>>>   since demonstration the possession of the key associated with the
>>>>   "cnf" claim is not covered by this specification. For more 
>>>> details,
>>>> How is this outside of the scope of this draft?  cnf is defined in 
>>>> this draft, so handling should be covered in this draft.  A pointer 
>>>> to the POP architecture draft is not helpful as it is not defined 
>>>> there, it's covered int his draft.  Should this text just be 
>>>> removed and replaced with more explicit handling information int he body of this draft?
>>> Good catch.  JWT [RFC 7519] Section 4 says that claims that are not understood must be ignored unless otherwise specified by the application.  This allows new claims to be dynamically added without breaking existing applications.  For the same reason, I have incorporated this language about understanding claims from 7519, but having it be about understanding confirmation members.  Ultimately, what features must be implemented are always up to the application, just as with JWT claims.
>> The new text in Section 3.1 looks good.  I'm not sure why the word "typically" appears int he new text of the security considerations section though after reading the new text in 3.1.  Wouldn't it just be ignored since 3.1 now says:
>>   "However, in the absence of such requirements,
>>    all confirmation members that are not understood by implementations
>>    MUST be ignored."
>> Thanks,
>> Kathleen
>>>> Thanks!
>>>> --
>>>> Best regards,
>>>> Kathleen
>>>> _______________________________________________
>>>> OAuth mailing list
>>>                                Thanks again,
>>>                                -- Mike
>> --
>> Best regards,
>> Kathleen
> --
> Best regards,
> Kathleen