Re: [Idr] RFC 4684 pedantry - routes with no Route Target

Jeffrey Haas <jhaas@pfrc.org> Wed, 21 May 2014 16:50 UTC

Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50CD81A0183 for <idr@ietfa.amsl.com>; Wed, 21 May 2014 09:50:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.219
X-Spam-Level:
X-Spam-Status: No, score=-2.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 lC9kbvIwhnUM for <idr@ietfa.amsl.com>; Wed, 21 May 2014 09:50:05 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id E01761A0834 for <idr@ietf.org>; Wed, 21 May 2014 09:50:01 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 1B886C26A; Wed, 21 May 2014 12:50:01 -0400 (EDT)
Date: Wed, 21 May 2014 12:50:01 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Robert Raszuk <robert@raszuk.net>
Message-ID: <20140521165001.GK9789@pfrc>
References: <20140521124753.GC5675@pfrc> <8540.1400685704@erosen-lnx> <CA+b+ERnwBqV8zgeSju_KiMEw_mnfOca8ZSiAuzMZt_U=Dd-r+g@mail.gmail.com> <CA+b+ER=Hx7qe_1QAsa_cpX_JEqPOc7bToDGTyFz+-XTP1iju4A@mail.gmail.com> <20140521163742.GG9789@pfrc> <CA+b+ERk7tb7x_z=biX9R8fXLN7YXGja+QW625Z0k6zNceGFkhg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CA+b+ERk7tb7x_z=biX9R8fXLN7YXGja+QW625Z0k6zNceGFkhg@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/rgD70qSZOGpU-S7ulhm6TglFKQY
Cc: idr wg <idr@ietf.org>, "erosen@cisco.com" <erosen@cisco.com>
Subject: Re: [Idr] RFC 4684 pedantry - routes with no Route Target
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 21 May 2014 16:50:06 -0000

On Wed, May 21, 2014 at 06:40:53PM +0200, Robert Raszuk wrote:
> > Default RT-C effectively negates the usefulness of the feature.  I wouldn't
> > recommend this.
>
> It all depends how you implement your filters :)

I'm not clear how this could be the case, even at a protocol abstraction
level.  Since RT-C entries are effectively longest match on RT (although I
know there's a push to change that behavior as part of the IPv6 work), for
any set of RT-Cs including default, any route containing an RT will match
default.  You're thus not constraining much at all. 

Modulo policy limiting the distribution of default in your network, of
course.  But I'm talking about on a single router.

-- Jeff