Re: [sacm] Call for adoption of draft-coffin-sacm-nea-swid-patnc as a SACM WG document

"Schmidt, Charles M." <cmschmidt@mitre.org> Wed, 18 May 2016 17:38 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 4BDAF12D584 for <sacm@ietfa.amsl.com>; Wed, 18 May 2016 10:38:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.626
X-Spam-Level:
X-Spam-Status: No, score=-5.626 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 TOSRR5fXzuuu for <sacm@ietfa.amsl.com>; Wed, 18 May 2016 10:38:32 -0700 (PDT)
Received: from smtpvmsrv1.mitre.org (smtpvmsrv1.mitre.org [192.52.194.136]) by ietfa.amsl.com (Postfix) with ESMTP id 74CA312D17C for <sacm@ietf.org>; Wed, 18 May 2016 10:38:32 -0700 (PDT)
Received: from smtpvmsrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id C0F3B6FCB53; Wed, 18 May 2016 13:38:31 -0400 (EDT)
Received: from imshyb01.MITRE.ORG (imshyb01.mitre.org [129.83.29.2]) by smtpvmsrv1.mitre.org (Postfix) with ESMTP id AA5646FCB57; Wed, 18 May 2016 13:38:31 -0400 (EDT)
Received: from imshyb02.MITRE.ORG (129.83.29.3) by imshyb01.MITRE.ORG (129.83.29.2) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Wed, 18 May 2016 13:38:31 -0400
Received: from gcc01-CY1-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 13:38:31 -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=QJKLFO6d3n65MazvcUcIE1CLVwcEdQydV9LYhTQ+8Ag=; b=XQ3Ucd/TPFtvfXM2SHbGqUJC2ylmzwjVxrrtr10CFvey8FU0Rnvc6hxIC6bhmO6rj90OPmcxDBZQHjKQRYSVO9Ljeq+WcJfG8KjK+BjRQT/bl+/w+lQI9K1LqQBANz4NdMo8rUFq3z9pfUpUgQTjg1wzhiiLcsezEJlEa/Vr7EM=
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 17:38:24 +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 17:38:24 +0000
From: "Schmidt, Charles M." <cmschmidt@mitre.org>
To: Michael Godsey <mgodsey@microsoft.com>, Jerome Athias <athiasjerome@gmail.com>, Tony Rutkowski <tony@yaanatech.com>
Thread-Topic: [sacm] Call for adoption of draft-coffin-sacm-nea-swid-patnc as a SACM WG document
Thread-Index: AQHRsIRJYgDnjWKISkyXny5miMOOyp+909wwgADujACAAAf/gIAAA+JAgAAhpFA=
Date: Wed, 18 May 2016 17:38:24 +0000
Message-ID: <SN1PR09MB0990AD2634A81C9A7128D120AB490@SN1PR09MB0990.namprd09.prod.outlook.com>
References: <17198AFF-DF5A-46BC-B84A-2AAF1717BD90@isoc.org> <e8798c66-2ac8-7b24-4ab3-d28b4868c94a@yaanatech.com> <BN1PR03MB1231A9F5A4EE487623E5C82AF490@BN1PR03MB123.namprd03.prod.outlook.com> <0aa7684f-5a47-c00a-4b5b-e19484dd718a@yaanatech.com> <CAA=AuEfepDpmQF7TOLe2nvkgEPU9LD49Fc8bSvUCW+F_6yYy5A@mail.gmail.com> <BN1PR03MB1236FEF6EE3127323F9294AAF490@BN1PR03MB123.namprd03.prod.outlook.com>
In-Reply-To: <BN1PR03MB1236FEF6EE3127323F9294AAF490@BN1PR03MB123.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: microsoft.com; dkim=none (message not signed) header.d=none;microsoft.com; dmarc=none action=none header.from=mitre.org;
x-originating-ip: [192.160.51.89]
x-ms-office365-filtering-correlation-id: 5d44c50e-650b-4fb4-8a31-08d37f4336d9
x-microsoft-exchange-diagnostics: 1; SN1PR09MB0990; 5:t/V7Kh8WfFG0rBJ2Dsn/RqgmaWO7W7wykn5nf+TI7eO2uRC3cvwttWyuuj+whckYBgfb8S0QQ8jaWKrthjWnO9/Ut0pq4Ng1eDI0wXhy58QkBRc9uOCdCqdphvFqASO+bguFUudgZDKu8tvoo7/+mA==; 24:vXQjWum2IV+4SvDavdt0x7olvdkSbpfgKWZq246JcLjlP/iLpXQownx1RfmGMSzpp5ojszhzSt9i2I41SLK0VnyiBtGFqaHTgqnfz03VX/8=; 7:HzPOL2b/IoKewZvda23t3R5KEKmf3UgzaUOwQ/EZjjekHR8P//nPEKZJfajAhRyB8Z4UrL7wzVJOe8O/4GiHqAMz3k4YvWiMtijpTS4GPYBmKvduuRW91auGiZ8RF2wou0sy/ZMw8JRa99GbLG1GYpG+SR46hpPWP4qZ1k9HZ0pyLSEsnr2iHD8ooRQZ/qAC
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR09MB0990;
x-microsoft-antispam-prvs: <SN1PR09MB0990233B92A17F5FEC43689CAB490@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)(10201501046)(3002001)(6055026); SRVR:SN1PR09MB0990; BCL:0; PCL:0; RULEID:; SRVR:SN1PR09MB0990;
x-forefront-prvs: 0946DC87A1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(53754006)(377424004)(377454003)(24454002)(13464003)(99286002)(2950100001)(33656002)(15975445007)(2900100001)(2421001)(122556002)(3660700001)(15395725005)(5004730100002)(5003600100002)(6116002)(5001770100001)(87936001)(106116001)(66066001)(10400500002)(5008740100001)(2906002)(54356999)(74316001)(3280700002)(4326007)(50986999)(76176999)(99936001)(76576001)(86362001)(1720100001)(19580405001)(2561002)(9686002)(230783001)(19580395003)(77096005)(93886004)(102836003)(189998001)(11100500001)(5002640100001)(8936002)(586003)(8666002)(92566002)(81166006)(8676002)(1220700001)(7059030); 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_00D1_01D1B102.252AFC00"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 May 2016 17:38:24.7259 (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/EVzRCVUCZsGUIPIgv-rLvuIotCo>
Cc: "sacm@ietf.org" <sacm@ietf.org>, Karen O'Donoghue <odonoghue@isoc.org>
Subject: Re: [sacm] Call for adoption of draft-coffin-sacm-nea-swid-patnc as a SACM WG document
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 17:38:35 -0000

