Re: [sacm] Fwd: I-D Action: draft-handt-sacm-asset-identifiers-00.txt

I may have answered my own question actually digging into it.  So, if I'm understanding this right, it seems like we'd be seeing arcs that would have OIDs that are named, which would have some node that acts as a class of the instances found below...  Maybe I'm still wrong.  More digging.

> -----Original Message-----
> From: sacm-bounces@ietf.org [mailto:sacm-bounces@ietf.org] On Behalf Of
> Adam Montville
> Sent: Thursday, July 25, 2013 10:04 AM
> To: Sean Turner; sacm@ietf.org
> Subject: Re: [sacm] Fwd: I-D Action: draft-handt-sacm-asset-identifiers-
> 00.txt
> 
> Being the transcriber of NISTS Asset Identification standard to an I-D format
> (now expired), I have some questions about this proposal.  First, however, I
> like the way this reads and flows and I enjoyed reading it, much like I enjoyed
> reading the alternate architecture document.
> 
> It seems that draft-handt-sacm-asset-identifiers-00 is squarely focused on
> instance-level identity, identification, and identifiers.  I believe, that we have
> several levels of "identification" requirements.  We do want instance-level
> identification, and I believe OIDs, as proposed, could be a good solution.  I
> believe we also want class-level identification, for which we have been
> considering CPE.
> 
> For example, I may have several OIDs, one for each of a Windows Server
> 2008 instance, RHEL 6 instance, Windows Server 2012 instance, and Solaris 9
> instance.  Now, I want to find all the assets in the "Windows" class, which
> would be the set of two OIDs representing the WS2008 and WS2012
> instances.  We could leave it up to implementers to provide this type of
> functionality, but would it not be useful to have some standardized way to
> represent that class?
> 
> An honest question: How would this proposal handle class-level
> identification?  Or, do we collectively believe there is no such need?
> 
> Adam
> 
> > -----Original Message-----
> > From: sacm-bounces@ietf.org [mailto:sacm-bounces@ietf.org] On Behalf
> > Of Sean Turner
> > Sent: Thursday, July 11, 2013 9:51 AM
> > To: sacm@ietf.org
> > Subject: [sacm] Fwd: I-D Action:
> > draft-handt-sacm-asset-identifiers-00.txt
> >
> > More food for thought.
> >
> > spt
> >
> > -------- Original Message --------
> > Subject: I-D Action: draft-handt-sacm-asset-identifiers-00.txt
> > Date: Thu, 11 Jul 2013 09:50:15 -0700
> > From: internet-drafts@ietf.org
> > Reply-To: internet-drafts@ietf.org
> > To: i-d-announce@ietf.org
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >
> >
> > 	Title           : sacm: Asset Identifier
> > 	Author(s)       : Russ Housley
> >                            Sean Turner
> > 	Filename        : draft-handt-sacm-asset-identifiers-00.txt
> > 	Pages           : 7
> > 	Date            : 2013-07-11
> >
> > Abstract:
> >     This document examines the asset identifiers available for sacm and
> >     it proposes that OIDs (Object Identifiers) be selected as the asset
> >     identifier format.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-handt-sacm-asset-identifiers
> >
> > There's also a htmlized version available at:
> > http://tools.ietf.org/html/draft-handt-sacm-asset-identifiers-00
> >
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html or
> > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> >
> >
> > _______________________________________________
> > sacm mailing list
> > sacm@ietf.org
> > https://www.ietf.org/mailman/listinfo/sacm
> >
> > ...
> 
> This message and attachments may contain confidential information.  If it
> appears that this message was sent to you by mistake, any retention,
> dissemination, distribution or copying of this message and attachments is
> strictly prohibited.  Please notify the sender immediately and permanently
> delete the message and any attachments.
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm
> 
> ...

This message and attachments may contain confidential information.  If it appears that this message was sent to you by mistake, any retention, dissemination, distribution or copying of this message and attachments is strictly prohibited.  Please notify the sender immediately and permanently delete the message and any attachments.