Re: [sacm] [sacmwg/draft-ietf-sacm-information-model] Section 6: No software, no hardware...no endpoint? (#80)

cliffordk <notifications@github.com> Tue, 20 June 2017 18:21 UTC

Return-Path: <bounces+848413-495d-sacm=ietf.org@sgmail.github.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 2391C1315C6 for <sacm@ietfa.amsl.com>; Tue, 20 Jun 2017 11:21:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.801
X-Spam-Level:
X-Spam-Status: No, score=-4.801 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 HvK8oRFsPkBb for <sacm@ietfa.amsl.com>; Tue, 20 Jun 2017 11:21:33 -0700 (PDT)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 B95EB1315CD for <sacm@ietf.org>; Tue, 20 Jun 2017 11:21:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=NcDHUKHXsFnUAcHTij2nne7CUTw=; b=NSacLpWftMlTAo0J vBg5OvcezrDwT827vvA/GMdcy5ZeLESXUpCG+LH62vsk+PqoFVYMKI08FW0uwCMX I8eBIA+GOW9QarorVW0FTQLFlsOqVQR4vIBeuPBLfBbHijqkRkN+CqxYWZVxmYPt LviZCysIHKkdoYyFG6y6lnNZ+rI=
Received: by filter1182p1mdw1.sendgrid.net with SMTP id filter1182p1mdw1-17845-594967AA-30 2017-06-20 18:21:30.605792581 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id -y0Vhnl4SRy94_30V6yIrw for <sacm@ietf.org>; Tue, 20 Jun 2017 18:21:30.594 +0000 (UTC)
Date: Tue, 20 Jun 2017 11:21:30 -0700
From: cliffordk <notifications@github.com>
Reply-To: sacmwg/draft-ietf-sacm-information-model <reply+00a6c4d1c410686cec064552fa6109ac3b88af4f29cfbded92cf00000001156129aa92a169ce0e24668d@reply.github.com>
To: sacmwg/draft-ietf-sacm-information-model <draft-ietf-sacm-information-model@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <sacmwg/draft-ietf-sacm-information-model/issues/80/309844991@github.com>
In-Reply-To: <sacmwg/draft-ietf-sacm-information-model/issues/80@github.com>
References: <sacmwg/draft-ietf-sacm-information-model/issues/80@github.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_594967aa66c98_22c043fd61c7bfc3c93350"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: cliffordk
X-GitHub-Recipient: sacm
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: sacm@ietf.org
X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H9jDTk3nqFsaQ6Kd3Ez6nBkxPXCmLyBpSCQQ6HxCfxoxzzs+gl1PfRFZnD C3MVapx+7WVIWyGPEUqBPzybVMnIY9sIvOcRBwdSbJlinttk2O88Y/V0Ch12sNkOyQ4Cb3RPrdFgzz jq2A00YKR1z5nab8sg1xRAWjct6TN00l6fJ/3WNvaRF3xvCcJL6U9wTIlw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/6EBbnvc9ARMqrs6gEK4r2dNRme8>
Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-information-model] Section 6: No software, no hardware...no endpoint? (#80)
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 20 Jun 2017 18:21:37 -0000

Hello, Adam.

It’s a fair question.

Not every hardware or software component will have been observed by a SACM sensor.

The paragraph says that an endpoint might have no hardware or software components known to SACM sensors. That’s not quite the same as what you said, Adam.

SACM sensors could know about an endpoint because they see traffic to and from its MAC address. SACM sensors might not know the components of the endpoint at all.

I think it’s useful to model an endpoint even if its components are wholly unknown. Other sensors could respond by probing to learn more about the endpoint, for example.

Best,
                                                Cliff

From: adammontville <notifications@github.com>
Reply-To: sacmwg/draft-ietf-sacm-information-model <reply@reply.github.com>
Date: Tuesday, June 20, 2017 at 12:12 PM
To: sacmwg/draft-ietf-sacm-information-model <draft-ietf-sacm-information-model@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [sacmwg/draft-ietf-sacm-information-model] Section 6: No software, no hardware...no endpoint? (#80)


The paragraph above figure 15 in section 6 (and figure 15 as well) describes an endpoint as having zero or more hardware components and zero or more software components, where each may have zero or more running instances.

...the make up of an Endpoint asset which contains zero or more hardware components and zero or more software components each of which may have zero or more instances running...

This feels incorrect, because it defines an endpoint as being capable of having neither hardware nor software, but (as mentioned elsewhere in the draft) is network addressable. Is it possible to have an endpoint without hardware and without software? Even if academically so, what place does it have in our information model?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://github.com/sacmwg/draft-ietf-sacm-information-model/issues/80>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMcywqOQaHwmkdtnU8vAeyCMqZCb02aDks5sF-9ugaJpZM4N_0ew>.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/sacmwg/draft-ietf-sacm-information-model/issues/80#issuecomment-309844991