Re: [Sidrops] draft-ymbk-sidrops-ov-clarify-01.txt
Randy Bush <randy@psg.com> Sat, 07 October 2017 00:51 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 C58C7133342 for <sidrops@ietfa.amsl.com>; Fri, 6 Oct 2017 17:51:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 RrzpjVQ7_VCU for <sidrops@ietfa.amsl.com>; Fri, 6 Oct 2017 17:51:51 -0700 (PDT)
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 BC24113331E for <sidrops@ietf.org>; Fri, 6 Oct 2017 17:51:51 -0700 (PDT)
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 1e0dLJ-0004IT-Uf; Sat, 07 Oct 2017 00:51:50 +0000
Date: Sat, 07 Oct 2017 09:51:48 +0900
Message-ID: <m2d15zn5jv.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Jakob Heitz <jheitz@cisco.com>
Cc: SIDR Operations WG <sidrops@ietf.org>
In-Reply-To: <4bb0679ec1284441a50d9a0ebb48e070@XCH-ALN-014.cisco.com>
References: <m2k22qzqm7.wl-randy@psg.com> <50b3ef1b548d4726a5628d5edf53cf2d@XCH-ALN-014.cisco.com> <m2h8vbn87h.wl-randy@psg.com> <4bb0679ec1284441a50d9a0ebb48e070@XCH-ALN-014.cisco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.2 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/3KO-0LK1Oj7eQW4UgkFUTHQ7B9w>
Subject: Re: [Sidrops] draft-ymbk-sidrops-ov-clarify-01.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: Sat, 07 Oct 2017 00:51:53 -0000
hi jakob, > 0 helps if an AS is not announcing its prefix in BGP. Registering it > under AS0 causes the evil announcement to be invalid. The evil > announcer cannot prepend 0. Of course, it should register under AS0 > only, not under its own ASN. > > RPKI is actually really good at protecting unannounced prefixes. It > can protect announced prefixes if you can manage to get a shorter > AS_PATH length than the evil prepended path. yep, all true. but, imiho, not for this doc. this doc is meant to clarify some things that implementations have shown to be insufficiently clear in 6811, how announcement are validated in a router, not in 7115, operational practices. but if you think your comments could be used to clarify 7115, i have no problem with that. randy
- [Sidrops] draft-ymbk-sidrops-ov-clarify-01.txt Randy Bush
- Re: [Sidrops] draft-ymbk-sidrops-ov-clarify-01.txt Jakob Heitz (jheitz)
- Re: [Sidrops] draft-ymbk-sidrops-ov-clarify-01.txt Randy Bush
- Re: [Sidrops] draft-ymbk-sidrops-ov-clarify-01.txt Jakob Heitz (jheitz)
- Re: [Sidrops] draft-ymbk-sidrops-ov-clarify-01.txt Randy Bush