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

Jeffrey Haas <jhaas@pfrc.org> Wed, 21 May 2014 16:36 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 87A411A0481 for <idr@ietfa.amsl.com>; Wed, 21 May 2014 09:36:23 -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 NcJCstBFTxEN for <idr@ietfa.amsl.com>; Wed, 21 May 2014 09:36:22 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 45BE91A03DD for <idr@ietf.org>; Wed, 21 May 2014 09:36:22 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 66389C26A; Wed, 21 May 2014 12:36:21 -0400 (EDT)
Date: Wed, 21 May 2014 12:36:21 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Robert Raszuk <robert@raszuk.net>
Message-ID: <20140521163621.GF9789@pfrc>
References: <20140521124753.GC5675@pfrc> <8540.1400685704@erosen-lnx> <CA+b+ERnwBqV8zgeSju_KiMEw_mnfOca8ZSiAuzMZt_U=Dd-r+g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CA+b+ERnwBqV8zgeSju_KiMEw_mnfOca8ZSiAuzMZt_U=Dd-r+g@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/jVOKksp5Txwil6ertW_8IAisL0U
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:36:23 -0000

Robert,

On Wed, May 21, 2014 at 06:20:58PM +0200, Robert Raszuk wrote:
> Remember that RFC 4684 enforces for any SAFI it is enabled under no
> route exchange happens at all till intersecting RTs are received over
> RTC SAFI.
> 
> That means that the spec is 180 degrees opposite to your above claim
> that routes with no RTs should be always exchanged.

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.)

So, while it causes potential delay to the subset of the routes carrying no
RT, presumably they're in the same family because some of the routes will
have an RT and want to benefit from the feature.

-- Jeff