IETF Logo Mail Archive

Re: [sacm] [sacmwg/draft-ietf-sacm-coswid] can't use CDDL to validate seemingly valid CBOR (#29)

cabo <notifications@github.com> Wed, 28 October 2020 13:30 UTC

Return-Path: <noreply@github.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1CA83A0138 for <sacm@ietfa.amsl.com>; Wed, 28 Oct 2020 06:30:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
X-Spam-Status: No, score=-2.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 492A9TDSFUiO for <sacm@ietfa.amsl.com>; Wed, 28 Oct 2020 06:30:35 -0700 (PDT)
Received: from out-25.smtp.github.com (out-25.smtp.github.com [192.30.252.208]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BBD63A0045 for <sacm@ietf.org>; Wed, 28 Oct 2020 06:30:35 -0700 (PDT)
Received: from github.com (hubbernetes-node-ac14c71.ash1-iad.github.net [10.56.120.41]) by smtp.github.com (Postfix) with ESMTPA id 52D92840F18 for <sacm@ietf.org>; Wed, 28 Oct 2020 06:30:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1603891834; bh=EB3oKQA7lz6Xxx62X+9Tk+nNiXLSacbkCS86ybnzDQk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Gux/+uUB9Z1qFEhYzGeaNMykQf81/+CHZ+JFwiZCstizfT9tTWnE2U+1V54bZUj2L BjJbFk4HvwYteGwNr4/lRsGsSwM0ZoAT73cXcZEGHqEf6WXyVOP/kYtVMmMki9WFEJ vpMZpjhfuf01OQoJn1nnpfIH1SigX7KPAqHZYEIM=
Date: Wed, 28 Oct 2020 06:30:34 -0700
From: cabo <notifications@github.com>
Reply-To: sacmwg/draft-ietf-sacm-coswid <reply+ACTMJUOU2NP5WC2J5DVUD2N5UVJXVEVBNHHCV7W7PY@reply.github.com>
To: sacmwg/draft-ietf-sacm-coswid <draft-ietf-sacm-coswid@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <sacmwg/draft-ietf-sacm-coswid/issues/29/717933662@github.com>
In-Reply-To: <sacmwg/draft-ietf-sacm-coswid/issues/29@github.com>
References: <sacmwg/draft-ietf-sacm-coswid/issues/29@github.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f99727a4f4bf_5919b4131667"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: cabo
X-GitHub-Recipient: sacm
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: sacm@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/fyskUsVBhmapHRcn4PyQtvY-WXU>
Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-coswid] can't use CDDL to validate seemingly valid CBOR (#29)
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.29
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2020 13:30:38 -0000

I'm also a bit more focused on the result than on the way of specifying it -- moving the globals to later in the group sequence might solve this problem already.  You just can't have two catch-alls.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/sacmwg/draft-ietf-sacm-coswid/issues/29#issuecomment-717933662

v2.23.0 | Report a Bug | By Email