[sacm] Proto-consensus - Removal of references to TNC's IF-IMV and IF-IMC specifications.

"Schmidt, Charles M." <cmschmidt@mitre.org> Wed, 18 May 2016 18:21 UTC

Return-Path: <cmschmidt@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 8703F12D607 for <sacm@ietfa.amsl.com>; Wed, 18 May 2016 11:21:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.625
X-Spam-Level:
X-Spam-Status: No, score=-5.625 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426] 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 HJl_Rmtz33qB for <sacm@ietfa.amsl.com>; Wed, 18 May 2016 11:21:33 -0700 (PDT)
Received: from smtpvmsrv1.mitre.org (smtpvmsrv1.mitre.org [192.52.194.136]) by ietfa.amsl.com (Postfix) with ESMTP id 52AFD12D62F for <sacm@ietf.org>; Wed, 18 May 2016 11:21:33 -0700 (PDT)
Received: from smtpvmsrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 02FF76FC045 for <sacm@ietf.org>; Wed, 18 May 2016 14:21:33 -0400 (EDT)
Received: from imshyb02.MITRE.ORG (imshyb02.mitre.org [129.83.29.3]) by smtpvmsrv1.mitre.org (Postfix) with ESMTP id E26D06FC042 for <sacm@ietf.org>; Wed, 18 May 2016 14:21:32 -0400 (EDT)
Received: from imshyb02.MITRE.ORG (129.83.29.3) by imshyb02.MITRE.ORG (129.83.29.3) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Wed, 18 May 2016 14:21:32 -0400
Received: from gcc01-dm2-obe.outbound.protection.outlook.com (10.140.19.249) by imshyb02.MITRE.ORG (129.83.29.3) with Microsoft SMTP Server (TLS) id 15.0.1130.7 via Frontend Transport; Wed, 18 May 2016 14:21:32 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mitre.onmicrosoft.com; s=selector1-mitre-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=osv9118qm4ipINEfBPlSh1IgXS3D9/JaVmBA55sZJiw=; b=HW4MsudiuoCmpnyi7O6kkgFPku+SidMDA8FAn4ds+LRGqHxyNJbrhwLALImFCt0Oo7sfKtakE6N3yn2wZujxpREWeJ75kg3z7wc2zG+CMHCik7jPx7xybUReudn9bGHbb4tQVHeFKBI8BM8Hw3w3tVmIuaOClRYtDaEI3o6N9PM=
Received: from SN1PR09MB0990.namprd09.prod.outlook.com (10.166.69.8) by SN1PR09MB0990.namprd09.prod.outlook.com (10.166.69.8) with Microsoft SMTP Server (TLS) id 15.1.497.12; Wed, 18 May 2016 18:21:26 +0000
Received: from SN1PR09MB0990.namprd09.prod.outlook.com ([10.166.69.8]) by SN1PR09MB0990.namprd09.prod.outlook.com ([10.166.69.8]) with mapi id 15.01.0497.019; Wed, 18 May 2016 18:21:26 +0000
From: "Schmidt, Charles M." <cmschmidt@mitre.org>
To: "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: Proto-consensus - Removal of references to TNC's IF-IMV and IF-IMC specifications.
Thread-Index: AdGxMCcXGwBSrRtdTQa8+RYb6MHMZw==
Date: Wed, 18 May 2016 18:21:25 +0000
Message-ID: <SN1PR09MB0990B4BB3647A131BC00BF63AB490@SN1PR09MB0990.namprd09.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=mitre.org;
x-originating-ip: [192.160.51.89]
x-ms-office365-filtering-correlation-id: d4978841-4c80-420c-a16d-08d37f493958
x-microsoft-exchange-diagnostics: 1; SN1PR09MB0990; 5:R4nob0Rfm5+o09J5HjA/BqN/IPR0rv5hVUcFQ6xt5/Sii8A+Vv0xNRqOUvrABN2Y/m4frfx0kcOS8HgmQPJibn5sga0vBfSGXaeFqQ3/CKpWqwg/LHP+jMT02zgTX/MGsjKYA3akMSPC6SuDoTqdFg==; 24:5S+hBE2gDM2PZKbq84wAnVHcY65LG6Xy0RPMeLxgVH6DDyjABXszZbUIhooGOpeE90QM706eLaxQhthfeVe6j3OeO/7VDnLb9tB4YfqBy7Q=; 7:TsHzRgeXcs4ljGgswYEvDcbKtdC6lLHcIOAmQaiHwneNsHfw8kUl9NLqiAZdVyVbF8pYlYyj8Rfp+hxO49w6dnXoaOyi9xJqWs9ezCMD6WhuwllSToi5i/BPyH8t1UX821fRKN8hwUlSfXM3w/XBpIkLTaWxEcb0uvDHpwnI2eda4/2ZwQy/IfduZUx3TGTY
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR09MB0990;
x-microsoft-antispam-prvs: <SN1PR09MB0990C788338D81350A5746D3AB490@SN1PR09MB0990.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415293)(102615271)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6055026); SRVR:SN1PR09MB0990; BCL:0; PCL:0; RULEID:; SRVR:SN1PR09MB0990;
x-forefront-prvs: 0946DC87A1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(55674003)(53754006)(107886002)(110136002)(86362001)(9686002)(19580395003)(450100001)(3280700002)(74316001)(54356999)(76576001)(50986999)(99936001)(586003)(81166006)(92566002)(2501003)(8936002)(1220700001)(8676002)(1730700003)(102836003)(5640700001)(77096005)(5002640100001)(31430400001)(189998001)(11100500001)(229853001)(3660700001)(2351001)(87936001)(66066001)(6116002)(5003600100002)(5004730100002)(33656002)(15975445007)(99286002)(122556002)(2900100001)(10400500002)(5008740100001)(2906002); DIR:OUT; SFP:1101; SCL:1; SRVR:SN1PR09MB0990; H:SN1PR09MB0990.namprd09.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_00DA_01D1B108.2B2D5160"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 May 2016 18:21:25.9571 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: c620dc48-1d50-4952-8b39-df4d54d74d82
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR09MB0990
X-OriginatorOrg: mitre.org
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/OcT8-Trab8yNfzENN4omIf6_oIE>
Subject: [sacm] Proto-consensus - Removal of references to TNC's IF-IMV and IF-IMC specifications.
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: Wed, 18 May 2016 18:21:39 -0000

