NOTE: Sorry for the delay... end of year commitments are pressing... Addressing 
these comments in descending order. 

See inline marked [tievens]


On 12/13/18, 12:26 PM, "Jakob Heitz (jheitz)" <[email protected]> wrote:

    Most of the routes will be deleted anyway.
    Only the locally originated routes will remain.
    
    I would suggest to keep the implicit withdraw behavior and not
    to explicitly withdraw any loc-rib routes when they go away.
    That means, the BGP speaker will send BMP loc-rib peer-down,
    not withdraw any routes to BMP and resend the locally originated
    routes again.


[tievens] As in the previous response, we have no choice but to clear the 
list/RIB and start over upon PEER DOWN/UP in order to maintain a consist 
Loc-RIB (e.g we are not just a log of history events, we are maintaining the 
RIB that should mirror the router's RIB state).  Local-RIB peer should not 
result in a DOWN just because one or more peers have gone down.  The expected 
behavior is that Loc-RIB peer will send withdraws or updates based on changes, 
as it would for Adj-RIB-Out.     
 

   I don't believe GR activates in this case, because when the ASN or
    BGP-ID changes, a NOTIFICATION will be sent. Can someone confirm?

[tievens] A change in BGP-ID is a change in BMP peer header. This MUST require 
a peer DOWN and PEER UP.
    
    Regards,
    Jakob.
    
    -----Original Message-----
    From: Jeffrey Haas <[email protected]> 
    Sent: Thursday, December 13, 2018 11:26 AM
    To: Jakob Heitz (jheitz) <[email protected]>
    Cc: Paolo Lucente <[email protected]>; [email protected]; 
[email protected]
    Subject: Re: [GROW] BMP loc-rib Peer-Type behavior
    
    Jakob,
    
    On Thu, Dec 13, 2018 at 07:12:08PM +0000, Jakob Heitz (jheitz) wrote:
    > Wait, a BMP server is not a BGP peer. It does not replicate a routing 
table.
    > It is a logger/processor of information. It doesn't "delete" older 
information,
    > just because some newer information arrived.
    > Its purpose it to tell you what happened at some time in the past,
    > because you are trying to debug a problem or do some capacity planning
    > or whatever. Just because a BGP router changed its BGP-ID does not mean
    > that all the routes it had 2 days ago magically did not happen.
    
    
    RFC 7854:
    :    A Peer Down message implicitly withdraws all routes that were
    :    associated with the peer in question.  A BMP implementation MAY omit
    :    sending explicit withdraws for such routes.
    
    -- Jeff
    

_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow

Reply via email to