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

Jeffrey Haas <jhaas@pfrc.org> Wed, 21 May 2014 15:52 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 5A0571A0445 for <idr@ietfa.amsl.com>; Wed, 21 May 2014 08:52:31 -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 APwg-gzJ--_b for <idr@ietfa.amsl.com>; Wed, 21 May 2014 08:52:26 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 5006F1A0738 for <idr@ietf.org>; Wed, 21 May 2014 08:52:26 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 11478C26A; Wed, 21 May 2014 11:52:25 -0400 (EDT)
Date: Wed, 21 May 2014 11:52:25 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Eric Rosen <erosen@cisco.com>
Message-ID: <20140521155225.GD9789@pfrc>
References: <20140521124753.GC5675@pfrc> <8540.1400685704@erosen-lnx>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <8540.1400685704@erosen-lnx>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/nvlfeLEeyuL5L6gzYU2MbgVfQRQ
Cc: idr@ietf.org
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 15:52:31 -0000

On Wed, May 21, 2014 at 11:21:44AM -0400, Eric Rosen wrote:
> Jeff> The broader question I'd put to the working group is whether any NLRI
> Jeff> not  having RTs isn't really a "VPN NLRI" for purposes of RT-C
> Jeff> filtering
> 
> I don't think RFC4684 really intends to restrict its applicability to "VPN
> routes".  It does say in section 1: "This mechanism is applicable to any BGP
> NLRI that controls the distribution of routing information by using Route
> Targets".

(And Jakob also raised the same point.)

It should be noted that we leveraged the same thing for the
draft-ietf-idr-mdcs proposal. :-)

> The problem arises because, on some NLRIs, the use of RTs is
> optional.  What you're suggesting is that RT-C should never filter out
> routes that don't have any RTs.  That does seem right.

I think that's 3 people that are in agreement.  I'd like to leave the
discussion open for a little bit to get additional consensus in the WG.

Chairs, presuming that we do end up with that sort of behavioral consensus
about no RT's, is an errata against RFC 4684 sufficient or would you want to
see something more?

-- Jeff