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

Robert Raszuk <robert@raszuk.net> Wed, 21 May 2014 16:55 UTC

Return-Path: <rraszuk@gmail.com>
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 265441A085D for <idr@ietfa.amsl.com>; Wed, 21 May 2014 09:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 ojd0kG_Ye2uu for <idr@ietfa.amsl.com>; Wed, 21 May 2014 09:55:29 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B48991A048D for <idr@ietf.org>; Wed, 21 May 2014 09:55:17 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id rl12so2288413iec.9 for <idr@ietf.org>; Wed, 21 May 2014 09:55:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=OuezuMxXZejBgKjumZ0uj+lggnR/X1LqDVABQ8iROjM=; b=F/xXUmi628WRg1xn1pEkI2Zud639fSugJ8jTorU8uwoNGtcFjOMep9h+TEKgKtsALO +vM7M3xnla7QfMxt4dJA+Zdx+1NIGL//+iGZWEGtcQLo+TzpZzmEXm0PSxFR++i87gdb 6LxmfXbp5khn73F6HZSWkYsBrpsb2kb1Hr0W7LzcESwY5Rn4jc3OYUNuaVxAIqQCs8M3 fPue0rSihjVHm+g3EBOEl66JZ+2HZvbanwCBRXLidIVPBIDTSz0MYyTb5BnqqamPleCn Nwo7BEOU1uiKgbWt0ClYRD35Tzr39TcMfYhRqtdZNiOpVFTPAv1XBU9CDkh15L7gcAU3 oZoQ==
MIME-Version: 1.0
X-Received: by 10.42.52.199 with SMTP id k7mr49503516icg.4.1400691316430; Wed, 21 May 2014 09:55:16 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.64.242.198 with HTTP; Wed, 21 May 2014 09:55:16 -0700 (PDT)
In-Reply-To: <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> <20140521165001.GK9789@pfrc>
Date: Wed, 21 May 2014 18:55:16 +0200
X-Google-Sender-Auth: FtJNkZ71pjOtkvHZcRuEEJkh5iE
Message-ID: <CA+b+ERmX-mHrdutd1eg30ySAq63Xh1yKmXyYmBTRkuYC6bX2nw@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: Jeffrey Haas <jhaas@pfrc.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/G2kQ72mwkEJdG_TnMiGQmyiuA9E
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:55:30 -0000

I meant that you do not execute the match of the default entry for
routes which contain RT AND RTC send anything more specific then
default RT.

But NULL RT idea is much more elegant and does not require any of the
above twicks.

R.

On Wed, May 21, 2014 at 6:50 PM, Jeffrey Haas <jhaas@pfrc.org> wrote:
> 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