IETF Logo Mail Archive

Re: [Idr] 2 week WG LC on changes to draft-ietf-idr-flowspec-redirect-rt-bis-04.txt (4/20 to 5/4/2015) - extended to 5/18/2015

Jeffrey Haas <jhaas@pfrc.org> Wed, 06 May 2015 14:06 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 ADF851AC408 for <idr@ietfa.amsl.com>; Wed, 6 May 2015 07:06:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.578
X-Spam-Level:
X-Spam-Status: No, score=-1.578 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 LrvQUvlJB3W0 for <idr@ietfa.amsl.com>; Wed, 6 May 2015 07:06:25 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id C6CCA1AC3E5 for <idr@ietf.org>; Wed, 6 May 2015 07:06:04 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 60FD01E302; Wed, 6 May 2015 14:06:11 +0000 (UTC)
Date: Wed, 06 May 2015 10:06:11 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Shishio Tsuchiya <shtsuchi@cisco.com>
Message-ID: <20150506140611.GA1007@pfrc.org>
References: <009101d08799$91662180$b4326480$@ndzh.com> <5549E242.80101@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5549E242.80101@cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/HfyznVN4Dtw2M1vDf1QJnBMhHj4>
Cc: jhaas@juniper.net, idr@ietf.org, shares@ndzh.com
Subject: Re: [Idr] 2 week WG LC on changes to draft-ietf-idr-flowspec-redirect-rt-bis-04.txt (4/20 to 5/4/2015) - extended to 5/18/2015
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, 06 May 2015 14:06:26 -0000

Shishio,

On Wed, May 06, 2015 at 06:43:30PM +0900, Shishio Tsuchiya wrote:
> I support this draft, and  type 0x8008(redirect AS-2byte) and 0x8208(redirect AS-4byte).
> 
> But I can't support type 0x8108 (redirect IPv4) to reduce confusion.
> I think the type should be included in "BGP Flow-Spec Redirect to IP Action".
> https://tools.ietf.org/html/draft-ietf-idr-flowspec-redirect-ip-02

Unlike the redirect-to-ip feature, this is a long deployed feature to
redirect routes to VRFs containing the mentioned route-target.  IPv4 is a
valid global administrator field in route-targets.

If your implementation is unable to support such route-targets, it's fine to
not implement it.  However, this is not redirecting based on IP nexthop or
tunnel.

-- Jeff

v2.23.0 | Report a Bug | By Email