ForCES Forwarding Element Functional Model

1
ForCES Forwarding Element Functional Model

• Presented by
• Joel M. Halpern
• Megisto Systems

2
draft-yang-forces-model-00.txt

• Lily L. Yang lily.l.yang_at_intel.com
• Joel Halpern jmh_at_joelhalpern.com
• Ram Gopal ram.gopal_at_nokia.com
• Ram Dantu ramd_at_netrake.com
• A Description of the Modeling required to support
  the Forces Protocol

3
Issues

• How to represent the Models
• On the Wire
• In the Document
• How complex a Capabilities Model
• What Elements for the State Model

4
Representation

• The two (Capabilities and State) models should
  share representation and element identification
• Should we use a combined document / on the wire
  representation (XML based?)
• Should we use an existing document representation
  / compilation (SMI, SPPI)
• Should we build our own NO!

5
Capabilities Model

• Current Document calls for a very dimple
  capabilities model
• There is now existing work on which to base a
  more complex capabilities model
• Framework Policy Information Base
• Differentiated Services Quality of Service Policy
  Information Base

6
Framework PIB Capabilities

• draft-ietf-rap-frameworkpib-09.txt
• Sections 4.1 gives an overview
• Particularly Component Limitations Table
• Describes what PIBS are supported
• Describes Limitations in support of objects
• Can limit the number of instances of an object
• Can limit the range or values of an attribute

7
DiffServ PIB Capabilities

• draft-ietf-diffserv-pib-09.txt
• Extends the Framework PIB Capabilities
• Section 4.7 has an overview
• Specific Element Capabilities information
• What fields can be filtered, what can be done
  with out of profile packets, how many scheduler
  inputs,
• Specific linkage restriction information

8
Model Components

• Called Forces Blocks in the document
• Base elements for modeling
• Need to build a good, but not excessive set
• The Diffserv set would seem a good starting point
  for QoS
• Also need a forwarding set
• And Forwarding Capabilities?