IETF Logo Mail Archive

Re: [Idr] draft-ietf-sidr-bgpsec-protocol-05 being WGLC'd in sidr

Danny McPherson <danny@tcb.net> Wed, 26 September 2012 16:27 UTC

Return-Path: <danny@tcb.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF1DB21F8527 for <idr@ietfa.amsl.com>; Wed, 26 Sep 2012 09:27:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.687
X-Spam-Level:
X-Spam-Status: No, score=-102.687 tagged_above=-999 required=5 tests=[AWL=-0.087, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hj+1BypQCKDB for <idr@ietfa.amsl.com>; Wed, 26 Sep 2012 09:27:08 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by ietfa.amsl.com (Postfix) with ESMTP id 2C53021F84F8 for <idr@ietf.org>; Wed, 26 Sep 2012 09:27:08 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id ABB3A2680C7; Wed, 26 Sep 2012 10:27:07 -0600 (MDT)
Received: from dul1dmcphers-m2.vcorp.ad.vrsn.com (nat1.corp-fo.iad1.verisign.com [216.168.230.7]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Wed, 26 Sep 2012 10:27:07 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=216.168.230.7; client-port=10143; syn-fingerprint=65535:53:1:64:M1460,N,W3,N,N,T,S MacOS 10.4.8; data-bytes=0
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="us-ascii"
From: Danny McPherson <danny@tcb.net>
X-Priority: Normal
In-Reply-To: <571358400-1348663504-cardhu_decombobulator_blackberry.rim.net-1797235029-@b12.c6.bise6.blackberry>
Date: Wed, 26 Sep 2012 12:27:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <67BAB02A-12B3-46C3-B660-66A93BDCCB0D@tcb.net>
References: <24B20D14B2CD29478C8D5D6E9CBB29F625F706AF@CMA-MB003.columbia.ads.sparta.com> <D7AC4E75-4B51-4F60-8B41-9B8EB3AEA3ED@juniper.net> <C3260DC8-984E-47B7-9738-01A61EA99EA4@tcb.net> <571358400-1348663504-cardhu_decombobulator_blackberry.rim.net-1797235029-@b12.c6.bise6.blackberry>
To: shares@ndzh.com
X-Mailer: Apple Mail (2.1283)
Cc: "idr@ietf. org" <idr@ietf.org>
Subject: Re: [Idr] draft-ietf-sidr-bgpsec-protocol-05 being WGLC'd in sidr
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Sep 2012 16:27:08 -0000

On Sep 26, 2012, at 4:01 AM, shares@ndzh.com wrote:

> Danny:
> 
> I would suggest the following  things prior to accepting this change
> 
> 1) Your proposal for threat analysis and requirements,
> 2) Deployments reports on interoperability on this feature,
> 3) Transition reports - in and out of bgpsecure zone.
> 4) Scaling in deployment
> 
> What do think?

Besides not being sure what "bgpsecure zone" is, yes -- these certainly seem like the kind of things that IDR and folks that operate BGP-speaking routers that this work _will impact should be asking.  

-danny

v2.23.0 | Report a Bug | By Email