This wiki has undergone a migration to Confluence found Here
Difference between revisions of "March 13, 2018 PSAF Call"
Jump to navigation
Jump to search
| Line 57: | Line 57: | ||
*Mike walked through recent changes to Trust Framework for Federated Authorization. We've restructured the TF4FA from one volume with 2 Chapters into two separate volumes. Also working on a third volume for Audit, Provenance, and Blockchain. | *Mike walked through recent changes to Trust Framework for Federated Authorization. We've restructured the TF4FA from one volume with 2 Chapters into two separate volumes. Also working on a third volume for Audit, Provenance, and Blockchain. | ||
*Ballot document will follow PASS ACS format with a business, information, computational and engineering perspectives. In conformance with RM-ODP, business perspective is converted to enterprise viewpoint. Computational view is deemed out of scope. | *Ballot document will follow PASS ACS format with a business, information, computational and engineering perspectives. In conformance with RM-ODP, business perspective is converted to enterprise viewpoint. Computational view is deemed out of scope. | ||
| − | *Initial Policy Diagram model is a high level view of the 4 key classes from ISO TS 22600-2:2006: Policy class specialized into Basic, Meta, and Composite policy. TF4FA will focus on Basic policy class. | + | *Initial Policy Diagram model is a high level view of the 4 key classes from ISO TS 22600-2:2006: Policy class specialized into Basic, Meta, and Composite policy. TF4FA will focus on Basic policy class. Meta and Composite |
| + | *Second is the overarching Trust Model with the three types of Authority Domains: Jurisdictional, Organizational, and subject of care. Removed the Venn Diagram from the Federated Domain because the trust contract is no longer considered an integration of policies, but a bridging between two domains where the disclosing domain has the final say on whether the policies in the trust proposal from the requesting domain are acceptable, and executes the contract. | ||
Revision as of 17:17, 15 March 2018
Attendees
| . | Member Name | . | Member Name | . | Member Name | . | Member Name | |||
|---|---|---|---|---|---|---|---|---|---|---|
| . | John Moehrke Security Co-chair | x | Kathleen Connor Security Co-chair | . | Alexander Mense Security Co-chair | . | Trish Williams Security Co-chair | |||
| x | Christopher Shawn] Security Co-chair | x | Suzanne Gonzales-Webb | x | Mike Davis | . | David Staggs | |||
| . | Mohammed Jafari | x | Beth Pumo | . | Ioana Singureanu | . | Rob Horn | |||
| x | Diana Proud-Madruga | x | Francsico Jauregui | . | Joe Lamy | . | Galen Mulrooney | |||
| . | Paul Knapp | . | Grahame Grieve | . | Johnathan Coleman | . | Aaron Seib | |||
| . | Ken Salyards | x | Jim Kretz | . | Gary Dickinson | x | Dave Silver | |||
| . | Oliver Lawless | . | [1] | . | David Tao | . | Greg Linden |
Agenda
- (3 min) Roll Call, Agenda Approval
- (5 min) Review and Approval of the March 6th Minutes
- (50 min) TF4FA Ballot Work Session - Mike Davis and Chris Shawn
Minutes
- Chris Chaired
- Agenda and Minutes were reviewed. Kathleen moved, Mike seconded. 7-0-0.
- Mike walked through recent changes to Trust Framework for Federated Authorization. We've restructured the TF4FA from one volume with 2 Chapters into two separate volumes. Also working on a third volume for Audit, Provenance, and Blockchain.
- Ballot document will follow PASS ACS format with a business, information, computational and engineering perspectives. In conformance with RM-ODP, business perspective is converted to enterprise viewpoint. Computational view is deemed out of scope.
- Initial Policy Diagram model is a high level view of the 4 key classes from ISO TS 22600-2:2006: Policy class specialized into Basic, Meta, and Composite policy. TF4FA will focus on Basic policy class. Meta and Composite
- Second is the overarching Trust Model with the three types of Authority Domains: Jurisdictional, Organizational, and subject of care. Removed the Venn Diagram from the Federated Domain because the trust contract is no longer considered an integration of policies, but a bridging between two domains where the disclosing domain has the final say on whether the policies in the trust proposal from the requesting domain are acceptable, and executes the contract.
