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

Jared Mauch <jared@puck.nether.net> Thu, 20 April 2017 13:58 UTC

Return-Path: <jared@puck.nether.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 632681205F0 for <idr@ietfa.amsl.com>; Thu, 20 Apr 2017 06:58:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9VCDpAzsFBT4 for <idr@ietfa.amsl.com>; Thu, 20 Apr 2017 06:58:49 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB3A1204DA for <idr@ietf.org>; Thu, 20 Apr 2017 06:58:49 -0700 (PDT)
Received: from [IPv6:2603:3015:3603:8e00:25c2:4c02:5849:c73d] (unknown [IPv6:2603:3015:3603:8e00:25c2:4c02:5849:c73d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id D6CE6540C0C; Thu, 20 Apr 2017 09:58:47 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <26662_1492682306_58F88642_26662_8569_1_53C29892C857584299CBF5D05346208A31CC0240@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Date: Thu, 20 Apr 2017 09:58:30 -0400
Cc: Job Snijders <job@ntt.net>, idr wg <idr@ietf.org>, Hares Susan <shares@ndzh.com>, Robert Raszuk <robert@raszuk.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D6039F63-2054-44DA-8583-348DE2D165DD@puck.nether.net>
References: <D4E812E8-AA7B-4EA2-A0AC-034AA8922306@juniper.net> <abe393d3-d1e4-7841-4620-38dab751765b@cisco.com> <CA+b+ERnRz8BEO3mb1fnsDPoiL6Wxjdfw9vQPbyODNEa+xCJdnw@mail.gmail.com> <D51D67E4.A9782%acee@cisco.com> <AF07526F-F08B-4084-937B-A9A2D2DD2813@juniper.net> <CA+b+ERnRbAG_WSppAVkWETL0zjeppmm9fwqRu8DV24Hcdihqiw@mail.gmail.com> <20170420090535.cfxn5tbhns5bszvf@hanna.meerval.net> <4993_1492680765_58F8803D_4993_4017_1_53C29892C857584299CBF5D05346208A31CBFE4F@OPEXCLILM21.corporate.adroot.infra.ftgroup> <20170420093706.ongrlwi47kew6vt2@hanna.meerval.net> <26662_1492682306_58F88642_26662_8569_1_53C29892C857584299CBF5D05346208A31CC0240@OPEXCLILM21.corporate.adroot.infra.ftgroup>
To: bruno.decraene@orange.com
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/U7uuRVUKHO8EarWV7ybBZOe0m8M>
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-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 13:58:50 -0000

> On Apr 20, 2017, at 5:58 AM, <bruno.decraene@orange.com>; <bruno.decraene@orange.com>; wrote:
> 
> The question was whether this new default policy could be proposed (or imposed) as a BCP only for _new_ implementations.
> And by new implementations, I mean new source code (e.g. RtBrick) not a software upgrade of an existing code.

My existing $dayjob vendors should expect we would not purchase equipment that is not secure out of the box.  If product management can’t get behind a strategy of secure devices, this speaks volumes to me and will impact our purchasing.

- Jared