[Sidrops] Fwd: AT&T/as7018 now drops invalid prefixes from peers

Sandra Murphy <sandy@tislabs.com> Mon, 11 February 2019 16:34 UTC

Return-Path: <sandy@tislabs.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id E6FEA131074 for <sidrops@ietfa.amsl.com>; Mon, 11 Feb 2019 08:34:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id vQZRNXzEpTBC for <sidrops@ietfa.amsl.com>; Mon, 11 Feb 2019 08:34:45 -0800 (PST)
Received: from walnut.tislabs.com (walnut.tislabs.com []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E51B12008A for <sidrops@ietf.org>; Mon, 11 Feb 2019 08:34:42 -0800 (PST)
Received: from nova.tislabs.com (unknown []) by walnut.tislabs.com (Postfix) with ESMTP id 5939B28B0041 for <sidrops@ietf.org>; Mon, 11 Feb 2019 11:34:41 -0500 (EST)
Received: from [] (localhost.localdomain []) by nova.tislabs.com (Postfix) with ESMTP id 3E0111F804E; Mon, 11 Feb 2019 11:34:41 -0500 (EST)
From: Sandra Murphy <sandy@tislabs.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0C941098-0436-42A6-9C63-3E30035C2F2D"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Mon, 11 Feb 2019 11:34:44 -0500
References: <23649.35961.352370.101277@oz.mt.att.com>
Cc: Sandra Murphy <sandy@tislabs.com>
To: sidrops@ietf.org
Message-Id: <B07A1487-7AC1-4F48-9D0C-C032E2780DFF@tislabs.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/pZT0FYQjV0Pjdjky740o3FwnGAk>
Subject: [Sidrops] Fwd: AT&T/as7018 now drops invalid prefixes from peers
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 11 Feb 2019 16:34:47 -0000

Great news for RPKI deployment.

One response asked for AT&T to share more about the experience.

Between this and the Cloudflare announcement some months back, someday the world might get to the point that there could be a current practice document for deployment, initial or steady state.


> Begin forwarded message:
> From: Jay Borkenhagen <jayb@braeburn.org>
> Subject: AT&T/as7018 now drops invalid prefixes from peers
> Date: February 11, 2019 at 9:53:45 AM EST
> To: nanog@nanog.org
> Reply-To: Jay Borkenhagen <jayb@braeburn.org>
> FYI:
> The AT&T/as7018 network is now dropping all RPKI-invalid route
> announcements that we receive from our peers.  
> We continue to accept invalid route announcements from our customers,
> at least for now.  We are communicating with our customers whose
> invalid announcements we are propagating, informing them that these
> routes will be accepted by fewer and fewer networks over time.
> Thanks to those of you who are publishing ROAs in the RPKI.  We would
> also like to encourage other networks to join us in taking this step
> to improve the quality of routing information in the Internet.
> Thanks!
> 						Jay B.