1 / 7

IPCDN QOS MIB

IPCDN QOS MIB. Schedule 7/31 to 8/5/00 Informally review these changes to ( via reflector) 8/11 Submit qos-mib-03 to IETF draft 8/11 - 9/8 IPCDN working group last call 9/15 Submit WG-approved -04 draft to IESG

chandler
Download Presentation

IPCDN QOS MIB

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. IPCDN QOS MIB • Schedule • 7/31 to 8/5/00 Informally review these changes to ( via reflector) • 8/11 Submit qos-mib-03 to IETF draft • 8/11 - 9/8 IPCDN working group last call • 9/15 Submit WG-approved -04 draft to IESG • 10/15 Submit “final” -05 draft • 12/15/00 IETF-49 (San Diego) Proposed RFC

  2. QOS MIB 02 Issues MIB changes 1. Reorganize docQosParamSetTable 2. Change type of docsQosParamSetRequestPolicy to OCTET STRING (4) 3. Add docsQosPktClassBitMap 4. Change Index of docsQosPHSTable 5. Change docsQosServiceClassName to DisplayString (1..15) Description Changes 6. Don’t support Docsis 1.0 modem flows 7. Clarify ‘TosAndMask and ‘TosOrMask as upstream only 8. Clarify ‘UpstreamStatsTable description concerning errored packets 9. Support Ethertype/DSAP/MacType parameter changes (RFI-N-00019). 10. Clarify docsQosPktClassVlanID compares only 12 MS bits (RFI-N-00059)

  3. Issue 1. Reorganize docsQosParamSetTable Qos-mib-02: Qos-mib-03: docsQosParamSetTable { ‘RowType, ‘QPSIndex} docsQosServiceFlowParamSetTable { ifIndex, SFID, ‘QPSType } ‘rowtype SF 1 (22 qos params) 2 (13 numeric params) prov(1) 0x100 SF 2 Service flows 2 0x100 admit(2) SF 3 2 4 0x100 active(3) SF 2 0x101 ... SF 2 0x101 1 SC Service Classes 2 docsQosServiceClassTable {‘Name} SC (20 qos params) 3 “default” SC ... docsQosServiceFlowTable { ifIndex, SFID } docsQosServiceFlowTable Prov Admit ActiveQPS ... 2 0x100 2 0x100 1 3 2 (6 QPSType-independent qos params) 4 6 2 0x101 5 2 0x101

  4. Issue 2: docsQosParamSetRequestPolicy TLV: Integer32 TLV: Integer32 31 31 3 2 1 0 3 2 1 0 ... ... msb lsb 8 0 1 2 3 4 5 6 7 8 msb lsb QOS-MIB-02: BITS QOS-MIB-03: OCTET STRING(4) Bit-swap required No Bit-swap

  5. Issue 3: Add docsQosPktClassBitMap • QOS-mib-02’s docsQosPktClassTable defines an object id column for each possible criteria. • What object value should be used for a criteria that is not present in the classifier? • -01 and -02 attempted to define “matches all packets” equivalent to missing criteria • Problem: ambiguous how to describe a rule that “matches all packets” • Problem: 802.1P priority needed an auxiliary bit to indicate it “applied” • How do you usually encode set presence? With a bit map. • -03 adds a docsQosPktClassBitMap BITS object to indicate which criteria are “present”. • Enumerated BITS • IpTos(0), IpSource(1), IpDest, SourcePort(2), DestPort(3), DestMac(4), SourceMac(5), PacketType(6), Dot1PPri(7), VlanId(8) docsQosPktClassBitMap 1 0 0 1 1 0 1 1 Present criteria Absent criteria

  6. Issue 4: Change Index of docsQosPHSTable QOS-MIB-02 QOS-MIB-03 docsQosPktClassTable docsQosPktClassTable ... ... ifIndex SFID ‘ClassId ifIndex SFID ‘ClassId 2 0x20 0x055 2 0x20 0x055 docsQosPHSTable docsQosPHSTable ... ... ifIndex SFID PHSI ClassId ifIndex SFID ClassId PHSI 2 0x20 5 0x55 2 0x20 5 0x55 Classifier ID is primary ID of a PHS

  7. -02 and -03 Compatibility • Not required, but believed to be desirable • -03 will not redefine (change the type of) an object ID defined in -02 • Some objects will be deleted • docsQosParamSetTable • docsQosPHSTable • docsQosServiceFlowProvisionedParamSetIndex, ‘Admitted, ‘Active... • Not using “deprecated” status • unused names (docsQosParamSetTable) simply removed from the .mib • -03 adds new objects to entries • docsQosPktClassBitMask • docsQosServiceClassXXX for QPS params XXX • -03 adds a new table • docsQosServiceFlowParamSetTable • Bottom Line: • An -02 Manager reading an -03 client will get “no such object” for deleted OIDs. • An -03 Manager reading an -02 client will get “no such object” for new OIDs.

More Related