IETF Logo Mail Archive

Re: [sacm] ECP Architecture Diagram Feedback

"Haynes Jr., Dan" <dhaynes@mitre.org> Tue, 03 April 2018 18:37 UTC

Return-Path: <dhaynes@mitre.org>
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 DCD8112EA52 for <sacm@ietfa.amsl.com>; Tue, 3 Apr 2018 11:37:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.208
X-Spam-Level:
X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mitre.onmicrosoft.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 rDCwSfKBH97q for <sacm@ietfa.amsl.com>; Tue, 3 Apr 2018 11:37:01 -0700 (PDT)
Received: from smtpvmsrv1.mitre.org (smtpvmsrv1.mitre.org [192.52.194.136]) by ietfa.amsl.com (Postfix) with ESMTP id 13CEA124BE8 for <sacm@ietf.org>; Tue, 3 Apr 2018 11:37:01 -0700 (PDT)
Received: from smtpvmsrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 0CFF06C009D; Tue, 3 Apr 2018 14:37:02 -0400 (EDT)
Received: from imshyb01.MITRE.ORG (unknown [129.83.29.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by smtpvmsrv1.mitre.org (Postfix) with ESMTPS id EF8E26C0091; Tue, 3 Apr 2018 14:37:01 -0400 (EDT)
Received: from imshyb01.MITRE.ORG (129.83.29.2) by imshyb01.MITRE.ORG (129.83.29.2) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 3 Apr 2018 14:37:00 -0400
Received: from GCC01-CY1-obe.outbound.protection.outlook.com (10.140.19.249) by imshyb01.MITRE.ORG (129.83.29.2) with Microsoft SMTP Server (TLS) id 15.0.1263.5 via Frontend Transport; Tue, 3 Apr 2018 14:37:00 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mitre.onmicrosoft.com; s=selector1-mitre-org; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=pPonZY5jbmgleYN8GZ7+uhVtzrt0aaCalkFe/46uTK0=; b=CgPqcIugY7bg7+LxVqfavxMTGiSMgapK/egRQCL6xwtt0MlM5aXpvWUGZy7hVOtI2MP+6KqprWwGF3ssMWzXH+XpRaYxk8yPMr0OARrYR//Ea7C/06Qj5/OhAp1lCk3kA1wHntQJ3//LjNTgIJjSNLgZAv/tV9BcARm88SPSINQ=
Received: from DM5PR0901MB2197.namprd09.prod.outlook.com (10.167.106.167) by DM5PR0901MB2200.namprd09.prod.outlook.com (10.167.110.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.631.10; Tue, 3 Apr 2018 18:36:58 +0000
Received: from DM5PR0901MB2197.namprd09.prod.outlook.com ([fe80::e550:42b2:7e29:134b]) by DM5PR0901MB2197.namprd09.prod.outlook.com ([fe80::e550:42b2:7e29:134b%13]) with mapi id 15.20.0631.013; Tue, 3 Apr 2018 18:36:58 +0000
From: "Haynes Jr., Dan" <dhaynes@mitre.org>
To: "Montville, Adam W" <adam.w.montville@gmail.com>
CC: "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: [sacm] ECP Architecture Diagram Feedback
Thread-Index: AdPKr9yz9kq0dQvQQLu6DiaYCmftPQACXycAADAUbYA=
Date: Tue, 03 Apr 2018 18:36:58 +0000
Message-ID: <DM5PR0901MB2197CA6B3C285DD17A0D1C04A5A50@DM5PR0901MB2197.namprd09.prod.outlook.com>
References: <DM5PR0901MB2197070C2CF8BA9A4283251CA5A60@DM5PR0901MB2197.namprd09.prod.outlook.com> <D0D3E5A5-2D22-4B3A-AD3E-27386CC43887@gmail.com>
In-Reply-To: <D0D3E5A5-2D22-4B3A-AD3E-27386CC43887@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.160.51.88]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR0901MB2200; 7:ewDUiRUqsYGvxfsCYQfFfHBd/wMV7E8hLGDc1oXmJytCqN4PCYQFBhJCdQuPaJ4Daj6P6M8+M7rktvi2Edm/AFdErmaTOLlD30w7Gvp40mdGVTGO0VXwkFap1L0Y/7AwRCqxD7KLoF3hO5e3b5W7dfYPNbE5p9AiRUQsbvgle1/Njpt/1yDLk07evP+fUCptpQ/I53MuWnGvafiketqAe7pYygUOVtUJRyWIbHXr05ZvAlcms2O0ZJxPOoA0529N
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: dc3fa335-f646-4a9b-2751-08d59991e255
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:DM5PR0901MB2200;
x-ms-traffictypediagnostic: DM5PR0901MB2200:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=dhaynes@mitre.org;
x-ld-processed: c620dc48-1d50-4952-8b39-df4d54d74d82,ExtAddr
x-microsoft-antispam-prvs: <DM5PR0901MB2200FA823E72C381F177E3A1A5A50@DM5PR0901MB2200.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(120809045254105)(85827821059158)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(3231221)(944501327)(52105095)(6055026)(6041310)(20161123560045)(20161123564045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(6072148)(201708071742011); SRVR:DM5PR0901MB2200; BCL:0; PCL:0; RULEID:; SRVR:DM5PR0901MB2200;
x-forefront-prvs: 0631F0BC3D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(346002)(366004)(396003)(39380400002)(39860400002)(199004)(189003)(53754006)(25786009)(76176011)(2900100001)(7696005)(8936002)(26005)(59450400001)(186003)(106356001)(3846002)(11346002)(7736002)(39060400002)(6116002)(316002)(6506007)(790700001)(6246003)(33656002)(9326002)(3280700002)(2906002)(99286004)(486006)(606006)(446003)(68736007)(3660700001)(81166006)(81156014)(97736004)(102836004)(6916009)(229853002)(53546011)(86362001)(5250100002)(8676002)(66066001)(105586002)(55016002)(6436002)(476003)(478600001)(9686003)(14454004)(5660300001)(74316002)(4326008)(236005)(54896002)(6306002)(966005)(53936002)(19609705001); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR0901MB2200; H:DM5PR0901MB2197.namprd09.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: mitre.org does not designate permitted sender hosts)
x-microsoft-antispam-message-info: QqeHbZj272vvDLrjSL/nXCTU9Uiuwo6eUP6j3hvXvsaeGEJ8hzdfqyjH3iWpxczrFooEyGXbScN+Wn+IbBMKEJKPRlbY+vx+ICztrBvppn8kgLa2Rs+Mi+GYD4WVgticee/7YRVyYXObH9O7ghMlO7kU6bv83JMZn4MH/I22QuTlfWb4k2wCjySlwKe73P27+76j+n05o4B5JOcGsFB724p5k5zPGkx+RgoYKd59mw/d4ILAU265d/YVOBFMOBUeLgfKoRsPOsG8IpOwZvGBCMZFWdfq90ODAKCDpdruaiNMSvl1Vi3+AbloAqHhUUowDr6q2ex+MmRXewFBR4jIKie4HRHugDYBK5Lb3slbU9VGnVeDqP3GsL9z8B0OQ8HxO+VTzQmv0SA7lWfoAytSOUli6Dq1T9bvLg2xRhIcCIM=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM5PR0901MB2197CA6B3C285DD17A0D1C04A5A50DM5PR0901MB2197_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: dc3fa335-f646-4a9b-2751-08d59991e255
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Apr 2018 18:36:58.8551 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: c620dc48-1d50-4952-8b39-df4d54d74d82
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR0901MB2200
X-OriginatorOrg: mitre.org
X-MITRE: 8GQsMWxq66rxk57w
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/3U_HR_DB8AyMzEC28zkhEdQXt_Q>
Subject: Re: [sacm] ECP Architecture Diagram Feedback
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 03 Apr 2018 18:37:04 -0000

Hi Adam,

I hope it was a good trip out there and that you were able to see some of the sights!

As far as scoping and the diagram, I think it's worth nothing that all the components in it are in scope for ECP. It is just a matter of when we actually get to creating drafts for them (if that makes any sense). I think what you are looking for is a diagram that shows what we are currently working on? Or, maybe I am misunderstanding your comments?

Thanks,

Danny

From: Adam Montville [mailto:adam.w.montville@gmail.com]
Sent: Monday, April 02, 2018 3:33 PM
To: Haynes Jr., Dan <dhaynes@mitre.org>
Cc: sacm@ietf.org
Subject: Re: [sacm] ECP Architecture Diagram Feedback

Hi Danny,

We missed you in London. I think the diagram is ok, but I do have scoping questions (just sent to the list) which may suggest some modification to the diagram once resolved. If the way I'm interpreting the ECP draft at this point is close to accurate, then it might be a good idea to add a horizontal scoping line between the left hand and the right hand of the diagram, where the posture manager is the first component on the right-hand side. Alternatively, an in-scope boundary box could be drawn around the appropriate components.

What really matters is whether the diagram accurately depicts the intended scope of the draft from the authors' perspectives, and whether a typical reader would see it that way.

Adam


On Apr 2, 2018, at 1:32 PM, Haynes Jr., Dan <dhaynes@mitre.org<mailto:dhaynes@mitre.org>> wrote:

Hi Everyone,

At IETF 101, we presented an updated architecture diagram [1] that was based on feedback from the September virtual interim [2][3] and was included in the ECP -01 draft [4]. During the meeting, we did not receive any feedback on the architecture diagram.

As a result, we just wanted to follow-up on the list and see if there was any feedback or objections to the updated ECP architecture diagram that was proposed.

Thanks,

Danny


[1] https://datatracker.ietf.org/meeting/101/materials/slides-101-sacm-endpoint-compliance-profile-00 (see slide 4)
[2] https://datatracker.ietf.org/doc/slides-interim-2017-sacm-03-sessa-ecp/00/ (see slide 5)
[3] https://datatracker.ietf.org/meeting/interim-2017-sacm-03/materials/minutes-interim-2017-sacm-03-201709260900-00 (see page 1 and 2)
[4] https://datatracker.ietf.org/doc/draft-ietf-sacm-ecp/

_______________________________________________
sacm mailing list
sacm@ietf.org<mailto:sacm@ietf.org>
https://www.ietf.org/mailman/listinfo/sacm

v2.23.0 | Report a Bug | By Email