Re: [sacm] ECP Architecture Diagram Feedback

Adam Montville <adam.w.montville@gmail.com> Wed, 04 April 2018 13:42 UTC

Return-Path: <adam.w.montville@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 CD8BA127601 for <sacm@ietfa.amsl.com>; Wed, 4 Apr 2018 06:42:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, 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 JdY6z0LhrPUC for <sacm@ietfa.amsl.com>; Wed, 4 Apr 2018 06:42:20 -0700 (PDT)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (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 140D0129C70 for <sacm@ietf.org>; Wed, 4 Apr 2018 06:42:19 -0700 (PDT)
Received: by mail-qk0-x235.google.com with SMTP id o64so22475508qkl.7 for <sacm@ietf.org>; Wed, 04 Apr 2018 06:42:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=x6DqdECq8rtsV2m64er2AsIAkbZBIvcRQdHSAkkadsU=; b=H1aJeF1IGtPF8Y/mAISGZqQSfwN3iDKDzIuLnlfeAEjYj/IiGFbN3dA3FKYhmmsUbw jZepjElBWV4ZT3YJ54U6wQOJvWtt3NXRYVJmg4/QSnKc32KbE3+CZ9jluWOSI/0kgeUm ydPY+x43XkCxHNKtv9+LrwHsYqD7oQKdjQxRU8dBn6wB0o5EA8qZZwM4Qy8TwkX2CJI4 MOAlyMvyNz3dCaMgS9aLdnlWGyg+9fHEAdKYlKDPTiBXjG1Lrjzg2ObB1vvyB8PPL13L bm1FMbW2uT9xqwe4uQO3r3bq7f966axZ68b2UhfvZtZsVhWpnCje/4YiKJT+Raj6IqNj lBwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=x6DqdECq8rtsV2m64er2AsIAkbZBIvcRQdHSAkkadsU=; b=MLznrepUAQ8y77IIRiiwAh0LITxdoZHXFWUA8rgmEA0qC4vFS25qD9GhZDEJbEkhZG pVUcf5XR8Efd2vYy/WCtGAfZLMuh3YIcK0fEZPHlFbKSregQ1X47hR3M+Zbnc8z+JOD0 30pKmT8o5fFGYjzyJZtIf9HRqSIMe/tUwjrSIa+9oMKtEZJfu6x9tLkyWqF/vTZavamh Ie2l2rafVzbJprkW9Q/Hzin52b636gkHhBko0Df4wiPA4rOSkWywDkVj3oLBmvNXYkDf BKJYH/AKut+6cYid66kbmSPWtAYdtahRqJExK6fcxcEUWpR5ovpqPkoWYZZlRhCw9BXR sSBA==
X-Gm-Message-State: ALQs6tDeVImehy9RVhDt7iKjGqfGkiKfSKnWR0Jwx9BNAQ8zp5H2WH1M ILZTeDBreI2mBaAl0hoGiUw=
X-Google-Smtp-Source: AIpwx49/TdA2A0URA81qBeZEvvcPaZO4+2DHi3ciQHYhLG/AEAjSxpKnEsD7HaCVtZsL4tdNqIKoyQ==
X-Received: by 10.55.75.205 with SMTP id y196mr25007143qka.44.1522849338119; Wed, 04 Apr 2018 06:42:18 -0700 (PDT)
Received: from macbook-3.lan (99-64-100-131.lightspeed.austtx.sbcglobal.net. [99.64.100.131]) by smtp.gmail.com with ESMTPSA id v14sm3683855qto.33.2018.04.04.06.42.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Apr 2018 06:42:17 -0700 (PDT)
From: Adam Montville <adam.w.montville@gmail.com>
Message-Id: <4F142E0D-1A4D-4BE9-9BC2-B72EDFFB2470@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9DE0B7E6-DCB3-4956-AFF9-421AA6A4F463"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Wed, 04 Apr 2018 08:42:15 -0500
In-Reply-To: <DM5PR0901MB2197A974B3AA9CEDB6435267A5A40@DM5PR0901MB2197.namprd09.prod.outlook.com>
Cc: "sacm@ietf.org" <sacm@ietf.org>
To: "Haynes Jr., Dan" <dhaynes@mitre.org>
References: <DM5PR0901MB2197070C2CF8BA9A4283251CA5A60@DM5PR0901MB2197.namprd09.prod.outlook.com> <D0D3E5A5-2D22-4B3A-AD3E-27386CC43887@gmail.com> <DM5PR0901MB2197CA6B3C285DD17A0D1C04A5A50@DM5PR0901MB2197.namprd09.prod.outlook.com> <578CB48E-1386-457B-81B9-EF0543F024FC@gmail.com> <DM5PR0901MB2197A974B3AA9CEDB6435267A5A40@DM5PR0901MB2197.namprd09.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/hm1Ssp2OSuUMc1G4nhel8VJRPpM>
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: Wed, 04 Apr 2018 13:42:24 -0000


> On Apr 4, 2018, at 8:18 AM, Haynes Jr., Dan <dhaynes@mitre.org> wrote:
> 
> Hi Adam,
>  
> What type of information are you looking for to make these components more explicit?

On a separate thread, I offered to attempt a scope statement of some kind (as well as helping to trim things back a bit). Let's leave this portion of the conversation in that thread?

>  
> Thanks,
> 
> Danny
>  
> From: Adam Montville [mailto:adam.w.montville@gmail.com] 
> Sent: Wednesday, April 04, 2018 9:00 AM
> To: Haynes Jr., Dan <dhaynes@mitre.org>
> Cc: sacm@ietf.org
> Subject: Re: [sacm] ECP Architecture Diagram Feedback
>  
> That helps, Danny, but then my comment about the ECP draft would change. As I read it, I do not take some of those components as being in scope (maybe some requirements for a cooperating component, but not - strictly speaking - in scope for ECP). If components such as the orchestrator and the repository are to be taken as in scope, it feels like that could be made more explicit.
>  
> Maybe I'm the only one who sees it this way?
>  
> Adam
>  
> On Apr 3, 2018, at 1:36 PM, Haynes Jr., Dan <dhaynes@mitre.org <mailto:dhaynes@mitre.org>> wrote:
>  
> 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 <mailto:adam.w.montville@gmail.com>] 
> Sent: Monday, April 02, 2018 3:33 PM
> To: Haynes Jr., Dan <dhaynes@mitre.org <mailto:dhaynes@mitre.org>>
> Cc: sacm@ietf.org <mailto: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 <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/ <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 <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/ <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 <https://www.ietf.org/mailman/listinfo/sacm>