1 / 8

ForCES Library Draft

ForCES Library Draft. Joel M. Halpern joel@stevecrocker.com. Purpose. To build a ForCES implementation that does anything, we need a set of LFB Class definitions There will be multiple documents that provide these This is intended to provide a good starting point. Structure.

aaralyn
Download Presentation

ForCES Library Draft

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ForCES Library Draft Joel M. Halpern joel@stevecrocker.com

  2. Purpose • To build a ForCES implementation that does anything, we need a set of LFB Class definitions • There will be multiple documents that provide these • This is intended to provide a good starting point

  3. Structure • I have grouped the Classes into sections • Groupings are fairly arbitrary • Connectivity LFBs • Packet Valdiation & Manipulation LFBs • Classifier LFBs • Packet Control LFBs • Queue & Scheduler LFBs

  4. Connectivity LFBs • These LFBs represent the connectivity (very generally) to the external world. • This includes provision for stacking connectivity (PPP stacked on Serial Line, Frame Relay, or Ethernet) • Redirect LFB for FE-CE redirect packets • Tagged Data is envisioned for backplanes that can carry meta-data.

  5. Packet Valdiation & Manipulation • Validators, trimmers, markers, and updaters • Separates validation from classification • Some implementations will not want to validate packets being forwarded • Updaters possibly should be folded into next hop selection LFBs

  6. Classifier LFBs • Cover the different kinds of classifiers • Currently, one that considers incoming LFB port, and matches field contents from meta-data and packet contents • Separate LPM classifier • Trying to fold LPM into the general classifer structure hurt my head • Should we have different classifiers? • One that used metadata, one for packet fields

  7. Packet Control LFBs • A catch all for odd functions • These may be better dealt with by the CE for the first release • They may exercise some useful features • ICMP, ARP related functions

  8. Queue & Scheduler LFBs • Need to store and send packets • Separating queue and scheduler has been found useful in other models • Need to model the relationship • Rather awkward approach. Suggestions would be appreciated.

More Related