Re: [Idr] IETF LC for IDR-ish document <draft-ietf-grow-bgp-reject-05.txt> (Default EBGP Route Propagation Behavior Without Policies) to Proposed Standard

[Robert Raszuk <[e-mail]>]

>
> Empty policy is fine -- I have a number of sessions where I
> intentionally have no policy. What I don't want to have happen is
> *accidental* sessions without policy


​BGP peers are usually configured using peer groups or peer templates.
Policy (especially empty one) would be part of such template anyway. So
changing the default ​would not help to prevent anything once the template
is applied. And session without template being applied would in vast
majority of cases not come up anyway.

Only in stub multi-homed small networks which someone configures peers by
hand the new default maybe will help.

As mentioned before for those cases much better would be to have BGP build
in protection.

*Example for new BGP rule: *

*IPv4 and IPv6 eBGP received routes to an AS (routes where AS_PATH contains
other then local ASN) may be advertised over eBGP session to other ASes
only when explicitly allowed by policy. *

Such change in default is actually much more practical to really help in a
lot of cases while not breaking anything to those which have little stub AS
and advertise their PI space of 4 routes. Such change also address cases
where someone just adds once "send all" to template.

Best,
Robert.