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

Robert Raszuk <robert@raszuk.net> Wed, 21 May 2014 16:46 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 B52961A0679 for <idr@ietfa.amsl.com>; Wed, 21 May 2014 09:46:05 -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 zuhLpugao6bF for <idr@ietfa.amsl.com>; Wed, 21 May 2014 09:46:05 -0700 (PDT)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D69341A0183 for <idr@ietf.org>; Wed, 21 May 2014 09:46:04 -0700 (PDT)
Received: by mail-ig0-f172.google.com with SMTP id uy17so6439431igb.17 for <idr@ietf.org>; Wed, 21 May 2014 09:46:03 -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=OUidLFsOHDpwfPlfBSr8At6lKnKFopYw1JeomjOdTXw=; b=v2O9L/osrm7xdckzFezI+WTqY8fWTrNlKr3gzBI0GK3Ux4VmriqeiGt0O7GouzTgwG OlHqJDijxYPOtlokn9guHVkEgEzWr10arLoEDyjo+LyMQ6ecLbsgJzn2iU/r/VteaEr7 F2Lw70tv/NtvZSLEqlU8RAEfmOCU2EV4BB4lQ3LKFTWOsFR+VfHNcWwtQDFM2aHrkpz9 9JlWKnK4Pv4U0DSdP4Tb+qFWiiXaXDZeA35I3LBU3n3HZ0DHv8kTqbEF34FFRiQtx2p5 697jWifzIzJiK0hV5CeysyJwlgIBQt/vFG/magswHVaz4Wnq48717XuS3z+9Dx6JFrn0 ZBaQ==
MIME-Version: 1.0
X-Received: by 10.50.13.67 with SMTP id f3mr15344561igc.9.1400690763723; Wed, 21 May 2014 09:46:03 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.64.242.198 with HTTP; Wed, 21 May 2014 09:46:03 -0700 (PDT)
In-Reply-To: <CA+b+ER=JoyPF9wFnFPUOA+4edJNshEjmv2OJY8tcM7KCaNQwSw@mail.gmail.com>
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>
Date: Wed, 21 May 2014 18:46:03 +0200
X-Google-Sender-Auth: lDbiimLWqr4pj_0BpgVAxLPATyM
Message-ID: <CA+b+ER=fuEMz-axYMma7Bw1cq-ddRS-23kM4uSbQwJNzLiDY7w@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/eoiJTzpfC5miqX--eQ6vESpC3QI
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:05 -0000

Assume I do have a valid SR application to filter tiny subset of
Internet table. For this I can mark such tiny subset of routes with
RTs, enable RTC and activate RT filtering on IPv4 session.

Sending full table there where I need only few routes would kill the
optimization completely.

Btw .. how do you handle the same problem with ORF ?

r.

On Wed, May 21, 2014 at 6:38 PM, Robert Raszuk <robert@raszuk.net> 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.
>
> r.
>
>> 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