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

<> Thu, 20 April 2017 09:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id ADC4212EBE8 for <>; Thu, 20 Apr 2017 02:40:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id N0dnsAyXBudX for <>; Thu, 20 Apr 2017 02:40:53 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B2DE112EBEB for <>; Thu, 20 Apr 2017 02:40:52 -0700 (PDT)
Received: from (unknown [xx.xx.xx.9]) by (ESMTP service) with ESMTP id 1ACE5160514; Thu, 20 Apr 2017 11:40:51 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.13]) by (ESMTP service) with ESMTP id E782AC0085; Thu, 20 Apr 2017 11:40:50 +0200 (CEST)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM6D.corporate.adroot.infra.ftgroup ([fe80::54f9:a6c3:c013:cbc7%19]) with mapi id 14.03.0319.002; Thu, 20 Apr 2017 11:40:50 +0200
To: Job Snijders <>, Enke Chen <>
CC: Hares Susan <>, idr wg <>
Thread-Topic: [Idr] IETF LC for IDR-ish document <draft-ietf-grow-bgp-reject-05.txt> (Default EBGP Route Propagation Behavior Without Policies) to Proposed Standard
Thread-Index: AQHSubXXFx6qnNOc8UaJCUOYEKex/KHN/y1Q
Date: Thu, 20 Apr 2017 09:40:50 +0000
Message-ID: <25911_1492681251_58F88222_25911_625_1_53C29892C857584299CBF5D05346208A31CBFF52@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
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
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 20 Apr 2017 09:40:54 -0000

> From: Idr [] On Behalf Of Job Snijders  > Sent: Thursday, April 20, 2017 11:10 AM
 > On Wed, Apr 19, 2017 at 04:34:10PM -0700, Enke Chen wrote:
 > > I had "in this case" with the statement "the default can not be changed".
 > > The reason is that the behavior change may completely cutoff connectivity
 > > in this case.
 > And very soon after the cutoff a customer may elect to roll back the
 > change and read the release notes!
 > The 'complete cutoff' only occurs after a specific sequence of events
 > which together would represent a cascading failure in due diligence.

The document is asking network operators which have correctly configured their network to retrofit the configuration of 1000s of EBGP configurations, in order to accommodate some operators which are not capable of correctly configuring their EBGP session.
Plus the solution is asking those later operators to do a configuration, while the assumption is that they can't be trusted to correctly configured their EBGP session. Why do you think that they won't just copy/past 1 additional line of configuration in order automatically distribute all the routes for each new EBGP session?

Kind regards,
 > Given that we've suffered through decennia of insecure behaviour on some
 > platforms, I'd be careful to weigh the cost of such a self-inflicted
 > 'complete cutoff' against the cost on internet operations in general to
 > persist in the folly behaviour that some platforms present.
 > Kind regards,
 > Job
 > _______________________________________________
 > Idr mailing list


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.