Hi Orie,
Thank you for the summary. Small corrections/clarifications below.
On 17/11/2023 18:03, Orie Steele wrote:
Alexey Melnikov and I had a chat about
https://datatracker.ietf.org/doc/draft-ietf-mediaman-suffixes
I am sharing a summary of our discussion for the benefit of the list
On Thu, Aug 29, 2019, at 1:52 PM, Torsten Lodderstedt wrote:
> Hi Alexey,
>
> > On 28. Aug 2019, at 13:21, Alexey Melnikov via Datatracker
> > wrote:
> >
> > Alexey Melnikov has entered the following ballot position for
> > draft-ietf-oauth-jwt-introspectio
Alexey Melnikov has entered the following ballot position for
draft-ietf-oauth-jwt-introspection-response-06: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however
Hi William,
On Thu, Aug 2, 2018, at 7:18 PM, William Denniss wrote:
> Alexey,
>
> Thank you for your feedback. Replies inline:
>
> On Sun, Jul 29, 2018 at 9:26 AM, Alexey Melnikov
> wrote:>>
>> ---
Alexey Melnikov has entered the following ballot position for
draft-ietf-oauth-device-flow-11: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please
Alexey Melnikov has entered the following ballot position for
draft-ietf-oauth-discovery-10: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer
f edits. (However, I'll wait for Adam to weigh in on his
> DISCUSS before republishing.)
>
> Let me know.
>
> Thanks again,
> -- Mike
>
> -Original Message-
> From: OAuth On Behalf Of Alexey Melnikov
> Sent: We
26, 2018 11:03 PM *To:*
> The IESG ; Alexey Melnikov
> *Cc:* draft-ietf-oauth-discov...@ietf.org; oauth-cha...@ietf.org;
> oauth@ietf.org *Subject:* RE: [OAUTH-WG] Alexey Melnikov's Discuss on
> draft-ietf-oauth-discovery-08: (with DISCUSS and COMMENT)>
> The attached draft
Alexey Melnikov has entered the following ballot position for
draft-ietf-oauth-discovery-09: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
https://tools.ietf.org/html/rfc7159#section-8.3.
My understanding is that RFC 7159 recommends case-sensitive comparison and that
is fine with me.
> Will that work for you, Alexey?
Best Regards,
Alexey
>
> Thanks,
> --
Alexey Melnikov has entered the following ballot position for
draft-ietf-oauth-discovery-08: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
Alexey Melnikov has entered the following ballot position for
draft-ietf-oauth-jwsreq-14: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
d also this errata notes that NOT RECOMMENDED should be in the first
> part of the abstract
> https://www.rfc-editor.org/errata_search.php?rfc=2119&eid=499
Never mind then!
>
> On Wed, May 24, 2017 at 9:27 AM, Alexey Melnikov
> wrote:>> Alexey Melnikov has entered
Alexey Melnikov has entered the following ballot position for
draft-ietf-oauth-native-apps-11: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please
On Tue, May 23, 2017, at 10:24 AM, Alexey Melnikov wrote:
> Hi William,
>
> On 22 May 2017, at 23:14, William Denniss wrote:>>>
> Section 8.1 makes the statement that "Loopback IP based redirect
>>> URIs may>>> be susceptible to intercept
Hi William,
On 22 May 2017, at 23:14, William Denniss wrote:
>> Section 8.1 makes the statement that "Loopback IP based redirect URIs may
>> be susceptible to interception by other apps listening on the same
>> loopback interface." That's not how TCP listener sockets work: for any
>> given IP ad
Alexey Melnikov has entered the following ballot position for
draft-ietf-oauth-jwsreq-13: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to https
Alexey Melnikov has entered the following ballot position for
draft-ietf-oauth-amr-values-06: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer
Alexey Melnikov has entered the following ballot position for
draft-ietf-oauth-jwsreq-12: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to https
Hi Mirja,
> On 16 Feb 2017, at 10:31, Mirja Kuehlewind wrote:
(Snip)
> - Should this be like this?
> OLD
> ""request" and "request_uri" parameters MUST NOT be included in Request
> Objects."
> NEW
> ""request" and "request_uri" parameters MUST NOT be both included in
> Request Objects."
You c
Alexey Melnikov has entered the following ballot position for
draft-ietf-oauth-jwsreq-12: No Record
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
the
text as specified is fine.
> -- Mike
>
> -Original Message-
> From: Alexey Melnikov [mailto:aamelni...@fastmail.fm]
> Sent: Thursday, February 2, 2017 7:07 AM
> To: Mike Jones ; The IESG
> Cc: draft-ietf-oauth-amr-val...@ietf.org; Hannes
n names. Can you
confirm?
>
> -Original Message-
> From: Alexey Melnikov [mailto:aamelni...@fastmail.fm]
> Sent: Thursday, February 2, 2017 12:06 AM
> To: The IESG
> Cc: draft-ietf-oauth-amr-val...@ietf.org; Hannes Tschofenig
> ; oauth-cha...@ietf.org;
> hannes.tsch
Alexey Melnikov has entered the following ballot position for
draft-ietf-oauth-amr-values-05: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
changing this in HTTPBIS is in progress
now.
-- Mike
-Original Message-
From: Alexey Melnikov [mailto:alexey.melni...@isode.com]
Sent: Tuesday, July 17, 2012 10:58 AM
To: Mike Jones
Cc: Julian Reschke; The IESG; General Area Review Team; oauth@ietf.org
okens, for instance, which is something we
*definitely* want to allow.
As a result, I don't think adding a reference to RFC 4648 is either necessary
or appropriate.
In this case, can you please rename the production to something which is
clearly not a base64 string.
Julian may be able
On 17/07/2012 17:40, Julian Reschke wrote:
On 2012-07-17 18:10, Mike Jones wrote:
FYI, the b64 token definition is identical to the one in
draft-ietf-httpbis-p7-auth-20. If it works there, it should work for
OAuth Bearer.
...
+1; not every constraint needs to be expressed in the ABNF. "b64tok
I am still Ok with -22, but I have 1 new comment raised by introduction
of the base64 ABNF non terminal:
I think it would be worth adding a comment for b64token that points to
the base64 RFC. The current ABNF is too permissive (arbitrary number of
"=" allowed at the end) and there are enough b
On 11/04/2012 01:25, Mike Jones wrote:
Hi Alexey,
Hi Mike,
I've dropped issue 2, Sean took charge of discussing it with IESG.
About your issue 1: The OAuth Core spec, where "scope" is primarily defined, includes
the sentence "The [scope] strings are defined by the authorization server" (see
18.txt
Reviewer: Alexey Melnikov
Review Date: 10 April 2012
IETF LC End Date: 7 Feb 2012
IESG Telechat date: 12 April 2012
Summary: Nearly ready to be published as Proposed Standard, with a
couple of things that should be addressed or at least discussed.
Thank you for addressing most of my other
Hi Mike,
On 31/01/2012 10:33, Alexey Melnikov wrote:
On 30/01/2012 05:20, Mike Jones wrote:
Thanks for your useful feedback, Alexey.
Hi Mike,
Below, I'll respond to each of your comments. I've also added the
OAuth working group to the thread, so they are aware of them as wel
On 31/01/2012 10:33, Alexey Melnikov wrote:
On 30/01/2012 05:20, Mike Jones wrote:
[...]
About your third minor issue on RFC 6125 versus RFC 2818, you'll find
that, per the history entries, a previous reference to RFC 2818 was
changed to RFC 6125 in draft 14 at the request of Security
se are fixed in -16, thanks.
Thanks again,
-- Mike
-Original Message-----
From:ietf-boun...@ietf.org [mailto:ietf-boun...@ietf.org] On Behalf Of Alexey
Melnikov
Sent: Sunday, January 29, 2012 8:38 AM
To: General Area Review Team
On 08/12/2011 14:18, Hannes Tschofenig wrote:
Hi all,
Hi Hannes,
Some random thoughts about your message below:
I read through this rather long mail thread again and see whether we are
reaching any conclusion on this discussion.
In turns out that there are actually two types of discussions tha
Eran Hammer-Lahav wrote:
Hi Alexey,
-Original Message-
From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf
Of Alexey Melnikov
Sent: Tuesday, May 03, 2011 4:17 AM
#10 8.4. Defining Additional Error Codes
http://trac.tools.ietf.org/wg/oauth/trac/ticket/10
Hi Barry,
Barry Leiba wrote:
There are three issues in the tracker that are just looking for
consensus on text that's in the document -- Eran had flagged them as
"pending consensus" in the -15 version. Let's look at closing those
issues now. The issues are
#8 4.1.2.1 and 4.2.2.1, text f
Hannes Tschofenig wrote:
Hi all,
Based on the positive response at the last IETF meeting we decided to hold
another Oauth tutorial, namely on Monday, November 8,0900-1130
I am sorry Hannes, but having this tutorial during the Apps Area open
meeting is not cool.
So "-1" from one of your Ap
Eran Hammer-Lahav wrote:
Any comments? Suggestions?
Hi Eran,
Speaking as an individual contributor:
EHL
On 12/4/09 9:19 AM, "Eran Hammer-Lahav" wrote:
The Authentication-Info header should be added to
draft-ietf-httpbis-p7-auth to provide a complete list of all the
defined aut
38 matches
Mail list logo
