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

George Michaelson <ggm@apnic.net> Wed, 26 November 2008 06:31 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 385353A6B2A; Tue, 25 Nov 2008 22:31:00 -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 AC1E83A6B2A for <sidr@core3.amsl.com>; Tue, 25 Nov 2008 22:30:59 -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=[AWL=0.000, 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 XPmDjm+fHSlu for <sidr@core3.amsl.com>; Tue, 25 Nov 2008 22:30:58 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [202.12.29.51]) by core3.amsl.com (Postfix) with ESMTP id C69533A6A0D for <sidr@ietf.org>; Tue, 25 Nov 2008 22:30:58 -0800 (PST)
Received: from dhcp151.apnic.net (dhcp151.apnic.net [202.12.29.151]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 2E93C11006A for <sidr@ietf.org>; Wed, 26 Nov 2008 16:30:56 +1000 (EST)
Message-Id: <41F912C2-9F6E-4DD9-9D94-2359944DDA5F@apnic.net>
From: George Michaelson <ggm@apnic.net>
To: sidr@ietf.org
In-Reply-To: <492CEC10.1070109@psg.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 26 Nov 2008 16:30:55 +1000
References: <C5521DCD.5484%andy@arin.net> <492CCB80.2030501@psg.com> <EED84F5B-FA73-48BC-8BA5-42C0F53051BB@apnic.net> <492CEC10.1070109@psg.com>
X-Mailer: Apple Mail (2.929.2)
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sidr-bounces@ietf.org
Errors-To: sidr-bounces@ietf.org

On 26/11/2008, at 4:26 PM, Randy Bush wrote: (quoting ggm, who quotes  
the roa draft)

>> 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

As Yakov Rekhter might say in IDR "please send text"

ie, if you dislike these words, please instead of just knocking down,  
can you help construct?

noting netmask, maxlen, which clearly removed the 'rigorous' -what  
else is wrong with the text?

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