Re: [OAUTH-WG] Call for adoption - OAuth 2.1 document

2020-07-15 Thread vittorio . bertocci=40auth0 . com 
+1

 

From: OAuth  On Behalf Of Dick Hardt
Sent: Wednesday, July 15, 2020 10:55 AM
To: Rifaat Shekh-Yusef 
Cc: oauth 
Subject: Re: [OAUTH-WG] Call for adoption - OAuth 2.1 document

 

+1

 

On Wed, Jul 15, 2020 at 10:42 AM Rifaat Shekh-Yusef mailto:rifaat.s.i...@gmail.com> > wrote:

All,

 

This is a call for adoption for the following OAuth 2.1 document as a WG 
document:

https://www.ietf.org/id/draft-parecki-oauth-v2-1-03.html

 

Please, provide your feedback on the mailing list by July 29th.

 

Regards,

 Rifaat & Hannes

 

___
OAuth mailing list
OAuth@ietf.org  
https://www.ietf.org/mailman/listinfo/oauth

___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

Re: [OAUTH-WG] Call for adoption - OAuth 2.1 document

2020-07-15 Thread Sascha Preibisch 
+1

On Wed, 15 Jul 2020 at 13:40, Hans Zandbelt  wrote:
>
> +1
>
> Hans.
>
> On Wed, Jul 15, 2020 at 7:43 PM Rifaat Shekh-Yusef  
> wrote:
>>
>> All,
>>
>> This is a call for adoption for the following OAuth 2.1 document as a WG 
>> document:
>> https://www.ietf.org/id/draft-parecki-oauth-v2-1-03.html
>>
>> Please, provide your feedback on the mailing list by July 29th.
>>
>> Regards,
>>  Rifaat & Hannes
>>
>> ___
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>
>
>
> --
> hans.zandb...@zmartzone.eu
> ZmartZone IAM - www.zmartzone.eu
> ___
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

[OAUTH-WG] OAuth WG Interims - Aug/Sep 2020

2020-07-15 Thread Rifaat Shekh-Yusef 
All,

As you might have noticed, we are starting a series of interim meetings in
August and September.
We have scheduled the following two meetings with specific topics:
1. *Aug 3rd* @ 12:00pm EDT to discuss *OAuth 2.1 *document.
2. *Aug 10th *@ 12:00pm EDT to discuss the *PAR* document

More to follow.

If you are interested in presenting your document during one of these
upcoming interims, and have not contacted us already, please do so as soon
as possible.

Regards,
 Rifaat & Hannes
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

[OAUTH-WG] Fwd: Webex meeting changed: OAuth WG - Aug 10th Interim

2020-07-15 Thread Rifaat Shekh-Yusef 
-- Forwarded message -
From: Web Authorization Protocol Working Group 
Date: Wed, Jul 15, 2020 at 5:09 PM
Subject: Webex meeting changed: OAuth WG - Aug 10th Interim
To: 

Brian noticed that the time was incorrect for this meeting, so I have
updated the meeting with the proper time.

Regards,
 Rifaat



You changed the Webex meeting information.


When it's time, start your Webex meeting here.

Meeting number (access code): 161 640 8279
Meeting password: x2H2VwPMUu9

Monday, August 10, 2020
12:00 pm  |  (UTC-04:00) Eastern Time (US & Canada)  |  1 hr

Start meeting


*Tap to join from a mobile device (attendees only)*
+1-650-479-3208,,1616408279## <%2B1-650-479-3208,,*01*1616408279%23%23*01*>
Call-in toll number (US/Canada)

*Join by phone*
1-650-479-3208 Call-in toll number (US/Canada)
Global call-in numbers


*Join from a video system or application*
Dial 1616408...@ietf.webex.com
You can also dial 173.243.2.68 and enter your meeting number.

*Join using Microsoft Lync or Microsoft Skype for Business*
Dial 1616408279.i...@lync.webex.com

If you are a host, click here

to view host information.

