Re: [Isis-wg] New Version Notification for draft-ginsberg-isis-sbfd-discriminator-00.txt

Jeffrey Haas <jhaas@pfrc.org> Wed, 14 May 2014 15:36 UTC

Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCDEE1A02AC; Wed, 14 May 2014 08:36:56 -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 Gthcfl-1MEyp; Wed, 14 May 2014 08:36:55 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 8694E1A02D5; Wed, 14 May 2014 08:36:48 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id E668EC26A; Wed, 14 May 2014 11:36:41 -0400 (EDT)
Date: Wed, 14 May 2014 11:36:41 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Hannes Gredler <hannes@juniper.net>
Message-ID: <20140514153641.GC13993@pfrc>
References: <20140508144606.23448.98448.idtracker@ietfa.amsl.com> <F3ADE4747C9E124B89F0ED2180CC814F23D873B9@xmb-aln-x02.cisco.com> <9DDF3832-A276-40F1-AF24-2CEAB31E63DC@juniper.net> <F3ADE4747C9E124B89F0ED2180CC814F23DB5518@xmb-aln-x02.cisco.com> <922372D3-6CE8-461E-9BD4-94C2B050C37D@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <922372D3-6CE8-461E-9BD4-94C2B050C37D@juniper.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/isis-wg/_q39AFSrQUoYzDGf4137H40s0zc
Cc: "Les Ginsberg \(ginsberg\)" <ginsberg@cisco.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: Re: [Isis-wg] New Version Notification for draft-ginsberg-isis-sbfd-discriminator-00.txt
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 May 2014 15:36:56 -0000

On Wed, May 14, 2014 at 05:26:52PM +0200, Hannes Gredler wrote:
> On May 14, 2014, at 5:22 PM, Les Ginsberg (ginsberg) wrote:
> > Thanx for the comments.
> > I don't see how your proposal solves the problem you are attempting to address. The sender of the S-BFD packet has no control over what interface is used to receive the packet on the target node. Associating it with a prefix will not help in that regard. 
> 
> well it would help first endpoint discovery and pinning down BFD traffic to particular line card.

Indeed.  In the SPRING related case (or even some MPLS scenarios), traffic
may be heavily steered to a given interface.  This interface may not even be
to a router, but may be an ingress for a SFC device and that ingress is
critical for the execution of the chain.

-- Jeff