Re: [sidr] Benoit Claise's No Objection on draft-ietf-sidr-bgpsec-ops-16: (with COMMENT)

Randy Bush <randy@psg.com> Thu, 05 January 2017 15:26 UTC

Return-Path: <randy@psg.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22F52129B5F; Thu, 5 Jan 2017 07:26:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.001
X-Spam-Level:
X-Spam-Status: No, score=-10.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-3.1, 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 agrvfWV9iv5e; Thu, 5 Jan 2017 07:26:56 -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 39C7C12995C; Thu, 5 Jan 2017 07:26:56 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cP9wJ-000105-Br; Thu, 05 Jan 2017 15:26:51 +0000
Date: Fri, 06 Jan 2017 00:26:48 +0900
Message-ID: <m2r34hfryf.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Benoit Claise <bclaise@cisco.com>
In-Reply-To: <148362671909.20702.5167377044454314977.idtracker@ietfa.amsl.com>
References: <148362671909.20702.5167377044454314977.idtracker@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 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/sidr/DCxXSzMIvbUaN_rP5WWLI7Spu_A>
Cc: Sheng Jiang <jiangsheng@huawei.com>, The IESG <iesg@ietf.org>, sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] Benoit Claise's No Objection on draft-ietf-sidr-bgpsec-ops-16: (with COMMENT)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jan 2017 15:26:57 -0000

> Proposal: one extra section on migration/deployability
> There is text in draft-ietf-sidr-bgpsec-protocol-21
> 
>    How will migration from BGP to BGPsec look like?  What are the
>    benefits for the first adopters?  Initially small groups of
>    contiguous ASes would be doing BGPsec.  There would be possibly one
>    or more such groups in different geographic regions of the global
>    Internet.  Only the routes originated within each group and
>    propagated within its borders would get the benefits of
>    cryptographic
>    AS path protection.  As BGPsec adoption grows, each group grows in
>    size and eventually they join together to form even larger BGPsec
>    capable groups of contiguous ASes.  The benefit for early adopters
>    starts with AS path security within the contiguous-AS regions
>    spanned
>    by their respective groups.  Over time they would see those
>    contiguous-AS regions grow much larger.
> 
> 

i see no merit in reproducing text from another document.  i could refer
to it, but i prefer to add

7.  Routing Policy

   As BGPsec signed paths can not traverse non-BGPsec topology, partial
   BGPsec deployment forms islands of assured paths.  As islands grow to
   touch each other, they become larger islands.

randy