[lamps] CAA update status
Jacob Hoffman-Andrews <jsha@eff.org> Fri, 21 July 2017 07:50 UTC
Return-Path: <jsha@eff.org>
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 9886C1316E2 for <spasm@ietfa.amsl.com>; Fri, 21 Jul 2017 00:50:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.002
X-Spam-Level:
X-Spam-Status: No, score=-7.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eff.org
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 Z2yEsLNsaE2d for <spasm@ietfa.amsl.com>; Fri, 21 Jul 2017 00:50:02 -0700 (PDT)
Received: from mail2.eff.org (mail2.eff.org [173.239.79.204]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3ED8012714F for <spasm@ietf.org>; Fri, 21 Jul 2017 00:50:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=eff.org; s=mail2; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date:Message-ID:To:Subject:From; bh=PVbejKo8dWx/jDCq8dFOGTOiVo87W4tQ9kIfykrBmeA=; b=ZzbKwVD54NQ/Sg3NANlLrW0HC8q/HveCPxcirysuPRFeFLDq+4IuEwtRuK9/9Mhg6R6sIyIUkT7qxVuY2Xj9/q6yuPR8QSxqfMD1gOv7sNH5As/NGzn1+I/hKjp3rMcLmOZ8ODxLGko3HNybjEsN/6Ep7N3V8J3xwDlIuXRxPrg=;
Received: ; Fri, 21 Jul 2017 00:50:00 -0700
From: Jacob Hoffman-Andrews <jsha@eff.org>
To: SPASM <spasm@ietf.org>
Message-ID: <7c3d47dd-ddfe-7afe-3a63-f21fd1c614d6@eff.org>
Date: Fri, 21 Jul 2017 00:50:01 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/QD5vVCa71-LRWeiYXYuuZCAYKxU>
Subject: [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 07:50:04 -0000
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