Yes thx both to Bruno and Jakob to bring the hard CEASE option as solution.
Subject draft is addressed. But we all need to watch for similar assumptions and consequences when persistent bgp feature is enabled. Best, R. On Wed, Jul 31, 2019, 03:21 Jakob Heitz (jheitz) <jhe...@cisco.com> wrote: > In response to Robert's point on the IDR list related to > draft-uttaro-idr-bgp-persistence: > > If BGP session terminates unexpectedly - say when max prefix is reached - > it is quite unclear on the operational consequences of such duet of > features enabled together. > > > > may I suggest that response to the outbound maximum prefix exceeded event > should be a hard CEASE > > as defined in https://tools.ietf.org/html/rfc8538. It already suggests to > use a hard CEASE for an > > inbound maximum prefix exceeded event. > > > > Robert, will that satisfy your concern with persistence? > > > > Regards, > > Jakob. > > > > *From:* GROW <grow-boun...@ietf.org> *On Behalf Of * Melchior Aelmans > *Sent:* Thursday, July 25, 2019 5:00 AM > *To:* grow@ietf.org > *Subject:* [GROW] Request WG Adoption for draft-sa-grow-maxprefix > > > > Hi WG, > > > > We would like to request WG adoption for > https://datatracker.ietf.org/doc/draft-sa-grow-maxprefix/ > > > > Thanks, > > Melchior > _______________________________________________ > GROW mailing list > GROW@ietf.org > https://www.ietf.org/mailman/listinfo/grow >
_______________________________________________ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
