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

<> Tue, 25 April 2017 07:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 286381289B0 for <>; Tue, 25 Apr 2017 00:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.398
X-Spam-Status: No, score=-5.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id XbA321tWq781 for <>; Tue, 25 Apr 2017 00:25:42 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 790F612896F for <>; Tue, 25 Apr 2017 00:25:42 -0700 (PDT)
Received: from (unknown [xx.xx.xx.66]) by (ESMTP service) with ESMTP id CE2AAC009F; Tue, 25 Apr 2017 09:25:40 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.24]) by (ESMTP service) with ESMTP id 98CC5120089; Tue, 25 Apr 2017 09:25:40 +0200 (CEST)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM7D.corporate.adroot.infra.ftgroup ([fe80::9044:c5ee:4dd2:4f16%19]) with mapi id 14.03.0319.002; Tue, 25 Apr 2017 09:25:40 +0200
To: Christopher Morrow <>, "Acee Lindem (acee)" <>
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: AQHSvSzT7FfrXgMKmU+OEgrGuKcw4aHVrpgg
Date: Tue, 25 Apr 2017 07:25:40 +0000
Message-ID: <1058_1493105140_58FEF9F4_1058_786_3_53C29892C857584299CBF5D05346208A31CCAD43@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A31CCAD43OPEXCLILM21corp_"
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: Tue, 25 Apr 2017 07:25:45 -0000

From: Christopher Morrow Sent: Monday, April 24, 2017 8:59 PM

On Wed, Apr 19, 2017 at 7:30 PM, Acee Lindem (acee) <<>> wrote:

On 4/19/17, 7:25 PM, "John Scudder" <<>> wrote:

>(As an individual contributor)
>On Apr 19, 2017, at 7:18 PM, Acee Lindem (acee) <<>> wrote:
>> the draft is conspicuously missing a “Backwards Compatibility” section.
>Seriously? "Backwards compatibility" in this case is "configure your
>router to do what it used to", right? We need a section to say that?

Anytime one proposes to change the default behavior of a decades old
protocol to be more restrictive, I would expect this to be discussed.

a few times in this discussion people say: "the protocol", but the draft doesn't propose changing the protocol, it proposes that implementations stop being wide-open with respect to send/receive conditioning/filtering.

There's no default behavior change in the protocol (which I think doesn't really talk about filtering prefixes at all, not in the sense of 'prefix-list foo in' anyway).

[Bruno] There seem to be various opinions about this. This is a bit of a concern at this stage. In particular, some previous comments/support may have used the wrong assumptions.
If this is indeed the goal to make no protocol change, including no default behavior change in the protocol, could the document be updated to state this. In which case, Standard Track may be required.



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.