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

<mark@internetpolicyadvisors.com> Mon, 08 July 2019 13:47 UTC

Return-Path: <mark@internetpolicyadvisors.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 168601201B3 for <smart@ietfa.amsl.com>; Mon, 8 Jul 2019 06:47:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level:
X-Spam-Status: No, score=-1.988 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_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=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=internetpolicyadvisors.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 XKYrphVuExEL for <smart@ietfa.amsl.com>; Mon, 8 Jul 2019 06:47:21 -0700 (PDT)
Received: from beige.elm.relay.mailchannels.net (beige.elm.relay.mailchannels.net [23.83.212.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF1D412003F for <smart@irtf.org>; Mon, 8 Jul 2019 06:47:20 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|mark@internetpolicyadvisors.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 9F955142396; Mon, 8 Jul 2019 13:47:19 +0000 (UTC)
Received: from pdx1-sub0-mail-a7.g.dreamhost.com (100-96-92-193.trex.outbound.svc.cluster.local [100.96.92.193]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 3B6361420A3; Mon, 8 Jul 2019 13:47:14 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|mark@internetpolicyadvisors.com
Received: from pdx1-sub0-mail-a7.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.17.3); Mon, 08 Jul 2019 13:47:19 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|mark@internetpolicyadvisors.com
X-MailChannels-Auth-Id: dreamhost
X-Illegal-Battle: 43c6ba4a6a2f8e9c_1562593634747_3521782982
X-MC-Loop-Signature: 1562593634747:2362539485
X-MC-Ingress-Time: 1562593634747
Received: from pdx1-sub0-mail-a7.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a7.g.dreamhost.com (Postfix) with ESMTP id 0DAF182AF5; Mon, 8 Jul 2019 06:47:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d= internetpolicyadvisors.com; h=reply-to:from:to:references :in-reply-to:subject:date:message-id:mime-version:content-type; s=internetpolicyadvisors.com; bh=ThAKf6cteM4CMVLI8cQKto+a+zE=; b= cQyqYC6aV+PZNGd734OeO2bBKoMJE9fBd7HI20/jofha6zWG5uNFbD6TGOxvcL61 nBRaykGh7CooMtsKx9ZRGQ3QZbwtwy0Ygv80hdGMlHbYYBH5KpC+30KVd8DcDcIt om2ene92KHu4HdNg9Xm7RIy8NJM2lf9x6Z5bOoKZjWo=
Received: from Kahlo (76-235-103-220.lightspeed.mdsnwi.sbcglobal.net [76.235.103.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: mark@internetpolicyadvisors.com) by pdx1-sub0-mail-a7.g.dreamhost.com (Postfix) with ESMTPSA id 358FA82AFF; Mon, 8 Jul 2019 06:47:08 -0700 (PDT)
Reply-To: mark@internetpolicyadvisors.com
X-DH-BACKEND: pdx1-sub0-mail-a7
From: mark@internetpolicyadvisors.com
To: 'Tony Rutkowski' <rutkowski.tony@gmail.com>, smart@irtf.org
References: <156259169027.840.9135095847874577233.idtracker@ietfa.amsl.com> <019f01d53590$cf8c2a50$6ea47ef0$@internetpolicyadvisors.com> <5efde727-8e1d-9e9e-a9a4-32ce3f60e359@gmail.com>
In-Reply-To: <5efde727-8e1d-9e9e-a9a4-32ce3f60e359@gmail.com>
Date: Mon, 08 Jul 2019 08:47:07 -0500
Organization: internet policy advisors
Message-ID: <01c301d53593$a3236c50$e96a44f0$@internetpolicyadvisors.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01C4_01D53569.BA4E27A0"
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-us
thread-index: AQFMPd84Pfj653eiQ4e3NZob+DYjrwEATBekAv2ZGCOnsrtQYA==
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduvddrgedtgdejudcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucggtfgfnhhsuhgsshgtrhhisggvpdfftffgtefojffquffvnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpehrhffvfhgjufffohfkgggtofhtsegrtdhgpedvtdejnecuhfhrohhmpeeomhgrrhhksehinhhtvghrnhgvthhpohhlihgthigrughvihhsohhrshdrtghomheqnecuffhomhgrihhnpehivghtfhdrohhrghenucfkphepjeeirddvfeehrddutdefrddvvddtnecurfgrrhgrmhepmhhouggvpehsmhhtphdphhgvlhhopefmrghhlhhopdhinhgvthepjeeirddvfeehrddutdefrddvvddtpdhrvghtuhhrnhdqphgrthhhpeeomhgrrhhksehinhhtvghrnhgvthhpohhlihgthigrughvihhsohhrshdrtghomheqpdhmrghilhhfrhhomhepmhgrrhhksehinhhtvghrnhgvthhpohhlihgthigrughvihhsohhrshdrtghomhdpnhhrtghpthhtohepshhmrghrthesihhrthhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptd
Archived-At: <https://mailarchive.ietf.org/arch/msg/smart/iHMUnN0RxwYYM-0bzhKJDRzOVqU>
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:47:24 -0000

Those are pretty useful questions. I’ve gotten the same comments from others off-list.  The scoping of CLESS is something we should try to make progress on the list.

 

The 5G question is a little different for me. Do you think that 5G introduces categories of endpoints that would not be present in existing, or other, transport infrastructures?  If so, I’m happy to amend the text.

 

Thanks,

 

mark

 

From: Tony Rutkowski <rutkowski.tony@gmail.com> 
Sent: Monday, July 8, 2019 8:36 AM
To: mark@internetpolicyadvisors.com; smart@irtf.org
Subject: Re: [Smart] New Version Notification for draft-mcfadden-smart-endpoint-taxonomy-for-cless-00.txt

 

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 <mailto: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