< Return to Calendar

* CTI TC Interoperabilty SC - Monthly Meeting (Conference Call)
Name * CTI TC Interoperabilty SC - Monthly Meeting (Conference Call)
Time Wednesday, 14 September 2016, 02:00pm to 02:30pm EDT
(Wednesday, 14 September 2016, 06:00pm to 06:30pm UTC)
Description

GoToMeeting Details sent via OOB Email.

Note:

  • I'm in the middle of switching from WebEx to GoToMeeting -
  • Please delete any WebEx based meetings from your Calendars.

 

Agenda

Agenda:

  • Decision Process for Interoperability Framework (e.g., Formal, Self-Certification)
    • OASIS CTI TC IO SC Certification Framework WG Kickoff Meeting - Doodle Poll sent to Interoperability SC Members
    • Agenda for Certification Framework WG Kickoff Meeting is to review, formalize, and frame the set of Certification Framework options for decision by the CTI TC.
      • (1) Uncontrolled self-certification: each candidate defines or uses its own test framework and test suite, and executes its own testing, without oversight. The testing is based on minimal test material produced by the TC, typically a set of test assertions and test guidelines. The candidate posts its test results, and remains open for particular inquiries from 3rd parties (e.g. customers) about test details. This option does not provide much guarantee – it is “user beware” – But is easiest to support by OASIS and TCs.
      • (2) Resource-based local self-certification: In this option, the testing is entirely done on the user side, but the resources necessary to do so are provided by the TC. The user downloads test framework components and test suites and runs them locally. WS-I is an example of this style of certification. This option provides more guarantee, as the tools and test suites are same for all candidates and are developed and validated by a third party.
      • (3) Service-based self-certification: In this option, testing is provided as a remote automated service. In addition to the test tools and test suite being developed by a third party, the core of the testing operation takes place on or is controlled by the service site, which is where test results are collected. A variant would allow the user to upload its implementation or part of it on the service site. In (b) and (c) 
  • Interoperability SC Github Repositories
  • Interim Ad Hoc Interoperability Initiative
  • RSA Interoperability Demonstration WG Update
  • Note: We have some important decisons to make.  Please RSVP  to indicate if you are planning to Attend


Submitter Patrick Maroney
GroupCTI Interoperability Subcommittee
Access This event is visible to CTI Interoperability Subcommittee and shared with
  • OASIS Open (General Membership)
  • General Public
  • OASIS Cyber Threat Intelligence (CTI) TC