Re: [OAUTH-WG] Call for agenda items

n-sakimura <n-sakimura@nri.co.jp> Wed, 07 March 2018 07:00 UTC

Return-Path: <n-sakimura@nri.co.jp>
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 890FC127601 for <oauth@ietfa.amsl.com>; Tue, 6 Mar 2018 23:00:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.789
X-Spam-Level:
X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nri365.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JVeLmyGTtRX8 for <oauth@ietfa.amsl.com>; Tue, 6 Mar 2018 23:00:10 -0800 (PST)
Received: from nrifs02.index.or.jp (nrigw01.index.or.jp [133.250.250.1]) by ietfa.amsl.com (Postfix) with ESMTP id 479AF124C27 for <oauth@ietf.org>; Tue, 6 Mar 2018 23:00:09 -0800 (PST)
Received: from nrimmfm052.index.or.jp (unknown [172.19.246.144]) by nrifs02.index.or.jp (Postfix) with ESMTP id 9FAD1196886; Wed, 7 Mar 2018 16:00:08 +0900 (JST)
Received: from index.or.jp (unknown [172.19.246.151]) by nrimmfm052.index.or.jp (Postfix) with ESMTP id 3EF5E4E0046; Wed, 7 Mar 2018 16:00:08 +0900 (JST)
Received: from nriea03.index.or.jp (localhost.localdomain [127.0.0.1]) by pps.mf051 (8.15.0.59/8.15.0.59) with SMTP id w27708d8028224; Wed, 7 Mar 2018 16:00:08 +0900
Received: from nrims00a.nri.co.jp ([192.50.135.11]) by nriea03.index.or.jp with ESMTP id w277077Y028221; Wed, 07 Mar 2018 16:00:08 +0900
Received: from nrims00a.nri.co.jp (localhost.localdomain [127.0.0.1]) by nrims00a.nri.co.jp (Switch-3.3.4/Switch-3.3.4) with ESMTP id w27707rC054514; Wed, 7 Mar 2018 16:00:07 +0900
Received: (from mailnull@localhost) by nrims00a.nri.co.jp (Switch-3.3.4/Switch-3.3.0/Submit) id w27707Tg054513; Wed, 7 Mar 2018 16:00:07 +0900
X-Authentication-Warning: nrims00a.nri.co.jp: mailnull set sender to n-sakimura@nri.co.jp using -f
Received: from nrizmf12.index.or.jp ([172.100.25.21]) by nrims00a.nri.co.jp (Switch-3.3.4/Switch-3.3.4) with ESMTP id w27707X4054510; Wed, 7 Mar 2018 16:00:07 +0900
Received: from CUEXE01PA.cu.nri.co.jp (192.51.23.31) by CUEXM02PA.cu.nri.co.jp (172.159.253.20) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 7 Mar 2018 16:00:06 +0900
Received: from JPN01-TY1-obe.outbound.protection.outlook.com (23.103.139.179) by ex.nri.co.jp (192.51.23.31) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 7 Mar 2018 16:00:04 +0900
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nri365.onmicrosoft.com; s=selector1-cu-nri-co-jp; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ETo8GLZHBik9vg1f1FU4r7rPdhG0bAWbDNToet+0638=; b=BiOTj4eHv+j263FvqNJmsoCthHpTzCzGp1lsbzAArTqnBiReARRmFxEG52VfoWmvhFA23avc4OZrXVsUJExW/knOTccg9y2Hg+dd/vwQgsXAREh14CNYbREWQIUEGfTjS+oa4zVco6qlC05UL7W5ikuo9oSkw7abj+xripSMflg=
Received: from TY1PR01MB1054.jpnprd01.prod.outlook.com (10.174.225.12) by TY1PR01MB1865.jpnprd01.prod.outlook.com (52.133.161.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.548.13; Wed, 7 Mar 2018 07:00:05 +0000
Received: from TY1PR01MB1054.jpnprd01.prod.outlook.com ([10.174.225.12]) by TY1PR01MB1054.jpnprd01.prod.outlook.com ([10.174.225.12]) with mapi id 15.20.0548.016; Wed, 7 Mar 2018 07:00:05 +0000
From: n-sakimura <n-sakimura@nri.co.jp>
To: Brian Campbell <bcampbell@pingidentity.com>, Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
CC: oauth <oauth@ietf.org>
Thread-Topic: [OAUTH-WG] Call for agenda items
Thread-Index: AdOZokfkKl3QavjXR5+VNijf+3VIVAbDb1oAAA3y6gAAHchUAAACZoYAAB5NaXA=
Date: Wed, 07 Mar 2018 07:00:05 +0000
Message-ID: <TY1PR01MB1054A105034F55F6B810D7C3F9D80@TY1PR01MB1054.jpnprd01.prod.outlook.com>
References: <AM4PR0801MB270614990E501071CDB3A2F9FAE40@AM4PR0801MB2706.eurprd08.prod.outlook.com> <CAAP42hAy8iFHDa9hQxNMxytiWjf=MyrCDRzZ4MjvRq8xi0+Baw@mail.gmail.com> <CABzCy2DzJUL86MVTA9xL4Cpv4=ooZyZJ3N1QNS0QKvgr8DJHgA@mail.gmail.com> <CAGL6epLa0J0-JH8-cZX_WZ5Ztficz0_n+C9dOP80Gkbp_jvPFQ@mail.gmail.com> <CA+k3eCSVdUWu2Cz1N6tF_V1wVJS_+v8UudvWyosc9W6DLt9HkA@mail.gmail.com>
In-Reply-To: <CA+k3eCSVdUWu2Cz1N6tF_V1wVJS_+v8UudvWyosc9W6DLt9HkA@mail.gmail.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailadviser: 20170719
authentication-results: spf=none (sender IP is ) smtp.mailfrom=n-sakimura@cu.nri.co.jp;
x-originating-ip: [133.250.250.4]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; TY1PR01MB1865; 7:SbpXj1/WB9f66RG7Py7i33lacFHc/2nrsGxse8ypgoVqC8kB00fxJmKM4m5BbyvEjx7AqISVLa1nHrlOvdRvm+Bqc+Q/jqgkiot7EVQ8gK+hZkYOopTB3XlPEKpfKJpQu9qypZSOcZMRZR6SxVSxDFhKnt16vzmLxILHnlpBR9vUwxhLEl/4m0b90SB6cjaOMB+ygBlfoExxU0GZbp4aqAy0v0qJjK0A6Ay3OKzl3LTG9/oaeBmQCD/8Eq0JOw33
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 4168b3ab-44da-47ef-7a6d-08d583f90e77
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:TY1PR01MB1865;
x-ms-traffictypediagnostic: TY1PR01MB1865:
x-microsoft-antispam-prvs: <TY1PR01MB1865914D8E8C7B80A8F07FECF9D80@TY1PR01MB1865.jpnprd01.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(180628864354917)(192374486261705)(85827821059158)(211936372134217)(100405760836317)(153496737603132)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040501)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(10201501046)(3231220)(944501244)(52105095)(6041288)(20161123560045)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123558120)(6072148)(201708071742011); SRVR:TY1PR01MB1865; BCL:0; PCL:0; RULEID:; SRVR:TY1PR01MB1865;
x-forefront-prvs: 0604AFA86B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39830400003)(376002)(39380400002)(366004)(346002)(199004)(189003)(36304003)(40434004)(53754006)(2906002)(33656002)(105586002)(26005)(3280700002)(25786009)(77096007)(76176011)(6246003)(316002)(59450400001)(53936002)(4326008)(102836004)(106356001)(6436002)(236005)(9686003)(53546011)(6506007)(54896002)(6306002)(55016002)(2950100002)(5890100001)(186003)(68736007)(606006)(86362001)(81156014)(81166006)(8676002)(5660300001)(8936002)(2900100001)(229853002)(110136005)(66066001)(966005)(14454004)(478600001)(3660700001)(74316002)(74482002)(7736002)(7696005)(99286004)(97736004)(3846002)(39060400002)(93886005)(6116002); DIR:OUT; SFP:1102; SCL:1; SRVR:TY1PR01MB1865; H:TY1PR01MB1054.jpnprd01.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en;
received-spf: None (protection.outlook.com: cu.nri.co.jp does not designate permitted sender hosts)
x-microsoft-antispam-message-info: herYmjxgCAjS/wwPPT1u4HVe9cp6WA6DwHNqzMuyblnBKrbA9CdPLe2dN+t6WkVdBfsryiAkwdh/0T1NG+CUrRrhBU+cSSEAJvnRwn5dWevbIAXzR2ecYiCRsduKIJuWFroYkiYiAjJXZmJzB2cMcKSehqLjXbzTV8yT6f6yK+CSZ7+V9ERW4IpGQXhWD4KnFXqmdRAUKCiEUWFNUHW8+uzkTEdzNe9WWuqC1UHeboC85EhUcitNz/kI5P2qwZcc0lmYaldRu8vk6/iuD/VO9gK4W2j6VqmQxdyTXdW3isQE9jKqDKJQlFSGO235h128dpZ6xrxdsPr4qL7+62xbYg==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_TY1PR01MB1054A105034F55F6B810D7C3F9D80TY1PR01MB1054jpnp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 4168b3ab-44da-47ef-7a6d-08d583f90e77
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Mar 2018 07:00:05.4818 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: e3e360d9-7e7f-48d5-ac33-3c5de61f0a75
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TY1PR01MB1865
X-OrganizationHeadersPreserved: TY1PR01MB1865.jpnprd01.prod.outlook.com
X-CrossPremisesHeadersPromoted: CUEXE01PA.cu.nri.co.jp
X-CrossPremisesHeadersFiltered: CUEXE01PA.cu.nri.co.jp
X-OriginatorOrg: cu.nri.co.jp
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/MrDOA54mPCz1wiIKsQ1Uf4QGVAc>
Subject: Re: [OAUTH-WG] Call for agenda items
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 07 Mar 2018 07:00:17 -0000

