Re: [Idr] I-D Action: draft-sas-idr-maxprefix-inbound-02.txt

Hi Robert

I agree “soft-reconfigure inbound” should be mentioned.

With route refresh version 1 RFC 2918 the adj-rib-out or  adj-rib-in
dynamically with a soft clear in or out CLi command.

With RFC 7513 provided an enhancement to dynamically update the  adj-rib
without a CLI soft clear.

The cisco “soft-reconfigure inbound” existed for a long time prior to RFC
2918 where it creates an additional pre policy RIB, essentially a copy of
the BGP rib - pre policy.  Soft-reconfigure was the way Cisco was able to
do soft clear so you don’t have to hard clear a peer.

Once RFC 2918 came out some operators ripped out the soft-reconfigure,
however a lot of operations kept in place for troubleshooting BGP policies
issues looking at the “pre policy” RIB in and out.

For maxim prefix with  soft-reconfigure configured on a peer, I think the
pre policy rib could change or be impacted so we should definitely include
in the draft.  Since soft is pre policy and maximum prefix acts on
adj-rib-in post policy I am guessing that it may not impact the pre policy
rib.

Kind Regards

Gyan

On Thu, Apr 15, 2021 at 8:17 AM Robert Raszuk <robert@raszuk.net> wrote:

> Authors,
>
> I think I have one question or suggestion.
>
> As you all  know some implementations allow you to explicitly force BGP
> speaker to keep (pre-policy) all routes/paths received.
>
> Example:
>
> neighbor 192.168.1.1 soft-reconfiguration inbound
>
> The draft does not seem to comment on this case yet if implementation
> maintains the above behaviour
> at least some of the justifications for the document is gone.
>
> I think that draft should at least mention such behaviour, not force to
> change it however put some light that if
> configured by the operator some of the benefits of inbound prefix limit
> will not be fully effective.
>
> Many thx,
> Robert.
>
>
>
>
>
>
>
> On Wed, Apr 14, 2021 at 11:27 PM <internet-drafts@ietf.org> wrote:
>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>
>>
>>         Title           : BGP Maximum Prefix Limits Inbound
>>         Authors         : Melchior Aelmans
>>                           Massimiliano Stucchi
>>                           Job Snijders
>>         Filename        : draft-sas-idr-maxprefix-inbound-02.txt
>>         Pages           : 8
>>         Date            : 2021-04-14
>>
>> Abstract:
>>    This document describes mechanisms to limit the negative impact of
>>    route leaks [RFC7908] and/or resource exhaustion in BGP [RFC4271]
>>    implementations.
>>
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-sas-idr-maxprefix-inbound/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-sas-idr-maxprefix-inbound-02
>> https://datatracker.ietf.org/doc/html/draft-sas-idr-maxprefix-inbound-02
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-sas-idr-maxprefix-inbound-02
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*

*M 301 502-1347*