IETF Logo Mail Archive

Re: [sidr] adoption call for draft-kent-sidr-adverse-actions-02

Andy Newton <andy@arin.net> Wed, 30 March 2016 15:09 UTC

Return-Path: <andy@arin.net>
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 72C9412D766 for <sidr@ietfa.amsl.com>; Wed, 30 Mar 2016 08:09:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 YnSIWkt4GuTp for <sidr@ietfa.amsl.com>; Wed, 30 Mar 2016 08:08:59 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 84C2B12D715 for <sidr@ietf.org>; Wed, 30 Mar 2016 08:08:58 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 323) id 175E82136E1; Wed, 30 Mar 2016 11:08:58 -0400 (EDT)
Received: from chaedge02.corp.arin.net (chaedge02.corp.arin.net [192.149.252.119]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp2.arin.net (Postfix) with ESMTP id 84DE4213618; Wed, 30 Mar 2016 11:08:55 -0400 (EDT)
Received: from CAS02CHA.corp.arin.net (10.1.30.63) by chaedge02.corp.arin.net (192.149.252.119) with Microsoft SMTP Server (TLS) id 14.3.210.2; Wed, 30 Mar 2016 11:07:21 -0400
Received: from CAS01CHA.corp.arin.net (10.1.30.62) by CAS02CHA.corp.arin.net (10.1.30.63) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 30 Mar 2016 11:06:09 -0400
Received: from CAS01CHA.corp.arin.net ([fe80::b4a5:12e4:34a8:a6e7]) by CAS01CHA.corp.arin.net ([fe80::b4a5:12e4:34a8:a6e7%13]) with mapi id 15.00.1104.000; Wed, 30 Mar 2016 11:06:08 -0400
From: Andy Newton <andy@arin.net>
To: Stephen Kent <kent@bbn.com>
Thread-Topic: [sidr] adoption call for draft-kent-sidr-adverse-actions-02
Thread-Index: AQHRe7g1YXn6Ql6T90y4lKvwss1hFJ9w75EAgAF8fQCAAAt/AA==
Date: Wed, 30 Mar 2016 15:06:08 +0000
Message-ID: <7835A724-0AC2-462C-A2AF-1B48BE78DD6D@arin.net>
References: <513BC696-168B-48A6-94EC-B0CD4B3292EC@icloud.com> <002885DC-BD79-47C4-A069-7F86269549B6@tislabs.com> <613CF604-76EC-4901-90D7-1DBB5A606946@ripe.net> <56FBE234.7090703@bbn.com>
In-Reply-To: <56FBE234.7090703@bbn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.1.34.130]
Content-Type: multipart/alternative; boundary="_000_7835A7240AC2462CA2AF1B48BE78DD6Darinnet_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/eIj5CUlJvpK-A3Vlvs7JUICSfUk>
Cc: "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [sidr] adoption call for draft-kent-sidr-adverse-actions-02
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: Wed, 30 Mar 2016 15:09:06 -0000

On Mar 30, 2016, at 10:27 AM, Stephen Kent <kent@bbn.com<mailto:kent@bbn.com>> wrote:

That's a fair point. Are you suggesting that we create a separate doc to enumerate
vulnerabilities in the IRR context, or that we add a section to this doc to describe,
in less detail, such vulnerabilities?

+1 on documenting this being a good idea.

Unfortunately, enumerating the IRR vulnerabilities would likely consume your current document.

Perhaps a companion document is more appropriate.

-andy

v2.23.0 | Report a Bug | By Email