Then let us do it. We need to put all the proposals on the table and strategize the design.
Perhaps we need a side meeting as well.

nat

From: OAuth [mailto:oauth-bounces@ietf.org] On Behalf Of Brian Campbell
Sent: Wednesday, March 07, 2018 1:31 AM
To: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Cc: oauth <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Call for agenda items

I hadn't previously been planning on it but am happy to do so.

On Tue, Mar 6, 2018 at 8:22 AM, Rifaat Shekh-Yusef <rifaat.ietf@gmail.com<mailto:rifaat.ietf@gmail.com>> wrote:
Nat,

During the interim meeting, 3 drafts mentioned in the context of Distributed OAuth:

https://tools.ietf.org/html/draft-sakimura-oauth-meta-08
https://tools.ietf.org/html/draft-campbell-oauth-resource-indicators-02
https://tools.ietf.org/html/draft-tschofenig-oauth-audience-00


Brian, Hannes,

Are you planning on presenting your documents?

Regards,
 Rifaat






On Mon, Mar 5, 2018 at 8:09 PM, Nat Sakimura <sakimura@gmail.com<mailto:sakimura@gmail.com>> wrote:
I would be interested in hearing that.

Also, as part of "Distributed OAuth", can we do a bit of re-cap on some of the previous drafts on the similar topic as we discussed in the interim? i.e., Brian's draft (where is the link now?) and my draft (draft-sakimura-oauth-meta<https://tools.ietf.org/id/draft-sakimura-oauth-meta-08.txt>)?

