[Acme] Handling non-conformant CAA property names in ACME-CAA

Roland Shoemaker <roland@letsencrypt.org> Wed, 20 June 2018 20:47 UTC

Return-Path: <roland@letsencrypt.org>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14817130EC4 for <acme@ietfa.amsl.com>; Wed, 20 Jun 2018 13:47:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level:
X-Spam-Status: No, score=-2.011 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_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=letsencrypt.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 QQP81TkugxZp for <acme@ietfa.amsl.com>; Wed, 20 Jun 2018 13:47:18 -0700 (PDT)
Received: from mail-ot0-x22d.google.com (mail-ot0-x22d.google.com [IPv6:2607:f8b0:4003:c0f::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8413D130E29 for <acme@ietf.org>; Wed, 20 Jun 2018 13:47:18 -0700 (PDT)
Received: by mail-ot0-x22d.google.com with SMTP id p95-v6so1063222ota.5 for <acme@ietf.org>; Wed, 20 Jun 2018 13:47:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=letsencrypt.org; s=google; h=from:content-transfer-encoding:mime-version:subject:message-id:date :cc:to; bh=Zt++PcHPVrm0duxyr1Qdw+ZhIK2PEma8MV6WkQBmTkU=; b=Icb9yRaBPrzDo6gcDyOXz7J+I8d0i60bNwMU3+2bnziCkcwN2naj8JQVFUCe9xjlwW XdY4Ybq/ewKwFgpVc9h3r9jFtj5jdCR1W7bCp2jg+wztNfTLc/Xj3bt84dqBixLNEvfU gkklDJobUJ3t+bT95kNiQCJh9cF6ku+NwwreI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:cc:to; bh=Zt++PcHPVrm0duxyr1Qdw+ZhIK2PEma8MV6WkQBmTkU=; b=TM6f/8PW8QFS4Qg4S2SHLnDywzLMg4IAqRP0SSsp3jbhqtcAjv5Ll5eJo9jDJMQoKE kdi+H1gJdvkiF1i9vPxq4ew+rsaB4m65SkZKZkxVXAqY6FVq6v/2TC4EJAENKNHkHKCa x0gCds+sCDRWaUbxHgYvCv9a7nRl0t91rSLA/g82aLAkGe+Vf6+COHgYpugsbBvzdtDq QXajlxEQESrJK3jHYrbAe1jHvGzCuLlfUhTHjwOhcFkpsBrT21j+YVhf0+Q/WB32EDqK FDfkGsiaSD7hzM33zcjbjEnz0HGRDpIq8E0gH4R7hLkwiqtTm565/MXUOX51hao3FnyW 9g4g==
X-Gm-Message-State: APt69E1rlAvxc9uWHA4UEZ0XZ4SNTS6w2/UN1z2lPVJlITUUFxrwilz7 24AQIXCY9gKNwszuwrrkl9TJy5za+uw=
X-Google-Smtp-Source: ADUXVKKinS68Cbxp3c3up1kewAddilNGRkvhycFrpEciddnZSOwgyJJuakDhiLBG5Ei8rD+GLYAJ8w==
X-Received: by 2002:a9d:2b64:: with SMTP id f33-v6mr14827940otd.342.1529527637637; Wed, 20 Jun 2018 13:47:17 -0700 (PDT)
Received: from ?IPv6:2600:1700:bd50:a5b0:c1:8d4:da37:9785? ([2600:1700:bd50:a5b0:c1:8d4:da37:9785]) by smtp.gmail.com with ESMTPSA id a14-v6sm1412109oia.20.2018.06.20.13.47.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Jun 2018 13:47:17 -0700 (PDT)
From: Roland Shoemaker <roland@letsencrypt.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
Message-Id: <DC2B6BEA-713F-468E-A374-97C3A01CFEAF@letsencrypt.org>
Date: Wed, 20 Jun 2018 13:47:15 -0700
Cc: Hugo Landau <hlandau@devever.net>
To: acme@ietf.org
X-Mailer: Apple Mail (2.3445.8.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/SrS6Z2mQhZDQxaxlAWceOT9PLCs>
Subject: [Acme] Handling non-conformant CAA property names in ACME-CAA
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jun 2018 20:47:21 -0000

As previously discussed on the list the two property names defined in draft-ietf-acme-caa, "validation-methods” and "account-uri”, do not conform to the ABNF syntax in RFC 6844 as they contain hyphens. 6844-bis fixes this by expanding the ABNF to be less restrictive but for now this doesn’t really address the problem at hand.

Given it is probably unlikely that 6844-bis will be standardized any time soon is there any plan to make changes to draft-ietf-acme-caa to address this in the short term? Given we are not yet at the point where there is wide deployment/adoption of this feature can we take the easy route and simply remove the hyphens so that the document at least complies with the existing CAA document?