IETF Logo Mail Archive

Re: [Secdispatch] [Smart] New Version Notification for draft-lazanski-smart-users-internet-00.txt

Phillip Hallam-Baker <phill@hallambaker.com> Mon, 15 July 2019 00:48 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75D3412018D for <secdispatch@ietfa.amsl.com>; Sun, 14 Jul 2019 17:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.558
X-Spam-Level:
X-Spam-Status: No, score=-1.558 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.091, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 oDZqHP2iHVEJ for <secdispatch@ietfa.amsl.com>; Sun, 14 Jul 2019 17:48:47 -0700 (PDT)
Received: from mail-ot1-f53.google.com (mail-ot1-f53.google.com [209.85.210.53]) (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 E73621202A4 for <Secdispatch@ietf.org>; Sun, 14 Jul 2019 17:48:45 -0700 (PDT)
Received: by mail-ot1-f53.google.com with SMTP id r6so15191770oti.3 for <Secdispatch@ietf.org>; Sun, 14 Jul 2019 17:48:45 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Okvd/cugBl0cOhRAaxCj9Rul/laZKddU6PVLk/2ULXY=; b=sQdB4nIrtL0ZUgw27LR3lLM6xjPHdKCKj3fG4KAtus3m2afF4XI3Hd8Lkv900p4xdt XYW3Zahnyl3zvsOAKdmVyFmxkVXwDaEl4ufl4ZjDvfrjsTLaF0esKFVR2dYrvdn03Xu4 aloBHi5NpCwxL3Z4xVgc9cBIvNXvTG7a0yJz59ej49QxotglCTlNHF63o1vR4sqOw8W5 034chAWf6Qr4GrIkdgMHguzztlMB8tHfROUhcVT3SSlrUUnFL0l86TNLbAjwCx/0MTy1 rDllSxQED5tj+DahBiXdctpp2hRHD5jPhkFYDWdYLr6k5fPKkMdH8fVmDDsx83AZHQQE 9vAg==
X-Gm-Message-State: APjAAAUw1/H7vx0lgvpsGw/C4GJSoBhPIxnKy0r40hC7wHMZPiQV+T1v ddmnpPf+waLlWQ0LEnsPeuQmR1njnoa0dA4HLwc=
X-Google-Smtp-Source: APXvYqwUD+g2VmcXTgEu8Ww0oH3asHkDxcqW57dCPDk1nOtWQRyiFDU26IeWmo4gmrchyNTJNZ9hgN1KM5ly6jlQskg=
X-Received: by 2002:a9d:7d02:: with SMTP id v2mr10033295otn.112.1563151725282; Sun, 14 Jul 2019 17:48:45 -0700 (PDT)
MIME-Version: 1.0
References: <0A8948DB-F97C-4F68-9173-7E627FB5019C@lastpresslabel.com> <4B10655B-8753-4B10-ACC9-16D7F78AD9F9@gmail.com> <CAMm+Lwh3KW6ZBbMktwmLcKyY8=_ysLYJF_7MsAuiOat6baQ=Kg@mail.gmail.com> <B551EF79-7E6E-4C4E-ADCA-6538F7972222@gmail.com> <CAMm+Lwg+2RFiXK43nJv7pD3OgM8y=ziVYxBkXD3F2kJyz37SxQ@mail.gmail.com> <50E59504-CA00-4792-AA72-FC08051E2486@gmail.com> <CAHbuEH5WUv-a4nKt5YAZosO-vE773Jh3xn1+-hA=4J7RBERc3g@mail.gmail.com> <78ccb680-9ccb-f13f-0442-02833cc7cc92@cs.tcd.ie> <CABcZeBNwmitpkJn0fCbNHOJtJ25yXdk6i6U9wK0a-9hwK1Tqcw@mail.gmail.com> <CAMm+Lwim0UK9YOO0vh+O0eOCQjZgsPQLdFZFQgsbpxpFNZChrA@mail.gmail.com> <CABcZeBOd9YM04OiY1BLw+YTn6FZKVg7PczLMggnowLjPo=k5Lg@mail.gmail.com>
In-Reply-To: <CABcZeBOd9YM04OiY1BLw+YTn6FZKVg7PczLMggnowLjPo=k5Lg@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sun, 14 Jul 2019 20:48:34 -0400
Message-ID: <CAMm+Lwj0rnrynnfHGE3cSnfV=D6in8AMz01+SOR5riKC8ZNjGw@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, smart@irtf.org, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, Dominique Lazanski <dml@lastpresslabel.com>, IETF SecDispatch <Secdispatch@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000050cb1c058dad9fbc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/ka9pNzH_fS3rgRht5jB6DwdmCXg>
Subject: Re: [Secdispatch] [Smart] New Version Notification for draft-lazanski-smart-users-internet-00.txt
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jul 2019 00:48:48 -0000

On Sun, Jul 14, 2019 at 8:34 PM Eric Rescorla <ekr@rtfm.com> wrote:

>
>
> On Sun, Jul 14, 2019 at 5:27 PM Phillip Hallam-Baker <
> phill@hallambaker.com> wrote:
>
>>
>>
> First, I'm not sure that I agree that cyber attacks on endpoints are
>>> the greatest threat to the Internet, but even assuming that's so,
>>> what are the implications of that for work in the IETF? It's one thing
>>> to change the words of 3552, but what work specifically would we
>>> do if those words were different.
>>>
>>
>> I'm not keen on the focus on the end point. It seems like it is brought
>> up as a trump card to 'prove' that all security efforts are futile and the
>> criminals must always win.
>>
>
> Well, that's certainly not my position.
>

I wasn't suggesting it was. It is just my experience that whenever I
discuss some security protocol development in the wider context there is
always some smart ass who wants to talk about end-point security rather
than the thing the presentation is actually about.

It is like the idea that the hackers have to be smarter than the security
specialists because they can always find a Ford Cortina with its doors
unlocked and the keys in the ignition.

v2.23.0 | Report a Bug | By Email