Re: fn-transport/ipfrr drafts

mike shand <mshand@cisco.com> Wed, 06 April 2011 09:23 UTC

Return-Path: <mshand@cisco.com>
X-Original-To: rtgwg@core3.amsl.com
Delivered-To: rtgwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9EFB3A68F9 for <rtgwg@core3.amsl.com>; Wed, 6 Apr 2011 02:23:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.599
X-Spam-Level:
X-Spam-Status: No, score=-9.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8SpU7-w8XC-u for <rtgwg@core3.amsl.com>; Wed, 6 Apr 2011 02:23:32 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 7F2153A68E6 for <rtgwg@ietf.org>; Wed, 6 Apr 2011 02:23:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mshand@cisco.com; l=2557; q=dns/txt; s=iport; t=1302081916; x=1303291516; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=G3ao7pEAa8TQdP+CobZezzuJzMIgZ01QUGkXheGMXhk=; b=RhgRmJAOw+kfS64HtuJ9W0pG5rGh/y8WUv/GwCA8CXe1/6w8DmgqoI0G 49wcWwhdItOal6009YGQ4QQ4dTNyj61yygZEWoJIvyBAhr3Kf8m1sgbNi Z2iIUJH0ExXSJ1/IzHIKTfWjTGGGFluaBbAtwOvky0jJV0jLuEW37+WNl w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AncFAEExnE2Q/khLgWdsb2JhbACYbI0LFAEBFiYlpSucFIVsBI06g2I
X-IronPort-AV: E=Sophos;i="4.63,309,1299456000"; d="scan'208";a="82387043"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 06 Apr 2011 09:25:15 +0000
Received: from [10.61.88.192] (ams3-vpn-dhcp6337.cisco.com [10.61.88.192]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p369PENE017871 for <rtgwg@ietf.org>; Wed, 6 Apr 2011 09:25:14 GMT
Message-ID: <4D9C317A.7090804@cisco.com>
Date: Wed, 06 Apr 2011 10:25:14 +0100
From: mike shand <mshand@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: rtgwg@ietf.org
Subject: Re: fn-transport/ipfrr drafts
References: <8DCD771BDA4A394E9BCBA8932E83929720E74AF21C@ESESSCMS0363.eemea.ericsson.se> <201104052137.p35LbquQ061587@harbor.orleans.occnc.com> <BANLkTimOkFh=Hm=g2KXBm7ysxqqBDsvHVw@mail.gmail.com>
In-Reply-To: <BANLkTimOkFh=Hm=g2KXBm7ysxqqBDsvHVw@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2011 09:23:33 -0000

Alia,

     My quick replies would be

a) possibly, but I'm not sure of the application. Certainly not (b).
b) I don't think so
c) I'd be very concerned about the scaling issues of doing that

     Mike


On 06/04/2011 02:00, Alia Atlas wrote:
> Curtis,
>
> Andras is familiar with the problem IPFRR is trying to solve.
>
> As I understand it, there are 3 separate questions:
>     a) Is a multicast distribution mechanism that can report bad news
> quickly&  survive single failures useful?
>     b) Is this useful for an IGP to speed network convergence?
>     c) If one assumes very rapid ( speed of light)  delays for remote
> failures, what pre-computation and FIB installation could be possible?
>
> I have not heard requirements and rationale sufficient yet.
> Security is also a concern - but the first questions are whether any
> mechanism is  desirable.
>
> Alia
>
> 2011/4/5 Curtis Villamizar<curtis@occnc.com>:
>> In message<8DCD771BDA4A394E9BCBA8932E83929720E74AF21C@ESESSCMS0363.eemea.ericsson.se>
>> András Császár writes:
>>> Dear All,
>>>
>>> Note that fn-transport already is at version 01. Links to the docs:
>>>
>>> http://tools.ietf.org/html/draft-lu-fn-transport-01
>>> http://tools.ietf.org/html/draft-csaszar-ipfrr-fn-00
>>>
>>> We'd really appreciate comments and suggestions.
>>>
>>> András
>>
>> Same comment as on the OSPF mailing list.  This is attacking a
>> non-problem.
>>
>> Flooding time is not a problem on modern implementations, unless the
>> implementation is badly designed or badly coded.
>>
>> IPFRR is intended to eliminate the need for an SPF and route
>> download and the need to contact any other router in any way to get an
>> initial repair done.  That is a different problem.
>>
>> Curtis
>>
>>
>>>> -----Original Message-----
>>>> From: rtgwg-bounces@ietf.org [mailto:rtgwg-bounces@ietf.org]
>>>> On Behalf Of Jeff Tantsura
>>>> Sent: 2011. március 29. 14:58
>>>> To: rtgwg@ietf.org
>>>> Subject: fn-transport/ipfrr drafts
>>>>
>>>> Hi rtgwg,
>>>>
>>>> The authors would like to solicit comments from the workgroup.
>>>>
>>>> draft-lu-fn-transport-00
>>>> draft-csaszar-ipfrr-fn-00
>>>>
>>>> Thank you in advance!
>>>>
>>>> Regards,
>>>> Jeff
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg
>>
>>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>