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

Mikael Abrahamsson <swmike@swm.pp.se> Fri, 21 April 2017 09:08 UTC

Return-Path: <swmike@swm.pp.se>
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 B1F28129426 for <idr@ietfa.amsl.com>; Fri, 21 Apr 2017 02:08:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 WulF3Q6jxyL8 for <idr@ietfa.amsl.com>; Fri, 21 Apr 2017 02:08:41 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FEE71292F5 for <idr@ietf.org>; Fri, 21 Apr 2017 02:08:41 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id C9336B0; Fri, 21 Apr 2017 11:08:38 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1492765718; bh=/PIOqjuuzBezlBrd3zqmibq5N7k3ZtAJ/oHL2cDhx9Q=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=plaI4HEo7gvb/BivHbTzpf6nXilTY7qIYofeTZ0Jwth2zrgloVN5XRwK6XOaoZj9t yWOtsdkNIWBp6Tkq701ZaznoLz36TqqTuvRCK4knHjmuG8NZs64sME2lgWZOXn9NFS E+nRjT2T/zsGwYCnIqykzX/7genjUOntz2xAZt2Q=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id B152BAF; Fri, 21 Apr 2017 11:08:38 +0200 (CEST)
Date: Fri, 21 Apr 2017 11:08:38 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Nick Hilliard <nick@foobar.org>
cc: Robert Raszuk <robert@raszuk.net>, idr wg <idr@ietf.org>
In-Reply-To: <58F9C95E.2050201@foobar.org>
Message-ID: <alpine.DEB.2.02.1704211103320.5591@uplift.swm.pp.se>
References: <CA+b+ERn5o-i-6shdzj_afa8Z1yQO3Ep6HmB=Fv4StSW_ge95Ew@mail.gmail.com> <CA+b+ERkBeBoz0Le4wgqZK1X76=_HKOEUYTWYBd_xnjYoaJgrsw@mail.gmail.com> <CA+b+ERnBL9Q3ep1JrC9HQp3B3AYmiQ8ctTssK1g4L_ueTTRaMQ@mail.gmail.com> <CA+b+ER=cZiBfWj4=+uKeqsWwypGFz3p+Tvx8Q2dD3hFFXSC4=w@mail.gmail.com> <CA+b+ER=f-S118JtY--n-B0P+CB0yvy_rw3JaJpWw02n7prQ=Ww@mail.gmail.com> <20170314204212.GD12864@pfrc.org> <815723FC-B143-4410-B0FF-D9FB4F827862@cisco.com> <20170314213607.GH12864@pfrc.org> <579D00D9-D80F-4625-BF16-0D5112C2FA98@cisco.com> <CA+b+ERkXLg3O0hEAtokUDn4ndjixyuT4dpv9LfLVPmfsb1akug@mail.gmail.com> <20170418203108.GB9688@pfrc.org> <CA+b+ERnxjsjVbSowzBgBhrCtY5ehhn+SM+uvF3G071No-3gk6Q@mail.gmail.com> <58F89C07.8080900@foobar.org> <CA+b+ERnZvPM0jyuMEx1cGTHS70Rw+h+Ze0KoM7cbCkvVMAKMTw@mail.gmail.com> <58F93B30.2010909@foobar.org> <CA+b+ER=QLQy8hTrw4Dvs7Au5uhQd=wUxdFWQqQx06Kc61n5BLg@mail.gmail.com> <58F9C95E.2050201@foobar.org>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/oOwkyauoUO2V1sbTi3XXdY55OfA>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-rs-bfd-02.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 21 Apr 2017 09:08:44 -0000

On Fri, 21 Apr 2017, Nick Hilliard wrote:

> Robert Raszuk wrote:
>> But my point is that we can come up with single solution to both
>> problems which would work in a hardware accelerated way equally well.
>
> Then I suggest you author documents to:
>
> - add a new icmp type to define reachability / mtu detection / etc mechanism

https://tools.ietf.org/html/draft-van-beijnum-multi-mtu-05

I am interested in working in this area, however IDR doesn't seem to be 
the ideal place to do that. I'd prefer to do it in INT-AREA (where I 
presented I van Beijnums work a few IETFs back.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se