Was discussed quickly during the last meeting:
- The mobile domain (iOS, Android, Windows Mobile...)
I just read the slides of the meeting of September 24 2015 (sorry was
not available), and see:
- "Support capture of endpoint system state data"
It was highlighted by @Tony Rutkowski that some entities are working,
and have been working for years, on these domains.
I strongly suggest, as it is clear that it was done before for the
objects we have today, to work with SMEs of these domains. It is in
our interest to not reinvent the wheel.
Many of us are participating in different groups outside OASIS.
I would be greatly beneficial to try to identify and collaborate with
the most 'mature' SMEs.
@Tony already shared a slide (attached for reference) of the ecosystem.
Based on personal judgment, i would STRONGLY suggest a liaison with
these entities for the following domains (and I invite people with
more deep knowledge regarding work/'maturity' of other entities to
complete or comment this list):
- Mobile domain: 3GPP, ETSI TC Cyber
- Endpoint identification and state: IETF SACM
I would appreciate the Interoperability TC to have an action plan
regarding liaisons.
Added for reference:
@Chet highlighted:
"The details are in the Liaison Policy section on TC liaisons here ->
https://www.oasis-open.org/policies-guidelines/liaison#liaisons
In a nutshell though, the process is: (a) identify a member of the TC
who will act as the liaison. Usually this is someone who is a member
of both organizations. (b) Approve that person as liaison by a motion
in a TC meeting or by an electronic ballot. (c) Notify the OASIS
President (Laurent - and cc me). (d) Post the person's name and
liaison organization on the TC's web page. Then that person (or
persons) can act as intermediary between the two organizations to keep
each other apprised of one another's work, help identify related
content, etc. etc. "
Thank you
Best regards
/JA