Re: [OAUTH-WG] PAR - Guidance on the request URI structure needed?
Sascha Preibisch <saschapreibisch@gmail.com> Mon, 27 April 2020 14:57 UTC
Return-Path: <saschapreibisch@gmail.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 F28BF3A0C01 for <oauth@ietfa.amsl.com>; Mon, 27 Apr 2020 07:57:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Yk_RDtS06r7t for <oauth@ietfa.amsl.com>; Mon, 27 Apr 2020 07:57:48 -0700 (PDT)
Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (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 2C4C73A0C2B for <oauth@ietf.org>; Mon, 27 Apr 2020 07:57:47 -0700 (PDT)
Received: by mail-wm1-x32e.google.com with SMTP id 188so4952wmc.2 for <oauth@ietf.org>; Mon, 27 Apr 2020 07:57:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=dYpxWwYs77L/wrRyDY6NkKLG3sfvC+ne1X8PwWUzbR0=; b=Rj+d4uIOAxwuWl/zqFQ5PbiPt33doqr/O9jlc0AkeLL4tScAHndarZecvxZPAsqxF2 gaBuuoMwr7T0ek+4Fqk6RmghtHU3oytnanBYRrHJeYkRjy7HG6LUOwtQ2H440ioGopjS ws0+TIp1bWvFX8qHSGtcxJmzsbN3R4VROcm3+crz/zGhe7sArshbJDMZKwSoM5FfE8IH aEVs5pT4E5NktJPDpMRbTmBsa0HiF04mFMewKDJJ63Fn+4NzyRa0Rp0XwE4y+hH1EQAI oBVXINqLBgESA6ILljx/DtAf7zv4fqEDGfsrsGxCLPl+Piqb3jcaNDm4LJYUkLhn7jrp 63FA==
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:content-transfer-encoding; bh=dYpxWwYs77L/wrRyDY6NkKLG3sfvC+ne1X8PwWUzbR0=; b=WXk7V53w+PEKmL4isNjknUGLZlzMZUry8PlQqEQmNT2NjmQ0ZxNykPlAkK9O8yPwil Pc4XCAhfZHVu+EHGyAsKkN//270d4pRZKWi0fme/+y6UQ0s01gM4Rh3oHt22lRS772qi q9fwTw/s3A9SS2FLMMBcn021Fc9UPRDbHoc0rkKIOiJt5WzQba5NxNbL+Lqhl9W6Rfdq TQZ3EVKc6U1bcl+RydayaB/Sh/H/smwOkAU3K1O8rauoDfohfJ7+AeeGQQBCtdhBfw2q 5T7FLPGG1zj1R/ZiXxqBqYxFXQTwMnecOCpsL4u/wA6ZxgOE/Sz2QIXowkF3dcqHEOEf kqMA==
X-Gm-Message-State: AGi0PuYuXl9oawEhek78YM1IPfzrzH+3Gw+p3PINH7rFhIJBV7ve3DrB 2WL7fwhZnISG6DPp1Ys+1Jv15yLw8p6QrgbjHZ4=
X-Google-Smtp-Source: APiQypJVyxsaYZu+VKrCh0LHxxO2P1jNfiCJAN8kjSHhaJfPb2HiBE/j5aCxzTm/fF9npL+1lB61/ry2NCFf0fpvOjM=
X-Received: by 2002:a1c:4d17:: with SMTP id o23mr26170060wmh.120.1587999466430; Mon, 27 Apr 2020 07:57:46 -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: Sascha Preibisch <saschapreibisch@gmail.com>
Date: Mon, 27 Apr 2020 07:57:10 -0700
Message-ID: <CAP=vD9uXNpH=iD_CpGVyiYkGuuZsRmmCMtDPjJyQYo54EV03Gg@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: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/yH-VJO3FnEsroVM1qDnBmpaijAc>
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: Mon, 27 Apr 2020 14:57:51 -0000
+1 On Mon, 27 Apr 2020 at 01: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
- [OAUTH-WG] PAR - Guidance on the request URI stru… Torsten Lodderstedt
- Re: [OAUTH-WG] PAR - Guidance on the request URI … Filip Skokan
- Re: [OAUTH-WG] PAR - Guidance on the request URI … Sascha Preibisch
- Re: [OAUTH-WG] PAR - Guidance on the request URI … Justin Richer
- Re: [OAUTH-WG] PAR - Guidance on the request URI … Brian Campbell
- Re: [OAUTH-WG] PAR - Guidance on the request URI … Benjamin Kaduk
- Re: [OAUTH-WG] PAR - Guidance on the request URI … Dave Tonge