Re: [saag] New Version Notification for draft-richardson-saag-onpath-attacker-02.txt

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 04 July 2021 20:50 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62A9D3A1E92 for <saag@ietfa.amsl.com>; Sun, 4 Jul 2021 13:50:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.236
X-Spam-Level:
X-Spam-Status: No, score=-2.236 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.338, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 hfgx-qN1xWiN for <saag@ietfa.amsl.com>; Sun, 4 Jul 2021 13:50:33 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B39773A1E90 for <saag@ietf.org>; Sun, 4 Jul 2021 13:50:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id C584838AFD for <saag@ietf.org>; Sun, 4 Jul 2021 16:52:52 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Cn9Jv_jeXaPM for <saag@ietf.org>; Sun, 4 Jul 2021 16:52:49 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7C4EF38ADD for <saag@ietf.org>; Sun, 4 Jul 2021 16:52:49 -0400 (EDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B881A4B6 for <saag@ietf.org>; Sun, 4 Jul 2021 16:50:27 -0400 (EDT)
To: saag@ietf.org
References: <161402913142.668.8084091230406313422@ietfa.amsl.com> <2322.1614029367@localhost>
From: Michael Richardson <mcr+ietf@sandelman.ca>
Message-ID: <8807c53a-6329-78b6-a883-374716eae600@sandelman.ca>
Date: Sun, 4 Jul 2021 16:50:27 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <2322.1614029367@localhost>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/H0e8AxUTH2eHYtoFqy8AAyXntXM>
Subject: Re: [saag] New Version Notification for draft-richardson-saag-onpath-attacker-02.txt
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Jul 2021 20:50:39 -0000

Again, I find situations in which some common understanding of attacks 
would be useful.   Is there any further interest in this document?

What do you think about Malory-in-the-Middle?
Can we come up with a less golf-aware term like "rough"?


On 2021-02-22 4:29 p.m., Michael Richardson wrote:
> 
> internet-drafts@ietf.org wrote:
>      > A new version of I-D, draft-richardson-saag-onpath-attacker-02.txt has
>      > been successfully submitted by Michael Richardson and posted to the
>      > IETF repository.
> 

> Html:           https://www.ietf.org/archive/id/draft-richardson-saag-onpath-attacker-02.html
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-richardson-saag-onpath-attacker-02
> 
> Abstract:
>     The terms on-path attacker and Man-in-the-Middle Attack have been
>     used in a variety of ways, sometimes interchangeably, and sometimes
>     meaning different things.
> 
>     This document offers an update on terminology for network attacks.  A
>     consistent set of terminology is important in describing what kinds
>     of attacks a particular protocol defends against, and which kinds the
>     protocol does not.