[Secdispatch] Re: ALFA 2.0 WG for IETF 121

Deb Cooley <debcooley1@gmail.com> Sun, 06 October 2024 18:36 UTC

Return-Path: <debcooley1@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 8CA07C151079 for <secdispatch@ietfa.amsl.com>; Sun, 6 Oct 2024 11:36:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.854
X-Spam-Level:
X-Spam-Status: No, score=-1.854 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 HIPOk808pdHZ for <secdispatch@ietfa.amsl.com>; Sun, 6 Oct 2024 11:36:04 -0700 (PDT)
Received: from mail-pg1-x534.google.com (mail-pg1-x534.google.com [IPv6:2607:f8b0:4864:20::534]) (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 EA248C14F704 for <secdispatch@ietf.org>; Sun, 6 Oct 2024 11:36:04 -0700 (PDT)
Received: by mail-pg1-x534.google.com with SMTP id 41be03b00d2f7-7db637d1e4eso2574038a12.2 for <secdispatch@ietf.org>; Sun, 06 Oct 2024 11:36:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728239764; x=1728844564; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=myP+SATe1Hy7OlVf38DeDQVl27fcYKzxAe99OIHOfAE=; b=ZcXqnCFLWkUXxg6mRiXDl33m8o0xYckWKbOrPRQ7Tw4k8VscbAqqLXsv/80s718lKW lGKWQpKR2Q0p0Ko9x93ZTl/GSNfe9tmTksya8mXQLpTxO5iwf5KaTigK29TK+GDAfZSm +doP0vGqRaHOQY/JsYJzjrzhU2EixXr+W6CDS4Goy+hry8fLVgxFAw36pur0jh7lSb0T FFAZ8+dYUbz0z4tO/OlBithLgGFXinJW8htWyZWw+j5VYhY60bYgLyMEBHANYUsfxhRx Jpvj06w4JW1KVjgofnwH1bkYfdv2GCtHJCG4+HpoKCq9OKHJabi8RRyeLgG9JWthYdJX btNw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728239764; x=1728844564; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=myP+SATe1Hy7OlVf38DeDQVl27fcYKzxAe99OIHOfAE=; b=sUnTRHfN/l4xRDMIjWRSdB0E3bBL3NMIG+aN5Uu8Avy9LD7UwefGHAAJIT1DcD6Ad+ A5u8IwmsNiGPXDIusU9xcNh2KityD9SB6V1poQAOA4zyfzMCMAUjmEkwRyjIAJjmLgKe sX0iB2yJISFUvc4CbkJmmJ/i+cNi9JK7oSlWMUxQzQXcZ+03lMpbm2RmXenWI8N/6DdD PHlT659eR5Bpu95tuzvf1aPIjQvKpmtyIbY2ODSIvWMTLc8Aaq+V4Kis4K+Ko2DgStpF wghVNjwhEuNKFMyFzwu+DyrRJzHxihV6blxjoJeIwppfbFSIGFcjwtFunQrUnZlwwW7W 2wYQ==
X-Forwarded-Encrypted: i=1; AJvYcCUFhYIitnCFrrianeLYN8wt+lTPvK3sTZY3OYWs6TL0q2WRbFfntmsCD6oHWAIihou+XgRg0lMYcouTFg==@ietf.org
X-Gm-Message-State: AOJu0YxQ+ZFFCl2fnewakpFzDCOx9m+T11NPkmfalBbf5J5cZKj+sgcS gMxBkjcYxKsXMX33T070WK1ThVulmPEObK8ObpX1tD8bAjTWwAg0PmL9mq3h5y47WalSBxKgaO2 CZTXQJ2MkyRtQjJaQanSykbfzQA==
X-Google-Smtp-Source: AGHT+IFTAfM8gmo75sXHtGRRdRyaTOB2jkqhVwkd2t6lD5mzUgebnIE4ihHkSZ+DS8HakZqZkgJ1QCtPrUxzbtec/Pg=
X-Received: by 2002:a05:6a20:c91b:b0:1d3:edb:d5cd with SMTP id adf61e73a8af0-1d6dfa33c74mr12712427637.16.1728239764308; Sun, 06 Oct 2024 11:36:04 -0700 (PDT)
MIME-Version: 1.0
References: <CAJO7GQ-V4hS887s4d9rhgMG12WAAybCuJ=7Rf+oAFBvpDUCAHA@mail.gmail.com> <DC4F3701-7A36-4C0A-BC69-91055D5EC38F@nohats.ca>
In-Reply-To: <DC4F3701-7A36-4C0A-BC69-91055D5EC38F@nohats.ca>
From: Deb Cooley <debcooley1@gmail.com>
Date: Sun, 06 Oct 2024 14:35:53 -0400
Message-ID: <CAGgd1OfjUCkh1xzTOWDWhxq+fZNYcSbgkz7V4E14=rUt8AuNHw@mail.gmail.com>
To: Andrew Clymer <andy@rocksolidknowledge.com>, Theo Dimitrakos <theo.dimitrakos@ifiptm.org>, theo.dimitrakos@huawei.com, secdispatch@ietf.org
Content-Type: multipart/alternative; boundary="0000000000003d0e500623d32d84"
Message-ID-Hash: WS5ONJVHXPHW4KXWWBCHWLVHGF5HNIPX
X-Message-ID-Hash: WS5ONJVHXPHW4KXWWBCHWLVHGF5HNIPX
X-MailFrom: debcooley1@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
CC: Paul Wouters <paul.wouters@aiven.io>, Paul Wouters <paul@nohats.ca>, Daniel Kahn Gillmor <dkg@fifthhorseman.net>, Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com>
X-Mailman-Version: 3.3.9rc5
Precedence: list
Subject: [Secdispatch] Re: ALFA 2.0 WG for IETF 121
List-Id: Security Dispatch <secdispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/9CJFZX5WJ6qSLkgswbcCkmY_Nec>
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,

I've taken the liberty to join these messages into one address list.
Apologies if the information below is redundant....

There is an experiment ongoing with the dispatch groups, at IETF 121 there
is an alldispatch (instead of secdispatch).  This experiment/working group
can be reached by emailing alldispatch@ietf.org .

This is exactly where you should bring your ideas.  Many times authors are
remote, if that is easier for you.

Oftentimes groups like to have a side meeting later in the week after a
dispatch meeting.  To do that you have to have at least one person on-site
(to run the meeting).  Side meetings can have remote participants, but
those participants need to be registered for the meeting.

Let us know what else we can do to help.

Deb Cooley
Sec AD


> Begin forwarded message:
>
> *From:* David Brossard <david.brossard@gmail.com>
> *Date:* October 4, 2024 at 06:15:03 EDT
> *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>
> *Subject:* *[Secdispatch] ALFA 2.0 WG for IETF 121*
>
> 
> 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 mailing list -- secdispatch@ietf.org
> To unsubscribe send an email to secdispatch-leave@ietf.org
>
>