Re: [sidr] adverse actions -01 posted

Stephen Kent <kent@bbn.com> Thu, 08 September 2016 14:28 UTC

Return-Path: <kent@bbn.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 C9EEA12B1A6 for <sidr@ietfa.amsl.com>; Thu, 8 Sep 2016 07:28:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level:
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 WmF_G7lyfbXc for <sidr@ietfa.amsl.com>; Thu, 8 Sep 2016 07:28:54 -0700 (PDT)
Received: from bos-mailout2.raytheon.com (bos-mailout2.raytheon.com [199.46.198.208]) (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 3759612B2A9 for <sidr@ietf.org>; Thu, 8 Sep 2016 07:28:51 -0700 (PDT)
Received: from ma-mailout10.rtnmail.ray.com (ma-mailout10.rtnmail.ray.com [147.25.130.27]) by bos-mailout2.raytheon.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id u88ESncl022138 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 8 Sep 2016 14:28:49 GMT
Received: from smtp.bbn.com ([128.33.0.80]) by ma-mailout10.rtnmail.ray.com (8.15.0.59/8.15.0.59) with ESMTPS id u88ESmWu010890 (version=TLSv1 cipher=AES256-SHA bits=256 verify=NOT); Thu, 8 Sep 2016 14:28:49 GMT
Received: from ssh.bbn.com ([192.1.122.15]:48848 helo=COMSEC.fios-router.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1bi0Js-000MBd-Kc; Thu, 08 Sep 2016 10:28:48 -0400
From: Stephen Kent <kent@bbn.com>
To: "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>, Christopher Morrow <morrowc.lists@gmail.com>
References: <76dad5c8-114a-19fe-6fc2-cf3c45e0f666@bbn.com> <227BF007-90BD-4301-A349-FC01A1A5969A@ripe.net> <c9243c24-e976-c234-01c7-110c768ba0b6@bbn.com> <m2zip43s0q.wl%randy@psg.com> <afb4f8dc-3e29-c8fe-f8fe-2d7b2fcd7a1f@bbn.com> <alpine.WNT.2.00.1607272054380.15548@mw-PC> <9b33dd4f-6361-626d-5e0b-fa6d4ba3b260@bbn.com> <m260rq39ma.wl%randy@psg.com> <de3222b6-98ec-3c87-5a68-101ee4f8f3a0@bbn.com> <CAL9jLaZ4Y2oK7Y9=EA8L+XpmBYB-RK_J9fCT8+JTb7PCxZ8zXA@mail.gmail.com> <DM2PR09MB0446F23D2A61F782077406F084E40@DM2PR09MB0446.namprd09.prod.outlook.com>
Message-ID: <cb8752b3-cf1b-addf-fcc1-6c0dceb7b8fd@bbn.com>
Date: Thu, 8 Sep 2016 10:28:48 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <DM2PR09MB0446F23D2A61F782077406F084E40@DM2PR09MB0446.namprd09.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-CC: sidr@ietf.org, morrowc.lists@gmail.com, kotikalapudi.sriram@nist.gov
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-09-08_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1609080208
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/UZkAe_ORM-dz3xlToMB0fQK9I0c>
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: Thu, 08 Sep 2016 14:28:57 -0000

"anomaly" is better than "unwanted" in some respects, but it too fails 
to convey the fact that the anomaly has an adverse impact on the INR 
holder. It would be anomalous if a CA changed a cert to contain more 
resources than were supposed to be allocated to the INR holder, but if 
these resources are not in conflict with allocations to other INR 
holders, the effect is not adverse. [Maybe it becomes adverse when the 
bill arrives ;-)]

I'm still reluctant to change the term given the changes I have already 
made to the text to note that a CA may engage in an action that is 
perceived as adverse by an INR holder, but the CA may be in the right in 
effecting this action.

Steve


> I think using the term "RPKI anomalies" is another choice here. It's kind of neutral about cause/intention.
> Advising/alerting the user community about -
> RPKI anomalies may arise due to various reasons.
> It could be due to fat fingers, negligence, or actions by your service provider or law enforcement, etc.
> They have potential impacts on your routing, so you should be watchful, etc..