IETF Logo Mail Archive

Re: [Idr] I-D Action: draft-ietf-idr-next-hop-capability-03.txt

Randy Bush <randy@psg.com> Fri, 29 June 2018 15:11 UTC

Return-Path: <randy@psg.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54479126CC7 for <idr@ietfa.amsl.com>; Fri, 29 Jun 2018 08:11:06 -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 0dv0caa9Kasc for <idr@ietfa.amsl.com>; Fri, 29 Jun 2018 08:11:04 -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 42D5712F1A6 for <idr@ietf.org>; Fri, 29 Jun 2018 08:11:02 -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 1fYv37-0008VO-80; Fri, 29 Jun 2018 15:11:01 +0000
Date: Fri, 29 Jun 2018 08:11:00 -0700
Message-ID: <m24lhlocfv.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: bruno.decraene@orange.com
Cc: Interminable Discussion Room <idr@ietf.org>
In-Reply-To: <6235_1530257497_5B35E059_6235_365_1_53C29892C857584299CBF5D05346208A47AB997A@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <153008684965.15406.536825824891886594@ietfa.amsl.com> <m2o9fvptr9.wl-randy@psg.com> <19553_1530173556_5B349874_19553_6_1_53C29892C857584299CBF5D05346208A47AB766D@OPEXCLILM21.corporate.adroot.infra.ftgroup> <m2h8lmq4rl.wl-randy@psg.com> <32389_1530204755_5B351253_32389_173_1_53C29892C857584299CBF5D05346208A47AB8A0A@OPEXCLILM21.corporate.adroot.infra.ftgroup> <m2r2kqo4rs.wl-randy@psg.com> <6235_1530257497_5B35E059_6235_365_1_53C29892C857584299CBF5D05346208A47AB997A@OPEXCLILM21.corporate.adroot.infra.ftgroup>
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/idr/61P0Mh43TYSvR5WpdRl5eF3gzA8>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-next-hop-capability-03.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2018 15:11:12 -0000

mornin' bruno,

> I generally agree that there are cases where you don't trust the
> source of the information. In such case, you can filter it a priori or
> a posteriori.  That doesn't mean that the ability to share an
> information is bad.

then make clear what the boundaries are and how to ameliorate this
exposure.  the example from ov-signal's sec cons specifically mandates
the defense.

randy

v2.23.0 | Report a Bug | By Email