IETF Logo Mail Archive

Re: [Smart] New I-D: draft-taddei-cless-introduction

"Arnaud.Taddei.IETF" <Arnaud.Taddei.IETF@protonmail.com> Tue, 19 March 2019 16:05 UTC

Return-Path: <Arnaud.Taddei.IETF@protonmail.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 CCA38131122 for <smart@ietfa.amsl.com>; Tue, 19 Mar 2019 09:05:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.958
X-Spam-Level:
X-Spam-Status: No, score=0.958 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, FROM_WORDY=1.147, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, TO_EQ_FM_DIRECT_MX=2.499, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=protonmail.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 1j_hedPgHtd7 for <smart@ietfa.amsl.com>; Tue, 19 Mar 2019 09:05:16 -0700 (PDT)
Received: from mail2.protonmail.ch (mail2.protonmail.ch [185.70.40.22]) (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 AEE67130E9A for <smart@irtf.org>; Tue, 19 Mar 2019 09:05:15 -0700 (PDT)
Date: Tue, 19 Mar 2019 16:05:11 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=default; t=1553011513; bh=4yffOSQnnCu9bx63Z3lUGLYYuUJk0Mq0IrInefupu6g=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References: Feedback-ID:From; b=NUkJGet4azDhOx1zkBdUyXGlbQbAGScces0v54gON3JKutWezFBUpIsr23NZhINP7 QPQ6+9/P6BIu+MCWE+VOegSZ2Gi6xbP8FWzeNyTZG1XgQNjRyLXivECjQypVWS56O4 iOZh0gresmlYKfqhMIopKOD/9e82wr/LINvW4X+c=
To: "Arnaud.Taddei.IETF" <Arnaud.Taddei.IETF@protonmail.com>
From: "Arnaud.Taddei.IETF" <Arnaud.Taddei.IETF@protonmail.com>
Cc: "smart@irtf.org" <smart@irtf.org>
Reply-To: "Arnaud.Taddei.IETF" <Arnaud.Taddei.IETF@protonmail.com>
Message-ID: <0-8oRm0eYLa3Tq7kSIN276eibkAbFyt-9VKHbV1s4_l6tyv-wDVQh7h50vMA17NBXJRD4VAkArcSibybNMgWXtmUSZ_PCdKSZdhGaH7EmAw=@protonmail.com>
In-Reply-To: <tUYHTisBMl4tMQGxMttcIKzr6sVTcfoDj0ecdxDs1TbvWkuXppnOylXChjHV3bYk66zscX9v50eYby7GLchs2mjxz-inxzHLYPUYB6XRBLA=@protonmail.com>
References: <tUYHTisBMl4tMQGxMttcIKzr6sVTcfoDj0ecdxDs1TbvWkuXppnOylXChjHV3bYk66zscX9v50eYby7GLchs2mjxz-inxzHLYPUYB6XRBLA=@protonmail.com>
Feedback-ID: kou6vaSHQeY5dgFN9dCIYKo4z6hnnNmKuV4IBJw2wx4vSVPtftyhWUTBigri6zMJ3K1hxYJjI-3RAIGaizMt5g==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="b1_3a9a465dce7b8e854b955a2b093b7768"
Archived-At: <https://mailarchive.ietf.org/arch/msg/smart/LubEUCDmkRc7WOd-yxpmKCNnA9U>
Subject: Re: [Smart] New I-D: draft-taddei-cless-introduction
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: Tue, 19 Mar 2019 16:05:19 -0000

The draft was merged in the SMART Github so the below should read (with the correct URL):

Name:           draft-taddei-cless-introduction
Revision:       00
Title:          Capabilities and Limitations of an Endpoint-only Security Solution
Document date:  2019-03-19
Group:          Individual Submission
Pages:          41
URL:            https://github.com/smart-rg/drafts/blob/master/draft-taddei-cless-introduction-00.txt

Abstract

   In the context of existing, proposed and newly published protocols,
   this draft RFC is to establish the capabilities and limitations of
   endpoint-only security solutions and explore benefits and
   alternatives to mitigate those limits with the support of real case
   studies.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday 19 March 2019 15:17, Arnaud.Taddei.IETF <Arnaud.Taddei.IETF=40protonmail.com@dmarc.ietf.org> wrote:

> FYI colleagues, I uploaded the following draft in Github for SMART.
>
> I was given 10' of the SMART agenda on Monday 25th at IETF104 at 4:10pm session.
>
> I am aware I passed the date for proper I-D submissions.
>
> At this stage I am simply looking for your consideration and feedback.
>
> I tried to respect all the rules to create an I-D but happy to learn.
>
> Name:           draft-taddei-cless-introduction
> Revision:       00
> Title:          Capabilities and Limitations of an Endpoint-only Security Solution
> Document date:  2019-03-19
> Group:          Individual Submission
> Pages:          41
> URL:            https://github.com/arnaudtaddei/drafts/blob/patch-1/draft-taddei-cless-introduction-00.txt
>
> Abstract
>
>    In the context of existing, proposed and newly published protocols,
>    this draft RFC is to establish the capabilities and limitations of
>    endpoint-only security solutions and explore benefits and
>    alternatives to mitigate those limits with the support of real case
>    studies.
>
> Sent with [ProtonMail](https://protonmail.com) Secure Email.

v2.23.0 | Report a Bug | By Email