IETF Logo Mail Archive

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

Randy Bush <randy@psg.com> Fri, 21 September 2012 09:13 UTC

Return-Path: <randy@psg.com>
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 754A621F871E for <idr@ietfa.amsl.com>; Fri, 21 Sep 2012 02:13:52 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rpJccY2WAxZQ for <idr@ietfa.amsl.com>; Fri, 21 Sep 2012 02:13:52 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 19D1F21F871C for <idr@ietf.org>; Fri, 21 Sep 2012 02:13:52 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TEzIz-000M3t-56; Fri, 21 Sep 2012 09:13:49 +0000
Date: Fri, 21 Sep 2012 18:13:48 +0900
Message-ID: <m2bogzivqr.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
In-Reply-To: <CAL9jLaYQNDVC7Dj02e-XtwrtKj-11kGTSaL1MUGTokT2XOgZLg@mail.gmail.com>
References: <24B20D14B2CD29478C8D5D6E9CBB29F625F706AF@CMA-MB003.columbia.ads.sparta.com> <D7AC4E75-4B51-4F60-8B41-9B8EB3AEA3ED@juniper.net> <505C0228.40805@raszuk.net> <CAL9jLaYQNDVC7Dj02e-XtwrtKj-11kGTSaL1MUGTokT2XOgZLg@mail.gmail.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.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Cc: idr wg <idr@ietf.org>, Robert Raszuk <robert@raszuk.net>
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: Fri, 21 Sep 2012 09:13:52 -0000

> I don't see why this is as much of an issue, particularly for any
> monitoring code/station/system... if they don't do bgpsec, they just
> see the same data as they do today. no changes are required,
> operations continue, people stay happy... win?

<pedantry>

sometimes, we will want to monitor the bgpsec aspects as well.  and
those monitors will do the capability negotiation for bgpsec, so will
get bgpsec as_sec_paths, which is cool.

randy

v2.23.0 | Report a Bug | By Email