Return-Path: X-Original-To: wimse@ietfa.amsl.com Delivered-To: wimse@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F17C7C151986 for ; Sun, 22 Sep 2024 20:18:10 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=beyondidentity.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 A7iQ2x0PCRuy for ; Sun, 22 Sep 2024 20:18:06 -0700 (PDT) Received: from mail-lj1-x242.google.com (mail-lj1-x242.google.com [IPv6:2a00:1450:4864:20::242]) (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 BA195C14EB17 for ; Sun, 22 Sep 2024 20:18:06 -0700 (PDT) Received: by mail-lj1-x242.google.com with SMTP id 38308e7fff4ca-2f66423686bso32249681fa.3 for ; Sun, 22 Sep 2024 20:18:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=beyondidentity.com; s=google-bid; t=1727061485; x=1727666285; 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=PXVoXUY8KHqsZJY7+Sp+E8SUqvzVrtjECW2U1HhsJZY=; b=byqCbreZIU3zfl4qp6whEvqz/3uw89SYBkNtPiepKd0srTnyyA6440cJ6V9expltPr WMjfnneTNY7X39t6nTX1Rf4hRqIWaIJw1SdC/kNKDH3DzGTAlslQpdEllK5O0boimqNP yX68fJoPhUKRyefOTYsyfmJWO5Of3UPxqny1yBTgoWLwUQKsoJDaZE2KRLG3Rv6JzVWj 4BZgvyl7CPKFzM//r4zn972xQdBexSKwRVOcG5NDtLWf0hVVEVIDsSxiFYJy/3HEifzE C3/ZSj8oeydTLzQv6rWXnn1DpVCzQJB8eQKnO5qikGf7TVpWW3OQSqblT6fJDiX+4A86 CCAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727061485; x=1727666285; 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=PXVoXUY8KHqsZJY7+Sp+E8SUqvzVrtjECW2U1HhsJZY=; b=oO5I2hPRB5UOsorHunWQhb/Vui5Q3xCbFSRRbdUh8u3piDEIQTzK3B9TQpZB2t5kDG VbyzHupWZm0MIa5N7ePHWBglmZ8ld6AhBTLrN7IVSd7P+mx0chZzw1ovpjyYI8CGp5rX MAqV2s7lSf1V+JPzi4gOkvNPDmpYl/LGrZpamEIXhk2Iwe1m+8Qz4iEc8xyiCqfx68t7 GWBaxml7EtUzYwbno3z/ceURoKuLSUpbDaINJFttfBvmRcuavG/wMO+8r4AbMKStjLyj X/+mCNKFrnK4T43NqRczJ673oC8YH6Y4E2ZqiV788d0R1L+lcob5u9g5C4w/SgZ56pL4 KTRg== X-Forwarded-Encrypted: i=1; AJvYcCWR59V5takhdOp0fbRsZwNPnB+xsaO2c6QhkZ3ptWBmjCg7fq5r8H9Koeqzc+Sl73iTwgsEjg==@ietf.org X-Gm-Message-State: AOJu0Yw4sqqNcS1bvivOZfap5RE6NuoOLVzIIaGG4145Pj9RN7xt0cvL 8AVHMnDnCe/5DitCB3/QXWxvjy+G0LKNmLHtg6gT29geV7tGIAplp5wc4SVDjse/BZ0iNIchay7 5fIZgrLB956rRFSNHhieWUGMCePytugRV+tJSqg== X-Google-Smtp-Source: AGHT+IFSsPSxAwy+6aDBL3JJwmKXBLpE+RjzoabbYt0HiCl5pIolFzsO3AwGtC1jh1MGgHKwMRVX/fKKp1Z7V6qzdsk= X-Received: by 2002:a2e:809:0:b0:2f7:4c9d:7a83 with SMTP id 38308e7fff4ca-2f7cc5baef2mr37183411fa.40.1727061484632; Sun, 22 Sep 2024 20:18:04 -0700 (PDT) Received: from 1064022179695 named unknown by gmailapi.google.com with HTTPREST; Sun, 22 Sep 2024 20:18:04 -0700 Received: from 1064022179695 named unknown by gmailapi.google.com with HTTPREST; Sun, 22 Sep 2024 23:18:01 -0400 MIME-Version: 1.0 (Mimestream 1.3.8) References: <013c01db090b$32f726f0$98e574d0$@gmx.net> <935246cc-1467-477b-96e0-48c820491f48@gmail.com> In-Reply-To: From: Dean Saxe Date: Sun, 22 Sep 2024 20:18:04 -0700 Message-ID: To: Justin Richer Content-Type: multipart/alternative; boundary="0000000000004c21c20622c0d6a1" Message-ID-Hash: HOGZDYWA3TX6MYGWI3EVMKVFFSHIVGQF X-Message-ID-Hash: HOGZDYWA3TX6MYGWI3EVMKVFFSHIVGQF X-MailFrom: dean.saxe@beyondidentity.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: John Kemp , "wimse@ietf.org" , "hannes.tschofenig@gmx.net" X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5BWimse=5D_Re=3A_Call_for_the_WIMSE_-_Token_Exchange/Translation?= List-Id: WIMSE Workload Identity in Multi-Service Environment Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --0000000000004c21c20622c0d6a1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks Justin. I=E2=80=99ve set up the new meeting series, I will post it= as described below. -- Dean H. Saxe, CIDPRO Principal Engineer Office of the CTO Beyond Identity dean.saxe@beyondidentity.com On Sep 20, 2024 at 3:35:25=E2=80=AFPM, Justin Richer wrot= e: > My recommendation for group members is to* not use calendar invites at > all*. They don=E2=80=99t tend to play nicely with mailing lists, which of > necessity redistribute the email and reformat it along the way. Weird > things happen. And in some systems, it shows up as extra suspicious when > there=E2=80=99s an invite from someone to a list on the calendar but it s= hows up as > from the list to you in email. > > So with that in mind, I would recommend that the dates and information fo= r > the list be POSTED to the list, in plain text as a message. Communication > for cancelled events can likewise be sent as messages POSTED to the list, > not as calendar actions. > > Additionally: If someone wants to make a public calendar that people can > subscribe to, and wants to keep it up to date, that can be helpful for so= me > folks. This would allow for a single canonical place for all the events > that can be subscribed to as wanted, without hitting issues with the > invitation system. > > As this call is not an official action or meeting of the WG, you=E2=80=99= re free > to organize how you like; but, this is my advice based on years of trying > to get people on a mailing list to call into the same place at the same > time. :) > > =E2=80=94 Justin > > On Sep 20, 2024, at 6:23=E2=80=AFPM, Dean Saxe 40beyondidentity.com@dmarc.ietf.org> wrote: > > To be clear, *all* of the meeting series have now been cancelled. > > If you=E2=80=99re aware of a better way to distribute a meeting series ot= her than > sending it to the mailing list, I=E2=80=99m all ears. > > -dhs > > -- > Dean H. Saxe, CIDPRO > Principal Engineer > Office of the CTO > Beyond Identity > dean.saxe@beyondidentity.com > > > > > On Sep 20, 2024 at 1:38:59=E2=80=AFPM, John Kemp > wrote: > >> Hi Dean, >> >> I don't know whether anyone else gets or got any cancellations, but I >> haven't seen one for this series, or the previous meeting, and I think >> the last invite sent to this list just changed the date to starting this >> prior Tuesday. FWIW. It is certainly confusing. I look forward to >> receiving/knowing the correct meeting series. >> >> Regards, - johnk >> >> On 9/20/24 2:34 PM, Dean Saxe wrote: >> >> Hannes, >> >> >> My apologies. I did cancel the call series and replaced it with one on >> >> the week of Sept 10 and Sept 24. Apparently that message was not >> >> received by all creating confusion. >> >> >> If you have accepted any of the current series of calls please cancel >> >> them. I have sent out cancellations for the existing series. >> >> >> I will resend a new series of meetings starting September 24. >> >> >> Again, my apologies for the confusion. >> >> >> -dhs >> >> >> -- >> >> Dean H. Saxe, CIDPRO >> >> Principal Engineer >> >> Office of the CTO >> >> Beyond Identity >> >> dean.saxe@beyondidentity.com >> >> >> >> >> >> On Sep 17, 2024 at 7:09:23=E2=80=AFAM, hannes.tschofenig@gmx.net >> >> wrote: >> >> > >> >> > Dean, >> >> > >> >> > you scheduled a recurring meeting for the WIMSE Token >> >> > Exchange/Translation, but this is the second time we've been waiting >> >> > in the room without you, the organizer, showing up. I suggest either >> >> > canceling this meeting series or planning it more effectively. >> >> > >> >> > Ciao >> >> > Hannes >> >> > >> >> >> -- > Wimse mailing list -- wimse@ietf.org > To unsubscribe send an email to wimse-leave@ietf.org > > > --0000000000004c21c20622c0d6a1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks Justin.=C2=A0 I=E2=80=99ve set up the new meeting series, I will= post it as described below.
--
Dean H. Saxe, CIDPRO
Principal Engineer
Office of the C= TO
Beyond Identity
<= div>



On Sep 20, 2024 at 3:35:25=E2=80= =AFPM, Justin Richer <jricher@mit.edu= > wrote:
My recommendation for group members is to not use calendar invites at al= l. They don=E2=80=99t tend to play nicely with mailing lists, which of = necessity redistribute the email and reformat it along the way. Weird thing= s happen. And in some systems, it shows up as extra suspicious when there=E2=80=99s an invite from someone to a li= st on the calendar but it shows up as from the list to you in email.

So with that in mind, I would recommend that the dates and information= for the list be POSTED to the list, in plain text as a message. Communicat= ion for cancelled events can likewise be sent as messages POSTED to the lis= t, not as calendar actions.

Additionally: If someone wants to make a public calendar that people c= an subscribe to, and wants to keep it up to date, that can be helpful for s= ome folks. This would allow for a single canonical place for all the events= that can be subscribed to as wanted, without hitting issues with the invitation system.

As this call is not an official action or meeting of the WG, you=E2=80= =99re free to organize how you like; but, this is my advice based on years = of trying to get people on a mailing list to call into the same place at th= e same time. :)

