Re: [GROW] Route Server ASN stripping hiding considered harmful?

Nick Hilliard <nick@foobar.org> Mon, 18 December 2017 15:32 UTC

Return-Path: <nick@foobar.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30CDA127369 for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 07:32:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level:
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, 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 cfXcZkKg9MJq for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 07:32:57 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5147B12708C for <grow@ietf.org>; Mon, 18 Dec 2017 07:32:57 -0800 (PST)
X-Envelope-To: grow@ietf.org
Received: from crumpet.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id vBIFWE51048886 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Dec 2017 15:32:15 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.local
Message-ID: <5A37DF7D.9040405@foobar.org>
Date: Mon, 18 Dec 2017 15:32:13 +0000
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.22 (Macintosh/20171208)
MIME-Version: 1.0
To: Job Snijders <job@ntt.net>
CC: "i3D.net - Martijn Schmidt" <martijnschmidt@i3d.net>, grow@ietf.org
References: <20171218105034.GD43144@vurt.meerval.net> <3f590dcc-da77-6349-6d36-cbd22c0b9693@nordu.net> <36e13c57-ac32-9fe9-ef31-e59ab1bc0c21@i3d.net> <20171218150741.GC1009@hanna.meerval.net>
In-Reply-To: <20171218150741.GC1009@hanna.meerval.net>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/tHLixEnsUzDhHtjdUXHeGNMNDzg>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Dec 2017 15:32:59 -0000

Job Snijders wrote:
> Right now some IXPs are using the IETF RFCs as a justification to not
> hide their ASN in the AS_PATH - and unfortunately some of them gloss
> over the recommendations to apply ingress filters. 

the two RS RFCs are split: one is a specification of what BGP must do,
and the other is a recommendation on operational issues.  Glossing over
the fact that IXP operators have not been inserting the rsasn since the
mid 1990s and that the RFCs are dated 2016, the document that IXPs need
to use is the operations doc: rfc7948, which says that RSs should be
operated in compliance with all the bits of rfc7454 that talk about
filtering. Stopping routing leaks is the aim of the game here.

> I mentioned before, I suspect that the route server's lack of visiblity
> is a direct contributor to the reluctance to apply filters on route
> servers.

Job, seriously, if you have helpful or useful comments to make, then
please make them.

Nick