Hi all,

To answer Tony's original question: "Why are we supporting the 2009 version of SWID tags given its known flaws?" - The question of whether to retain support for the 2009 SWID specification was raised at IETF 95 and, within that room, the consensus was to support both versions. The reason was that there are existing 2009 SWID tags deployed today and there was a desire to allow them to be delivered by SWID M&A. If SWID M&A only supported the 2015 SWID version, those older version tags are effectively lost to SACM assessment. Between this and the fact that the same design supports both versions of SWID tags (albeit using a slightly different procedure, which will be better clarified in the next revision), it seemed like there was little point in explicitly excluding collection and delivery of any 2009 tags that might exist.

Regarding Michael's comment about adding a reference to NIST IR 8060 - that sounds like a great idea to me.

Charles

> -----Original Message-----
> From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Michael Godsey
> Sent: Wednesday, May 18, 2016 10:23 AM
> To: Jerome Athias <athiasjerome@gmail.com>; Tony Rutkowski
> <tony@yaanatech.com>
> Cc: sacm@ietf.org; Karen O'Donoghue <odonoghue@isoc.org>
> Subject: Re: [sacm] Call for adoption of draft-coffin-sacm-nea-swid-patnc as
> a SACM WG document
> 
> The current version of the 19770-2:2015 schema can always be found here
> (note difference from below):
>  http://standards.iso.org/iso/19770/-2/2015-current/schema.xsd
> 
> The schema must be published along with and at the time of the standard,
> thus a "point in time" version is in the 19770/-2/2015/ directory.   The
> previous as-published version is in the 19770/-2/2009 directory structure as
> well.   However, the "up to date" version of the 2015 edition of the standard
> is always at the link above, the 19770/-2/2015-current/ directory.
> 
> RE the NIST IR:
> A few weeks ago NIST hosted a workshop on SWID adoption (which I
> attended, along with other software publishers, some end customers, and
> reps from various US Govt agencies).  We mainly reviewed the final draft
> version (released April 2016)  of NISTIR 8060 – Guidelines for the Creation of
> Interoperable Software Identification (SWID) Tags.
> •	This NIST IR (plus related reference info) can be found on their portal
> at: http://csrc.nist.gov/publications/PubsNISTIRs.html
> •	Or here is a direct link to the NIST IR 8060 itself:
> http://dx.doi.org/10.6028/NIST.IR.8060
> 
> This is a really good reference which includes sections giving an overview of
> SWID Tags, the SWID Tag structure, and some implementation guidance for
> Tag creators.   I think this would be a good reference to include, as it is
> available without any paywall.
> 
> Also in the TagVault board meeting yesterday we discussed the need to
> provide some help/guidance for adoption of SWID tags, similar to the NISTIR
> 8060, which being a US document is not appealing to all countries.   We
> decided to create a reference implementation guide which would come out
> of TagVault and be available to anyone.   I am guessing this should be
> available in maybe 3-4 months.
> 
> 
> -----Original Message-----
> From: Jerome Athias [mailto:athiasjerome@gmail.com]
> Sent: Wednesday, May 18, 2016 7:58 AM
> To: Tony Rutkowski <tony@yaanatech.com>
> Cc: Michael Godsey <mgodsey@microsoft.com>; Karen O'Donoghue
> <odonoghue@isoc.org>; sacm@ietf.org
> Subject: Re: [sacm] Call for adoption of draft-coffin-sacm-nea-swid-patnc as
> a SACM WG document
> 
> Maybe a misread and difference between the Specification and the XML
> Schema in 2.1.
> "The SWID specification is available from ISO/IEC at
> http://www.iso.org/iso/catalogue_detail.htm?csnumber=53670.
> The XML schema for a SWID tag file is available from ISO:
> http://standards.iso.org/iso/19770/-2/2009/schema.xsd.
> The most current working and production versions of the XML schema for
> SWID tags can be found in the directory listing
> http://standards.iso.org/iso/19770/-2/.
> The US National Institute of Standards and Technology (NIST) also has
> published guidelines for
>    SWID tag creation, which provide further guidance for those
>    interested in the use and best practices surrounding SWID tags.
>    [NIST-SWID]"
> 
> 
> 
> 
> 
> 2016-05-18 17:29 GMT+03:00 Tony Rutkowski <tony@yaanatech.com>:
> > For those unfamiliar with this topic, there is a fairly good
> > explanation of why the old
> > 2009 version was significantly flawed and revised at:
> > http://tagvault.org/2015/06/11/isoiec-19770-2-revision-moving-to-publi
> > cation/
> >
> > --tony
> >
> > ps. Still waiting for someone to request ISO to make the specification
> > publicly available without coughing up CHF 178.  It's not that
> > difficult, and has been widely done for important specifications.  It
> > is also generally required for standards that are imposed as normative
> > requirements by government.
> >
> >
> > On 2016-05-17 8:18 PM, Michael Godsey wrote:
> >
> > I echo the concern and question.   If this points to the 2009 version, it
> > needs to be updated.  Not only did we put a ton of work into revising
> > the -2 standard for 2015, but this also obsoletes the 2009 version.
> > As noted the NISTIR 8060 was based entirely on the 19770-2:2015
> > version, leveraging the many changes implemented for better
> > instrumentation and fidelity of tag data, tag relationships, etc.
> >
> >
> >
> > From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Tony Rutkowski
> > Sent: Tuesday, May 17, 2016 2:37 PM
> > To: Karen O'Donoghue <odonoghue@isoc.org>; sacm@ietf.org
> > Subject: Re: [sacm] Call for adoption of
> > draft-coffin-sacm-nea-swid-patnc as a SACM WG document
> >
> >
> >
> > Remind us again why this ID references the 2009 version of ISO/IEC
> > 19770-2, when there a 2015 apparently significantly different version
> > has been adopted and is referenced in the NISTIR 8060 as the basis for
> > implementations?
> >
> > It's interesting that the 2015 version for the GUID data element
> > references 19770-5.  It's great to see it's apparently now publicly
> > available at
> > https://www.iso.org/obp/ui/#iso:std:iso-iec:19770:-5:ed-2:v1:en
> >
> > The version question seem rather significant for progressing the
> > working group document.  Was there some discussion somewhere?
> >
> > --tony
> >
> > On 2016-05-17 12:21 PM, Karen O'Donoghue wrote:
> >
> > Folks,
> >
> >
> >
> > As discussed during our last couple of meetings, this is the official
> > call for adoption of
> > https://datatracker.ietf.org/doc/draft-coffin-sacm-nea-swid-patnc/ as
> > a SACM working group document.
> >
> >
> >
> > Please reply with any comments or concerns along your support of this
> > action to the mailing list.
> >
> >
> >
> > Thanks,
> >
> > Karen and Adam
> >
> >
> >
> >
> > _______________________________________________
> >
> > sacm mailing list
> >
> > sacm@ietf.org
> >
> > https://www.ietf.org/mailman/listinfo/sacm
> >
> >
> >
> >
> > --
> >
> > ________________________________
> >
> > Anthony Michael Rutkowski
> >
> > EVP, Industry Standards & Regulatory Affairs
> >
> > tony@yaanatech.com
> >
> > +1 703 999 8270
> >
> > ________________________________
> >
> > Yaana Technologies LLC
> >
> > 542 Gibraltar Drive
> >
> > Milpitas CA 95035 USA
> >
> >
> > _______________________________________________
> > sacm mailing list
> > sacm@ietf.org
> > https://www.ietf.org/mailman/listinfo/sacm
> >
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm