Re: [Smart] New Version Notification for draft-mcfadden-smart-endpoint-taxonomy-for-cless-00.txt

Tony Rutkowski <rutkowski.tony@gmail.com> Mon, 08 July 2019 13:36 UTC

Return-Path: <rutkowski.tony@gmail.com>
X-Original-To: smart@ietfa.amsl.com
Delivered-To: smart@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF2C12022A for <smart@ietfa.amsl.com>; Mon, 8 Jul 2019 06:36:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.702
X-Spam-Level:
X-Spam-Status: No, score=-0.702 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, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 aANRoGxgD5oi for <smart@ietfa.amsl.com>; Mon, 8 Jul 2019 06:36:21 -0700 (PDT)
Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) (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 972FB120221 for <smart@irtf.org>; Mon, 8 Jul 2019 06:36:21 -0700 (PDT)
Received: by mail-qk1-x72b.google.com with SMTP id d15so13275083qkl.4 for <smart@irtf.org>; Mon, 08 Jul 2019 06:36:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=IjNhrg7W3w8KEcakDet3gLAzjUL+kJVLqgRHTCKFPRk=; b=a4rAEUdXUqz4WefKnoQFLxYlElTkfwfwy42nOLqFudZdO6mbGan8hpxYpcX3N4H4UT 0hNamZOs+1dMIV9PlVzCKtFiMcFwe7RbZV15ajicNquo5dK0rO190ueRmChNniS2L7i8 KSPWTHTDbeep9wc2SCtj9mG9V1yxspV/YHBH7CEYY2rvgd4vmbWOEalYHVpoTikH66H3 okmTp1QTwx9qlTHLfcZzDP0TLEfNrNnAr7DHd6N10VGQJtW4mabIDS+mgi1xhtkgyUJD CD8Osz3RXeJmJ9E5o3Z31rN6hCIJbbNO7ioakYaqjbg5ZdFz8p7Rs8MR/UlzCElAguCJ 80nA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=IjNhrg7W3w8KEcakDet3gLAzjUL+kJVLqgRHTCKFPRk=; b=MWAGhKLtehg42IXjMlttuvFRYlzjB5zTQdvolNkeJAWMY3CW2vDyKkoJXmNwymkDi1 sHKxGIeWzjS5VNAv+DGAWc15Mktwo0aZY+HhrFH98kc1Qz2UjomI1zPSz3mGyI9tMBT6 wceQPf/LrjvpYrefaxao+UkUfaer3LDO7ZaDZ0j8e3RQSuKUG5+MVGFe+2gRHML10XGl U3TX8LYYjV1G7fAi2m+7t/hnbf/UQgCiUI7vtqI5UP8CyFJBd2Zhl/MQVO//PN+Y46XF B+dHEzVHEpKr/vJuEN3csSrnKO9oWQSfjPOqQHCJBZhho00MWrPQyIpXn5uOCmDWji9n CeOQ==
X-Gm-Message-State: APjAAAVA0Xdj5PLPWk+1FCREFBLX63oq3DtsMk5TQjKLNUp1Etrsx+uL JUB61l8jCTUnP0bvkYNRxYYWDAxz
X-Google-Smtp-Source: APXvYqyGBIc4aWH0iIcZU7p5qz5He0w4qWViTSaplFgd7J8BR56mkWtoQqhTSeR0pzEhQrXUDhA2Eg==
X-Received: by 2002:a05:620a:1443:: with SMTP id i3mr14750397qkl.11.1562592980374; Mon, 08 Jul 2019 06:36:20 -0700 (PDT)
Received: from [192.168.1.53] (pool-70-106-252-118.clppva.fios.verizon.net. [70.106.252.118]) by smtp.gmail.com with ESMTPSA id b23sm8740264qte.19.2019.07.08.06.36.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Jul 2019 06:36:19 -0700 (PDT)
To: mark@internetpolicyadvisors.com, smart@irtf.org
References: <156259169027.840.9135095847874577233.idtracker@ietfa.amsl.com> <019f01d53590$cf8c2a50$6ea47ef0$@internetpolicyadvisors.com>
From: Tony Rutkowski <rutkowski.tony@gmail.com>
Message-ID: <5efde727-8e1d-9e9e-a9a4-32ce3f60e359@gmail.com>
Date: Mon, 08 Jul 2019 09:36:19 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <019f01d53590$cf8c2a50$6ea47ef0$@internetpolicyadvisors.com>
Content-Type: multipart/alternative; boundary="------------572A4D83BD28589F3D353DCF"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/smart/M2w8J3KQ_dOD_Irt8QvMkQfIGP0>
Subject: Re: [Smart] New Version Notification for draft-mcfadden-smart-endpoint-taxonomy-for-cless-00.txt
X-BeenThere: smart@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Stopping Malware And Researching Threats <smart.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/smart>, <mailto:smart-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/smart/>
List-Post: <mailto:smart@irtf.org>
List-Help: <mailto:smart-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/smart>, <mailto:smart-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jul 2019 13:36:32 -0000

> But, there's an important question here. CLESS specifically rules out 
> network infrastructure in its discussion. Should the taxonomy for 
> CLESS incorporate endpoints that are part of the network 
> infrastructure? Said a different way: is network infrastructure out of 
> scope for CLESS? 
Do you intend this to be 5G relevant?

-tr

On 08-Jul-19 9:26 AM, mark@internetpolicyadvisors.com wrote:
> A new version of I-D, draft-mcfadden-smart-endpoint-taxonomy-for-cless-00.txt
> has been successfully submitted by Mark McFadden and posted to the IETF repository.
>
> Name:		draft-mcfadden-smart-endpoint-taxonomy-for-cless
> Revision:	00
> Title:		Endpoint Taxonomy for CLESS
> Document date:	2019-07-08
> Group:		Individual Submission
> Pages:		15
> URL:            https://www.ietf.org/internet-drafts/draft-mcfadden-smart-endpoint-taxonomy-for-cless-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-mcfadden-smart-endpoint-taxonomy-for-cless/
> Htmlized:       https://tools.ietf.org/html/draft-mcfadden-smart-endpoint-taxonomy-for-cless-00
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-mcfadden-smart-endpoint-taxonomy-for-cless
>
>
> Abstract:
>     A separate document [I-D:draft-taddei-smart-cless-introduction]
>     (CLESS) attempts to establish the capabilities and limitations of
>     endpoint-only security solutions and explore potential alternative
>     approaches. That document discusses endpoints in general terms. It
>     has been suggested that there are classes of endpoints that have
>     different characteristics. Those classes may have completely
>     different threat landscapes and the endpoints may have completely
>     different security capabilities. In support of the work on CLESS,
>     this document provides a taxonomy of endpoints that is intended to
>     provide a foundation for further work on CLESS and research on
>     approaches to providing endpoint security alternatives in a diverse
>     group of settings.
>
>                                                                                    
>
>
> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>