IETF Logo Mail Archive

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

David Freedman <david.freedman@uk.clara.net> Mon, 16 March 2015 11:08 UTC

Return-Path: <david.freedman@uk.clara.net>
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 C94E41A00BE for <idr@ietfa.amsl.com>; Mon, 16 Mar 2015 04:08:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_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 8NwhW-FAE81W for <idr@ietfa.amsl.com>; Mon, 16 Mar 2015 04:08:43 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.117]) by ietfa.amsl.com (Postfix) with ESMTP id 8BB681A007C for <idr@ietf.org>; Mon, 16 Mar 2015 04:08:42 -0700 (PDT)
Received: from [193.109.255.99] by server-13.bemta-14.messagelabs.com id C6/8E-13815-9B9B6055; Mon, 16 Mar 2015 11:08:41 +0000
X-Env-Sender: david.freedman@uk.clara.net
X-Msg-Ref: server-14.tower-48.messagelabs.com!1426504119!9283843!1
X-Originating-IP: [80.168.41.245]
X-StarScan-Received:
X-StarScan-Version: 6.13.4; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17742 invoked from network); 16 Mar 2015 11:08:39 -0000
Received: from staff03.mail.eu.clara.net (HELO staff03.mail.eu.clara.net) (80.168.41.245) by server-14.tower-48.messagelabs.com with SMTP; 16 Mar 2015 11:08:39 -0000
Received: from [80.168.41.252] (port=54742 helo=SRVGREXCAS05.claranet.local) by staff03.mail.eu.clara.net (staff03.mail.eu.clara.net [80.168.41.245]:25) with esmtps (TLS-1.0:RSA_AES_128_CBC_SHA1:16) id 1YXSsx-0003RZ-AL (return-path <david.freedman@uk.clara.net>); Mon, 16 Mar 2015 11:08:39 +0000
Received: from SRVGREXMB06.claranet.local ([fe80::70d4:3322:86e0:c10c]) by SRVGREXCAS05.claranet.local ([fe80::3915:cdff:95ac:dcdb%11]) with mapi id 14.03.0224.002; Mon, 16 Mar 2015 11:08:38 +0000
From: David Freedman <david.freedman@uk.clara.net>
To: Randy Bush <randy@psg.com>
Thread-Topic: [Idr] 2 Week WG Adoption call for draft-ymbk-idr-rs-bfd-00 (3/2/2015 to 3/16/2015)
Thread-Index: AQHQX2KQloKaLrJPrEOg21NQaaXf050ez1mAgAAC6kKAAB+egIAAAlmA
Date: Mon, 16 Mar 2015 11:08:38 +0000
Message-ID: <D12C68E3.B2D5B%david.freedman@uk.clara.net>
References: <7BDA4F61-AF6C-4B56-AFC8-D5CC2B9E7A96@cisco.com> <m2a8zdmcm0.wl%randy@psg.com>
In-Reply-To: <m2a8zdmcm0.wl%randy@psg.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.8.150116
x-originating-ip: [172.26.6.254]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <71BEB750BEFA5D4BBE86ADB07753386E@claranet.local>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Original-Recipient: randy@psg.com
X-Original-Sender: david.freedman@uk.clara.net
X-Original-Recipient: idr@ietf.org
X-Clara-Helo: SRVGREXCAS05.claranet.local
X-BorderScout: cm=0.00 ca=0.00 time=4406 size=2664
X-BorderScout-CM-Score: 0
X-BorderScout-CA-Score: 0
X-ClamAV: clean
X-Cloudmark: 0.00
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/E63zkZ4BlGVwqkvVHd619ni1Ua4>
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 11:08:46 -0000


On 16/03/2015 10:59, "Randy Bush" <randy@psg.com> wrote:

>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?


It doesn't , but then, if the exchange is having issues, I won't be
sending 
any further traffic over it until it is repaired, so I would stop trusting
the RS at this point.

>
>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.

Being that we are already in 'hack' territory
(http://seclists.org/nanog/2015/Feb/259)
This one IMHO requires the least protocol changes (we just register a new
diagnostic flag
from an existing IANA FCFS registry), no changes needed to BGP or the RS
implementation.

Saying this, it is useful for the RS operator to be aware that there is a
problem
(but then again, being that in almost all cases they run the exchange
itself
and , you would hope, have monitoring, I guess they would already be so)

>
>but i definitely appreciate this discussion as opposed to reading the
>completely engineering-free discussions on the ietf list etc.

As much as I would love to be there, I can't, but I believe Jerome is
sending a Rep.

Dave.

v2.23.0 | Report a Bug | By Email