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

["Dickinson, Ian" <[e-mail]>]

Inline with [IanD]

-----Original Message-----
From: Idr [mailto:[e-mail]] On Behalf Of Jared Mauch
Sent: 20 April 2017 14:56
To: [e-mail]
Cc: [e-mail]; Hares Susan <[e-mail]>
Subject: 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


> On Apr 20, 2017, at 5:50 AM, <[e-mail]> <[e-mail]> wrote:
>
> Because I think the document means "configured route (re)distribution/advertisement policy".
> Possibly this was implied by the word "export" but one could read this as any outbound policy, while a policy setting some communities would probably not help much.

IMO:

someone writing the policy statement saying

term { accept; }

is enough to satisfy my concerns, it’s when people do nothing and are left sending their full rib back to their upstream causing load it’s a problem.  While we’ve moved past the days of 11.1&12.0 in IOS land where there was a high cost on the CPUs to x86 compute where the burden is less, it’s still additional processing and a resource consumer.

[IanD] The larger issue here is not local load causing impact to the "perpetrator" but the leak effectively hijacking traffic that has a much larger blast radius. I've been annoyed at implementations failing open for years, and I'd like to see this addressed. I think this draft at least codifies good behaviour and I support it.

- Jared

_______________________________________________
Idr mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/idr
Information in this email including any attachments may be privileged, confidential and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you have received it in error, please notify the sender by return e-mail and delete it from your system. You should not reproduce, distribute, store, retransmit, use or disclose its contents to anyone. Please note we reserve the right to monitor all e-mail communication through our internal and external networks. SKY and the SKY marks are trademarks of Sky plc and Sky International AG and are used under licence.

Sky UK Limited (Registration No. 2906991), Sky-In-Home Service Limited (Registration No. 2067075) and Sky Subscribers Services Limited (Registration No. 2340150) are direct or indirect subsidiaries of Sky plc (Registration No. 2247735). All of the companies mentioned in this paragraph are incorporated in England and Wales and share the same registered office at Grant Way, Isleworth, Middlesex TW7 5QD.