Re: [OSPF] draft-kini-ospf-fast-notification-01

John E Drake <jdrake@juniper.net> Tue, 05 April 2011 16:15 UTC

Return-Path: <jdrake@juniper.net>
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 131133A694C for <ospf@core3.amsl.com>; Tue, 5 Apr 2011 09:15:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.213
X-Spam-Level:
X-Spam-Status: No, score=-6.213 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 COPohmGPnST2 for <ospf@core3.amsl.com>; Tue, 5 Apr 2011 09:15:30 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by core3.amsl.com (Postfix) with ESMTP id 137013A67B0 for <ospf@ietf.org>; Tue, 5 Apr 2011 09:15:30 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKTZtAgIwBrlXLshHFDVYcyl+nFpDQZeyk@postini.com; Tue, 05 Apr 2011 09:17:13 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Tue, 5 Apr 2011 09:12:38 -0700
From: John E Drake <jdrake@juniper.net>
To: =?iso-8859-1?Q?Andr=E1s_Cs=E1sz=E1r?= <Andras.Csaszar@ericsson.com>, "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>, "curtis@occnc.com" <curtis@occnc.com>
Date: Tue, 5 Apr 2011 09:14:18 -0700
Thread-Topic: [OSPF] draft-kini-ospf-fast-notification-01
Thread-Index: AcvzOMWKeSZDVLdCRrGNCXiliv07mAADWi0gABK94eAABsDbUA==
Message-ID: <5E893DB832F57341992548CDBB33316399F2BD0718@EMBX01-HQ.jnpr.net>
References: Your message of "Tue, 05 Apr 2011 05:29:16 +0530." <7C362EEF9C7896468B36C9B79200D8350CFCF67253@INBANSXCHMBSA1.in.alcatel-lucent.com> <201104050225.p352PaCS029256@harbor.orleans.occnc.com> <7C362EEF9C7896468B36C9B79200D8350CFCF67274@INBANSXCHMBSA1.in.alcatel-lucent.com> <8DCD771BDA4A394E9BCBA8932E83929720E74AF217@ESESSCMS0363.eemea.ericsson.se>
In-Reply-To: <8DCD771BDA4A394E9BCBA8932E83929720E74AF217@ESESSCMS0363.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ospf@ietf.org" <ospf@ietf.org>
Subject: Re: [OSPF] draft-kini-ospf-fast-notification-01
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2011 16:15:31 -0000

Also, what you describe in your second and third paragraphs is an implementation choice - no protocol changes are required.

Sent from my iPhone


> -----Original Message-----
> From: ospf-bounces@ietf.org [mailto:ospf-bounces@ietf.org] On Behalf Of
> András Császár
> Sent: Tuesday, April 05, 2011 6:09 AM
> To: Bhatia, Manav (Manav); curtis@occnc.com
> Cc: ospf@ietf.org
> Subject: Re: [OSPF] draft-kini-ospf-fast-notification-01
> 
> > I believe the idea is quite simple -
> > Flooding a changed LSA in HW (data plane) is faster than
> > doing it in SW (not matter how optimized the latter is) or
> > your control plane.
> 
> That's the main purpose, yes.
> 
> You could combine this with something else: OSPF could pre-calc/pre-
> download potential new LSAs to the dataplane anticipating local
> failures.
> 
> Whenever a local failure really happens, dataplane notices it by LoS or
> BFD, then can immediately disseminate the changed LSA using FN. So, in
> addition to the per-hop CP processing of LSAs, you could also spare
> some time with originating an LSA:
> - failure trigger reaching/processed by CP
> - OSPF originating a new LSA
> - OSPF sending the LSU packet down to DP
> 
> Cheers,
> András
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf