[OAUTH-WG] Next steps on the OAuth Assertion Drafts

"Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com> Tue, 10 September 2013 14:26 UTC

Return-Path: <hannes.tschofenig@nsn.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B234D11E81D0 for <oauth@ietfa.amsl.com>; Tue, 10 Sep 2013 07:26:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Boh7bCaacDyA for <oauth@ietfa.amsl.com>; Tue, 10 Sep 2013 07:26:48 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 636C411E81B7 for <oauth@ietf.org>; Tue, 10 Sep 2013 07:26:37 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id r8AEQXGg008925 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <oauth@ietf.org>; Tue, 10 Sep 2013 16:26:33 +0200
Received: from USCHHTC001.nsn-intra.net ([10.159.161.14]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id r8AEQO05003655 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <oauth@ietf.org>; Tue, 10 Sep 2013 16:26:33 +0200
Received: from USCHHTC004.nsn-intra.net (10.159.161.17) by USCHHTC001.nsn-intra.net (10.159.161.14) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 10 Sep 2013 09:26:30 -0500
Received: from USCHMBX001.nsn-intra.net ([169.254.1.11]) by USCHHTC004.nsn-intra.net ([10.159.161.17]) with mapi id 14.03.0123.003; Tue, 10 Sep 2013 09:26:30 -0500
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: "oauth@ietf.org" <oauth@ietf.org>
Thread-Topic: Next steps on the OAuth Assertion Drafts
Thread-Index: Ac6uKyKB5V+iuMO1SeCJM7UwusBI5A==
Date: Tue, 10 Sep 2013 14:26:29 +0000
Message-ID: <1373E8CE237FCC43BCA36C6558612D2AA33964@USCHMBX001.nsn-intra.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.159.42.97]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 1855
X-purgate-ID: 151667::1378823193-00003561-146DF74B/0-0/0-0
Subject: [OAUTH-WG] Next steps on the OAuth Assertion Drafts
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 10 Sep 2013 14:26:58 -0000

Hi all, 

I am trying to wrap up the assertion documents and I took a look at the meeting minutes from the Berlin IETF meeting and the actions are as follows:

** John & Torsten: Please post your document review to the list.

** Authors of draft-ietf-oauth-saml2-bearer: Please provide the additional SAML related text (as discussed during the meeting) and submit an updated document. 

Ciao
Hannes

------- copy from the minutes --------

* Assertions (BC)
 https://datatracker.ietf.org/doc/draft-ietf-oauth-assertions/
 https://datatracker.ietf.org/doc/draft-ietf-oauth-jwt-bearer/
 https://datatracker.ietf.org/doc/draft-ietf-oauth-saml2-bearer/

    - WGLC ends by 8/8
    - BL on WGLC comments: talked to MJ about how to achieve interop.
    - BL: describe how you could combine specifications to make at least one interoperable specification
    - MJ: profiles exists for both SAML and OpenIDC. those are not IETF specifications though
    - BL: ok to point to external doc from either of the I-Ds in question
    - MJ: very achievable
    - BL: all should go to the IESG at the same time to establish context
    - PHO: is this for the IESG benefit or for future developers
    - BL: the latter
    - PHO: talk to Heather Flanagan or the IANA - they have talked about having long-term access to external documents
    - BL: ok will consider that - or we can copy text into WG wiki
    - BC: interop does not require external profiles actually
    - TL: same experience at DT with the JSON-based assertion format - no addl profiles are needed
    - MJ: a SAML deployment needs agreement on certain SAML-specific conventions - this is what BL is referring to
    - BC: right
    - TN: so just refer to the SAML specs
    - BL: maybe enough
    - JB and TL volunteered to make a review.