IETF Logo Mail Archive

Re: [lamps] S/MIME fix

Ryan Sleevi <ryan-ietf@sleevi.com> Thu, 17 May 2018 18:54 UTC

Return-Path: <ryan-ietf@sleevi.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 A46B1127058 for <spasm@ietfa.amsl.com>; Thu, 17 May 2018 11:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sleevi.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 F7CaJsRL6Zbl for <spasm@ietfa.amsl.com>; Thu, 17 May 2018 11:53:57 -0700 (PDT)
Received: from homiemail-a49.g.dreamhost.com (homie-sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E66D126C25 for <SPASM@ietf.org>; Thu, 17 May 2018 11:53:57 -0700 (PDT)
Received: from homiemail-a49.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a49.g.dreamhost.com (Postfix) with ESMTP id C6C54680079E2 for <SPASM@ietf.org>; Thu, 17 May 2018 11:53:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sleevi.com; h=mime-version :in-reply-to:references:from:date:message-id:subject:to:cc :content-type; s=sleevi.com; bh=rk2rUoQINpSIw0XADp6CtkxZ9ZY=; b= p1g2t1///vOJgUxdC9KIRKlBgGMlp6WHNqegp0WBI9Eh+iTF0pBmRX+3t+/sRzsh Zz3iybfTsm3KnmD4vOXBrAuBv+y6PF2pLASwNOpvA1SsIeQwlrKTbzRqxFjgQJdB PVNccuRt1KSeI3Ar9PdJim37LMDVmU3qM/BdsVFcEe8=
Received: from mail-it0-f52.google.com (mail-it0-f52.google.com [209.85.214.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: ryan@sleevi.com) by homiemail-a49.g.dreamhost.com (Postfix) with ESMTPSA id B2860680079D8 for <SPASM@ietf.org>; Thu, 17 May 2018 11:53:55 -0700 (PDT)
Received: by mail-it0-f52.google.com with SMTP id y189-v6so10145316itb.2 for <SPASM@ietf.org>; Thu, 17 May 2018 11:53:55 -0700 (PDT)
X-Gm-Message-State: ALKqPwe4ySxJGN3JUUiI7H85z8SfYseq1sFuzMJfO3pOj6nkpM+VCzDQ lk9/Wg/hhlzsQe/IlmXCLkRqqcH2+5FCkk8W49E=
X-Google-Smtp-Source: AB8JxZqUAixyP1LYVj9f5w9KVePeaCydcc8ZR4Dxey1uVkcUbezB51Z8fyeiDRb6ojN18A6TyelpCrB6nB+iD/jCM3c=
X-Received: by 2002:a24:9d44:: with SMTP id f65-v6mr3831822itd.119.1526583235083; Thu, 17 May 2018 11:53:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a02:985a:0:0:0:0:0 with HTTP; Thu, 17 May 2018 11:53:54 -0700 (PDT)
In-Reply-To: <c6424d23-493c-8831-41c1-2ebcc808b7c9@nostrum.com>
References: <CAMm+Lwj=VTBHYxH-iOaqEUHxALpBfSXWG3p0+xxUnY+o4CmGvA@mail.gmail.com> <BN6PR14MB1106A2890EE8B9243B4EA08C83920@BN6PR14MB1106.namprd14.prod.outlook.com> <CAMm+LwhuBoQ1VHQy-=E2FODYq4Fnzs8e24Yqyfg4akwQTsqc=w@mail.gmail.com> <1e8468d7-da6c-62f1-e24b-1ee03df22606@cs.tcd.ie> <e678276f-79c2-ec3c-7df5-f70794740f77@nostrum.com> <AB332E06-E1F5-4E82-9EF8-B49846865DAC@vigilsec.com> <f623981f-a379-4a94-0fda-a765a8318841@nostrum.com> <CAMm+LwjFqv4JiRLTBAcZB+EvBC0nH53jgBaCfFfaGTa5QSbrZw@mail.gmail.com> <c6424d23-493c-8831-41c1-2ebcc808b7c9@nostrum.com>
From: Ryan Sleevi <ryan-ietf@sleevi.com>
Date: Thu, 17 May 2018 14:53:54 -0400
X-Gmail-Original-Message-ID: <CAErg=HF9hMZwPsZUAK81WigdmGLTGaRK7bJ=BrjnHhjBWvYNLg@mail.gmail.com>
Message-ID: <CAErg=HF9hMZwPsZUAK81WigdmGLTGaRK7bJ=BrjnHhjBWvYNLg@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, SPASM <SPASM@ietf.org>, Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary="0000000000007293c8056c6b5b15"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/ajjNHD5GqROuFx0VeOGHjwhhoD8>
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: Thu, 17 May 2018 18:54:10 -0000

I'm having trouble understanding how the current discussion relates to the
LAMPS work. It sounds from Phil's initial message, is that this isn't
related to LAMPS. There's been suggestions that this might be the
CA/Browser Forum (despite the CA/Browser Forum not even having a proposed
charter to clean this up), that this might be a W3C/WHATWG issue (despite
the browsers explicitly rejecting some of these proposals), or perhaps
somewhere else.

For my own understanding, is there a concrete proposal for either a
document or work LAMPS should take on? Otherwise, would it be better to
have this discussion elsewhere?

On Thu, May 17, 2018 at 11:51 AM, Adam Roach <adam@nostrum.com> wrote:

> On 5/17/18 10:46 AM, Phillip Hallam-Baker wrote:
>
> I am composing this in Gmail right now. And there is my outlook client in
> the window underneath. ​The Web browser is not just a full fledged email
> client, it is the client of choice.
>
>
> I don't want to get too far down the rabbit hole of semantics here, but
> claiming that a browser is an email client because it can run Gmail is
> fully congruent with claiming your operating system is an email client
> because it can run Outlook.
>
> More to the point: you know what I meant.
>
> /a
>
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm
>
>

v2.23.0 | Report a Bug | By Email