IETF Logo Mail Archive

Re: [GROW] call for adoption draft-evens-grow-bmp-adj-rib-out

John Kemp <kemp@network-services.uoregon.edu> Thu, 20 April 2017 18:37 UTC

Return-Path: <kemp@network-services.uoregon.edu>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FB59129BAB for <grow@ietfa.amsl.com>; Thu, 20 Apr 2017 11:37:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f6clkQeKKkGK for <grow@ietfa.amsl.com>; Thu, 20 Apr 2017 11:37:44 -0700 (PDT)
Received: from network-services.uoregon.edu (uowireless.uoregon.edu [IPv6:2001:468:d01:3c::80df:3c5e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 234331314EB for <grow@ietf.org>; Thu, 20 Apr 2017 11:37:42 -0700 (PDT)
Received: from rvpro.routeviews.org (rvpro.routeviews.org [128.223.51.52]) (authenticated bits=0) by network-services.uoregon.edu (8.13.8/8.13.8) with ESMTP id v3KIbnaA031940 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 20 Apr 2017 11:37:52 -0700
Reply-To: kemp@network-services.uoregon.edu
References: <BL2PR01MB193780745973D8183C3BE4CBDF180@BL2PR01MB1937.prod.exchangelabs.com> <21f3da70-c6c9-9cc4-b027-0a03c8105c3a@network-services.uoregon.edu> <26E7F977-6F52-44AD-92AE-EC1E8E97096D@cisco.com>
To: "Tim Evens (tievens)" <tievens@cisco.com>, "grow@ietf.org" <grow@ietf.org>
From: John Kemp <kemp@network-services.uoregon.edu>
Organization: RouteViews, University of Oregon
Message-ID: <ac3e5aea-57e9-9e19-415c-2b173126e0e4@network-services.uoregon.edu>
Date: Thu, 20 Apr 2017 11:37:38 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <26E7F977-6F52-44AD-92AE-EC1E8E97096D@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/N_w-IwO6gtsOXfYRvz3OWuuRClM>
Subject: Re: [GROW] call for adoption draft-evens-grow-bmp-adj-rib-out
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 18:37:45 -0000

And I'm assuming this is not going to be "over complicated" by
things like VRF's... ?

I mean, you don't want to take the extra step of also adding some
kind of naming specificity in the case there are also other local
copies of tables used on the same router... ?

Just asking.  I'm wondering if people want to have that capability
as well.

John Kemp


On 4/19/17 12:58 PM, Tim Evens (tievens) wrote:
> Hi John.
> 
> On 4/19/17, 12:42 PM, "GROW on behalf of John Kemp" <grow-bounces@ietf.org on behalf of kemp@network-services.uoregon.edu> wrote:
> 
>>    Just noticed these.  I'm curious why they weren't combined
>>   into one.  Seems like it's the same topic.
> 
> [TE] The primary reason to have them separated was so that we can work on them independently of each other without becoming to monolithic with the updates.
>    
>>    Other question was, just to make sure, this is everything.
>>    So you got PRE, LOC, and POST covered now, correct?
> 
> [TE] Yes and more.  We have Pre/Post-Policy RIB-In, Pre/Post-Policy RIB-Out, and Loc-RIB.  With these two additional drafts, we should have complete monitoring coverage for BGP of what the router "sees," what the router "does to received," what the router "sends," and what the router "uses."
>    
>>    JohN Kemp
>     
>  
>

v2.23.0 | Report a Bug | By Email