Re: [secdir] Assignments

Phillip Hallam-Baker <ietf@hallambaker.com> Thu, 02 May 2019 14:46 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F113512019C for <secdir@ietfa.amsl.com>; Thu, 2 May 2019 07:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.647
X-Spam-Level:
X-Spam-Status: No, score=-1.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 0xGyA-qHEmev for <secdir@ietfa.amsl.com>; Thu, 2 May 2019 07:46:23 -0700 (PDT)
Received: from mail-ot1-f48.google.com (mail-ot1-f48.google.com [209.85.210.48]) (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 D4E1B12013E for <secdir@ietf.org>; Thu, 2 May 2019 07:46:22 -0700 (PDT)
Received: by mail-ot1-f48.google.com with SMTP id b1so2306401otp.5 for <secdir@ietf.org>; Thu, 02 May 2019 07:46:22 -0700 (PDT)
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=QgpzW1ZLOumVwKr7JP4O+7IuJzgqoKZYUmR/q4xvC7k=; b=T9L7gNuWcPuvQcd8GUVaV0k4vga8dlL1z/y/kDKitxevKkl6HT7zRSHKisD7uHzsDH wx0f4R81JCrxYlUFW10wdaFMwJrjNmRYXL7mukh1c58teF3T0nCh0hZabrN/O5dB60np Nh+3KTQYtABXr/BwYKE+emZx3mBr/ZP+uPW9LWh5JOCP0uVl8mNdfSp92LI3SyX2eg1n miB8Cs8mzi6eU/Exbc8igYAUEQfEYOUt5Px8XnBuq47L5IR7B69CmKwlY83UgqOptokf kJEsRva5Bbt4S6mum3priA5L0McDGdAMnxGYPwxTvPe9o5IAxxvEqGKc39MsDpdRCcyi KMdA==
X-Gm-Message-State: APjAAAVVv8zQpcf7QxJs3QS01TLuBHNMiT4jwZB6gY8JrvfN5vzrBhUb Z2CRGy/deTslkxi1WBJ5NnxzG5kk1gBSZGcjg68=
X-Google-Smtp-Source: APXvYqxkgEogSDshHPdrlEOX4dHubBSfJABCxINDs4aTBaTMxKDCaJ2LbpNBoC265LTlr1jSbOvnQ6I5huzTZoDg1sU=
X-Received: by 2002:a9d:5a11:: with SMTP id v17mr2841060oth.150.1556808382162; Thu, 02 May 2019 07:46:22 -0700 (PDT)
MIME-Version: 1.0
References: <155618781878.23454.9844389863110194782.idtracker@ietfa.amsl.com> <CAMm+LwgOYJW=mM7FH05NOrhjZM8=atfo1jS6VjnxNjYtAYZ4Ww@mail.gmail.com> <23750.56385.220502.134039@fireball.acr.fi>
In-Reply-To: <23750.56385.220502.134039@fireball.acr.fi>
From: Phillip Hallam-Baker <ietf@hallambaker.com>
Date: Thu, 2 May 2019 10:46:11 -0400
Message-ID: <CAMm+Lwhr3k3Fb2obE=k7uzyaH_=wtJPNXRchFn4JEGhHSVwJZA@mail.gmail.com>
To: Tero Kivinen <kivinen@iki.fi>
Cc: secdir-secretary@mit.edu, secdir@ietf.org
Content-Type: multipart/alternative; boundary="0000000000009a2d680587e8b206"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/NavqOKSsU0wxp5DQ6N-nv4ZYmT8>
Subject: Re: [secdir] Assignments
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2019 14:46:25 -0000

On Mon, Apr 29, 2019 at 7:13 AM Tero Kivinen <kivinen@iki.fi> wrote:

> Phillip Hallam-Baker writes:
> > Ooops. Just noticed that these have not been going into my action items
> folder
> > and I missed one. My filter must have been relying on a feature that
> changed.
>
> I switched to use emails sent from datatracker two and half years ago,
> i.e., end of 2016. Reply to, To and Subject should have been same.
>
> From address field did change from kivinen@iki.fi to noreply@ietf.org
> in the beginning of March, because of some datatracker changes, so
> that is the one that most likely caused the issue. Anyways it is
> always better to use something else than From address for filtering as
> the secdir secretary might change :-)
>

Yes, that looks like what happened. My fault of course.

But what I always try to look for is what an event might tell us about the
functioning of the system as a whole. Fixing things for ourselves is useful
but the end goal is to improve the Internet for users as a whole.

I agree simply doing S/MIME might not be enough. We might well need to
engineer a new protocol for the purpose and deploy that in niche intranet
environments before attempting internet deployment.

For any work flow process to be useful, it would probably have to handle
50% of my tasks at the least. Which is obviously likely to be true of my
employer workflow system but not the IETF data tracker except for people
like me who have no employer right now.




> The reply-to address of secdir-secretary@mit.edu should stay same.
>
> > Not really a tools team issue or critical. But it is a systemic
> > problem with using SMTP mail for workflow.
>
> You can always see your review requests also in the datatracker by
> going to the
>
> https://datatracker.ietf.org/accounts/review/
>
> page, and also the datatracker should send you automatic email when
> one is assigned to you in addition to my summary...
>
> One good thing about mail workflow is that I do get all the
> notifications in the same place, I hate the cases where I need to go
> and check through few dozen different web pages to see if there is
> anything new there for me to do...
>
> > We have traditionally considered the killer app for S/MIME to be
> > confidentiality. What if it was authentication and access control?
> Signing
> > meeting requests, calendar entries, task items allows people to add
> things to
> > my work queue.
>
> That would be nice, but the problem again is that you want to
> configure your systems to act on certain requests differently. Whether
> it is S/MIME authenticated does not really help there, you still do
> not want to accept random S/MIME authenticated request to add new
> entries to your calendar, so you are still left with whitelist of
> people who can add items to your calendar, and when things change then
> those will break...
>
> > Trying to retrofit might be a case of trying to balance too many
> > plates on the stack though.
>
> Adding generic code to the datatracker that signs emails with S/MIME,
> would actually be quite good enhancement, and I did make a new ticket
> #2716 about this...
> --
> kivinen@iki.fi
>