IETF Logo Mail Archive

Re: [sidr] draft-ymbk-rpki-grandparenting-00.txt

Terry Manderson <terry.manderson@icann.org> Tue, 12 June 2012 00:28 UTC

Return-Path: <terry.manderson@icann.org>
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 37B8F21F854D for <sidr@ietfa.amsl.com>; Mon, 11 Jun 2012 17:28:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MC2euwa0JKwL for <sidr@ietfa.amsl.com>; Mon, 11 Jun 2012 17:28:25 -0700 (PDT)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by ietfa.amsl.com (Postfix) with ESMTP id 920CE21F852A for <sidr@ietf.org>; Mon, 11 Jun 2012 17:28:25 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Mon, 11 Jun 2012 17:28:25 -0700
From: Terry Manderson <terry.manderson@icann.org>
To: Randy Bush <randy@psg.com>, Byron Ellacott <bje@apnic.net>
Date: Mon, 11 Jun 2012 17:28:17 -0700
Thread-Topic: [sidr] draft-ymbk-rpki-grandparenting-00.txt
Thread-Index: Ac1Gj53/Rj1/BNaOQs2DzA1efNjnTQBoqTMu
Message-ID: <CBFCCA41.269A9%terry.manderson@icann.org>
In-Reply-To: <m2zk8cglss.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="B_3422341697_36297637"
MIME-Version: 1.0
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] draft-ymbk-rpki-grandparenting-00.txt
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 12 Jun 2012 00:28:26 -0000

Hi Randy,

On 10/06/12 8:30 AM, "Randy Bush" <randy@psg.com> wrote:

>> before the wanderings, there were three announcements.
>>    A  10.0.0.0/8
>>    C  10.42.0.0/16
>>    G  10.42.2.0/2
>                  /24
> 
>> gonna be hard to convince C to become chopped liver so that G can be
>> independent.  also gonna be a bit of pollution.
> 

Can you define 'pollution'? in what sense? In C no longer going to announce
the full /16 aggregate? Is the goal here routing security, or bgp table
growth limitation?

Why does 'C' having their resource certificate list specifically what
resources they are in control of ("chopped liver") and therefore what they
can announce/route have any bearing on something that is a) the antecedent
for routing security, and B) something that is mostly machine generated and
machine parsed?

Cheers
Terry

v2.23.0 | Report a Bug | By Email