IETF Logo Mail Archive

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

"i3D.net - Martijn Schmidt" <martijnschmidt@i3d.net> Thu, 20 April 2017 13:38 UTC

Return-Path: <martijnschmidt@i3d.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 1FF8F12F268 for <idr@ietfa.amsl.com>; Thu, 20 Apr 2017 06:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 NyXpu8952avw for <idr@ietfa.amsl.com>; Thu, 20 Apr 2017 06:38:10 -0700 (PDT)
Received: from mail.i3d.net (mail.i3d.nl [213.163.77.240]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAA43129AF7 for <idr@ietf.org>; Thu, 20 Apr 2017 06:38:09 -0700 (PDT)
X-Footer: aTNkLm5s
Received: from localhost ([127.0.0.1]) by mail.i3d.net with ESMTPSA (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128 bits)); Thu, 20 Apr 2017 15:38:04 +0200
To: Jared Mauch <jared@puck.nether.net>, Keyur Patel <keyur@arrcus.com>
References: <D4E812E8-AA7B-4EA2-A0AC-034AA8922306@juniper.net> <9047A5A0-ED12-43C2-B2C5-D2A71CBB4373@arrcus.com> <D51D46A7.A9732%acee@cisco.com> <0A49219D-E721-4DA8-B9BF-A55C2FA36FBE@puck.nether.net> <D95C67A4-AEBF-400B-A360-61C342FD6E4A@arrcus.com> <DFD12A2C-ED40-4550-A65F-22322CFDEEBC@puck.nether.net>
Cc: Hares Susan <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
From: "i3D.net - Martijn Schmidt" <martijnschmidt@i3d.net>
Organization: i3D.net
Message-ID: <f7cc33e7-de3b-fde5-4dc0-9b8d3ead3e3b@i3d.net>
Date: Thu, 20 Apr 2017 15:37:28 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <DFD12A2C-ED40-4550-A65F-22322CFDEEBC@puck.nether.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/NesbrvNt_jHx-Bq-n_nJYx1Ehsg>
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:38:12 -0000

On 20-04-17 15:33, Jared Mauch wrote:
>> On Apr 19, 2017, at 6:16 PM, Keyur Patel <keyur@arrcus.com> wrote:
>>
>> And that would be good enough if that would allow exemptions of DC networks and any other networks that may need exemption.
> I’m not sure what makes DC networks unique to be exempt from adding a one line policy to their configuration, this is a very low bar similar to configuring a hostname or AAA authentication that a DC network would have come from their ZTP/automation.
>
> I find this incredibly worrisome thinking, next we will have an exemption for government run networks to what end?
>
> - Jared
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
Hi all,

DC network operator here! As long as it's well documented, adding a new 
line to my configuration shouldn't be a problem when I'm doing an 
upgrade during a maintenance window anyway. Moreover, we operate our 
network on a "trust nothing" basis even for our internal BGP sessions.

Best regards,
Martijn Schmidt
i3D.net / AS49544

v2.23.0 | Report a Bug | By Email