Re: [Suit] draft-ietf-suit-manifest-09 references question
housley@vigilsec.com Sat, 17 October 2020 15:04 UTC
Return-Path: <housley@vigilsec.com>
X-Original-To: suit@ietfa.amsl.com
Delivered-To: suit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D96453A0953 for <suit@ietfa.amsl.com>; Sat, 17 Oct 2020 08:04:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 HsQwTPy2fnAN for <suit@ietfa.amsl.com>; Sat, 17 Oct 2020 08:04:36 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EB473A0924 for <suit@ietf.org>; Sat, 17 Oct 2020 08:04:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 7E670300B9B for <suit@ietf.org>; Sat, 17 Oct 2020 11:04:33 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id jOuybTXGNCx4 for <suit@ietf.org>; Sat, 17 Oct 2020 11:04:32 -0400 (EDT)
Received: from mail.smeinc.net (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTPSA id D2B3C300AEA; Sat, 17 Oct 2020 11:04:31 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Sat, 17 Oct 2020 11:04:31 -0400
From: housley@vigilsec.com
To: Dave Thaler <dthaler=40microsoft.com@dmarc.ietf.org>
Cc: suit <suit@ietf.org>
In-Reply-To: <BL0PR2101MB10272A3174C93F0FF414FE5EA3030@BL0PR2101MB1027.namprd21.prod.outlook.com>
References: <BL0PR2101MB10272A3174C93F0FF414FE5EA3030@BL0PR2101MB1027.namprd21.prod.outlook.com>
Message-ID: <16f349d352c6c2e1a0f1e4d031054de6@vigilsec.com>
X-Sender: housley@vigilsec.com
User-Agent: Roundcube Webmail
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/7G4-XCVXV4N4WJt7IWIr5HDj1gs>
Subject: Re: [Suit] draft-ietf-suit-manifest-09 references question
X-BeenThere: suit@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Software Updates for Internet of Things <suit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/suit>, <mailto:suit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/suit/>
List-Post: <mailto:suit@ietf.org>
List-Help: <mailto:suit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/suit>, <mailto:suit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Oct 2020 15:04:38 -0000
Yes, I think a reference is needed. Russ On 2020-10-16 19:26, Dave Thaler wrote: > Currently draft-ietf-suit-manifest-09 talks about Concise Software > Identifiers > > (or CoSWIDs) in a number of sections, but does not appear to cite any > reference > > that specifies what one is. This seems like a gap to me. > > Should draft-ietf-sacm-coswid be added as a normative reference? > > (I suspect yes.) > > Dave > _______________________________________________ > Suit mailing list > Suit@ietf.org > https://www.ietf.org/mailman/listinfo/suit