Subject: [sacm] draft 2 liaison - call for contributions for the SACM Information Model

From: "Romascanu, Dan (Dan)" <[email-masked]>
Date: Tue, 29 Apr 2014 11:57:15 +0000

Hi,

Please find below the Call For Contributions for the SACM Information Model with modifications as per the comments received.

While we incorporated most comments that we received, there are a couple of comments from Gunnar which de suggest to leave out:
-        Does "Endpoint Attribute Expression" refer to how to request certain attributes rather than how to express the set of those attributes?  Both are needed.
-        Will the recipients of this be aware of the distinction between Endpoint Identification and Endpoint Characterization?

Our proposal is to leave these as is, as defining terminology is beyond the scope of a liaison statement. We do provide a list of references that includes the terminology document, and if such terms are not clear the respective organization can reply with a request for clarification.

We shall discuss this shortly in the virtual interim meeting tomorrow.

Regards,

Dan

To: DMTF
      The Open Group
      The Open Management Group
      NIST
      OASIS
      ITU-T Study Groups 2 and 17
      ISO/IEC JTC1 SC7 (Software and systems engineering) and SC27 (IT Security techniques)
     TCG

From: IETF SACM WG - Adam Montville, Dan Romascanu (co-chairs)
Cc: Kathleen Moriarty (Security AD), Scott Mansfield (IETF liaison manager to the ITU-T)

The Security Automation and Continuous Monitoring (SACM) Working
Group in the IETF is chartered to define a set of standards to enable assessment
of endpoint posture [5].

Please find below a call for contributions for the SACM Information Model.
Although the work on use cases and requirements is not completed, we
believe that there is enough substance and stability in the existing work-in-
progress documents and that we should not serialize the process. We believe
that we need the future SACM information model to cover  at least the
following general areas:

  1) Endpoint Identification

  2) Endpoint Characterization

  3) Endpoint Attribute Expression/Representation

  4) Policy evaluation expression and results reporting

We invite interested parties to submit their potential contributions as
follows:

  1) Area being addressed (from the list above)

  2) Textual description of the proposed contribution

  3) References to freely available existing work (i.e.
specifications)

  4) Mapping of the proposed contribution to existing use cases [1]
and requirements [2] (terminology definitions in our use cases and
requirements can be found in [3])

The best way to submit contributions is by writing individual Internet-
Drafts, but to begin with emails to the SACM mailing list [4] work as well.

For the IETF perspective on Information Models see RFC 3444 [6].
An example of an Information Model developed in the IETF is RFC 5477 [7].

While SACM holds (virtual) interim meetings as needed, the next face-to-
face session is expected to take place during the 90th meeting of the
Internet Engineering Task Force which will take place in Toronto between
July 20-25, 2014.  During this session, we will discuss the
merits of potential contributions. The cut-off date to submit Internet-Drafts
for this meeting is July 4, 2014.

For further information, please contact one or both of the SACM chairs:
Adam Montville ([email-masked]<mailto:[email-masked]>) or Dan Romascanu
([email-masked]<mailto:[email-masked]>).

----
[1] http://datatracker.ietf.org/doc/draft-ietf-sacm-use-cases/

[2] http://datatracker.ietf.org/doc/draft-camwinget-sacm-requirements/

[3] http://datatracker.ietf.org/doc/draft-ietf-sacm-terminology/

[4] https://www.ietf.org/mailman/listinfo/sacm

[5] http://datatracker.ietf.org/wg/sacm/charter/

[6] http://www.rfc-editor.org/info/rfc3444

[7] http://www.rfc-editor.org/info/rfc5477