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

Di Ma <madi@zdns.cn> Mon, 11 February 2019 16:47 UTC

Return-Path: <madi@zdns.cn>
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 14C4F130EBB for <sidrops@ietfa.amsl.com>; Mon, 11 Feb 2019 08:47:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level:
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 DGqMLunV38YM for <sidrops@ietfa.amsl.com>; Mon, 11 Feb 2019 08:47:07 -0800 (PST)
Received: from smtpbguseast3.qq.com (smtpbguseast3.qq.com [54.243.244.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7904A131058 for <sidrops@ietf.org>; Mon, 11 Feb 2019 08:47:05 -0800 (PST)
X-QQ-mid: bizesmtp12t1549903619t04l7d0r
Received: from [192.168.3.18] (unknown [118.247.10.155]) by esmtp6.qq.com (ESMTP) with id ; Tue, 12 Feb 2019 00:46:56 +0800 (CST)
X-QQ-SSF: 00400000002000M0ZI70B00A0000000
X-QQ-FEAT: +IkrLX7ElIJQftKf0YEMjUhR4K3VKY0/L+7lKt05qAG0DFsKYRGsLj6q/GyiO MfpHaAnYaCuWZWsytWC5euKtB5ZKa3QRxFKr0T8HurnNCPJflcJnYM6Sw5DX0r2eObYZxDM 1Ia9HVJKPwIh12D/r/dJYhLYdZhx/9idw2qF4sQck7b8tImpCBNbyhwQEFUziYf6LRXUypZ m6KTAyYzxHZi+ffeuH9BKWdZit9x+p/8VYRazN+d65V04dG6L4Fny55KIgKo2kPJWvwKgLF RJ353eMejeA1ZKCo9o5KkgZHATIZPrCE4L9t4VmQG3iUmf
X-QQ-GoodBg: 1
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Di Ma <madi@zdns.cn>
In-Reply-To: <B07A1487-7AC1-4F48-9D0C-C032E2780DFF@tislabs.com>
Date: Tue, 12 Feb 2019 00:46:55 +0800
Cc: sidrops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <19FC2A7A-574C-467D-A0B7-079CAEF595FC@zdns.cn>
References: <23649.35961.352370.101277@oz.mt.att.com> <B07A1487-7AC1-4F48-9D0C-C032E2780DFF@tislabs.com>
To: Sandra Murphy <sandy@tislabs.com>
X-Mailer: Apple Mail (2.3445.102.3)
X-QQ-SENDSIZE: 520
Feedback-ID: bizesmtp:zdns.cn:qybgforeign:qybgforeign2
X-QQ-Bgrelay: 1
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/33nAnaMVd1O-tOhLNkHHAjlnG-0>
Subject: Re: [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:47:12 -0000

Sandy,

Thanks for sharing. 

Glad to know another ISP to let the RPKI take effect.

Is there an official statement from AT&T on this for reference? 

Di

> 在 2019年2月12日,00:34,Sandra Murphy <sandy@tislabs.com> 写道:
> 
> 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.
> 
> —Sandy
> 
> 
>> 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.
>> 
>> 
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops