Re: [sacm] [sacmwg/draft-ietf-sacm-information-model] softwareClass does not support softwareDependencies (#76)

Danny Haynes <notifications@github.com> Thu, 06 April 2017 14:14 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 09381128616 for <sacm@ietfa.amsl.com>; Thu, 6 Apr 2017 07:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.295
X-Spam-Level:
X-Spam-Status: No, score=-9.295 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-2.796, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=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 X2GNxkPz8fiz for <sacm@ietfa.amsl.com>; Thu, 6 Apr 2017 07:14:15 -0700 (PDT)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext3.iad.github.net [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA33C129505 for <sacm@ietf.org>; Thu, 6 Apr 2017 07:14:12 -0700 (PDT)
Date: Thu, 06 Apr 2017 07:14:12 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1491488052; bh=6tcSNkCaaICnsdL21v5gk8Y4/68X/RckIYPImqxw0Ww=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FdAZhS/MABemPxRzR0yYOj5+zOzIauIysoUK1QG424N0y7u6ovP8kCWNa+miR+k2S 32GFWJbFh/RhiUzU6kKqIEA8BSZI3qzRNPuxn8L+6D++yl49YtNpW/W7p2bMz0Pep5 tVvvS4g+o541GP9OY2Esp9lndzZhtTxtBHQB7J4I=
From: Danny Haynes <notifications@github.com>
Reply-To: sacmwg/draft-ietf-sacm-information-model <reply+00a6c4d13c123fe4f670c43d2f19a54c97b055227012218092cf0000000114fe0f3492a169ce0cca955a@reply.github.com>
To: sacmwg/draft-ietf-sacm-information-model <draft-ietf-sacm-information-model@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <sacmwg/draft-ietf-sacm-information-model/issues/76/292187417@github.com>
In-Reply-To: <sacmwg/draft-ietf-sacm-information-model/issues/76@github.com>
References: <sacmwg/draft-ietf-sacm-information-model/issues/76@github.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_58e64d3433504_292b3fe3ff26fc3c1536d8"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: djhaynes
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/R3wsx78BKVJQ6_CC4bIk1Qa11_c>
Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-information-model] softwareClass does not support softwareDependencies (#76)
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.22
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, 06 Apr 2017 14:14:17 -0000

Would it be enough to include an absolute file path and the versions/hashes could be looked up at a later point in time? Or, does that information need to be embedded in the SoftwareInstance IE?

So, I think it is okay that the softwareInstance IE doesn't support everything in CIM_SoftwareIdentity (or any other DM for that matter) because DMs may support IEs beyond those specified by the IM. We also want to be careful not to make IM IEs so specific that they preclude the use of DMs because they can't implement the IE. For example, we wouldn't want to use the CIM_SoftwareIdentity version property because it is fairly restrictive and would not accommodate version strings used to describe RPM and DPKG software on Linux among others.  With all that said, if there are certain properties that seem generally applicable that should be included, I would like to hear your's and others' thoughts on them.

-- 
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-information-model/issues/76#issuecomment-292187417