DM-016: Data Source Location

[jimsch]

Version -04

The meaning of this requirement is not clear to me. It could be represent two different things and needs to be clarified

1. The physical or logical location of the entity that provides the data
2. The location where the data was stored when it was provided to the customer.

[ncamwing]

Hi Jim,
This is a fair point. I think the location is really meant to be a "source" of the data not really the physical (geographical or topological) location of the data provider. We haven't really tagged or defined what a "source" would be, I think this could be a hostname, domain (DNS) name or application name.

Would you accept a rewording to be:
The data model SHOULD allow the provider to include attributes defining the data source (e.g. hostname, domain (DNS) name or application name.)

Thanks, Nancy.

[jimsch]

Perfectly reasonable update. I wonder if you would also like to include “collector” to the list of possible data sources or do you think that is covered by application name?

Jim

From: ncamwing [mailto:notifications@github.com]
Sent: Sunday, May 03, 2015 5:57 PM
To: sacmwg/draft-ietf-sacm-requirements
Cc: Jim Schaad
Subject: Re: [draft-ietf-sacm-requirements] DM-016: Data Source Location (#35)

Hi Jim,
This is a fair point. I think the location is really meant to be a "source" of the data not really the physical (geographical or topological) location of the data provider. We haven't really tagged or defined what a "source" would be, I think this could be a hostname, domain (DNS) name or application name.

Would you accept a rewording to be:
The data model SHOULD allow the provider to include attributes defining the data source (e.g. hostname, domain (DNS) name or application name.)

Thanks, Nancy.

—
Reply to this email directly or view it on GitHub #35 (comment) .Image removed by sender.

[ncamwing]

Yes, actually “application” could be a collector, aggregator, producer, or any other type of application that could be storing relevant posture information.

Thanks, Nancy

From: Jim Schaad <notifications@github.commailto:notifications@github.com>
Reply-To: sacmwg/draft-ietf-sacm-requirements <reply@reply.github.commailto:reply@reply.github.com>
Date: Sunday, May 3, 2015 at 6:21 PM
To: sacmwg/draft-ietf-sacm-requirements <draft-ietf-sacm-requirements@noreply.github.commailto:draft-ietf-sacm-requirements@noreply.github.com>
Cc: "ncamwing@cisco.commailto:ncamwing@cisco.com" <ncamwing@cisco.commailto:ncamwing@cisco.com>
Subject: Re: [draft-ietf-sacm-requirements] DM-016: Data Source Location (#35)

Perfectly reasonable update. I wonder if you would also like to include “collector” to the list of possible data sources or do you think that is covered by application name?

Jim

From: ncamwing [mailto:notifications@github.com]
Sent: Sunday, May 03, 2015 5:57 PM
To: sacmwg/draft-ietf-sacm-requirements
Cc: Jim Schaad
Subject: Re: [draft-ietf-sacm-requirements] DM-016: Data Source Location (#35)

Hi Jim,
This is a fair point. I think the location is really meant to be a "source" of the data not really the physical (geographical or topological) location of the data provider. We haven't really tagged or defined what a "source" would be, I think this could be a hostname, domain (DNS) name or application name.

Would you accept a rewording to be:
The data model SHOULD allow the provider to include attributes defining the data source (e.g. hostname, domain (DNS) name or application name.)

Thanks, Nancy.

—
Reply to this email directly or view it on GitHub #35 (comment) .Image removed by sender.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/35#issuecomment-98564390.

[jimsch]

I think this is probably ok in -05.