Re: [Lsvr] [OPSEC] security against what?

Randy Bush <randy@psg.com> Tue, 04 September 2018 15:38 UTC

Return-Path: <randy@psg.com>
X-Original-To: lsvr@ietfa.amsl.com
Delivered-To: lsvr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B39AA130E2F; Tue, 4 Sep 2018 08:38:07 -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 e8pkpct3j5Pc; Tue, 4 Sep 2018 08:38:06 -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 8B82512426A; Tue, 4 Sep 2018 08:38:06 -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 1fxDP1-0002Y0-90; Tue, 04 Sep 2018 15:38:03 +0000
Date: Tue, 04 Sep 2018 08:38:02 -0700
Message-ID: <m2wos1p92d.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
Cc: Erik Kline <ek@google.com>, opsec wg mailing list <opsec@ietf.org>, lsvr@ietf.org, gunter.van_de_velde@nokia.com
In-Reply-To: <CAL9jLaa0VmEQpi45T0wdNV51R5+ib4Lo8NhmO9RJq-6OiO69EA@mail.gmail.com>
References: <m21sbkjba8.wl-randy@psg.com> <AM5PR0701MB172966DC99841C55D5E26CA2E0030@AM5PR0701MB1729.eurprd07.prod.outlook.com> <CAAedzxrX5TWxYtA-uCfA3QyF_N1L3-tmjtqWTNThXvNNi4Uppw@mail.gmail.com> <m2zhwxposb.wl-randy@psg.com> <CAL9jLaa0VmEQpi45T0wdNV51R5+ib4Lo8NhmO9RJq-6OiO69EA@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/lsvr/R-5Wf8NDJGwK9wkcRrQ2_wpqhNE>
Subject: Re: [Lsvr] [OPSEC] security against what?
X-BeenThere: lsvr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Vector Routing <lsvr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsvr>, <mailto:lsvr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsvr/>
List-Post: <mailto:lsvr@ietf.org>
List-Help: <mailto:lsvr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsvr>, <mailto:lsvr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Sep 2018 15:38:08 -0000

> 'datacenter operators' == "hyperscale web wonkers" ?

i asked in lsvr, which is what i guess you woud call hyperscale.  lsvr
also tends toward decentralized,

> or 'datacenter operators' == 'colo provider' ('the planet' not 'equinix' -
> and 'the planet' is now 'someone else' but...)

1x would seem especially inapporpriate here as there is no
centralisation of authority.

>>> Is recommending 802.1x possible/sufficient (given the description in
>>> Randy's strawperson comment)?
>> it's a long way to that radius server

with coffee, i might expand a bit.  during turn up of new links and
devices, it may not be easy to get to a distant 1x authority.

randy