IETF Logo Mail Archive

Re: [Idr] IETF LC for IDR-ish document <draft-ietf-grow-bgp-reject-05.txt> (Default EBGP Route Propagation Behavior Without Policies) to Proposed Standard

<bruno.decraene@orange.com> Thu, 20 April 2017 09:52 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 3FEB012EC4E for <idr@ietfa.amsl.com>; Thu, 20 Apr 2017 02:52:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, 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 ZIfsySEj3UNO for <idr@ietfa.amsl.com>; Thu, 20 Apr 2017 02:52:54 -0700 (PDT)
Received: from relais-inet.orange.com (mta239.mail.business.static.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19A1712EC45 for <idr@ietf.org>; Thu, 20 Apr 2017 02:52:49 -0700 (PDT)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) by opfedar22.francetelecom.fr (ESMTP service) with ESMTP id EDE3360607; Thu, 20 Apr 2017 11:52:47 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.34]) by opfedar06.francetelecom.fr (ESMTP service) with ESMTP id CEE828007D; Thu, 20 Apr 2017 11:52:47 +0200 (CEST)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM6F.corporate.adroot.infra.ftgroup ([fe80::bd00:88f8:8552:3349%17]) with mapi id 14.03.0319.002; Thu, 20 Apr 2017 11:52:47 +0200
From: bruno.decraene@orange.com
To: Job Snijders <job@ntt.net>
CC: "John G. Scudder" <jgs@juniper.net>, "idr@ietf.org" <idr@ietf.org>, Hares Susan <shares@ndzh.com>
Thread-Topic: [Idr] IETF LC for IDR-ish document <draft-ietf-grow-bgp-reject-05.txt> (Default EBGP Route Propagation Behavior Without Policies) to Proposed Standard
Thread-Index: AQHSublpFx6qnNOc8UaJCUOYEKex/KHOBBnQ
Date: Thu, 20 Apr 2017 09:52:46 +0000
Message-ID: <27506_1492681967_58F884EF_27506_8047_1_53C29892C857584299CBF5D05346208A31CC011B@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <D4E812E8-AA7B-4EA2-A0AC-034AA8922306@juniper.net> <19878_1492639968_58F7E0E0_19878_13298_1_53C29892C857584299CBF5D05346208A31CBE742@OPEXCLILM21.corporate.adroot.infra.ftgroup> <22424_1492672809_58F86129_22424_6810_15_53C29892C857584299CBF5D05346208A31CBF5DB@OPEXCLILM21.corporate.adroot.infra.ftgroup> <20170420091610.e67lqxdkdmixvaci@hanna.meerval.net> <27497_1492680634_58F87FBA_27497_546_3_53C29892C857584299CBF5D05346208A31CBFDCE@OPEXCLILM21.corporate.adroot.infra.ftgroup> <20170420093513.zmpv7lunfkgoqtsa@hanna.meerval.net>
In-Reply-To: <20170420093513.zmpv7lunfkgoqtsa@hanna.meerval.net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.5]
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/7GBHKTbZBvJ2edJegktPDlBxmtM>
Subject: Re: [Idr] IETF LC for IDR-ish document <draft-ietf-grow-bgp-reject-05.txt> (Default EBGP Route Propagation Behavior Without Policies) to Proposed Standard
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 20 Apr 2017 09:52:55 -0000

> From: Job Snijders [mailto:job@ntt.net]  > Sent: Thursday, April 20, 2017 11:35 AM
> 
 > On Thu, Apr 20, 2017 at 09:30:34AM +0000, bruno.decraene@orange.com wrote:
 > > > From: Job Snijders [mailto:job@ntt.net]  > Sent: Thursday, April 20, 2017 11:16 AM
 > > >
 > >  > On Thu, Apr 20, 2017 at 07:20:08AM +0000, bruno.decraene@orange.com wrote:
 > >  > > 5) Isn't this problem statement/proposed solution a sub-part of the
 > >  > > route leak issue?  IOW, wouldn't it be better addressed by/in
 > >  > > draft-ymbk-idr-bgp-open-policy or draft-ietf-idr-route-leak-detection-mitigation ?
 > >  >
 > >  > Why do you think so?
 > >
 > > Route leak is mentioned in the introduction (read justification) of
 > > this document.
 > 
 > A mention of the phrase "route leak" does not constitute as to why
 > draft-ymbk-idr-bgp-open-policy or
 > draft-ietf-idr-route-leak-detection-mitigation are better at addressing
 > the problem of insecure defaults. Perhaps the drafts complement each
 > other?

Eventually.
I'm asking for this discussion to happen.

Kind regards,
--Bruno

 
 > Kind regards,
 > 
 > Job

_________________________________________________________________________________________________________________________

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.

v2.23.0 | Report a Bug | By Email