IETF Logo Mail Archive

Re: [sidr] Request for WG Last Call for draft-ietf-sidr-bogons-02.txt and draft-ietf-sidr-roa-validation-01.txt

Randy Bush <randy@psg.com> Wed, 26 November 2008 06:26 UTC

Return-Path: <sidr-bounces@ietf.org>
X-Original-To: sidr-archive@megatron.ietf.org
Delivered-To: ietfarch-sidr-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E39183A6B34; Tue, 25 Nov 2008 22:26:30 -0800 (PST)
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 E90653A6B34 for <sidr@core3.amsl.com>; Tue, 25 Nov 2008 22:26:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 ssL2HP63Ipkg for <sidr@core3.amsl.com>; Tue, 25 Nov 2008 22:26:29 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 193053A6A31 for <sidr@ietf.org>; Tue, 25 Nov 2008 22:26:29 -0800 (PST)
Received: from 50.216.138.210.bn.2iij.net ([210.138.216.50] helo=rmac.psg.com) by ran.psg.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <randy@psg.com>) id 1L5Dqz-000F77-Fm; Wed, 26 Nov 2008 06:26:25 +0000
Message-ID: <492CEC10.1070109@psg.com>
Date: Wed, 26 Nov 2008 15:26:24 +0900
From: Randy Bush <randy@psg.com>
User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105)
MIME-Version: 1.0
To: George Michaelson <ggm@apnic.net>
References: <C5521DCD.5484%andy@arin.net> <492CCB80.2030501@psg.com> <EED84F5B-FA73-48BC-8BA5-42C0F53051BB@apnic.net>
In-Reply-To: <EED84F5B-FA73-48BC-8BA5-42C0F53051BB@apnic.net>
X-Enigmail-Version: 0.95.7
Cc: sidr@ietf.org
Subject: Re: [sidr] Request for WG Last Call for draft-ietf-sidr-bogons-02.txt and draft-ietf-sidr-roa-validation-01.txt
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sidr-bounces@ietf.org
Errors-To: sidr-bounces@ietf.org

> 2.1.3.2. eContent
> 
>   The content of a ROA identifies a single AS that has been authorized
>   by the address space holder to originate routes and a list of one or
>   more IP address prefixes that will be advertised.  If the address
>   space holder needs to authorize multiple ASes to advertise the same
>   set of address prefixes, the holder issues multiple ROAs, one per AS
>   number.
> 
> and
> 
> 4. Security Considerations
> 
> 
> ....   The purpose of a ROA is to convey authorization for an AS to
>   originate a route to the prefix(es) in the ROA.
> 
> these are basic, clear, simple, concise, terse, and rigorous definition
> of the semantics of a roa.

and incomplete.  for example, this does not deal with netmask and max
len issues.

randy
_______________________________________________
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr

v2.23.0 | Report a Bug | By Email