ne that the BCP would cover any issue
>> that arises not just mix-up
>>
>> -Original Message-
>> From: OAuth [mailto:oauth-boun...@ietf.org] On Behalf Of Hannes Tschofenig
>> Sent: Monday, July 25, 2016 3:59 AM
>> To: oauth@ietf.org
>> Subject: [OAUT
e
> that arises not just mix-up
>
> -Original Message-
> From: OAuth [mailto:oauth-boun...@ietf.org] On Behalf Of Hannes Tschofenig
> Sent: Monday, July 25, 2016 3:59 AM
> To: oauth@ietf.org
> Subject: [OAUTH-WG] OAuth Security -- Next Steps
>
> Hi all,
>
>
Sounds about right, but I would imagine that the BCP would cover any issue that
arises not just mix-up
-Original Message-
From: OAuth [mailto:oauth-boun...@ietf.org] On Behalf Of Hannes Tschofenig
Sent: Monday, July 25, 2016 3:59 AM
To: oauth@ietf.org
Subject: [OAUTH-WG] OAuth Security
Hi all,
We had two working group sessions at the Berlin IETF meeting and I am
happy about the progress on many of the subjects. We managed to progress
token exchange, native apps, AMR, and authorization server meta-data. We
also identified new use cases to explore with the device flow document.
W
