Re: [sidr] WGLC: draft-ietf-sidr-usecases-02.txt

Randy Bush <> Thu, 08 September 2011 06:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 10F6B21F8C64; Wed, 7 Sep 2011 23:40:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id XEhk02RNIN90; Wed, 7 Sep 2011 23:40:47 -0700 (PDT)
Received: from ( [IPv6:2001:418:1::36]) by (Postfix) with ESMTP id A278221F8C40; Wed, 7 Sep 2011 23:40:47 -0700 (PDT)
Received: from localhost ([] by with esmtp (Exim 4.76 (FreeBSD)) (envelope-from <>) id 1R1YJq-000ErM-45; Thu, 08 Sep 2011 06:42:38 +0000
Date: Thu, 08 Sep 2011 08:42:36 +0200
Message-ID: <>
From: Randy Bush <>
To: Christopher Morrow <>
In-Reply-To: <>
References: <>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Subject: Re: [sidr] WGLC: draft-ietf-sidr-usecases-02.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 08 Sep 2011 06:40:48 -0000

i do not think this document is at all ready for publication.  someone
with time and energy to clean up the wording needs to spend a half day
with the poor thing.


1.2 i believe that redefining AS and ASN are ill-advised.  just refer
elsewhere.  we readlly do not want to go there.  e.g. there are a lot of
ASs which are not under a single administrative control.

if you insist on defining it, i would probably s/route/as-path/

Aggregate Route makes an assumption that 'more general' and 'specific'
are well definined.  maybe try something like shorter and longer
netmask, or greater or smaller prefix mask length.

'Covering Aggregate' uses 'cover' in its definition, which makes it
pretty useless.

'Multi-homed prefix' is 'originated via'.  is it transited via/through
or originated by/from?


   3.1.  Single Announcement

   An organization (Org A with ASN 64496) has been allocated the prefix  It wishes to announce the /24 prefix from ASN 64496
   such that relying parties interpret the route as intended.

look at rfc 5737 IPv4 Address Blocks Reserved for Documentation

i could go on and on.  essentially this document is sloppy and needs to
be seriously cleaned up.