Re: [Idr] 2 Week WG Adoption call for draft-ymbk-idr-rs-bfd-00 (3/2/2015 to 3/16/2015)

Randy Bush <randy@psg.com> Mon, 16 March 2015 10:59 UTC

Return-Path: <randy@psg.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 E21581A8701 for <idr@ietfa.amsl.com>; Mon, 16 Mar 2015 03:59:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 Hi_IhHRKPH15 for <idr@ietfa.amsl.com>; Mon, 16 Mar 2015 03:59:56 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [198.180.150.18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E50AA1A86F7 for <idr@ietf.org>; Mon, 16 Mar 2015 03:59:55 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1YXSkS-0006iD-7y; Mon, 16 Mar 2015 10:59:52 +0000
Date: Mon, 16 Mar 2015 11:59:51 +0100
Message-ID: <m2a8zdmcm0.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: David Freedman <david.freedman@uk.clara.net>
In-Reply-To: <E2B120470A420C49A1CB4F6D01C013F8C0BF8EDA@SRVGREXMB06.claranet.local>
References: <7BDA4F61-AF6C-4B56-AFC8-D5CC2B9E7A96@cisco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/qXtj5JASa-iMgALsYifwHkV3oWc>
Cc: idr wg <idr@ietf.org>
Subject: Re: [Idr] 2 Week WG Adoption call for draft-ymbk-idr-rs-bfd-00 (3/2/2015 to 3/16/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: Mon, 16 Mar 2015 10:59:57 -0000

hi david,

clue bat, please.  how does your scheme tell the rs to give me next best
paths instead of those over the failing link?

how likely are we to get the bfd hacks from C, J, A, B, ...?  in our
draft, we are trying to minimize dependence on vendor hacks for a
reason.  their frelling bfds are not even fully compatible today.

but i definitely appreciate this discussion as opposed to reading the
completely engineering-free discussions on the ietf list etc.  and i
look forward to discussing this with you in dallas.

randy