Return-Path: <rifaat.s.ietf@gmail.com>
X-Original-To: secdispatch@mail2.ietf.org
Delivered-To: secdispatch@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1])
	by mail2.ietf.org (Postfix) with ESMTP id 3DB4BFC1D61E
	for <secdispatch@mail2.ietf.org>; Fri,  5 Jun 2026 18:12:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1780708363; bh=GyQ3bTXLYt1aBZWvNja8kzk5EhfDLbAG4O/GCvu3yhc=;
	h=References:In-Reply-To:From:Date:Subject:To:Cc;
	b=TnJ5OGfRXbnZU8AR7BWf3TyXGLmQJ3dtSt3fN3cTDJVUDl7RG4GZgmi+DiEmwpdzv
	 bGhLkU3sjF1V7nKGDeuvLUTg5LaOnh6tpevG1nFnSkyjjxhPLrS4Xfh5ADq3Sp3AfV
	 L1xHaitmi2segAHfJFa9n/8UaaPUSqfMGuP7qDLM=
X-Virus-Scanned: amavisd-new at ietf.org
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, FREEMAIL_FROM=0.001,
	HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
	SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key)
	header.d=gmail.com
Received: from mail2.ietf.org ([166.84.6.31])
	by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YXuXdecfyIgV for <secdispatch@mail2.ietf.org>;
	Fri,  5 Jun 2026 18:12:41 -0700 (PDT)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com
 [IPv6:2a00:1450:4864:20::12b])
	(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 mail2.ietf.org (Postfix) with ESMTPS id 206B7FC1D5D4
	for <secdispatch@ietf.org>; Fri,  5 Jun 2026 18:12:34 -0700 (PDT)
Received: by mail-lf1-x12b.google.com with SMTP id
 2adb3069b0e04-5aa63628d26so2094898e87.0
        for <secdispatch@ietf.org>; Fri, 05 Jun 2026 18:12:34 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1780708353; cv=none;
        d=google.com; s=arc-20240605;
        b=I44fZmxFbyTPLZ5QkoZtjDQsw42NXNLrVp9AS9YnDqswo1KkZPffVFMuD4+ogsuzoP
         7zQA9T5e5BFNSbOieHLjiCGv92KU8acTug/jgOaHL57f5MbVZMHJkmibno9ZkxyT2jMY
         rvRpexN/yIenvkPdYn0wMTvlJNPszxCDQUit3Df+ucZZeCZgD78hyp0b/xvgvTvlL0FL
         vOP3CG/JSTNNMeaAvjassSPAVqVBOdn8fFA2jhtdt7IE2hnOCNJ5PgjpWToDINbObHzS
         MlULxTM6WrJhfKj+SJIWJA1k+MH7b5nPRanhw7fGhJB14ur5cvmmK3Nj2yfPoWyAwk8T
         JqQQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com;
 s=arc-20240605;
        h=cc:to:subject:message-id:date:from:in-reply-to:references
         :mime-version:dkim-signature;
        bh=lO/e2bNhy8eL6gsIeiS4k5cefETFBNtONnWtyYC7Bnw=;
        fh=e0P0E6tXSQwi+0VALq9wq0+6FzUskvybvLXs6wbaFP8=;
        b=XLky7ojUCdsRuqL2rmBPNsbYtsmfpX3V3cxdWQfAqOzgDB3hjCF1GmhGXW/j8LzRFO
         NweE7MV0l5WIccXJ/71efQzCzxqeMDtVd3fvgbyvT9WCiisT+wk1rK9cxzNpOc72Xwtx
         teXzXqjWx3S/7ArzCJr5yFEhKAu++56tx3+HrPAhJfes/1u6IeVRVsUWmVQADNx5NNRM
         9vmLAfcKDlNp+1HGB3vp8ozKJM2ulrzgFZKshlQxZg4bgsjbl4Rbf+dzUkqhRoJ2cFS4
         ENH7oMVzv/aGTi0eGtMbyydV2f6J7kVXgEUGsEqKpBYXPKxorIXtNZIgw6caxG0ZgiPk
         aD+Q==;
        darn=ietf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20251104; t=1780708353; x=1781313153; 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=lO/e2bNhy8eL6gsIeiS4k5cefETFBNtONnWtyYC7Bnw=;
        b=j8wqm77U6IHkZyTwnSCzVOAGUzpinYXkIYUO3x2Uwv7yRafeyzWaIQQE4fvkDzaxPJ
         a0cNdN6uyERv0kAR9ifrOPeQf/YUwlvyLkOdiqqXhw+delYWzCUW8rFCiW8kJ2Q1joaW
         jICbObaMIrlllCjX/RVmYnpv5g2bfizvTHNWHjTYgv3+TsgIx3IIG+F4VVj5yAen5oBa
         Zh/iyoRw8toEqRWmo8cgUNi37BRBXlfJtFCgBvED4Ep2QVjHhYVLv75X+JNXY6Bne7UU
         SK8pt0B6FfmDyF5GNx/IWlRj7m0rfoV1h/KC+VhrfwbYq3wpKN2fPLQwdTIIVNBDDWkI
         NGAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20251104; t=1780708353; x=1781313153;
        h=cc:to:subject:message-id:date:from:in-reply-to:references
         :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date
         :message-id:reply-to;
        bh=lO/e2bNhy8eL6gsIeiS4k5cefETFBNtONnWtyYC7Bnw=;
        b=J74BgqswEkWxfVkOASt5ngImIXQkJoZlSeHvJDVY8pvBAkKE6isXPi3Y68i0N9SW8E
         xff95lgoAah5Ne5wAyvDXL4Njg/pYo5bFrq/e809BF5illWVBNbEGpzd02ooGSEDb1lD
         tfB9nB0GABWDijN2FrfghOleN3mAZMEDQj37Jhl5OGgMIOHkUCHroxfMhsm4nDmpQ5hu
         x3qPVC1L0Fz7Lk4zP5/2x8Kj9T67bACWa/UUCJMA4pDp2m0x/xSRzV55cRhLr78lktKz
         mgSaLiX/JXLD0fAT706Q+Dfco06eQNUcXsuxDqJ3g0CSbgsNoHOZfMsU0rZ5NiYQCiBy
         UDpA==
X-Forwarded-Encrypted: i=1;
 AFNElJ8ZMHnqg/jRnSDUIM3Ek2Tlo4KEVysLEru4s3QVkWfikXocQHFhlDlxtTiG0GHRluIdQGRw/jnwHPlbqg==@ietf.org
X-Gm-Message-State: AOJu0YxVVoQHvlUF2Op8YuJQYsZ89dYEDL2eQsJQ7z+Ulz4VhS3fCZ1R
	ytI0JrMgbjAPRiAmVLPMcgI/o1OrAXt3mg6Ezeca0d+7GLh2K38IgQCJoOdoe+MUpeO4TVamQk4
	O16YrTSA0UKjxI5EZ0whDpTwUD14Eze9awIDD
X-Gm-Gg: Acq92OEgAaLFer5YH+Z3sInqSdw9fnAoA2ciwOTGzIjKMo0VMuTkwuMtwe+RnBHdgfk
	6mhVHmZQrMdK8q3Q235OUIA3jYbogBFkv+4nUlZe8DOatllS8aFdi9gq95/rkwde6dXB3Xoe3U7
	/L2m69P0gV0MMTG8neK5S7XfekK19DB0F5CITD/XUtdp+jXuWftoHIh5OZ5LDdhWWDUwZebHSHZ
	ft3lXKkrg5qtcAOZTGd3GmwCb3ivTm5+r351+0MENPQiFab6p9YtBx9uO+p07IVVPZVQ0mhJcZS
	no1smnoTxdWdxI96BWBzzBTYYkuQ9GiTimVIwcmhWp0HyOwq0qan26ByUZnV56aVEyZOscfR1jc
	U+VnBFHvF/hZzIpWqKVGyRbUyZvOunssoPP+R
X-Received: by 2002:a05:6512:239f:b0:5aa:6c05:f0a with SMTP id
 2adb3069b0e04-5aa87c03936mr1605127e87.35.1780708352457; Fri, 05 Jun 2026
 18:12:32 -0700 (PDT)
MIME-Version: 1.0
References: <ec69a424-7795-4c58-a3f0-9667536a8ca9@cs.tcd.ie>
 <CADNypP_CxHSsEOXeLL7U_fY3ej8EHOOxiYMQ=EtUoZZ=GFpTjg@mail.gmail.com>
 <CABcZeBPHahXTBv13qyFBdf8+yrj45dqSMabhtsx=cpsm+me1yg@mail.gmail.com>
 <CADNypP8Qqjo_Wn0QhPdTw2Nti8k+Shjsg3uW4=1kA3N5JN9q=g@mail.gmail.com>
 <1AD31B62A46771994025AF39@PSB>
 <CADNypP-CWFt6=XoMdLKjakKaTVMePE3CV5imESiv8w95Y7EpUg@mail.gmail.com>
 <53B984E48E83A2BA25C83DB2@PSB>
In-Reply-To: <53B984E48E83A2BA25C83DB2@PSB>
From: Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com>
Date: Fri, 5 Jun 2026 21:12:19 -0400
X-Gm-Features: AVVi8CcwWePiFZ7Ome0cAB8geV6UEnXlv4wu_Q3nUtRhWT9PYJWHraRsk2VenO8
Message-ID: 
 <CADNypP_n3+7QZC0CQH2FFDLgA1yzcZS6G9knoJXcOa7rkzjqLQ@mail.gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary="000000000000cbfef906538b78c4"
Message-ID-Hash: QS5SAQD3MNHPSBWW46VD7WNZDNYNL5JR
X-Message-ID-Hash: QS5SAQD3MNHPSBWW46VD7WNZDNYNL5JR
X-MailFrom: rifaat.s.ietf@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: Eric Rescorla <ekr@rtfm.com>, dispatch@ietf.org,
 secdispatch <secdispatch@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: =?utf-8?q?=5BSecdispatch=5D_Re=3A_=5Bdispatch=5D_Re=3A_Re=3A_DISPATCH/SECDIS?=
 =?utf-8?q?PATCH_-_Call_for_topics_for_Vienna=2E?=
List-Id: Security Dispatch <secdispatch.ietf.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/secdispatch/HDc4pN9euEQ-ZAmLysUPnglQF64>
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>

--000000000000cbfef906538b78c4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi John,

Using the
> interim slot for an informal way to focus part of the at-meeting
> discussion would seem like a way to avoid that problem.


This sounds like an interesting idea and reasonable compromise.
Use the interim to discuss the drafts, but make a final decision during the
Vienna meeting without rehashing the interim meeting discussion.

Regards,
 Rifaat


On Fri, Jun 5, 2026 at 8:07=E2=80=AFPM John C Klensin <john-ietf@jck.com> w=
rote:

> Rifaat,
>
> Noting Jim's and Ekr's later messages, with which I do not disagree,
> an added comment or two inline below...
>
> --On Friday, June 5, 2026 17:13 -0400 Rifaat Shekh-Yusef
> <rifaat.s.ietf@gmail.com> wrote:
>
> > Ekr, John,
> >
> > These are valid concerns and I'm not going to pretend that I have
> > all the answers to these questions/concerns.
> > Having said that, I agree that the mailing list must have the final
> > say on any decision we make during an interim meeting.
> >
> > More inline..,
> >
> > Regards,
> >  Rifaat
> >
> > On Fri, Jun 5, 2026 at 4:22=E2=80=AFPM John C Klensin <john-ietf@jck.co=
m>
> > wrote:
> >
> >> --On Friday, June 5, 2026 15:44 -0400 Rifaat Shekh-Yusef
> >> <rifaat.s.ietf@gmail.com> wrote:
> >>
> >> > On Fri, Jun 5, 2026 at 3:17=E2=80=AFPM Eric Rescorla <ekr@rtfm.com>
> >> > wrote:
> >> >
> >> >> Like I take Stephen to be, I can't say I'm that excited about
> >> >> that. The audience for a virtual dispatch is entirely different
> >> >> from that at the IETF plenary meeting, and I don't think as
> >> >> representative of IETF consensus.
> >>
> >> > That might end up being the case, but we would like to try that
> >> > and see if enough people show up to make it a viable option.
> >>
> >> Rifaat,
> >>
> >> I share at least some of Stephen's and Ekr's concern, but given
> >> your response above, want to add an additional caution.  The
> >> reason we've traditionally had a rule requiring that decisions be
> >> made on mailing lists and not in meetings is precisely because
> >> even agreement at IETF plenary meetings cannot be taken as
> >> representative of IETF consensus. The IESG (and the community)
> >> have cut DISPATCH some slack about that in the past and that has
> >> raised additional concerns when DISPATCH meetings are scheduled
> >> against other meetings in the same time slot. Even if none of
> >> those meetings are in DISPATCH-related Areas, many of us have
> >> interest in multiple areas and therefore might still have
> >> conflicts.    It might be possible to make the case that
> >> participation in an interim/ virtual meeting is even worse as a
> >> measure of IETF consensus than plenary meeting sessions or,
> >> depending on attendance, better.   But trying to make that
> >> determination would be difficult or impossible, requiring
> >> agreement about what is to be counted and how, agreement that I'm
> >> guessing we could never reach.
> >>
> >> However, even if the error has been made in other places, I'm quite
> >> sure that trying to make a determination of representativeness and
> >> validity of a meeting and its results based on the number of people
> >> who show up, as you suggest, does not work.  Unless evaluated very
> >> carefully -- not just counting heads-- an interim poses a
> >> particularly serious risk because, without registration fees,
> >> travel commitments, or restrictions on participation from
> >> particular sectors or interests, it would be all too easy for an
> >> organization or cluster of interests to get enough people to show
> >> up to make a particular point of view appear to dominate a
> >> discussion and its outcomes.
>
> > Fair concern, but a counter argument might be that
> > "...registration fees,
> > travel commitments,... "
> > means only powerful and well funded corporations have advantage
> > because they can afford to send their people to the meetings.
>
> Absolutely... and I tried to hint at that elsewhere in my note.
>
> Of course, that is also only a step short of an argument that we
> should stop holding in-person meetings at all, or at least cut their
> frequency.  We've had that discussion in other contexts and it has
> not led anywhere.
>
> >> So go for this if it makes sense but be _really_ careful about how
> >> you evaluate success (including the ability to make decisions or
> >> determine consensus).  Or...
>
> > We, as a community, need to evaluate the success of this exercise.
> > The chairs are here to help make this happen, but we will always
> > look for the community to make a final decision on whether we
> > continue with this approach or not.
>
> Yes.  And see those subsequent notes.
>
>
> >> >> I would prefer that we instead use discussion and interest on
> >> >> the mailing list to guide which proposals get time at that
> >> >> meeting. Proposals which can't meet a minimum support level
> >> >> on-list are unlikely to get traction in IETF in any case.
>
> >> A different idea (not necessarily better, just different and maybe
> >> worth considering) would be to use an interim meeting to formulate
> >> a concise summary of the issues and decision points for
> >> presentation during the plenary Meeting.  There might not be
> >> universal agreement with that approach either, but it would at
> >> least avoid the appearance of making a consensus determination at
> >> an unusual and unrepresentative meeting.
>
> > Interesting idea.
> > But if we agree that the mailing list must have the final say on any
> > decision, is this needed?
>
> Two things, without really answering your question:
>
> * Even when we say "final say on mailing list" and especially if one
> has a relatively low-participation list (for reasons Ekr and Jim have
> explained and because Dispatch has traditionally, at least IMO, not
> been a list-centered operation for actual evaluations, what is
> decided on at meetings does bias the mailing list review.  That is
> even more so when it is couched as a review (e.g., "anyone have
> serious objections to what the meeting decided?" rather than a
> reexamination with the meeting discussions contributing to that.
>
> * What I had in mind was using the interim to provide a concise and
> succinct discussion of the AI-related issues to the meeting at IETF
> 126 and discuss the issues and their implications at that meeting.
> That would be instead of effectively dividing that meeting into two
> parts and, rather than trying to get a slot for each slot on the
> meeting agenda, treating this interim as the alternate slot.   The
> intent would be to condense the AI discussion at IETF sufficiently
> that you could squeeze the rest of the agenda in, rather than pulling
> the AI discussion off the agenda.
>
> Of course, given the exceptional circumstances of the "new" DISPATCH
> just having approved by the IESG, the chairs could just ask for a
> second slot, or a longer slot, at the IETF meeting and either avoid
> the interim --or make it more clearly supplemental-- that way.
>
> I think this may be before your time, but, once upon a time, we had
> at least an informal rule prohibiting interims within about three
> weeks before, or some time after, an IETF plenary meeting week,
> precisely to avoid interims as substitutes for all or part of a
> regular meeting session rather than actual between-meeting sessions.
> I don't recall when that rule disappeared (or just stopped being
> enforced) but this interim, if used to substitute for what would
> otherwise be part of the meeting agenda, looks like a fairly good
> example of the reason for that rule when it was created.  Using the
> interim slot for an informal way to focus part of the at-meeting
> discussion would seem like a way to avoid that problem.
>
> >> > Many times requests on the list do not get much attention, but
> >> > that does not always mean they do not have merit.
> >>
> >> Sure.  And, at least sometimes, requests on the list get a good
> >> deal of attention and stir up considerable noise.  That doesn't
> >> always mean that they have merit either.
>
> > Agree.
>
> Thanks.  And, again borrowing from the later notes, both are high
> risk when list participation does not actively reflect the people
> among IETF, or even WG, participants with an active interest in (or
> likely to be affected by) any outcomes.
>
> best,
>   john
>
>

--000000000000cbfef906538b78c4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi John,</div><div><br></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex">Using the<br>interim slot for an informal way to =
focus part of the at-meeting<br>discussion would seem like a way to avoid t=
hat problem.</blockquote><div>=C2=A0</div><div>This sounds like an interest=
ing=C2=A0idea and reasonable compromise.</div><div>Use the interim to discu=
ss the drafts, but make a final decision during the Vienna meeting without =
rehashing the interim meeting discussion.</div><div><br></div><div>Regards,=
</div><div>=C2=A0Rifaat</div><div><br></div></div><br><div class=3D"gmail_q=
uote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, J=
un 5, 2026 at 8:07=E2=80=AFPM John C Klensin &lt;<a href=3D"mailto:john-iet=
f@jck.com">john-ietf@jck.com</a>&gt; wrote:<br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">Rifaat,<br>
<br>
Noting Jim&#39;s and Ekr&#39;s later messages, with which I do not disagree=
,<br>
an added comment or two inline below...<br>
<br>
--On Friday, June 5, 2026 17:13 -0400 Rifaat Shekh-Yusef<br>
&lt;<a href=3D"mailto:rifaat.s.ietf@gmail.com" target=3D"_blank">rifaat.s.i=
etf@gmail.com</a>&gt; wrote:<br>
<br>
&gt; Ekr, John,<br>
&gt; <br>
&gt; These are valid concerns and I&#39;m not going to pretend that I have<=
br>
&gt; all the answers to these questions/concerns.<br>
&gt; Having said that, I agree that the mailing list must have the final<br=
>
&gt; say on any decision we make during an interim meeting.<br>
&gt; <br>
&gt; More inline..,<br>
&gt; <br>
&gt; Regards,<br>
&gt;=C2=A0 Rifaat<br>
&gt; <br>
&gt; On Fri, Jun 5, 2026 at 4:22=E2=80=AFPM John C Klensin &lt;<a href=3D"m=
ailto:john-ietf@jck.com" target=3D"_blank">john-ietf@jck.com</a>&gt;<br>
&gt; wrote:<br>
&gt; <br>
&gt;&gt; --On Friday, June 5, 2026 15:44 -0400 Rifaat Shekh-Yusef<br>
&gt;&gt; &lt;<a href=3D"mailto:rifaat.s.ietf@gmail.com" target=3D"_blank">r=
ifaat.s.ietf@gmail.com</a>&gt; wrote:<br>
&gt;&gt; <br>
&gt;&gt; &gt; On Fri, Jun 5, 2026 at 3:17=E2=80=AFPM Eric Rescorla &lt;<a h=
ref=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt;<br>
&gt;&gt; &gt; wrote:<br>
&gt;&gt; &gt; <br>
&gt;&gt; &gt;&gt; Like I take Stephen to be, I can&#39;t say I&#39;m that e=
xcited about<br>
&gt;&gt; &gt;&gt; that. The audience for a virtual dispatch is entirely dif=
ferent<br>
&gt;&gt; &gt;&gt; from that at the IETF plenary meeting, and I don&#39;t th=
ink as<br>
&gt;&gt; &gt;&gt; representative of IETF consensus.<br>
&gt;&gt; <br>
&gt;&gt; &gt; That might end up being the case, but we would like to try th=
at<br>
&gt;&gt; &gt; and see if enough people show up to make it a viable option.<=
br>
&gt;&gt; <br>
&gt;&gt; Rifaat,<br>
&gt;&gt; <br>
&gt;&gt; I share at least some of Stephen&#39;s and Ekr&#39;s concern, but =
given<br>
&gt;&gt; your response above, want to add an additional caution.=C2=A0 The<=
br>
&gt;&gt; reason we&#39;ve traditionally had a rule requiring that decisions=
 be<br>
&gt;&gt; made on mailing lists and not in meetings is precisely because<br>
&gt;&gt; even agreement at IETF plenary meetings cannot be taken as<br>
&gt;&gt; representative of IETF consensus. The IESG (and the community)<br>
&gt;&gt; have cut DISPATCH some slack about that in the past and that has<b=
r>
&gt;&gt; raised additional concerns when DISPATCH meetings are scheduled<br=
>
&gt;&gt; against other meetings in the same time slot. Even if none of<br>
&gt;&gt; those meetings are in DISPATCH-related Areas, many of us have<br>
&gt;&gt; interest in multiple areas and therefore might still have<br>
&gt;&gt; conflicts.=C2=A0 =C2=A0 It might be possible to make the case that=
<br>
&gt;&gt; participation in an interim/ virtual meeting is even worse as a<br=
>
&gt;&gt; measure of IETF consensus than plenary meeting sessions or,<br>
&gt;&gt; depending on attendance, better.=C2=A0 =C2=A0But trying to make th=
at<br>
&gt;&gt; determination would be difficult or impossible, requiring<br>
&gt;&gt; agreement about what is to be counted and how, agreement that I&#3=
9;m<br>
&gt;&gt; guessing we could never reach.<br>
&gt;&gt; <br>
&gt;&gt; However, even if the error has been made in other places, I&#39;m =
quite<br>
&gt;&gt; sure that trying to make a determination of representativeness and=
<br>
&gt;&gt; validity of a meeting and its results based on the number of peopl=
e<br>
&gt;&gt; who show up, as you suggest, does not work.=C2=A0 Unless evaluated=
 very<br>
&gt;&gt; carefully -- not just counting heads-- an interim poses a<br>
&gt;&gt; particularly serious risk because, without registration fees,<br>
&gt;&gt; travel commitments, or restrictions on participation from<br>
&gt;&gt; particular sectors or interests, it would be all too easy for an<b=
r>
&gt;&gt; organization or cluster of interests to get enough people to show<=
br>
&gt;&gt; up to make a particular point of view appear to dominate a<br>
&gt;&gt; discussion and its outcomes.<br>
<br>
&gt; Fair concern, but a counter argument might be that<br>
&gt; &quot;...registration fees,<br>
&gt; travel commitments,... &quot;<br>
&gt; means only powerful and well funded corporations have advantage<br>
&gt; because they can afford to send their people to the meetings.<br>
<br>
Absolutely... and I tried to hint at that elsewhere in my note.<br>
<br>
Of course, that is also only a step short of an argument that we<br>
should stop holding in-person meetings at all, or at least cut their<br>
frequency.=C2=A0 We&#39;ve had that discussion in other contexts and it has=
<br>
not led anywhere.<br>
<br>
&gt;&gt; So go for this if it makes sense but be _really_ careful about how=
<br>
&gt;&gt; you evaluate success (including the ability to make decisions or<b=
r>
&gt;&gt; determine consensus).=C2=A0 Or...<br>
<br>
&gt; We, as a community, need to evaluate the success of this exercise.<br>
&gt; The chairs are here to help make this happen, but we will always<br>
&gt; look for the community to make a final decision on whether we<br>
&gt; continue with this approach or not.<br>
<br>
Yes.=C2=A0 And see those subsequent notes.<br>
<br>
<br>
&gt;&gt; &gt;&gt; I would prefer that we instead use discussion and interes=
t on<br>
&gt;&gt; &gt;&gt; the mailing list to guide which proposals get time at tha=
t<br>
&gt;&gt; &gt;&gt; meeting. Proposals which can&#39;t meet a minimum support=
 level<br>
&gt;&gt; &gt;&gt; on-list are unlikely to get traction in IETF in any case.=
<br>
<br>
&gt;&gt; A different idea (not necessarily better, just different and maybe=
<br>
&gt;&gt; worth considering) would be to use an interim meeting to formulate=
<br>
&gt;&gt; a concise summary of the issues and decision points for<br>
&gt;&gt; presentation during the plenary Meeting.=C2=A0 There might not be<=
br>
&gt;&gt; universal agreement with that approach either, but it would at<br>
&gt;&gt; least avoid the appearance of making a consensus determination at<=
br>
&gt;&gt; an unusual and unrepresentative meeting.<br>
<br>
&gt; Interesting idea.<br>
&gt; But if we agree that the mailing list must have the final say on any<b=
r>
&gt; decision, is this needed?<br>
<br>
Two things, without really answering your question:<br>
<br>
* Even when we say &quot;final say on mailing list&quot; and especially if =
one<br>
has a relatively low-participation list (for reasons Ekr and Jim have<br>
explained and because Dispatch has traditionally, at least IMO, not<br>
been a list-centered operation for actual evaluations, what is<br>
decided on at meetings does bias the mailing list review.=C2=A0 That is<br>
even more so when it is couched as a review (e.g., &quot;anyone have<br>
serious objections to what the meeting decided?&quot; rather than a<br>
reexamination with the meeting discussions contributing to that.<br>
<br>
* What I had in mind was using the interim to provide a concise and<br>
succinct discussion of the AI-related issues to the meeting at IETF<br>
126 and discuss the issues and their implications at that meeting.<br>
That would be instead of effectively dividing that meeting into two<br>
parts and, rather than trying to get a slot for each slot on the<br>
meeting agenda, treating this interim as the alternate slot.=C2=A0 =C2=A0Th=
e<br>
intent would be to condense the AI discussion at IETF sufficiently<br>
that you could squeeze the rest of the agenda in, rather than pulling<br>
the AI discussion off the agenda.<br>
<br>
Of course, given the exceptional circumstances of the &quot;new&quot; DISPA=
TCH<br>
just having approved by the IESG, the chairs could just ask for a<br>
second slot, or a longer slot, at the IETF meeting and either avoid<br>
the interim --or make it more clearly supplemental-- that way.<br>
<br>
I think this may be before your time, but, once upon a time, we had<br>
at least an informal rule prohibiting interims within about three<br>
weeks before, or some time after, an IETF plenary meeting week,<br>
precisely to avoid interims as substitutes for all or part of a<br>
regular meeting session rather than actual between-meeting sessions.<br>
I don&#39;t recall when that rule disappeared (or just stopped being<br>
enforced) but this interim, if used to substitute for what would<br>
otherwise be part of the meeting agenda, looks like a fairly good<br>
example of the reason for that rule when it was created.=C2=A0 Using the<br=
>
interim slot for an informal way to focus part of the at-meeting<br>
discussion would seem like a way to avoid that problem.<br>
<br>
&gt;&gt; &gt; Many times requests on the list do not get much attention, bu=
t<br>
&gt;&gt; &gt; that does not always mean they do not have merit.<br>
&gt;&gt; <br>
&gt;&gt; Sure.=C2=A0 And, at least sometimes, requests on the list get a go=
od<br>
&gt;&gt; deal of attention and stir up considerable noise.=C2=A0 That doesn=
&#39;t<br>
&gt;&gt; always mean that they have merit either.<br>
<br>
&gt; Agree.<br>
<br>
Thanks.=C2=A0 And, again borrowing from the later notes, both are high<br>
risk when list participation does not actively reflect the people<br>
among IETF, or even WG, participants with an active interest in (or<br>
likely to be affected by) any outcomes.<br>
<br>
best,<br>
=C2=A0 john<br>
<br>
</blockquote></div>

--000000000000cbfef906538b78c4--

