[Secdispatch] Re: [dispatch] Re: Re: DISPATCH/SECDISPATCH - Call for topics for Vienna.
Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com> Sat, 06 June 2026 01:12 UTC
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, 05 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: [Secdispatch] Re: [dispatch] Re: Re: DISPATCH/SECDISPATCH - Call for topics for Vienna.
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>
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 PM John C Klensin <john-ietf@jck.com> wrote: > 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 PM John C Klensin <john-ietf@jck.com> > > 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 PM 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 > >
- [Secdispatch] DISPATCH/SECDISPATCH - Call for top… Rifaat Shekh-Yusef
- [Secdispatch] Re: [dispatch] DISPATCH/SECDISPATCH… Stephen Farrell
- [Secdispatch] Re: [dispatch] DISPATCH/SECDISPATCH… Rifaat Shekh-Yusef
- [Secdispatch] Re: [dispatch] DISPATCH/SECDISPATCH… Eric Rescorla
- [Secdispatch] Re: [dispatch] DISPATCH/SECDISPATCH… Rifaat Shekh-Yusef
- [Secdispatch] Re: [dispatch] DISPATCH/SECDISPATCH… Eric Rescorla
- [Secdispatch] Re: [dispatch] DISPATCH/SECDISPATCH… Demi Marie Obenour
- [Secdispatch] Re: [dispatch] DISPATCH/SECDISPATCH… Eric Rescorla
- [Secdispatch] Re: [dispatch] DISPATCH/SECDISPATCH… Demi Marie Obenour
- [Secdispatch] Re: [dispatch] DISPATCH/SECDISPATCH… Eric Rescorla
- [Secdispatch] Re: [dispatch] DISPATCH/SECDISPATCH… Rifaat Shekh-Yusef
- [Secdispatch] Re: [dispatch] DISPATCH/SECDISPATCH… Michael Richardson
- [Secdispatch] Re: [dispatch] Re: DISPATCH/SECDISP… Jim Fenton
- [Secdispatch] Re: [dispatch] Re: DISPATCH/SECDISP… Eric Rescorla
- [Secdispatch] Re: [dispatch] Re: Re: DISPATCH/SEC… John C Klensin
- [Secdispatch] Re: [dispatch] Re: Re: DISPATCH/SEC… Rifaat Shekh-Yusef
- [Secdispatch] Re: [dispatch] Re: Re: DISPATCH/SEC… John C Klensin
- [Secdispatch] Re: [dispatch] Re: Re: DISPATCH/SEC… Eric Rescorla
- [Secdispatch] Re: [dispatch] Re: Re: DISPATCH/SEC… John C Klensin
- [Secdispatch] Re: [dispatch] Re: Re: DISPATCH/SEC… Rifaat Shekh-Yusef
- [Secdispatch] Re: [dispatch] Re: Re: DISPATCH/SEC… John C Klensin
- [Secdispatch] Re: [dispatch] Re: Re: DISPATCH/SEC… Rifaat Shekh-Yusef
- [Secdispatch] Re: [dispatch] Re: Re: DISPATCH/SEC… Eliot Lear
- [Secdispatch] Re: [dispatch] Re: Re: DISPATCH/SEC… John C Klensin
- [Secdispatch] Re: [dispatch] Re: Re: DISPATCH/SEC… Eliot Lear
- [Secdispatch] Re: [dispatch] Re: Re: DISPATCH/SEC… Rifaat Shekh-Yusef
- [Secdispatch] Re: [dispatch] DISPATCH/SECDISPATCH… Michael Richardson
- [Secdispatch] Re: DISPATCH/SECDISPATCH - Call for… Nico Williams
- [Secdispatch] Re: DISPATCH/SECDISPATCH - Call for… Eric Rescorla
- [Secdispatch] Re: DISPATCH/SECDISPATCH - Call for… Nico Williams
- [Secdispatch] Re: DISPATCH/SECDISPATCH - Call for… Rifaat Shekh-Yusef
- [Secdispatch] Re: DISPATCH/SECDISPATCH - Call for… Nico Williams
- [Secdispatch] Re: DISPATCH/SECDISPATCH - Call for… Rifaat Shekh-Yusef
- [Secdispatch] Re: DISPATCH/SECDISPATCH - Call for… Rifaat Shekh-Yusef
- [Secdispatch] Re: DISPATCH/SECDISPATCH - Call for… Nico Williams
- [Secdispatch] Re: DISPATCH/SECDISPATCH - Call for… Rifaat Shekh-Yusef
- [Secdispatch] Re: DISPATCH/SECDISPATCH - Call for… Nico Williams
- [Secdispatch] Re: DISPATCH/SECDISPATCH - Call for… Nico Williams
- [Secdispatch] Re: DISPATCH/SECDISPATCH - Call for… Demi Marie Obenour
- [Secdispatch] Re: DISPATCH/SECDISPATCH - Call for… Nico Williams
- [Secdispatch] Re: DISPATCH/SECDISPATCH - Call for… Nico Williams
- [Secdispatch] Y2K29 (was Re: DISPATCH/SECDISPATCH… Nico Williams
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… Arnaud Taddei
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… Nico Williams
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… Arnaud Taddei
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… Nico Williams
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… Nico Williams
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… Arnaud Taddei
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… Gianpaolo Angelo Scalone, Vodafone
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… Daniel Apon
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… Trey Darley
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… Arnaud Taddei
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… Paul Hoffman
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… Eric Rescorla
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… David Benjamin
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… Nico Williams
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… David Benjamin
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… Michael Richardson
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… Nico Williams
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… David Benjamin
- [Secdispatch] secure local IPC without HTTPS (was… Michael Richardson
- [Secdispatch] Re: secure local IPC without HTTPS … Nico Williams
- [Secdispatch] Re: secure local IPC without HTTPS … Demi Marie Obenour
- [Secdispatch] Re: secure local IPC without HTTPS … Nico Williams
- [Secdispatch] Re: secure local IPC without HTTPS … Paul Hoffman
- [Secdispatch] Re: [dispatch] Re: secure local IPC… Eric Rescorla
- [Secdispatch] Re: [dispatch] Re: secure local IPC… Nico Williams
- [Secdispatch] Re: [dispatch] secure local IPC wit… Jim Fenton
- [Secdispatch] Re: [dispatch] secure local IPC wit… Nico Williams
- [Secdispatch] Re: secure local IPC without HTTPS … Demi Marie Obenour
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… Nico Williams
- [Secdispatch] Re: Y2K29 (was Re: DISPATCH/SECDISP… Paul Hoffman
- [Secdispatch] Re: DISPATCH/SECDISPATCH - Call for… Andrew Campling