Re: [lamps] The LAMPS WG has placed draft-hoffman-andrews-caa-simplification in state "Candidate for WG Adoption"

Corey Bonnell <CBonnell@trustwave.com> Tue, 27 February 2018 20:20 UTC

Return-Path: <CBonnell@trustwave.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 04557126FDC; Tue, 27 Feb 2018 12:20:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 wxJt7TajeLX5; Tue, 27 Feb 2018 12:20:26 -0800 (PST)
Received: from seg-node-elk-02.trustwave.com (seg-node-elk-02.trustwave.com [204.13.202.188]) (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 7F3FE1201FA; Tue, 27 Feb 2018 12:20:26 -0800 (PST)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (Not Verified[216.32.180.54]) by seg-node-elk-02.trustwave.com with Trustwave SEG (v8, 0, 6, 10676) (using TLS: TLSv1.2, AES256-SHA256) id <B5a95bd860001>; Tue, 27 Feb 2018 14:20:23 -0600
Received: from CY4PR07MB3575.namprd07.prod.outlook.com (10.171.253.14) by CY4PR07MB3208.namprd07.prod.outlook.com (10.172.115.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.527.15; Tue, 27 Feb 2018 20:20:19 +0000
Received: from CY4PR07MB3575.namprd07.prod.outlook.com ([fe80::9993:ac58:1046:e047]) by CY4PR07MB3575.namprd07.prod.outlook.com ([fe80::9993:ac58:1046:e047%13]) with mapi id 15.20.0527.021; Tue, 27 Feb 2018 20:20:19 +0000
From: Corey Bonnell <CBonnell@trustwave.com>
To: Jacob Hoffman-Andrews <jsha@eff.org>, Tim Hollebeek <tim.hollebeek@digicert.com>, IETF Secretariat <ietf-secretariat-reply@ietf.org>, "spasm@ietf.org" <spasm@ietf.org>, "lamps-chairs@ietf.org" <lamps-chairs@ietf.org>, "draft-hoffman-andrews-caa-simplification@ietf.org" <draft-hoffman-andrews-caa-simplification@ietf.org>
Thread-Topic: [lamps] The LAMPS WG has placed draft-hoffman-andrews-caa-simplification in state "Candidate for WG Adoption"
Thread-Index: AQHTraVoHn8WdZxpn0O7x51qlIqxJKO2xeCAgABILwCAAVOZAA==
Date: Tue, 27 Feb 2018 20:20:19 +0000
Message-ID: <7D9F4BE0-4760-4191-846F-3DA8511C9F03@trustwave.com>
References: <151950039671.13803.5548300357689455000.idtracker@ietfa.amsl.com> <MWHPR14MB1376ABAA3A2ADE2383B90BF283C10@MWHPR14MB1376.namprd14.prod.outlook.com> <bb6b0378-2d5d-f0f1-4070-b8c506d4ec86@eff.org>
In-Reply-To: <bb6b0378-2d5d-f0f1-4070-b8c506d4ec86@eff.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=CBonnell@trustwave.com;
x-originating-ip: [50.243.167.1]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR07MB3208; 7:4CANpNlwlJz5UbPtcvmFyHimNRXLCjRkCw+hvpM+Pwgq+5sirzY9JwrWYm5FGDaM9khx0wZhD/ZQaHwnjzecAJVOdZIRC9+WSnCcoLU8FBV7IFpCBvmWstvBbZDSMw6MaQWzK80qLRrbcqRbTnnpPcnpUH3Dx5ibFr85EAMrkb7Lm0M0qW2NKr5vB479cB2qy7fjBsT3hBYxwiZjFdHtJq1opCikgUKWXUmF6Q5iyb/EtZ0KsZAwA8a0Q3KNPBHg
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: f87d75d2-1997-4b17-367c-08d57e1f85a0
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:CY4PR07MB3208;
x-ms-traffictypediagnostic: CY4PR07MB3208:
x-microsoft-antispam-prvs: <CY4PR07MB320842355220B37B7EBB44FACFC00@CY4PR07MB3208.namprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(232896897485771);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(5005006)(8121501046)(10201501046)(93006095)(93001095)(3231220)(944501161)(3002001)(6041288)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123564045)(6072148)(201708071742011); SRVR:CY4PR07MB3208; BCL:0; PCL:0; RULEID:; SRVR:CY4PR07MB3208;
x-forefront-prvs: 05961EBAFC
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39860400002)(346002)(376002)(39380400002)(366004)(189003)(199004)(2950100002)(6116002)(2906002)(82746002)(80792005)(99286004)(105586002)(81166006)(81156014)(33656002)(229853002)(8936002)(305945005)(478600001)(97736004)(3660700001)(6512007)(6306002)(3846002)(6246003)(2900100001)(3280700002)(7736002)(53936002)(8676002)(6436002)(83716003)(6506007)(26005)(186003)(53546011)(76176011)(66066001)(36756003)(102836004)(2201001)(86362001)(6486002)(106356001)(14454004)(5250100002)(25786009)(316002)(966005)(2501003)(110136005)(72206003)(68736007)(5660300001)(19400905002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR07MB3208; H:CY4PR07MB3575.namprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: trustwave.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: /HUZiiv3CuBfoKyE7F/WAGIZnHKJnzCHp1HWpeNPAx01OZKAngQt8fRFXK90xRs1p2IVZ8ZgF0l/OUPURqqsA7sKl+YvXlTsJcYaOYYxqlUcbjkRsVStgENyvD1f1IDmR8rmNoo8wS/n8pF7ps+JkDlcQ4JRLKm/7a//XjzzxYg=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <BA23157B2FB08D478B2AE68CFE419C56@namprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: trustwave.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f87d75d2-1997-4b17-367c-08d57e1f85a0
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Feb 2018 20:20:19.1717 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cb1dab68-a067-4b6b-ae7e-c012e8c33f6a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR07MB3208
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/c6pHCdZ_Oh0r4JFE6-MT3WZ9xPg>
Subject: Re: [lamps] The LAMPS WG has placed draft-hoffman-andrews-caa-simplification in state "Candidate for WG Adoption"
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: Tue, 27 Feb 2018 20:20:29 -0000

Hi Jacob,
I have a few minor changes I'd like to make to the grammar I proposed a few months ago, namely to add support for whitespace surrounding the equals sign in parameter tag/value pairs as well as to allow for hyphens to appear in parameter tags (this is necessary to support the parameter names proposed in https://tools.ietf.org/html/draft-ietf-acme-caa-03):

issuevalue = *WSP [domain] *WSP [";" *WSP [parameters] *WSP]

domain = label *("." label)
label = (ALPHA / DIGIT) *( *("-") (ALPHA / DIGIT))

parameters = (parameter *WSP “;” *WSP parameters) / parameter
parameter = tag *WSP "=" *WSP value
tag = (ALPHA / DIGIT) *( *("-") (ALPHA / DIGIT))
value = *(%x21-3A / %x3C-7E)

I used the same production rule value for "tag" that currently exists for "label" to allow for hyphens in the parameter tag, but didn't combine them so that we can continue to use the descriptive rule names of "tag" and "label" as opposed to something potentially confusing like "tag-or-label".

For the purposes of getting this incorporated into RFC 6844-bis (or RFC 6844-bis-bis), should I create an erratum, or is this email sufficient?

Thanks,
Corey


On 2/26/18, 2:04 PM, "Spasm on behalf of Jacob Hoffman-Andrews" <spasm-bounces@ietf.org on behalf of jsha@eff.org> wrote:

    On 02/26/2018 06:46 AM, Tim Hollebeek wrote:
    > the RFC 6844 grammar contradicts the examples.  Corey had an excellent
    > proposed fix for this issue.  It should probably be incorporated.
    I tried to incorporate changes based on the thread Corey started, but
    wound up deciding it was better to have something to adopt sooner rather
    than later. Definitely happy to continue to work on those changes in
    parallel with the call for adoption. Assuming the draft gets adopted as
    a WG work product, it's easy enough to land the changes on the WG draft.
    
    _______________________________________________
    Spasm mailing list
    Spasm@ietf.org
    https://scanmail.trustwave.com/?c=4062&d=2NqU2pDGsMarVBeRjdNh5mhb8N_iwA-esZb_hxFN5Q&s=5&u=https%3a%2f%2fwww%2eietf%2eorg%2fmailman%2flistinfo%2fspasm