IETF Logo Mail Archive

Re: [sacm] Question regarding Figure 2 in the SACM Architecture -00

Bill Munyan <bill.munyan.ietf@gmail.com> Wed, 12 September 2018 13:55 UTC

Return-Path: <bill.munyan.ietf@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81B82130E08 for <sacm@ietfa.amsl.com>; Wed, 12 Sep 2018 06:55:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VmdVhiUrZ3tt for <sacm@ietfa.amsl.com>; Wed, 12 Sep 2018 06:55:05 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C0421200D6 for <sacm@ietf.org>; Wed, 12 Sep 2018 06:55:05 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id m11-v6so3878384oic.2 for <sacm@ietf.org>; Wed, 12 Sep 2018 06:55:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4yPZzJhWpD79wyopJeEJlSnRP6me3eH0mknEiAVs/7I=; b=uILOFg4vCRxyJH0NtoxubOgL4W5HhiUwKcRvOL7AUYHyDEy3hz5WqzcsjAaZIeG2UI ShwFaFDohQ4Ua/AN/gcI6XFP1zC7Wjge6oASxvOSoZXzVw5ljBETmEsk8bARY+JCRSdg TaqUdAgCI1U19GvbXJtBNWprRiSdFS/WqHrIqvBwMPDVxk5Q1TRFomYqDMc9c6kj/uR8 SanKiB7b0Zsa3Jycgf8SWE6U5GNHTRS38R2iZnU6/Kf/ZWU9Ok01WfQpAa3Cm2s9zH2G kQAFIzwiTlho0nWePfUFYMpUQHw4Z11mK2EIujVyMiQy2Zls6GC9UIh5owbAoKjXC9Ax i2hg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4yPZzJhWpD79wyopJeEJlSnRP6me3eH0mknEiAVs/7I=; b=GPzRS3L5PoQSASJL52MF4MCL5CP5lU6sfxMwt5SXmuUuMa8Vp2XMhHkZ1y+9so74fI 2SqPmmgkof69M/fpIvatPyfKIrvOjiZEuV6IDYKpRTVoBhXCpK59FP/WpOwG4WJOZwgj uSnrRGwlMfPg+ifODoG33NduI+fn9F86FB9gUjuUNfAz4Az4piuS8JO7my8teY9n0tP4 Nh+YHLV25H98c2+9KVztjg7wX8Qb7fKnk3MEvhXtIoq4UiS3CDj3H6f8Uff52B7XmrUx GtMbLIQT5ESPmLmqDoPAAh7jR4xkZ4jPvKWFzIg+TUlLaoXZmRx1ahY4UOaB53Ut0w9W q+Rg==
X-Gm-Message-State: APzg51A3iY8/+X8iAqKoZ6IzCTkpZF03aT4PuA3oCWVM/nLErAdC1V+K g9rR8LDdNRSYAHTU9UFKGiAVkxOsTe0PjBkSf64=
X-Google-Smtp-Source: ANB0VdbxbVwLPsiiFb5JyR0Pk34HOAo8eBJj1zrgYsayJqi4cdG47m3fgrBqlfRLQVrVtG66NA8Bjahf0u2DJN+cbbE=
X-Received: by 2002:a54:4f88:: with SMTP id g8-v6mr2167550oiy.191.1536760504405; Wed, 12 Sep 2018 06:55:04 -0700 (PDT)
MIME-Version: 1.0
References: <BN7PR09MB2913B4791EE81204562DBE96AB040@BN7PR09MB2913.namprd09.prod.outlook.com>
In-Reply-To: <BN7PR09MB2913B4791EE81204562DBE96AB040@BN7PR09MB2913.namprd09.prod.outlook.com>
From: Bill Munyan <bill.munyan.ietf@gmail.com>
Date: Wed, 12 Sep 2018 09:54:56 -0400
Message-ID: <CAKUOEQyFVaKctsAdidUxAArbE+Nw3RvBODgrN5PAqjHh4DsPTg@mail.gmail.com>
To: cmschmidt@mitre.org
Cc: "<sacm@ietf.org>" <sacm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f8530e0575acef3c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/zQcQrBt2yPJSJBhG9LqIaP3WVCg>
Subject: Re: [sacm] Question regarding Figure 2 in the SACM Architecture -00
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Sep 2018 13:55:07 -0000

Charles,
Thanks for the question.  I think the intent of figure 2 is to provide
notional examples of the fact that there could be many different endpoint
attribute collection systems representing various types of posture
collection, such as asset inventory, configuration and vulnerability
management.  EPCP is one such collection system (and is diagrammed as a
pointer to asset inventory) and the box for that in the diagram should
represent an entire EPCP implementation, as per that spec (including
posture collection manager, posture collectors, posture validators, etc).
Another example, labeled "datastream" is meant to represent those
collectors able to interpret SCAP datastreams, collect system
characteristics, etc.  The idea is that many disparate collection systems
may collect endpoint posture attributes in their own way, and would thus
need a set of interfaces (the "XMPP Grid Connector") to publish that
information to the message transfer system (XMPP with Pub/Sub for example).

If the labeling is off or misleading, we'd be happy to get consensus on
what would be the clearest label.

Cheers,
-Bill M.


On Tue, Sep 11, 2018 at 3:59 PM Schmidt, Charles M. <cmschmidt@mitre.org>
wrote:

> Hello,
>
>
>
> A quick question regarding Figure 2 in the SACM Architecture -00 draft: It
> looks like there is a connection between “SWIMA” and an XMPP-Grid
> connector. By “SWIMA” do you mean a “NEA Server”? I could certainly see a
> NEA server interacting with an XMPP Grid Connector. I’m less convinced of
> there being a SWIMA PV or a SWIMA PC having a direct connection to a
> Connector.
>
>
>
> For that matter, NEA Server might be an appropriate word to use for the
> ECP as well, since ECP is also multi-component, and some of those
> components probably don’t need direct interactions with Connectors.
>
>
>
> Thoughts?
>
>
>
> Charles
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm
>

v2.23.0 | Report a Bug | By Email