Hi Rob, Thanks for the input and suggestions. My actual requirement is, some of the hardware vendors support offloading BFD sessions to hardware (BFD hardware offloading). i.e the router hardware constructs and sends OAM messages. Normally an special FPGA will be employed to offload OAM processing from routing processing resources ensuring scalability and quick restoration. This is very much required in case of MPLS TP OAM mechanisms
I just want to understand whether there is any proposal or discussion in ONF to support this in OpenFlow Switches aligning to the BFD hardware offload mechanism. Regards, S. Kingston Smiler. On Mon, Aug 22, 2011 at 11:50 PM, Rob Sherwood <[email protected]>wrote: > On Mon, Aug 22, 2011 at 10:58 AM, Kingston Smiler > <[email protected]> wrote: > > Hi All, > > The OpenFlow Spec 1.1.0 doesn't mention anything about the OAM > mechanisms. > > Please let me if anyone is working on the OAM aspects in OpenFlow. > > So, at least IMHO, OpenFlow is roughly orthogonal to most OAM > mechanism. There do exist hooks from OpenFlow into a box's existing > mechanisms, e.g., BFD, via the group table's "fast-failover" group, > but OpenFlow proper focuses on forwarding. Independently, it's > possible to do topology discovery strictly through OpenFlow's > packet_in/packet_out messages, although there are scaling concerns > about this approach and various people have talked about ways to > better leverage the box's already existing OAM mechanisms, but they > have never really taken off. > > Was there some specific use-case you were concerned about? > > I guess to more directly answer your question, there have been > discussions about OAM but I'm not aware of any active proposals in the > ONF. Strictly IMHO, but I haven't heard anyone discuss these issues > as a major pain point. > > Hope that helps, > > - Rob > . >
_______________________________________________ openflow-discuss mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
