Re: [sidr] adverse actions -01 posted

Randy Bush <randy@psg.com> Tue, 26 July 2016 23:21 UTC

Return-Path: <randy@psg.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 861CF12DBA0 for <sidr@ietfa.amsl.com>; Tue, 26 Jul 2016 16:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.187
X-Spam-Level:
X-Spam-Status: No, score=-8.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.287] 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 htjecCO0I65B for <sidr@ietfa.amsl.com>; Tue, 26 Jul 2016 16:21:13 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 801A212DB8F for <sidr@ietf.org>; Tue, 26 Jul 2016 16:21:13 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1bSBj8-0006e8-5M; Tue, 26 Jul 2016 23:25:30 +0000
Date: Wed, 27 Jul 2016 08:21:09 +0900
Message-ID: <m2zip43s0q.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Stephen Kent <kent@bbn.com>
In-Reply-To: <c9243c24-e976-c234-01c7-110c768ba0b6@bbn.com>
References: <76dad5c8-114a-19fe-6fc2-cf3c45e0f666@bbn.com> <227BF007-90BD-4301-A349-FC01A1A5969A@ripe.net> <c9243c24-e976-c234-01c7-110c768ba0b6@bbn.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/cqVbG34wv-XRolkxQn8yoJ3xMA8>
Cc: sidr <sidr@ietf.org>
Subject: Re: [sidr] adverse actions -01 posted
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2016 23:21:14 -0000

>> To me the word "adverse" communicates an unfavourable, possibly even
>> malicious, action by an adversary.
> 
> The term adverse is appropriate as used in this document. When I look
> up the term I find the following primary definitions:
> 
>      unfavorable or antagonistic in purpose or effect, opposed to
> one's interests, causing harm, etc.
> 
> Synonyms include inimical and injurious.
> 
> These meanings are precisely what is intended here.

and what tim, and others, are trying to say is that exactly those
meanings are inappropriate.  we do not really know intent, contracts,
and business/social context.

i picked the first example of an 'adverse action' in your document and
explained how it can be normal operations (and it is said you have fixed
it, tyvm).  i had hopes you would induce.

operations and deployment are messy.  apologies.

tim made a fair suggeston of a lighter word.

randy