Re: [Sidrops] New Version Notification for draft-sriram-sidrops-drop-invalid-policy-00.txt

Randy Bush <randy@psg.com> Sun, 11 March 2018 03:50 UTC

Return-Path: <randy@psg.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 045881270A3 for <sidrops@ietfa.amsl.com>; Sat, 10 Mar 2018 19:50:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, WEIRD_PORT=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 W981RzUAu3xh for <sidrops@ietfa.amsl.com>; Sat, 10 Mar 2018 19:50:20 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DA141200C5 for <sidrops@ietf.org>; Sat, 10 Mar 2018 19:50:20 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1eus03-000340-2U; Sun, 11 Mar 2018 03:50:19 +0000
Date: Sun, 11 Mar 2018 12:50:17 +0900
Message-ID: <m237176zk6.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Job Snijders <job@ntt.net>
Cc: SIDR Operations WG <sidrops@ietf.org>
In-Reply-To: <20180310120844.GC35705@vurt.meerval.net>
References: <152029076512.12908.14537578849320525718.idtracker@ietfa.amsl.com> <BYAPR09MB2773819AB3961189CDA9B4D784D90@BYAPR09MB2773.namprd09.prod.outlook.com> <074D75CB-7D34-4838-BEAA-88AE5E044F6C@ripe.net> <20180310120844.GC35705@vurt.meerval.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/giwQgu-fGi8CI7TDbcjcvmNCVRo>
Subject: Re: [Sidrops] New Version Notification for draft-sriram-sidrops-drop-invalid-policy-00.txt
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Mar 2018 03:50:22 -0000

> Take as example the DE-CIX Peering LAN prefix (taken from
> https://www.peeringdb.com/ix/31) - it is not really globally
> reachable, and that is the intention. What we see here though that
> some folks carry it in their IGP
> http://lg.ring.nlnog.net/prefix_detail/lg01/ipv4?q=80.81.192.0 and
> seem to advertise it by accident to this collector.
> 
> These accidental announcements shouldn't be accepted, ever. This is the
> ROA: http://localcert.ripe.net:8088/roas?q=80.81.192.0 - with the
> current DSIR idea they _would_ be accepted if I am not mistaken.
> 
> DE-CIX is not announcing the peering lan prefix for various operational
> reasons, and the ROA should help supress global visiblity, especially
> the global visibility of more-specifics. More-specifics of the peering lan
> are disastrous for IXPs.

who has the authority to issue valid roas for any possibly improper
subset of the de-cix lan?

if someone else announces a possibly improper subset of that lan,
it's a misannouncement and would be marked invalid.

if you hear that announcement and believe it, who's the fool?

randy