[sacm] Question about DM Requirements

"Haynes, Dan" <dhaynes@mitre.org> Tue, 21 June 2016 17:54 UTC

Return-Path: <dhaynes@mitre.org>
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 A6E7D12DB90 for <sacm@ietfa.amsl.com>; Tue, 21 Jun 2016 10:54:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.716
X-Spam-Level:
X-Spam-Status: No, score=-3.716 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mitre.onmicrosoft.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 a6tO-tmF3U6N for <sacm@ietfa.amsl.com>; Tue, 21 Jun 2016 10:54:19 -0700 (PDT)
Received: from smtpvmsrv1.mitre.org (smtpvmsrv1.mitre.org [192.52.194.136]) by ietfa.amsl.com (Postfix) with ESMTP id 9B06512DB7F for <sacm@ietf.org>; Tue, 21 Jun 2016 10:54:19 -0700 (PDT)
Received: from smtpvmsrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 193CA6C007C for <sacm@ietf.org>; Tue, 21 Jun 2016 13:54:19 -0400 (EDT)
Received: from imshyb01.MITRE.ORG (imshyb01.mitre.org [129.83.29.2]) by smtpvmsrv1.mitre.org (Postfix) with ESMTP id 093657BC046 for <sacm@ietf.org>; Tue, 21 Jun 2016 13:54:19 -0400 (EDT)
Received: from imshyb01.MITRE.ORG (129.83.29.2) by imshyb01.MITRE.ORG (129.83.29.2) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Tue, 21 Jun 2016 13:54:18 -0400
Received: from gcc01-CY1-obe.outbound.protection.outlook.com (10.140.19.249) by imshyb01.MITRE.ORG (129.83.29.2) with Microsoft SMTP Server (TLS) id 15.0.1130.7 via Frontend Transport; Tue, 21 Jun 2016 13:54:18 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mitre.onmicrosoft.com; s=selector1-mitre-org; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=i+Weg5/7hGwy8/RJOxJ3fEIlAlTYhJI+zfoNQWVmHZs=; b=pkUV8HRRVd8nBKtDxA0h+SA2+dO0fb8T6BjQ5jrxD8d/KleHUl5suEZTyQyxbNLY2eDqkrNEjSEHSReaMlwxetwlobNKK+BFgC7JgPp7BR7VRTfU3CKJKot26Bj6bBtQv0DGZ9UN9st+lXu1UU2PVzTY1t7AP+uezOlXEWm0NC0=
Received: from BY2PR09MB1078.namprd09.prod.outlook.com (10.166.116.10) by BY2PR09MB1080.namprd09.prod.outlook.com (10.166.116.12) with Microsoft SMTP Server (TLS) id 15.1.523.12; Tue, 21 Jun 2016 17:54:17 +0000
Received: from BY2PR09MB1078.namprd09.prod.outlook.com ([10.166.116.10]) by BY2PR09MB1078.namprd09.prod.outlook.com ([10.166.116.10]) with mapi id 15.01.0523.015; Tue, 21 Jun 2016 17:54:17 +0000
From: "Haynes, Dan" <dhaynes@mitre.org>
To: "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: Question about DM Requirements
Thread-Index: AdHL4+wgxazq+QzLQVe22pvEQ/aWnw==
Date: Tue, 21 Jun 2016 17:54:17 +0000
Message-ID: <BY2PR09MB107821EBB3255BF6C6352628A52B0@BY2PR09MB1078.namprd09.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=dhaynes@mitre.org;
x-originating-ip: [192.160.51.87]
x-ms-office365-filtering-correlation-id: 0de197b2-1b52-4565-07c4-08d399fd107f
x-microsoft-exchange-diagnostics: 1; BY2PR09MB1080; 6:PXnjmB/cSJCvZ1Q0GqErdrsEmglGdsfN6OE6Mf8kMupeBEUUaKVp8RKt25LhP14zRpPBrvE1lxz7MJb3bzvpP9Xty9+rq2m8T3ChlmvpyMscyDPGQbaqAbXGmV63FMGqZzTzbYGDtBAM07z4fUBrpckzuCMN8mV3lmzvSDmccni0Jx+KAHlCNI1iO0suEUVB3Cu8qcZzjqPxQ1y2vm97q2SSBlBKI4MavZ7LdbZpH88QL1XIstAmne8GT14DxOe5RHJl3EfHBNAvfjkB84oqQelTGuBugj9WUdtz69LEFQ80vYxxqVOJaZSDF1rLGJvPZszEki1+nbm6+m2ydRjlxw==; 5:Jpf+HDs9T4bEPYdH7wGiGRBJdw8fZpkYKFtD59BFW5ySBLVsZvBRulRfFrwikK8YLQuLOwnbkkLNRkysmbQ9cEH/gk9Q9qXc+qvuo3AbwyzS64fnbftm0rHPvLUIxaRsH1fb7ZZfufpRnF1LCRdOXQ==; 24:BV7ZF/A/tUKEU/TAMwYJt6krs7oJjwDYws8E2IQoC5a1Ni2NhrsgYY44w9WHhL5cCiXopCaSMA174gBYzf//dVT2DZuzZh29G540EgMnN9U=; 7:JXzAHscRp3uUw0ubChnKK1vsSbdfKPcAK+OMVHCT1vwywli6UVihLphbDIQfa2hsgTWASs8rVjO7lFDLbUjSql+O4lDAHtpza+HA1RQz6wxRouQrpnrL4fiIhnX3gfCB5K9jqu3G9jmlnkYUBTDMIFbeNPKGByr6kMRwOmevzYBhoWnQ1hanvf6bpmBrg2EL0o7J36pITOkUiWdS0j/xIihc2kkyLVyA9rCGAM8bCgcHEFsl839NwYNXGJ/LJYAb
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY2PR09MB1080;
x-microsoft-antispam-prvs: <BY2PR09MB1080ED57056FCB80C0E4122FA52B0@BY2PR09MB1080.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(131327999870524)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026); SRVR:BY2PR09MB1080; BCL:0; PCL:0; RULEID:; SRVR:BY2PR09MB1080;
x-forefront-prvs: 098076C36C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(199003)(189002)(10400500002)(81166006)(99286002)(8676002)(81156014)(66066001)(1730700003)(5002640100001)(122556002)(86362001)(3660700001)(74316001)(2501003)(87936001)(15975445007)(19300405004)(2900100001)(16236675004)(97736004)(19580395003)(2351001)(229853001)(68736007)(77096005)(102836003)(105586002)(9686002)(107886002)(110136002)(19625215002)(3280700002)(189998001)(450100001)(54356999)(101416001)(5630700001)(2906002)(8936002)(5640700001)(3480700004)(50986999)(33656002)(106356001)(11100500001)(790700001)(3846002)(92566002)(76576001)(7846002)(7736002)(6116002)(7696003)(5003600100003)(586003); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR09MB1080; H:BY2PR09MB1078.namprd09.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: mitre.org does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BY2PR09MB107821EBB3255BF6C6352628A52B0BY2PR09MB1078namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jun 2016 17:54:17.0927 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: c620dc48-1d50-4952-8b39-df4d54d74d82
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR09MB1080
X-OriginatorOrg: mitre.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/WyJPtTtUAc0-SXZfWFa4j6jpGVQ>
Subject: [sacm] Question about DM Requirements
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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: Tue, 21 Jun 2016 17:54:28 -0000

I was reviewing the DM requirements based on the SWID M&A call for adoption thread and had some questions.


In Section 2 of the Requirements, it says:


                    "Multiple data models, protocols, and transports may be employed in a SACM environment..."



Then DM-001 says:



"DM-001  Element Association: The data model MUST contain a data model element for each information model element (e.g. endpoint, IP address, asset).  In other words, for every item in the information model, there must be an item in the data model.  The data model can also include elements that do not exist in the information model."



Does this requirement conflict with the text above in Section 2 by saying that every DM must contain an element for each IM element?  That is, each DM must support the entire IM and it is not possible for a DM to just support a portion of the IM.



Also, DM-002 says:


"DM-002  Data Model Structure: The data model can be structured either as one single module or separated into modules and sub-modules that allow for references between them.  The data model structure MAY reflect structure in the information model, but does not need to. For example, the data model might use one module to define endpoints, and that module might reference other modules that describe the various assets associated with the endpoint. Constraints and interfaces might further be defined to resolve or tolerate ambiguity in the references (e.g. same IP address used in two separate networks)."



Is this effectively reiterating that a DM must support everything in the IM, but, that the DM can choose to break it up into submodules if they so choose?



Thanks,

Danny