Need help? Go to http://help.webex.com


invite.ics
Description: application/ics


Webex_Meeting.ics
Description: application/ics
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

Re: [OAUTH-WG] Call for adoption - OAuth 2.1 document

2020-07-15 Thread Hans Zandbelt 
+1

Hans.

On Wed, Jul 15, 2020 at 7:43 PM Rifaat Shekh-Yusef 
wrote:

> All,
>
> This is a *call for adoption* for the following *OAuth 2.1* document as a
> WG document:
> https://www.ietf.org/id/draft-parecki-oauth-v2-1-03.html
>
> Please, provide your feedback on the mailing list by *July 29th.*
>
> Regards,
>  Rifaat & Hannes
>
> ___
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>


-- 
hans.zandb...@zmartzone.eu
ZmartZone IAM - www.zmartzone.eu
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

[OAUTH-WG] Fwd: (Forward to others) Webex meeting invitation: OAuth WG - Aug 3rd Interim

2020-07-15 Thread Rifaat Shekh-Yusef 
BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 10.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/New_York
TZURL:http://tzurl.org/zoneinfo-outlook/America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20200715T172011Z
ATTENDEE;CN="Web Authorization Protocol Working Group";ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:oauth-cha...@ietf.org
ORGANIZER;CN="Web Authorization Protocol Working Group":MAILTO:oauth-cha...@ietf.org
DTSTART;TZID=America/New_York:20200803T12
DTEND;TZID=America/New_York:20200803T13
LOCATION:https://ietf.webex.com/ietf/j.php?MTID=m1285bd51ffb5dcd173147c531b5fabf3
TRANSP:OPAQUE
SEQUENCE:1594833611
UID:2f650555-8e74-4f50-b9eb-e9391e18fd91
DESCRIPTION:\n\n\n\nJOIN WEBEX MEETING\nhttps://ietf.webex.com/ietf/j.php?MTID=m1285bd51ffb5dcd173147c531b5fabf3\nMeeting number (access code): 161 700 3301\n\nMeeting password: 99N5Myuqwph\n\n\n\nTAP TO JOIN FROM A MOBILE DEVICE (ATTENDEES ONLY)\n+1-650-479-3208,,1617003301## tel:%2B1-650-479-3208,,*01*1617003301%23%23*01* Call-in toll number (US/Canada)\n\n\nJOIN BY PHONE\n1-650-479-3208 Call-in toll number (US/Canada)\n\nGlobal call-in numbers\nhttps://ietf.webex.com/ietf/globalcallin.php?MTID=m2d91ed8ceb631fdacdc654450f71b65f\n\n\nJOIN FROM A VIDEO SYSTEM OR APPLICATION\nDial sip:1617003...@ietf.webex.com\nYou can also dial 173.243.2.68 and enter your meeting number.\n\n\nJoin using Microsoft Lync or Microsoft Skype for Business\nDial sip:1617003301.i...@lync.webex.com\n\n\n\n\n\nCan't join the meeting?\nhttps://collaborationhelp.cisco.com/article/WBX29055\n\n\nIMPORTANT NOTICE: Please note that this Webex service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session.\n
X-ALT-DESC;FMTTYPE=text/html:\ntable {\n	border-collapse: separate; width =100%;	border: 0;	border-spacing: 0;}\n\ntr {\n	line-height: 18px;}\n\na, td {\n	font-size: 14px;	font-family: Arial;	color: #333;	word-wrap: break-word;	word-break: normal;	padding: 0;}\n\n.title {\n	font-size: 28px;}\n\n.image {\n	width: auto;	max-width: auto;}\n\n.footer {\n	width: 604px;}\n\n.main {\n\n}@media screen and (max-device-width: 800px) {\n	.title {\n		font-size: 22px !important;	}\n	.image {\n		width: auto !important;		max-width: 100% !important;	}\n	.footer {\n		width: 100% !important;		max-width: 604px !important\n	}\n	.main {\n		width: 100% !important;		max-width: 604px !important\n	}\n}\n\n\n\n	\n	\n		\n			\n\n\n\n\n\n			\n\n	\n		When it's time, join the Webex meeting here.\n	\n\n\n\n	\n		Meeting number (access code): 161 700 3301\n	\n\n			\n			Meeting password:99N5Myuqwph\n\n\n	\n			\n\n	\n		\n			https://ietf.webex.com/ietf/j.php?MTID=m1285bd51ffb5dcd173147c531b5fabf3; style="color:#FF; font-size:20px; text-decoration:none;">Join meeting\n		\n	\n\n			\n		\n\n \n\n\n Tap to join from a mobile device (attendees only)  +1-650-479-3208,,1617003301## Call-in toll number (US/Canada) Join by phone  1-650-479-3208 Call-in toll number (US/Canada)  https://ietf.webex..com/ietf/globalcallin.php?MTID=m2d91ed8ceb631fdacdc654450f71b65f; style="text-decoration:none;font-size:14px;color:#00AFF9">Global call-in numbers \n\n\n\nJoin from a video system or applicationDial 1617003...@ietf.webex.com You can also dial 173.243.2.68 and enter your meeting number.   \n\nJoin using Microsoft Lync or Microsoft Skype for BusinessDial 1617003301.i...@lync.webex.com\n\n	\n	\n\n			\n\n\n	Need help? Go to http://help.webex.com; style="color:#049FD9; text-decoration:none;">http://help.webex.com\n	\n\n\n			\n		\n	\n\n
SUMMARY:OAuth WG - Aug 3rd Interim
PRIORITY:5
CLASS:PUBLIC
BEGIN:VALARM
TRIGGER:-PT5M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR


Webex_Meeting.ics
Description: application/ics
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

[OAUTH-WG] Fwd: (Forward to others) Webex meeting invitation: OAuth WG - Aug 10th Interim

2020-07-15 Thread Rifaat Shekh-Yusef 
BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 10.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/New_York
TZURL:http://tzurl.org/zoneinfo-outlook/America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20200715T172806Z
ATTENDEE;CN="Web Authorization Protocol Working Group";ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:oauth-cha...@ietf.org
ORGANIZER;CN="Web Authorization Protocol Working Group":MAILTO:oauth-cha...@ietf.org
DTSTART;TZID=America/New_York:20200810T06
DTEND;TZID=America/New_York:20200810T07
LOCATION:https://ietf.webex.com/ietf/j.php?MTID=m02cd2236222d8e7032dac03ee763d386
TRANSP:OPAQUE
SEQUENCE:1594834086
UID:231b1bad-abc7-4707-b7e6-307147247c29
DESCRIPTION:\n\n\n\nJOIN WEBEX MEETING\nhttps://ietf.webex.com/ietf/j.php?MTID=m02cd2236222d8e7032dac03ee763d386\nMeeting number (access code): 161 640 8279\n\nMeeting password: x2H2VwPMUu9\n\n\n\nTAP TO JOIN FROM A MOBILE DEVICE (ATTENDEES ONLY)\n+1-650-479-3208,,1616408279## tel:%2B1-650-479-3208,,*01*1616408279%23%23*01* Call-in toll number (US/Canada)\n\n\nJOIN BY PHONE\n1-650-479-3208 Call-in toll number (US/Canada)\n\nGlobal call-in numbers\nhttps://ietf.webex.com/ietf/globalcallin.php?MTID=m50db3a00ed4125cdeb4a6bf0e352cfbf\n\n\nJOIN FROM A VIDEO SYSTEM OR APPLICATION\nDial sip:1616408...@ietf.webex.com\nYou can also dial 173.243.2.68 and enter your meeting number.\n\n\nJoin using Microsoft Lync or Microsoft Skype for Business\nDial sip:1616408279.i...@lync.webex.com\n\n\n\n\n\nCan't join the meeting?\nhttps://collaborationhelp.cisco.com/article/WBX29055\n\n\nIMPORTANT NOTICE: Please note that this Webex service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session.\n
X-ALT-DESC;FMTTYPE=text/html:\ntable {\n	border-collapse: separate; width =100%;	border: 0;	border-spacing: 0;}\n\ntr {\n	line-height: 18px;}\n\na, td {\n	font-size: 14px;	font-family: Arial;	color: #333;	word-wrap: break-word;	word-break: normal;	padding: 0;}\n\n.title {\n	font-size: 28px;}\n\n.image {\n	width: auto;	max-width: auto;}\n\n.footer {\n	width: 604px;}\n\n.main {\n\n}@media screen and (max-device-width: 800px) {\n	.title {\n		font-size: 22px !important;	}\n	.image {\n		width: auto !important;		max-width: 100% !important;	}\n	.footer {\n		width: 100% !important;		max-width: 604px !important\n	}\n	.main {\n		width: 100% !important;		max-width: 604px !important\n	}\n}\n\n\n\n	\n	\n		\n			\n\n\n\n\n\n			\n\n	\n		When it's time, join the Webex meeting here.\n	\n\n\n\n	\n		Meeting number (access code): 161 640 8279\n	\n\n			\n			Meeting password:x2H2VwPMUu9\n\n\n	\n			\n\n	\n		\n			https://ietf.webex.com/ietf/j.php?MTID=m02cd2236222d8e7032dac03ee763d386; style="color:#FF; font-size:20px; text-decoration:none;">Join meeting\n		\n	\n\n			\n		\n\n \n\n\n Tap to join from a mobile device (attendees only)  +1-650-479-3208,,1616408279## Call-in toll number (US/Canada) Join by phone  1-650-479-3208 Call-in toll number (US/Canada)  https://ietf.webex..com/ietf/globalcallin.php?MTID=m50db3a00ed4125cdeb4a6bf0e352cfbf; style="text-decoration:none;font-size:14px;color:#00AFF9">Global call-in numbers \n\n\n\nJoin from a video system or applicationDial 1616408...@ietf.webex.com You can also dial 173.243.2.68 and enter your meeting number.   \n\nJoin using Microsoft Lync or Microsoft Skype for BusinessDial 1616408279.i...@lync.webex.com\n\n	\n	\n\n			\n\n\n	Need help? Go to http://help.webex.com; style="color:#049FD9; text-decoration:none;">http://help.webex.com\n	\n\n\n			\n		\n	\n\n
SUMMARY:OAuth WG - Aug 10th Interim
PRIORITY:5
CLASS:PUBLIC
BEGIN:VALARM
TRIGGER:-PT5M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR


Webex_Meeting.ics
Description: application/ics
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

Re: [OAUTH-WG] (Forward to others) Webex meeting invitation: OAuth WG - Aug 3rd Interim

2020-07-15 Thread Rifaat Shekh-Yusef 
On Wed, Jul 15, 2020 at 1:20 PM Web Authorization Protocol Working Group <
messen...@webex.com> wrote:

>
> You can forward this invitation to others.
> Web Authorization Protocol Working Group invites you to join this Webex
> meeting.
>
> Meeting number (access code): 161 700 3301
> Meeting password: 99N5Myuqwph
>
> Monday, August 3, 2020
> 12:00 pm  |  (UTC-04:00) Eastern Time (US & Canada)  |  1 hr
>
> Join meeting
> 
>
> *Tap to join from a mobile device (attendees only)*
> +1-650-479-3208,,1617003301##
> <%2B1-650-479-3208,,*01*1617003301%23%23*01*> Call-in toll number
> (US/Canada)
>
> *Join by phone*
> 1-650-479-3208 Call-in toll number (US/Canada)
> Global call-in numbers
> 
>
> *Join from a video system or application*
> Dial 1617003...@ietf.webex.com
> You can also dial 173.243.2.68 and enter your meeting number.
>
> *Join using Microsoft Lync or Microsoft Skype for Business*
> Dial 1617003301.i...@lync.webex.com
>
>
> Need help? Go to http://help.webex.com
>
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

Re: [OAUTH-WG] Call for adoption - OAuth 2.1 document

2020-07-15 Thread Falk Andreas 
+1

I support adoption


--

Andreas Falk
Managing Consultant / Practice Lead Agile Security

[Novatec Logo]

T. +49 711 22040-700 ∙ M. +49 151 
46146778
andreas.f...@novatec-gmbh.de ⋅ 
www.novatec-gmbh.de

Novatec Consulting GmbH
Dieselstraße 18/1, D-70771 Leinfelden-Echterdingen

Folgen Sie uns auf Facebook, 
LinkedIn, 
Twitter, 
XING oder auf unserem 
Blog

Sitz: Leinfelden-Echterdingen ∙ Handelsregister: Amtsgericht Stuttgart ∙ HRB 
739078
Geschäftsführer: Stefan Bleicher, Hans-Dieter Brenner, Konrad Pfeilsticker, 
Michael Schuchart


Von: OAuth  im Auftrag von Torsten Lodderstedt 

Gesendet: Mittwoch, 15. Juli 2020 21:40
An: John Bradley 
Cc: oauth@ietf.org 
Betreff: Re: [OAUTH-WG] Call for adoption - OAuth 2.1 document

+1

> On 15. Jul 2020, at 21:37, John Bradley  wrote:
>
> I support addoption
>
> On 7/15/2020 3:32 PM, Neil Madden wrote:
>> I support adoption.
>>
>>> On 15 Jul 2020, at 18:42, Rifaat Shekh-Yusef  
>>> wrote:
>>>
>>> 
>>> All,
>>>
>>> This is a call for adoption for the following OAuth 2.1 document as a WG 
>>> document:
>>> https://www.ietf.org/id/draft-parecki-oauth-v2-1-03.html
>>>
>>> Please, provide your feedback on the mailing list by July 29th.
>>>
>>> Regards,
>>>  Rifaat & Hannes
>>>
>>> ___
>>> OAuth mailing list
>>> OAuth@ietf.org
>>> https://www.ietf.org/mailman/listinfo/oauth
>>
>>
>> ___
>> OAuth mailing list
>>
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
> ___
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

[OAUTH-WG] Web Authorization Protocol (oauth) WG Virtual Meeting: 2020-08-10

2020-07-15 Thread IESG Secretary 
The Web Authorization Protocol (oauth) WG will hold
a virtual interim meeting on 2020-08-10 from 12:00 to 13:00 America/Toronto 
(16:00 to 17:00 UTC).

Agenda:
OAuth WG - Aug 10th Interim
Hosted by Web Authorization Protocol Working Group

Monday, Aug 10, 2020 12:00 pm | 1 hour | (UTC+02:00) Amsterdam, Berlin, Bern, 
Rome, Stockholm, Vienna
Meeting number: 161 640 8279
Password: x2H2VwPMUu9
https://ietf.webex.com/ietf/j.php?MTID=m02cd2236222d8e7032dac03ee763d386

Join by video system
Dial 1616408...@ietf.webex.com
You can also dial 173.243.2.68 and enter your meeting number.

Join by phone
1-650-479-3208 Call-in toll number (US/Canada)
Access code: 161 640 8279

Information about remote participation:
https://ietf.webex.com/ietf/j.php?MTID=m02cd2236222d8e7032dac03ee763d386

___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

[OAUTH-WG] Web Authorization Protocol (oauth) WG Virtual Meeting: 2020-08-03

2020-07-15 Thread IESG Secretary 
The Web Authorization Protocol (oauth) WG will hold
a virtual interim meeting on 2020-08-03 from 12:00 to 13:00 America/Toronto 
(16:00 to 17:00 UTC).

Agenda:
OAuth WG - Aug 3rd Interim
Hosted by Web Authorization Protocol Working Group

Monday, Aug 3, 2020 6:00 pm | 1 hour | (UTC+02:00) Amsterdam, Berlin, Bern, 
Rome, Stockholm, Vienna
Meeting number: 161 700 3301
Password: 99N5Myuqwph
https://ietf.webex.com/ietf/j.php?MTID=m1285bd51ffb5dcd173147c531b5fabf3

Join by video system
Dial 1617003...@ietf.webex.com
You can also dial 173.243.2.68 and enter your meeting number.

Join by phone
1-650-479-3208 Call-in toll number (US/Canada)
Access code: 161 700 3301

Information about remote participation:
https://ietf.webex.com/ietf/j.php?MTID=m1285bd51ffb5dcd173147c531b5fabf3

___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

Re: [OAUTH-WG] Call for adoption - OAuth 2.1 document

2020-07-15 Thread Michael A Peck 
+1
I support adoption of this document by the working group.

From: OAuth  on behalf of Dick Hardt 

Date: Wednesday, July 15, 2020 at 1:56 PM
To: Rifaat Shekh-Yusef 
Cc: "oauth@ietf.org" 
Subject: [EXT] Re: [OAUTH-WG] Call for adoption - OAuth 2.1 document

+1

On Wed, Jul 15, 2020 at 10:42 AM Rifaat Shekh-Yusef 
mailto:rifaat.s.i...@gmail.com>> wrote:
All,

This is a call for adoption for the following OAuth 2.1 document as a WG 
document:
https://www.ietf.org/id/draft-parecki-oauth-v2-1-03.html

Please, provide your feedback on the mailing list by July 29th.

Regards,
 Rifaat & Hannes

___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

Re: [OAUTH-WG] Call for adoption - OAuth 2.1 document

2020-07-15 Thread Torsten Lodderstedt 
+1

> On 15. Jul 2020, at 21:37, John Bradley  wrote:
> 
> I support addoption
> 
> On 7/15/2020 3:32 PM, Neil Madden wrote:
>> I support adoption. 
>> 
>>> On 15 Jul 2020, at 18:42, Rifaat Shekh-Yusef  
>>> wrote:
>>> 
>>> 
>>> All,
>>> 
>>> This is a call for adoption for the following OAuth 2.1 document as a WG 
>>> document:
>>> https://www.ietf.org/id/draft-parecki-oauth-v2-1-03.html
>>> 
>>> Please, provide your feedback on the mailing list by July 29th.
>>> 
>>> Regards,
>>>  Rifaat & Hannes
>>> 
>>> ___
>>> OAuth mailing list
>>> OAuth@ietf.org
>>> https://www.ietf.org/mailman/listinfo/oauth
>> 
>> 
>> ___
>> OAuth mailing list
>> 
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
> ___
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth



smime.p7s
Description: S/MIME cryptographic signature
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

Re: [OAUTH-WG] Call for adoption - OAuth 2.1 document

2020-07-15 Thread John Bradley 
I support addoption

On 7/15/2020 3:32 PM, Neil Madden wrote:
> I support adoption. 
>
>> On 15 Jul 2020, at 18:42, Rifaat Shekh-Yusef
>>  wrote:
>>
>> 
>> All,
>>
>> This is a *call for adoption* for the following *OAuth 2.1* document
>> as a WG document:
>> https://www.ietf.org/id/draft-parecki-oauth-v2-1-03.html
>>
>> Please, provide your feedback on the mailing list by *July 29th.*
>>
>> Regards,
>>  Rifaat & Hannes
>>
>> ___
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>
> ___
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

Re: [OAUTH-WG] Call for adoption - OAuth 2.1 document

2020-07-15 Thread Neil Madden 
I support adoption. 

> On 15 Jul 2020, at 18:42, Rifaat Shekh-Yusef  wrote:
> 
> 
> All,
> 
> This is a call for adoption for the following OAuth 2.1 document as a WG 
> document:
> https://www.ietf.org/id/draft-parecki-oauth-v2-1-03.html
> 
> Please, provide your feedback on the mailing list by July 29th.
> 
> Regards,
>  Rifaat & Hannes
> 
> ___
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

Re: [OAUTH-WG] Call for adoption - OAuth 2.1 document

2020-07-15 Thread Rifaat Shekh-Yusef 
Warren,

Please, start a separate thread for this issue.

Regards,
 Rifaat


On Wed, Jul 15, 2020 at 2:57 PM Warren Parad  wrote:

> I only recently joined this WG DL, so maybe this was already discussed by
> I have two things I'm confused/curious about:
>
> 1. Can we avoid using (1, 2, 3) on the left side of the diagram to
> describe, I'm not even sure what they are supposed to represent, not to
> mention the RO in the diagram doesn't really provide value (for me)
> relevant to the code grant flow. It's confusing to see these numerical
> identifiers twice in the same picture. But maybe there is something hidden
> in this that I'm missing, still 3a and 3b could be used to identify
> different legs of the same code path.
> [image: image.png]
>
> 2. It seems recently more and more common to pass the access_token to some
> RS via a cookie, yet 7.2.1 says it defines two methods. I think we need
> some RFC2119
>  keywords
> here, to suggest that either SHOULD use one of these two, or MUST. And then
> optionally state whether or not we recommend or reject the use of cookies
> as a place for access tokens. It's also possible that the language threw me
> off, because would an access token in a cookie be a bearer token, but no
> matter, if I'm having this thought, then surely others have it as well,
> right?
>
> [image: image.png]
>
>
> *Warren Parad*
> Secure your user data and complete your authorization architecture.
> Implement Authress .
> 
>
>
> On Wed, Jul 15, 2020 at 7:55 PM Dick Hardt  wrote:
>
>> +1
>>
>> On Wed, Jul 15, 2020 at 10:42 AM Rifaat Shekh-Yusef <
>> rifaat.s.i...@gmail.com> wrote:
>>
>>> All,
>>>
>>> This is a *call for adoption* for the following *OAuth 2.1* document as
>>> a WG document:
>>> https://www.ietf.org/id/draft-parecki-oauth-v2-1-03.html
>>>
>>> Please, provide your feedback on the mailing list by *July 29th.*
>>>
>>> Regards,
>>>  Rifaat & Hannes
>>>
>>> ___
>>> OAuth mailing list
>>> OAuth@ietf.org
>>> https://www.ietf.org/mailman/listinfo/oauth
>>>
>> ___
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>>
>
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

Re: [OAUTH-WG] Call for adoption - OAuth 2.1 document

2020-07-15 Thread Aaron Parecki 
Just to clarify, this thread is a call for adoption, not meant to discuss
the details of this particular draft.

Any issues with the draft can be raised as new threads. But right now, the
question posed to the list is whether the group thinks this document should
be adopted as a working group item.

Oh, and +1 from me :-)

Aaron Parecki
https://aaronparecki.com

On Wed, Jul 15, 2020 at 11:57 AM Warren Parad  wrote:

> I only recently joined this WG DL, so maybe this was already discussed by
> I have two things I'm confused/curious about:
>
> 1. Can we avoid using (1, 2, 3) on the left side of the diagram to
> describe, I'm not even sure what they are supposed to represent, not to
> mention the RO in the diagram doesn't really provide value (for me)
> relevant to the code grant flow. It's confusing to see these numerical
> identifiers twice in the same picture. But maybe there is something hidden
> in this that I'm missing, still 3a and 3b could be used to identify
> different legs of the same code path.
> [image: image.png]
>
> 2. It seems recently more and more common to pass the access_token to some
> RS via a cookie, yet 7.2.1 says it defines two methods. I think we need
> some RFC2119
>  keywords
> here, to suggest that either SHOULD use one of these two, or MUST. And then
> optionally state whether or not we recommend or reject the use of cookies
> as a place for access tokens. It's also possible that the language threw me
> off, because would an access token in a cookie be a bearer token, but no
> matter, if I'm having this thought, then surely others have it as well,
> right?
>
> [image: image.png]
>
>
> *Warren Parad*
> Secure your user data and complete your authorization architecture.
> Implement Authress .
> 
>
>
> On Wed, Jul 15, 2020 at 7:55 PM Dick Hardt  wrote:
>
>> +1
>>
>> On Wed, Jul 15, 2020 at 10:42 AM Rifaat Shekh-Yusef <
>> rifaat.s.i...@gmail.com> wrote:
>>
>>> All,
>>>
>>> This is a *call for adoption* for the following *OAuth 2.1* document as
>>> a WG document:
>>> https://www.ietf.org/id/draft-parecki-oauth-v2-1-03.html
>>>
>>> Please, provide your feedback on the mailing list by *July 29th.*
>>>
>>> Regards,
>>>  Rifaat & Hannes
>>>
>>> ___
>>> OAuth mailing list
>>> OAuth@ietf.org
>>> https://www.ietf.org/mailman/listinfo/oauth
>>>
>> ___
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>>
> ___
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

Re: [OAUTH-WG] Call for adoption - OAuth 2.1 document

2020-07-15 Thread Warren Parad 
I only recently joined this WG DL, so maybe this was already discussed by I
have two things I'm confused/curious about:

1. Can we avoid using (1, 2, 3) on the left side of the diagram to
describe, I'm not even sure what they are supposed to represent, not to
mention the RO in the diagram doesn't really provide value (for me)
relevant to the code grant flow. It's confusing to see these numerical
identifiers twice in the same picture. But maybe there is something hidden
in this that I'm missing, still 3a and 3b could be used to identify
different legs of the same code path.
[image: image.png]

2. It seems recently more and more common to pass the access_token to some
RS via a cookie, yet 7.2.1 says it defines two methods. I think we need
some RFC2119
 keywords
here, to suggest that either SHOULD use one of these two, or MUST. And then
optionally state whether or not we recommend or reject the use of cookies
as a place for access tokens. It's also possible that the language threw me
off, because would an access token in a cookie be a bearer token, but no
matter, if I'm having this thought, then surely others have it as well,
right?

[image: image.png]


*Warren Parad*
Secure your user data and complete your authorization architecture.
Implement Authress .



On Wed, Jul 15, 2020 at 7:55 PM Dick Hardt  wrote:

> +1
>
> On Wed, Jul 15, 2020 at 10:42 AM Rifaat Shekh-Yusef <
> rifaat.s.i...@gmail.com> wrote:
>
>> All,
>>
>> This is a *call for adoption* for the following *OAuth 2.1* document as
>> a WG document:
>> https://www.ietf.org/id/draft-parecki-oauth-v2-1-03.html
>>
>> Please, provide your feedback on the mailing list by *July 29th.*
>>
>> Regards,
>>  Rifaat & Hannes
>>
>> ___
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>>
> ___
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

Re: [OAUTH-WG] Call for adoption - OAuth 2.1 document

2020-07-15 Thread Dick Hardt 
+1

On Wed, Jul 15, 2020 at 10:42 AM Rifaat Shekh-Yusef 
wrote:

> All,
>
> This is a *call for adoption* for the following *OAuth 2.1* document as a
> WG document:
> https://www.ietf.org/id/draft-parecki-oauth-v2-1-03.html
>
> Please, provide your feedback on the mailing list by *July 29th.*
>
> Regards,
>  Rifaat & Hannes
>
> ___
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

[OAUTH-WG] Call for adoption - OAuth 2.1 document

2020-07-15 Thread Rifaat Shekh-Yusef 
All,

This is a *call for adoption* for the following *OAuth 2.1* document as a
WG document:
https://www.ietf.org/id/draft-parecki-oauth-v2-1-03.html

Please, provide your feedback on the mailing list by *July 29th.*

Regards,
 Rifaat & Hannes
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth