IETF Logo Mail Archive

Re: [GNAP] Some remaining issues about the core-protocol

Aaron Parecki <aaron@parecki.com> Thu, 06 May 2021 14:48 UTC

Return-Path: <aaron@parecki.com>
X-Original-To: txauth@ietfa.amsl.com
Delivered-To: txauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EBFB3A24CE for <txauth@ietfa.amsl.com>; Thu, 6 May 2021 07:48:49 -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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=parecki.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 T9sYHoZwKgwo for <txauth@ietfa.amsl.com>; Thu, 6 May 2021 07:48:44 -0700 (PDT)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 95E1F3A24E2 for <txauth@ietf.org>; Thu, 6 May 2021 07:48:44 -0700 (PDT)
Received: by mail-io1-xd2b.google.com with SMTP id f6so5055645iow.2 for <txauth@ietf.org>; Thu, 06 May 2021 07:48:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parecki.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=opW+76T7Kq6oBYAqtZZZJE/xy6dw1hj8Iefew5Ju3ZQ=; b=Vrpgda6jzBMlm4To5TFCGMK3pKxf/e9gkxvkZWncGCSBgK1JMSIlDSHEMhGSu8TBh3 attXGvarADwb/EAA5IBSyKhK6/1Fh+ixum1m1GH8F5P0NkFrtIKQAdIuoDeZtJQ/ufSE QFsb6lIohuYrz0ckqua/wbGyIfsOBurakvchXdy4EmfDR5kMRl/jQvYSBmW//T8onhDz 8G5TBgkTSnxVCHFO04wpnMWGsc6J3VP1xRrovnBNvhhnRgRzNj6/uQOqEzWI7DzcDp4p qXUmt9Kmp87rd3pC0tpX+TBAgg6CQtbDX+CHSWR+VevO6pWjaQWehEvh/iWywAUeD8VH 7CHg==
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=opW+76T7Kq6oBYAqtZZZJE/xy6dw1hj8Iefew5Ju3ZQ=; b=px4E1r7LCYIjqJFKXfzatNeRflyVUj+gGWbjXQMf4dJClkdM8QtyV6kNLNvnT+tiYP buCqj+6VMMCc/GyOFC16KO6IXBMiqZjwDBsSnRM6AaR2jQn3QTOwbfNu2xSuAWNL/QWQ d1U/FFXG5FQTK6M2VN3WDBH6dQAVoxfJpNFgaG4vqfcoBYIkAajzkkr9mt36/uRwWhsU uJP225KqxDOBB99InlCQgB5WHujxTWQgSVkwb4RIJoJHKNnZLt7Z4yfFLycRx9GlsmmK 1e8ECU0ba3r0l/TMeA6CUyI8JuoJjn3Zi9FoAdE7JYrG4k7oAUDx5QRAgUpFgMlVahLT mpXw==
X-Gm-Message-State: AOAM530Til6uog7PEuiajTqU5amgekAlNyRtovL3zFtirOu+JBAA155I YcGnzq3cLncvD4U8cFTrQywZ88VaxPeFVQ==
X-Google-Smtp-Source: ABdhPJxOgumNASlMQEnNLTImnMXWbYuQ0KNbV+h3OUTvF8DEwz1vTM1uqlGwao+UDz8nYkUK+mFHdg==
X-Received: by 2002:a05:6602:718:: with SMTP id f24mr3489850iox.59.1620312522126; Thu, 06 May 2021 07:48:42 -0700 (PDT)
Received: from mail-io1-f45.google.com (mail-io1-f45.google.com. [209.85.166.45]) by smtp.gmail.com with ESMTPSA id k17sm1047166ioa.44.2021.05.06.07.48.41 for <txauth@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 06 May 2021 07:48:41 -0700 (PDT)
Received: by mail-io1-f45.google.com with SMTP id l21so5050544iob.1 for <txauth@ietf.org>; Thu, 06 May 2021 07:48:41 -0700 (PDT)
X-Received: by 2002:a6b:6013:: with SMTP id r19mr3619756iog.208.1620312521262; Thu, 06 May 2021 07:48:41 -0700 (PDT)
MIME-Version: 1.0
References: <0536f389-ea4f-358c-7142-91d41fe8924a@free.fr> <fab7789d-2f86-4d2a-c5f4-93e0107c4ba2@free.fr>
In-Reply-To: <fab7789d-2f86-4d2a-c5f4-93e0107c4ba2@free.fr>
From: Aaron Parecki <aaron@parecki.com>
Date: Thu, 06 May 2021 07:48:30 -0700
X-Gmail-Original-Message-ID: <CAGBSGjrxRij15+9pGjG-aoZoeL+-=--dsJMmGiXPye6T9eL9rw@mail.gmail.com>
Message-ID: <CAGBSGjrxRij15+9pGjG-aoZoeL+-=--dsJMmGiXPye6T9eL9rw@mail.gmail.com>
To: Denis <denis.ietf@free.fr>
Cc: GNAP Mailing List <txauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000414efa05c1aa6877"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/uZQN7sqGBS33GuLvwDFhkpJxAVw>
Subject: Re: [GNAP] Some remaining issues about the core-protocol
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: GNAP <txauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/txauth>, <mailto:txauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/txauth/>
List-Post: <mailto:txauth@ietf.org>
List-Help: <mailto:txauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/txauth>, <mailto:txauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2021 14:48:49 -0000

This issue?

https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/241


On Thu, May 6, 2021 at 7:43 AM Denis <denis.ietf@free.fr> wrote:

> Quite strange, between the time I prepared my message and now, the
> following issue has disappeared:
> 5. Unlinkability #241
>
> Is there a way to have a look at missing or closed issues ?
>
> Denis
>
> Hello,
>
> The mailing list has been pretty silent these last days.
>
> Hereafter is a quick overview about some of the remaining issues
> classified by order of  importance (from my point of view).
>
> 1. User choice and consent, and user notice #215
>
> smartopain wote:
>
> To draw a parallel: Since the publication of the EU GDPR (General Data
> Protection Regulation) the use of the cookies has changed.
> An end-user is allowed to accept them all, to deny them all (except
> functional cookies) and even to make some choices.
> The end-users can know which legal entity will collect the cookies and
> what for.
>
> The same kind of screens should be proposed to the end-user.
> *From a technical perspective, specific end-points should be defined and
> used, since this kind of dialog is done using APIs.*
>
>  I agree with smartopain.
>
> *2. Trust relationships **#214*
>
> There are still left undefined. AS-RS trust relationships are important.
> RO relationships with both ASs and RSs are very important
> but unfortunately are discussed nowhere in the current draft (except in
> text proposals about this issue)
>
> *3. **Interaction (1) between the Client Instance and the RS as described
> in the first figure **#252*
>
> Still on the table but not progressing.
> 4. The first figure in section 1.4 should be split and revisited #192
>
> This is still not done.
> 5. Unlinkability #241
>
> Still on the table but not progressing.
> 6. Requesting User Information #197
>
> This is still a hazy topic.
>
>
>  Denis
>
>
>
> --
> TXAuth mailing list
> TXAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/txauth
>

v2.23.0 | Report a Bug | By Email