Re: [lamps] CAA update status
Russ Housley <housley@vigilsec.com> Fri, 21 July 2017 09:51 UTC
Return-Path: <housley@vigilsec.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 0303D129B40 for <spasm@ietfa.amsl.com>; Fri, 21 Jul 2017 02:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham 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 jnqCwFzYZwDh for <spasm@ietfa.amsl.com>; Fri, 21 Jul 2017 02:50:58 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E698712EE45 for <spasm@ietf.org>; Fri, 21 Jul 2017 02:50:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 317AA30050A for <spasm@ietf.org>; Fri, 21 Jul 2017 05:50:57 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id xLphpKT2Kup2 for <spasm@ietf.org>; Fri, 21 Jul 2017 05:50:56 -0400 (EDT)
Received: from [5.5.33.183] (vpn.snozzages.com [204.42.252.17]) by mail.smeinc.net (Postfix) with ESMTPSA id 88CD4300429; Fri, 21 Jul 2017 05:50:55 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <7c3d47dd-ddfe-7afe-3a63-f21fd1c614d6@eff.org>
Date: Fri, 21 Jul 2017 05:51:02 -0400
Cc: SPASM <spasm@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <70F123F5-4995-4631-99A6-D9145C86C7FD@vigilsec.com>
References: <7c3d47dd-ddfe-7afe-3a63-f21fd1c614d6@eff.org>
To: Jacob Hoffman-Andrews <jsha@eff.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/aR_klyfuTm54l8ltpE_Yu9EqPeA>
Subject: Re: [lamps] CAA update status
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: Fri, 21 Jul 2017 09:51:00 -0000
One of the Area Directors needs to take that action. Russ > On Jul 21, 2017, at 3:50 AM, Jacob Hoffman-Andrews <jsha@eff.org> wrote: > > I missed dialing into the LAMPS session at IETF 99, but it sounds like > erratum 5065 (https://www.rfc-editor.org/errata/eid5065) was discussed > and there was general consensus on moving it forward. What still needs > to happen in order for it to get moved to "Held for Document Update" > status so the CA/Browser Forum can hold a ballot on it?
- [lamps] CAA update status Jacob Hoffman-Andrews
- Re: [lamps] CAA update status Russ Housley