[sacm] FW: Notes from terminology discussion

"Haynes, Dan" <dhaynes@mitre.org> Fri, 07 August 2015 17:17 UTC

From: "Haynes, Dan" <dhaynes@mitre.org>
To: "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: Notes from terminology discussion
Thread-Index: AdDFW+X/BKOAO0a8TxePrtRZVbcEkgL2MIAQ
Date: Fri, 07 Aug 2015 17:17:44 +0000
Message-ID: <BLUPR09MB10430065876D48FBC6F6210A5730@BLUPR09MB104.namprd09.prod.outlook.com>
References: <BN1PR06MB437D4B8DA8EC56A907EED54A8810@BN1PR06MB437.namprd06.prod.outlook.com>
In-Reply-To: <BN1PR06MB437D4B8DA8EC56A907EED54A8810@BN1PR06MB437.namprd06.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: mitre.org does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Aug 2015 17:17:44.6389 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: c620dc48-1d50-4952-8b39-df4d54d74d82
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR09MB104
X-OriginatorOrg: mitre.org
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/kWxlnboHAXD87cned9WavwPZy5w>
Subject: [sacm] FW: Notes from terminology discussion
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 07 Aug 2015 17:17:50 -0000

Just sharing some notes that were taken during an IETF 93 SACM working session.  Thanks to Lisa for putting them together!

-Danny

-----Original Message-----
From: Lisa Lorenzin [mailto:llorenzin@pulsesecure.net] 
Sent: Friday, July 24, 2015 6:20 PM
To: Jarrett Lu <jarrett.lu@oracle.com>; Adam Montville <adam.w.montville@gmail.com>; Haynes, Dan <dhaynes@mitre.org>; Nancy Cam-Winget (ncamwing) <ncamwing@cisco.com>; Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
Subject: Notes from terminology discussion

Hi all,

Here are the brief notes I took during the terminology discussion:

TERMINOLOGY NOTES:

relationships:
an asset instantiates an asset class or asset classes can use attributes collected from a target endpoint to map the target endpoint to an asset class or asset classes

an IP address can be any or all of: an attribute of an asset (hardware or software component), an attribute of a target endpoint, an attribute of <another container>

in the triple of subject, predicate, object - you MUST be able to use asset or endpoint as the subject, and you MUST also be able to use other subjects (i.e. asset and endpoint are the mandatory-to-implement subject, but implementers are not restricted to only asset and endpoint as subjects)

need a relationships section in the terminology draft since there's lots of glue information about how individual terms fit together which doesn't fall nicely under any single term definition

in a container, you can have other containers.  In a container, you can have more than one of any given container or any given AVP.
so the container network address contains the container IP address (along with other containers such as MAC address, and an extension point for future containers), and the container IP address might contain ipv4 address = $foo, ipv4 address = $bar, ipv6 address = $baz

container: network address
	container: IP address
		container: IPv4 address
			value

							Regards,

								Lisa

-- 
Lisa Lorenzin    /    Principal Solutions Architect
llorenzin@pulsesecure.net    /    919-384-7275

Pulse Secure    /    https://www.pulsesecure.net
Facebook: https://www.facebook.com/pulsesecure1
LinkedIn: https://www.linkedin.com/company/pulse-secure
Twitter: https://twitter.com/PulseSecure1

[sacm] FW: Notes from terminology discussion Haynes, Dan