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

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