Re: [Sidrops] New Version Notification for draft-sriram-sidrops-drop-invalid-policy-00.txt

Jeffrey Haas <jhaas@pfrc.org> Thu, 15 March 2018 23:36 UTC

Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D33BB127599; Thu, 15 Mar 2018 16:36:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 XWy7-VTwrj9x; Thu, 15 Mar 2018 16:36:12 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 00D83124239; Thu, 15 Mar 2018 16:36:11 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id A69801E3FF; Thu, 15 Mar 2018 19:36:12 -0400 (EDT)
Date: Thu, 15 Mar 2018 19:36:12 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>
Cc: "sidrops@ietf.org" <sidrops@ietf.org>, "sidrops-chairs@ietf.org" <sidrops-chairs@ietf.org>
Message-ID: <20180315233612.GE6209@pfrc.org>
References: <152029076512.12908.14537578849320525718.idtracker@ietfa.amsl.com> <BYAPR09MB2773819AB3961189CDA9B4D784D90@BYAPR09MB2773.namprd09.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <BYAPR09MB2773819AB3961189CDA9B4D784D90@BYAPR09MB2773.namprd09.prod.outlook.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/FMF_ebx6DXVmNijApPaOae4J-PE>
Subject: Re: [Sidrops] New Version Notification for draft-sriram-sidrops-drop-invalid-policy-00.txt
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2018 23:36:14 -0000

Sriram,


On Tue, Mar 06, 2018 at 04:34:17PM +0000, Sriram, Kotikalapudi (Fed) wrote:
> We have requested the chairs for time on the SIDROPS meeting agenda to discuss this work:
>  
> https://tools.ietf.org/html/draft-sriram-sidrops-drop-invalid-policy-00 
> 
> The authors would appreciate comments/discussion on the list as well.

I have a concern with one of the terms of your procedure.  From section 3:

:    4.  If selected route is Valid/NotFound, then add the route to Loc-
:        RIB; Else, if Invalid, then add the route to Loc-RIB only if
:        there is no existing route in the Loc-RIB for a subsuming Less
:        Specific prefix.

This sort of thing tries to get periodically added to BGP specs.  In
general, BGP tries *VERY* hard to avoid any sort of cascading dependency
between routes due to the ripple effects.  Enough so that the following is
enshrined in the core spec:

RFC 4271, Section 9.1:

:    The function that calculates the degree of preference for a given
:    route SHALL NOT use any of the following as its inputs: the existence
:    of other routes, the non-existence of other routes, or the path
:    attributes of other routes.

I appreciate what you're trying to do here.  However, my strong advice is
DON'T.

-- Jeff