1 / 9

Framework PIB

Framework PIB. David Durham Intel. COPS-PR/PIB Concepts. Shared (reusable) PIBs Client-Types, Contexts and Handles Framework PIB Incarnation Roles and Interface types Capabilities Limits. Reusable PIBs. Reusable PIBs in general is a useful concept Prevent redundant definitions

chill
Download Presentation

Framework PIB

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. Framework PIB David Durham Intel

  2. COPS-PR/PIB Concepts • Shared (reusable) PIBs • Client-Types, Contexts and Handles • Framework PIB • Incarnation • Roles and Interface types • Capabilities • Limits

  3. Reusable PIBs • Reusable PIBs in general is a useful concept • Prevent redundant definitions • Allow different COPS-PR Client-Types to reuse existing PIBs • Use Client-Type clause (List or “all”)

  4. Contexts • Each COPS Client-Type opened initialized a new non-overlapping instance namespace • Within a Client-Type, multiple contexts can be established, only one active at a time (these contexts identified via COPS Request Handle) • Framework PIB determines which context is active • Turn one context on, others turn off

  5. Framework PIB • Specify incarnation information • Identify active request state within Client-Type • Identify last PDP information, policy ID, TTL • Indicates supported PIB classes (PRCs) and attributes in support table • Specifies limitations on supported PRCs & restrictions on supported attributes • Roles supported by the device • Interface Types + corresponding capabilities

  6. Support Table • Devices vary, so PIBs will be augmented and deprecated • Support table identifies supported PRCs on the client • Support table identify supported attributes within a PRC • Expressed via a bit mask • Specifies maximum number of attributes supported

  7. Device Limitations • More up-front information to help PDP proactively provision policy • Further constrain support table • Specify what values within an attribute within a PRC are supported • Could use OCL-string style constraints

  8. Roles map to Interface Types Interface Type maps to capabilities Structure and Mappings Role Combination A+B Role Combination B+C Role A Role B Role C Interface Type A Interface Type B Capabilities Table Capabilities Table Capabilities Table

  9. Capabilities • Sent in COPS-PR Request • Corresponds to an Interface Type • Determines Interface Type specific capabilities • Classification • Policing • Scheduling • Etc. • Fundamentally determines what a particular interface type is capable of doing

More Related