IETF Logo Mail Archive

Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-18.txt

Pawel Kowalik <kowalik@denic.de> Mon, 24 October 2022 14:58 UTC

Return-Path: <kowalik@denic.de>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23BB0C14CE2B for <regext@ietfa.amsl.com>; Mon, 24 Oct 2022 07:58:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=denic.de
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cymByZc_RWwf for <regext@ietfa.amsl.com>; Mon, 24 Oct 2022 07:58:04 -0700 (PDT)
Received: from mout-b-206.mailbox.org (mout-b-206.mailbox.org [IPv6:2001:67c:2050:102:465::206]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE392C14CE3C for <regext@ietf.org>; Mon, 24 Oct 2022 07:57:49 -0700 (PDT)
Received: from smtp202.mailbox.org (smtp202.mailbox.org [10.196.197.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-b-206.mailbox.org (Postfix) with ESMTPS id 4MwyqC2zKBz9sm2; Mon, 24 Oct 2022 16:57:43 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=denic.de; s=MBO0001; t=1666623463; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=oA7L/H7+te7SbzpcE3bsmv4ez4xK7arGj1sbHp4iF48=; b=Gu6HB60iSBkZKDtVLO8vLJOTzavjNQFS3Gq8ckNC8na2gAq9m2zGeQnrWd8Fo0gMo9zmhJ +xCFZMNyL8Zth6Z7To+daLg1BHXFl+Ac/v3BgRSeyIF7oMMrzH3GyP4bQHmcKRfUYIW/Qv V3iTdRiwNDIYu3uq8TLYmKDD6HYKiVlqciSDM+cdCoy0juyvlpX/6ohbmKC/GZ6M3VNHNN cWIV2NHGdBjkYZ7pq2VEKF++neyoowRhvwGMyvC37nsxTp/FjJ2s4dgwHTDsTC3ZZF/8Aa 5iMOW8r031uqtgVb7u3f6ZbpS+DjrTcvNNGXFBKXYV3/M1T1o+humEtmu5Pt6Q==
Content-Type: multipart/mixed; boundary="------------8kb4G2aoOiKkwUSFROeFM7Mj"
Message-ID: <05ed620b-7ecf-bfae-1af4-0847850fc8f2@denic.de>
Date: Mon, 24 Oct 2022 16:57:41 +0200
MIME-Version: 1.0
From: Pawel Kowalik <kowalik@denic.de>
References: <c6967e00-d860-a1f4-cd70-ed26bae4f305@denic.de>
Content-Language: en-GB
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, "regext@ietf.org" <regext@ietf.org>
In-Reply-To: <c6967e00-d860-a1f4-cd70-ed26bae4f305@denic.de>
X-MBO-RS-ID: fa384713b50828c91e3
X-MBO-RS-META: j4gdbmsyy4bnxsynp49g65o7hox63o1g
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/Wj1bkoYmshTMbM1zC24qzN2uJT0>
Subject: Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-18.txt
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Oct 2022 14:58:09 -0000

Hi Scott,

Am 19.10.22 um 14:13 schrieb Hollenbeck, Scott:
>>
>>>> 1. How do we address web service clients?
>> [PK] I think the elements we need for web service clients were already
>> elaborated in the discussion over the version 17.
>> I'm happy to support with text proposal if needed.
> [SAH] Text would be appreciated. Something like this perhaps?
>
> 4.2.5 Web Service Clients
>
> <Paragraph that describes what a web service client is>
>
> 4.2.5.1 Web Service Client Login
>
> <Query parameters and/or path segment descriptions>
>
> 4.2.5.2 Web Service Client Session Management
>
> <Query parameters and/or path segment descriptions>
>
[PK] Please find attached my draft on Web Service Clients. Most of it is 
based on the concepts of the version 9. Scope "feature" is also included 
in the proposal.

Open point would be to add an optional possibility for 
confidential/registered clients and some security considerations.

Kind Regards,

Pawel

v2.23.0 | Report a Bug | By Email