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

Jeffrey Haas <jhaas@pfrc.org> Wed, 21 May 2014 16:46 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 605AE1A06B3 for <idr@ietfa.amsl.com>; Wed, 21 May 2014 09:46:35 -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 OZjnIaKZbSnn for <idr@ietfa.amsl.com>; Wed, 21 May 2014 09:46:30 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id BB12B1A06D3 for <idr@ietf.org>; Wed, 21 May 2014 09:46:30 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id E850BC277; Wed, 21 May 2014 12:46:29 -0400 (EDT)
Date: Wed, 21 May 2014 12:46:29 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Robert Raszuk <robert@raszuk.net>
Message-ID: <20140521164629.GJ9789@pfrc>
References: <20140521124753.GC5675@pfrc> <8540.1400685704@erosen-lnx> <CA+b+ERnwBqV8zgeSju_KiMEw_mnfOca8ZSiAuzMZt_U=Dd-r+g@mail.gmail.com> <20140521163621.GF9789@pfrc> <CA+b+ER=JoyPF9wFnFPUOA+4edJNshEjmv2OJY8tcM7KCaNQwSw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CA+b+ER=JoyPF9wFnFPUOA+4edJNshEjmv2OJY8tcM7KCaNQwSw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/BceXXFgQbDddHdjhfnAA8vf3yqM
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:46:35 -0000

On Wed, May 21, 2014 at 06:38:49PM +0200, Robert Raszuk wrote:
> > While a complicating factor certainly, we'd still end up sending along those
> > routes after either end-of-rib for RT-C or the timeout.  (Presuming the
> > implementation follows the SHOULD.)
> 
> After timeout yes, but not after valid set of RTC RT NLRIs followed by
> EOR. .. I would not expect to see those in the latter case.

I believe that's the point of contention.  Should we be applying filters
when there's nothing to match on?

To echo a point Yakov raised in a side chat, what this would mean
protocol-wise would be a NULL RT-C entry.  This is distinct from a default
which is a "match all".

-- Jeff