Re: [lamps] WG Last Call for rfc6844bis

"Salz, Rich" <rsalz@akamai.com> Mon, 15 October 2018 16:18 UTC

Return-Path: <rsalz@akamai.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 649C4130EB7 for <spasm@ietfa.amsl.com>; Mon, 15 Oct 2018 09:18:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.051
X-Spam-Level:
X-Spam-Status: No, score=-3.051 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.351, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, KHOP_DYNAMIC=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=akamai.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 PqJ2xE1s-hUm for <spasm@ietfa.amsl.com>; Mon, 15 Oct 2018 09:18:52 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCE33130DC4 for <spasm@ietf.org>; Mon, 15 Oct 2018 09:18:52 -0700 (PDT)
Received: from pps.filterd (m0050093.ppops.net [127.0.0.1]) by m0050093.ppops.net-00190b01. (8.16.0.23/8.16.0.23) with SMTP id w9FGD3iQ030651; Mon, 15 Oct 2018 17:18:51 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=ZwlH/uOsPnlYMGWacPrOunOVZ4cv1oUY587SG6/ZG/4=; b=Zor5VeThIpB26nK8BVOMNUowP9i6z0gxvxQk7crlOo/JL906GCQSB9JgxFR36gctHUiL 7oCo92OQzIjAASbKu3UQV939SNOSBjhV51HQ10eYqqB6PU/U6t/9eG0/3mmwP/CEFTuX i9EEU6G2xdAOhc7sQ+vaeUUGeWdVZI8anYO4svgaOimau/raaseDu2coIDHOETO9pRMy T88cfMqBtS6jlMWk7DHm620Y/z8qnsvbAL0YcPlOYKISBuv1bJg0wd2A3HcLZPhYv924 eqcS0e2SRbaaFuvvHTfKMxVzSC17dTHGLWRudUqVQ+T36na7zqZlk+ptzQyXaCd/lG6D UA==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18]) by m0050093.ppops.net-00190b01. with ESMTP id 2n3dr6x45w-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 15 Oct 2018 17:18:51 +0100
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w9FG5eIq027414; Mon, 15 Oct 2018 12:18:50 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.33]) by prod-mail-ppoint1.akamai.com with ESMTP id 2n3c1ugx2j-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 15 Oct 2018 12:18:50 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb2.msg.corp.akamai.com (172.27.123.102) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Mon, 15 Oct 2018 12:18:49 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1365.000; Mon, 15 Oct 2018 12:18:49 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Sean Turner <sean@sn3rd.com>, Tim Hollebeek <tim.hollebeek@digicert.com>
CC: SPASM <spasm@ietf.org>, Russ Housley <housley@vigilsec.com>
Thread-Topic: [lamps] WG Last Call for rfc6844bis
Thread-Index: AQHUYYx4wqAyciY7xUefcXJ6qShYqaUasEwAgAYMx4D//8VVAA==
Date: Mon, 15 Oct 2018 16:18:48 +0000
Message-ID: <CFD82416-765E-4DFC-BD62-0918A7452CC2@akamai.com>
References: <F72DABEA-234C-4644-914A-81FBCC86D11B@vigilsec.com> <BN6PR14MB11063B4401B3C6BEBAF7A68D83E10@BN6PR14MB1106.namprd14.prod.outlook.com> <3C360C1C-E112-4044-BC2A-AF9BFFD3673C@sn3rd.com>
In-Reply-To: <3C360C1C-E112-4044-BC2A-AF9BFFD3673C@sn3rd.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.11.0.180909
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.39.93]
Content-Type: text/plain; charset="utf-8"
Content-ID: <5BB72F6D122A9D4F8481106027F09F04@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-15_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=819 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810150143
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-15_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=809 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810150144
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/aayWpZ1Mex7_grgA1WyBuBnaLd0>
Subject: Re: [lamps] WG Last Call for rfc6844bis
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 15 Oct 2018 16:18:54 -0000

>    My thinking is that if the fixes to CAA are done we should not wait to publish those while we figure out what to do wither these “new” things.  I.e., ship this draft if it is ready and do the “new” things in a separate draft.
  
Strongly agree.

And I am glad to hear that CA/Browser Forum is interested in helping write RFC's :)

Thanks for raising the issue, Tim.