Hello all,

Between the discussions at IETF 95 and the virtual interim yesterday, there
appears to be "in room" consensus on a few proposed updates and expansions
to SWID M&A. As no IETF consensus is complete without mailing-list
consensus, I'm sending out messages on each point of proto-consensus.  

Item 1: Remove references to TNC's IF-IMV and IF-IMC specifications
The current SWID M&A specification references TNC's IF-IMV and IF-IMC
specifications. While both of these specification have been approved by the
Trusted Computing Group board for transfer to the IETF, we are going to hold
off on that delivery since these specifications 1) are long, 2) somewhat
peripheral to the vulnerability assessment scenario on which we are
currently focusing, and 3) there has been a major recent document dump and
we don't want people more overwhelmed than they are. In the meantime, since
these references are not critical to the specification, it was felt that we
should just remove them to avoid normative references to external
specifications as much as possible.

Both IF-IMV and IF-IMC are referenced with regard to interface functions
that are defined in those specifications. The purpose of naming those
specific interface functions is to describe how the identity of components
on the endpoint and the policy server are captured. This component identity
information is already conveyed between the communicants over the PB-TNC
messages over which SWID M&A communicates. In effect the text will change
from "collect the component identity as conveyed in the PB-TNC message by
using IF-IMC/IMV function XYZ to get the PB message information" to "collect
the component identity as conveyed in the PB-TNC message". The net effect is
the same - we just don't recommend a specific, named interface function.

Any concerns about this or can we call this consensus?

Charles