[Secdispatch] ALFA 2.0 WG for IETF 121
David Brossard <david.brossard@gmail.com> Fri, 04 October 2024 10:14 UTC
Return-Path: <david.brossard@gmail.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D7C1C1519B0 for <secdispatch@ietfa.amsl.com>; Fri, 4 Oct 2024 03:14:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.844
X-Spam-Level:
X-Spam-Status: No, score=-1.844 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, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=gmail.com
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 QHTEbLpOzdf6 for <secdispatch@ietfa.amsl.com>; Fri, 4 Oct 2024 03:14:07 -0700 (PDT)
Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43889C1840D0 for <secdispatch@ietf.org>; Fri, 4 Oct 2024 03:14:07 -0700 (PDT)
Received: by mail-wr1-x42a.google.com with SMTP id ffacd0b85a97d-37cfff59d04so1761690f8f.1 for <secdispatch@ietf.org>; Fri, 04 Oct 2024 03:14:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728036846; x=1728641646; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=bOlJmyFRDzl3O1Rzpx6ZqjQvkY3zOTmhNgvy0zV2swk=; b=UcBp1DQWa4F65yL06J2NT9Qnu7feJN1n/fAfz3JDL72DyAXzHr6U6OYl4y8qJ+7xJS rcJ8DUEjRAzFl+R23J461cq8JlruTr1bhMy0udy2cf621t8F0HolwKCZsIM5R4lMVi76 lXQE2aobQPFJ/zkEtGYU2N2LKynGXAWbt6BcVT1BBlJpdCQ6arM9hv/hKEfoj8O9NSFJ 5bhKbtSPqq/+VokNNdGqCqJlSSyjT7cfKtAAZ5PFVGmJz+GHC495LpbPRZCHdZQa7t5w zU0MHI9voN5taZ7+1NxsL9fPbEVkEqYXRnaFr245NOYeFmSXXrahs4+NJTGKZeAQ4KYR dgEA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728036846; x=1728641646; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=bOlJmyFRDzl3O1Rzpx6ZqjQvkY3zOTmhNgvy0zV2swk=; b=R1t9/AzeQSnnFUq7hCDA8xCNgAZPmch04vWd1IKN7L6+9t9+TEJ7qSEZaQb3V91GqZ kky+X7xXaBVKVHs9wBZvNC5+gikZShEdPXS4U6MFZN0TmfoxsWGA+ncDsrhFS+P1zku6 h1MbLnbcr1Pu3GeNxsNdOx5EeU6yXuPysCfoVx3iVpUjxTfydCyX5u5ws1ZSfEtae+ah 1UEC0NUM4074XpxlirgPdJ3LYEpWLw3561jnYVKOozhYe8JgPge120eJDz2YdMonASui Y7YwsDPvd0FZG09BjKMIJVWSuOvmvQcmXvOEve8RzUR0iWpbIKT+OPSszNLwtHwIL6Da voPg==
X-Forwarded-Encrypted: i=1; AJvYcCWPD6MJZFqTAXyzeeqgWtzAmttexNS8pNR6iUGps9D3wc3dWHkbr5FTAn4tNFTtgCgei4VrpI0kjWIVCw==@ietf.org
X-Gm-Message-State: AOJu0YwkEbOL8BJrpxzwOUSCCIJDV0zc3+HKZ7a4YzmKOKLLLqAZtg5D UPuIRSauuOoZaU5SdXWwErYs5k366UFnesintP101IOMmNhyylomqqy9uRFwWZRT3b23NLuqBla VLH3WEUQW9g6PRCKIIntPeJrNuxM=
X-Google-Smtp-Source: AGHT+IGrz5d99YtZ2/C1TGCY3wBFchB6+5zmhfqh1R3iUeZn5sOyN5XqZg8fko7sv6bA8iR5kKP4ekzEEtb5Qi/HvmY=
X-Received: by 2002:a05:6000:d91:b0:374:badf:3017 with SMTP id ffacd0b85a97d-37d0f720689mr1092110f8f.33.1728036845305; Fri, 04 Oct 2024 03:14:05 -0700 (PDT)
MIME-Version: 1.0
From: David Brossard <david.brossard@gmail.com>
Date: Fri, 04 Oct 2024 12:13:53 +0200
Message-ID: <CAJO7GQ-V4hS887s4d9rhgMG12WAAybCuJ=7Rf+oAFBvpDUCAHA@mail.gmail.com>
To: Andrew Clymer <andy@rocksolidknowledge.com>, Theo Dimitrakos <theo.dimitrakos@ifiptm.org>, theo.dimitrakos@huawei.com, secdispatch@ietf.org, Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com>, paul.wouters@aiven.io, Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Content-Type: multipart/alternative; boundary="00000000000052c7880623a3eef0"
Message-ID-Hash: WFF66PYAET3H6XBO2Z5KROUXB5Q5MENO
X-Message-ID-Hash: WFF66PYAET3H6XBO2Z5KROUXB5Q5MENO
X-MailFrom: david.brossard@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-secdispatch.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc5
Precedence: list
Subject: [Secdispatch] ALFA 2.0 WG for IETF 121
List-Id: Security Dispatch <secdispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/sbVQahW1JSMOawKpLqfokHKPuvI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Owner: <mailto:secdispatch-owner@ietf.org>
List-Post: <mailto:secdispatch@ietf.org>
List-Subscribe: <mailto:secdispatch-join@ietf.org>
List-Unsubscribe: <mailto:secdispatch-leave@ietf.org>
Hi Daniel, Rifaat, and Paul, With IETF 120 in the back, I wanted to circle back and talk about next steps. After the lightning talk, a few folks came up to me to talk about their needs for an authorization policy language. In OAuth, there is also a need but the consensus was that the language should live outside OAuth and OAuth would just be a consumer of it. Other WGs e.g. WIMSE, SCIM, ACE of course, and perhaps SPICE. I am thinking therefore that ALFA 2.0 would belong to the Security Area (SEC) which is why I am reaching out. @Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com>, given you were in the OAuth sessions, what do you think? What are the next steps to create a WG? Does it make sense to attend IETF 121 and if so what would the expectations be? The current stub of a draft is here: https://datatracker.ietf .org/doc/draft-brossard-alfa-authz/ . I have also CCed my two co-authors, Andy Clymer from Rock Solid Knowledge (UK) and Theo Dimitrakos (IFIPTM, UK and Huawei, Germany) who should be able to attend IETF 121 in Dublin. Thanks for your insights, David.
- [Secdispatch] ALFA 2.0 WG for IETF 121 David Brossard
- [Secdispatch] Re: ALFA 2.0 WG for IETF 121 Michael Richardson
- [Secdispatch] Re: ALFA 2.0 WG for IETF 121 Salz, Rich
- [Secdispatch] Re: ALFA 2.0 WG for IETF 121 David Brossard
- [Secdispatch] Re: ALFA 2.0 WG for IETF 121 Rifaat Shekh-Yusef
- [Secdispatch] Re: ALFA 2.0 WG for IETF 121 Deb Cooley