Return-Path: X-Original-To: oauth@core3.amsl.com Delivered-To: oauth@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B1B23A6C48 for ; Sun, 26 Sep 2010 21:20:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.902 X-Spam-Level: X-Spam-Status: No, score=-9.902 tagged_above=-999 required=5 tests=[AWL=0.696, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bcKZ3Tn4qtJY for ; Sun, 26 Sep 2010 21:20:06 -0700 (PDT) Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id CD20B3A6AF9 for ; Sun, 26 Sep 2010 21:20:06 -0700 (PDT) Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Sun, 26 Sep 2010 21:20:44 -0700 Received: from TK5EX14MBXC202.redmond.corp.microsoft.com ([169.254.2.167]) by TK5EX14MLTC104.redmond.corp.microsoft.com ([157.54.79.159]) with mapi id 14.01.0218.012; Sun, 26 Sep 2010 21:20:44 -0700 From: Mike Jones To: Dick Hardt Thread-Topic: [OAUTH-WG] JSON Web Token (JWT) Specification Draft Thread-Index: Actbfov76Bkh7l/GQKOvG+24lxItYgCtviMAAA6kzvA= Date: Mon, 27 Sep 2010 04:20:44 +0000 Message-ID: <4E1F6AAD24975D4BA5B168042967394313FBA71C@TK5EX14MBXC202.redmond.corp.microsoft.com> References: <4E1F6AAD24975D4BA5B168042967394313F95E5F@TK5EX14MBXC202.redmond.corp.microsoft.com> <9B677A76-F163-4542-B898-EFAF612D936B@gmail.com> In-Reply-To: <9B677A76-F163-4542-B898-EFAF612D936B@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [157.54.123.12] Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B168042967394313FBA71CTK5EX14MBXC202r_" MIME-Version: 1.0 Cc: "oauth@ietf.org" Subject: Re: [OAUTH-WG] JSON Web Token (JWT) Specification Draft X-BeenThere: oauth@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: OAUTH WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Sep 2010 04:20:11 -0000 --_000_4E1F6AAD24975D4BA5B168042967394313FBA71CTK5EX14MBXC202r_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I'd be open to a proposal for also supporting encryption. The draft was in= tended to be a starting point for productive discussion - not a finished pr= oduct. Your thoughts? -- Mike From: Dick Hardt [mailto:dick.hardt@gmail.com] Sent: Sunday, September 26, 2010 9:17 PM To: Mike Jones Cc: oauth@ietf.org Subject: Re: [OAUTH-WG] JSON Web Token (JWT) Specification Draft Did you intentionally decide not to support encrypting the token? On 2010-09-23, at 5:22 PM, Mike Jones wrote: Recognizing that there is substantial interest in representing sets of clai= ms in JSON tokens, Yaron Goland and I have put together a draft JSON Web To= ken (JWT) spec for that purpose. To answer the obvious question, while this was produced independently of Di= rk's JSON token proposal, both of us agree that we should come up with a uni= fied spec. Consider this an additional point in the possible design space = from which to start discussions and drive consensus. (If you read the two = proposals, I think you'll find that there's already a lot in common, which = is great.) Thanks to those of you who have already given us feedback to improve the dr= aft prior to this point. Cheers, -- Mike _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth --_000_4E1F6AAD24975D4BA5B168042967394313FBA71CTK5EX14MBXC202r_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I’d be open to a pr= oposal for also supporting encryption.  The draft was intended to be a= starting point for productive discussion – not a finished product.

 <= /p>

Your thoughts?=

 <= /p>

    &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;     -- Mike

 <= /p>

From: Dick Har= dt [mailto:dick.hardt@gmail.com]
Sent: Sunday, September 26, 2010 9:17 PM
To: Mike Jones
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] JSON Web Token (JWT) Specification Draft

 

Did you intentionally decide not to support encrypti= ng the token?

 

On 2010-09-23, at 5:22 PM, Mike Jones wrote:



Recognizing that there is substantial i= nterest in representing sets of claims in JSON tokens, Yaron Goland and I h= ave put together a draft JSON Web Token (JWT) spec for that purpose.

 

To answer the obvious question, while t= his was produced independently of&nbs= p;Dirk’s JSON token proposal, both of us agree that we should come up with a un= ified spec.  Consider this an additional point in the possible design = space from which to start discussions and drive consensus.  (If you re= ad the two proposals, I think you’ll find that there’s already a lot in common, which is great.)

 

Thanks to those of you who have already= given us feedback to improve the draft prior to this point.

 

      &nb= sp;            =             &nb= sp;            =             &nb= sp;   Cheers,

      &nb= sp;            =              &n= bsp;            = ;            &n= bsp;  -- Mike

 

<jwt.html><jwt.xml>______= _________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.or= g/mailman/listinfo/oauth

 

--_000_4E1F6AAD24975D4BA5B168042967394313FBA71CTK5EX14MBXC202r_--