Re: [sidr] various

Randy Bush <randy@psg.com> Sat, 12 November 2011 10:45 UTC

Return-Path: <randy@psg.com>
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 03B2D21F899F for <sidr@ietfa.amsl.com>; Sat, 12 Nov 2011 02:45:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level:
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599]
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 80ljdxjGeQir for <sidr@ietfa.amsl.com>; Sat, 12 Nov 2011 02:45:28 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA6E21F8797 for <sidr@ietf.org>; Sat, 12 Nov 2011 02:45:28 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76 (FreeBSD)) (envelope-from <randy@psg.com>) id 1RPB5T-000LJe-BB; Sat, 12 Nov 2011 10:45:27 +0000
Date: Sat, 12 Nov 2011 18:45:26 +0800
Message-ID: <m2d3cxei0p.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Wesley George <wesley.george@twcable.com>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD4656937791451B2CCE5@PRVPEXVS03.corp.twcable.com>
References: <20111031193803.30761.81234.idtracker@ietfa.amsl.com> <4EB02586.5010101@bbn.com> <DCC302FAA9FE5F4BBA4DCAD4656937791451B2CC8D@PRVPEXVS03.corp.twcable.com> <m2ehxef1ob.wl%randy@psg.com> <DCC302FAA9FE5F4BBA4DCAD4656937791451B2CCDA@PRVPEXVS03.corp.twcable.com> <m2aa81g7hp.wl%randy@psg.com> <DCC302FAA9FE5F4BBA4DCAD4656937791451B2CCE5@PRVPEXVS03.corp.twcable.com>
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
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] various
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: Sat, 12 Nov 2011 10:45:29 -0000

> "However, signed updates received from BGPSec speakers outside of the
> confederation (i.e. those transiting the confederation ASes) MUST be
> passed to the other Member-ASes BGPSec speakers intact.

nope.  you could decide to strip toward one or more confed peers which
are not bgpsec capable.  your routers, your decision, your policy.
don't go there.

the rule was very intentionally precise and simple, two members of the
same confderation must not add sigs toward each other.  

imiho, saying anything more is either adding unnecessary words at best
or opening up large complexity holes at worst.

>> tell that to someone trying to secure some multi-as private network
>> using rfc 1918 addresses and asns.
> [WEG] you know I debated making a clarifying exception to the above

i try to minimize statements that require clarifying exceptions.  they
tend to open primrose paths with no proof of termination.

> I figured it'd be clear from the above discussion

and yet you want to me to go into unnecessary complications not directly
needed given my brutally specific statement?  :)

randy