Subject: Re: [sacm] [draft-ietf-sacm-architecture] Differentiate semantics of collection results vs. assertions (#7)

From: Lisa Lorenzin <[email-masked]>
Date: Fri, 17 Apr 2015 20:24:13 +0000

My $.02 on this issue:

The AVP itself does not assert anything.  The AVP simply captures (represents) a relationship: the value of attribute X is Y.  

The _assertion_ is being made by the party reporting the AVP (i.e. the collector).  The collector is asserting that the value of attribute X is Y.  This assertion may be correct, incorrect, or incomplete depending on the authoritativeness of the asserting party.  (For example, software on an endpoint may assert that for the attribute "AV-enabled" the value is "true" - but if some malware has compromised the OS and is able to provide false information to the collector, the assertion may not be correct.

Regards,
Lisa

-----Original Message-----
From: adammontville [mailto:[email-masked]] 
Sent: Friday, April 17, 2015 12:25 PM
To: sacmwg/draft-ietf-sacm-architecture
Subject: [draft-ietf-sacm-architecture] Differentiate semantics of collection results vs. assertions (#7)

This issue was raised during the 2015-04-17 endpoint ID design team meeting. At issue is whether a "collection result" embodies an "assertion", or if the "collection result" is simply an attribute-value pair (AVP). From one perspective, the AVP simply is; from another perspective, the AVP is asserting that the attribute A "has value" V.

—
Reply to this email directly or view it on GitHub <https://github.com/sacmwg/draft-ietf-sacm-architecture/issues/7> . <https://github.com/notifications/beacon/AKcH1aiG1cccTfCHLtDC-_vsNrl2mhK6ks5oAStQgaJpZM4EC3hu.gif>