Re: [OAUTH-WG] PAR - Guidance on the request URI structure needed?

Dave Tonge <dave.tonge@momentumft.co.uk> Tue, 28 April 2020 06:02 UTC

Return-Path: <dave.tonge@moneyhub.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 8DD353A0B59 for <oauth@ietfa.amsl.com>; Mon, 27 Apr 2020 23:02:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.738
X-Spam-Level:
X-Spam-Status: No, score=-1.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=momentumft.co.uk
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 Aj0-8uQCXpTw for <oauth@ietfa.amsl.com>; Mon, 27 Apr 2020 23:02:55 -0700 (PDT)
Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B1243A0B37 for <oauth@ietf.org>; Mon, 27 Apr 2020 23:02:54 -0700 (PDT)
Received: by mail-ot1-x32c.google.com with SMTP id e26so30749366otr.2 for <oauth@ietf.org>; Mon, 27 Apr 2020 23:02:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=momentumft.co.uk; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0HURr68Hgx7wBPF0K7c+xXX5qtiVzqv0maziP/prEu4=; b=I1R3qJf03XEFTm2KnCGdN322aXfVeT1c+MqyCmTGGkNYq+GrAbKQxJ5RpnsyeT5Qf6 UgJ5WUZcQYuku6rTIziDJec9m1fkf+WydC+cdI9od4dBJ6f/WmPuuL0FRJH3nCe8Zcfy bizGYfWLrY8kva9s61EE83kp3lTakEYNtZ+y8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0HURr68Hgx7wBPF0K7c+xXX5qtiVzqv0maziP/prEu4=; b=jedMqWUDHn9pYG8O5HIn2u1iIAuD3P7aqpflU5yngh1BpuP6ik0XS9GgU07A2SbVES E10hJGR0/X+yAn02Aw9nBmlAiwPMsfow1+amJ4fMCNCVC/1KOyKMqLtMNvzdLyQ0a7nl gKILRqVieFpfn+Rt7RU7eLXnc6upNVGUwc5yzjW6JLJcd8rxj8MgvnpoxV85aBf0iigw tUa9hjQNsZQJOtMzTAFmFs4UZbVNrTn0q8b8dkurmEd2yqTPOhi7L2KSo6Tcxzc0E4e4 YNKnpG61nWB+8TK7LFNGhfxwkYEZ9IHB2noNwbxbuCeTzoOewQjIrEqNl05I/xNn5pvM JbYw==
X-Gm-Message-State: AGi0PuYa84IefhcFiaT3zgc1yBJ65b+GwjZVNnMkgKgCQ8nmvkPq4egw 2qJAup21+SiZHT8a5v8x65vdpPnzx5HiyJPuJhq7l3hudMyOqA==
X-Google-Smtp-Source: APiQypKymEa5m8yIIgyQGOstTKIRgouS1mbopOhy4tgEKds4WmTexN/n7SAwLlkLcIX/AtZ1/ww21zmIZTepi7eorr4=
X-Received: by 2002:aca:5014:: with SMTP id e20mr1904378oib.34.1588053774075; Mon, 27 Apr 2020 23:02:54 -0700 (PDT)
MIME-Version: 1.0
References: <A680BD1A-1E79-40C0-B325-91EEEFD7BDA5@lodderstedt.net> <CALAqi_-xtfcrWg0bvMTae9GkbOzCorNENpPiwt0kjzw5sgn_Mg@mail.gmail.com>
In-Reply-To: <CALAqi_-xtfcrWg0bvMTae9GkbOzCorNENpPiwt0kjzw5sgn_Mg@mail.gmail.com>
From: Dave Tonge <dave.tonge@momentumft.co.uk>
Date: Tue, 28 Apr 2020 08:02:42 +0200
Message-ID: <CAP-T6TT+jTYyF2mNpFkvbo0uNV763RBUbM3-bPUkgdnC7XabxA@mail.gmail.com>
To: Filip Skokan <panva.ip@gmail.com>
Cc: Torsten Lodderstedt <torsten=40lodderstedt.net@dmarc.ietf.org>, oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000016a2ba05a453951a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/f1jnRYAmgLfMX0HhMXAgxVSF1p4>
Subject: Re: [OAUTH-WG] PAR - Guidance on the request URI structure needed?
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 28 Apr 2020 06:02:58 -0000

+1 to Filip's suggestion

On Mon, 27 Apr 2020 at 10:42, Filip Skokan <panva.ip@gmail.com> wrote:

> I believe implementers should be free to devise their own URIs and not be
> locked down to one by the spec, at the same time,
> and RFC6755 subnamespace would be good for guidance.
>
> So, I would suggest it be RECOMMENDED to use e.g.
> `urn:ietf:params:oauth:request_uri:<random>` (Brian's proposal) but also
> that any URN or URL will do if the circumstances call for it.
>
> Best,
> *Filip*
>
>
> On Sun, 26 Apr 2020 at 17:20, Torsten Lodderstedt <torsten=
> 40lodderstedt.net@dmarc.ietf.org> wrote:
>
>> Hi all,
>>
>> another topic from last week’s virtual meeting.
>>
>> Shall there be guidance on the request URI structure?
>>
>> Please state your opinion.
>>
>> thanks in advance,
>> Torsten.
>> _______________________________________________
>> 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
>


-- 
Dave Tonge
CTO
[image: Moneyhub Enterprise]
<http://www.google.com/url?q=http%3A%2F%2Fmoneyhubenterprise.com%2F&sa=D&sntz=1&usg=AFQjCNGUnR5opJv5S1uZOVg8aISwPKAv3A>
Moneyhub Financial Technology, 5th Floor, 10 Temple Back, Bristol, BS1 6FL
t: +44 (0)117 280 5120

Moneyhub Enterprise is a trading style of Moneyhub Financial Technology
Limited which is authorised and regulated by the Financial Conduct
Authority ("FCA"). Moneyhub Financial Technology is entered on the
Financial Services Register (FRN 809360) at fca.org.uk/register.
Moneyhub Financial
Technology is registered in England & Wales, company registration number
06909772 .
Moneyhub Financial Technology Limited 2018 ©

DISCLAIMER: This email (including any attachments) is subject to copyright,
and the information in it is confidential. Use of this email or of any
information in it other than by the addressee is unauthorised and unlawful.
Whilst reasonable efforts are made to ensure that any attachments are
virus-free, it is the recipient's sole responsibility to scan all
attachments for viruses. All calls and emails to and from this company may
be monitored and recorded for legitimate purposes relating to this
company's business. Any opinions expressed in this email (or in any
attachments) are those of the author and do not necessarily represent the
opinions of Moneyhub Financial Technology Limited or of any other group
company.