Having separate threads is frequently simpler so I have no objections to that.
I really wish Trevor was not on vacation so he could respond. Instead I will attempt to channel him and try not to get things really wrong. Based on previous conversations that I have had with Trevor (including last week at the Plasma side bar), the assumption we are working on is that users are not the brightest of people and things should be made as simple as possible for them. One of the corollaries of this is that options should generally not be given to users for configuration purposes. This means that there is no expectation that a generic ITAR policy would ever exist for a company. Instead you would define a different policy for each of the ITAR export licenses/ projects. Thus if you work on aircraft as an engineer, you would choose a role for a specific plane and get a small list of policies. It might be that the end-user would not even see that it was ITAR export controlled, but rather just that it is internal, external for that specific project. The more options that make the end user select, the more likely that are to get things wrong has been a basic philosophy that Trevor has espoused during the design. Counter arguments would be interesting, but probably better after he gets back at the end of the month. Jim > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Fitch, Scott C > Sent: Thursday, August 04, 2011 2:05 PM > To: [email protected] > Subject: [plasma] Advanced Policies > > (Apologies for all the posts. Just trying to keep the threads separate for > commenting.) > > It's important to acknowledge that many Advanced policies will required > information about the message beyond just the Policy identifier. An example > from the export control world: An email may be governed by the ITAR policy, > however, access control decisions are made based ITAR and the specific > export license or agreement that applies to the message. Simply identifying > that the document is export controlled doesn't given the PDP enough > information to make a grant or deny decision. > > Stated differently, an access decision is based on attributes about the > requester, resource, environment, and action. The plasma scenarios for > Advanced Policies should include the ability to convey attributes (labels) > about the message (including, but not limited to the policy identifier) and > attributes about the recipient. > > > > > > Scott Fitch > Cyber Architect > Lockheed Martin Enterprise Business Services > > > _______________________________________________ > plasma mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/plasma _______________________________________________ plasma mailing list [email protected] https://www.ietf.org/mailman/listinfo/plasma
