Re: [Secdispatch] Call for agenda items at IETF 104

"R. Miles McCain" <miles@rmrm.io> Tue, 26 February 2019 23:18 UTC

Return-Path: <miles@rmrm.io>
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 969291286E7 for <secdispatch@ietfa.amsl.com>; Tue, 26 Feb 2019 15:18:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rmrm.io
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qI2jUlVjOEZ1 for <secdispatch@ietfa.amsl.com>; Tue, 26 Feb 2019 15:18:41 -0800 (PST)
Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3D11126D00 for <secdispatch@ietf.org>; Tue, 26 Feb 2019 15:18:40 -0800 (PST)
Received: by mail-lf1-x134.google.com with SMTP id x206so2989969lff.3 for <secdispatch@ietf.org>; Tue, 26 Feb 2019 15:18:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rmrm.io; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=TJ6kEC7UsnwOal1x7WZKm0kM6R7QdQ/i2myzJePHbd0=; b=Om8PWkPs6QRoptyuK2nBj6ATylqX9jKUrq9p6bH/P/SqxiR4MZIaat/WeQIVSdzLJx 6TeU6OaoBFn1t+KPHaefX7NCl8KW15PWMd/BSRJLWSojig1xf9jrBzT8Q2XY0xIVUlOE qUYbNMai9bVs7P3/wxsb+2R2Ew2PgSdnCem9lIAceDokxGLDTIWl/QtS9QKu3FCgSUta ss3gErhV2qUz32TtDKdVfRAwSW8+SzQ3AFqv2GyLBOFPyC1hy/zROiehgrK6HG2q8OUB cs2+VGRxM6n4D/66odRqADLRiGvOFplkzZZfL9NZ18MzxPhmnPjsteGIx0xUicC8yYlB Jo7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=TJ6kEC7UsnwOal1x7WZKm0kM6R7QdQ/i2myzJePHbd0=; b=G/Z+Vt0ootJtmxy7IDSY2BCiV4wmnrCNEbJjJQRfaIhgfpXZuE18tH+wBDesDsYRUg IzZfrNT8FbomfN2CMBFnqZ+9W/3hfXf+bxVfAK/FvQ11YNhJg8+upxebQhRm2uYDTU2R DHELis0oxPcTbzZ7oQGCkmkBdh6k/ktfchZ9dSzToc9YZQr0Di6WqQXksbRIGKENUWrE DU6cRAHFmjKsBc76Ns2lFhz/bzEY3wz22jqIa8nJL/t9o9PjbgHtYm+lAMmk+cVfsaqk hldrwfW3++Rb2e8LxcgcFFdUKcOpK93dEGl9vyCmd7iNIsbDHI6R6xE89n82aaUZRTfA Z/Zg==
X-Gm-Message-State: AHQUAuaJdWXUc8tVuUBHPfPseKTJIMmCgIenyvO9cec5yw6pVKfsenLm 6XJ1Y6V/GYvpk1MN3v5Wl6zjuXcqtAcOw66065wT7w==
X-Google-Smtp-Source: AHgI3IbLTXqQTRIveLxdI5Vmps/YVO0z5t0vSZPGC0YnankijdGxSFLzIAEZW9FO9J5uh+gUeCJpX6tSMVFt2T0ovks=
X-Received: by 2002:a19:5003:: with SMTP id e3mr13698523lfb.160.1551223118631; Tue, 26 Feb 2019 15:18:38 -0800 (PST)
MIME-Version: 1.0
References: <359EC4B99E040048A7131E0F4E113AFC01857D9E92@marathon>
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFC01857D9E92@marathon>
From: "R. Miles McCain" <miles@rmrm.io>
Date: Tue, 26 Feb 2019 18:18:27 -0500
Message-ID: <CAC5Wr35fA_dtj-GwpHBeHc1GWXyEBPxmhppYpX7NLi0hTMCi0A@mail.gmail.com>
To: Roman Danyliw <rdd@cert.org>, secdispatch@ietf.org
Cc: Nat Welch <nat@natwelch.com>, Micah Lee <micah.lee@theintercept.com>
Content-Type: multipart/alternative; boundary="000000000000f43f9f0582d446a4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/3C0fhVxGoC3KUi6zKtinceJzqW8>
Subject: Re: [Secdispatch] Call for agenda items at IETF 104
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2019 23:18:45 -0000

Hello,

If any additional time is available, I would like to request time to
discuss draft-mccain-keylist (<
https://datatracker.ietf.org/doc/draft-mccain-keylist/>) during the
SecDispatch meeting at IETF 104.

Most discussion so far has taken place in the OpenPGP mailing list (see <
https://mailarchive.ietf.org/arch/browse/openpgp/?gbt=1&index=tFzcDPVHylKrLmZY_2Vcw0bdjog>),
and 'development' of the draft has taken place on GitHub (<
https://github.com/firstlookmedia/keylist-rfc>). (Note that because of the
recent constructive feedback from the OpenPGP mailing list, my co-authors
and I plan to release an updated version of the draft in the coming days.)

The spec itself has been implemented by GPGSync, an open-source tool
currently in use by First Look Media (parent of *The Intercept*) and the
Freedom of the Press Foundation. Other background materials are available
at <https://tech.firstlook.media/gpg-sync-v0-3> and <
https://tech.firstlook.media/keylist-rfc-explainer>.

My co-authors and I imagine that this work could *potentially* be suitable
for the OpenPGP working group, but we also realize that our draft has less
to do with OpenPGP itself and more to do with key management, and are
therefore open to working with whatever group is appropriate. We hope to be
guided by the feedback from a working group, but my co-authors and I
nonetheless anticipate that the majority of work done to advance the draft
will be our own. (That being said, we welcome and encourage anyone to
submit a pull request to the draft's GitHub repository should they like to
make edits themselves.)

It is also worth mentioning that we will be participating in the meeting
remotely.

Thank you for your consideration,
Miles McCain



On Tue, Feb 26, 2019 at 11:15 AM Roman Danyliw <rdd@cert.org> wrote:

> Hello!
>
> The draft agenda for IETF 104 [1] has SecDispatch scheduled for Monday,
> March 25 from 1350 - 1550.  A reminder, if you would like time on the
> agenda, please send your request to the mailing list.
>
> Regards,
> Roman and Richard
>
> [1] https://datatracker.ietf.org/meeting/agenda/
>
> > -----Original Message-----
> > From: Roman Danyliw
> > Sent: Monday, February 11, 2019 12:40 PM
> > To: secdispatch@ietf.org
> > Subject: Call for agenda items at IETF 104
> >
> > Hello!
> >
> > SecDispatch will be meeting at IETF 104 (at a time yet to be
> determined).  If
> > you would like time on the agenda, send your request to the mailing list.
> > Helpful items to include in your request (if known/applicable) are:
> >
> > (1) pointers to a draft(s)
> > (2) pointers to ongoing/prior discussions
> > (3) pointers to implementations
> > (4) pointers to any other background materials
> > (5) summarizing prior engagement with existing WGs
> > (6) summarizing who would want to advance this work
> > (7) desired next steps
> >
> > If needed, precedence will be given to documents that have demonstrated
> > interest in the form of active drafts and list discussion.
> >
> > If you have questions, please reach out to the co-chairs.
> >
> > Regards,
> > Roman and Richard
>
> _______________________________________________
> Secdispatch mailing list
> Secdispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/secdispatch
>