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

<bruno.decraene@orange.com> Fri, 29 June 2018 07:31 UTC

Return-Path: <bruno.decraene@orange.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 9557A130E09 for <idr@ietfa.amsl.com>; Fri, 29 Jun 2018 00:31:41 -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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 PMJ6OqQcvn6k for <idr@ietfa.amsl.com>; Fri, 29 Jun 2018 00:31:40 -0700 (PDT)
Received: from orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC644127AC2 for <idr@ietf.org>; Fri, 29 Jun 2018 00:31:39 -0700 (PDT)
Received: from opfedar05.francetelecom.fr (unknown [xx.xx.xx.7]) by opfedar27.francetelecom.fr (ESMTP service) with ESMTP id 41H7cn73xXz2xS3; Fri, 29 Jun 2018 09:31:37 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.43]) by opfedar05.francetelecom.fr (ESMTP service) with ESMTP id DAADC6006E; Fri, 29 Jun 2018 09:31:37 +0200 (CEST)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM5F.corporate.adroot.infra.ftgroup ([fe80::e172:f13e:8be6:71cc%18]) with mapi id 14.03.0399.000; Fri, 29 Jun 2018 09:31:37 +0200
From: bruno.decraene@orange.com
To: Randy Bush <randy@psg.com>
CC: Interminable Discussion Room <idr@ietf.org>
Thread-Topic: [Idr] I-D Action: draft-ietf-idr-next-hop-capability-03.txt
Thread-Index: AQHUDznwV9AUMg5HA0yhNHH3IN7qaKR20qkg
Date: Fri, 29 Jun 2018 07:31:37 +0000
Message-ID: <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>
In-Reply-To: <m2r2kqo4rs.wl-randy@psg.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/DeLDKkzvuGehSCWZEf9zpKaInHk>
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 07:31:42 -0000

Hi Randy,

> From: Randy Bush [mailto:randy@psg.com]
> 
 > hey bruno,
 > 
 > an example
 > 
 > the new next hop may not be in a shared trust domain

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.
 
 > at an exchange point, A tells B to to use C as the next hop, thereby
 > avoiding carrying B's outbound traffic

Another point related to transitive trust.
If I trust A, and A tells me he can provide me a car for next WE, I trust him. Regardless of whether he owns the car, or rent/borrow it from some else (who I may not trust/know).
That's also applicable to a company which may outsource some part of the job, although with companies trust tend to be replaced by legal contract and penalty.
But it's also fine to have partial trust, including refusing any transitivity.

Note that your example is not specific to this attribute/information.  You may not trust the route itself i.e. the ability of C to adequately forward your traffic.

--Bruno
 
 > randy

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.