Re: [sacm] [sacmwg/draft-ietf-sacm-coswid] Addressed comments from WGLC reviewers. (#13)

Alex Nelson <notifications@github.com> Thu, 25 July 2019 00:52 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 1E7031204D7 for <sacm@ietfa.amsl.com>; Wed, 24 Jul 2019 17:52:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level:
X-Spam-Status: No, score=-8 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, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 zn4vJ7qX6XKb for <sacm@ietfa.amsl.com>; Wed, 24 Jul 2019 17:52:34 -0700 (PDT)
Received: from out-10.smtp.github.com (out-10.smtp.github.com [192.30.254.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00D7D1203E9 for <sacm@ietf.org>; Wed, 24 Jul 2019 17:52:33 -0700 (PDT)
Date: Wed, 24 Jul 2019 17:52:33 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1564015953; bh=Qw7PtyQ5smiw1pqnkKUUHLrAGPkHQ/Wsi9AAi/WyBXI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DueQR66B/16iRcRISP8UgiBjsl4mPouX37tfwMXldRXVA1fFtskg1pXRaLif3FBBB exyHmEVPn9xIIgMmSDt3wGOXGsjw2JLXxnLRV4oQKw7kPwQuOc1WAkIkOGX/HUnhQL 7wMfkcZpE3wzNpmf97ncraHLawnVhTjd0ohV2uWs=
From: Alex Nelson <notifications@github.com>
Reply-To: sacmwg/draft-ietf-sacm-coswid <reply+ACTMJUMAH5V6L7BTDMZE6EV3IYX5DEVBNHHBYKUYNA@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/pull/13/review/266354395@github.com>
In-Reply-To: <sacmwg/draft-ietf-sacm-coswid/pull/13@github.com>
References: <sacmwg/draft-ietf-sacm-coswid/pull/13@github.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d38fd5127245_3ff73fbfbbecd960643256"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ajnelson-nist
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/or7FZw2etCTmQNwgGCh5cDlZDs0>
Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-coswid] Addressed comments from WGLC reviewers. (#13)
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: Thu, 25 Jul 2019 00:52:36 -0000

ajnelson-nist commented on this pull request.



> @@ -1405,14 +1451,17 @@ security considerations regarding SWID/CoSWID tags focus on the application
 of SWID/CoSWID tags to address security challenges, and the possible
 disclosure of the results of those applications.
 
-A signed SWID/CoSWID tag whose signature has been validated can be relied upon to be
-unchanged since it was signed.  If the SWID/CoSWID tag was created by the
-software provider, is signed, and the software provider can be authenticated as the originator of the signature, then the tag can be considered authoritative.
-In this way, an authoritative SWID/CoSWID tag contains information about a software component provided by the maintainer of the software component, who is expected to be an expert in their own software. Thus, authoritative SWID/CoSWID tags can be trusted to represent authoritative information about the software component.  Having an authoritative SWID/CoSWID tag can be useful when the information in the
-tag needs to be trusted, such as when the tag is being used to convey
-reference integrity measurements for software components.  By contrast, the data contained in unsigned
+A tag is cnsidered "authoritative" if the SWID/CoSWID tag was created by the
+software provider. An authoritative SWID/CoSWID tag contains information about a software component provided by the maintainer of the software component, who is expected to be an expert in their own software. Thus, authoritative SWID/CoSWID tags can be trusted to represent authoritative information about the software component.  
+
+A signed SWID/CoSWID tag (see {{appendix-cose}}) whose signature has been validated can be relied upon to be
+unchanged since it was signed. By contrast, the data contained in unsigned o

Typo? Dangling `o`.

-- 
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/pull/13#pullrequestreview-266354395