IETF Logo Mail Archive

Re: [Idr] I-D Action: draft-ietf-idr-rs-bfd-02.txt

Randy Bush <randy@psg.com> Tue, 14 March 2017 05:33 UTC

Return-Path: <randy@psg.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A2FE1293EC for <idr@ietfa.amsl.com>; Mon, 13 Mar 2017 22:33:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 Z7kXzrMvsY0x for <idr@ietfa.amsl.com>; Mon, 13 Mar 2017 22:33:01 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EA78126BF7 for <idr@ietf.org>; Mon, 13 Mar 2017 22:33:01 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cnf4t-0000gR-EQ; Tue, 14 Mar 2017 05:32:59 +0000
Date: Tue, 14 Mar 2017 14:32:57 +0900
Message-ID: <m2o9x4whh2.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Robert Raszuk <robert@raszuk.net>
In-Reply-To: <CA+b+ER=MaOqOr0A9VZ3TfgbSWgjk3eGwLKmnfr=byvOs11Ppfg@mail.gmail.com>
References: <148924277112.2960.17904473852401253352@ietfa.amsl.com> <m2k27tzs5k.wl-randy@psg.com> <CA+b+ERmmqtUkJMtfOE9ABFHN0gNdztjOGELmirNgWRnDENrjaA@mail.gmail.com> <m2zigpxu7o.wl-randy@psg.com> <CA+b+ER=MaOqOr0A9VZ3TfgbSWgjk3eGwLKmnfr=byvOs11Ppfg@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ofutwt0Cqkf0KbZvxvs87Qo7DnM>
Cc: Interminable Discussion Room <idr@ietf.org>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-rs-bfd-02.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 14 Mar 2017 05:33:02 -0000

> ​That not correct if you do it right. If you can reach A via NH1 and NH2
> and RS propagates both of those NHs to clients - it is up to clients to
> validate those NHs and choose one which they prefer for forwarding at a
> given point of time.

why do folk use RS?  to offload the bgp decision process.

randy

v2.23.0 | Report a Bug | By Email