Re: [sidr] I-D Action: draft-ietf-sidr-rpki-validation-reconsidered-00.txt

Andy Newton <andy@arin.net> Fri, 08 August 2014 15:39 UTC

Return-Path: <andy@arin.net>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96B011B2B84 for <sidr@ietfa.amsl.com>; Fri, 8 Aug 2014 08:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
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 GeBmWNl5TBfd for <sidr@ietfa.amsl.com>; Fri, 8 Aug 2014 08:39:09 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id 34E931B2AF2 for <sidr@ietf.org>; Fri, 8 Aug 2014 08:39:09 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id E4A8516501E; Fri, 8 Aug 2014 11:39:08 -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 smtp1.arin.net (Postfix) with ESMTP id 5ED74165012; Fri, 8 Aug 2014 11:39:08 -0400 (EDT)
Received: from CHACAS02.corp.arin.net (10.1.30.108) by chaedge02.corp.arin.net (192.149.252.119) with Microsoft SMTP Server (TLS) id 14.3.181.6; Fri, 8 Aug 2014 11:40:00 -0400
Received: from CHAMBX02.corp.arin.net ([fe80::905e:9b4d:2909:f55a]) by CHACAS02.corp.arin.net ([fe80::54ae:f9de:2f8b:1072%12]) with mapi id 14.03.0181.006; Fri, 8 Aug 2014 11:39:02 -0400
From: Andy Newton <andy@arin.net>
To: Stephen Kent <kent@bbn.com>
Thread-Topic: [sidr] I-D Action: draft-ietf-sidr-rpki-validation-reconsidered-00.txt
Thread-Index: AQHPnD4MWZPJUx8QpU+h2rFbrnAOgJuuUuIAgAFi9wCAADDNAIAAG7gAgAASbgCAAQkngIAARcuAgAAYJwCACYOYgIAHti8AgAA4cYCAAAsogIABK/gAgAMjF4A=
Date: Fri, 08 Aug 2014 15:39:01 +0000
Message-ID: <75B90A7B-ED14-4716-A12C-2EDB1AA7851D@arin.net>
References: <20140702012717.18291.24295.idtracker@ietfa.amsl.com> <415BB336-1A6C-48DD-BD0F-BC9EB0C3506F@ripe.net> <53CFFF3C.2040406@bbn.com> <BB01407F-A226-4531-9FDD-50E1B0A238F0@ripe.net> <53D151F0.80808@bbn.com> <C838412C-D16C-4C88-B022-85484789444A@ripe.net> <53D178A6.7060502@bbn.com> <CFF7CDF2.4AB4B%bje@apnic.net> <65886423-144A-48B5-A0EF-D35D4A4FE890@ripe.net> <CA+z-_EUXA0TWDqHV-9sFbgS2vyXiKE9EKBae6K0eihuhKTsm2A@mail.gmail.com> <53DAA101.8020305@bbn.com> <53E11912.7050904@gmail.com> <53E1486B.1080604@bbn.com> <53E151C7.1090508@gmail.com> <53E24D68.8020705@bbn.com>
In-Reply-To: <53E24D68.8020705@bbn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.1.0.87]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <0EEDDCE9DFF2634C940621C331ECD37A@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/sidr/jsUiV02l_lV6OdNffnkbsjqaOOE
Cc: "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [sidr] I-D Action: draft-ietf-sidr-rpki-validation-reconsidered-00.txt
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 08 Aug 2014 15:39:10 -0000

On Aug 6, 2014, at 11:44 AM, Stephen Kent <kent@bbn.com> wrote:

> Carlos,
> 
> ...
>> Given that S-BGP failed to gain any traction and most people outside the
>> IETF have never heard of it, I don´t think it sets a particularly
>> encouraging precedent.
> You asked why 3779. I explained. The were many reasons why S-BGP
> didn't succeed, but use of 3779 is not likely one of them.
>> There is nothing wrong with the extension, nor with the rules per-se.
>> Some of us believe that 3779 rules are not a good match for this
>> particular problem. They may very well be for other, related, problem
>> domains (whole network transfers come to mind now).
> The SIDR WG began meeting in 2006, I believe. The SIDR arch doc was first posted
> (as an accepted WG I-D) on 2/28/07. It cited 3779 as the basis for the RPKI.

Either the question Carlos has asked is unanswered or the answer is using circular logic. I cannot tell which.

The question was about why, in this effort, we are using 3779 validation rules, and the answer appears to be because a past, failed effort used them. Is there really no technical justification?

> It seems curious to me that it has taken 7 years for senior RIR tech staff to
> determine that there is a problem. You are relatively new to this effort, but what
> is the excuse for your co-authors?

C’mon Steve. You're better than this.

-andy