IETF Logo Mail Archive

Re: [secdir] New Routing Area Security Design Team

"Russ White" <russ@riw.us> Sun, 15 April 2018 18:04 UTC

Return-Path: <russ@riw.us>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B4B6126CC4 for <secdir@ietfa.amsl.com>; Sun, 15 Apr 2018 11:04:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
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 4M1wOgqXHRbx for <secdir@ietfa.amsl.com>; Sun, 15 Apr 2018 11:04:40 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 682101201FA for <secdir@ietf.org>; Sun, 15 Apr 2018 11:04:40 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 8C9BC21AE4; Sun, 15 Apr 2018 14:04:39 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Sun, 15 Apr 2018 14:04:39 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Ea1aBh 2hlNcOd0prNrhUehEOctRJkDmhwmnYX3lyRSg=; b=V8d3DD3t1TW2Mt+dikqbLu DVFkF2TySFKLTUXWzOi9jOw09tCusyJNpCIdY/npjVVJPDZzUeUMlcK5yYc/Cat3 cjepKue3PQCg4GEkVQg7jqIy4F8u9sQC2/Z5QBA29tI9+ynHDTPiFw6L51EYWqIz /NYmwu2hqb+TvXuuadQLvH4Uce61J98PiBSADkXgeK1lw34M6Pa2pOxTJku9HOhs n79tWYFVFLp8X7JcCEAEcg9ALjLNDGAxiBQ02EhRz2UIhZ8Q171VasiX1SjlMOUh pvCxLq1g7VUVktNbLE3qucbAdUSeymmFbbnfTCH3xUwh3gWH0wU+U5NRo37o4u1Q ==
X-ME-Sender: <xms:N5TTWtyJQRCbNFXYNwYxt3JWEabxX3XQpiwHFR60J3AnzN5tKDVRXQ>
Received: from Russ (162-229-180-77.lightspeed.rlghnc.sbcglobal.net [162.229.180.77]) by mail.messagingengine.com (Postfix) with ESMTPA id 0E7AC10256; Sun, 15 Apr 2018 14:04:39 -0400 (EDT)
From: Russ White <russ@riw.us>
To: 'Christian Huitema' <huitema@huitema.net>, 'Jeffrey Haas' <jhaas@pfrc.org>, 'Richard Barnes' <rlb@ipv.sx>
Cc: 'Stewart Bryant' <stewart.bryant@gmail.com>, "'Acee Lindem (acee)'" <acee@cisco.com>, "'BRUNGARD, DEBORAH A'" <db3546@att.com>, secdir@ietf.org
References: <F64C10EAA68C8044B33656FA214632C8882C74A7@MISOUT7MSGUSRDE.ITServices.sbc.com> <CAL02cgS9rZKVtZs4aRWJmaQj-anaSqYj8rn8roDdxP+JhBR++A@mail.gmail.com> <F64B6EFA-1CB3-454B-B827-B5886A723D36@pfrc.org> <d37721c3-8e78-6eb8-c0ae-ba0e57a623c3@huitema.net>
In-Reply-To: <d37721c3-8e78-6eb8-c0ae-ba0e57a623c3@huitema.net>
Date: Sun, 15 Apr 2018 14:04:37 -0400
Message-ID: <026301d3d4e4$380d8b00$a828a100$@riw.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQIXNZBmczwARyMumKcTrqeA3r6qigBoV+JkAj23bD0BpoR9waNY99Kg
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/8whhSYyw9EEuuo6QqhiHgSlXs1o>
Subject: Re: [secdir] New Routing Area Security Design Team
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Apr 2018 18:04:42 -0000

> As Richard said, the headline issue for outsiders like me is BGP hijacking,
> whether as a mean to hijack addresses and inject spam, or as a way to

This is more about documenting how routing folks should build their security considerations sections to reduce the friction between the security area and the routing area. A much more prosaic situation, I know... 😊

If you'd like to chat about the BGP hijack problem, ping me. It's not something I'm interested in trying to "solve" in the context of the IETF any longer, for various reasons. 

😊

Russ

v2.23.0 | Report a Bug | By Email