<?xml version="1.0" encoding="UTF-8"?>
<PerformancePlanOrReport xmlns="urn:ISO:std:iso:17469:tech:xsd:PerformancePlanOrReport" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

 xsi:schemaLocation="urn:ISO:std:iso:17469:tech:xsd:PerformancePlanOrReport http://stratml.us/references/PerformancePlanOrReport20160216.xsd" Type="Strategic_Plan"><Name>Security Algorithms and Methods (SAM)</Name><Description>The SAM TC works to deliver the following business benefits:

* Enable referencing of existing and emerging algorithms and methods for utilisation in other standards work (including multiple OASIS TCs)

* Enable referencing of existing and emerging algorithms and methods, so that they can be used in an interoperable way

* Provide a faster path to the registration than existing methods such as NIST and the IETF</Description><OtherInformation>Note: SAM TC does not seek to replace the work of other standards bodies, merely to provide a fast path to referencing the information.</OtherInformation><StrategicPlanCore><Organization><Name>Organization for the Advancement of Structured Information Standards</Name><Acronym>OASIS</Acronym><Identifier>_81300f81-424c-472b-bae9-f7f70b7420b4</Identifier><Description/><Stakeholder StakeholderTypeType="Generic_Group"><Name>Organisations</Name><Description>Many organisations are unable to comply with a range of standards that deal with cryptographic algorithms or methods because there are a number of algorithms and methods that are not documented in a manner readily referenced by implementers. </Description></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>SAM Technical Committee</Name><Description>The SAM Technical Committee will develop a set of documents to aid in the interoperability of implementations implementing cryptographic capabilities in support of OASIS and other standards and specifications. The TC’s work products will allow for the earlier adoption of existing and emerging security algorithms and approaches and to provide other technical committees a path to adoption where those defining the algorithms, mechanisms and methods are themselves not focused on or interested in the formal standardisation process.</Description></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>SAM Stakeholders</Name><Description>SAM is intended for the following audiences:

Architects, designers, and implementers of providers and consumers of systems or services that need to utilise cryptographic algorithms, methods, or objects.</Description></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>SAM-Related Efforts</Name><Description>Identification of Similar Work -- 
* National Institute of Standards and Technology (NIST) - https://csrc.nist.gov/Projects/Cryptographic-Standards-and-Guidelines
* Internet Engineering Task Force (IETF), Security Area (sec) - https://www.ietf.org/topics/areas/
* International Standards Organisation (ISO), JTC1, SC27 - https://www.iso.org/committee/45306.html</Description></Stakeholder><Stakeholder StakeholderTypeType="Organization"><Name>National Institute of Standards and Technology (NIST)</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Organization"><Name>Internet Engineering Task Force (IETF)</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Organization"><Name>International Standards Organisation (ISO)</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>SAM TC Proposers</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Person"><Name>Tony Cox</Name><Description>Cryptsoft -- TC Convener</Description></Stakeholder><Stakeholder StakeholderTypeType="Person"><Name>Tim Hudson</Name><Description>Cryptsoft</Description></Stakeholder><Stakeholder StakeholderTypeType="Person"><Name>Jason Thatcher</Name><Description>Cryptsoft</Description></Stakeholder><Stakeholder StakeholderTypeType="Person"><Name>Tim Chevalier</Name><Description>NetApp</Description></Stakeholder><Stakeholder StakeholderTypeType="Person"><Name>Judy Furlong</Name><Description>Dell</Description></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>SAM TC Primary Representatives</Name><Description>Primary Representatives' Support</Description></Stakeholder><Stakeholder StakeholderTypeType="Person"><Name>Tim Hudson</Name><Description>as OASIS primary representative for Cryptsoft Pty Ltd, confirms our support for the proposed SAM TC charter and endorses our participants listed above.</Description></Stakeholder><Stakeholder StakeholderTypeType="Person"><Name>Judy Furlong</Name><Description>as OASIS primary representative for Dell, confirms our support for the proposed SAM TC charter and endorses our participants listed above.</Description></Stakeholder><Stakeholder StakeholderTypeType="Person"><Name>David Dale</Name><Description>as OASIS primary representative for NetApp Inc., confirms our support for the proposed SAM TC charter and endorses our participants listed above.</Description></Stakeholder></Organization><Vision><Description>Cryptographic algorithms and methods can be used in an interoperable way</Description><Identifier>_13bfd978-9d10-11ea-98c6-07092f83ea00</Identifier></Vision><Mission><Description>To aid in the interoperability of implementations implementing cryptographic capabilities</Description><Identifier>_13bfdb26-9d10-11ea-98c6-07092f83ea00</Identifier></Mission><Value><Name>Cryptography</Name><Description/></Value><Value><Name>Interoperability</Name><Description/></Value><Value><Name>Implementation</Name><Description/></Value><Goal><Name>References</Name><Description>Provide a standardised set of references that can be used in other OASIS technical committees or where the standards are not yet defined by another recognised standards body.</Description><Identifier>_13bfdcca-9d10-11ea-98c6-07092f83ea00</Identifier><SequenceIndicator/><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>The primary goal of the SAM Technical Committee is to provide a standardised set of references of algorithms, mechanisms, and methods, including test-vectors, that can be used in other OASIS technical committees or where the standards are not yet defined by another recognised standards body.

Any analysis of the security properties of included cryptographic algorithms, methods, and objects contained in their specifications are out of scope...

The format of the SAM TC deliverables will be agreed upon by the SAM TC but will include sufficient documentation to:</OtherInformation><Objective><Name>Algorithms, Mechanisms &amp; Methods </Name><Description>Capture target algorithms, mechanisms and methods in sufficient detail to enable implementers to use the work to reliably reproduce interoperable implementations</Description><Identifier>_13bfdda6-9d10-11ea-98c6-07092f83ea00</Identifier><SequenceIndicator>1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Implementations</Name><Description>Test target algorithms, mechanisms and methods to ensure accurate implementations can be generated</Description><Identifier>_13bfde6e-9d10-11ea-98c6-07092f83ea00</Identifier><SequenceIndicator>2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Interoperability</Name><Description>Test target algorithms, mechanisms and methods to ensure implementations are interoperable</Description><Identifier>_13bfdf36-9d10-11ea-98c6-07092f83ea00</Identifier><SequenceIndicator>3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Definition</Name><Description>Define references sufficiently, so that they can be used by OASIS and other standards in the production of other interoperable systems.</Description><Identifier>_13bfe008-9d10-11ea-98c6-07092f83ea00</Identifier><SequenceIndicator>4</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Liaisons</Name><Description>Establish liaisons (as appropriate) with other organisations that perform similar work including those organisations.</Description><Identifier>_13bfe0d0-9d10-11ea-98c6-07092f83ea00</Identifier><SequenceIndicator>5</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal></StrategicPlanCore><AdministrativeInformation><StartDate>2020-05-21</StartDate><EndDate/><PublicationDate>2020-05-23</PublicationDate><Source>https://www.oasis-open.org/news/announcements/call-for-participation-security-algorithms-and-methods-sam-tc</Source><Submitter><GivenName>Owen</GivenName><Surname>Ambur</Surname><PhoneNumber/><EmailAddress>Owen.Ambur@verizon.net</EmailAddress></Submitter></AdministrativeInformation></PerformancePlanOrReport>