IETF Logo Mail Archive

Re: [Sidrops] RtgDir review: draft-ietf-sidrops-rtr-keying-01

Randy Bush <randy@psg.com> Fri, 14 December 2018 11:57 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 E911B130DCA; Fri, 14 Dec 2018 03:57:06 -0800 (PST)
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 xV8pcl6qrZ7u; Fri, 14 Dec 2018 03:57:05 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 88C7512D7F8; Fri, 14 Dec 2018 03:57:05 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1gXm5V-0003aD-Jk; Fri, 14 Dec 2018 11:57:02 +0000
Date: Fri, 14 Dec 2018 03:57:00 -0800
Message-ID: <m2lg4s8goj.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
Cc: rtg-ads@ietf.org, rtg-dir@ietf.org, draft-ietf-sidrops-rtr-keying.all@ietf.org, sidrops@ietf.org, Dhruv Dhody <dhruv.dhody@huawei.com>
In-Reply-To: <CAB75xn7Hs8FMg6_HPiDM22+g=boYVVKotkeB5+oq3FuRbmNzfw@mail.gmail.com>
References: <CAB75xn7Hs8FMg6_HPiDM22+g=boYVVKotkeB5+oq3FuRbmNzfw@mail.gmail.com>
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/KnByWtMvWDdBgKdQX4WFMVSe6po>
Subject: Re: [Sidrops] RtgDir review: draft-ietf-sidrops-rtr-keying-01
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: Fri, 14 Dec 2018 11:57:07 -0000

i will leave other issues for sean, who is both more expert and more
patient :)

>    Also, did the authors/WG consider making Router-driven as default
>    and operator-driven to be used with utmost care and only when
>    router-driven is not possible?

we do not tell operators how to run their networks.  for examplem many
will choose operator driven because it allows them to quickly swap new
gear for a failed device without backflow into the rpki.

randy

v2.23.0 | Report a Bug | By Email