[GNAP] Technical considerations around forced association in GNAP

Adrian Gropper <agropper@healthurl.com> Fri, 02 December 2022 18:49 UTC

Return-Path: <agropper@gmail.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 2A418C14CF02 for <txauth@ietfa.amsl.com>; Fri, 2 Dec 2022 10:49:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.396
X-Spam-Level:
X-Spam-Status: No, score=-1.396 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
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 JAmU9fq3qY6H for <txauth@ietfa.amsl.com>; Fri, 2 Dec 2022 10:49:35 -0800 (PST)
Received: from mail-yb1-f169.google.com (mail-yb1-f169.google.com [209.85.219.169]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 61F6FC14F692 for <txauth@ietf.org>; Fri, 2 Dec 2022 10:49:35 -0800 (PST)
Received: by mail-yb1-f169.google.com with SMTP id y135so2523905yby.12 for <txauth@ietf.org>; Fri, 02 Dec 2022 10:49:35 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=6x+w/soOJKuI4dOXbMrUiSILGDhPCg2DuMXGoVHBmag=; b=BfUjFUEd2pHUGPLeaGKbkFXmwSEuHD3BqIUWb5VCaeySg+TP7BA4vajgW6/xYUGZ95 L6uxn8sPXN7B13Qho72UboDgOon1QpbZty8aJRqypP74Qhq9g+jJTg1IVAKDdjoKB2C4 HZNKD60BP7xOO0/Lbcek17+V5vTQUeQFUEGNscu73qQiJYlvE5HhfR+AH46+5XiSR9lQ 3yU+zjvQN+uyk/HEJAWdWVlFr4Fjh6qaliS/eweQetTkXbO0rH3R5HvME39yrzSRBXXj mDjq0gwSWtAI9n6Qu7JM84A8EgqyIHPATSxbzkZwGbURJvR1qhJF+xbHl8Nzyyx9FOwm 4frA==
X-Gm-Message-State: ANoB5pm1J3NC5TiDk4fO+bbQBkGJL76h5MdBdcDsQVSR2KHqZIxsUstR 5RY7m4FnuFY3SejhYzL2vDvPX+g1hpw/eH+fB3qlCpkTGmM=
X-Google-Smtp-Source: AA0mqf6TrE4CZZpmqkEK1quW01Bs+f+wMkf/iTN0OaQ7ewmXUNxiANEJl+ezWu/xJXv/bpgRW2i6BjfZykbLt9fLMq0=
X-Received: by 2002:a25:4144:0:b0:6fc:aa95:9637 with SMTP id o65-20020a254144000000b006fcaa959637mr6359632yba.327.1670006974130; Fri, 02 Dec 2022 10:49:34 -0800 (PST)
MIME-Version: 1.0
From: Adrian Gropper <agropper@healthurl.com>
Date: Fri, 02 Dec 2022 13:49:22 -0500
Message-ID: <CANYRo8g7H4znjcFE49Ak13j=NFFASLAG+QSVBngncihpu5UuDA@mail.gmail.com>
To: GNAP Mailing List <txauth@ietf.org>
Cc: Alan Karp <alanhkarp@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000007736bd05eedcccfd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/c0TrVPMlW9pFlBrG3nB3wMgTy5A>
Subject: [GNAP] Technical considerations around forced association in GNAP
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 02 Dec 2022 18:49:36 -0000

Over the past weeks, a discussion of human rights considerations in GNAP on
the HRPC list has turned technical and paused as GNAP considers the
protocol implications of avoiding forced association. Here's the most
recent posts:

https://mailarchive.ietf.org/arch/msg/hrpc/VhroNqqmg9SuqXlsOWieijuobCI/

I'm hoping to continue the discussion here at least to determine how to
phrase the issue.

Thank you,
Adrian