IETF Logo Mail Archive

[OAUTH-WG] JSON Token spec work at IIW

Mike Jones <Michael.Jones@microsoft.com> Wed, 10 November 2010 05:59 UTC

Return-Path: <Michael.Jones@microsoft.com>
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 1CFFA3A68A2 for <oauth@core3.amsl.com>; Tue, 9 Nov 2010 21:59:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=0.000, 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 CPdguEwQwYBH for <oauth@core3.amsl.com>; Tue, 9 Nov 2010 21:59:20 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id 4CDD83A67DB for <oauth@ietf.org>; Tue, 9 Nov 2010 21:59:20 -0800 (PST)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 9 Nov 2010 21:59:46 -0800
Received: from TK5EX14MBXC202.redmond.corp.microsoft.com ([169.254.2.127]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.01.0255.003; Tue, 9 Nov 2010 21:59:46 -0800
From: Mike Jones <Michael.Jones@microsoft.com>
To: "oauth@ietf.org" <oauth@ietf.org>
Thread-Topic: JSON Token spec work at IIW
Thread-Index: AcuAnHngxqllPP84QQuaDfx3hl7Zjw==
Date: Wed, 10 Nov 2010 05:59:46 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943245DF444@TK5EX14MBXC202.redmond.corp.microsoft.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_4E1F6AAD24975D4BA5B1680429673943245DF444TK5EX14MBXC202r_"
MIME-Version: 1.0
Cc: "openid-specs-ab@lists.openid.net" <openid-specs-ab@lists.openid.net>, "openid-specs-connect@lists.openid.net" <openid-specs-connect@lists.openid.net>
Subject: [OAUTH-WG] JSON Token spec work at IIW
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Nov 2010 05:59:23 -0000

I've now finished my series of posts on the JSON token spec work that occurred at IIW.  For reference, they are:

  - JSON Token Spec Results at IIW on Tuesday:  http://self-issued.info/?p=361

  - JSON Token Encryption Spec Results at IIW on Wednesday:  http://self-issued.info/?p=378

  - JSON Token Naming Spec Results at IIW on Wednesday:  http://self-issued.info/?p=386
  - JSON Public Key Spec Results at IIW on Thursday:  http://self-issued.info/?p=390

                                                            Cheers,
                                                            -- Mike

v2.23.0 | Report a Bug | By Email