IETF Logo Mail Archive

Re: [lamps] S/MIME fix

Phillip Hallam-Baker <phill@hallambaker.com> Wed, 16 May 2018 20:55 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AB9312DA21 for <spasm@ietfa.amsl.com>; Wed, 16 May 2018 13:55:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Nj-RLg8QL2he for <spasm@ietfa.amsl.com>; Wed, 16 May 2018 13:55:35 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (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 EA92912E034 for <SPASM@ietf.org>; Wed, 16 May 2018 13:55:22 -0700 (PDT)
Received: by mail-oi0-x233.google.com with SMTP id e80-v6so2003195oig.11 for <SPASM@ietf.org>; Wed, 16 May 2018 13:55:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=oQjKnxl/FS5ceuuPaPr6B2Z/gX2D+LsoWePWx93KcIQ=; b=gkp8YulOGkNkqJ8zo6da+7IHw9BnP+DC8ptUXoVziUwskuVJcYqUoKsNw9Eu0ZODnG pOn7yMhjxqNVV208PjsYDYhBMiR0snKK60b8aCH5xVL2eBdfcsBjjOvv4bQbI0vsC+bn kKCR06IuHhUv6ufrxdnjiLir8cqnmc/zhEBHAUXy50fKCwFArO/s1dLf3QEbc9hw7vLh MQZHN8Nz2W9iGODwWoITrqAA8zY8whdq6zaUdMdYzEXMtGfK8yrbPEIwEwymh81bHPjY 79EnozFPI1qTIvfl+F35cpwuGFe5yb7OjLUbaLEB/oQ2knDX3zT3ZhAQ3O9TFgEkKhID bxzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=oQjKnxl/FS5ceuuPaPr6B2Z/gX2D+LsoWePWx93KcIQ=; b=ciQ2YUacqbuA5c/Z3h3C0DQycQP4clQ76ikwqQz7G+LHeX2VgcPS1p45LWmRTCezIJ raqcAK+ah2iS3TkObB29D3Lroc7wwi5ClgrSohRyzqDpaMQBflFZb5h6WDy0TVUWhkY3 SpFb+1Tbelri0ihF93J0mnUM9wuQKAP6mCOFNX+kgLQ4yhEdfOrU7NjJc9R7I2Erh5Jh 4+5B3lm9J99IZ46wx2L7BXIOtV1WdJnJ+Zpbz7cHRXHIf6HWRFzEB7LS5I332/WYA+4q MH7/sQFywvtVQNe75qrhNs5ho0wVaSojpgaxs1STBskYW1tBVDuE4TcDQWu6bUXqprc3 ujWA==
X-Gm-Message-State: ALKqPwd8sBZjTI0QcyZsLkRXFTu8k1wUZKGkkAgtXKdeAHjbiUSf0AvH YnydWqQFVdSDzyTuDlWEmObyGWWBU6HkHBVJhVU=
X-Google-Smtp-Source: AB8JxZqU6IYIE7O/Uld4R4tbG3A54Py5OhHUlBNF6O1SNX0Pk1mx1NyFvvWhVi+WU0Wd3oQOXedIa2CYCJz5OrM8K1Q=
X-Received: by 2002:aca:ce42:: with SMTP id e63-v6mr1782126oig.34.1526504122283; Wed, 16 May 2018 13:55:22 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 2002:a9d:23:0:0:0:0:0 with HTTP; Wed, 16 May 2018 13:55:21 -0700 (PDT)
In-Reply-To: <BN6PR14MB1106A2890EE8B9243B4EA08C83920@BN6PR14MB1106.namprd14.prod.outlook.com>
References: <CAMm+Lwj=VTBHYxH-iOaqEUHxALpBfSXWG3p0+xxUnY+o4CmGvA@mail.gmail.com> <BN6PR14MB1106A2890EE8B9243B4EA08C83920@BN6PR14MB1106.namprd14.prod.outlook.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 16 May 2018 16:55:21 -0400
X-Google-Sender-Auth: 9uhBNfw60-GgVZBRURwzRf29NuI
Message-ID: <CAMm+LwhuBoQ1VHQy-=E2FODYq4Fnzs8e24Yqyfg4akwQTsqc=w@mail.gmail.com>
To: Tim Hollebeek <tim.hollebeek@digicert.com>
Cc: SPASM <SPASM@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f4fcef056c58efc5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/-C5sfIBEXV95vM88nee-sk58WG4>
Subject: Re: [lamps] S/MIME fix
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2018 20:55:42 -0000

Absolutely, it is not either/or.

What I would like to see us do however is come together at some point and
identify ALL the issues that are barriers to ubiquitous deployment of
S/MIME and come up with a comprehensive scheme.

What I think we are going to need is a standard that allows folk to know if
their infrastructure supports S/MIME-NG.


On Wed, May 16, 2018 at 3:59 PM, Tim Hollebeek <tim.hollebeek@digicert.com>
wrote:

> It’s not necessarily an either / or thing.  After July 3, we’ll have a
> S/MIME group at CABF and from talking privately to some people it sounds
> like we will have good participation.  But that will mostly be a policy
> discussion.
>
>
>
> It would be nice to have IETF RFCs to point to for all the persnickety
> technical details about how things like ACME and CAA work with email.  I’m
> sure there’s plenty of nuances we haven’t thought of yet.  There certainly
> were for the web.
>
>
>
> Draining the email swamp is actually very high on my priority list for
> this year.
>
>
>
> -Tim
>
>
>
> I am not necessarily thinking of this as a LAMPS thing because we also
> need to get CAs, probably CABForum involved and maybe the OpenPGP folk.
>

v2.23.0 | Report a Bug | By Email