Re: [sidr] Comments on draft-ymbk-rpki-rtr-protocol

Stephen Kent <kent@bbn.com> Thu, 05 August 2010 14:48 UTC

Return-Path: <kent@bbn.com>
X-Original-To: sidr@core3.amsl.com
Delivered-To: sidr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5490E3A6814 for <sidr@core3.amsl.com>; Thu, 5 Aug 2010 07:48:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.399
X-Spam-Level:
X-Spam-Status: No, score=-102.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OW0ru9BrWobm for <sidr@core3.amsl.com>; Thu, 5 Aug 2010 07:48:36 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id 1BEFF3A6B0F for <sidr@ietf.org>; Thu, 5 Aug 2010 07:48:36 -0700 (PDT)
Received: from dhcp89-089-072.bbn.com ([128.89.89.72]:49256) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1Oh1kn-0002zU-Qb; Thu, 05 Aug 2010 10:49:06 -0400
Mime-Version: 1.0
Message-Id: <p06240805c880782ba411@[128.89.89.72]>
In-Reply-To: <20100804190209.GB27912@slice>
References: <20100804153322.GB25173@slice> <20100804170808.3662522829@thrintun.hactrn.net> <20100804174424.GA27912@slice> <20100804180653.77B3B22829@thrintun.hactrn.net> <20100804190209.GB27912@slice>
Date: Thu, 05 Aug 2010 10:23:29 -0400
To: Jeffrey Haas <jhaas@pfrc.org>
From: Stephen Kent <kent@bbn.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: sidr@ietf.org
Subject: Re: [sidr] Comments on draft-ymbk-rpki-rtr-protocol
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 05 Aug 2010 14:48:38 -0000

>...
>
>A provider may wish to override validated RPKI data for their own purposes.
>While not explicitly a SIDR-driven requirement, this was discussed multiple
>times as a requirement during the original RPSEC work.

A specific proposal for how to locally override the RPKI structure as 
retrieved form the repository system is contained in a document being 
considered as a SIDR WG item: 
http://tools.ietf.org/html/draft-reynolds-rpki-ltamgmt-00

>
>The resulting output (override or no), is a set of AS:prefix/maxlen tuples
>that reflects the provider's routing policy with regard to origin
>validation.

In the case of the doc cited above, it is not in that form.

>
>This policy must now be distributed to routers for implementation.  The
>mechanism for distributing the policy is currently
>draft-ymbk-rpki-rtr-protocol.

I think the ymbk protocol distributes the results of validating the 
RPKI data, with whatever policy has been applied to that validation 
process.

Steve