Best,

Nat

On Tue, Mar 6, 2018 at 3:30 AM William Denniss <wdenniss@google.com<mailto:wdenniss@google.com>> wrote:
Hannes & Rifaat,

I would like the opportunity to present on OAuth 2.0 Incremental Authorization (draft-wdenniss-oauth-incremental-auth) [an update for which will be posted today] and "OAuth 2.0 Device Posture Signals" (draft-wdenniss-oauth-device-posture).

I can also give an update on the status of Device Flow (draft-ietf-oauth-device-flow). I expect that to be short now that WGLC has concluded and the document has advanced.

Little late to this thread and I see we already have 2 sessions in the draft agenda, but I'd like to add my support to keeping both sessions, there's always a lot to discuss and in the past we've been able to use any spare time to discuss the security topics of the day.

Regards,
William



On Tue, Jan 30, 2018 at 4:40 AM Hannes Tschofenig <Hannes.Tschofenig@arm.com<mailto:Hannes.Tschofenig@arm.com>> wrote:
Hi all,

It is time already to think about the agenda for the next IETF meeting. Rifaat and I were wondering whether we need one or two sessions. We would like to make the decision based on the topics we will discuss. Below you can find a first version of the agenda with a few remarks. Let us know if you have comments or suggestions for additional agenda items.

Ciao
Hannes & Rifaat

OAuth Agenda
------------

- Welcome and Status Update  (Chairs)

  * OAuth Security Workshop Report

  * Documents in IESG processing
     # draft-ietf-oauth-device-flow-07
     # draft-ietf-oauth-discovery-08
     # draft-ietf-oauth-jwsreq-15
     # draft-ietf-oauth-token-exchange-11

       Remark: Status updates only if needed.

-  JSON Web Token Best Current Practices
   # draft-ietf-oauth-jwt-bcp-00

   Remark: We are lacking reviews on this document.
   Most likely we will not get them during the f2f meeting
   but rather by reaching out to individuals ahead of time.

-  OAuth 2.0 Mutual TLS Client Authentication and Certificate Bound Access Tokens
   # draft-ietf-oauth-mtls-06

   Remark: Could be completed by the time of the IETF meeting.

- OAuth Security Topics
  # draft-ietf-oauth-security-topics-04

  Remark: We could do a consensus call on parts of the document soon.

- OAuth 2.0 Token Binding
  # draft-ietf-oauth-token-binding-05

  Remark: Document is moving along but we are lacking implementations.

- OAuth 2.0 Device Posture Signals
  # draft-wdenniss-oauth-device-posture-01

  Remark: Interest in the work but we are lacking content (maybe even
  expertise in the group)

- Reciprocal OAuth
  # draft-hardt-oauth-mutual-02

  Remark: We had a virtual interim meeting on this topic and there is
  interest in this work and apparently no competing solutions. The plan
  is to run a call for adoption once we are allowed to add a new milestone
  to our charter.

- Distributed OAuth
  # draft-hardt-oauth-distributed-00

  Remark: We had a virtual interim meeting on this topic and there is
  interest in this work. Further work on the scope is needed.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
_______________________________________________
OAuth mailing list
OAuth@ietf.org<mailto:OAuth@ietf.org>
https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________
OAuth mailing list
OAuth@ietf.org<mailto:OAuth@ietf.org>
https://www.ietf.org/mailman/listinfo/oauth
--

Nat Sakimura

Chairman of the Board, OpenID Foundation

_______________________________________________
OAuth mailing list
OAuth@ietf.org<mailto:OAuth@ietf.org>
https://www.ietf.org/mailman/listinfo/oauth


_______________________________________________
OAuth mailing list
OAuth@ietf.org<mailto:OAuth@ietf.org>
https://www.ietf.org/mailman/listinfo/oauth


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.