=C2=A0=E2=80=94 Justin

On Sep 20, 2024, at 6:23=E2=80=AFPM, Dean Saxe <dean.saxe=3D40beyondidentity.com@dmarc.= ietf.org> wrote:

To be clear, all of the meeting series have now bee= n cancelled. =C2=A0

If you=E2=80=99re aware of a better way to distribute a me= eting series other than sending it to the mailing list, I=E2=80=99m all ear= s.

-dhs

--
Dean H. Saxe, CIDPRO=
Principal Engineer
Office of the CTO
Beyond Identity




On Sep 20, 2024 at 1:38:59=E2=80=AFPM= , John Kemp <stable.pseudo= nym@gmail.com> wrote:
Hi Dean,

I don't know whether anyone else gets or got any cancellations, but I <= br> haven't seen one for this series, or the previous meeting, and I think =
the last invite sent to this list just changed the date to starting this prior Tuesday. FWIW. It is certainly confusing. I look forward to
receiving/knowing the correct meeting series.

Regards, - johnk

On 9/20/24 2:34 PM, Dean Saxe wrote:
Hannes,

My apologies.=C2=A0 I did cancel the call series = and replaced it with one on
the week of Sept 10 and Sept 24.=C2=A0 Apparently= that message was not
received by all creating confusion.

If you have accepted any of the current series of= calls please cancel
them.=C2=A0 I have sent out cancellations for the= existing series.

I will resend a new series of meetings starting S= eptember 24.

Again, my apologies for the confusion.

-dhs

--
Dean H. Saxe, CIDPRO <https://idpro.org/cidpro/>
Principal Engineer
Office of the CTO
Beyond Identity
d= ean.saxe@beyondidentity.com <mailto:dean.saxe@beyondidentity.com>




On Sep 17, 2024 at 7:09:23=E2=80=AFAM, hannes.tschofenig@gmx.net
<mailto:hannes.tschofenig@gmx.net> wrote:
>
> Dean,
>
> you scheduled a recurring meeting for the WI= MSE Token
> Exchange/Translation, but this is the second= time we've been waiting
> in the room without you, the organizer, show= ing up. I suggest either
> canceling this meeting series or planning it= more effectively.
>
> Ciao
> Hannes
>

--
Wimse mailing list -- wimse@ietf.org<= br> To unsubscribe send an email to wim= se-leave@ietf.org

--0000000000004c21c20622c0d6a1--