IETF Logo Mail Archive

Re: [Sidrops] I-D Action: draft-ietf-sidrops-signed-tal-05.txt

Randy Bush <randy@psg.com> Fri, 06 March 2020 18:42 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 2105F3A0366 for <sidrops@ietfa.amsl.com>; Fri, 6 Mar 2020 10:42:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 NzsBRWKUoMUt for <sidrops@ietfa.amsl.com>; Fri, 6 Mar 2020 10:41:57 -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 38AC93A03EC for <sidrops@ietf.org>; Fri, 6 Mar 2020 10:41:57 -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 1jAHv1-0002Xt-Af; Fri, 06 Mar 2020 18:41:55 +0000
Date: Fri, 06 Mar 2020 10:41:54 -0800
Message-ID: <m2lfodjpfx.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Robert Kisteleki <robert@ripe.net>
Cc: SIDR Operations WG <sidrops@ietf.org>
In-Reply-To: <c0774788-c572-7dd1-8b15-41bee5af16c6@ripe.net>
References: <157914534015.22379.11024327123542212494@ietfa.amsl.com> <CAL9jLabyFSP0C1Rq3FY6JkJVbPbm9yG9JuAfMQeZZtEeSb0Dfg@mail.gmail.com> <CAKr6gn11jN5Jb+uTeQerSktE5mE_DH+rSiBeYc90dpJqsAXGig@mail.gmail.com> <920CAE43-E94A-45A1-AD2C-86095F396E96@nlnetlabs.nl> <c0774788-c572-7dd1-8b15-41bee5af16c6@ripe.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/gG8VLCTI1eKaNJCJfYZTVG7ihJ4>
Subject: Re: [Sidrops] I-D Action: draft-ietf-sidrops-signed-tal-05.txt
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, 06 Mar 2020 18:42:02 -0000

automatic modification of trusted credentials is scary.  but assuming
the folk who understand the bgp and server configurations have not moved
to marrakesh is naïve.

as to pre-notification of an upcoming automatic change; i suspect very
few who are not in this 'room' actually monitor rpki caches in any way.
this will not improve.

will such dilemmas drive us toward centralised cache services at google,
yandex, ...?  and then we will have serious transport security issues.

i wanna go back to 1996.

randy

v2.28.0 | Report a Bug | By Email | System Status