From mailnull@www1.ietf.org Sat Feb 1 12:33:45 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11956 for ; Sat, 1 Feb 2003 12:33:45 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h11Hbou10173 for ipcdn-archive@odin.ietf.org; Sat, 1 Feb 2003 12:37:50 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h11Hb8J09685; Sat, 1 Feb 2003 12:37:08 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h11HaRJ09419 for ; Sat, 1 Feb 2003 12:36:27 -0500 Received: from ftpbox.mot.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11912; Sat, 1 Feb 2003 12:31:28 -0500 (EST) Received: from pobox.mot.com (pobox.mot.com [129.188.137.100]) by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id h11HZ36P008104; Sat, 1 Feb 2003 10:35:03 -0700 (MST) Received: [from ma07exm01.dma.isg.mot.com (ma07exm01.dma.isg.mot.com [150.21.2.102]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id KAA28511; Sat, 1 Feb 2003 10:35:01 -0700 (MST)] Received: by ma07exm01.dma.isg.mot.com with Internet Mail Service (5.5.2656.59) id ; Sat, 1 Feb 2003 12:35:01 -0500 Message-ID: <19CD0E423FC1D611893500508B6F0B9C08496B@ma07exm01.dma.isg.mot.com> From: Murwin William-LWM008 To: "'internet-drafts@ietf.org'" Cc: "'Michael W. Patrick (E-mail)'" , "'Docsis-Oss (E-mail) (E-mail)'" , "'IPCDN (E-mail) (E-mail)'" , "'Richard Woundy (E-mail)'" Date: Sat, 1 Feb 2003 12:35:00 -0500 Importance: high X-Priority: 1 Deferred-Delivery: Fri, 31 Jan 2003 15:00:00 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C2C958.BC3FAD70" Subject: [ipcdn] draft-ietf-ipcdn-qos-mib-07.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C2C958.BC3FAD70 Content-Type: text/plain; charset="iso-8859-1" Please post the following draft, Tiitle: Data Over Cable System Quality of Service Management Information Base (DOCSIS-QOS MIB) Version: 7 Dated: February 1, 2003 Work Group: IPCDN Authors: Michael Patrick and William Murwin ______________________________ William Murwin Broadband Communications Sector Motorola Inc. Email: W.Murwin@motorola.com Tel: (508) 851-8385 <> ------_=_NextPart_000_01C2C958.BC3FAD70 Content-Type: text/plain; name="draft-ietf-ipcdn-qos-mib-07.txt" Content-Disposition: attachment; filename="draft-ietf-ipcdn-qos-mib-07.txt" Content-Transfer-Encoding: quoted-printable =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= IPCDN Working Group Michael = Patrick=0A= William = Murwin=0A= Motorola BCS=0A= =0A= =0A= =0A= Data Over Cable System Quality of Service=0A= Management Information Base (DOCSIS-QOS MIB)=0A= =0A= February 1, 2003=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Status of this Memo=0A= =0A= This document is an Internet-Draft and is in full conformance = with=0A= all the provisions of Section 10 of RFC2026. Internet-Drafts are=0A= working documents of the Internet Engineering Task Force (IETF), = its=0A= Areas, and its Working Groups. Note that other groups may also=0A= distribute working documents as Internet-Drafts.=0A= =0A= Internet-Drafts are draft documents valid for a maximum of six = months=0A= and may be updated, replaced, or obsoleted by other documents at = any=0A= time. It is inappropriate to use Internet-Drafts as reference=0A= material or to cite them other than as a "work in progress".=0A= =0A= The list of current Internet-Drafts can be accessed at=0A= http://www.ietf.org/ietf/1id-abstracts.txt=0A= =0A= The list of Internet-Draft Shadow Directories can be accessed at=0A= http://www.ietf.org/shadow.html.=0A= =0A= =0A= Copyright (c) The Internet Society 2001. All Rights Reserved.=0A= =0A= =0A= Abstract=0A= =0A= This document defines a basic set of managed objects for = SNMP-based=0A= management of extended QOS features of Cable Modems (CMs) and = Cable=0A= Modem Termination Systems (CMTSs) conforming to the Data over = Cable=0A= System (DOCSIS) standard version 1.1.=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Expires August 2003 [Page 1]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= Table of Contents=0A= =0A= =0A= Status of this Memo............................... 1=0A= Abstract.......................................... 1=0A= Revision History.................................. 3=0A= =0A= 1. Introduction...................................... 6=0A= 1.1 The Internet-Standard Management Framework... 6=0A= 1.2 Glossary..................................... 6=0A= =0A= 2. Overview.......................................... 8=0A= 2.1 Textual Conventions.......................... 8=0A= 2.2 MIB Organization............................ 8=0A= 2.2.1 docsQosPktClassTable................. 12=0A= 2.2.2 docsQosParamSetTable................. 12=0A= 2.2.2.1 Interoperation with DOCSIS 1.0....... 14=0A= 2.2.3 docsQosServiceFlowTable.............. 15=0A= 2.2.4 docsQosServiceFlowStatsTable......... 16=0A= 2.2.5 docsQosUpstreamStatsTable............ 17=0A= 2.2.6 docsQosDynamicServiceStatsTable...... 17=0A= 2.2.7 docsQosServiceFlowLogTable........... 17=0A= 2.2.8 docsQosServiceClassTable............. 18=0A= 2.2.9 docsQosServiceClassPolicyTable....... 18=0A= 2.2.10 docsQosPHSTable...................... 18=0A= 2.2.11 docsQosCmtsMacToSrvFlowTable......... 19=0A= =0A= 3. Externally Administered Classification............ 19=0A= =0A= 4. Definitions....................................... 23=0A= =0A= 5. Security Considerations........................... 80=0A= =0A= 6. Intellectual Property............................. 81=0A= =0A= 7. Acknowledgement................................... 82=0A= =0A= 8. Normative References.............................. 82=0A= =0A= 9. Informative References............................ 83=0A= =0A= 10. Author's Address.................................. 83=0A= =0A= 11. Full Copyright Statement.......................... 84=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Expires August 2003 [Page 2]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= Revision History=0A= =0A= Rev Date Description=0A= --- -------- -----------=0A= -07 2/01/03 Functional Changes:=0A= - Re-routed the docQosMib because of = compilation=0A= errors.=0A= - Removed obsolete and deprecated = objects.=0A= - Renumbered existing objects after removal = of=0A= obsolete and deprecated objects.=0A= - Clarified the operation of the RowStatus = objects.=0A= - Clarified the description for = docsQosPktClassPkts.=0A= - Clarified the description for=0A= docsQosServiceFlowOctets.=0A= - Clarified the description for=0A= docsQosServiceFlowPkts.=0A= - Clarified the operation of the=0A= docsQosServiceClassStatus.=0A= - Changed the description of the reported = default=0A= values for the = docsQosParamSetMaxTrafficBurst and=0A= docsQosParamSetMaxConcatBurst.=0A= - Changed the default values for the=0A= docsQosServiceClassMaxTrafficBurst.=0A= and docsQosServiceClassMaxConcatBurst = objects.=0A= - Changed docsQosPktClassPkts to a 64-bit = counter.=0A= - Changed docsQosServiceFlowOctets to a=0A= 64-bit counter.=0A= - Changed docsQosServiceFlowPkts to a = 64-bit=0A= counter.=0A= - Changed docsQosServiceFlowLogPkts to a = 64-bit=0A= counter.=0A= - Changed docsQosServiceFlowLogOctets to a = 64-bit=0A= counter.=0A= Editorial Changes:=0A= - Updated Author's Address.=0A= - Updated Section 2.2.4 = docsQosServiceFlowStatsTable.=0A= - Section 1.1 was updated to reflect the=0A= most recent MIB boilerplate.=0A= - Section 5 was updated to reflect the=0A= most recent Security Considerations.=0A= - Split References into Normative and = Informative.=0A= - Updated references to refer to current = RFCs.=0A= - Removed section 2.2.1.1 InetAddress = Transition.=0A= -06 11/8/01 Functional Changes:=0A= - Deprecated objects that were of type = IpAddress=0A= and added new objects that were of type=0A= InetAddressType and InetAddress, to = support both=0A= IPv4 and IPv6 in the = docsQosPktClassTable.=0A= - Clarified the default value of the=0A= docsQosPktClassIpDestMask and=0A= docsQosPktClassIpSourceMask.=0A= =0A= =0A= =0A= Expires August 2003 [Page 3]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= - Clarified that some of counters from = the=0A= docsQosDynamicServiceStatsTable, = include=0A= retries.=0A= - Added objects that were removed from = earlier=0A= revisions of the mib, as obsolete.=0A= - In section 2.2.2.1, in bullet item (1) = removed=0A= requirement of adding row to=0A= docsIfQosProfileTable.=0A= - Clarified the Cable Modem's implementation = of the=0A= docsQosParamSetTosAndMask.=0A= Editorial Changes:=0A= - Corrected the description of the = individual bits=0A= that make up = docsQosParamsSetRequestPolicyOct.=0A= - Corrected the spelling of = docsCableMaclayer in the=0A= description of the = docsQosServiceFlowLogIfIndex.=0A= - In section 2.2.1, clarified the definition = of=0A= classifiers in the = docsQosPktClassTable.=0A= - In section 2.2.2.1, in bullet item (3) = flexibility=0A= was given to implementing=0A= docsIfQosProfileTable.=0A= - In section 2.2.2.1, added bullet item = (6).=0A= - Changed references to the latest = Data-Over-Cable=0A= Service Interface Specifications: Radio = Frequency=0A= Interface Specification.=0A= - Added section 2.2.1.1 InetAddress = Transition,=0A= to discuss the change from IpAddress = objects=0A= to InetAddressType and InetAddress = objects.=0A= - Changed the description of objects within = the=0A= docsQosServiceClassTable, so that they = were=0A= no longer templates for obsolete = objects.=0A= - Changed section 5 to "Security = Considerations".=0A= - Changed section 6 to "Intellectual = Property".=0A= - "References" where moved to section 8.=0A= - "Author's Address" where moved to section = 9.=0A= - Added section 7, "Acknowledgement".=0A= - Added section 10, "Full Copyright = Statement".=0A= - Section 1.1 was updated to reflect the=0A= most recent MIB boilerplate.=0A= - Updated references to refer to current = RFCs.=0A= =0A= =0A= -05 03/01/01 Functional Changes:=0A= - Changed default values of=0A= dosQosPktClassIpSourceMask and=0A= docsQosPktClassIpDestMask to = 255.255.255.255.=0A= Editorial Changes:=0A= - Corrected ifDirection values in 2.1.=0A= - In section 2.2.2.1, clarified which=0A= packets/bytes are counted in = docsIfCmtsService-=0A= InPkts and docsIfCmtsServiceInOctets.=0A= - Clarified description of = dosQosServiceFlowPkts=0A= =0A= =0A= =0A= Expires August 2003 [Page 4]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= to avoid requiring CMs to classify = downstream=0A= packets.=0A= - Clarified that = docsQosServiceFlowPHSUnknowns only=0A= applies to received packets.=0A= - Clarified that docsQosPktClassBitMap = and=0A= docsQosParamSetBitMap indicate all = parameters for=0A= both adds and changes.=0A= =0A= =0A= -04 10/18/00 - Updated descriptions of UGS applicable = QOS=0A= param set objects.=0A= - Added two new docsQosPktClassBitMap = bits=0A= and *renumbered* the bits.=0A= - Added docsQosServiceClassDirection=0A= =0A= -04 10/10/00 - Updated Overview to not mention = restriction=0A= to SnmpV1.=0A= - Updated most docsQosParamSet objects to=0A= clarify default and "not applicable" = values.=0A= - Add docsQosPktClassBitMap, = docsQosParamSetBitMap=0A= - Restore docsQosParamSetServiceClassName=0A= - Add 5 objects to = docsQosServiceFlowLogTable=0A= =0A= -04 10/01/00 - Move six objects from = docsQosServiceFlowTable=0A= back to docsQosParamSetTable.=0A= - Add DCC statistics=0A= - Removed notApplicable(256) from=0A= docsQosParamSetSchedulingType=0A= =0A= -03 08/11/00 Reorganize docsQosParamSetTable.=0A= =0A= -02 12/08/99 Add docsQosServiceFlowStatsTable,=0A= docsQosUpstreamStatsTable,=0A= docsQosDynamicServiceStatsTable,=0A= docsQosServiceFlowLogTable=0A= -01 06/25/99 Complete rewrite based on -I01 draft=0A= -00 08/07/98 Initial draft posted for discussion.=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Expires August 2003 [Page 5]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= 1. Introduction=0A= =0A= This memo specifies a MIB module in a manner that is compliant to = the=0A= SNMP SMIv2[1][2][3]. The set of objects is consistent with the = SNMP=0A= framework and existing SNMP standards.=0A= =0A= This memo is a product of the IPCDN working group within the = Internet=0A= Engineering Task Force. Comments are solicited and should be=0A= addressed to the working group's mailing list at ipcdn@ietf.org=0A= and/or the author.=0A= =0A= =0A= 1.1 The Internet-Standard Management Framework=0A= =0A= For a detailed overview of the documents that describe the = current=0A= Internet-Standard Management Framework, please refer to section 7 = of=0A= RFC 3410 [12].=0A= =0A= Managed objects are accessed via a virtual information store, = termed=0A= the Management Information Base or MIB. MIB objects are = generally=0A= accessed through the Simple Network Management Protocol (SNMP).=0A= Objects in the MIB are defined using the mechanisms defined in = the=0A= Structure of Management Information (SMI). This memo specifies a = MIB=0A= module that is compliant to the SMIv2, which is described in STD = 58,=0A= RFC 2578 [1], STD 58, RFC 2579 [2] and STD 58, RFC 2580 [3].=0A= =0A= 1.2 Glossary=0A= =0A= =0A= =0A= Active QPS Active Qos Parameter Set. The set of QOS = parameters=0A= that describe the current level service provided to = a=0A= Service Flow.=0A= =0A= Active SF Active Service Flow. An SF with a non-empty Active=0A= QPS.=0A= =0A= Admitted QPS Admitted Qos Parameter Set. The set of QOS = parameters=0A= that describe a level of service which the Service=0A= Flow is not currently using, but which it is=0A= guaranteed to receive upon the SF's request to = make=0A= the set Active.=0A= =0A= Admitted SF A Service Flow with a non-empty Admitted QPS.=0A= =0A= CATV Cable TV=0A= =0A= CM Cable Modem, a modem connecting a subscriber's LAN = the=0A= CATF RF network. DOCSIS CMs operate as a MAC layer=0A= bridge between the home LAN and the RF network.=0A= =0A= =0A= =0A= =0A= Expires August 2003 [Page 6]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= CMTS Cable Modem Termination System, the "head-end" = device=0A= providing connectivity between the RF network and = the=0A= Internet.=0A= =0A= Downstream The direction from the head end towards the=0A= subscriber.=0A= =0A= DSA Dynamic Service Addition, a DOCSIS MAC management=0A= message requesting the dynamic creation of a new=0A= Service Flow. New SFs are created with a three-=0A= message exchange of a DSA-REQ, DSA-RSP, and = DSA-ACK.=0A= =0A= DSC Dynamic Service Change, a DOCSIS MAC management=0A= message requesting a change to the attributes of a=0A= Service Flow. SFs are changed with a = three-message=0A= exchange of a DSC-REQ, DSC-RSP, and DSC-ACK.=0A= =0A= DSD Dynamic Service Delete, a DOCSIS MAC management=0A= message requesting the deletion of a Service Flow. = SFs=0A= are deleted with a two-message exchange of a = DSD-REQ=0A= and DSD-ACK.=0A= =0A= Head-end The origination point in most cable systems of the=0A= subsriber video signals. It is generally also the=0A= location of the CMTS.=0A= =0A= PHS Payload Header Suppression, a feature of DOCSIS 1.1 = in=0A= which header bytes that are common in a sequence = of=0A= packets of a Service Flow are replaced by a = one-byte=0A= PHSI Index (PHSI) when transmitting the packet on = the=0A= RF network.=0A= =0A= Provisioned QPS A QOS Parameter Set describing an envelope of = service=0A= within which a Service Flow is authorized to = request=0A= admission. All existing service flows must have a=0A= non-empty Provisioned QPS, hence all SFs are=0A= considered to be "Provisioned".=0A= =0A= SCN Service Class Name -- a named set of QOS = parameters.=0A= A Service Flow may or may not be associated with a=0A= single named Service Class. A Service Class has as = an=0A= attribute a Qos Parameter Set that is used as the=0A= default set of values for all Service Flows = belonging=0A= to the Service Class.=0A= =0A= SID Service ID. A 16-bit integer assigned by the CMTS = for=0A= an Upstream Service Flow with a non-empty Active = QOS=0A= Parameter Set.=0A= =0A= SF Service Flow. A unidirectional stream of packets=0A= between the CM and CMTS. SFs are characterized as=0A= =0A= =0A= =0A= Expires August 2003 [Page 7]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= upstream or downstream. The SF is the fundamental=0A= unit of service provided on a DOCSIS CATV network.=0A= =0A= SFID Service Flow ID. A 32-bit unsigned integer = assigned=0A= by the CMTS to each Service Flows=0A= =0A= Upstream The direction from a subscriber CM to the head-end=0A= CMTS.=0A= =0A= =0A= =0A= =0A= 2. Overview=0A= =0A= This MIB provides a set of objects required for the management of=0A= DOCSIS 1.1 compliant Cable Modems (CM) and Cable Modem = Termination=0A= Systems (CMTS). The specification is derived from the DOCSIS 1.1=0A= Radio Frequency Interface specification [4]. Please note that = the=0A= referenced DOCSIS standard only requires Cable Modems to process = IPv4=0A= customer traffic. Design choices in this MIB reflect those=0A= requirements. Future versions of the DOCSIS standard are expected = to=0A= require support for IPv6 as well.=0A= =0A= The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL = NOT",=0A= "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in = this=0A= document are to be interpreted as described in [7].=0A= =0A= =0A= 2.1 Textual Conventions=0A= =0A= The textual convention "IfDirection" is defined to indicate the=0A= direction of a packet classifier relative to an interface. It = takes=0A= the values of either downstream(1) or upstream(2).=0A= =0A= The textual convention "BitRate" corresponds to the bits per = second=0A= as defined for QOS Parameter Sets in DOCSIS1.1. This definition=0A= includes all bits of the Ethernet MAC frame as transmitted on the = RF=0A= network, starting with the Destination Address and ending with = the=0A= Ethernet FCS. It does NOT includes bits in the DOCSIS MAC header.=0A= =0A= =0A= =0A= =0A= =0A= 2.2 MIB Organization=0A= =0A= =0A= The structure of the MIB is summarized below:=0A= =0A= =0A= =0A= =0A= =0A= =0A= Expires August 2003 [Page 8]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosMIB=0A= docsQosMIBObjects=0A= docsQosPktClassTable=0A= docsQosPktClassEntry=0A= docsQosPktClassId=0A= docsQosPktClassDirection=0A= docsQosPktClassPriority=0A= docsQosPktClassIpTosLow=0A= docsQosPktClassIpTosHigh=0A= docsQosPktClassIpTosMask=0A= docsQosPktClassIpProtocol=0A= docsQosPktClassInetSourceAddrType=0A= docsQosPktClassInetSourceAddr=0A= docsQosPktClassInetSourceMaskType=0A= docsQosPktClassInetSourceMask=0A= docsQosPktClassInetDestAddrType=0A= docsQosPktClassInetDestAddr=0A= docsQosPktClassInetDestMaskType=0A= docsQosPktClassInetDestMask=0A= docsQosPktClassSourcePortStart=0A= docsQosPktClassSourcePortEnd=0A= docsQosPktClassDestPortStart=0A= docsQosPktClassDestPortEnd=0A= docsQosPktClassDestMacAddr=0A= docsQosPktClassDestMacMask=0A= docsQosPktClassSourceMacAddr=0A= docsQosPktClassEnetProtocolType=0A= docsQosPktClassEnetProtocol=0A= docsQosPktClassUserPriLow=0A= docsQosPktClassUserPriHigh=0A= docsQosPktClassVlanId=0A= docsQosPktClassState=0A= docsQosPktClassPkts=0A= docsQosPktClassBitMap=0A= docsQosParamSetTable=0A= docsQosParamSetEntry=0A= docsQosParamSetServiceClassName=0A= docsQosParamSetPriority=0A= docsQosParamSetMaxTrafficRate=0A= docsQosParamSetMaxTrafficBurst=0A= docsQosParamSetMinReservedRate=0A= docsQosParamSetMinReservedPkt=0A= docsQosParamSetActiveTimeout=0A= docsQosParamSetAdmittedTimeout=0A= docsQosParamSetMaxConcatBurst=0A= docsQosParamSetSchedulingType=0A= docsQosParamSetNomPollInterval=0A= docsQosParamSetTolPollJitter=0A= docsQosParamSetUnsolicitGrantSize=0A= docsQosParamSetNomGrantInterval=0A= docsQosParamSetTolGrantJitter=0A= =0A= =0A= =0A= Expires August 2003 [Page 9]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosParamSetGrantsPerInterval=0A= docsQosParamSetTosAndMask=0A= docsQosParamSetTosOrMask=0A= docsQosParamSetMaxLatency=0A= docsQosParamSetType=0A= docsQosParamSetRequestPolicyOct=0A= docsQosParamSetBitMap=0A= docsQosServiceFlowTable=0A= docsQosServiceFlowEntry=0A= docsQosServiceFlowId=0A= docsQosServiceFlowSID=0A= docsQosServiceFlowDirection=0A= docsQosServiceFlowPrimary=0A= docsQosServiceFlowStatsTable=0A= docsQosServiceFlowStatsEntry=0A= docsQosServiceFlowPkts=0A= docsQosServiceFlowOctets=0A= docsQosServiceFlowTimeCreated=0A= docsQosServiceFlowTimeActive=0A= docsQosServiceFlowPHSUnknowns=0A= docsQosServiceFlowPolicedDropPkts=0A= docsQosServiceFlowPolicedDelayPkts=0A= docsQosUpstreamStatsTable=0A= docsQosUpstreamStatsEntry=0A= docsQosSID=0A= docsQosUpstreamFragments=0A= docsQosUpstreamFragDiscards=0A= docsQosUpstreamConcatBursts=0A= docsQosDynamicServiceStatsTable=0A= docsQosDynamicServiceStatsEntry=0A= docsQosIfDirection=0A= docsQosDSAReqs=0A= docsQosDSARsps=0A= docsQosDSAAcks=0A= docsQosDSCReqs=0A= docsQosDSCRsps=0A= docsQosDSCAcks=0A= docsQosDSDReqs=0A= docsQosDSDRsps=0A= docsQosDynamicAdds=0A= docsQosDynamicAddFails=0A= docsQosDynamicChanges=0A= docsQosDynamicChangeFails=0A= docsQosDynamicDeletes=0A= docsQosDynamicDeleteFails=0A= docsQosDCCReqs=0A= docsQosDCCRsps=0A= docsQosDCCAcks=0A= docsQosDCCs=0A= docsQosDCCFails=0A= docsQosServiceFlowLogTable=0A= =0A= =0A= =0A= Expires August 2003 [Page 10]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosServiceFlowLogEntry=0A= docsQosServiceFlowLogIndex=0A= docsQosServiceFlowLogIfIndex=0A= docsQosServiceFlowLogSFID=0A= docsQosServiceFlowLogCmMac=0A= docsQosServiceFlowLogPkts=0A= docsQosServiceFlowLogOctets=0A= docsQosServiceFlowLogTimeDeleted=0A= docsQosServiceFlowLogTimeCreated=0A= docsQosServiceFlowLogTimeActive=0A= docsQosServiceFlowLogDirection=0A= docsQosServiceFlowLogPrimary=0A= docsQosServiceFlowLogServiceClassName=0A= docsQosServiceFlowLogPolicedDropPkts=0A= docsQosServiceFlowLogPolicedDelayPkts=0A= docsQosServiceFlowLogControl=0A= docsQosServiceClassTable=0A= docsQosServiceClassEntry=0A= docsQosServiceClassName=0A= docsQosServiceClassStatus=0A= docsQosServiceClassMaxTrafficRate=0A= docsQosServiceClassMaxTrafficBurst=0A= docsQosServiceClassMinReservedRate=0A= docsQosServiceClassMinReservedPkt=0A= docsQosServiceClassMaxConcatBurst=0A= docsQosServiceClassNomPollInterval=0A= docsQosServiceClassTolPollJitter=0A= docsQosServiceClassUnsolicitGrantSize=0A= docsQosServiceClassNomGrantInterval=0A= docsQosServiceClassTolGrantJitter=0A= docsQosServiceClassGrantsPerInterval=0A= docsQosServiceClassMaxLatency=0A= docsQosServiceClassActiveTimeout=0A= docsQosServiceClassAdmittedTimeout=0A= docsQosServiceClassSchedulingType=0A= docsQosServiceClassRequestPolicy=0A= docsQosServiceClassTosAndMask=0A= docsQosServiceClassTosOrMask=0A= docsQosServiceClassDirection=0A= docsQosServiceClassPolicyTable=0A= docsQosServiceClassPolicyEntry=0A= docsQosServiceClassPolicyIndex=0A= docsQosServiceClassPolicyName=0A= docsQosServiceClassPolicyRulePriority=0A= docsQosServiceClassPolicyStatus=0A= docsQosPHSTable=0A= docsQosPHSEntry=0A= docsQosPHSField=0A= docsQosPHSMask=0A= docsQosPHSSize=0A= docsQosPHSVerify=0A= =0A= =0A= =0A= Expires August 2003 [Page 11]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosPHSIndex=0A= docsQosCmtsMacToSrvFlowTable=0A= docsQosCmtsMacToSrvFlowEntry=0A= docsQosCmtsCmMac=0A= docsQosCmtsServiceFlowId=0A= docsQosCmtsIfIndex=0A= =0A= =0A= =0A= The MIB is organized as 11 tables. Most tables are implemented in=0A= both the CM and CMTS; the docsQosUpstreamStatsTable and=0A= docsQosServiceFlowLogTable are implemented on the CMTS only.=0A= =0A= =0A= 2.2.1 docsQosPktClassTable=0A= =0A= The docsQosPktClassTable reports the Service Flow Classifiers=0A= implemented by the managed device. The table is indexed by the = tuple=0A= { ifIndex, docsQosServiceFlowId, docsQosPktClassId }. The = ifIndex=0A= corresponds to an CATV MAC interface. Each CATV MAC interfaces has = a=0A= set of Service Flows, identified with a docsQosServiceFlowId = value=0A= that is unique for that interface. Each service flow may have a=0A= number of packet classifiers that map packets to the flow. The=0A= ClassifierId for the classifier is unique only within a = particular=0A= service flow.=0A= =0A= The semantics of packet classification are provided in [4]. = Briefly,=0A= the DOCSIS MAC interface calls for matching packets based on = values=0A= within the 802.2 (LLC), 802.3, IP, and/or UDP/TCP headers. = Packets=0A= which map more than one classifier are prioritized according to = their=0A= docsQosPktClassPriority value. The docsQosServiceFlowId (an index=0A= object) indicates to which service flow the packet is classified.=0A= =0A= The docsQosPktClassTable is distinct from the docsDevIpFilterTable = of=0A= [9] in that docsQosPktClassTable is intended only to reflect the=0A= state of the Service Flow Classifiers. Service Flow Classifiers = may=0A= be created only via a CM configuration file or from the Dynamic=0A= Service Addition (DSA) messages. For this reason,=0A= docsQosPktClassTable is read-only.=0A= =0A= The docsDevIpFilterTable is intended for external policy-based=0A= administration of packet classifiers. See the section = "Externally=0A= Administered Classification", below.=0A= =0A= =0A= 2.2.2 docsQosParamSetTable=0A= =0A= The docsQosParamSetTable reports the values of Qos Parameter Set = as=0A= defined in Section C.2.2 of [4].=0A= =0A= In general, a Service Flow is associated with three different Qos=0A= =0A= =0A= =0A= Expires August 2003 [Page 12]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= Parameter Sets (QPSs): an "active" QPS, an "admitted" QPS, and a=0A= "provisioned" or "authorized" QPS. The relationship of these = three=0A= sets is represented below:=0A= =0A= =0A= =0A= =0A= =0A= +---------------------+=0A= | Provisioned |=0A= | |=0A= | +---------------+ |=0A= | | Admitted | |=0A= | | | |=0A= | | +---------+ | |=0A= | | | Active | | |=0A= | | | | | |=0A= | | +---------+ | |=0A= | | | |=0A= | +---------------+ |=0A= | |=0A= +---------------------+=0A= =0A= Figure 1: Qos Parameter Sets=0A= =0A= =0A= =0A= The Provisioned QPS describes the maximum service envelope for = which=0A= the SF is authorized. The Admitted QPS is the set of services for=0A= which a service flow has requested admission to the DOCSIS RF=0A= network, but which is not yet active. The Admitted QPS is used = during=0A= the two-phase process of IP Telephony service flow admission to = admit=0A= the bandwidth for a bidirectional voice call when the far end is=0A= ringing. Since ringing may occur for up to four minutes, this=0A= permits the bandwidth to be reserved but not actually consumed = during=0A= this interval. The Active QPS is the set of services actually = being=0A= used by the Service Flow. The DOCSIS v1.1 specification [4] = defines=0A= what it means for a QPS envelope to be "within" another. In = general,=0A= an inner QPS is considered to be "within" an outer QPS when all = QOS=0A= parameters represent demands of equal or fewer resources of the=0A= network.=0A= =0A= In addition to their use as attributes of a Service Flow, a QPS = is=0A= also an attribute of a Service Class. A DOCSIS CM configuration = file=0A= or DSA message may request the creation of a new SF and give only = the=0A= Service Class Name. The CMTS "expands the macro" of a Service = Class=0A= Name creation by populating the Provisioned, Admitted, and/or = Active=0A= QPSs of the Service Flow with the QPS of the Service Class Name. = All=0A= of the QPSs of a Service Flow must be expansions of the same = Service=0A= Class, and in this case the SF is said to "belong" to the Service=0A= Class. Changing the contents of a Service Class' QPS does not = affect=0A= =0A= =0A= =0A= Expires August 2003 [Page 13]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= the QPS of any Service Flow earlier expanded from that Service = Class=0A= name. Only the CMTS implements docsQosServiceClassTable.=0A= =0A= See [4] section 8 for a full description and the theory of = operation=0A= of Docsis 1.1 QOS operation.=0A= =0A= =0A= =0A= The docsQosParamSetTable sets are indexed by { ifIndex,=0A= docsQosServiceFlowId, docsQosParamSetType}. ifIndex indicates a=0A= particular "DOCSIS MAC Domain". docsQosServiceFlowId uniquely=0A= identifies a service flow on that MAC domain. The=0A= docsQosParamSetType indicates whether the row describes an = active,=0A= admitted, or provisioned Qos Parameter Set.=0A= =0A= The docsQosParamSetTable is read-only, because it indicates the = Qos=0A= Parameter Set contents as defined by DOCSIS signaling. The=0A= docsQosServiceClassTable is read-create to permit managers to = define=0A= a template of Qos Parameters that can be referenced by DOCSIS = modems=0A= when creating their Qos Parameter Sets.=0A= =0A= =0A= 2.2.2.1 Interoperation with DOCSIS 1.0=0A= =0A= The DOCSIS 1.0 DOCS-IF-MIB [10] specifies a docsIfQosProfileTable = to=0A= describe the set of Class Of Service (COS) parameters associated = with=0A= a COS "profile". The docsIfCmServiceTable, which contains one = entry=0A= per SID, references this table with a docsIfCmServiceQosProfile=0A= number.=0A= =0A= The DOCSIS 1.1 CM registration process allows a modem to register = as=0A= operating either with DOCSIS 1.0 or DOCSIS 1.1 functionality. = For=0A= ease of expression, we call a modem registering with DOCSIS 1.0=0A= functionality a "DOCSIS 1.0 modem", regardless of the modem's=0A= capabilities.=0A= =0A= A CMTS or CM supporting both DOCSIS 1.0 and DOCSIS 1.1 implements=0A= both the tables of [10] and the tables of this MIB. The=0A= interoperation goal is that before modem registration, the DOCSIS = 1.0=0A= MIB [10] applies. After registration, either the DOCSIS 1.0 or=0A= DOCSIS 1.1 MIB applies, depending on the mode with which the = modem=0A= registered. The specific interoperation rules are:=0A= =0A= =0A= 1. When a CM initially ranges, the CM implements a row in the=0A= DOCS-IF-MIB docsIfCmServiceTable and the CMTS implements a = row=0A= in the DOCS-IF-MIB docsIfCmtsServiceTable corresponding to = the=0A= default upstream Service ID (SID) used for = pre-registration=0A= upstream traffic. For historical compatibility a row may be=0A= created for the docsIfQosProfileTable with default values,=0A= which may be referenced by the docsIfCmServiceTable = entries.=0A= =0A= =0A= =0A= Expires August 2003 [Page 14]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= 2. Both a CMTS and CM implementing this MIB MUST NOT implement=0A= docsQosParamSetTable or docsQosServiceFlowTable rows until=0A= after the CM registers with DOCSIS 1.1 modem operation.=0A= =0A= =0A= 3. When a modem registers with the CMTS as a "DOCSIS 1.1" = modem,=0A= any exclusively-referenced row in DOCS-IF-MIB=0A= docsQosProfileTable representing the modems upstream Qos=0A= profile for pre-registration traffic MUST be removed.=0A= Multiply-referenced rows may remain. The=0A= docsQosIfCmServiceQosProfile object in the CM's row of=0A= docsIfCmServiceTable MUST be set to zero. The=0A= docsIfCmServiceTable row for the DOCSIS 1.1 modem continues = to=0A= exist, and the various statistic objects in that row are=0A= incremented. The CMTS should retain the = docsIfCmtsServiceTable=0A= entry for the DOCSIS 1.1 CM.=0A= =0A= =0A= 4. When a DOCSIS 1.1 modem registers, both the CMTS and CM=0A= represent all service flows described in the modem=0A= configuration file in docsQosParamSetTable and=0A= docsQosServiceFlowTable.=0A= =0A= =0A= 5. At the CMTS, the Docsis 1.0 MIB objects=0A= docsIfCmtsServiceInPackets and docsIfCmtsServiceInOctets for = a=0A= SID assigned to a Docsis 1.1 modem count only the pre-=0A= registration packets/bytes of those modems.=0A= =0A= =0A= 6. DOCSIS 1.0 modems do not have entries in the DOCS-QOS-MIB.=0A= =0A= =0A= =0A= 2.2.3 docsQosServiceFlowTable=0A= =0A= The docsQosServiceFlowTable provides read-only information about = all=0A= of the service flows known by the device. It is indexed by the=0A= combination of { ifIndex, dosQosServiceFlowId }, where ifIndex=0A= corresponds to a CATV MAC interface and docsQosServiceFlowId is = the=0A= 32- bit integer assigned by the CMTS controlling the MAC domain. = A=0A= CM typically has only a single CATV MAC interface, while a CMTS = may=0A= have several. See [10] for a description of the ifIndex = numbering=0A= for DOCSIS devices.=0A= =0A= The table indicates whether a given SF is in the upstream or=0A= downstream direction, and whether it is the "primary" SF in that=0A= direction. The primary SF carries traffic that is not otherwise=0A= classified to any other SF in that direction.=0A= =0A= =0A= =0A= =0A= =0A= Expires August 2003 [Page 15]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= 2.2.4 docsQosServiceFlowStatsTable=0A= =0A= The docsQosServiceFlowStatsTable provides statistics for all=0A= currently existing SFs known by the managed device. It provides=0A= basic packet and octet counters, as well as certain other = SF-specific=0A= stats such as the time at which the flow was created and how many=0A= seconds it has been active.=0A= =0A= The table also provides objects which can be used to fine-tune=0A= admission control decisions, namely the number of packets dropped = or=0A= delayed due to QOS policing decisions enforced by the managed = device.=0A= =0A= The model of the service flows stats table is that there exists a=0A= service flow Classification function followed by a service flow=0A= maximum rate Policing function for packets transmitted onto the=0A= Docsis RF network, as depicted below=0A= =0A= =0A= +----------+=0A= +------------+ clsfy 1 -----+ | Per-SF | = forwarded=0A= Pkts | |-----------> | | Maximum |---> for = Docsis=0A= ----->| Classify | clsfy 2 SF1 |--> | Rate | RF = Network=0A= | Function |-----------> | | Policing | = transmission=0A= | | -----+ | Function |=0A= | | | |----+=0A= | | | | |=0A= | | +----------+ = Dropped=0A= +------------+ | ^=0A= +----+ Delayed=0A= =0A= Packets intended for transmission onto the Docsis RF network=0A= (upstream or downstream) are first classified to a service flow = by=0A= matching one of several possible classifiers associated with that=0A= service flow. The docsQosPktClassPkts count includes the number = of=0A= packets that match the classifier, regardless of the eventual=0A= disposition of the packet.=0A= =0A= DOCSIS requires that each service flow be policed to maintain a=0A= maximum rate of transmission. This is performed by either dropping = or=0A= delaying a packet on that service flow. The=0A= docsQosServiceFlowPolicedDropPkts object counts the number of = service=0A= flow packets dropped by the policing function. The=0A= docsQosServiceFlowPolicedDelayPkts counts the number of packet=0A= delayed but still forwarded. The docsQosServiceFlowPkts object=0A= counts the total number of packets forwarded beyond the policing=0A= function intended for eventual transmission onto the DOCSIS RF=0A= network. Although packets may be latter dropped by other = functions=0A= (e.g. a transmit queue overflow on a DOCSIS hardware = transmitter),=0A= the docsQos MIB per service-flow counters are not affected in = this=0A= case.=0A= =0A= =0A= =0A= =0A= Expires August 2003 [Page 16]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= 2.2.5 docsQosUpstreamStatsTable=0A= =0A= This table provides statistics that are measured only at the CMTS = in=0A= the upstream direction. These include a count of the number of=0A= fragmentation headers received, fragments discarded, and the = number=0A= of concatenation headers received.=0A= =0A= =0A= 2.2.6 docsQosDynamicServiceStatsTable=0A= =0A= This table provides read-only stats on the operation of the = Dynamic=0A= Service state machines as specified in section 9.4 of [4]. It=0A= provides a set of 14 counters *in each direction* for a Docsis = MAC=0A= layer interface. That is, each Docsis MAC layer interface has one = row=0A= for downstream stats, and a second row for upstream stats.=0A= =0A= Eight of the counters are DSx packet type counts, one counter for=0A= each of the eight DSx packet types. For example, the = docsQosDSAReqs=0A= object in the upstream row at the CMTS counts the number of = DSA-REQ=0A= messages received by the CMTS from that interface. The=0A= docsQosDSAReqs object in the downstream row at the CMTS counts = the=0A= number of DSA-REQ messages transmitted by the CMTS on that = interface.=0A= =0A= The remaining six counters per (interface, direction) combination=0A= count the number of successful and unsuccessful *transactions* = that=0A= were initiated on the interface and direction. For example, the=0A= upstream docsQosDynamicAdds on a CMTS is the number of = successfully=0A= completed CM-initiated dynamic additions, because at the CMTS a = CM-=0A= initiated DSA starts in the upstream direction. The downstream=0A= docsQosDynamicAdds at a CMTS is the number of successful CMTS-=0A= initiated DSA transactions.=0A= =0A= Dynamic service transactions can fail for a number of reasons, as=0A= listed in the state machines of section 9.4. Rather than include=0A= still more counters for each different failure reason, they are=0A= grouped into a single count, e.g docsQosDynamicAddFails. Again, = this=0A= object exists in both directions, so that locally originated vs=0A= remotely originated transaction failures are counted separately.=0A= Further troubleshooting of transaction failures will require = vendor-=0A= specific queries and operation.=0A= =0A= =0A= 2.2.7 docsQosServiceFlowLogTable=0A= =0A= This table contains a log of the Service Flows no longer existing = in=0A= the docsQosServiceFlowTable. It is intended to be periodically = polled=0A= by traffic monitoring and billing agents. It is implemented only = at=0A= the CMTS.=0A= =0A= It contains a chronological log of SF session statistics, including = a=0A= total count of packets and octets transferred on the SF. It = includes=0A= =0A= =0A= =0A= Expires August 2003 [Page 17]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= time stamps of the SF creation and deletion time, as well as its=0A= number of active seconds. The active second count is the count of=0A= seconds that the SF had a non-empty Active Qos Parameter Set, i.e. = it=0A= was eligible to pass data. For unicast SFs, it includes the CM = MAC=0A= address associated with the flow for billing reference purposes.=0A= =0A= The maximum number of log records kept by a CMTS, and the = duration=0A= that a log record is maintained in the table is vendor-specific. = An=0A= explicit control object is provided so that the monitoring=0A= application can explicitly delete records it has read.=0A= =0A= =0A= 2.2.8 docsQosServiceClassTable=0A= =0A= This table defines the Service Class Name and references a Qos=0A= Parameter Set for each Service Class defined in a CMTS. It is=0A= indexed by the Service Class Name string itself. The table is = read-=0A= create on a CMTS, and is not implemented in a CM. Each entry of = the=0A= docsQosServiceClassTable should define a template for flows in a=0A= given direction (upstream or downstream). Some parameters of the=0A= docsQosServiceClassTable are specific to a particular direction, = and=0A= so their values are not-applicable when used as a template for = flows=0A= in the other direction.=0A= =0A= =0A= =0A= 2.2.9 docsQosServiceClassPolicyTable=0A= =0A= =0A= The docsQosServiceClassPolicyTable can be referenced by the=0A= docsDevFilterPolicyTable of [9] in order to have a "policy" that=0A= classifies packets to a named Service Class. This is one mechanism = by=0A= which "external" entities (like an SNMP manager) may control the=0A= classification of packet for QOS purposes. Entries are indexed by = a=0A= small integer docsQosServiceClassPolicyIndex. They provide a = Service=0A= Class Name and a Rule Priority. A policy referencing a row of = this=0A= table intends the packet to be forwarded on a Service Flow=0A= "belonging" to the named Service Class. See the section = "Externally=0A= Administered Classification", below.=0A= =0A= This table is implemented on both the CM and CMTS, and is = read-create=0A= on both.=0A= =0A= =0A= 2.2.10 docsQosPHSTable=0A= =0A= The Payload Header Suppression (PHS) feature of DOCSIS 1.1 = permits=0A= packets to replace the unchanging bytes of the Ethernet, IP, and = UDP=0A= headers with a one-byte index when transmitting on the cable = network.=0A= This is especially useful for IP Telephony packets, where such=0A= suppression can result in almost twice the number of calls = supported=0A= =0A= =0A= =0A= Expires August 2003 [Page 18]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= within the same upstream channel.=0A= =0A= Each entry of the table corresponds to a PHS Rule as described in=0A= section 8.4 of [4]. The rules are identified by their = corresponding=0A= service flow ID and docsQosPktClassId. A PHS rule is associated = with=0A= exactly one classifier. The table is therefore indexed by the = tuple=0A= { ifIndex, docsQosServiceFlowId, docsQosPktClassId}.=0A= =0A= This table is read-only, and MUST be implemented on both the CM = and=0A= CMTS when PHS is supported.=0A= =0A= =0A= 2.2.11 docsQosCmtsMacToSrvFlowTable=0A= =0A= The docsQosCmtsMacToSrvFlowTable provides describes the mapping of = CM=0A= mac addresses to the Service Flow Ids that are uniquely = identified=0A= with that CM. External applications may collect statistics on = all=0A= packets flowing through a CM by determining the SFID of all of = its=0A= flows, and then collecting the statistics of packets and bytes = for=0A= each flow.=0A= =0A= Downstream multicast service flows are not indicated in the=0A= docsQosCmtsMacToSrvFlowTable because they are not associated with=0A= only one CM.=0A= =0A= =0A= =0A= =0A= 3. Externally Administered Classification=0A= =0A= Docsis 1.1 provides rich semantics for the classification of = packets=0A= to service flows with it Service Flow Classifier table. Service = Flow=0A= Classifiers may be created statically in the DOCSIS CM = configuration=0A= file, or may be created dynamically with Dynamic Service Addition=0A= (DSA) and Dynamic Service Change (DSC) DOCSIS MAC messages.=0A= =0A= Several major issues arose with the concept of externally=0A= administered classification, i.e. should an external SNMP manager = be=0A= permitted to create classification rows? One problem was the co-=0A= ordination of classifier IDs, since such an approach would = require=0A= either separate classifier ID number spaces or objects to = co-ordinate=0A= both internal and external classifier ID assignments. A more = serious=0A= problem, however, was the requirement that external creation of = SF=0A= Classifiers would require "knowledge" of the individual Service = Flow=0A= ID for service flows by external applications. It was strongly = felt=0A= by the committee that SFIDs should remain an internal Docsis = object,=0A= and not be transmitted as part of protocol flows, e.g. for IP = packet=0A= telephony signaling. Docsis 1.1 introduced the concept of named=0A= Service Classes for ease of administration within a domain of CMs = and=0A= CMTSs. What was desired was to permit external classification of=0A= packets to a Service Class, not a particular Service Flow.=0A= =0A= =0A= =0A= Expires August 2003 [Page 19]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= The DOCSIS committee therefore decided to use the already-defined = IP=0A= Packet Filter Table [9] for the external classification of = packets=0A= for QOS purposes. The docsDevIpPacketFilterTable defines similar=0A= packet matching criteria as docsQosPktClassTable, but it matches = a=0A= packet to an arbitrary "policy set" instead of a particular = Service=0A= Flow. One of the policies in the policy set then selects the = Service=0A= Class of the SF on which to forward the packet. The=0A= docsQosServiceClassPolicyTable of this MIB defines the Service = Class=0A= Name to which a packet is classified.=0A= =0A= The interaction of external and internal packet classification is=0A= depicted below.=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Expires August 2003 [Page 20]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= =0A= =0A= |=0A= | Outbound Pkt=0A= V=0A= docsDevIpFilterTable------> docsDevFilterPolicyTable=0A= | |=0A= | V=0A= | docsQosServiceClassPolicyTable=0A= | |=0A= | Pkt | ServiceClassName,=0A= | | = ServiceClassPolicyRulePriority=0A= V V=0A= +--------------------------------------------------------+=0A= | | DOCSIS MAC LAYER ENTITY | |=0A= | | | Select any |=0A= | V | SFID Y in SCN|=0A= | docsQosPktClassTable <---------------| |=0A= | | | |=0A= | | docsQosPktClassPriority, | |=0A= | | SFID X | |=0A= | V V |=0A= | ----------------------------------------+ |=0A= | | Select the SFID associated with the | |=0A= | | higher of docsQosPktClassPriority or | |=0A= | | docsQosServiceClassPolicyRulePriority | |=0A= | +---------------------------------------+ |=0A= | | |=0A= | V |=0A= | | | | | |=0A= | | | ... | | Service Flows |=0A= | +----+ +----+ |=0A= | SFID X SFID Y |=0A= +--------------------------------------------------------+=0A= =0A= Figure 2: Docsis Packet Classification=0A= =0A= =0A= The processing of an outgoing packet proceeds as follows:=0A= =0A= 1. The packet is first checked for matches with rows of = the=0A= docsDevIpFilterTable. If it matches, the matching row=0A= provides a docsDevFilterPolicyId integer.=0A= =0A= 2. The docsDevFilterPolicyId indexes into one (or more) = rows=0A= of docsDevFilterPolicyTable. Each row provides an=0A= arbitrary RowPointer (docsDevFilterPolicyPtr),=0A= corresponding to a policy to be applied to the packet.=0A= =0A= 3. This MIB defines a docsQosServiceClassPolicyTable = whose=0A= entries may be pointed to by docsDevFilterPolicyPtr in=0A= =0A= =0A= =0A= Expires August 2003 [Page 21]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= order to administratively classify packets to a named=0A= DOCSIS Service Class. The = docsQosServiceClassPolicyEntry=0A= provides a Service Class Name (SCN) as=0A= docsQosServiceClassPolicyName and a classification = rule=0A= priority as docsQosServiceClassPolicyRulePriority. = These=0A= are submitted to the device's Docsis MAC Layer entity as = a=0A= special form of the MAC_DATA.request primitive, as=0A= described in Section E.2.1 of [4].=0A= =0A= 4. The MAC Layer selects an SFID ("Y") of an active = Service=0A= Flow belonging to the named class, choosing an SF=0A= arbitrarily if there is more than one.=0A= =0A= 5. The packet is then classified according to the=0A= docsQosPktClassTable, which may classify the packet to = a=0A= different SFID "X". Associated with the classifier is = a=0A= docsQosPktClassPriority.=0A= =0A= 6. In the event of a conflict between the SCN-determined = SFID=0A= and the classified SFID, the greater of=0A= docsQosPktClassPriority and=0A= docsQosServiceClassPolicyRulePriority determines which=0A= SFID is selected to forward the packet.=0A= =0A= A packet which does not match a = docsQosServiceClassPolicyEntry=0A= is directly submitted to the Docsis MAC layer, where the=0A= docsQosPktClassTable selects the SID on which it is to be=0A= forwarded.=0A= =0A= By convention (in [4]), the "internal" = docsQosPktClassPriority=0A= values should be in the range of 64-191, while the = "external"=0A= priorities may be either in the range 192-255 to override = the=0A= internal classification or the range 0-63 to be overridden = by=0A= internal classification.=0A= =0A= This classification mechanism applies both upstream from the = CM=0A= and downstream from the CMTS.=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Expires August 2003 [Page 22]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= 4. Definitions=0A= =0A= --=0A= -- Docsis QOS Extensions MIB=0A= --=0A= =0A= DOCS-QOS-MIB DEFINITIONS ::=3D BEGIN=0A= =0A= IMPORTS=0A= MODULE-IDENTITY,=0A= OBJECT-TYPE,=0A= Integer32,=0A= Counter32,=0A= Unsigned32,=0A= Counter64=0A= FROM SNMPv2-SMI=0A= =0A= TEXTUAL-CONVENTION,=0A= MacAddress,=0A= RowStatus,=0A= TruthValue,=0A= DisplayString,=0A= TimeStamp=0A= FROM SNMPv2-TC=0A= =0A= OBJECT-GROUP,=0A= MODULE-COMPLIANCE=0A= FROM SNMPv2-CONF=0A= =0A= ifIndex,=0A= InterfaceIndex=0A= FROM IF-MIB=0A= =0A= docsIfMib=0A= FROM DOCS-IF-MIB=0A= =0A= InetAddressType,=0A= InetAddress=0A= FROM INET-ADDRESS-MIB;=0A= =0A= docsQosMIB MODULE-IDENTITY=0A= LAST-UPDATED "200302010000Z" -- February 1, 2003=0A= ORGANIZATION "IETF IPCDN Working Group"=0A= CONTACT-INFO=0A= "=0A= Co-Author: Michael Patrick=0A= Postal: Motorola BCS=0A= 20 Cabot Blvd, MS M2-330=0A= Mansfield, MA 02048-1193=0A= U.S.A.=0A= Phone: +1 508 851 8402=0A= =0A= =0A= =0A= Expires August 2003 [Page 23]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= E-mail: michael.patrick@motorola.com=0A= =0A= Co-Author: William Murwin=0A= Postal: Motorola BCS=0A= 20 Cabot Blvd, MS M2-330=0A= Mansfield, MA 02048-1193=0A= U.S.A.=0A= Phone: +1 508 851 8385=0A= E-mail: w.murwin@motorola.com"=0A= =0A= DESCRIPTION=0A= "This is the management information for=0A= Quality Of Service (QOS) for DOCSIS 1.1."=0A= =0A= REVISION "200302010000Z" -- February 1, 2003=0A= DESCRIPTION=0A= "Published as draft-ietf-ipcdn-qos-mib-07.txt.=0A= =0A= Changes from qos-mib-06 include:=0A= =0A= - Re-routed the docQosMib because of compilation errors.=0A= - Removed obsolete and deprecated objects.=0A= - Renumbered existing objects after removal of=0A= obsolete and deprecated objects.=0A= - Clarified the description for = docsQosServiceFlowPolicedDropPkts.=0A= - Clarified the description for = docsQosServiceFlowPolicedDelayPkts.=0A= - Clarified the description for docsQosPktClassPkts.=0A= - Clarified the description for docsQosServiceFlowOctets.=0A= - Clarified the description for docsQosServiceFlowPkts.=0A= - Clarified the operation of the docsQosServiceClassStatus=0A= and the docsQosServiceClassPolicyStatus objects.=0A= - Changed docsQosPktClassPkts to a 64-bit counter.=0A= - Changed docsQosServiceFlowOctets to a 64-bit counter.=0A= - Changed docsQosServiceFlowPkts to a 64-bit counter.=0A= - Changed docsQosServiceFlowLogPkts to a 64-bit counter.=0A= - Changed docsQosServiceFlowLogOctets to a 64-bit counter.=0A= - Changed the description of the reported default values for = the=0A= docsQosParamSetMaxTrafficBurst and = docsQosParamSetMaxConcatBurst.=0A= - Changed the default values for the = docsQosServiceClassMaxTrafficBurst.=0A= and docsQosServiceClassMaxConcatBurst objects.=0A= - Changed references to the latest Data-Over-Cable=0A= Service Interface Specifications: Radio Frequency=0A= Interface Specification."=0A= REVISION "200111090000Z" -- November 9, 2001=0A= DESCRIPTION=0A= "Published as draft-ietf-ipcdn-qos-mib-06.txt.=0A= =0A= Changes from qos-mib-05 include:=0A= -Deprecated objects that were of type IpAddress=0A= and added new objects that were of type=0A= InetAddressType and InetAddress, to support both=0A= =0A= =0A= =0A= Expires August 2003 [Page 24]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= IPv4 and IPv6 in the docsQosPktClassTable.=0A= -Clarified the default value of the=0A= docsQosPktClassIpDestMask and=0A= docsQosPktClassIpSourceMask.=0A= -Corrected the description of the individual bits=0A= that make up the docsQosParamsSetRequestPolicyOct.=0A= -Corrected the spelling of docsCableMaclayer in the=0A= description of the docsQosServiceFlowLogIfIndex.=0A= -Clarified that some of counters from the=0A= docsQosDynamicServiceStatsTable, include retries.=0A= -Changed references to the latest Data-Over-Cable=0A= Service Interface Specifications: Radio Frequency=0A= Interface Specification.=0A= -Added objects that were removed from earlier=0A= revisions of the mib, as obsolete.=0A= -Clarified the Cable Modem's implementation of the=0A= docsQosParamSetTosAndMask.=0A= -Change the description of objects within the=0A= docsQosServiceClassTable, so that they were no longer=0A= templates for obsolete objects."=0A= REVISION "200103010000Z" -- March 1, 2001=0A= DESCRIPTION=0A= "Published as draft-ietf-ipcdn-qos-mib-05.txt.=0A= =0A= Changes from qos-mib-04 include:=0A= - Changed default value of docsQosPktClassIpSourceMask and=0A= docsQosPktClassIpDestMask to 255.255.255.255. This is the=0A= only functional change of the revision.=0A= - Clarified description of dosQosServiceFlowPkts to avoid=0A= requiring CMs to classify downstream packets.=0A= - Clarified that docsQosServiceFlowPHSUnknowns only applies = to=0A= received packets.=0A= - Clarified that docsQosPktClassBitMap and = docsQosParamSetBitMap=0A= indicate all parameters for both adds and changes."=0A= ::=3D { docsIfMib XXX } -- BPIPlus mib is docsIfMIb = 6=0A= =0A= docsQosMIBObjects OBJECT IDENTIFIER ::=3D { docsQosMIB 1 }=0A= =0A= -- Textual Conventions=0A= IfDirection ::=3D TEXTUAL-CONVENTION=0A= STATUS current=0A= DESCRIPTION "Indicates a direction on an RF MAC interface.=0A= =0A= The value downstream(1) is from Cable Modem=0A= Termination System to Cable Modem.=0A= =0A= The value upstream(2) is from Cable Modem to=0A= Cable Modem Termination System."=0A= SYNTAX INTEGER {=0A= downstream(1),=0A= upstream(2)=0A= =0A= =0A= =0A= Expires August 2003 [Page 25]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= }=0A= =0A= BitRate ::=3D TEXTUAL-CONVENTION=0A= DISPLAY-HINT "d"=0A= STATUS current=0A= DESCRIPTION "The rate of traffic in unit of bits per second.=0A= Used to specify traffic rate for QOS."=0A= SYNTAX Unsigned32=0A= =0A= SchedulingType ::=3D TEXTUAL-CONVENTION=0A= STATUS current=0A= DESCRIPTION "The scheduling service provided by a CMTS for = an=0A= upstream service flow. If the parameter is = omitted=0A= from an upstream QOS Parameter Set, this object = takes=0A= the value of bestEffort (2). This parameter must = be=0A= reported as undefined (1) for downstream QOS = Parameter=0A= Sets."=0A= SYNTAX INTEGER {=0A= undefined (1),=0A= bestEffort (2),=0A= nonRealTimePollingService(3),=0A= realTimePollingService(4),=0A= unsolictedGrantServiceWithAD(5),=0A= unsolictedGrantService(6)=0A= }=0A= =0A= -----------------------------------------------------------------------=0A= --=0A= -- Packet Classifier Table=0A= --=0A= docsQosPktClassTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosPktClassEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table describes the packet classification=0A= configured on the CM or CMTS.=0A= The model is that a packet either received=0A= as input from an interface or transmitted=0A= for output on an interface may be compared=0A= against an ordered list of rules pertaining to=0A= the packet contents. Each rule is a row of this=0A= table. A matching rule provides a service flow=0A= id to to which the packet is classified.=0A= All rules need to match for a packet to match=0A= a classifier.=0A= =0A= The objects in this row correspond to a set of=0A= Classifier Encoding parameters in a DOCSIS=0A= MAC management message. The = docsQosPktClassBitMap=0A= indicates which particular parameters were = present=0A= in the classifier as signaled in the DOCSIS = message.=0A= =0A= =0A= =0A= Expires August 2003 [Page 26]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= If the referenced parameter was not present=0A= in the signaled DOCSIS 1.1 Classifier, the=0A= corresponding object in this row reports a=0A= value as specified in the DESCRIPTION section.=0A= "=0A= ::=3D { docsQosMIBObjects 1 }=0A= =0A= =0A= docsQosPktClassEntry OBJECT-TYPE=0A= SYNTAX DocsQosPktClassEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "An entry in this table provides a single packet=0A= classifier rule. The index ifIndex is an ifType=0A= of docsCableMaclayer(127)."=0A= INDEX {=0A= ifIndex,=0A= docsQosServiceFlowId,=0A= docsQosPktClassId=0A= }=0A= ::=3D { docsQosPktClassTable 1 }=0A= =0A= =0A= =0A= DocsQosPktClassEntry ::=3D SEQUENCE {=0A= docsQosPktClassId Integer32,=0A= docsQosPktClassDirection IfDirection,=0A= docsQosPktClassPriority Integer32,=0A= docsQosPktClassIpTosLow OCTET STRING,=0A= docsQosPktClassIpTosHigh OCTET STRING,=0A= docsQosPktClassIpTosMask OCTET STRING,=0A= docsQosPktClassIpProtocol Integer32,=0A= docsQosPktClassInetSourceAddrType InetAddressType,=0A= docsQosPktClassInetSourceAddr InetAddress,=0A= docsQosPktClassInetSourceMaskType InetAddressType,=0A= docsQosPktClassInetSourceMask InetAddress,=0A= docsQosPktClassInetDestAddrType InetAddressType,=0A= docsQosPktClassInetDestAddr InetAddress,=0A= docsQosPktClassInetDestMaskType InetAddressType,=0A= docsQosPktClassInetDestMask InetAddress,=0A= docsQosPktClassSourcePortStart Integer32,=0A= docsQosPktClassSourcePortEnd Integer32,=0A= docsQosPktClassDestPortStart Integer32,=0A= docsQosPktClassDestPortEnd Integer32,=0A= docsQosPktClassDestMacAddr MacAddress,=0A= docsQosPktClassDestMacMask MacAddress,=0A= docsQosPktClassSourceMacAddr MacAddress,=0A= docsQosPktClassEnetProtocolType INTEGER,=0A= docsQosPktClassEnetProtocol Integer32,=0A= docsQosPktClassUserPriLow Integer32,=0A= docsQosPktClassUserPriHigh Integer32,=0A= =0A= =0A= =0A= Expires August 2003 [Page 27]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosPktClassVlanId Integer32,=0A= docsQosPktClassState INTEGER,=0A= docsQosPktClassPkts Counter64,=0A= docsQosPktClassBitMap BITS=0A= }=0A= =0A= docsQosPktClassId OBJECT-TYPE=0A= SYNTAX Integer32 (1..65535)=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Index assigned to packet classifier entry by=0A= the CMTS which is unique per service flow."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.3.2"=0A= ::=3D { docsQosPktClassEntry 1 }=0A= =0A= docsQosPktClassDirection OBJECT-TYPE=0A= SYNTAX IfDirection=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Indicates the direction to which the classifier=0A= is applied."=0A= ::=3D { docsQosPktClassEntry 2 }=0A= =0A= docsQosPktClassPriority OBJECT-TYPE=0A= SYNTAX Integer32 (0..255)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The value specifies the order of evaluation=0A= of the classifiers.=0A= The higher the value the higher the priority.=0A= The value of 0 is used as default in=0A= provisioned service flows classifiers.=0A= The default value of 64 is used for dynamic=0A= service flow classifiers.=0A= If the referenced parameter is not present=0A= in a classifier, this object reports the default = value=0A= as defined above."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.3.5"=0A= ::=3D { docsQosPktClassEntry 3 }=0A= =0A= docsQosPktClassIpTosLow OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(1))=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The low value of a range of TOS byte values.=0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value of = 0."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.1"=0A= ::=3D { docsQosPktClassEntry 4 }=0A= =0A= docsQosPktClassIpTosHigh OBJECT-TYPE=0A= =0A= =0A= =0A= Expires August 2003 [Page 28]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= SYNTAX OCTET STRING (SIZE(1))=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The 8-bit high value of a range of TOS byte=0A= values.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value of = 0."=0A= REFERENCE "SP-RFIv1.1-I07-010829, Appendix C.2.1.5.1"=0A= ::=3D { docsQosPktClassEntry 5 }=0A= =0A= docsQosPktClassIpTosMask OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(1))=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The mask value is bitwise ANDed with TOS byte=0A= in an IP packet and this value is used check=0A= range checking of TosLow and TosHigh.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value of = 0."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.1"=0A= ::=3D { docsQosPktClassEntry 6 }=0A= =0A= docsQosPktClassIpProtocol OBJECT-TYPE=0A= SYNTAX Integer32 (0..258)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object indicates the value of the IP=0A= Protocol field required for IP packets to match=0A= this rule.=0A= =0A= The value 256 matches traffic with any IP = Protocol=0A= value. The value 257 by convention matches both = TCP=0A= and UDP.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value of = 258."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.2"=0A= ::=3D { docsQosPktClassEntry 7 }=0A= =0A= docsQosPktClassInetSourceAddrType OBJECT-TYPE=0A= SYNTAX InetAddressType=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The type of the internet address for=0A= docsQosPktClassInetSourceAddr. This type must = be=0A= the same as the = docsQosPktClassInetSourceMaskType.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= =0A= =0A= =0A= Expires August 2003 [Page 29]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= ipv4(1)."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.3"=0A= ::=3D { docsQosPktClassEntry 8 }=0A= =0A= docsQosPktClassInetSourceAddr OBJECT-TYPE=0A= SYNTAX InetAddress=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object specifies the value of the IP=0A= Source Address required for packets to match=0A= this rule. An IP packet matches the rule when=0A= the packet ip source address bitwise ANDed=0A= with the docsQosPktClassInetSourceMask value=0A= equals the docsQosPktClassInetSourceAddr value.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= '00000000'H."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.3"=0A= ::=3D { docsQosPktClassEntry 9 }=0A= =0A= docsQosPktClassInetSourceMaskType OBJECT-TYPE=0A= SYNTAX InetAddressType=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The type of the internet address for=0A= docsQosPktClassInetSourceMask. This type must = be=0A= the same as the = docsQosPktClassInetSourceAddrType.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= ipv4(1)."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.4"=0A= ::=3D { docsQosPktClassEntry 10 }=0A= =0A= docsQosPktClassInetSourceMask OBJECT-TYPE=0A= SYNTAX InetAddress=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object specifies which bits of a packet's=0A= IP Source Address that are compared to match=0A= this rule.=0A= An IP packet matches the rule when the packet=0A= source address bitwise ANDed with the=0A= docsQosPktClassInetSourceMask value equals the=0A= docsQosIpPktClassInetSourceAddr value.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= 'FFFFFFFF'H."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.4"=0A= =0A= =0A= =0A= Expires August 2003 [Page 30]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= ::=3D { docsQosPktClassEntry 11 }=0A= =0A= docsQosPktClassInetDestAddrType OBJECT-TYPE=0A= SYNTAX InetAddressType=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The type of the internet address for=0A= docsQosPktClassInetDestAddr. This type must be=0A= the same as the = docsQosPktClassInetDestMaskType.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= ipv4(1)."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.5"=0A= ::=3D { docsQosPktClassEntry 12 }=0A= =0A= docsQosPktClassInetDestAddr OBJECT-TYPE=0A= SYNTAX InetAddress=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object specifies the value of the IP=0A= Destination Address required for packets to = match=0A= this rule. An IP packet matches the rule when=0A= the packet ip destination address=0A= bitwise ANDed with the=0A= docsQosPktClassInetDestMask value=0A= equals the docsQosPktClassInetDestAddr value.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= '00000000'H."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.5"=0A= ::=3D { docsQosPktClassEntry 13 }=0A= =0A= docsQosPktClassInetDestMaskType OBJECT-TYPE=0A= SYNTAX InetAddressType=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The type of the internet address for=0A= docsQosPktClassInetDestMask. This type must be=0A= the same as the = docsQosPktClassInetDestAddrType.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= ipv4(1)."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.6"=0A= ::=3D { docsQosPktClassEntry 14 }=0A= =0A= docsQosPktClassInetDestMask OBJECT-TYPE=0A= SYNTAX InetAddress=0A= MAX-ACCESS read-only=0A= =0A= =0A= =0A= Expires August 2003 [Page 31]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= STATUS current=0A= DESCRIPTION "This object specifies which bits of a packet's=0A= IP Destination Address that are compared to=0A= match this rule.=0A= An IP packet matches the rule when the packet=0A= destination address bitwise ANDed with the=0A= docsQosPktClassInetDestMask value equals the=0A= docsQosIpPktClassInetDestAddr value.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= 'FFFFFFFF'H."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.6"=0A= ::=3D { docsQosPktClassEntry 15 }=0A= =0A= docsQosPktClassSourcePortStart OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object specifies the low end inclusive=0A= range of TCP/UDP source port numbers to which=0A= a packet is compared. This object is irrelevant=0A= for non-TCP/UDP IP packets.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value of 0= ."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.7"=0A= ::=3D { docsQosPktClassEntry 16 }=0A= =0A= docsQosPktClassSourcePortEnd OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object specifies the high end inclusive=0A= range of TCP/UDP source port numbers to which=0A= a packet is compared. This object is irrelevant=0A= for non-TCP/UDP IP packets.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= 65535."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.8"=0A= ::=3D { docsQosPktClassEntry 17 }=0A= =0A= docsQosPktClassDestPortStart OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object specifies the low end inclusive=0A= range of TCP/UDP destination port numbers to=0A= which a packet is compared.=0A= =0A= =0A= =0A= Expires August 2003 [Page 32]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value of = 0."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.9"=0A= ::=3D { docsQosPktClassEntry 18 }=0A= =0A= docsQosPktClassDestPortEnd OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object specifies the high end inclusive=0A= range of TCP/UDP destination port numbers to = which=0A= a packet is compared.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= 65535."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.10"=0A= ::=3D { docsQosPktClassEntry 19 }=0A= =0A= docsQosPktClassDestMacAddr OBJECT-TYPE=0A= SYNTAX MacAddress=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "An Ethernet packet matches an entry when its=0A= destination MAC address bitwise ANDed with=0A= docsQosPktClassDestMacMask equals the value of=0A= docsQosPktClassDestMacAddr.=0A= =0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= '000000000000'H.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.6.1"=0A= ::=3D { docsQosPktClassEntry 20 }=0A= =0A= docsQosPktClassDestMacMask OBJECT-TYPE=0A= SYNTAX MacAddress=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "An Ethernet packet matches an entry when its=0A= destination MAC address bitwise ANDed with=0A= docsQosPktClassDestMacMask equals the value of=0A= docsQosPktClassDestMacAddr.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= '000000000000'H.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.6.1"=0A= ::=3D { docsQosPktClassEntry 21 }=0A= =0A= =0A= =0A= Expires August 2003 [Page 33]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosPktClassSourceMacAddr OBJECT-TYPE=0A= SYNTAX MacAddress=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "An Ethernet packet matches this entry when its=0A= source MAC address equals the value of=0A= this object.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= 'FFFFFFFFFFFF'H.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.6.2"=0A= ::=3D { docsQosPktClassEntry 22 }=0A= =0A= docsQosPktClassEnetProtocolType OBJECT-TYPE=0A= SYNTAX INTEGER {=0A= none(0),=0A= ethertype(1),=0A= dsap(2),=0A= mac(3),=0A= all(4)=0A= }=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object indicates the format of the layer 3=0A= protocol id in the Ethernet packet. A value of=0A= none(0) means that the rule does not use the=0A= layer 3 protocol type as a matching criteria.=0A= =0A= A value of ethertype(1) means that the rule=0A= applies only to frames which contains an=0A= EtherType value. Ethertype values are contained=0A= in packets using the Dec-Intel-Xerox (DIX)=0A= encapsulation or the RFC1042 Sub-Network Access=0A= Protocol (SNAP) encapsulation formats.=0A= =0A= A value of dsap(2) means that the rule applies=0A= only to frames using the IEEE802.3=0A= encapsulation format with a Destination Service=0A= Access Point (DSAP) other=0A= than 0xAA (which is reserved for SNAP).=0A= =0A= A value of mac(3) means that the rule applies=0A= only to MAC management messages for MAC = management=0A= messages.=0A= =0A= A value of all(4) means that the rule matches=0A= all Ethernet packets.=0A= =0A= If the Ethernet frame contains an 802.1P/Q Tag=0A= =0A= =0A= =0A= Expires August 2003 [Page 34]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= header (i.e. EtherType 0x8100), this object=0A= applies to the embedded EtherType field within=0A= the 802.1P/Q header.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value of = 0.=0A= =0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.6.3"=0A= ::=3D { docsQosPktClassEntry 23 }=0A= =0A= docsQosPktClassEnetProtocol OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "If docsQosEthPktClassProtocolType is none(0),=0A= this object is ignored when considering whether=0A= a packet matches the current rule.=0A= =0A= If dosQosPktClassEnetProtocolType is = ethertype(1),=0A= this object gives the 16-bit value of the=0A= EtherType that the packet must match in order to=0A= match the rule.=0A= =0A= If docsQosPktClassEnetProtocolType is dsap(2), = the=0A= lower 8 bits of this object's value must match = the=0A= DSAP byte of the packet in order to match the=0A= rule.=0A= =0A= If docsQosPktClassEnetProtocolType is mac(3), = the=0A= lower 8 bits of this object value represent a=0A= lower bound (inclusive) of MAC management = message=0A= type codes matched, and the upper 8 bits of this=0A= object value represent the upper bound = (inclusive)=0A= of matched MAC message type codes. Certain=0A= message type codes are excluded from matching, = as=0A= specified in the reference.=0A= =0A= If the Ethernet frame contains an 802.1P/Q Tag = header=0A= (i.e. EtherType 0x8100), this object applies to = the=0A= embedded EtherType field within the 802.1P/Q = header.=0A= =0A= If the referenced parameter is not present in = the=0A= classifier, the value of this object is reported as = 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.6.3"=0A= ::=3D { docsQosPktClassEntry 24 }=0A= =0A= docsQosPktClassUserPriLow OBJECT-TYPE=0A= SYNTAX Integer32 (0..7)=0A= MAX-ACCESS read-only=0A= =0A= =0A= =0A= Expires August 2003 [Page 35]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= STATUS current=0A= DESCRIPTION "This object applies only to Ethernet frames=0A= using the 802.1P/Q tag header (indicated with=0A= EtherType 0x8100). Such frames include a 16-bit=0A= Tag that contains a 3 bit Priority field and=0A= a 12 bit VLAN number.=0A= =0A= Tagged Ethernet packets must have a 3-bit=0A= Priority field within the range of=0A= docsQosPktClassPriLow and docsQosPktClassPriHigh = in=0A= order to match this rule.=0A= =0A= If the referenced parameter is not present in = the=0A= classifier, the value of this object is reported as = 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.7.1"=0A= ::=3D { docsQosPktClassEntry 25 }=0A= =0A= docsQosPktClassUserPriHigh OBJECT-TYPE=0A= SYNTAX Integer32 (0..7)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object applies only to Ethernet frames=0A= using the 802.1P/Qtag header (indicated with=0A= EtherType 0x8100). Such frames include a 16-bit=0A= Tag that contains a 3 bit Priority field and=0A= a 12 bit VLAN number.=0A= =0A= Tagged Ethernet packets must have a 3-bit=0A= Priority field within the range of=0A= docsQosPktClassPriLow and=0A= docsQosPktClassPriHigh in order to match this=0A= rule.=0A= =0A= If the referenced parameter is not present in = the=0A= classifier, the value of this object is reported=0A= as 7.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.7.1"=0A= ::=3D { docsQosPktClassEntry 26 }=0A= =0A= docsQosPktClassVlanId OBJECT-TYPE=0A= SYNTAX Integer32 (0..4095)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object applies only to Ethernet frames=0A= using the 802.1P/Q tag header.=0A= =0A= If this object's value is nonzero, tagged=0A= packets must have a VLAN Identifier that matches=0A= the value in order to match the rule.=0A= =0A= =0A= =0A= Expires August 2003 [Page 36]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= Only the least significant 12 bits of this = object's=0A= value are valid.=0A= =0A= If the referenced parameter is not present in = the=0A= classifier, the value of this object is reported=0A= as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.7.2"=0A= ::=3D { docsQosPktClassEntry 27 }=0A= =0A= docsQosPktClassState OBJECT-TYPE=0A= SYNTAX INTEGER {=0A= active(1),=0A= inactive(2)=0A= }=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object indicates whether or not the = classifier=0A= is enabled to classify packets to a Service = Flow.=0A= =0A= If the referenced parameter is not present in = the=0A= classifier, the value of this object is reported=0A= as active(1).=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.3.6"=0A= ::=3D { docsQosPktClassEntry 28 }=0A= =0A= docsQosPktClassPkts OBJECT-TYPE=0A= SYNTAX Counter64=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object counts the number of packets that = have=0A= been classified using this entry. This=0A= includes all packets delivered to a service flow=0A= maximum rate policing function, whether or not = that=0A= function drops the packets."=0A= ::=3D { docsQosPktClassEntry 29 }=0A= =0A= =0A= docsQosPktClassBitMap OBJECT-TYPE=0A= SYNTAX BITS { -- Reference = SP-RFIv1.1-I09-020830=0A= rulePriority(0), -- Appendix C.2.1.3.4=0A= activationState(1), -- Appendix C.2.1.3.6=0A= ipTos(2), -- Appendix C.2.1.5.1=0A= ipProtocol(3), -- Appendix C.2.1.5.2=0A= ipSourceAddr(4), -- Appendix C.2.1.5.3=0A= ipSourceMask(5), -- Appendix C.2.1.5.4=0A= ipDestAddr(6), -- Appendix C.2.1.5.5=0A= ipDestMask(7), -- Appendix C.2.1.5.6=0A= sourcePortStart(8), -- Appendix C.2.1.5.7=0A= sourcePortEnd(9), -- Appendix C.2.1.5.8=0A= =0A= =0A= =0A= Expires August 2003 [Page 37]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= destPortStart(10), -- Appendix C.2.1.5.9=0A= destPortEnd(11), -- Appendix C.2.1.5.10=0A= destMac(12), -- Appendix C.2.1.6.1=0A= sourceMac(13), -- Appendix C.2.1.6.2=0A= ethertype(14), -- Appendix C.2.1.6.3=0A= userPri(15), -- Appendix C.2.1.7.1=0A= vlanId(16) -- Appendix C.2.1.7.2=0A= }=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION=0A= "This object indicates which parameter encodings = were=0A= actually present in the DOCSIS packet classifier=0A= encoding signaled in the DOCSIS message that=0A= created or modified the classifier. Note that=0A= Dynamic Service Change messages have replace=0A= semantics, so that all non-default parameters = must=0A= be present whether the classifier is being = created=0A= or changed.=0A= =0A= A bit of of this object is set to 1 if the = parameter=0A= indicated by the comment was present in the = classifier=0A= encoding, and 0 otherwise.=0A= =0A= Note that BITS are encoded most significant bit=0A= first, so that if e.g. bits 6 and 7 are set, this = object=0A= is encoded as the octet string '030000'H.=0A= "=0A= ::=3D { docsQosPktClassEntry 30 }=0A= =0A= --=0A= -- QOS Parameter Set Table=0A= --=0A= docsQosParamSetTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosParamSetEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table describes the set of DOCSIS 1.1 QOS=0A= parameters defined in a managed device.=0A= =0A= The ifIndex index specifies a DOCSIS MAC Domain.=0A= The docsQosServiceFlowId index specifies a = particular=0A= Service Flow.=0A= The docsQosParamSetType index indicates whether=0A= the active, admitted, or provisioned QOS = Parameter=0A= Set is being described by the row.=0A= =0A= Only the QOS Parameter Sets of Docsis 1.1 = service=0A= flows are represented in this table. Docsis 1.0=0A= QOS service profiles are not represented in this=0A= table.=0A= =0A= =0A= =0A= Expires August 2003 [Page 38]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= Each row corresponds to a DOCSIS QOS Parameter = Set=0A= as signaled via DOCSIS MAC management messages.=0A= Each object in the row corresponds to one or=0A= part of one DOCSIS 1.1 Service Flow Encoding.=0A= The docsQosParamSetBitMap object in the row = indicates=0A= which particular parameters were signaled in=0A= the original registration or dynamic service=0A= request message that created the QOS Parameter = Set.=0A= =0A= In many cases, even if a QOS Parameter Set = parameter=0A= was not signaled, the DOCSIS specification calls=0A= for a default value to be used. That default = value=0A= is reported as the value of the corresponding = object=0A= in this row.=0A= =0A= Many objects are not applicable depending on=0A= the service flow direction or upstream = scheduling=0A= type. The object value reported in this case=0A= is specified in the DESCRIPTION clause.=0A= "=0A= ::=3D { docsQosMIBObjects 2 }=0A= =0A= -- docsQosParamSetEntry { docsQosParamSetTable 1 } was=0A= -- removed in an initial and unimplemented version of this mib.=0A= =0A= docsQosParamSetEntry OBJECT-TYPE=0A= SYNTAX DocsQosParamSetEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION=0A= "A unique set of QOS parameters."=0A= INDEX {=0A= ifIndex, docsQosServiceFlowId, docsQosParamSetType=0A= }=0A= ::=3D { docsQosParamSetTable 1 }=0A= =0A= DocsQosParamSetEntry ::=3D SEQUENCE {=0A= docsQosParamSetServiceClassName DisplayString,=0A= docsQosParamSetPriority Integer32,=0A= docsQosParamSetMaxTrafficRate BitRate,=0A= docsQosParamSetMaxTrafficBurst Unsigned32,=0A= docsQosParamSetMinReservedRate BitRate,=0A= docsQosParamSetMinReservedPkt Integer32,=0A= docsQosParamSetActiveTimeout Integer32,=0A= docsQosParamSetAdmittedTimeout Integer32,=0A= docsQosParamSetMaxConcatBurst Integer32,=0A= docsQosParamSetSchedulingType SchedulingType,=0A= docsQosParamSetNomPollInterval Unsigned32,=0A= docsQosParamSetTolPollJitter Unsigned32,=0A= docsQosParamSetUnsolicitGrantSize Integer32,=0A= docsQosParamSetNomGrantInterval Unsigned32,=0A= =0A= =0A= =0A= Expires August 2003 [Page 39]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosParamSetTolGrantJitter Unsigned32,=0A= docsQosParamSetGrantsPerInterval Integer32,=0A= docsQosParamSetTosAndMask OCTET STRING,=0A= docsQosParamSetTosOrMask OCTET STRING,=0A= docsQosParamSetMaxLatency Unsigned32,=0A= docsQosParamSetType INTEGER,=0A= docsQosParamSetRequestPolicyOct OCTET STRING,=0A= docsQosParamSetBitMap BITS=0A= }=0A= =0A= docsQosParamSetServiceClassName OBJECT-TYPE=0A= SYNTAX DisplayString=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Refers to the Service Class Name that the=0A= parameter set values were derived.=0A= =0A= If the referenced parameter is not present in = the=0A= corresponding DOCSIS QOS Parameter Set, the = default=0A= value of this object is a zero length string.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.3.4"=0A= ::=3D { docsQosParamSetEntry 4 }=0A= =0A= docsQosParamSetPriority OBJECT-TYPE=0A= SYNTAX Integer32 (0..7)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The relative priority of a service flow.=0A= Higher numbers indicate higher priority.=0A= This priority should only be used to = differentiate=0A= service flow with identical parameter sets.=0A= =0A= If the referenced parameter is not present in = the=0A= corresponding DOCSIS QOS Parameter Set, the = default=0A= value of this object is 0. If the parameter is=0A= not applicable, the reported value is 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.1"=0A= ::=3D { docsQosParamSetEntry 5 }=0A= =0A= docsQosParamSetMaxTrafficRate OBJECT-TYPE=0A= SYNTAX BitRate=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Maximum sustained traffic rate allowed for this=0A= service flow in bits/sec. Must count all MAC = frame=0A= data PDU from the bytes following the MAC header = HCS to=0A= the end of the CRC. The number of bytes=0A= forwarded is limited during any time interval.=0A= The value 0 means no maximum traffic rate is=0A= =0A= =0A= =0A= Expires August 2003 [Page 40]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= enforced. This object applies to both upstream = and=0A= downstream service flows.=0A= =0A= If the referenced parameter is not present in = the=0A= corresponding DOCSIS QOS Parameter Set, the = default=0A= value of this object is 0. If the parameter is=0A= not applicable, it is reported as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.2"=0A= ::=3D { docsQosParamSetEntry 6 }=0A= =0A= docsQosParamSetMaxTrafficBurst OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the token bucket size in bytes=0A= for this parameter set. The value is calculated=0A= from the byte following the MAC header HCS to=0A= the end of the CRC. This object is applied in=0A= conjunction with docsQosParamSetMaxTrafficRate = to=0A= calculate maximum sustained traffic rate.=0A= =0A= If the referenced parameter is not present in = the=0A= corresponding DOCSIS QOS Parameter Set, the = default=0A= value of this object for scheduling types=0A= bestEffort (2), nonRealTimePollingService(3),=0A= and realTimePollingService(4) is 3044.=0A= =0A= If this parameter is not applicable, it is = reported=0A= as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.3"=0A= ::=3D { docsQosParamSetEntry 7 }=0A= =0A= docsQosParamSetMinReservedRate OBJECT-TYPE=0A= SYNTAX BitRate=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the guaranteed minimum rate in=0A= bits/sec for this parameter set. The value is=0A= calculated from the byte following the MAC=0A= header HCS to the end of the CRC. The default=0A= value of 0 has the meaning that no bandwidth=0A= is reserved.=0A= If the referenced parameter is not present in = the=0A= corresponding DOCSIS QOS Parameter Set, the = default=0A= value of this object is 0. If the parameter=0A= is not applicable, it is reported as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.4"=0A= ::=3D { docsQosParamSetEntry 8 }=0A= =0A= =0A= =0A= Expires August 2003 [Page 41]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosParamSetMinReservedPkt OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies an assumed minimum packet size in=0A= bytes for which the = docsQosParamSetMinReservedRate=0A= will be provided. The value is calculated from=0A= the byte following the MAC header HCS to the=0A= end of the CRC.=0A= =0A= If the referenced parameter is omitted from a=0A= DOCSIS QOS parameter set, the default value is=0A= CMTS implementation dependent. In this case, the=0A= CMTS reports the default value it is using and = the=0A= CM reports a value of 0. If the referenced=0A= parameter is not applicable to the direction or=0A= scheduling type of the service flow, both CMTS = and=0A= CM report this object's value as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.5"=0A= ::=3D { docsQosParamSetEntry 9 }=0A= =0A= docsQosParamSetActiveTimeout OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= UNITS "seconds"=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the maximum duration in seconds that=0A= resources remain unused on an active service=0A= flow before CMTS signals that both active and=0A= admitted parameters set are null.=0A= The default value of 0 signifies an=0A= infinite amount of time.=0A= =0A= If the referenced parameter is not present in = the=0A= corresponding DOCSIS QOS Parameter Set, the = default=0A= value of this object is 0.=0A= "=0A= =0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.6"=0A= ::=3D { docsQosParamSetEntry 10 }=0A= =0A= docsQosParamSetAdmittedTimeout OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= UNITS "seconds"=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the maximum duration in seconds that=0A= resources remain in admitted state before=0A= resources must be released.=0A= The value of 0 signifies an infinite amount=0A= =0A= =0A= =0A= Expires August 2003 [Page 42]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= of time.=0A= =0A= If the referenced parameter is not present in = the=0A= corresponding DOCSIS QOS Parameter Set, the=0A= default value of this object is 200.=0A= "=0A= =0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.7"=0A= DEFVAL { 200 }=0A= ::=3D { docsQosParamSetEntry 11 }=0A= =0A= docsQosParamSetMaxConcatBurst OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the maximum concatenated burst in=0A= bytes which an upstream service flow is = allowed.=0A= The value is calculated from the FC byte of the=0A= Concatenation MAC Header to the last CRC byte in=0A= of the last concatenated MAC frame, inclusive.=0A= The value of 0 specifies no maximum burst.=0A= =0A= If the referenced parameter is not present in = the=0A= corresponding DOCSIS QOS Parameter Set, the = default=0A= value of this object for scheduling types=0A= bestEffort(2), nonRealTimePollingService(3), and=0A= realTimePollongSerivce is 1522. If the parameter = is=0A= not applicable, this object's value is reported=0A= as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.1"=0A= ::=3D { docsQosParamSetEntry 12 }=0A= =0A= =0A= docsQosParamSetSchedulingType OBJECT-TYPE=0A= SYNTAX SchedulingType=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the upstream scheduling service used = for=0A= upstream service flow.=0A= =0A= If the referenced parameter is not present in = the=0A= corresponding DOCSIS QOS Parameter Set of an=0A= upstream service flow, the default value of this=0A= object is bestEffort(2). For QOS parameter sets = of=0A= downstream service flows, this object's value is=0A= reported as undefined(1).=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.2"=0A= ::=3D { docsQosParamSetEntry 13 }=0A= =0A= =0A= =0A= =0A= Expires August 2003 [Page 43]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosParamSetNomPollInterval OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the nominal interval in microseconds=0A= between successive unicast request=0A= opportunities on an upstream service flow.=0A= =0A= This object applies only to upstream service = flows=0A= with schedulingType of value=0A= nonRealTimePollingService(3),=0A= realTimePollingService(4), and=0A= unsolictedGrantServiceWithAD(5). The parameter = is=0A= mandatory for realTimePollingService(4). If the=0A= parameter is omitted with=0A= nonRealTimePollingService(3), the CMTS uses an=0A= implementation dependent value. If the = parameter=0A= is omitted with unsolictedGrantServiceWithAD(5),=0A= the CMTS uses as a default value the value of = the=0A= Nominal Grant Interval parameter. In all cases,=0A= the CMTS reports the value it is using when the=0A= parameter is applicable. The CM reports the=0A= signaled parameter value if it was signaled,=0A= and 0 otherwise.=0A= =0A= If the referenced parameter is not applicable to=0A= the direction or scheduling type of the=0A= corresponding DOCSIS QOS Parameter Set, both=0A= CMTS and CM report this object's value as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.4"=0A= ::=3D { docsQosParamSetEntry 15 }=0A= =0A= docsQosParamSetTolPollJitter OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the maximum amount of time in=0A= microseconds that the unicast request interval=0A= may be delayed from the nominal periodic=0A= schedule on an upstream service flow.=0A= =0A= This parameter is applicable only to upstream=0A= service flows with a Schedulingtype of=0A= realTimePollingService(4) or=0A= unsolictedGrantServiceWithAD(5).=0A= =0A= If the referenced parameter is applicable but = not=0A= present in the corresponding DOCSIS QOS = Parameter=0A= =0A= =0A= =0A= Expires August 2003 [Page 44]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= Set, the CMTS uses an implementation dependent=0A= value and reports the value it is using.=0A= The CM reports a value of 0 in this case.=0A= =0A= If the parameter is not applicable to the=0A= direction or upstream scheduling type of the=0A= service flow, both CMTS and CM report this=0A= object's value as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.5"=0A= ::=3D { docsQosParamSetEntry 16 }=0A= =0A= docsQosParamSetUnsolicitGrantSize OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the unsolicited grant size in bytes.=0A= The grant size includes the entire MAC frame=0A= data PDU from the Frame Control byte to end of=0A= the MAC frame.=0A= =0A= The referenced parameter is applicable only=0A= for upstream flows with a SchedulingType of=0A= of unsolicitedGrantServicewithAD(5) or=0A= unsolicitedGrantService(6), and is mandatory=0A= when applicable. Both CMTS and CM report=0A= the signaled value of the parameter in this=0A= case.=0A= =0A= If the referenced parameter is not applicable to=0A= the direction or scheduling type of the=0A= corresponding DOCSIS QOS Parameter Set, both=0A= CMTS and CM report this object's value as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.6"=0A= ::=3D { docsQosParamSetEntry 17 }=0A= =0A= docsQosParamSetNomGrantInterval OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the nominal interval in microseconds=0A= between successive data grant opportunities=0A= on an upstream service flow.=0A= =0A= The referenced parameter is applicable only=0A= for upstream flows with a SchedulingType of=0A= of unsolicitedGrantServicewithAD(5) or=0A= unsolicitedGrantService(6), and is mandatory=0A= when applicable. Both CMTS and CM report the=0A= =0A= =0A= =0A= Expires August 2003 [Page 45]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= signaled value of the parameter in this case.=0A= =0A= If the referenced parameter is not applicable to=0A= the direction or scheduling type of the=0A= corresponding DOCSIS QOS Parameter Set, both=0A= CMTS and CM report this object's value as 0.=0A= "=0A= =0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.7"=0A= ::=3D { docsQosParamSetEntry 18 }=0A= =0A= docsQosParamSetTolGrantJitter OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the maximum amount of time in=0A= microseconds that the transmission opportunities=0A= may be delayed from the nominal periodic = schedule.=0A= =0A= The referenced parameter is applicable only=0A= for upstream flows with a SchedulingType of=0A= of unsolicitedGrantServicewithAD(5) or=0A= unsolicitedGrantService(6), and is mandatory=0A= when applicable. Both CMTS and CM report the=0A= signaled value of the parameter in this case.=0A= =0A= If the referenced parameter is not applicable to=0A= the direction or scheduling type of the=0A= corresponding DOCSIS QOS Parameter Set, both=0A= CMTS and CM report this object's value as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.8"=0A= ::=3D { docsQosParamSetEntry 19 }=0A= =0A= docsQosParamSetGrantsPerInterval OBJECT-TYPE=0A= SYNTAX Integer32 (0..127)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the number of data grants per Nominal=0A= Grant Interval=0A= (docsQosParamSetNomGrantInterval).=0A= =0A= The referenced parameter is applicable only=0A= for upstream flows with a SchedulingType of=0A= of unsolicitedGrantServicewithAD(5) or=0A= unsolicitedGrantService(6), and is mandatory=0A= when applicable. Both CMTS and CM report the=0A= signaled value of the parameter in this case.=0A= =0A= If the referenced parameter is not applicable to=0A= =0A= =0A= =0A= Expires August 2003 [Page 46]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= the direction or scheduling type of the=0A= corresponding DOCSIS QOS Parameter Set, both=0A= CMTS and CM report this object's value as 0.=0A= "=0A= =0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.9"=0A= ::=3D { docsQosParamSetEntry 20 }=0A= =0A= docsQosParamSetTosAndMask OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(1))=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the AND mask for IP TOS byte for = overwriting=0A= IP packets TOS value. The IP packets TOS byte = is=0A= bitwise ANDed with docsQosParamSetTosAndMask and=0A= result is bitwise ORed with = docsQosParamSetTosORMask=0A= and result is written to IP packet TOS byte.=0A= A value of 'FF'H for docsQosParamSetTosAndMask = and=0A= a value of '00'H for docsQosParamSetTosOrMask = means=0A= that IP Packet TOS byte is not overwritten.=0A= =0A= Even though the this object is only enforced by = the=0A= Cable Modem Termination System (CMTS),=0A= Cable Modems must report the value as signaled = in=0A= the referenced parameter.=0A= =0A= This combination is reported if the referenced=0A= parameter is not present in a QOS Parameter = Set."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.10"=0A= ::=3D { docsQosParamSetEntry 21 }=0A= =0A= docsQosParamSetTosOrMask OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(1))=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the OR mask for IP TOS byte.=0A= See the description of docsQosParamSetTosAndMask=0A= for further details."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.10"=0A= ::=3D { docsQosParamSetEntry 22 }=0A= =0A= docsQosParamSetMaxLatency OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the maximum latency between the=0A= reception of a packet by the CMTS on its NSI=0A= and the forwarding of the packet to the RF=0A= interface. A value of 0 signifies no maximum=0A= latency enforced. This object only applies to=0A= =0A= =0A= =0A= Expires August 2003 [Page 47]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= downstream service flows.=0A= =0A= If the referenced parameter is not present in = the=0A= corresponding downstream DOCSIS QOS Parameter = Set,=0A= the default value is 0. This parameter is=0A= not applicable to upstream DOCSIS QOS Parameter = Sets,=0A= and its value is reported as 0 in this case.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.7.1"=0A= ::=3D { docsQosParamSetEntry 23 }=0A= =0A= =0A= docsQosParamSetType OBJECT-TYPE=0A= SYNTAX INTEGER {=0A= active (1),=0A= admitted (2),=0A= provisioned (3)=0A= }=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Defines the type of the QOS parameter set = defined=0A= by this row. active(1) indicates the Active QOS=0A= parameter set, describing the service currently=0A= being provided by the Docsis MAC domain to the=0A= service flow. admitted(2) indicates the Admitted=0A= QOS Parameter Set, describing services reserved = by=0A= by the Docsis MAC domain for use by the service = flow.=0A= provisioned (3) describes the QOS Parameter Set=0A= defined in the DOCSIS CM Configuration file for=0A= the service flow."=0A= REFERENCE "SP-RFIv1.1-I09-020830, 8.1.5"=0A= ::=3D { docsQosParamSetEntry 24 }=0A= =0A= docsQosParamSetRequestPolicyOct OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(4))=0A= -- A 32-bit mask represented most significant = byte=0A= -- first. The 32 bit integer represented in this = manner=0A= -- equals the binary value of the referenced = integer=0A= -- parameter of the DOCSIS RFI specification.=0A= -- The BITS syntax is not used in order to avoid=0A= -- the confusion caused by different bit = numbering=0A= -- conventions.=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies which transmit interval opportunities=0A= the CM omits for upstream transmission requests = and=0A= packet transmissions. This object takes its=0A= default value for downstream service flows.=0A= =0A= Unless otherwise indicated, a bit value of 1 = means=0A= that a CM must *not* use that opportunity for=0A= =0A= =0A= =0A= Expires August 2003 [Page 48]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= upstream transmission.=0A= =0A= Calling bit 0 the least significant bit of the=0A= least significant (4th) octet, and increasing=0A= bit number with significance, the bit = definitions=0A= are as defined below:=0A= =0A= broadcastReqOpp(0):=0A= all CMs broadcast request opportunities=0A= =0A= priorityReqMulticastReq(1):=0A= priority request multicast request = opportunities=0A= =0A= reqDataForReq(2):=0A= request/data opportunities for requests=0A= =0A= reqDataForData(3):=0A= request/data opportunities for data=0A= =0A= piggybackReqWithData(4):=0A= piggyback requests with data=0A= =0A= concatenateData(5):=0A= concatenate data=0A= =0A= fragmentData(6):=0A= fragment data=0A= =0A= suppresspayloadheaders(7):=0A= suppress payload headers=0A= =0A= dropPktsExceedUGSize(8):=0A= A value of 1 mean that service flow must = drop=0A= packet that do not fit in the Unsolicited=0A= Grant size=0A= =0A= If the referenced parameter is not present in=0A= a QOS Parameter Set, the value of this object is=0A= reported as '00000000'H.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.3"=0A= ::=3D { docsQosParamSetEntry 25 }=0A= =0A= docsQosParamSetBitMap OBJECT-TYPE=0A= -- Each bit corresponds to a = parameter=0A= -- from SP-RFI-v1.1-I07-010829, = Appendix C=0A= SYNTAX BITS { -- in the indicated section number.=0A= trafficPriority(0), -- C.2.2.5.1=0A= maxTrafficRate(1), -- C.2.2.5.2=0A= maxTrafficBurst(2), -- C.2.2.5.3=0A= minReservedRate(3), -- C.2.2.5.4=0A= =0A= =0A= =0A= Expires August 2003 [Page 49]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= minReservedPkt(4), -- C.2.2.5.5=0A= activeTimeout(5), -- C.2.2.5.6=0A= admittedTimeout(6), -- C.2.2.5.7=0A= maxConcatBurst(7), -- C.2.2.6.1=0A= schedulingType(8), -- C.2.2.6.2=0A= requestPolicy(9), -- C.2.2.6.3=0A= nomPollInterval(10), -- C.2.2.6.4=0A= tolPollJitter(11), -- C.2.2.6.5=0A= unsolicitGrantSize(12), -- C.2.2.6.6=0A= nomGrantInterval(13), -- C.2.2.6.7=0A= tolGrantJitter(14), -- C.2.2.6.8=0A= grantsPerInterval(15), -- C.2.2.6.9=0A= tosOverwrite(16), -- C.2.2.6.10=0A= maxLatency(17) -- C.2.2.7.1=0A= }=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object indicates the set of QOS Parameter=0A= Set parameters actually signaled in the=0A= DOCSIS registration or dynamic service request=0A= message that created or modified the QOS Parameter = Set.=0A= A bit is set to 1 when the parameter described=0A= by the indicated reference section is present=0A= in the original request.=0A= =0A= Note that when Service Class names are expanded,=0A= the registration or dynamic response message may=0A= contain parameters as expanded by the CMTS based=0A= on a stored service class. These expanded=0A= parameters are *not* indicated by a 1 bit in = this=0A= object.=0A= =0A= Note that even though some QOS Parameter Set=0A= parameters may not be signaled in a message=0A= (so that the paramater's bit in this object is = 0)=0A= the DOCSIS specification calls for default=0A= values to be used. These default values are=0A= reported as the corresponding object's value in=0A= the row.=0A= =0A= Note that BITS objects are encoded most=0A= significant bit first. For example, if bits=0A= 1 and 16 are set, the value of this object=0A= is the octet string '400080'H.=0A= =0A= "=0A= ::=3D { docsQosParamSetEntry 26 }=0A= =0A= --=0A= -- Service Flow Table=0A= --=0A= =0A= =0A= =0A= Expires August 2003 [Page 50]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosServiceFlowTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosServiceFlowEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table describes the set of Docsis-QOS=0A= Service Flows in a managed device. "=0A= ::=3D { docsQosMIBObjects 3 }=0A= =0A= docsQosServiceFlowEntry OBJECT-TYPE=0A= SYNTAX DocsQosServiceFlowEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Describes a service flow.=0A= An entry in the table exists for each=0A= Service Flow ID. The ifIndex is an=0A= ifType of docsCableMaclayer(127)."=0A= INDEX {=0A= ifIndex,=0A= docsQosServiceFlowId=0A= }=0A= ::=3D { docsQosServiceFlowTable 1 }=0A= =0A= DocsQosServiceFlowEntry ::=3D SEQUENCE {=0A= docsQosServiceFlowId Unsigned32,=0A= docsQosServiceFlowSID Unsigned32,=0A= docsQosServiceFlowDirection IfDirection,=0A= docsQosServiceFlowPrimary TruthValue=0A= }=0A= =0A= docsQosServiceFlowId OBJECT-TYPE=0A= SYNTAX Unsigned32 (1..4294967295)=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "An index assigned to a service flow by CMTS."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.3.2"=0A= ::=3D { docsQosServiceFlowEntry 1 }=0A= =0A= docsQosServiceFlowSID OBJECT-TYPE=0A= SYNTAX Unsigned32 (0..16383)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Service Identifier (SID) assigned to an=0A= admitted or active service flow. This object=0A= reports a value of 0 if a Service Id is not=0A= associated with the service flow. Only active=0A= or admitted upstream service flows will have a=0A= Service Id (SID)."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.3.3"=0A= ::=3D { docsQosServiceFlowEntry 2 }=0A= =0A= docsQosServiceFlowDirection OBJECT-TYPE=0A= =0A= =0A= =0A= Expires August 2003 [Page 51]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= SYNTAX IfDirection=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The direction of the service flow."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.1/2"=0A= ::=3D { docsQosServiceFlowEntry 3 }=0A= =0A= docsQosServiceFlowPrimary OBJECT-TYPE=0A= SYNTAX TruthValue=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Object reflects whether service flow is the = primary=0A= or a secondary service flow.=0A= =0A= A primary service flow is the default service = flow=0A= for otherwise unclassified traffic and all MAC=0A= messages."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Section 8.1 "=0A= ::=3D { docsQosServiceFlowEntry 4 }=0A= =0A= --=0A= -- Service Flow Stats Table=0A= --=0A= docsQosServiceFlowStatsTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosServiceFlowStatsEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table describes statistics associated with = the=0A= Service Flows in a managed device. "=0A= ::=3D { docsQosMIBObjects 4 }=0A= =0A= docsQosServiceFlowStatsEntry OBJECT-TYPE=0A= SYNTAX DocsQosServiceFlowStatsEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Describes a set of service flow statistics.=0A= An entry in the table exists for each=0A= Service Flow ID. The ifIndex is an=0A= ifType of docsCableMaclayer(127)."=0A= INDEX {=0A= ifIndex,=0A= docsQosServiceFlowId=0A= }=0A= ::=3D { docsQosServiceFlowStatsTable 1 }=0A= =0A= DocsQosServiceFlowStatsEntry ::=3D SEQUENCE {=0A= docsQosServiceFlowPkts Counter64,=0A= docsQosServiceFlowOctets Counter64,=0A= docsQosServiceFlowTimeCreated TimeStamp,=0A= docsQosServiceFlowTimeActive Counter32,=0A= docsQosServiceFlowPHSUnknowns Counter32,=0A= =0A= =0A= =0A= Expires August 2003 [Page 52]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosServiceFlowPolicedDropPkts Counter32,=0A= docsQosServiceFlowPolicedDelayPkts Counter32=0A= }=0A= =0A= docsQosServiceFlowPkts OBJECT-TYPE=0A= SYNTAX Counter64=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Packet Data PDUs classified to = this=0A= service flow and forwarded beyond a service flow=0A= maximum rate policing function.=0A= This object does not count MAC-specific=0A= management messages.=0A= CMs not classifying downstream packets may = report=0A= this object's value as 0.=0A= =0A= Particularly for UGS flows, packets sent on the=0A= primary service flow in violation of the UGS = grant=0A= size should be counted only on the primary = service=0A= flow's counters.=0A= =0A= Unclassified upstream user data packets (i.e. = non=0A= MAC-management) forwarded to the default = upstream=0A= service flow should be incremented for this = object.=0A= =0A= This object does include packets counted by=0A= docsQosServiceFlowPolicedDelayPkts, but does not = include=0A= packets counted by = docsQosServiceFlowPolicedDropPkts."=0A= ::=3D { docsQosServiceFlowStatsEntry 1 }=0A= =0A= docsQosServiceFlowOctets OBJECT-TYPE=0A= SYNTAX Counter64=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of octets from the byte after the MAC=0A= header HCS to the end of the CRC for all packets = counted=0A= in the docsQosServiceFlowPkts object for this = row.=0A= Note that this counts the octets after payload = header=0A= suppression has been applied. CMs not classifying = to a=0A= downstream service flow may report this object's=0A= value as 0 for that flow."=0A= ::=3D { docsQosServiceFlowStatsEntry 2 }=0A= =0A= docsQosServiceFlowTimeCreated OBJECT-TYPE=0A= SYNTAX TimeStamp=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The value of sysUpTime when the service flow=0A= was created."=0A= ::=3D { docsQosServiceFlowStatsEntry 3 }=0A= =0A= =0A= =0A= =0A= Expires August 2003 [Page 53]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosServiceFlowTimeActive OBJECT-TYPE=0A= SYNTAX Counter32=0A= UNITS "seconds"=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The total time that service flow has been = active."=0A= ::=3D { docsQosServiceFlowStatsEntry 4 }=0A= =0A= docsQosServiceFlowPHSUnknowns OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of packets received on the service = flow=0A= with an unknown payload header suppression = index."=0A= ::=3D { docsQosServiceFlowStatsEntry 5 }=0A= =0A= docsQosServiceFlowPolicedDropPkts OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Packet Data PDUs classified to = this=0A= service flow dropped due to:=0A= (1) implementation-dependent excessive delay = while=0A= enforcing the Maximum Sustained Traffic = Rate; or=0A= (2) UGS packets dropped due to exceeding the=0A= Unsolicited Grant Size with a=0A= Request/Transmission policy that requires = such=0A= packets to be dropped.=0A= Classified packets dropped due to other reasons = must be=0A= counted in ifOutDiscards for interface of this=0A= service flow."=0A= ::=3D { docsQosServiceFlowStatsEntry 6 }=0A= =0A= docsQosServiceFlowPolicedDelayPkts OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object counts only packets delayed in order = to=0A= maintain the Maximum Sustained Traffic Rate. This = object=0A= will always report a value of 0 for UGS flows = because the=0A= Maximum Sustained Traffic Rate does not apply."=0A= ::=3D { docsQosServiceFlowStatsEntry 7 }=0A= =0A= --=0A= -- Upstream Service Flow Stats Table (CMTS ONLY)=0A= --=0A= docsQosUpstreamStatsTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosUpstreamStatsEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table describes statistics associated with=0A= =0A= =0A= =0A= Expires August 2003 [Page 54]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= upstream service flows. All counted frames must=0A= be received without an FCS error."=0A= ::=3D { docsQosMIBObjects 5 }=0A= =0A= docsQosUpstreamStatsEntry OBJECT-TYPE=0A= SYNTAX DocsQosUpstreamStatsEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Describes a set of upstream service flow = statistics.=0A= An entry in the table exists for each=0A= upstream Service Flow in a managed device.=0A= The ifIndex is an ifType of = docsCableMaclayer(127)."=0A= INDEX {=0A= ifIndex,=0A= docsQosSID=0A= }=0A= ::=3D { docsQosUpstreamStatsTable 1 }=0A= =0A= DocsQosUpstreamStatsEntry ::=3D SEQUENCE {=0A= docsQosSID Integer32,=0A= docsQosUpstreamFragments Counter32,=0A= docsQosUpstreamFragDiscards Counter32,=0A= docsQosUpstreamConcatBursts Counter32=0A= }=0A= =0A= docsQosSID OBJECT-TYPE=0A= SYNTAX Integer32 (1..16383)=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Identifies a service id for an admitted or = active=0A= upstream service flow."=0A= ::=3D { docsQosUpstreamStatsEntry 1 }=0A= =0A= docsQosUpstreamFragments OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of fragmentation headers received on = an=0A= upstream service flow, regardless of whether=0A= the fragment was correctly reassembled into a=0A= valid packet. "=0A= ::=3D { docsQosUpstreamStatsEntry 2 }=0A= =0A= docsQosUpstreamFragDiscards OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of upstream fragments discarded and = not=0A= assembled into a valid upstream packet."=0A= ::=3D { docsQosUpstreamStatsEntry 3 }=0A= =0A= =0A= =0A= =0A= Expires August 2003 [Page 55]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosUpstreamConcatBursts OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of concatenation headers received on = an=0A= upstream service flow."=0A= ::=3D { docsQosUpstreamStatsEntry 4 }=0A= =0A= =0A= --=0A= -- Dynamic Service Stats Table=0A= --=0A= docsQosDynamicServiceStatsTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosDynamicServiceStatsEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table describes statistics associated with = the=0A= Dynamic Service Flows in a managed device. "=0A= ::=3D { docsQosMIBObjects 6 }=0A= =0A= docsQosDynamicServiceStatsEntry OBJECT-TYPE=0A= SYNTAX DocsQosDynamicServiceStatsEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Describes a set of dynamic service flow = statistics.=0A= Two entries exist for each Docsis mac layer=0A= interface for the upstream and downstream = direction.=0A= On the CMTS, the downstream direction row = indicates=0A= messages transmitted or transactions originated=0A= by the CMTS. The upstream direction row = indicates=0A= messages received or transaction originated by = the=0A= CM. On the CM, the downstream direction row=0A= indicates messages received or transactions=0A= originated by the CMTS. The upstream direction=0A= row indicates messages transmitted by the CM or=0A= transactions originated by the CM.=0A= The ifIndex is an ifType of = docsCableMaclayer(127)."=0A= INDEX {=0A= ifIndex,=0A= docsQosIfDirection=0A= }=0A= ::=3D { docsQosDynamicServiceStatsTable 1 }=0A= =0A= DocsQosDynamicServiceStatsEntry ::=3D SEQUENCE {=0A= docsQosIfDirection IfDirection,=0A= docsQosDSAReqs Counter32,=0A= docsQosDSARsps Counter32,=0A= docsQosDSAAcks Counter32,=0A= docsQosDSCReqs Counter32,=0A= docsQosDSCRsps Counter32,=0A= docsQosDSCAcks Counter32,=0A= =0A= =0A= =0A= Expires August 2003 [Page 56]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosDSDReqs Counter32,=0A= docsQosDSDRsps Counter32,=0A= docsQosDynamicAdds Counter32,=0A= docsQosDynamicAddFails Counter32,=0A= docsQosDynamicChanges Counter32,=0A= docsQosDynamicChangeFails Counter32,=0A= docsQosDynamicDeletes Counter32,=0A= docsQosDynamicDeleteFails Counter32,=0A= docsQosDCCReqs Counter32,=0A= docsQosDCCRsps Counter32,=0A= docsQosDCCAcks Counter32,=0A= docsQosDCCs Counter32,=0A= docsQosDCCFails Counter32=0A= }=0A= =0A= docsQosIfDirection OBJECT-TYPE=0A= SYNTAX IfDirection=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "The direction of interface."=0A= ::=3D { docsQosDynamicServiceStatsEntry 1 }=0A= =0A= docsQosDSAReqs OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Service Addition Requests,=0A= including retries."=0A= ::=3D { docsQosDynamicServiceStatsEntry 2 }=0A= =0A= docsQosDSARsps OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Service Addition = Responses,=0A= including retries."=0A= ::=3D { docsQosDynamicServiceStatsEntry 3 }=0A= =0A= docsQosDSAAcks OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Service Addition = Acknowledgements,=0A= including retries."=0A= ::=3D { docsQosDynamicServiceStatsEntry 4 }=0A= =0A= docsQosDSCReqs OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Service Change Requests,=0A= =0A= =0A= =0A= Expires August 2003 [Page 57]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= including retries."=0A= ::=3D { docsQosDynamicServiceStatsEntry 5 }=0A= =0A= docsQosDSCRsps OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Service Change Responses,=0A= including retries."=0A= ::=3D { docsQosDynamicServiceStatsEntry 6 }=0A= =0A= docsQosDSCAcks OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Service Change = Acknowledgements,=0A= including retries."=0A= ::=3D { docsQosDynamicServiceStatsEntry 7 }=0A= =0A= docsQosDSDReqs OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Service Delete Requests,=0A= including retries."=0A= ::=3D { docsQosDynamicServiceStatsEntry 8 }=0A= =0A= docsQosDSDRsps OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Service Delete Responses,=0A= including retries."=0A= ::=3D { docsQosDynamicServiceStatsEntry 9 }=0A= =0A= docsQosDynamicAdds OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of successful Dynamic Service = Addition=0A= transactions."=0A= ::=3D { docsQosDynamicServiceStatsEntry 10 }=0A= =0A= docsQosDynamicAddFails OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of failed Dynamic Service Addition=0A= transactions."=0A= ::=3D { docsQosDynamicServiceStatsEntry 11 }=0A= =0A= =0A= =0A= =0A= Expires August 2003 [Page 58]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosDynamicChanges OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of successful Dynamic Service Change=0A= transactions."=0A= ::=3D { docsQosDynamicServiceStatsEntry 12 }=0A= =0A= docsQosDynamicChangeFails OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of failed Dynamic Service Change=0A= transactions."=0A= ::=3D { docsQosDynamicServiceStatsEntry 13 }=0A= =0A= docsQosDynamicDeletes OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of successful Dynamic Service Delete=0A= transactions."=0A= ::=3D { docsQosDynamicServiceStatsEntry 14 }=0A= =0A= docsQosDynamicDeleteFails OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of failed Dynamic Service Delete=0A= transactions."=0A= ::=3D { docsQosDynamicServiceStatsEntry 15 }=0A= =0A= =0A= docsQosDCCReqs OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Channel Change Request = messages=0A= traversing an interface. This count is nonzero only = on=0A= downstream direction rows. This count should=0A= include number of retries."=0A= ::=3D { docsQosDynamicServiceStatsEntry 16 }=0A= =0A= docsQosDCCRsps OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Channel Change Response = messages=0A= traversing an interface. This count is nonzero=0A= only on upstream direction rows. This count = should=0A= include number of retries."=0A= =0A= =0A= =0A= Expires August 2003 [Page 59]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= ::=3D { docsQosDynamicServiceStatsEntry 17 }=0A= =0A= docsQosDCCAcks OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Channel Change = Acknowledgement=0A= messages traversing an interface. This count=0A= is nonzero only on downstream direction rows.=0A= This count should include number of retries."=0A= ::=3D { docsQosDynamicServiceStatsEntry 18 }=0A= =0A= docsQosDCCs OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of successful Dynamic Channel Change=0A= transactions. This count is nonzero only on = downstream=0A= direction rows."=0A= ::=3D { docsQosDynamicServiceStatsEntry 19 }=0A= =0A= docsQosDCCFails OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of failed Dynamic Channel Change=0A= transactions. This count is nonzero only on=0A= downstream direction rows."=0A= ::=3D { docsQosDynamicServiceStatsEntry 20 }=0A= =0A= =0A= --=0A= -- Service Flow Log Table (CMTS ONLY)=0A= --=0A= docsQosServiceFlowLogTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosServiceFlowLogEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table contains a log of the disconnected=0A= Service Flows in a managed device."=0A= ::=3D { docsQosMIBObjects 7 }=0A= =0A= docsQosServiceFlowLogEntry OBJECT-TYPE=0A= SYNTAX DocsQosServiceFlowLogEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "The information regarding a single disconnected=0A= service flow."=0A= INDEX {=0A= docsQosServiceFlowLogIndex=0A= }=0A= =0A= =0A= =0A= Expires August 2003 [Page 60]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= ::=3D { docsQosServiceFlowLogTable 1 }=0A= =0A= DocsQosServiceFlowLogEntry ::=3D SEQUENCE {=0A= docsQosServiceFlowLogIndex Unsigned32,=0A= docsQosServiceFlowLogIfIndex InterfaceIndex,=0A= docsQosServiceFlowLogSFID Unsigned32,=0A= docsQosServiceFlowLogCmMac MacAddress,=0A= docsQosServiceFlowLogPkts Counter64,=0A= docsQosServiceFlowLogOctets Counter64,=0A= docsQosServiceFlowLogTimeDeleted TimeStamp,=0A= docsQosServiceFlowLogTimeCreated TimeStamp,=0A= docsQosServiceFlowLogTimeActive Counter32,=0A= docsQosServiceFlowLogDirection IfDirection,=0A= docsQosServiceFlowLogPrimary TruthValue,=0A= docsQosServiceFlowLogServiceClassName DisplayString,=0A= docsQosServiceFlowLogPolicedDropPkts Counter32,=0A= docsQosServiceFlowLogPolicedDelayPkts Counter32,=0A= docsQosServiceFlowLogControl INTEGER=0A= }=0A= =0A= docsQosServiceFlowLogIndex OBJECT-TYPE=0A= SYNTAX Unsigned32 (1..4294967295)=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Unique index for a logged service flow."=0A= ::=3D { docsQosServiceFlowLogEntry 1 }=0A= =0A= docsQosServiceFlowLogIfIndex OBJECT-TYPE=0A= SYNTAX InterfaceIndex=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The ifIndex of ifType docsCableMaclayer(127)=0A= on the CMTS where the service flow was = present."=0A= ::=3D { docsQosServiceFlowLogEntry 2 }=0A= =0A= docsQosServiceFlowLogSFID OBJECT-TYPE=0A= SYNTAX Unsigned32 (1..4294967295)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The index assigned to the service flow by the = CMTS."=0A= ::=3D { docsQosServiceFlowLogEntry 3 }=0A= =0A= docsQosServiceFlowLogCmMac OBJECT-TYPE=0A= SYNTAX MacAddress=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The MAC address for the cable modem associated = with=0A= the service flow."=0A= ::=3D { docsQosServiceFlowLogEntry 4 }=0A= =0A= docsQosServiceFlowLogPkts OBJECT-TYPE=0A= =0A= =0A= =0A= Expires August 2003 [Page 61]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= SYNTAX Counter64=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of packets counted on this service = flow=0A= after payload header suppression."=0A= ::=3D { docsQosServiceFlowLogEntry 5 }=0A= =0A= docsQosServiceFlowLogOctets OBJECT-TYPE=0A= SYNTAX Counter64=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of octets counted on this service = flow=0A= after payload header suppression."=0A= ::=3D { docsQosServiceFlowLogEntry 6 }=0A= =0A= docsQosServiceFlowLogTimeDeleted OBJECT-TYPE=0A= SYNTAX TimeStamp=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The value of sysUpTime when the service flow=0A= was deleted."=0A= ::=3D { docsQosServiceFlowLogEntry 7 }=0A= =0A= docsQosServiceFlowLogTimeCreated OBJECT-TYPE=0A= SYNTAX TimeStamp=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The value of sysUpTime when the service flow=0A= was created."=0A= ::=3D { docsQosServiceFlowLogEntry 8 }=0A= =0A= docsQosServiceFlowLogTimeActive OBJECT-TYPE=0A= SYNTAX Counter32=0A= UNITS "seconds"=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The total time that service flow was active."=0A= ::=3D { docsQosServiceFlowLogEntry 9 }=0A= =0A= docsQosServiceFlowLogDirection OBJECT-TYPE=0A= SYNTAX IfDirection=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The value of docsQosServiceFlowDirection=0A= for the service flow."=0A= ::=3D { docsQosServiceFlowLogEntry 10 }=0A= =0A= docsQosServiceFlowLogPrimary OBJECT-TYPE=0A= SYNTAX TruthValue=0A= MAX-ACCESS read-only=0A= STATUS current=0A= =0A= =0A= =0A= Expires August 2003 [Page 62]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= DESCRIPTION "The value of docsQosServiceFlowPrimary for the=0A= service flow."=0A= ::=3D { docsQosServiceFlowLogEntry 11 }=0A= =0A= docsQosServiceFlowLogServiceClassName OBJECT-TYPE=0A= SYNTAX DisplayString=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The value of docsQosParamSetServiceClassName for=0A= the provisioned QOS Parameter Set of the=0A= service flow."=0A= ::=3D { docsQosServiceFlowLogEntry 12 }=0A= =0A= docsQosServiceFlowLogPolicedDropPkts OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The final value of = docsQosServiceFlowPolicedDropPkts=0A= for the service flow."=0A= ::=3D { docsQosServiceFlowLogEntry 13 }=0A= =0A= docsQosServiceFlowLogPolicedDelayPkts OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The final value of = docsQosServiceFlowPolicedDelayPkts=0A= for the service flow."=0A= ::=3D { docsQosServiceFlowLogEntry 14 }=0A= =0A= docsQosServiceFlowLogControl OBJECT-TYPE=0A= SYNTAX INTEGER {=0A= active(1),=0A= destroy(6)=0A= }=0A= =0A= MAX-ACCESS read-write=0A= STATUS current=0A= DESCRIPTION "Setting this object to the value destroy(6) = removes=0A= this entry from the table.=0A= Reading this object return the value active(1)."=0A= ::=3D { docsQosServiceFlowLogEntry 15 }=0A= =0A= --=0A= -- Service Class Table (CMTS ONLY)=0A= --=0A= docsQosServiceClassTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosServiceClassEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table describes the set of Docsis-QOS=0A= Service Classes in a CMTS. "=0A= =0A= =0A= =0A= Expires August 2003 [Page 63]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= ::=3D { docsQosMIBObjects 8 }=0A= =0A= docsQosServiceClassEntry OBJECT-TYPE=0A= SYNTAX DocsQosServiceClassEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "A provisioned service class on a CMTS.=0A= Each entry defines a template for certain=0A= DOCSIS QOS Parameter Set values. When a CM=0A= creates or modifies an Admitted QOS Parameter Set for = a=0A= Service Flow, it may reference a Service Class=0A= Name instead of providing explicit QOS Parameter=0A= Set values. In this case, the CMTS populates=0A= the QOS Parameter Set with the applicable=0A= corresponding values from the named Service Class.=0A= Subsequent changes to a Service Class row do *not*=0A= affect the QOS Parameter Set values of any service = flows=0A= already admitted.=0A= =0A= A service class template applies to only=0A= a single direction, as indicated in the=0A= docsQosServiceClassDirection object.=0A= "=0A= INDEX {=0A= docsQosServiceClassName=0A= }=0A= ::=3D { docsQosServiceClassTable 1 }=0A= =0A= DocsQosServiceClassEntry ::=3D SEQUENCE {=0A= docsQosServiceClassName DisplayString,=0A= docsQosServiceClassStatus RowStatus,=0A= docsQosServiceClassPriority Integer32,=0A= docsQosServiceClassMaxTrafficRate BitRate,=0A= docsQosServiceClassMaxTrafficBurst Unsigned32,=0A= docsQosServiceClassMinReservedRate BitRate,=0A= docsQosServiceClassMinReservedPkt Integer32,=0A= docsQosServiceClassMaxConcatBurst Integer32,=0A= docsQosServiceClassNomPollInterval Unsigned32,=0A= docsQosServiceClassTolPollJitter Unsigned32,=0A= docsQosServiceClassUnsolicitGrantSize Integer32,=0A= docsQosServiceClassNomGrantInterval Unsigned32,=0A= docsQosServiceClassTolGrantJitter Unsigned32,=0A= docsQosServiceClassGrantsPerInterval Integer32,=0A= docsQosServiceClassMaxLatency Unsigned32,=0A= docsQosServiceClassActiveTimeout Integer32,=0A= docsQosServiceClassAdmittedTimeout Integer32,=0A= docsQosServiceClassSchedulingType SchedulingType,=0A= docsQosServiceClassRequestPolicy OCTET STRING,=0A= docsQosServiceClassTosAndMask OCTET STRING,=0A= docsQosServiceClassTosOrMask OCTET STRING,=0A= docsQosServiceClassDirection IfDirection=0A= =0A= =0A= =0A= Expires August 2003 [Page 64]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= }=0A= =0A= docsQosServiceClassName OBJECT-TYPE=0A= SYNTAX DisplayString (SIZE(1..15))=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Service Class Name. DOCSIS specifies that the=0A= maximum size is 15 printable ASCII characters = with=0A= a terminating zero. The terminating zero is not=0A= represented in this DisplayString syntax object.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.3.4"=0A= ::=3D { docsQosServiceClassEntry 1 }=0A= =0A= docsQosServiceClassStatus OBJECT-TYPE=0A= SYNTAX RowStatus=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Used to create or delete rows in this table.=0A= There is no restriction on the ability=0A= to change values in this row while the row is = active.=0A= Inactive rows need not be timed out."=0A= ::=3D { docsQosServiceClassEntry 2 }=0A= =0A= docsQosServiceClassPriority OBJECT-TYPE=0A= SYNTAX Integer32 (0..7)=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetPriority."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 3 }=0A= =0A= docsQosServiceClassMaxTrafficRate OBJECT-TYPE=0A= SYNTAX BitRate=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetMaxTrafficRate."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 4 }=0A= =0A= docsQosServiceClassMaxTrafficBurst OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetMaxTrafficBurst."=0A= DEFVAL { 3044 }=0A= ::=3D { docsQosServiceClassEntry 5 }=0A= =0A= docsQosServiceClassMinReservedRate OBJECT-TYPE=0A= SYNTAX BitRate=0A= MAX-ACCESS read-create=0A= =0A= =0A= =0A= Expires August 2003 [Page 65]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSEtMinReservedRate."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 6 }=0A= =0A= docsQosServiceClassMinReservedPkt OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetMinReservedPkt."=0A= ::=3D { docsQosServiceClassEntry 7 }=0A= =0A= docsQosServiceClassMaxConcatBurst OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetMaxConcatBurst."=0A= DEFVAL { 1522 }=0A= ::=3D { docsQosServiceClassEntry 8 }=0A= =0A= docsQosServiceClassNomPollInterval OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetNomPollInterval."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 9 }=0A= =0A= docsQosServiceClassTolPollJitter OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetTolPollJitter."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 10 }=0A= =0A= docsQosServiceClassUnsolicitGrantSize OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetUnsolicitGrantSize."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 11 }=0A= =0A= docsQosServiceClassNomGrantInterval OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-create=0A= STATUS current=0A= =0A= =0A= =0A= Expires August 2003 [Page 66]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= DESCRIPTION "Template for docsQosParamSetNomGrantInterval."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 12 }=0A= =0A= docsQosServiceClassTolGrantJitter OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetTolGrantJitter."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 13 }=0A= =0A= docsQosServiceClassGrantsPerInterval OBJECT-TYPE=0A= SYNTAX Integer32 (0..127)=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetGrantsPerInterval."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 14 }=0A= =0A= docsQosServiceClassMaxLatency OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetClassMaxLatency."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.7.1"=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 15 }=0A= =0A= docsQosServiceClassActiveTimeout OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= UNITS "seconds"=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetActiveTimeout."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 16 }=0A= =0A= docsQosServiceClassAdmittedTimeout OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= UNITS "seconds"=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetAdmittedTimeout."=0A= DEFVAL { 200 }=0A= ::=3D { docsQosServiceClassEntry 17 }=0A= =0A= docsQosServiceClassSchedulingType OBJECT-TYPE=0A= SYNTAX SchedulingType=0A= =0A= =0A= =0A= Expires August 2003 [Page 67]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetSchedulingType."=0A= DEFVAL { bestEffort }=0A= ::=3D { docsQosServiceClassEntry 18 }=0A= =0A= docsQosServiceClassRequestPolicy OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(4))=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetRequestPolicyOct."=0A= DEFVAL { '00000000'H } -- no bits are set=0A= ::=3D { docsQosServiceClassEntry 19 }=0A= =0A= docsQosServiceClassTosAndMask OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(1))=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetTosAndMask."=0A= DEFVAL { 'FF'H }=0A= ::=3D { docsQosServiceClassEntry 20 }=0A= =0A= docsQosServiceClassTosOrMask OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(1))=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetTosOrMask."=0A= DEFVAL { '00'H }=0A= ::=3D { docsQosServiceClassEntry 21 }=0A= =0A= docsQosServiceClassDirection OBJECT-TYPE=0A= SYNTAX IfDirection=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Specifies whether the service class template=0A= applies to upstream or downstream service = flows."=0A= DEFVAL { upstream }=0A= ::=3D { docsQosServiceClassEntry 22 }=0A= =0A= --=0A= -- Service Class PolicyTable=0A= --=0A= docsQosServiceClassPolicyTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosServiceClassPolicyEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table describes the set of Docsis-QOS=0A= Service Class Policies.=0A= =0A= This table is an adjunct to the=0A= docsDevFilterPolicy table. Entries in=0A= =0A= =0A= =0A= Expires August 2003 [Page 68]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsDevFilterPolicy table can point to=0A= specific rows in this table.=0A= =0A= This table permits mapping a packet to a service=0A= class name of an active service flow so long as=0A= a classifier does not exist at a higher=0A= priority.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix E.2.1"=0A= ::=3D { docsQosMIBObjects 9 }=0A= =0A= docsQosServiceClassPolicyEntry OBJECT-TYPE=0A= SYNTAX DocsQosServiceClassPolicyEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "A service class name policy entry."=0A= INDEX {=0A= docsQosServiceClassPolicyIndex=0A= }=0A= ::=3D { docsQosServiceClassPolicyTable 1 }=0A= =0A= DocsQosServiceClassPolicyEntry ::=3D SEQUENCE {=0A= docsQosServiceClassPolicyIndex Integer32,=0A= docsQosServiceClassPolicyName DisplayString,=0A= docsQosServiceClassPolicyRulePriority Integer32,=0A= docsQosServiceClassPolicyStatus RowStatus=0A= }=0A= =0A= docsQosServiceClassPolicyIndex OBJECT-TYPE=0A= SYNTAX Integer32 (1..2147483647)=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Index value to uniquely identify an entry in=0A= this table."=0A= ::=3D { docsQosServiceClassPolicyEntry 1 }=0A= =0A= docsQosServiceClassPolicyName OBJECT-TYPE=0A= SYNTAX DisplayString=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Service Class Name to identify the name of the=0A= service class flow to which the packet should be=0A= directed."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix E.2.1"=0A= ::=3D { docsQosServiceClassPolicyEntry 2 }=0A= =0A= docsQosServiceClassPolicyRulePriority OBJECT-TYPE=0A= SYNTAX Integer32 (0..255)=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Service Class Policy rule priority for the=0A= =0A= =0A= =0A= Expires August 2003 [Page 69]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= entry."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.3.5"=0A= ::=3D { docsQosServiceClassPolicyEntry 3 }=0A= =0A= docsQosServiceClassPolicyStatus OBJECT-TYPE=0A= SYNTAX RowStatus=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Used to create or delete rows in this table.=0A= This object should not be deleted if it is=0A= reference by an entry in docsDevFilterPolicy.=0A= The reference should be deleted first.=0A= There is no restriction on the ability=0A= to change values in this row while the row is = active.=0A= Inactive rows need not be timed out."=0A= ::=3D { docsQosServiceClassPolicyEntry 4 }=0A= =0A= --=0A= -- Payload Header Suppression(PHS) Table=0A= --=0A= docsQosPHSTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosPHSEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table describes set of payload header=0A= suppression entries."=0A= ::=3D { docsQosMIBObjects 10 }=0A= =0A= docsQosPHSEntry OBJECT-TYPE=0A= SYNTAX DocsQosPHSEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "A payload header suppression entry.=0A= The ifIndex is an ifType of = docsCableMaclayer(127).=0A= The index docsQosServiceFlowId selects one=0A= service flow from the cable MAC layer = interface.=0A= The docsQosPktClassId index matches an=0A= index of the docsQosPktClassTable.=0A= "=0A= INDEX {=0A= ifIndex,=0A= docsQosServiceFlowId,=0A= docsQosPktClassId=0A= }=0A= ::=3D { docsQosPHSTable 1 }=0A= =0A= DocsQosPHSEntry ::=3D SEQUENCE {=0A= docsQosPHSField OCTET STRING,=0A= docsQosPHSMask OCTET STRING,=0A= docsQosPHSSize Integer32,=0A= docsQosPHSVerify TruthValue,=0A= =0A= =0A= =0A= Expires August 2003 [Page 70]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosPHSIndex Integer32=0A= }=0A= =0A= -- docsQosPHSIndex { docsQosPHSEntry 1 } was=0A= -- moved to docsQosPHSIndex { docsQosPHSEntry 7 }=0A= -- in an ealier revisions of the mib.=0A= =0A= docsQosPHSField OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(0..255))=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Payload header suppression field defines the=0A= bytes of the header which must be=0A= suppressed/restored by the sending/receiving=0A= device.=0A= =0A= The number of octets in this object should be=0A= the same as the value of docsQosPHSSize."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.10.1"=0A= ::=3D { docsQosPHSEntry 2 }=0A= =0A= docsQosPHSMask OBJECT-TYPE=0A= SYNTAX OCTET STRING(SIZE(0..32))=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Payload header suppression mask defines the=0A= bit mask which used in combination with the=0A= docsQosPHSField defines which bytes in header=0A= must be suppressed/restored by the sending or=0A= receiving device.=0A= =0A= Each bit of this bit mask corresponds to a byte=0A= in the docsQosPHSField, with the least=0A= significant bit corresponding to first byte of=0A= the docsQosPHSField.=0A= =0A= Each bit of the bit mask specifies whether of=0A= not the corresponding byte should be suppressed=0A= in the packet. A bit value of '1' indicates that=0A= the byte should be suppressed by the sending=0A= device and restored by the receiving device.=0A= A bit value of '0' indicates that=0A= the byte should not be suppressed by the sending=0A= device or restored by the receiving device.=0A= =0A= If the bit mask does not contain a bit for each=0A= byte in the docsQosPHSField then the bit mask is=0A= extended with bit values of '1' to be the=0A= necessary length."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.10.3"=0A= ::=3D { docsQosPHSEntry 3 }=0A= =0A= =0A= =0A= Expires August 2003 [Page 71]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosPHSSize OBJECT-TYPE=0A= SYNTAX Integer32 (0..255)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Payload header suppression size specifies the=0A= number of bytes in the header to be suppressed=0A= and restored.=0A= =0A= The value of this object must match the number=0A= of bytes in the docsQosPHSField."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.10.4"=0A= ::=3D { docsQosPHSEntry 4 }=0A= =0A= docsQosPHSVerify OBJECT-TYPE=0A= SYNTAX TruthValue=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Payload header suppression verification value of=0A= 'true' the sender must verify docsQosPHSField=0A= is the same as what is contained in the packet=0A= to be suppressed."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.10.5"=0A= ::=3D { docsQosPHSEntry 5 }=0A= =0A= docsQosPHSIndex OBJECT-TYPE=0A= SYNTAX Integer32 (1..255)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Payload header suppression index uniquely=0A= references the PHS rule for a given service = flow."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.10.2"=0A= ::=3D { docsQosPHSEntry 6 }=0A= =0A= =0A= --=0A= -- docsQosCmtsMacToSrvFlowTable (CMTS Only)=0A= --=0A= docsQosCmtsMacToSrvFlowTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosCmtsMacToSrvFlowEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table provide for referencing the service = flows=0A= associated with a particular cable modem. This = allows=0A= for indexing into other docsQos tables that are=0A= indexed by docsQosServiceFlowId and ifIndex."=0A= ::=3D { docsQosMIBObjects 11 }=0A= =0A= docsQosCmtsMacToSrvFlowEntry OBJECT-TYPE=0A= SYNTAX DocsQosCmtsMacToSrvFlowEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= =0A= =0A= =0A= Expires August 2003 [Page 72]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= DESCRIPTION "An entry is created by CMTS for each service = flow=0A= connected to this CMTS."=0A= INDEX {=0A= docsQosCmtsCmMac,=0A= docsQosCmtsServiceFlowId=0A= }=0A= ::=3D { docsQosCmtsMacToSrvFlowTable 1 }=0A= =0A= DocsQosCmtsMacToSrvFlowEntry ::=3D SEQUENCE {=0A= docsQosCmtsCmMac MacAddress,=0A= docsQosCmtsServiceFlowId Unsigned32,=0A= docsQosCmtsIfIndex InterfaceIndex=0A= }=0A= =0A= docsQosCmtsCmMac OBJECT-TYPE=0A= SYNTAX MacAddress=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "The MAC address for the referenced CM."=0A= ::=3D { docsQosCmtsMacToSrvFlowEntry 1 }=0A= =0A= docsQosCmtsServiceFlowId OBJECT-TYPE=0A= SYNTAX Unsigned32 (1..4294967295)=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "An index assigned to a service flow by CMTS."=0A= ::=3D { docsQosCmtsMacToSrvFlowEntry 2 }=0A= =0A= docsQosCmtsIfIndex OBJECT-TYPE=0A= SYNTAX InterfaceIndex=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The ifIndex of ifType docsCableMacLayter(127)=0A= on the CMTS that is connected to the Cable = Modem."=0A= ::=3D { docsQosCmtsMacToSrvFlowEntry 3 }=0A= =0A= =0A= --=0A= -- Placeholder for notifications/traps.=0A= --=0A= docsQosNotification OBJECT IDENTIFIER ::=3D { docsQosMIB 2 }=0A= =0A= =0A= --=0A= -- Conformance definitions=0A= --=0A= docsQosConformance OBJECT IDENTIFIER ::=3D { docsQosMIB 3 }=0A= docsQosGroups OBJECT IDENTIFIER ::=3D { docsQosConformance 1 = }=0A= docsQosCompliances OBJECT IDENTIFIER ::=3D { docsQosConformance 2 = }=0A= =0A= docsQosCompliance MODULE-COMPLIANCE=0A= =0A= =0A= =0A= Expires August 2003 [Page 73]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= STATUS current=0A= DESCRIPTION=0A= "The compliance statement for MCNS Cable Modems and=0A= Cable Modem Termination Systems that implement DOCSIS=0A= Service Flows."=0A= =0A= MODULE -- docsQosMIB=0A= MANDATORY-GROUPS { docsQosBaseGroup }=0A= =0A= GROUP docsQosCmtsGroup=0A= DESCRIPTION=0A= "This group is mandatory for only Cable Modem = Termination=0A= Systems (CMTS) and not implemented for Cable Modems."=0A= =0A= GROUP docsQosParamSetGroup=0A= DESCRIPTION=0A= "This group is mandatory for Cable Modem Termination=0A= Systems (CMTS) and Cable Modems. Cable modems only = implement=0A= objects in this group as read-only."=0A= =0A= GROUP docsQosSrvClassPolicyGroup=0A= DESCRIPTION=0A= "This group is optional for Cable Modem Termination=0A= Systems (CMTS) and Cable Modems. This group only needs = to=0A= be implement if policy based service flow = classification=0A= is implemented. See docsDevPolicyTable in=0A= DOCS-CABLE-DEVICE-MIB for more details. "=0A= =0A= GROUP docsQosServiceClassGroup=0A= DESCRIPTION=0A= "The docsQosServiceClassTable group of objects."=0A= =0A= OBJECT docsQosPktClassPkts=0A= DESCRIPTION=0A= "This object only needs to be implemented in entries=0A= that are classifying packets and not policing packets."=0A= =0A= OBJECT docsQosPktClassInetSourceAddrType=0A= -- SYNTAX InetAddressType { ipv4(1) }=0A= DESCRIPTION=0A= "An implementation is only required to support IPv4=0A= address."=0A= =0A= OBJECT docsQosPktClassInetSourceAddr=0A= SYNTAX InetAddress (SIZE(4))=0A= DESCRIPTION=0A= "An implementation is only required to support IPv4=0A= address."=0A= =0A= OBJECT docsQosPktClassInetSourceMaskType=0A= -- SYNTAX InetAddressType { ipv4(1) }=0A= =0A= =0A= =0A= Expires August 2003 [Page 74]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= DESCRIPTION=0A= "An implementation is only required to support IPv4=0A= address."=0A= =0A= OBJECT docsQosPktClassInetSourceMask=0A= SYNTAX InetAddress (SIZE(4))=0A= DESCRIPTION=0A= "An implementation is only required to support IPv4=0A= address."=0A= =0A= OBJECT docsQosPktClassInetDestAddrType=0A= -- SYNTAX InetAddressType { ipv4(1) }=0A= DESCRIPTION=0A= "An implementation is only required to support IPv4=0A= address."=0A= =0A= OBJECT docsQosPktClassInetDestAddr=0A= SYNTAX InetAddress (SIZE(4))=0A= DESCRIPTION=0A= "An implementation is only required to support IPv4=0A= address."=0A= =0A= OBJECT docsQosPktClassInetDestMaskType=0A= -- SYNTAX InetAddressType { ipv4(1) }=0A= DESCRIPTION=0A= "An implementation is only required to support IPv4=0A= address."=0A= =0A= OBJECT docsQosPktClassInetDestMask=0A= SYNTAX InetAddress (SIZE(4))=0A= DESCRIPTION=0A= "An implementation is only required to support IPv4=0A= address."=0A= =0A= ::=3D { docsQosCompliances 1 }=0A= =0A= docsQosBaseGroup OBJECT-GROUP=0A= OBJECTS {=0A= docsQosPktClassDirection,=0A= docsQosPktClassPriority,=0A= docsQosPktClassIpTosLow,=0A= docsQosPktClassIpTosHigh,=0A= docsQosPktClassIpTosMask,=0A= docsQosPktClassIpProtocol,=0A= docsQosPktClassSourcePortStart,=0A= docsQosPktClassSourcePortEnd,=0A= docsQosPktClassDestPortStart,=0A= docsQosPktClassDestPortEnd,=0A= docsQosPktClassDestMacAddr,=0A= docsQosPktClassDestMacMask,=0A= docsQosPktClassSourceMacAddr,=0A= =0A= =0A= =0A= Expires August 2003 [Page 75]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosPktClassEnetProtocolType,=0A= docsQosPktClassEnetProtocol,=0A= docsQosPktClassUserPriLow,=0A= docsQosPktClassUserPriHigh,=0A= docsQosPktClassVlanId,=0A= docsQosPktClassState,=0A= docsQosPktClassPkts,=0A= docsQosPktClassBitMap,=0A= docsQosPktClassInetSourceAddrType,=0A= docsQosPktClassInetSourceAddr,=0A= docsQosPktClassInetSourceMaskType,=0A= docsQosPktClassInetSourceMask,=0A= docsQosPktClassInetDestAddrType,=0A= docsQosPktClassInetDestAddr,=0A= docsQosPktClassInetDestMaskType,=0A= docsQosPktClassInetDestMask,=0A= =0A= docsQosServiceFlowSID,=0A= docsQosServiceFlowDirection,=0A= docsQosServiceFlowPrimary,=0A= =0A= docsQosServiceFlowPkts, -- not sure if CM should implement=0A= docsQosServiceFlowOctets,=0A= docsQosServiceFlowTimeCreated,=0A= docsQosServiceFlowTimeActive,=0A= docsQosServiceFlowPHSUnknowns,=0A= docsQosServiceFlowPolicedDropPkts,=0A= docsQosServiceFlowPolicedDelayPkts,=0A= =0A= docsQosDSAReqs,=0A= docsQosDSARsps,=0A= docsQosDSAAcks,=0A= docsQosDSCReqs,=0A= docsQosDSCRsps,=0A= docsQosDSCAcks,=0A= docsQosDSDReqs,=0A= docsQosDSDRsps,=0A= docsQosDynamicAdds,=0A= docsQosDynamicAddFails,=0A= docsQosDynamicChanges,=0A= docsQosDynamicChangeFails,=0A= docsQosDynamicDeletes,=0A= docsQosDynamicDeleteFails,=0A= docsQosDCCReqs,=0A= docsQosDCCRsps,=0A= docsQosDCCAcks,=0A= docsQosDCCs,=0A= docsQosDCCFails,=0A= =0A= docsQosPHSField,=0A= docsQosPHSMask,=0A= =0A= =0A= =0A= Expires August 2003 [Page 76]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosPHSSize,=0A= docsQosPHSVerify,=0A= docsQosPHSIndex=0A= }=0A= STATUS current=0A= DESCRIPTION=0A= "Group of objects implemented in both Cable Modems and=0A= Cable Modem Termination Systems."=0A= ::=3D { docsQosGroups 1 }=0A= =0A= docsQosParamSetGroup OBJECT-GROUP=0A= OBJECTS {=0A= docsQosParamSetServiceClassName,=0A= docsQosParamSetPriority,=0A= docsQosParamSetMaxTrafficRate,=0A= docsQosParamSetMaxTrafficBurst,=0A= docsQosParamSetMinReservedRate,=0A= docsQosParamSetMinReservedPkt,=0A= docsQosParamSetActiveTimeout,=0A= docsQosParamSetAdmittedTimeout,=0A= docsQosParamSetMaxConcatBurst,=0A= docsQosParamSetSchedulingType,=0A= docsQosParamSetNomPollInterval,=0A= docsQosParamSetTolPollJitter,=0A= docsQosParamSetUnsolicitGrantSize,=0A= docsQosParamSetNomGrantInterval,=0A= docsQosParamSetTolGrantJitter,=0A= docsQosParamSetGrantsPerInterval,=0A= docsQosParamSetTosAndMask,=0A= docsQosParamSetTosOrMask,=0A= docsQosParamSetMaxLatency,=0A= docsQosParamSetRequestPolicyOct,=0A= docsQosParamSetBitMap=0A= }=0A= STATUS current=0A= DESCRIPTION=0A= "Group of objects implemenented in both Cable Modems and=0A= Cable Modem Termination Systems for QOS parameter sets."=0A= ::=3D { docsQosGroups 2 }=0A= =0A= =0A= docsQosCmtsGroup OBJECT-GROUP=0A= OBJECTS {=0A= =0A= docsQosUpstreamFragments,=0A= docsQosUpstreamFragDiscards,=0A= docsQosUpstreamConcatBursts,=0A= =0A= docsQosServiceFlowLogIfIndex,=0A= docsQosServiceFlowLogSFID,=0A= docsQosServiceFlowLogCmMac,=0A= =0A= =0A= =0A= Expires August 2003 [Page 77]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosServiceFlowLogPkts,=0A= docsQosServiceFlowLogOctets,=0A= docsQosServiceFlowLogTimeDeleted,=0A= docsQosServiceFlowLogTimeCreated,=0A= docsQosServiceFlowLogTimeActive,=0A= docsQosServiceFlowLogDirection,=0A= docsQosServiceFlowLogPrimary,=0A= docsQosServiceFlowLogServiceClassName,=0A= docsQosServiceFlowLogPolicedDropPkts,=0A= docsQosServiceFlowLogPolicedDelayPkts,=0A= docsQosServiceFlowLogControl,=0A= =0A= docsQosCmtsIfIndex -- docsQosCmtsMacToSrvFlowTable = required=0A= =0A= }=0A= STATUS current=0A= DESCRIPTION=0A= "Mandatory group of objects implemented only in the CMTS."=0A= ::=3D { docsQosGroups 3 }=0A= =0A= docsQosSrvClassPolicyGroup OBJECT-GROUP=0A= OBJECTS {=0A= docsQosServiceClassPolicyName,=0A= docsQosServiceClassPolicyRulePriority,=0A= docsQosServiceClassPolicyStatus=0A= }=0A= STATUS current=0A= DESCRIPTION=0A= "Group of objects implemented in both Cable Modems and=0A= Cable Modem Termination Systems when supporting policy = based=0A= service flows."=0A= ::=3D { docsQosGroups 4 }=0A= =0A= docsQosServiceClassGroup OBJECT-GROUP=0A= OBJECTS {=0A= docsQosServiceClassStatus,=0A= docsQosServiceClassPriority,=0A= docsQosServiceClassMaxTrafficRate,=0A= docsQosServiceClassMaxTrafficBurst,=0A= docsQosServiceClassMinReservedRate,=0A= docsQosServiceClassMinReservedPkt,=0A= docsQosServiceClassMaxConcatBurst,=0A= docsQosServiceClassNomPollInterval,=0A= docsQosServiceClassTolPollJitter,=0A= docsQosServiceClassUnsolicitGrantSize,=0A= docsQosServiceClassNomGrantInterval,=0A= docsQosServiceClassTolGrantJitter,=0A= docsQosServiceClassGrantsPerInterval,=0A= docsQosServiceClassMaxLatency,=0A= docsQosServiceClassActiveTimeout,=0A= docsQosServiceClassAdmittedTimeout,=0A= =0A= =0A= =0A= Expires August 2003 [Page 78]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosServiceClassSchedulingType,=0A= docsQosServiceClassRequestPolicy,=0A= docsQosServiceClassTosAndMask,=0A= docsQosServiceClassTosOrMask,=0A= docsQosServiceClassDirection=0A= }=0A= STATUS current=0A= DESCRIPTION=0A= "The docsQosServiceClassTable objects. If a CMTS implements=0A= expansion of Service Class Names in a QOS Parameter Set,=0A= this group is mandatory on the CMTS. If the CMTS does not=0A= support Service Class Names, this group may be = unimplemented=0A= in the CMTS. This group is not implemented on the CM.=0A= "=0A= ::=3D { docsQosGroups 5 }=0A= =0A= END=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Expires August 2003 [Page 79]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= 5. Security Considerations=0A= =0A= =0A= This MIB relates to a agent which will provide metropolitan = public=0A= internet access. As such, improper manipulation of the objects=0A= represented by this MIB may result in denial of service to a = large=0A= number of end-users [9]. Manipulation of the=0A= docsQosServiceClassTable and docsQosServiceClassPolicyTable may = allow=0A= an end-user to increase their service levels, or affect other = end-=0A= users in either a positive or negative manner. In addition,=0A= manipulation of docsQosServiceFlowLogControl could allow an = attacker=0A= to remove logs of packet and byte counts forwarded on a service = flow.=0A= If such logs were used for billing, the attacker would obtain = free=0A= service.=0A= =0A= There are a number of management objects defined in this MIB = module=0A= with a MAX-ACCESS clause of read-write and/or read-create. Such=0A= objects may be considered sensitive or vulnerable in some network=0A= environments. The support for SET operations in a non-secure=0A= environment without proper protection can have a negative effect = on=0A= network operations. These are the tables and objects and their=0A= sensitivity/vulnerability:=0A= =0A= o The docsQosServiceClassTable provides a template of QOS=0A= parameters such as maximum rate limits for a named service=0A= class. Changing these parameters would allow an attacker = to=0A= obtain unauthorized class of service.=0A= =0A= o The docsQosServiceClassPolicyTable applies CMTS vendor=0A= proprietary policies for packet forwarding, including=0A= dropping, scheduling, notification, or other policies.=0A= Changing this table could allow an attacker to deny = service=0A= to all subscribers of the CMTS or grant the attacker=0A= unauthorized forwarding policies.=0A= =0A= o The docsQosServiceFlowLogControl object controls the = deletion=0A= of entries in the docsQosServiceFlowLogTable, which acts as = a=0A= historical "detail record" of DOCSIS service flow packets = and=0A= bytes transmitted. Such records may be used for billing=0A= purposes, so the unauthorized deletion of the records can=0A= result in free service.=0A= =0A= Some of the readable objects in this MIB module (i.e., objects with = a=0A= MAX-ACCESS other than not-accessible) may be considered sensitive = or=0A= vulnerable in some network environments. It is thus important to=0A= control even GET access to these objects and possibly to even = encrypt=0A= the values of these objects when sending them over the network = via=0A= SNMP. These are the tables and objects and their=0A= sensitivity/vulnerability:=0A= =0A= o Unauthorized SNMP GET access of the docsQosPktClassTable = or=0A= =0A= =0A= =0A= Expires August 2003 [Page 80]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= docsQosPHSTable can allow an attacker to learn IP = addresses=0A= permitted to have enhanced quality of service, for = possible=0A= spoofing. This table typically contains the IP addresses=0A= involved in voice-over-IP sessions, for example.=0A= =0A= o Unauthorized SNMP GET access of the docsQosParamSetTable=0A= allows an attacker to learn the names of service classes=0A= which are permitted to have enhanced QOS service, and the=0A= values of that enhanced service. That name can be = referenced=0A= in an unauthorized DOCSIS cable modem configuration file = to=0A= obtain enhanced service.=0A= =0A= o Unauthorized SNMP GET access of the = docsQosServiceFlowTable=0A= can tell an attacker when service flows are active, e.g.=0A= when a voice-over-IP call is in progress.=0A= =0A= o Unauthorized SNMP GET access of the=0A= docsQosServiceFlowStatsTable, docsQosUpstreamStatsTable,=0A= docsQosDynamicServiceStatsTable, = docsQosServiceFlogLogTable,=0A= and docsQosCmtsMacToSrvFlowTable can tell an attacker the=0A= volume of traffic to and from any service flow in the = system,=0A= resulting in loss of privacy of the amount and direction = of=0A= data transfer.=0A= =0A= SNMP versions prior to SNMPv3 did not include adequate security.=0A= Even if the network itself is secure (for example by using = IPSec),=0A= even then, there is no control as to who on the secure network is=0A= allowed to access and GET/SET (read/change/create/delete) the = objects=0A= in this MIB module. It is RECOMMENDED that implementers consider = the=0A= security features as provided by the SNMPv3 framework (see [12],=0A= section 8), including full support for the SNMPv3 cryptographic=0A= mechanisms (for authentication and privacy). Further, deployment = of=0A= SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is=0A= RECOMMENDED to deploy SNMPv3 and to enable cryptographic = security.=0A= It is then a customer/operator responsibility to ensure that the = SNMP=0A= entity giving access to an instance of this MIB module, is = properly=0A= configured to give access to the objects only to those principals=0A= (users) that have legitimate rights to indeed GET or SET=0A= (change/create/delete) them.=0A= =0A= =0A= =0A= 6. Intellectual Property=0A= =0A= The IETF takes no position regarding the validity or scope of any=0A= intellectual property or other rights that might be claimed to=0A= pertain to the implementation or use of the technology described = in=0A= this document or the extent to which any license under such = rights=0A= might or might not be available; neither does it represent that = it=0A= has made any effort to identify any such rights. Information on = the=0A= IETF's procedures with respect to rights in standards-track and=0A= =0A= =0A= =0A= Expires August 2003 [Page 81]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= standards-related documentation can be found in BCP-11. Copies = of=0A= claims of rights made available for publication and any assurances = of=0A= licenses to be made available, or the result of an attempt made = to=0A= obtain a general license or permission for the use of such=0A= proprietary rights by implementers or users of this specification = can=0A= be obtained from the IETF Secretariat.=0A= =0A= The IETF invites any interested party to bring to its attention = any=0A= copyrights, patents or patent applications, or other proprietary=0A= rights which may cover technology that may be required to = practice=0A= this standard. Please address the information to the IETF = Executive=0A= Director.=0A= =0A= =0A= =0A= 7. Acknowledgement=0A= =0A= Funding for the RFC Editor function is currently provided by the=0A= Internet Society.=0A= =0A= =0A= =0A= 8. Normative References=0A= =0A= [1] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Structure = of=0A= Management Information for Version 2 (SMIv2)", STD 58,=0A= RFC 2578, April 1999.=0A= =0A= [2] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Textual=0A= Conventions for SMIv2", STD 58, RFC 2579, April 1999.=0A= =0A= [3] McCloghrie, K., Perkins, D. and J. Schoenwaelder, = "Conformance=0A= Statements for SMIv2", STD 58, RFC 2580, April 1999.=0A= =0A= [4] "Data-Over-Cable Service Interface Specifications:=0A= Radio Frequency Interface Specification = SP-RFIv1.1-I09-020830",=0A= DOCSIS, August 2002, http://www.cablemodem.com/.=0A= =0A= [5] L. Steinberg, "Techniques for Managing Asynchronously = Generated=0A= Alerts", RFC 1224, May 1991.=0A= =0A= [6] "Data-Over-Cable Service Interface Specifications: Operations=0A= Support System Interface Specification = SP-OSSIv1.1-I06-020830",=0A= DOCSIS, August 2002, http://www.cablemodem.com/.=0A= =0A= [7] Bradner, S., "Key words for use in RFCs to Indicate = Requirement=0A= Levels", RFC2119, March 1997.=0A= =0A= [8] "Data-Over-Cable Service Interface Specifications: Baseline=0A= Privacy Plus Interface Specification SP-BPI+-I07-020830",=0A= DOCSIS, August 2002, http://www.cablemodem.com/.=0A= =0A= =0A= =0A= Expires August 2003 [Page 82]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= [9] St. Johns, M., "Cable Device Management Information Base for=0A= DOCSIS compliant Cable Modems and Cable Modem Termination=0A= Systems", RFC 2669, August 1999.=0A= =0A= [10] St. Johns, M., "Radio Frequency (RF) Interface Management=0A= Information Base for MCNS/DOCSIS compliant RF interfaces",=0A= RFC 2670, August 1999.=0A= =0A= [11] Daniele, M. et. al.,"Textual Conventions for Internet = Network=0A= Addresses", RFC 2851, June 2000.=0A= =0A= =0A= =0A= 9. Informative References=0A= =0A= [12] Case, J., Mundy, R., Partain, D. and B. Stewart,=0A= "Introduction and Applicability Statements for Internet-=0A= Standard Management Framework", RFC 3410, December 2002.=0A= =0A= =0A= =0A= 10. Author's Address=0A= =0A= Michael Patrick=0A= Motorola Broadband Communications Sector=0A= 20 Cabot Blvd., MS M2-330=0A= Mansfield, MA 02048=0A= Phone: (508) 851-8402=0A= Email: michael.patrick@motorola.com=0A= =0A= William Murwin=0A= Motorola Broadband Communications Sector=0A= 20 Cabot Blvd., MS M2-330=0A= Mansfield, MA 02048=0A= Phone: (508) 851-8385=0A= Email: w.murwin@motorola.com=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Expires August 2003 [Page 83]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFTFebruary 2003=0A= =0A= =0A= =0A= 11. Full Copyright Statement=0A= =0A= Copyright (C) The Internet Society (2001). All Rights Reserved.=0A= =0A= This document and translations of it may be copied and furnished = to=0A= others, and derivative works that comment on or otherwise explain = it=0A= or assist in its implementation may be prepared, copied, = published=0A= and distributed, in whole or in part, without restriction of any=0A= kind, provided that the above copyright notice and this paragraph = are=0A= included on all such copies and derivative works. However, this=0A= document itself may not be modified in any way, such as by = removing=0A= the copyright notice or references to the Internet Society or = other=0A= Internet organizations, except as needed for the purpose of=0A= developing Internet standards in which case the procedures for=0A= copyrights defined in the Internet Standards process must be=0A= followed, or as required to translate it into languages other = than=0A= English.=0A= =0A= The limited permissions granted above are perpetual and will not = be=0A= revoked by the Internet Society or its successors or assigns.=0A= =0A= This document and the information contained herein is provided on = an=0A= "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET = ENGINEERING=0A= TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, = INCLUDING=0A= BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION=0A= HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF=0A= MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Expires August 2003 [Page 84]=0A= =0A= =0A= =0A= =0A= ------_=_NextPart_000_01C2C958.BC3FAD70-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Sun Feb 2 16:44:46 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12367 for ; Sun, 2 Feb 2003 16:44:46 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h12LnR524745 for ipcdn-archive@odin.ietf.org; Sun, 2 Feb 2003 16:49:27 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h12LnNJ24738; Sun, 2 Feb 2003 16:49:23 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0VIx1J12304 for ; Fri, 31 Jan 2003 13:59:01 -0500 Received: from scbh01.terayon.com (desktop.terayon.com [63.201.251.10]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15441 for ; Fri, 31 Jan 2003 13:54:53 -0500 (EST) Received: by SCBH01 with Internet Mail Service (5.5.2655.55) id ; Fri, 31 Jan 2003 10:57:07 -0800 Message-ID: From: "Lejeune, Andre" To: Murwin William-LWM008 , "Pollak, Lucy" Cc: "Docsis-Oss (E-mail) (E-mail)" , "IPCDN (E-mail) (E-mail)" Date: Fri, 31 Jan 2003 10:54:50 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h0VIx5J12309 Subject: [ipcdn] RE: Draft-ietf-ipcdn-qos-mib.txt Jan 30, 2003 Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit The posted version states: docsQosServiceFlowPolicedDropPkts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Packet Data PDUs classified to this service flow, but dropped for some reason such as violation of the Maximum Sustained Traffic Rate or UGS packet exceeding the grant size. This object does not count dropped MAC-specific management messages. Dropped unclassified upstream user date packets (i.e. non MAC-management) forwarded to the default upstream service flow should be incremented for this object." ::= { docsQosServiceFlowStatsEntry 6 } Will, I think you should correct the typo: "date" should read "data". Lucy, why is it that MAC-specific management packets are not counted? Are these counted elsewhere or is it because some of the MAC-Management packets are difficult to count? I would prefer to see all types of packets counted. Also, why is it that packets forwarded to the primary flow would increment this MIB? These are not dropped, they are re-classified. It is true though that they are not sent on the classified flow, so a separate counter would have been nice, but the packet does end up being counted as a sent packet on the primary interface. I would prefer to see re-classified packets not counted. Thank you, André -----Original Message----- From: Murwin William-LWM008 [mailto:W.Murwin@motorola.com] Sent: Thursday, January 30, 2003 3:16 PM To: Docsis-Oss (E-mail) (E-mail); IPCDN (E-mail) (E-mail) Subject: Draft-ietf-ipcdn-qos-mib.txt Jan 30, 2003 This is the latest draft of the docQosMib version 7 dated Jan 30, 2003. We have decided to extended the deadline to submit to IETF till Feb 1, 2003. This way we will have a full 6 months before the version 7 expires. NOTE: The DOCS-QOS-MIB has been re-rooted ::= {docsQosMib XXX } because of compilation errors. (1) Thus all of the QoS MIB depercated and obsolete objects have been removed. (2) The High Capacity Object have been removed and the existing 32-bit objects have become 64-bit objects. (3) The IpAddress syntax has been removed. (4) All of the objects within a table have been re-numbered inorder. This version ends the QoS MIB's backwards compatibility with older versions. It will now be the responsiblity of CableLabs to maintain a version of DOC-QOS-MIB v4 for those cable operators wanting to manage agents that are currently in the field that no longer are supported by their vendor. ______________________________ William Murwin Broadband Communications Sector Motorola Inc. Email: W.Murwin@motorola.com Tel: (508) 851-8385 <> <> _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Tue Feb 4 06:46:59 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17539 for ; Tue, 4 Feb 2003 06:46:59 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h14BqOQ19845 for ipcdn-archive@odin.ietf.org; Tue, 4 Feb 2003 06:52:24 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14BqJJ19830; Tue, 4 Feb 2003 06:52:19 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14BooJ19653 for ; Tue, 4 Feb 2003 06:50:50 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17249; Tue, 4 Feb 2003 06:44:52 -0500 (EST) Message-Id: <200302041144.GAA17249@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ipcdn@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Tue, 04 Feb 2003 06:44:52 -0500 Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-qos-mib-07.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over Cable Data Network Working Group of the IETF. Title : Data Over Cable System Quality of Service Management Information Base (DOCSIS-QOS MIB) Author(s) : M. Patrick, W. Murwin Filename : draft-ietf-ipcdn-qos-mib-07.txt Pages : 84 Date : 2003-2-3 This document defines a basic set of managed objects for SNMP-based management of extended QOS features of Cable Modems (CMs) and Cable Modem Termination Systems (CMTSs) conforming to the Data over Cable System (DOCSIS) standard version 1.1. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-qos-mib-07.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipcdn-qos-mib-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipcdn-qos-mib-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-2-3125511.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipcdn-qos-mib-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipcdn-qos-mib-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-2-3125511.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Tue Feb 4 19:37:42 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09089 for ; Tue, 4 Feb 2003 19:37:42 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h150hN404887 for ipcdn-archive@odin.ietf.org; Tue, 4 Feb 2003 19:43:23 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h150hDJ04880; Tue, 4 Feb 2003 19:43:13 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h150gQJ04855 for ; Tue, 4 Feb 2003 19:42:26 -0500 Received: from baltic.yas.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09067 for ; Tue, 4 Feb 2003 19:36:13 -0500 (EST) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [ipcdn] Comments on CableHome MIB drafts X-MIMEOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Tue, 4 Feb 2003 19:39:50 -0500 Message-ID: Thread-Topic: [ipcdn] Comments on CableHome MIB drafts Thread-Index: AcKlIqoaDSzuhmKlSCG9zSAt2myGMAnikryQ From: "Doug Jones" To: "Nakanishi Greg-MGI8179" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h150gQJ04856 Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit greg, thank-you very much for these comments. they have been reflected in the updated I-Ds: - draft-jones-cable-gateway-addressing-01 http://www.ietf.org/internet-drafts/draft-jones-cable-gateway-addressing-mib-01.txt - draft-jones-cable-gateway-config-mib-01 http://www.ietf.org/internet-drafts/draft-jones-cable-gateway-config-mib-01.txt - draft-jones-cable-gateway-device-mib-01 http://www.ietf.org/internet-drafts/draft-jones-cable-gateway-device-mib-01.txt - draft-jones-cable-gateway-security-mib-01 http://www.ietf.org/internet-drafts/draft-jones-cable-gateway-security-mib-01.txt - draft-jones-cable-gateway-tools-mib-01 http://www.ietf.org/internet-drafts/draft-jones-cable-gateway-tools-mib-01.txt further analysis, comments, and reactions are appreciated. thanks, doug -----Original Message----- From: Nakanishi Greg-MGI8179 [mailto:gnakanishi@motorola.com] Sent: Monday, December 16, 2002 9:41 AM To: 'ipcdn@ietf.org' Subject: [ipcdn] Comments on CableHome MIB drafts My comments on the CableHome draft documents --- - draft-jones-cable-gateway-addressing-00 - draft-jones-cable-gateway-config-mib-00 - draft-jones-cable-gateway-device-mib-00 - draft-jones-cable-gateway-security-mib-00 - draft-jones-cable-gateway-tools-mib-00 greg ---- General 1) MIB Boiler Plate - I don't know if this is an issue or not, but the reference format used differs from the boiler plate defined in http://www.ops.ietf.org/mib-boilerplate.html. E.g. The draft uses [1] whereas the boiler plate uses [RFC2571]. 2) References - Missing RFC 2578 and RFC 2570 as required by http://www.ops.ietf.org/mib-boilerplate.html. 3) The MIBs are currently rooted under the CableLabs branch. Prior to the draft becoming an RFC, I would think it would need to be rooted under the IETF. 4) Glossary - Cable Gateway Device : The definition in the Gateway Address MIB and Gateway Tools MIB doesn't include the phrase "...using techniques described in [RFC3280]" in the last sentence. It probably should be added for consistency. Also, references are made to [RFC2131], [RFC1350], and [RFC3280]. These references should be added to the references section. Cable Gateway Address Mapping MIB 1) Overview section. Uses the term "CableHome Residential Gateway". Does this term means the same thing as "Cable Gateway device" as defined in the glossary? Should use consistent terminology. Perhaps "Cable Gateway device" in the glossary should be renamed to "CableHome Residential Gateway"? 2) Security Considerations - Need to add the following: ... Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB. It is recommended that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model RFC 2574 [RFC2574] and the View- based Access Control Model RFC 2575 [RFC2575] is recommended. It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. Cable Gateway Configuration MIB 1) Convention Used in This Document section : Reference to RFC-2119[2] doesn't match what is listed in the references section. 2) Section 3.2.1, 3rd paragraph - "See section 8...". This needs to be updated to something like "See section 8 of the CableHome specification [16]...". 3) Section 3.2.1, last paragraph, second sentence: typo - "alsoexchange" -> "also exchance"; "behalfof" -> "behalf of". 4) Section 3.2.1, last paragraph, 3rd sentence: typo - "DHCPoptions" -> "DHCP options". 5) Section 3.2.1.1, second bullet: typo - "theWAN" -> "theWAN". 6) Section 3.2.1.1, 3rd bullet: The term "CAT" is not defined. 7) Section 3.2.1.1, 3rd bullet, 3rd sentence: typo - "occur if he limit" -> "occur if the limit". 8) Section 3.2.1.1, last bullet - references are made to cabhCapPrimaryMode and cabhPsDevProvState. References should be made to where these MIB objects are documented. 9) Section 3.2.1.1, paragraph after the bullet list: Reference made to figure 7-2. Should it be "figure 7-2 of CableHome specification" ? 10) Section 3.2.1.1, 3rd paragraph after the bullet list. The term 'CMP' is not defined. 11) Section 3.2.1.1, last paragraph. Typo - Need period at end of sentence. 12) Section after section 3.2.1.1 is also labelled 3.2.1.1. 13) 2nd Section 3.2.1.1, first bullet item : typo "WANman" -> "WAN-man" 14) 2nd Section 3.2.1.1, 4th bullet item : typo "theWAN-man" -> "the WAN-man" 15) section 3.2.1.1.2, first bullet : Reference made to section 8.3.2. Should it be "8.3.2 of CableHome specification" ? 16) section 3.2.1.1.2, page 15, 1st paragraph : typo - "WAN- Data" -> WAN-Data", "subsequentWAN-Data" -> "subsequent WAN-Data", "requestedWAN-Data" -> "requested WAN-Data" 17) section 4 MIB definition : - need space between cabhCdpServerNetworkNumberType and OBJECT-TYPE - need space between cabhCdpServerVendorSpecific and OBJECT-TYPE - need space between cabhCdpServerDhcpAddress and OBJECT-TYPE 18) Section 7, first paragraph : "In addition, manipulation of the cabhPsDevConfigFile and cabhPsDevConfigHash...". These are objects in a different MIB. Is this a relevent Security Consideration for this document? 19) Section 7, 2nd bullet item : "The device may be reset by setting cabhPsDevResetNow...". Same comment as above. Cable Gateway Remote Diagnostic Tools MIB 1) References : Missing required boiler plate references for MIB documents. 2) Security considerations: same comment as Cable Gateway Address Mapping MIB, item 2 3) Pagination : In the MIB definition section there are no paginations. CableHome Residential Gateway Device Security MIB 1) Title : The title of the other CableHome MIBs use the term "Cable Gateway" whereas this one uses the term "CableHome Residential Gateway Device". All the MIB document titles should probably use the same term. 2) Abstract : The mailing list addresses is given as "ipcdn@terayon.com". Is this correct? The other CableHome MIB documents give an address of "ipcdn@ietf.org". 3) Definitions : Note that X509Certificate object is being imported from the BPI2 MIB which is currently still a draft. 4) X509Certificate object REFERENCE : Should update the reference to -I02. Cable Gateway Device MIB 1) Section 3.2.2, 4th paragraph : "7.3.3.3.1 in [16]" -> "7.3.3.3.1 of [16]" 2) Section 3.2.2, 5th paragraph, 2nd sentence : Suggest rewording to - "The PsDevProv group also includes statistics variables for keeping track of the number of Type-Length-Value (TLV) objects passed in the configuration file that the PS processed and the number that were rejected." 3) Section 3.2.3 : Makes a number of references not in the references section. _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Wed Feb 5 13:33:39 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05830 for ; Wed, 5 Feb 2003 13:33:39 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h15IdiK13390 for ipcdn-archive@odin.ietf.org; Wed, 5 Feb 2003 13:39:44 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15IdZJ13376; Wed, 5 Feb 2003 13:39:35 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15IcXJ13346 for ; Wed, 5 Feb 2003 13:38:33 -0500 Received: from snowmass.tci.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05767 for ; Wed, 5 Feb 2003 13:31:57 -0500 (EST) Received: from mms01-relayb.tci.com (mms01-relayb.broadband.att.com [147.191.90.1]) by snowmass.tci.com (8.12.2/8.12.2) with ESMTP id h15IXTt5004247; Wed, 5 Feb 2003 11:35:32 -0700 (MST) Received: from 147.191.89.203 by mms01-relaya.tci.com with ESMTP ( Tumbleweed MMS SMTP Relay (MMS v5.5.0)); Wed, 05 Feb 2003 11:35:30 -0600 Received: by entexchimc01.broadband.att.com with Internet Mail Service ( 5.5.2653.19) id ; Wed, 5 Feb 2003 11:35:44 -0700 Message-ID: <6732623D2548D61193C90002A5C88DCC0566362F@entmaexch02.broadband.att.com> From: "Woundy, Richard" To: "'ipcdn@ietf.org '" , "'docsis-oss@cablelabs.com '" cc: "Woundy, Richard" , "'jfm@cablelabs.com '" Date: Wed, 5 Feb 2003 11:35:21 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) X-WSS-ID: 125F86F8580548-02-01 Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [ipcdn] IPCDN interim working group meeting, February 13th Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Folks, We are planning an IPCDN interim working group meeting on February 13th in Louisville, CO. There have been two recent planning updates to the interim meeting: - We are meeting at the CableLabs facility. - We have a proposed agenda (see below) Please be sure to register for the IPCDN interim meeting using the email procedure on the website above. -- Rich Agenda I. Agenda Bashing (e.g. some folks are interested in discussing the DSG MIB) II. One-by-one DOCSIS MIB review (8am - 12pm noon) Budget time: 30 minutes each - QoS MIB draft-ietf-ipcdn-qos-mib-07.txt - Cable Device MIB draft-ietf-ipcdn-device-mibv2-04.txt - BPI+ MIB - updated draft to be published next week - Event Notification MIB draft-ietf-ipcdn-docsisevent-mib-03.txt - RFI MIB draft-ietf-ipcdn-docs-rfmibv2-05.txt - Subscriber Management MIB draft-ietf-ipcdn-subscriber-mib-08.txt - review of MIB doctor comments & resolution III. CableHome (1pm - 2pm) Budget time: 10-15 minutes each Review of CableHome MIBs one-by-one for consideration by WG per last meeting request. All MIBs were recently updated (and the initial QoS MIB was submitted) in January 2003. - Security MIB draft-jones-cable-gateway-security-mib-01.txt - Configuration MIB draft-jones-cable-gateway-config-mib-01.txt - Device Management MIB draft-jones-cable-gateway-device-mib-01.txt - Address Mapping MIB draft-jones-cable-gateway-addressing-mib-01.txt - Remote Diagnostic Tools MIB draft-jones-cable-gateway-tools-mib-01.txt - CableHome QoS MIB draft-jones-cable-gateway-qos-mib-00.txt IV. PacketCable MIBs (as time permits) Review all IPCDN PacketCable MIBs, especially Wim's draft changes in draft-ietf-ipcdn-pktc-eventmess-01.txt. V. WG San Francisco Agenda Prep & Next Steps _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Sun Feb 9 09:28:57 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29290 for ; Sun, 9 Feb 2003 09:28:57 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h19Earu04580 for ipcdn-archive@odin.ietf.org; Sun, 9 Feb 2003 09:36:53 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h19EYUp04538; Sun, 9 Feb 2003 09:34:30 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h19EXAp04502 for ; Sun, 9 Feb 2003 09:33:10 -0500 Received: from peacock.tci.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29182 for ; Sun, 9 Feb 2003 09:24:43 -0500 (EST) Received: from mms02-RelayB.tci.com (mms02-relayb.broadband.att.com [147.191.89.213]) by peacock.tci.com (8.12.2/8.12.2) with ESMTP id h19ESNJD001146 for ; Sun, 9 Feb 2003 07:28:23 -0700 (MST) Received: from 147.191.90.10 by mms02-RelayB.tci.com with ESMTP ( Tumbleweed MMS SMTP Relay (MMS v5.5.0)); Sun, 09 Feb 2003 07:28:14 -0600 Received: by entexchimc03.broadband.att.com with Internet Mail Service ( 5.5.2653.19) id ; Sun, 9 Feb 2003 07:26:55 -0700 Message-ID: <6732623D2548D61193C90002A5C88DCC0566364A@entmaexch02.broadband.att.com> From: "Woundy, Richard" To: "'ipcdn@ietf.org '" Date: Sun, 9 Feb 2003 07:28:10 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) X-WSS-ID: 1258BAF44370-01-01 Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [ipcdn] Guidelines for MIB Authors and Reviewers Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Folks, The MIB doctors are starting to codify their list of guidelines for MIB doctor reviews. Note that this draft is a work in progress. Such a document should greatly assist our specification writing and reviews. See . -- Rich _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Mon Feb 10 17:03:01 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27725 for ; Mon, 10 Feb 2003 17:03:01 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1AMBaL16599 for ipcdn-archive@odin.ietf.org; Mon, 10 Feb 2003 17:11:36 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AM9Lp16488; Mon, 10 Feb 2003 17:09:21 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AM88p16439 for ; Mon, 10 Feb 2003 17:08:08 -0500 Received: from snowmass.tci.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27620 for ; Mon, 10 Feb 2003 16:59:02 -0500 (EST) Received: from mms01-relayb.tci.com (mms01-relayb.broadband.att.com [147.191.90.1]) by snowmass.tci.com (8.12.2/8.12.2) with ESMTP id h1AM2Esu007513 for ; Mon, 10 Feb 2003 15:02:42 -0700 (MST) Received: from 147.191.90.11 by mms01-relayb.tci.com with ESMTP ( Tumbleweed MMS SMTP Relay (MMS v5.5.0)); Mon, 10 Feb 2003 15:02:34 -0600 Received: by entexchimc04.broadband.att.com with Internet Mail Service ( 5.5.2653.19) id <1RRPCZX0>; Mon, 10 Feb 2003 15:01:55 -0700 Message-ID: <6732623D2548D61193C90002A5C88DCC05663656@entmaexch02.broadband.att.com> From: "Woundy, Richard" To: "IPCDN WG (E-mail)" Date: Mon, 10 Feb 2003 15:02:26 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) X-WSS-ID: 1256FEFC1222662-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [ipcdn] BPI+ MIB draft posted Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Folks, I have posted the most recent BPI+ MIB on the ipcdn.org website: . I also updated the list of internet-drafts: . All of the internet-drafts in the Interim Meeting agenda are now available for review for this Thursday. -- Rich _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Mon Feb 10 17:09:34 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27925 for ; Mon, 10 Feb 2003 17:09:34 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1AMI9V16872 for ipcdn-archive@odin.ietf.org; Mon, 10 Feb 2003 17:18:09 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AMG3p16785; Mon, 10 Feb 2003 17:16:03 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1AMF2p16740 for ; Mon, 10 Feb 2003 17:15:02 -0500 Received: from snowmass.tci.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27811 for ; Mon, 10 Feb 2003 17:05:55 -0500 (EST) Received: from mms01-relayb.tci.com (mms01-relayb.broadband.att.com [147.191.90.1]) by snowmass.tci.com (8.12.2/8.12.2) with ESMTP id h1AM9bst010540 for ; Mon, 10 Feb 2003 15:09:37 -0700 (MST) Received: from 147.191.89.203 by mms01-relaya.tci.com with ESMTP ( Tumbleweed MMS SMTP Relay (MMS v5.5.0)); Mon, 10 Feb 2003 15:09:30 -0600 Received: by entexchimc01.broadband.att.com with Internet Mail Service ( 5.5.2653.19) id ; Mon, 10 Feb 2003 15:09:51 -0700 Message-ID: <6732623D2548D61193C90002A5C88DCC05663657@entmaexch02.broadband.att.com> From: "Woundy, Richard" To: "IPCDN WG (E-mail)" Date: Mon, 10 Feb 2003 15:09:19 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) X-WSS-ID: 1256FC901252715-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [ipcdn] Interim Meeting Update Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Folks, I updated the link to the BPI+ MIB in . -- Rich _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Tue Feb 11 06:58:59 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29356 for ; Tue, 11 Feb 2003 06:58:59 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1BC7qB08928 for ipcdn-archive@odin.ietf.org; Tue, 11 Feb 2003 07:07:52 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BC5kp08204; Tue, 11 Feb 2003 07:05:46 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1BBtip07815 for ; Tue, 11 Feb 2003 06:55:44 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28755; Tue, 11 Feb 2003 06:46:21 -0500 (EST) Message-Id: <200302111146.GAA28755@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ipcdn@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Tue, 11 Feb 2003 06:46:21 -0500 Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-bpiplus-mib-08.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over Cable Data Network Working Group of the IETF. Title : Management Information Base for DOCSIS Cable Modems and Cable Modem Termination Systems for Baseline Privacy Plus Author(s) : S. Green, K. Katsnelson Filename : draft-ietf-ipcdn-bpiplus-mib-08.txt Pages : 74 Date : 2003-2-10 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a set of managed objects for SNMP-based management of the Baseline Privacy Plus features [17] of DOCSIS1.1- compliant[16] Cable Modems and Cable Modem Termination Systems. This memo specifies a MIB module in a manner that is compliant to the SNMP SMIv2 [5][6][7]. The set of objects are consistent with the SNMP framework and existing SNMP standards. This memo is a product of the IPCDN working group within the Internet Engineering Task Force. Comments are solicited and should be addressed to the working group's mailing list at ipcdn@ietf.org and/or the authors. Conventions used in this document A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-bpiplus-mib-08.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipcdn-bpiplus-mib-08.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipcdn-bpiplus-mib-08.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-2-10135926.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipcdn-bpiplus-mib-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipcdn-bpiplus-mib-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-2-10135926.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Thu Feb 13 09:11:06 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12496 for ; Thu, 13 Feb 2003 09:11:06 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1DEL0023031 for ipcdn-archive@odin.ietf.org; Thu, 13 Feb 2003 09:21:00 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DEIap22875; Thu, 13 Feb 2003 09:18:36 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DEHsp22841 for ; Thu, 13 Feb 2003 09:17:54 -0500 Received: from ihemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12444 for ; Thu, 13 Feb 2003 09:07:29 -0500 (EST) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h1DEBBr18329 for ; Thu, 13 Feb 2003 09:11:12 -0500 (EST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Thu, 13 Feb 2003 15:11:11 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155E64BD7@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: Wilson.Sawyer@arrisi.com, bwijnen@lucent.com Cc: "Ipcdn (E-mail)" Date: Thu, 13 Feb 2003 15:11:05 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [ipcdn] RE: ipcdn docsis subscriber management draft revision 8 Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , I believe I am OK with this document now. One nit, copyright year in sect 10 should be 2003. RFC-Editor will catch it (if you do not do another rev before that time). Thanks, Bert > -----Original Message----- > From: Wilson.Sawyer@arrisi.com [mailto:Wilson.Sawyer@arrisi.com] > Sent: donderdag 13 februari 2003 14:38 > To: bwijnen@lucent.com > Subject: ipcdn docsis subscriber management draft > > > Haven't heard from you lately. Have you had a chance to look > at the -08 > draft? > > - Wilson > _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Thu Feb 13 10:06:18 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14604 for ; Thu, 13 Feb 2003 10:06:18 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1DFGEM26991 for ipcdn-archive@odin.ietf.org; Thu, 13 Feb 2003 10:16:14 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DFE7p26898; Thu, 13 Feb 2003 10:14:07 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DFD9p26845 for ; Thu, 13 Feb 2003 10:13:09 -0500 Received: from peacock.tci.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14403 for ; Thu, 13 Feb 2003 10:02:42 -0500 (EST) Received: from mms02-RelayB.tci.com (mms02-relayb.broadband.att.com [147.191.89.213]) by peacock.tci.com (8.12.2/8.12.2) with ESMTP id h1DF62JE010581 for ; Thu, 13 Feb 2003 08:06:25 -0700 (MST) Received: from 147.191.90.11 by mms02-RelayB.tci.com with ESMTP ( Tumbleweed MMS SMTP Relay (MMS v5.5.0)); Thu, 13 Feb 2003 08:06:13 -0600 Received: by entexchimc04.broadband.att.com with Internet Mail Service ( 5.5.2653.19) id <1RRP23AT>; Thu, 13 Feb 2003 08:05:37 -0700 Message-ID: <6732623D2548D61193C90002A5C88DCC0566367A@entmaexch02.broadband.att.com> From: "Woundy, Richard" To: "IPCDN WG (E-mail)" Date: Thu, 13 Feb 2003 08:06:09 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) X-WSS-ID: 12556BEF761586-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [ipcdn] Presentations for today's interim meeting Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Folks, I posted five of today's presentations on the IPCDN website. See , particularly the row corresponding to the Interim IPCDN WG Meeting in Denver. -- Rich _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Thu Feb 13 10:13:11 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15106 for ; Thu, 13 Feb 2003 10:13:11 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1DFN7Q27333 for ipcdn-archive@odin.ietf.org; Thu, 13 Feb 2003 10:23:07 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DFL5p27263; Thu, 13 Feb 2003 10:21:05 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DFK7p27201 for ; Thu, 13 Feb 2003 10:20:07 -0500 Received: from ihemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14786 for ; Thu, 13 Feb 2003 10:09:40 -0500 (EST) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h1DFDOr21432 for ; Thu, 13 Feb 2003 10:13:24 -0500 (EST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Thu, 13 Feb 2003 16:13:23 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155E64C20@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Ipcdn (E-mail)" Cc: stu.green@arrisi.com, a.katsnelson@cablelabs.com, k.ozawa@cablelabs.com Date: Thu, 13 Feb 2003 16:12:51 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [ipcdn] Review of: draft-ietf-ipcdn-bpiplus-mib-08.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Here are my comments: - references/citations in abstract are not allowed per RFC-Editor policy - 2nd para in abstract seems not needed. but I can live with it - Tiltle of sect 1 is not inline with MIB boilerplate - 3rd para in section 1 is not needed, in fact I'd rather see it removed. The RFC3410 explains all that. - DESCRIPTION clause of MODULE-IDENTITY is missing the MIB copyright statement - I had asked in in earlier email: Mmm.. did I review rev 07. I can't quickly find that I did send a review report. I am assuming that you will take care of all the comments that are (in my view) to be expected based on the review of the subscriber mib I did, right? - Is this MIB obsoleteing an earlier (RFC) version? If so, then that should noted on front page/abstract and we should see a revision statement that lists the original RFC. If this is the first time this MIB gets publsihed as an RFC, then we want to see only one simple revisions clause with a DESCRIPTION aka: "Initial version, published as RFC xxxx." -- RFC-editor assigns xxxx We do not want to see long lists of changes that happened during initial revisions of Internet Drafts - And how did you decide to assign the docsBpi2MIB MODULE-IDENTITY ... ::= { docsIfMib 6 } I worry a lot about this practice, cause it is very difficult to keep track and to ensure that no conflicts arise. - I worry about: X509Certificate ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An X509 digital certificate encoded as an ASN.1 DER object." SYNTAX OCTET STRING (SIZE (0..1400)) The reason is that this is not some X509 generic Certificate but a special one for your IPCDN use. How about renaming it to DocsX509ASN1DEREncodedCertificate ?? - docsBpi2CmAuthReset OBJECT-TYPE Would it be wise to add a docsBpi2CmAuthLastReset object similar as what was done in the subscriber MIB module? - objects like: docsBpi2CmAuthRejects OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object is the count of times the CM has received an Authorization Reject message, since reboot." require that a Counter starts at zero. But those are NOT the semanticws of a Counter32. If this is what you want, I think you need to use the ZeroBasedCounter32 as per RFC2021. Pls read draft-ietf-ops-mib-review-guidelines-00.txt sect 4.6 specifically 4.6.1.2 You have quite a few of those objetcs - docsBpi2CmAuthRejectErrorString OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..128)) MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object is the Display-String in S/Display-String/text string/ ?? Same for docsBpi2CmAuthInvalidErrorString And for docsBpi2CmTEKKeyRejectErrorString docsBpi2CmTEKInvalidErrorString docsBpi2CmIpMulticastSAMapRejectErrorString docsBpi2CmtsAuthInvalidErrorString - docsBpi2CmTEKDataEncryptAlg OBJECT-TYPE SYNTAX INTEGER { none(0), des56CbcMode(1), des40CbcMode(2) } We recommend to start Enumerations from 1. Possibly the 1 and 2 for the desXxxx enumerations are so numbered to align with some other place. If so, then starting with zero seems acceptable. But pls add some explanantion in that case Same question for simial xxxCrypto object - docsBpi2CmTEKDataAuthentAlg OBJECT-TYPE SYNTAX INTEGER { none(0) } An object that can only have one value that is ALWAYS zero? What is the use of that? Maybe future extensibility, but if so, then please say so in DESCRIPTION clause, otherwise this seems nonsense and bloat. Same question for simial xxxCrypto object - docsBpi2CmIpMulticastIndex OBJECT-TYPE SYNTAX Integer32 (1..1000) It is valid. But for INDEX objects we prefer Unsigned32 with a range. see again the mib review guidelines doc I think this occurs a few more time in this MIB module. As I say, it is valid, but since your still working on this MIB module, might as well use the recommended method. - docsBpi2CmIpMulticastAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "This object represents the IP multicast address to be mapped." you MUST specify with InetAddressType object defines the context or type of this object. You did it correct in subscriber mib. - docsBpi2CmtsDefaultSelfSignedManufCertTrust OBJECT-TYPE SYNTAX INTEGER { trusted (1), untrusted (2) } Seems to me that docsBpi2CmtsDefaultSelfSignedManufCertTrusted descriptor with a syntax of TruthValue is more appropriate - docsBpi2CmtsCheckCertValidityPeriods OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Setting this object to TRUE causes all chained and The better wording is: "Setting this object to 'true' causes all chained and This occurs a few more times in this MIB module - docsBpi2CmtsAuthCmBpiVersion OBJECT-TYPE SYNTAX INTEGER { bpi (0), bpiPlus (1) } Any special reason why enumeration cannot start at 1? - docsBpi2CmtsAuthCmReset OBJECT-TYPE Yet another way in which you guys do resets. - docsBpi2CmtsAuthCmInfos OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object is the count of times the CMTS has received an Authentication Information message from this CM, since entry creatiion." ZeroBasedCounter32 ?? You have several of those - docsBpi2CmtsAuthBpkmCmCertValid OBJECT-TYPE SYNTAX INTEGER { unknown (0), validCmChained (1), validCmTrusted (2), invalidCmUntrusted (3), invalidCAUntrusted (4), invalidCmOther (5), invalidCAOther (6) } Any special reason to start ENUMERATION with zero ?? - docsBpi2CmtsTEKSAType OBJECT-TYPE SYNTAX INTEGER { none(0), primary(1), static(2), dynamic(3) } Any special reason to start ENUMERATION with zero ?? There are more of those... I won;t list them anymore, I guess you get the gist. - I wonder if it would not be better to have 2 compliance statements, one for CM and one for CMTS. It is unclear to me if any GROUPS are mandatory. I think some are, but it depends if your are CM or CMTS - -- relaxation on IP addressing OBJECT docsBpi2CmIpMulticastAddressType -- SYNTAX InetAddressType { ipv4(1) } Pls make it a real SYNTAX clause and not a comment. That SMICng barks at it is something we know and SMICng should be fixed. - You have citations in DESCRIPTION clauses. We normally do not do that, cause they will be lost when people extract the MIB module from the RFC. - Mmm.. you start off with some OBSOLETED object group right away he? You might want to say something about when/why that happened. - References need to be split in normative and informative - You have picked up the new MIB boilerplate, but you still have a lot of old MIB boilerplate references included, which make no sense anymore - The new MIB boilerplate has [RFC2578], [RFC2579] and [RFC2580] as citations, but they do not show as such in the references section - The security considerations section is not compliant with the new MIB security guidelines. The subscriber MIB has done a much better job. You should too. - I see 3 names in CONTACT-INFO while only two are listed on front page and only two are listed in Author's addresses? Oh well... lots of little nits that the WG could have found without me having to do a review. Bert _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Thu Feb 13 10:59:35 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16273 for ; Thu, 13 Feb 2003 10:59:34 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1DG9Vg30983 for ipcdn-archive@odin.ietf.org; Thu, 13 Feb 2003 11:09:31 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DG75p30329; Thu, 13 Feb 2003 11:07:05 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DG6Wp30148 for ; Thu, 13 Feb 2003 11:06:32 -0500 Received: from ihemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16238 for ; Thu, 13 Feb 2003 10:56:04 -0500 (EST) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h1DFxnr17295 for ; Thu, 13 Feb 2003 10:59:49 -0500 (EST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Thu, 13 Feb 2003 16:59:45 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155E64C51@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Ipcdn (E-mail)" Date: Thu, 13 Feb 2003 16:59:42 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [ipcdn] quick review of draft-ietf-ipcdn-qos-mib-07.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , I did a very quick check of: http://www.ipcdn.org/drafts/draft-ietf-ipcdn-qos-mib-07.txt - first para of sect 1 is redundant - This is the first RFC-tobe. So we do not want to see longs list of REVISION clauses with pre-RFC changes - IfDirection, probably betternamed DocsRFMacIfDirection it is not generic TC. In any event, it conflicts with IfDirection in RFC3289 (which I guess should have had another name too). - In general, I'd like your TCs to start with DocsXxxx - We prefer interger-based INDEX objects to be Unsigned32 (with a range that excludes zero) - You seem to have used RFC2851 when understanding InetAddresType and InetAddress. Pls see the newer RFC3291, which also explains that you can use one AddressType to specify the type of multople Addresses. That will reduce the size of the mIB module somewhat I expect. The xxxMask objects probably should be InetAddressPrefixLength TC - RFC3291 also has InetPort as a TC that you probably should use - I am not happy with diffServMultiFieldClfrProtocol OBJECT-TYPE SYNTAX Unsigned32 (0..255) See RFC3289 diffServMultiFieldClfrProtocol OBJECT-TYPE SYNTAX Unsigned32 (0..255) And you will hopefully understand why - When I see things like: docsQosPktClassState OBJECT-TYPE SYNTAX INTEGER { active(1), inactive(2) } I always wonder if a TruthValue is bot better - Have you checked your use of VLANID with other MIB modules where they use it? - docsQosParamSetServiceClassName OBJECT-TYPE SYNTAX DisplayString Is this intended for human consumption? Then RFC2277 says it must allow for internatioalization, so an SnmpAdminString or some other UTF-8 based TC seems better - For Counter (both 32 or 64) you must specify a discontinuity object (often a timer). See the Counter32 and Counter64 specs in RFC2578 - docsQosServiceFlowTimeActive OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The total time that service flow has been active." I would say' "The number of seconds that the flow has been active." That way I can see it has Counter32 semantics, otherwise that is hard to see. - docsQosServiceClassTable Can you pls add a StorageType object or specify the persistency behaviour of entries in this table? - OBJECT docsQosPktClassInetSourceAddrType -- SYNTAX InetAddressType { ipv4(1) } Remove the two dashed. This is a valid statement. SMICng needs fixing As I said... it was just a quick check. So I do not claim my comments are complete. I also di not do a SYNATX compile check yet. Thanks, Bert _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Thu Feb 13 13:08:52 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20540 for ; Thu, 13 Feb 2003 13:08:52 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1DIC7i07720 for ipcdn-archive@odin.ietf.org; Thu, 13 Feb 2003 13:12:07 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DIA7p07663; Thu, 13 Feb 2003 13:10:07 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DI97p07609 for ; Thu, 13 Feb 2003 13:09:07 -0500 Received: from ihemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20492 for ; Thu, 13 Feb 2003 13:05:21 -0500 (EST) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h1DI94e09392 for ; Thu, 13 Feb 2003 13:09:04 -0500 (EST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Thu, 13 Feb 2003 19:09:03 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155E64CB2@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Ipcdn (E-mail)" Cc: "Wijnen, Bert (Bert)" Date: Thu, 13 Feb 2003 19:07:36 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [ipcdn] RE: quick review of draft-ietf-ipcdn-qos-mib-07.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , > - I am not happy with > diffServMultiFieldClfrProtocol OBJECT-TYPE > SYNTAX Unsigned32 (0..255) Oops. I meant to say: docsQosPktClassIpProtocol OBJECT-TYPE SYNTAX Integer32 (0..258) > see RFC3289 which says > diffServMultiFieldClfrProtocol OBJECT-TYPE > SYNTAX Unsigned32 (0..255) Bert _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Thu Feb 13 13:16:40 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20830 for ; Thu, 13 Feb 2003 13:16:40 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1DIJtM08164 for ipcdn-archive@odin.ietf.org; Thu, 13 Feb 2003 13:19:55 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DII2p08077; Thu, 13 Feb 2003 13:18:02 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DIHhp08039 for ; Thu, 13 Feb 2003 13:17:43 -0500 Received: from ondar.cablelabs.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20743 for ; Thu, 13 Feb 2003 13:13:57 -0500 (EST) Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20]) by ondar.cablelabs.com (8.12.6/8.12.6) with ESMTP id h1DIHdwH028065; Thu, 13 Feb 2003 11:17:39 -0700 (MST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: [ipcdn] quick review of draft-ietf-ipcdn-qos-mib-07.txt Date: Thu, 13 Feb 2003 11:17:38 -0700 Message-ID: Thread-Topic: [ipcdn] quick review of draft-ietf-ipcdn-qos-mib-07.txt Thread-Index: AcLTeT/7W/BlrZ6zQS2aGeT5MeoTaAAErVtw From: "Eduardo Cardona" To: "Wijnen, Bert (Bert)" , "Ipcdn (E-mail)" X-Approved: ondar Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1DIHhp08040 Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit FYI Could be in other places but a starting point. draft-ietf-bridge-bridgemib-01.txt VlanId ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The 12-bit VLAN ID used in the VLAN Tag header." SYNTAX INTEGER (1..4094) -----Original Message----- From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] Sent: Thursday, February 13, 2003 9:00 AM To: Ipcdn (E-mail) Subject: [ipcdn] quick review of draft-ietf-ipcdn-qos-mib-07.txt I did a very quick check of: http://www.ipcdn.org/drafts/draft-ietf-ipcdn-qos-mib-07.txt - first para of sect 1 is redundant - This is the first RFC-tobe. So we do not want to see longs list of REVISION clauses with pre-RFC changes - IfDirection, probably betternamed DocsRFMacIfDirection it is not generic TC. In any event, it conflicts with IfDirection in RFC3289 (which I guess should have had another name too). - In general, I'd like your TCs to start with DocsXxxx - We prefer interger-based INDEX objects to be Unsigned32 (with a range that excludes zero) - You seem to have used RFC2851 when understanding InetAddresType and InetAddress. Pls see the newer RFC3291, which also explains that you can use one AddressType to specify the type of multople Addresses. That will reduce the size of the mIB module somewhat I expect. The xxxMask objects probably should be InetAddressPrefixLength TC - RFC3291 also has InetPort as a TC that you probably should use - I am not happy with diffServMultiFieldClfrProtocol OBJECT-TYPE SYNTAX Unsigned32 (0..255) See RFC3289 diffServMultiFieldClfrProtocol OBJECT-TYPE SYNTAX Unsigned32 (0..255) And you will hopefully understand why - When I see things like: docsQosPktClassState OBJECT-TYPE SYNTAX INTEGER { active(1), inactive(2) } I always wonder if a TruthValue is bot better - Have you checked your use of VLANID with other MIB modules where they use it? - docsQosParamSetServiceClassName OBJECT-TYPE SYNTAX DisplayString Is this intended for human consumption? Then RFC2277 says it must allow for internatioalization, so an SnmpAdminString or some other UTF-8 based TC seems better - For Counter (both 32 or 64) you must specify a discontinuity object (often a timer). See the Counter32 and Counter64 specs in RFC2578 - docsQosServiceFlowTimeActive OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The total time that service flow has been active." I would say' "The number of seconds that the flow has been active." That way I can see it has Counter32 semantics, otherwise that is hard to see. - docsQosServiceClassTable Can you pls add a StorageType object or specify the persistency behaviour of entries in this table? - OBJECT docsQosPktClassInetSourceAddrType -- SYNTAX InetAddressType { ipv4(1) } Remove the two dashed. This is a valid statement. SMICng needs fixing As I said... it was just a quick check. So I do not claim my comments are complete. I also di not do a SYNATX compile check yet. Thanks, Bert _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Thu Feb 13 13:43:49 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21804 for ; Thu, 13 Feb 2003 13:43:49 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1DIl5710429 for ipcdn-archive@odin.ietf.org; Thu, 13 Feb 2003 13:47:05 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DIj4p10366; Thu, 13 Feb 2003 13:45:04 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DIicp10297 for ; Thu, 13 Feb 2003 13:44:38 -0500 Received: from ihemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21707 for ; Thu, 13 Feb 2003 13:40:51 -0500 (EST) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h1DIiZe25210 for ; Thu, 13 Feb 2003 13:44:35 -0500 (EST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Thu, 13 Feb 2003 19:44:30 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155E64CBB@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: Eduardo Cardona , "Wijnen, Bert (Bert)" , "Ipcdn (E-mail)" Subject: RE: [ipcdn] quick review of draft-ietf-ipcdn-qos-mib-07.txt Date: Thu, 13 Feb 2003 19:44:21 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Eduardo writes: > > FYI > Could be in other places but a starting point. > > draft-ietf-bridge-bridgemib-01.txt > > VlanId ::= TEXTUAL-CONVENTION > STATUS current > DESCRIPTION > "The 12-bit VLAN ID used in the VLAN Tag header." > SYNTAX INTEGER (1..4094) > And so... why does yours differ docsQosPktClassVlanId OBJECT-TYPE SYNTAX Integer32 (0..4095) MAX-ACCESS read-only STATUS current I am not claiming that one is better than the other. But I always wonder why they are different. Best to try and get in touch with the bridgemib people Bert _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Thu Feb 13 14:06:04 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22313 for ; Thu, 13 Feb 2003 14:06:04 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1DJ9K512049 for ipcdn-archive@odin.ietf.org; Thu, 13 Feb 2003 14:09:20 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DJ75p11372; Thu, 13 Feb 2003 14:07:05 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DJ6op11218 for ; Thu, 13 Feb 2003 14:06:50 -0500 Received: from ondar.cablelabs.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22267 for ; Thu, 13 Feb 2003 14:03:03 -0500 (EST) Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20]) by ondar.cablelabs.com (8.12.6/8.12.6) with ESMTP id h1DJ6jwH029596; Thu, 13 Feb 2003 12:06:45 -0700 (MST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: [ipcdn] quick review of draft-ietf-ipcdn-qos-mib-07.txt Date: Thu, 13 Feb 2003 12:06:45 -0700 Message-ID: Thread-Topic: [ipcdn] quick review of draft-ietf-ipcdn-qos-mib-07.txt Thread-Index: AcLTkCwhGFz8HAgzTpe8ptYnfs6QhAAANxBw From: "Greg White" To: "Wijnen, Bert (Bert)" , "Eduardo Cardona" , "Ipcdn (E-mail)" X-Approved: ondar Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1DJ6op11219 Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit It is important that the range for docsQosPktClassVlanId include the value 0: If the referenced parameter is not present in the classifier, the value of this object is reported as 0. -Greg -----Original Message----- From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] Sent: Thursday, February 13, 2003 11:44 AM To: Eduardo Cardona; Wijnen, Bert (Bert); Ipcdn (E-mail) Subject: RE: [ipcdn] quick review of draft-ietf-ipcdn-qos-mib-07.txt Eduardo writes: > > FYI > Could be in other places but a starting point. > > draft-ietf-bridge-bridgemib-01.txt > > VlanId ::= TEXTUAL-CONVENTION > STATUS current > DESCRIPTION > "The 12-bit VLAN ID used in the VLAN Tag header." > SYNTAX INTEGER (1..4094) > And so... why does yours differ docsQosPktClassVlanId OBJECT-TYPE SYNTAX Integer32 (0..4095) MAX-ACCESS read-only STATUS current I am not claiming that one is better than the other. But I always wonder why they are different. Best to try and get in touch with the bridgemib people Bert _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Thu Feb 13 14:19:36 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22647 for ; Thu, 13 Feb 2003 14:19:36 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1DJMrT12716 for ipcdn-archive@odin.ietf.org; Thu, 13 Feb 2003 14:22:53 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DJL6p12628; Thu, 13 Feb 2003 14:21:06 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DJKIp12570 for ; Thu, 13 Feb 2003 14:20:18 -0500 Received: from ihemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22560 for ; Thu, 13 Feb 2003 14:16:30 -0500 (EST) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h1DJKDX10808 for ; Thu, 13 Feb 2003 14:20:14 -0500 (EST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Thu, 13 Feb 2003 20:20:12 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155E64CC0@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Ipcdn (E-mail)" Cc: bwijnen@lucent.com Date: Thu, 13 Feb 2003 20:20:12 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [ipcdn] review of draft-ietf-ipcdn-device-mibv2-04.txt - use of InetPortN umber Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , You now use InetPortNumber for ports. That is in principle good, but since that TC has SYNTAX Unsigned32 (0..65535) as underlying datatype. Your RFC2669 has SYNTAX Integer32 (0..65535) as datatype. So by switching to InetPortNumber you cause a change on the wire. That is not allowed. You'd need to deprecate the old objects and create new ones for such a change to be legal according to the SMI rules. Thanks, Bert _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Thu Feb 13 15:36:01 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27257 for ; Thu, 13 Feb 2003 15:36:01 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1DKdKn18576 for ipcdn-archive@odin.ietf.org; Thu, 13 Feb 2003 15:39:20 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DKb8p18014; Thu, 13 Feb 2003 15:37:08 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DKahp17791 for ; Thu, 13 Feb 2003 15:36:43 -0500 Received: from ihemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26858 for ; Thu, 13 Feb 2003 15:32:53 -0500 (EST) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h1DKabX15280 for ; Thu, 13 Feb 2003 15:36:38 -0500 (EST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Thu, 13 Feb 2003 21:36:37 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155E64CD4@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: Greg White , "Wijnen, Bert (Bert)" , Eduardo Cardona , "Ipcdn (E-mail)" Subject: RE: [ipcdn] quick review of draft-ietf-ipcdn-qos-mib-07.txt Date: Thu, 13 Feb 2003 21:36:33 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Inline > -----Original Message----- > From: Greg White [mailto:g.white@CableLabs.com] > Sent: donderdag 13 februari 2003 20:07 > To: Wijnen, Bert (Bert); Eduardo Cardona; Ipcdn (E-mail) > Subject: RE: [ipcdn] quick review of draft-ietf-ipcdn-qos-mib-07.txt > > > It is important that the range for docsQosPktClassVlanId include the > value 0: > > If the referenced parameter is not present in the > classifier, the value of this object is reported > as 0. > Well, yours also goes up to (and inclusive) 4095 while bridgemib only goes up to (and inclusive 4094). If zero is not a valid VLAN ID and you want to niclude it as not present, then maybe yours should be renamed to docsQosPktClassVlanIdOrNone or some such Bert > -Greg > > -----Original Message----- > From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] > Sent: Thursday, February 13, 2003 11:44 AM > To: Eduardo Cardona; Wijnen, Bert (Bert); Ipcdn (E-mail) > Subject: RE: [ipcdn] quick review of draft-ietf-ipcdn-qos-mib-07.txt > > > Eduardo writes: > > > > FYI > > Could be in other places but a starting point. > > > > draft-ietf-bridge-bridgemib-01.txt > > > > VlanId ::= TEXTUAL-CONVENTION > > STATUS current > > DESCRIPTION > > "The 12-bit VLAN ID used in the VLAN Tag header." > > SYNTAX INTEGER (1..4094) > > > And so... why does yours differ > docsQosPktClassVlanId OBJECT-TYPE > SYNTAX Integer32 (0..4095) > MAX-ACCESS read-only > STATUS current > > I am not claiming that one is better than the other. > But I always wonder why they are different. > Best to try and get in touch with the bridgemib people > > Bert > _______________________________________________ > IPCDN mailing list > IPCDN@ietf.org > https://www1.ietf.org/mailman/listinfo/ipcdn > _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Thu Feb 13 17:17:47 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13059 for ; Thu, 13 Feb 2003 17:17:47 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1DML8U25309 for ipcdn-archive@odin.ietf.org; Thu, 13 Feb 2003 17:21:08 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DMJ7p25215; Thu, 13 Feb 2003 17:19:07 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DMIBp25106 for ; Thu, 13 Feb 2003 17:18:11 -0500 Received: from ondar.cablelabs.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12737 for ; Thu, 13 Feb 2003 17:14:18 -0500 (EST) Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20]) by ondar.cablelabs.com (8.12.6/8.12.6) with ESMTP id h1DMHbwH005906; Thu, 13 Feb 2003 15:17:37 -0700 (MST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: Counters and use of TC ZeroBasedCounter32/64 (was RE: [ipcdn] Review of: draft-ietf-ipcdn-bpiplus-mib-08.txt) Date: Thu, 13 Feb 2003 15:17:37 -0700 Message-ID: Thread-Topic: Counters and use of TC ZeroBasedCounter32/64 (was RE: [ipcdn] Review of: draft-ietf-ipcdn-bpiplus-mib-08.txt) Thread-Index: AcLTcy1oUzrP+TZJSta0Z6wy3lxNNQAN1SlQ From: "Jean-Francois Mule" To: "Wijnen, Bert (Bert)" , "Ipcdn (E-mail)" Cc: , "Alexander Katsnelson" , X-Approved: ondar Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1DMIBp25107 Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Bert, Thank you for all the valuable comments on bpiplus-mib-08. 2 questions for clarification on ZeroBasedCounter32/64: Re: > docsBpi2CmAuthRejects OBJECT-TYPE > SYNTAX Counter32 > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "The value of this object is the count of times the CM > has received an Authorization Reject message, > since reboot." you wrote: > require that a Counter starts at zero. But those are NOT the > semanticws of a Counter32. If this is what you want, I think you > need to use the ZeroBasedCounter32 as per RFC2021. > Pls read draft-ietf-ops-mib-review-guidelines-00.txt sect 4.6 > specifically 4.6.1.2 > You have quite a few of those objetcs Reading again through the reference above and digging the textual conventions in rfc2021 & rfc2856, I got 2 questions: 1. the descriptions of ZeroBasedCounter32/64 both define some applicability of those TCs: " Typically this TC is used in tables where the INDEX space is constantly changing and/or the TimeFilter mechanism is in use." Can we then assume that you're ok with us using those ZeroBasedCounter32/64 TCs everywhere we have a counter that is set to zero on creation and wraps up on reboot or registration. 2. Do we have to add any text in the description clause to the effect of "minimum time to wrap"? Most of the description text defines "reboot or registration" as the event when counters get reset to zero. So I think we are fine. But just to be sure, those TCs define: "Provided that an application discovers the new object within the minimum time to wrap it can use the initial value as a delta since it last polled the table of which this object is part. It is important for a management station to be aware of this minimum time and the actual time between polls, and to discard data if the actual time is too long or there is no defined minimum time." Can we assume we are ok there? Jean-Francois. _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Thu Feb 13 17:54:56 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16660 for ; Thu, 13 Feb 2003 17:54:56 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1DMwGd27599 for ipcdn-archive@odin.ietf.org; Thu, 13 Feb 2003 17:58:16 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DMu6p27521; Thu, 13 Feb 2003 17:56:06 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DMtkp27470 for ; Thu, 13 Feb 2003 17:55:46 -0500 Received: from hoemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16196 for ; Thu, 13 Feb 2003 17:51:55 -0500 (EST) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h1DMtbj14549 for ; Thu, 13 Feb 2003 17:55:37 -0500 (EST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Thu, 13 Feb 2003 23:55:36 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155E64CE5@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: Jean-Francois Mule , "Wijnen, Bert (Bert)" , "Ipcdn (E-mail)" Cc: stu.green@arrisi.com, Alexander Katsnelson , k.ozawa@cablelabs.com Date: Thu, 13 Feb 2003 23:55:30 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [ipcdn] RE: Counters and use of TC ZeroBasedCounter32/64 (was RE: [ipcdn] Review of: draft-ietf-ipcdn-bpiplus-mib-08.txt) Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Inline. > 2 questions for clarification on ZeroBasedCounter32/64: > Re: > > docsBpi2CmAuthRejects OBJECT-TYPE > > SYNTAX Counter32 > > MAX-ACCESS read-only > > STATUS current > > DESCRIPTION > > "The value of this object is the count of times the CM > > has received an Authorization Reject message, since reboot." > > you wrote: > > require that a Counter starts at zero. But those are NOT the > > semanticws of a Counter32. If this is what you want, I think you > > need to use the ZeroBasedCounter32 as per RFC2021. > > Pls read draft-ietf-ops-mib-review-guidelines-00.txt sect 4.6 > > specifically 4.6.1.2 > > You have quite a few of those objetcs > > Reading again through the reference above and digging the textual > conventions in rfc2021 & rfc2856, I got 2 questions: > > > 1. the descriptions of ZeroBasedCounter32/64 both define some > applicability of those TCs: > " Typically this TC is used in tables where the INDEX space is > constantly changing and/or the TimeFilter mechanism is in use." > Can we then assume that you're ok with us using those > ZeroBasedCounter32/64 TCs everywhere we have a counter that is set to > zero on creation and wraps up on reboot or registration. > In many cases, I (we as MIB dcotors) do not like Counters that are supposed to start at zero at all. However, in some cases it is acceptable. I believe in your case this is so, that is why I made the suggestion to use those TCs. As (I think I also said), pls take a look at http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-00.txt Specifically section 4.6.1.2 which says: 4.6.1.2. Counter32 and Counter64 Counter32 and Counter64 have special semantics as described in RFC 2578 Sections 7.1.6 and 7.1.10 respectively. Object definitions MUST (and textual conventions SHOULD) respect these semantics. That means: - It is OK to use Counter32/64 for counters that can reset themselves on unusual/irregular events (e.g., counters maintained on a line card may be reset when the line card is reset), and it is not illegal if their value after the reset happens to be zero (i.e., it does not have to be non-zero). So, "counters that can reset to zero" is not automatically wrong for Counter32/64. However, if it is possible for such resets to occur, then a discontinuity indicator object SHOULD be provided to indicate when the last such reset occurred. - It is NOT OK to put in the DESCRIPTION clause of a Counter32/64 that there is a requirement that on a discontinuity the counter MUST reset to zero. - It is NOT OK to put in the DESCRIPTION clause of a Counter32/64 that there is a requirement that it MUST reset at any specific time/event (e.g., midnight). - It is NOT OK for one manager to request the agent to reset the value of counter(s) to zero, and Counter32/64 is the wrong syntax for "counters" which regularly reset themselves to zero. For the latter it is better to define or use textual conventions such as those in RFC 2493 [RFC2493]. There also exist closely-related textual conventions ZeroBasedCounter32 and ZeroBasedCounter64 defined in RMON2-MIB [RFC2021] and HCNUM-TC [RFC2856], respectively. The only difference between ZeroBasedCounter32/64 TCs and Counter32/64 is their starting value; at time=X, where X is their minimum-wrap-time after they were created, the behaviour of ZeroBasedCounter32/64 becomes exactly the same as Counter32/64. Thus, the preceeding paragraphs/rules apply not only to Counter32/64, but also to ZeroBasedCounter32/64 TCs. Specifically that last para is important. So people who use the ZeroBasedCounterxx have to be carefull that a wrap of the counter makes it just a regular Counter32, and so it is not longer usefull to do something with a single value, only with a difference between two values. > 2. Do we have to add any text in the description clause to > the effect of "minimum time to wrap"? > Most of the description text defines "reboot or registration" as the > event when counters get reset to zero. So I think we are fine. So I don't think that they "reset to zero", they start at zero the at the time they come into existence. > But just to be sure, those TCs define: > "Provided that an application discovers the new object within > the minimum time to wrap it can use the initial value as a > delta since it last polled the table of which this object is > part. It is important for a management station to be aware > of this minimum time and the actual time between polls, and > to discard data if the actual time is too long or there is > no defined minimum time." > Can we assume we are ok there? > So if you use the TC, then the DESCRIPTION clause of the TC already explains this, and so people who use your objects that have this TC as their SYNTAX should be able to udnerstand from that what exactly the constraints are. So yes, I think you are then OK. Bert > Jean-Francois. > _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Fri Feb 14 12:48:58 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28571 for ; Fri, 14 Feb 2003 12:48:58 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1EHqfJ11113 for ipcdn-archive@odin.ietf.org; Fri, 14 Feb 2003 12:52:41 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1EHoTp10994; Fri, 14 Feb 2003 12:50:29 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1EHn3p10931 for ; Fri, 14 Feb 2003 12:49:03 -0500 Received: from peacock.tci.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28493 for ; Fri, 14 Feb 2003 12:44:48 -0500 (EST) Received: from mms01-relaya.tci.com (mms01-relaya.broadband.att.com [147.191.90.228]) by peacock.tci.com (8.12.2/8.12.2) with ESMTP id h1EHm6JE012616 for ; Fri, 14 Feb 2003 10:48:32 -0700 (MST) Received: from 147.191.90.10 by mms01-relaya.tci.com with ESMTP ( Tumbleweed MMS SMTP Relay (MMS v5.5.0)); Fri, 14 Feb 2003 10:48:23 -0600 Received: by entexchimc03.broadband.att.com with Internet Mail Service ( 5.5.2653.19) id ; Fri, 14 Feb 2003 10:47:02 -0700 Message-ID: <6732623D2548D61193C90002A5C88DCC05663682@entmaexch02.broadband.att.com> From: "Woundy, Richard" To: "IPCDN WG (E-mail)" Date: Fri, 14 Feb 2003 10:48:20 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) X-WSS-ID: 1253F46D591564-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [ipcdn] Post-interim meeting updates to the www.ipcdn.org website Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Folks, I have posted all of the presentations from the WG Interim meeting on our website: . The meeting minutes will be ready by late next week. Also, I made a few minor tweaks to our internet-drafts list, . I have to find out why the DOCSIS Event Notification MIB still hasn't been posted on the IETF website, but you can still obtain the latest copy from our IPCDN website. -- Rich _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Tue Feb 18 07:11:51 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26051 for ; Tue, 18 Feb 2003 07:11:51 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1ICHQd21928 for ipcdn-archive@odin.ietf.org; Tue, 18 Feb 2003 07:17:26 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1ICFSp21857; Tue, 18 Feb 2003 07:15:28 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1ICEqp21816 for ; Tue, 18 Feb 2003 07:14:52 -0500 Received: from ihemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26012 for ; Tue, 18 Feb 2003 07:08:47 -0500 (EST) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h1ICCYZ14536 for ; Tue, 18 Feb 2003 07:12:34 -0500 (EST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Tue, 18 Feb 2003 13:12:33 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155E6541E@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Ipcdn (E-mail)" Cc: "Thomas Narten (E-mail)" , "Erik Nordmark (E-mail)" , "Randy Bush (E-mail)" Date: Tue, 18 Feb 2003 13:12:30 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [ipcdn] InetAddress or PrefixLength as a mask Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , DDDDDuring the IPCDN WG interim meeting last week I question why in docsBpi2CmtsIpMulticastMask OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "This object represents the IP multicast address mask for this row. An IP multicast address matches this row if the logical AND of the address with docsBpi2CmtsIpMulticastMask is identical to the logical AND of docsBpi2CmtsIpMulticastAddr with docsBpi2CmtsIpMulticastMask." ::= { docsBpi2CmtsIpMulticastMapEntry 5 } You specify the mask as an InetAddress and not as an InetAddressPrefixLength. I was given some explanations, but I am not 100% sure I understood and I am not 100% sure they are valid. Could the authors pls respond with an explanation (which I think should also be inclued in the DESCRIPTION clause if it is accepted). There may be other occurences of this in one ore more of your MIB documents. Thanks, Bert _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Wed Feb 19 08:20:55 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24236 for ; Wed, 19 Feb 2003 08:20:55 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1JDR0x08864 for ipcdn-archive@odin.ietf.org; Wed, 19 Feb 2003 08:27:00 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JDLWp08632; Wed, 19 Feb 2003 08:21:32 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JDJBp08488 for ; Wed, 19 Feb 2003 08:19:11 -0500 Received: from SCBH02.terayon.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24106 for ; Wed, 19 Feb 2003 08:12:35 -0500 (EST) Received: by SCBH02.terayon.com with Internet Mail Service (5.5.2653.19) id <1NZ04JJ1>; Wed, 19 Feb 2003 05:16:06 -0800 Message-ID: From: "Raftus, David" To: "'Minnie Lu'" , "Raftus, David" Cc: docsis-oss@cablelabs.com, ipcdn@ietf.org Date: Wed, 19 Feb 2003 05:16:12 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [ipcdn] RE: Q of rfmibv2-05 docsIfCmtsChannelUtiliaztionTable Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Hi Minnie, Please see replies inline. Thanks, Dave ************************************ David Raftus Imedia Semiconductor 340 Terry Fox Drive, Suite 202 Ottawa Canada K2K 3A2 david.raftus@imedia.com 613.592.1052 ext 222 ************************************ -----Original Message----- From: Minnie Lu [mailto:milu@cisco.com] Sent: Tuesday, February 18, 2003 8:18 PM To: Raftus, David Cc: docsis-oss@cablelabs.com; ipcdn@ietf.org; milu@cisco.com Subject: Q of rfmibv2-05 docsIfCmtsChannelUtiliaztionTable Hi, David, I have questions about the docsIfCmtsChannelUtilizationTable in draft-ietf-ipcdn-docs-rfmibv2-05.txt. Appreciate your help in advance ! Q1. docsIfCmtsChannelUtIfType : Is it the same meaning as Upstream or Downstream ifType in ifTable ? Yes, limited to US/DS iana values. As the description says: Indicates the IANA interface type associated with this physical channel. Only docsCableDownstreamInterface (128) and docsCableUpstreamInterface (129) are valid. Q2: docsIfCmtsChannelUtId: Is it the same meaning as docsIfDownChannelId for Downstream and docsIfUpChannelId for Upstream ? If yes, why is the range different ? Yes. The range extension is an oversite. However, I see no harm. The downChannelId and upChannelId are 0..255. Even though the docsIfCmtsChannelUtId is given the full int32 range, there is no reason to use more than 0..255. If I ever get around to v6 (sigh), I'll fix it. Q3: If yes for both Q1 and Q2, why does this table need so many indexes ? I think ifIndex itself is good enough to identify a entry in this table. Minnie, this was done as a convenience to operators. As stated in the discussion leading to the issuance of this mib, this approach allows an operator to receive all statistics for a single channel on a single line. A walk of this table will provide a single line utilization figure for each channel. Eg: .6.128.12 = 80% .7.128.13 = 85% .8.129.17 = 90%, etc Please correct me if I miss anything. Thanks a lot ! Minnie _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Wed Feb 19 09:24:31 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25733 for ; Wed, 19 Feb 2003 09:24:31 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1JEUc513709 for ipcdn-archive@odin.ietf.org; Wed, 19 Feb 2003 09:30:38 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JES7p13559; Wed, 19 Feb 2003 09:28:07 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1J1KOp10724 for ; Tue, 18 Feb 2003 20:20:24 -0500 Received: from sj-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13999 for ; Tue, 18 Feb 2003 20:14:00 -0500 (EST) Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17]) by sj-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h1J1HhSQ013142; Tue, 18 Feb 2003 17:17:43 -0800 (PST) Received: from milu-w2k.cisco.com (anhan-w2-6.cisco.com [171.71.51.1]) by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA) with ESMTP id ADN28514; Tue, 18 Feb 2003 17:17:42 -0800 (PST) Message-Id: <4.3.2.7.2.20030218170541.048de988@mira-sjc5-1.cisco.com> X-Sender: milu@mira-sjc5-1.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 18 Feb 2003 17:17:41 -0800 To: "Raftus, David" From: Minnie Lu Cc: docsis-oss@cablelabs.com, ipcdn@ietf.org, milu@cisco.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [ipcdn] Q of rfmibv2-05 docsIfCmtsChannelUtiliaztionTable Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Hi, David, I have questions about the docsIfCmtsChannelUtilizationTable in draft-ietf-ipcdn-docs-rfmibv2-05.txt. Appreciate your help in advance ! Q1. docsIfCmtsChannelUtIfType : Is it the same meaning as Upstream or Downstream ifType in ifTable ? Q2: docsIfCmtsChannelUtId: Is it the same meaning as docsIfDownChannelId for Downstream and docsIfUpChannelId for Upstream ? If yes, why is the range different ? Q3: If yes for both Q1 and Q2, why does this table need so many indexes ? I think ifIndex itself is good enough to identify a entry in this table. Please correct me if I miss anything. Thanks a lot ! Minnie _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Wed Feb 19 10:04:04 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27003 for ; Wed, 19 Feb 2003 10:04:04 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1JFAC317496 for ipcdn-archive@odin.ietf.org; Wed, 19 Feb 2003 10:10:12 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JF85p17375; Wed, 19 Feb 2003 10:08:05 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JF7Wp17326 for ; Wed, 19 Feb 2003 10:07:32 -0500 Received: from snowmass.tci.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26806 for ; Wed, 19 Feb 2003 10:00:53 -0500 (EST) Received: from mms01-relaya.tci.com (mms01-relaya.broadband.att.com [147.191.90.228]) by snowmass.tci.com (8.12.2/8.12.2) with ESMTP id h1JF4g84008299; Wed, 19 Feb 2003 08:04:42 -0700 (MST) Received: from 147.191.90.11 by mms01-relayb.tci.com with ESMTP ( Tumbleweed MMS SMTP Relay (MMS v5.5.0)); Wed, 19 Feb 2003 08:04:32 -0600 Received: by entexchimc04.broadband.att.com with Internet Mail Service ( 5.5.2653.19) id <1RRPR3WG>; Wed, 19 Feb 2003 08:03:54 -0700 Message-ID: <6732623D2548D61193C90002A5C88DCC056636AF@entmaexch02.broadband.att.com> From: "Woundy, Richard" To: "'Wijnen, Bert (Bert)'" , "IPCDN WG (E-mail)" cc: "Thomas Narten (E-mail)" , "Erik Nordmark (E-mail)" , "Randy Bush (E-mail)" Subject: RE: [ipcdn] InetAddress or PrefixLength as a mask Date: Wed, 19 Feb 2003 08:04:29 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) X-WSS-ID: 124D428A1091004-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Bert, Since I am the person that most likely influenced the BPI+ MIB's use of a netmask rather than a prefix length, I suppose I should directly answer your question. (Of course, that makes your suggestion about putting the explanation in the DESCRIPTION clause all the wiser.) The IPv6 addressing architecture is currently defined in RFC 2373. Section 2.7 describes the format of the IPv6 multicast addresses: 8 bits of '11111111' for identification as multicast, 4 bits of 'flags', 4 bits of 'scope', and 112 bits of 'group ID'. Five scope values are defined for node-local, link-local, site-local, organization-local, and global scopes. Section 2.7.2 shows how new IPv6 multicast addresses can be assigned, making reference to RFC 2375. The draft draft-ietf-ipngwg-addr-arch-v3-11.txt, which updates RFC 2373, defines six scope values: interface-local, link-local, admin-local, site-local, organization-local, and global scopes. Some of the permanently assigned IPv6 multicast addresses appear in RFC 2375. This RFC includes all-scope addresses in section 3.0 -- these multicast address assignments apply for all IPv6 multicast scope contexts. Typically, these assignments are written as "FF0X:...". These assignments are referred to as "Variable Scope Multicast Addresses" by IANA, . As an operator, I would strongly prefer to use one row in the BPI+ MIB table to match each of these variable-scope permanently assigned addresses. I want to avoid creating five to six rows (one per defined multicast scope) or sixteen rows (one per potential multicast scope). Unfortunately, every prefix of an IPv6 multicast address that contains at least one bit of the 'group ID' MUST contain the entire 'flags' and 'scope' components. The only way to perform an address match based solely on 'group ID' while ignoring the 'scope' is to use a non-contiguous netmask. If there is a better way to accomplish this, I would love to learn about it. -- Rich -----Original Message----- From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] Sent: Tuesday, February 18, 2003 7:13 AM To: Ipcdn (E-mail) Cc: Thomas Narten (E-mail); Erik Nordmark (E-mail); Randy Bush (E-mail) Subject: [ipcdn] InetAddress or PrefixLength as a mask During the IPCDN WG interim meeting last week I question why in docsBpi2CmtsIpMulticastMask OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "This object represents the IP multicast address mask for this row. An IP multicast address matches this row if the logical AND of the address with docsBpi2CmtsIpMulticastMask is identical to the logical AND of docsBpi2CmtsIpMulticastAddr with docsBpi2CmtsIpMulticastMask." ::= { docsBpi2CmtsIpMulticastMapEntry 5 } You specify the mask as an InetAddress and not as an InetAddressPrefixLength. I was given some explanations, but I am not 100% sure I understood and I am not 100% sure they are valid. Could the authors pls respond with an explanation (which I think should also be inclued in the DESCRIPTION clause if it is accepted). There may be other occurences of this in one ore more of your MIB documents. Thanks, Bert _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Wed Feb 19 10:09:00 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27377 for ; Wed, 19 Feb 2003 10:09:00 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1JFF8f17787 for ipcdn-archive@odin.ietf.org; Wed, 19 Feb 2003 10:15:08 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JFD2p17709; Wed, 19 Feb 2003 10:13:02 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JFC6p17662 for ; Wed, 19 Feb 2003 10:12:06 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27214; Wed, 19 Feb 2003 10:05:28 -0500 (EST) Message-Id: <200302191505.KAA27214@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ipcdn@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Wed, 19 Feb 2003 10:05:28 -0500 Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-subscriber-mib-09.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over Cable Data Network Working Group of the IETF. Title : MManagement Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modem Termination Systems for Subscriber Management Author(s) : W. Sawyer Filename : draft-ietf-ipcdn-subscriber-mib-09.txt Pages : 28 Date : 2003-2-18 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a set of managed objects for SNMP-based management of Data-over-Cable Service Interface Specification (DOCSIS)-compliant Cable Modem Termination Systems. These managed objects facilitate protection of the cable network from misuse by subscribers. This memo is a product of the IPCDN working group within the Internet Engineering Task Force. Comments are solicited and should be addressed to the working group's mailing list at ipcdn@ietf.org and/or the author. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-subscriber-mib-09.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipcdn-subscriber-mib-09.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipcdn-subscriber-mib-09.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-2-18160438.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipcdn-subscriber-mib-09.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipcdn-subscriber-mib-09.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-2-18160438.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Wed Feb 19 17:10:55 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10743 for ; Wed, 19 Feb 2003 17:10:54 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1JMHAi14812 for ipcdn-archive@odin.ietf.org; Wed, 19 Feb 2003 17:17:10 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JMF9p14469; Wed, 19 Feb 2003 17:15:09 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JLapp11340 for ; Wed, 19 Feb 2003 16:36:51 -0500 Received: from sj-msg-core-3.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09301 for ; Wed, 19 Feb 2003 16:30:04 -0500 (EST) Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17]) by sj-msg-core-3.cisco.com (8.12.2/8.12.6) with ESMTP id h1JLXfB6017976; Wed, 19 Feb 2003 13:33:41 -0800 (PST) Received: from milu-w2k.cisco.com (anhan-w2-6.cisco.com [171.71.51.1]) by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA) with ESMTP id ADO30016; Wed, 19 Feb 2003 13:33:50 -0800 (PST) Message-Id: <4.3.2.7.2.20030219133147.04692e50@mira-sjc5-1.cisco.com> X-Sender: milu@mira-sjc5-1.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 19 Feb 2003 13:33:49 -0800 To: "Raftus, David" From: Minnie Lu Cc: "'Minnie Lu'" , docsis-oss@cablelabs.com, ipcdn@ietf.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [ipcdn] RE: Q of rfmibv2-05 docsIfCmtsChannelUtiliaztionTable Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Hi, David, Thanks for helping me understanding this table. Maybe in next revision, adding some comments as you explained to me in the MIB file will also help other people just in case they would have the same questions as me.;-) Thanks again! Minnie At 05:16 AM 2/19/2003 -0800, Raftus, David wrote: >Hi Minnie, > >Please see replies inline. > >Thanks, >Dave > >************************************ >David Raftus >Imedia Semiconductor >340 Terry Fox Drive, Suite 202 >Ottawa Canada K2K 3A2 > >david.raftus@imedia.com >613.592.1052 ext 222 >************************************ > > >-----Original Message----- >From: Minnie Lu [mailto:milu@cisco.com] >Sent: Tuesday, February 18, 2003 8:18 PM >To: Raftus, David >Cc: docsis-oss@cablelabs.com; ipcdn@ietf.org; milu@cisco.com >Subject: Q of rfmibv2-05 docsIfCmtsChannelUtiliaztionTable > >Hi, David, > > I have questions about the docsIfCmtsChannelUtilizationTable in >draft-ietf-ipcdn-docs-rfmibv2-05.txt. Appreciate your help in advance ! > > Q1. docsIfCmtsChannelUtIfType : > Is it the same meaning as Upstream or Downstream ifType in >ifTable ? > Yes, limited to US/DS iana values. As the description says: >Indicates the IANA interface type associated with this physical channel. >Only >docsCableDownstreamInterface (128) and docsCableUpstreamInterface (129) are >valid. > > > Q2: docsIfCmtsChannelUtId: > Is it the same meaning as docsIfDownChannelId for Downstream >and docsIfUpChannelId for Upstream ? > If yes, why is the range different ? > Yes. The range extension is an oversite. However, I see no harm. The >downChannelId and upChannelId are 0..255. Even though the >docsIfCmtsChannelUtId is given the full int32 range, there is no reason to >use more than 0..255. If I ever get around to v6 (sigh), I'll fix it. > > Q3: If yes for both Q1 and Q2, why does this table need so many indexes >? I think ifIndex itself is good enough to identify a entry in this table. > Minnie, this was done as a convenience to operators. As stated in the >discussion leading to the issuance of this mib, this approach allows an >operator to receive all statistics for a single channel on a single line. A >walk of this table will provide a single line utilization figure for each >channel. >Eg: >.6.128.12 = 80% >.7.128.13 = 85% >.8.129.17 = 90%, etc > > > Please correct me if I miss anything. > > Thanks a lot ! > Minnie > > _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Wed Feb 19 18:27:51 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12722 for ; Wed, 19 Feb 2003 18:27:51 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1JNY8118695 for ipcdn-archive@odin.ietf.org; Wed, 19 Feb 2003 18:34:08 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JNW8p18575; Wed, 19 Feb 2003 18:32:08 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JNV6p18538 for ; Wed, 19 Feb 2003 18:31:06 -0500 Received: from motgate5.mot.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12554 for ; Wed, 19 Feb 2003 18:24:17 -0500 (EST) Received: from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by motgate5.mot.com (Motorola/Motgate5) with ESMTP id h1JNRtmG022016 for ; Wed, 19 Feb 2003 16:27:55 -0700 (MST) Received: [from ma07exm01.dma.isg.mot.com (ma07exm01.dma.isg.mot.com [150.21.2.102]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id QAA23455 for ; Wed, 19 Feb 2003 16:26:35 -0700 (MST)] Received: by ma07exm01.dma.isg.mot.com with Internet Mail Service (5.5.2656.59) id <1SR75HJ9>; Wed, 19 Feb 2003 18:28:06 -0500 Message-ID: <19CD0E423FC1D611893500508B6F0B9C084993@ma07exm01.dma.isg.mot.com> From: Murwin William-LWM008 To: "IPCDN (E-mail) (E-mail)" , "Docsis-Oss (E-mail) (E-mail)" Date: Wed, 19 Feb 2003 18:28:06 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Subject: [ipcdn] docsQosServiceClassName match Spec Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , A comment made from the IPCDN Interim Working Group was The docsQosServiceClassName from the DOCS-QOS-MIB did not match the Specification. After reviewing the DOCS-QOS-MIB the docsQosServiceClassName is (1..15) ASCII characters. The DOCSIS RFI Spec 2.2.3.4 say: The value of the field refers to a predefined CMTS service configuration to be used for this Service Flow. Type Length Value [24/25].4 2 to 16 Zero-terminated string of ASCII characters. Note: The length includes the terminating zero. When the Service Class Name is used in a Service Flow encoding, it indicates that all the unspecified QoS Parameters of the Service Flow need to be provided by the CMTS. It is up to the operator to synchronize the definition of Service Class Names in the CMTS and in the configuration file. NOTE: The DOCS-QOS-MIB states that this object does not include the zero-terminated character. Thus the MIB matches the Spec. ______________________________ William Murwin Broadband Communications Sector Motorola Inc. Email: W.Murwin@motorola.com Tel: (508) 851-8385 _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Thu Feb 20 07:40:50 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09760 for ; Thu, 20 Feb 2003 07:40:50 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1KClNe09109 for ipcdn-archive@odin.ietf.org; Thu, 20 Feb 2003 07:47:23 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KCj9p08965; Thu, 20 Feb 2003 07:45:09 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KCiEp08884 for ; Thu, 20 Feb 2003 07:44:14 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09275; Thu, 20 Feb 2003 07:37:11 -0500 (EST) Message-Id: <200302201237.HAA09275@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ipcdn@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 20 Feb 2003 07:37:10 -0500 Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-docsisevent-mib-02.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over Cable Data Network Working Group of the IETF. Title : Event Notification Management Information Base for DOCSIS 1.1 Compliant Cable Modems and Cable Modem Termination Systems Author(s) : J. Gao, P. Siripunkaw, D. Raftus Filename : draft-ietf-ipcdn-docsisevent-mib-02.txt Pages : 28 Date : 2003-2-19 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP- based event notification management of DOCSIS compliant Cable Modems and Cable Modem Termination Systems. This MIB is defined as an extension to the DOCSIS Cable Device MIB, RFC 2669. This memo specifies a MIB module in a manner that is compliant to the SMIv2. The set of objects is consistent with the SNMP framework and existing SNMP standards. This memo is a product of the IPCDN working group within the Internet Engineering Task Force. Comments are solicited and should be addressed to the working group's mailing list at ipcdn@ietf.org and/or the author. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docsisevent-mib-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipcdn-docsisevent-mib-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipcdn-docsisevent-mib-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-2-19142135.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipcdn-docsisevent-mib-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipcdn-docsisevent-mib-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-2-19142135.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Thu Feb 20 12:44:05 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22570 for ; Thu, 20 Feb 2003 12:44:05 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1KHoiG00404 for ipcdn-archive@odin.ietf.org; Thu, 20 Feb 2003 12:50:44 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KHmVp00353; Thu, 20 Feb 2003 12:48:31 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KHl8p32754 for ; Thu, 20 Feb 2003 12:47:08 -0500 Received: from hoemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22499 for ; Thu, 20 Feb 2003 12:39:56 -0500 (EST) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h1KHhkC00610 for ; Thu, 20 Feb 2003 12:43:46 -0500 (EST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Thu, 20 Feb 2003 18:43:45 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155F7C32E@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Ipcdn (E-mail)" Cc: bwijnen@lucent.com, "Erik Nordmark (E-mail)" , "Thomas Narten (E-mail)" Date: Thu, 20 Feb 2003 18:43:00 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [ipcdn] RE: Tos field - draft-ietf-ipcdn-subscriber-mib-09.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , I asked this question (at the bottom of this email) to a few experts, and Erik cam back with this answer. So can you please evaluate this issue and respond. Bert -----Original Message----- From: Erik Nordmark [mailto:Erik.Nordmark@sun.com] Sent: donderdag 20 februari 2003 14:58 To: Wijnen, Bert (Bert) Cc: Thomas Narten (E-mail); Erik Nordmark (E-mail); Randy Bush (E-mail) Subject: Re: Tos field > Now... this is IPv4 only... So I wonder > - should they say something about that? > - should they deal with IPv6 traffic class as well, or at least > mention it? They do deal with IPv6 packets, so it seems strange > to not make clear that ToS filed is is IPv4 only, no? > Their RFC2669 talks about Tos as well.. so maybe they just > inherited it. If the MIB does v4 and v6 it would make sense to calls this DSCP and have it apply across both. Also, I think it should be explicitly restricted to the DSCP bits and not be able to filter on the ECN bits - too high risk that somebody could accidentially break ECN. I hope they are not assuming the old IPv4 ToS definitions. Erik > -----Original Message----- > From: Wijnen, Bert (Bert) > Sent: dinsdag 18 februari 2003 13:02 > To: Thomas Narten (E-mail); Erik Nordmark (E-mail) > Cc: Randy Bush (E-mail) > Subject: Tos field > > The draft-ietf-ipcdn-subscriber-mib-09.txt > (which should show up today, but revision 8 has the same) > has these definitions (around page 14/15): > > docsSubMgtPktFilterTosValue OBJECT-TYPE > SYNTAX OCTET STRING (SIZE(1)) > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "The TOS value to match in the IP packet." > DEFVAL { '00'h } > ::= { docsSubMgtPktFilterEntry 9 } > > docsSubMgtPktFilterTosMask OBJECT-TYPE > SYNTAX OCTET STRING(SIZE(1)) > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "The mask to apply against the TOS value to be matched in the > IP packet. The default for both these objects taken together > matches all TOS values. A packet matches this filter if the > following is true: > AND (FilterTosValue, FilterTosMask) == > AND (Packet TOS Value, FilterTosMask)." > DEFVAL { '00'h } > ::= { docsSubMgtPktFilterEntry 10 } > > Now... this is IPv4 only... So I wonder > - should they say something about that? > - should they deal with IPv6 traffic class as well, or at least > mention it? They do deal with IPv6 packets, so it seems strange > to not make clear that ToS filed is is IPv4 only, no? > Their RFC2669 talks about Tos as well.. so maybe they just > inherited it. > > Something that botters me now that I investigated it somewhat: > - RFC2096 has it defined as an Integer32 > ipCidrRouteTos OBJECT-TYPE > SYNTAX Integer32 > - RFC2669 defines it as OCTET-STRING SIZE(1) > docsDevFilterIpTos OBJECT-TYP > SYNTAX OCTET STRING ( SIZE (1)) > So does this new docsSubMIB draft > - RFC1850 defines a TC for it > TOSType ::= TEXTUAL-CONVENTION > SYNTAX Integer32 (0..30) > - RFC2925 says: > pingCtlDSField OBJECT-TYPE > SYNTAX Unsigned32 (0..255) > DESCRIPTION > "Specifies the value to store in the Differentiated > Services (DS) Field in the IP packet used to > encapsulate the ping probe. The DS Field is defined > as the Type of Service (TOS) octet in a IPv4 header > or as the Traffic Class octet in a IPv6 header. > - RFC2584 does things totally different again.. but it is > SAN APPN, so I won't bother anymore (I think) > - RFC3289 defines a Dscp and DscpOrAny TC which I think for > IPv4 also travels in the ToS field, does it not? > Dscp ::= TEXTUAL-CONVENTION > DISPLAY-HINT "d" > STATUS current > DESCRIPTION > "A Differentiated Services Code-Point that may be used for > marking a traffic stream." > REFERENCE > "RFC 2474, RFC 2780" > SYNTAX Integer32 (0..63) > > DscpOrAny ::= TEXTUAL-CONVENTION > DISPLAY-HINT "d" > STATUS current > DESCRIPTION > "The IP header Differentiated Services Code-Point that may be > used for discriminating among traffic streams. The value -1 is > used to indicate a wild card i.e. any value." > REFERENCE > "RFC 2474, RFC 2780" > SYNTAX Integer32 (-1 | 0..63) > > > Oh well... we know how to get ourselves in a mess. > > Thanks, > Bert > _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Thu Feb 20 14:43:11 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27036 for ; Thu, 20 Feb 2003 14:43:11 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1KJnqJ10029 for ipcdn-archive@odin.ietf.org; Thu, 20 Feb 2003 14:49:52 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KJm6p09933; Thu, 20 Feb 2003 14:48:06 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KJlwp09912 for ; Thu, 20 Feb 2003 14:47:58 -0500 Received: from titan.arrisi.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26972; Thu, 20 Feb 2003 14:40:44 -0500 (EST) From: Wilson.Sawyer@arrisi.com Subject: Re: [ipcdn] RE: Tos field - draft-ietf-ipcdn-subscriber-mib-09.txt To: ipcdn@ietf.org Cc: bwijnen@lucent.com, "Erik Nordmark (E-mail)" , "Ipcdn (E-mail)" , ipcdn-admin@ietf.org, "Thomas Narten (E-mail)" X-Mailer: Lotus Notes Release 5.0.9 November 16, 2001 Message-ID: Date: Thu, 20 Feb 2003 14:40:18 -0500 X-MIMETrack: Serialize by Router on Titan/Arris(Release 5.0.9a |January 7, 2002) at 02/20/2003 02:44:13 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , What is the sense of the working group? Both the IPv6 Traffic Class octet and the old IPv4 ToS byte are currently defined as a 6-bit DSCP plus a 2-bit ECN. As a practical matter, there are still other network devices out there which use arbitrary 8-bit 'ToS' values. The TosMask already allows us to exclude the ECN bits if desired (although not automatically). A minimal change would add references to IPv6 Traffic Class in the description. Or we can go further to explicitly state that the low-order ECN bits will be treated as zero. - Wilson "Wijnen, Bert (Bert)" To: "Ipcdn (E-mail)" , "Thomas Narten (E-mail)" Sent by: Subject: [ipcdn] RE: Tos field - draft-ietf-ipcdn-subscriber-mib-09.txt ipcdn-admin@ietf. org 02/20/03 12:43 PM I asked this question (at the bottom of this email) to a few experts, and Erik cam back with this answer. So can you please evaluate this issue and respond. Bert -----Original Message----- From: Erik Nordmark [mailto:Erik.Nordmark@sun.com] Sent: donderdag 20 februari 2003 14:58 To: Wijnen, Bert (Bert) Cc: Thomas Narten (E-mail); Erik Nordmark (E-mail); Randy Bush (E-mail) Subject: Re: Tos field > Now... this is IPv4 only... So I wonder > - should they say something about that? > - should they deal with IPv6 traffic class as well, or at least > mention it? They do deal with IPv6 packets, so it seems strange > to not make clear that ToS filed is is IPv4 only, no? > Their RFC2669 talks about Tos as well.. so maybe they just > inherited it. If the MIB does v4 and v6 it would make sense to calls this DSCP and have it apply across both. Also, I think it should be explicitly restricted to the DSCP bits and not be able to filter on the ECN bits - too high risk that somebody could accidentially break ECN. I hope they are not assuming the old IPv4 ToS definitions. Erik > -----Original Message----- > From: Wijnen, Bert (Bert) > Sent: dinsdag 18 februari 2003 13:02 > To: Thomas Narten (E-mail); Erik Nordmark (E-mail) > Cc: Randy Bush (E-mail) > Subject: Tos field > > The draft-ietf-ipcdn-subscriber-mib-09.txt > (which should show up today, but revision 8 has the same) > has these definitions (around page 14/15): > > docsSubMgtPktFilterTosValue OBJECT-TYPE > SYNTAX OCTET STRING (SIZE(1)) > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "The TOS value to match in the IP packet." > DEFVAL { '00'h } > ::= { docsSubMgtPktFilterEntry 9 } > > docsSubMgtPktFilterTosMask OBJECT-TYPE > SYNTAX OCTET STRING(SIZE(1)) > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "The mask to apply against the TOS value to be matched in the > IP packet. The default for both these objects taken together > matches all TOS values. A packet matches this filter if the > following is true: > AND (FilterTosValue, FilterTosMask) == > AND (Packet TOS Value, FilterTosMask)." > DEFVAL { '00'h } > ::= { docsSubMgtPktFilterEntry 10 } > > Now... this is IPv4 only... So I wonder > - should they say something about that? > - should they deal with IPv6 traffic class as well, or at least > mention it? They do deal with IPv6 packets, so it seems strange > to not make clear that ToS filed is is IPv4 only, no? > Their RFC2669 talks about Tos as well.. so maybe they just > inherited it. > > Something that botters me now that I investigated it somewhat: > - RFC2096 has it defined as an Integer32 > ipCidrRouteTos OBJECT-TYPE > SYNTAX Integer32 > - RFC2669 defines it as OCTET-STRING SIZE(1) > docsDevFilterIpTos OBJECT-TYP > SYNTAX OCTET STRING ( SIZE (1)) > So does this new docsSubMIB draft > - RFC1850 defines a TC for it > TOSType ::= TEXTUAL-CONVENTION > SYNTAX Integer32 (0..30) > - RFC2925 says: > pingCtlDSField OBJECT-TYPE > SYNTAX Unsigned32 (0..255) > DESCRIPTION > "Specifies the value to store in the Differentiated > Services (DS) Field in the IP packet used to > encapsulate the ping probe. The DS Field is defined > as the Type of Service (TOS) octet in a IPv4 header > or as the Traffic Class octet in a IPv6 header. > - RFC2584 does things totally different again.. but it is > SAN APPN, so I won't bother anymore (I think) > - RFC3289 defines a Dscp and DscpOrAny TC which I think for > IPv4 also travels in the ToS field, does it not? > Dscp ::= TEXTUAL-CONVENTION > DISPLAY-HINT "d" > STATUS current > DESCRIPTION > "A Differentiated Services Code-Point that may be used for > marking a traffic stream." > REFERENCE > "RFC 2474, RFC 2780" > SYNTAX Integer32 (0..63) > > DscpOrAny ::= TEXTUAL-CONVENTION > DISPLAY-HINT "d" > STATUS current > DESCRIPTION > "The IP header Differentiated Services Code-Point that may be > used for discriminating among traffic streams. The value -1 is > used to indicate a wild card i.e. any value." > REFERENCE > "RFC 2474, RFC 2780" > SYNTAX Integer32 (-1 | 0..63) > > > Oh well... we know how to get ourselves in a mess. > > Thanks, > Bert > _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Thu Feb 20 17:20:09 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01817 for ; Thu, 20 Feb 2003 17:20:09 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1KMQtp21423 for ipcdn-archive@odin.ietf.org; Thu, 20 Feb 2003 17:26:55 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KMP9p21365; Thu, 20 Feb 2003 17:25:09 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KMO6p21312 for ; Thu, 20 Feb 2003 17:24:06 -0500 Received: from hoemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01700; Thu, 20 Feb 2003 17:16:47 -0500 (EST) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h1KMKav11581; Thu, 20 Feb 2003 17:20:36 -0500 (EST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Thu, 20 Feb 2003 23:20:35 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155F7C377@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: Wilson.Sawyer@arrisi.com, ipcdn@ietf.org Cc: bwijnen@lucent.com, "Erik Nordmark (E-mail)" , "Ipcdn (E-mail)" , ipcdn-admin@ietf.org, "Thomas Narten (E-mail)" Subject: RE: [ipcdn] RE: Tos field - draft-ietf-ipcdn-subscriber-mib-09.tx t Date: Thu, 20 Feb 2003 23:20:34 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , I think the suggestion from Erik seemed more to be to use the Dscp or DscpOrAny TC from RFC3289. Thanks, Bert > -----Original Message----- > From: Wilson.Sawyer@arrisi.com [mailto:Wilson.Sawyer@arrisi.com] > Sent: donderdag 20 februari 2003 20:40 > To: ipcdn@ietf.org > Cc: bwijnen@lucent.com; Erik Nordmark (E-mail); Ipcdn (E-mail); > ipcdn-admin@ietf.org; Thomas Narten (E-mail) > Subject: Re: [ipcdn] RE: Tos field - > draft-ietf-ipcdn-subscriber-mib-09.txt > > > > What is the sense of the working group? > > Both the IPv6 Traffic Class octet and the old IPv4 ToS byte > are currently > defined as a 6-bit DSCP plus a 2-bit ECN. As a practical > matter, there are > still other network devices out there which use arbitrary 8-bit 'ToS' > values. > > The TosMask already allows us to exclude the ECN bits if > desired (although > not automatically). > > A minimal change would add references to IPv6 Traffic Class in the > description. > > Or we can go further to explicitly state that the low-order > ECN bits will > be treated as zero. > > - Wilson > > > > > > "Wijnen, Bert > > (Bert)" To: > "Ipcdn (E-mail)" > bwijnen@lucent.com, "Erik Nordmark (E-mail)" > om> > , "Thomas Narten (E-mail)" > > Sent by: Subject: > [ipcdn] RE: Tos field - draft-ietf-ipcdn-subscriber-mib-09.txt > ipcdn-admin@ietf. > > org > > > > > > 02/20/03 12:43 PM > > > > > > > > > > I asked this question (at the bottom of this email) > to a few experts, and Erik cam back with this answer. > So can you please evaluate this issue and respond. > > Bert > -----Original Message----- > From: Erik Nordmark [mailto:Erik.Nordmark@sun.com] > Sent: donderdag 20 februari 2003 14:58 > To: Wijnen, Bert (Bert) > Cc: Thomas Narten (E-mail); Erik Nordmark (E-mail); Randy > Bush (E-mail) > Subject: Re: Tos field > > > > Now... this is IPv4 only... So I wonder > > - should they say something about that? > > - should they deal with IPv6 traffic class as well, or at least > > mention it? They do deal with IPv6 packets, so it seems strange > > to not make clear that ToS filed is is IPv4 only, no? > > Their RFC2669 talks about Tos as well.. so maybe they just > > inherited it. > > If the MIB does v4 and v6 it would make sense to calls this > DSCP and have it apply across both. > Also, I think it should be explicitly restricted to the DSCP bits and > not be able to filter on the ECN bits - too high risk that > somebody could > accidentially break ECN. > > I hope they are not assuming the old IPv4 ToS definitions. > > Erik > > -----Original Message----- > > From: Wijnen, Bert (Bert) > > Sent: dinsdag 18 februari 2003 13:02 > > To: Thomas Narten (E-mail); Erik Nordmark (E-mail) > > Cc: Randy Bush (E-mail) > > Subject: Tos field > > > > The draft-ietf-ipcdn-subscriber-mib-09.txt > > (which should show up today, but revision 8 has the same) > > has these definitions (around page 14/15): > > > > docsSubMgtPktFilterTosValue OBJECT-TYPE > > SYNTAX OCTET STRING (SIZE(1)) > > MAX-ACCESS read-create > > STATUS current > > DESCRIPTION > > "The TOS value to match in the IP packet." > > DEFVAL { '00'h } > > ::= { docsSubMgtPktFilterEntry 9 } > > > > docsSubMgtPktFilterTosMask OBJECT-TYPE > > SYNTAX OCTET STRING(SIZE(1)) > > MAX-ACCESS read-create > > STATUS current > > DESCRIPTION > > "The mask to apply against the TOS value to be > matched in the > > IP packet. The default for both these objects taken together > > matches all TOS values. A packet matches this filter if the > > following is true: > > AND (FilterTosValue, FilterTosMask) == > > AND (Packet TOS Value, FilterTosMask)." > > DEFVAL { '00'h } > > ::= { docsSubMgtPktFilterEntry 10 } > > > > Now... this is IPv4 only... So I wonder > > - should they say something about that? > > - should they deal with IPv6 traffic class as well, or at least > > mention it? They do deal with IPv6 packets, so it seems strange > > to not make clear that ToS filed is is IPv4 only, no? > > Their RFC2669 talks about Tos as well.. so maybe they just > > inherited it. > > > > Something that botters me now that I investigated it somewhat: > > - RFC2096 has it defined as an Integer32 > > ipCidrRouteTos OBJECT-TYPE > > SYNTAX Integer32 > > - RFC2669 defines it as OCTET-STRING SIZE(1) > > docsDevFilterIpTos OBJECT-TYP > > SYNTAX OCTET STRING ( SIZE (1)) > > So does this new docsSubMIB draft > > - RFC1850 defines a TC for it > > TOSType ::= TEXTUAL-CONVENTION > > SYNTAX Integer32 (0..30) > > - RFC2925 says: > > pingCtlDSField OBJECT-TYPE > > SYNTAX Unsigned32 (0..255) > > DESCRIPTION > > "Specifies the value to store in the Differentiated > > Services (DS) Field in the IP packet used to > > encapsulate the ping probe. The DS Field is defined > > as the Type of Service (TOS) octet in a IPv4 header > > or as the Traffic Class octet in a IPv6 header. > > - RFC2584 does things totally different again.. but it is > > SAN APPN, so I won't bother anymore (I think) > > - RFC3289 defines a Dscp and DscpOrAny TC which I think for > > IPv4 also travels in the ToS field, does it not? > > Dscp ::= TEXTUAL-CONVENTION > > DISPLAY-HINT "d" > > STATUS current > > DESCRIPTION > > "A Differentiated Services Code-Point that may be used for > > marking a traffic stream." > > REFERENCE > > "RFC 2474, RFC 2780" > > SYNTAX Integer32 (0..63) > > > > DscpOrAny ::= TEXTUAL-CONVENTION > > DISPLAY-HINT "d" > > STATUS current > > DESCRIPTION > > "The IP header Differentiated Services Code-Point that may be > > used for discriminating among traffic streams. The > value -1 is > > used to indicate a wild card i.e. any value." > > REFERENCE > > "RFC 2474, RFC 2780" > > SYNTAX Integer32 (-1 | 0..63) > > > > > > Oh well... we know how to get ourselves in a mess. > > > > Thanks, > > Bert > > > _______________________________________________ > IPCDN mailing list > IPCDN@ietf.org > https://www1.ietf.org/mailman/listinfo/ipcdn > > > > _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Fri Feb 21 18:53:24 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18899 for ; Fri, 21 Feb 2003 18:53:23 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1M00fO31402 for ipcdn-archive@odin.ietf.org; Fri, 21 Feb 2003 19:00:41 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1M00Np31394; Fri, 21 Feb 2003 19:00:23 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1LNxWp31335 for ; Fri, 21 Feb 2003 18:59:32 -0500 Received: from snowmass.tci.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18844 for ; Fri, 21 Feb 2003 18:51:44 -0500 (EST) Received: from mms01-relaya.tci.com (mms01-relaya.broadband.att.com [147.191.90.228]) by snowmass.tci.com (8.12.2/8.12.2) with ESMTP id h1LNtW84000437; Fri, 21 Feb 2003 16:55:33 -0700 (MST) Received: from 147.191.89.201 by mms01-relaya.tci.com with ESMTP ( Tumbleweed MMS SMTP Relay (MMS v5.5.0)); Fri, 21 Feb 2003 16:55:23 -0600 Received: by entexchimc02.broadband.att.com with Internet Mail Service ( 5.5.2653.19) id ; Fri, 21 Feb 2003 16:54:58 -0700 Message-ID: <6732623D2548D61193C90002A5C88DCC05663709@entmaexch02.broadband.att.com> From: "Woundy, Richard" To: "IPCDN WG (E-mail)" cc: "Bert Wijnen (E-mail)" , "Thomas Narten (E-mail)" , "Jean-Francois Mule (E-mail)" , "Woundy, Richard" Date: Fri, 21 Feb 2003 16:55:17 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) X-WSS-ID: 124863E1543792-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [ipcdn] IPCDN interim meeting minutes Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Folks, The latest edited version of the meeting minutes from last week's interim meeting of the IPCDN WG can be found at: . My deep thanks goes to Greg Nakanishi, who did most of the work into producing detailed minutes. Let me know if there are errors in the minutes (which needs to be submitted to the IETF by Monday). Errors don't include technical findings (e.g. correct VLAN ID formats) that we make after the interim meeting has concluded. Also note that all of the Powerpoint slides from the interim meeting are available on the website: . -- Richard Woundy, IPCDN Co-Chair _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Mon Feb 24 15:34:59 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25632 for ; Mon, 24 Feb 2003 15:34:58 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1OKheB22293 for ipcdn-archive@odin.ietf.org; Mon, 24 Feb 2003 15:43:40 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OKhOp22276; Mon, 24 Feb 2003 15:43:24 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OKgnp22227 for ; Mon, 24 Feb 2003 15:42:49 -0500 Received: from ondar.cablelabs.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25606 for ; Mon, 24 Feb 2003 15:33:37 -0500 (EST) Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20]) by ondar.cablelabs.com (8.12.6/8.12.6) with ESMTP id h1OKbJwJ003893; Mon, 24 Feb 2003 13:37:21 -0700 (MST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 24 Feb 2003 13:37:19 -0700 Message-ID: Thread-Topic: QoS Mib I-D draft 07 : document Header and footer thread-index: AcLaBQEV2Hbs6+PDTFKQJ2gNVhGUkwCJ331w From: "Eduardo Cardona" To: "Woundy, Richard" , "IPCDN WG (E-mail)" X-Approved: ondar Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1OKgnp22228 Subject: [ipcdn] QoS Mib I-D draft 07 : document Header and footer Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Michael, Willliam, FYI, Seems that the format is missing the ff (form feed ) 0x0c character, Extracting tools like mstrip dis not work Also the title "<" ">" in the header, shouldn't it be "DOCSIS Quality of Service MIB" ? Eduardo _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Mon Feb 24 17:40:36 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29081 for ; Mon, 24 Feb 2003 17:40:35 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1OMnKM31248 for ipcdn-archive@odin.ietf.org; Mon, 24 Feb 2003 17:49:20 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OMn8p31240; Mon, 24 Feb 2003 17:49:08 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OMmhp31222 for ; Mon, 24 Feb 2003 17:48:43 -0500 Received: from motgate.mot.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29066 for ; Mon, 24 Feb 2003 17:39:07 -0500 (EST) Received: from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate.mot.com (Motorola/Motgate) with ESMTP id h1OMfdcK005866 for ; Mon, 24 Feb 2003 15:41:39 -0700 (MST) Received: [from ma07exm01.dma.isg.mot.com (ma07exm01.dma.isg.mot.com [150.21.2.102]) by mothost.mot.com (MOT-pobox 2.0) with ESMTP id PAA29546 for ; Mon, 24 Feb 2003 15:41:38 -0700 (MST)] Received: by ma07exm01.dma.isg.mot.com with Internet Mail Service (5.5.2656.59) id <1SR75PXH>; Mon, 24 Feb 2003 17:41:37 -0500 Message-ID: <19CD0E423FC1D611893500508B6F0B9C084998@ma07exm01.dma.isg.mot.com> From: Murwin William-LWM008 To: "Docsis-Oss (E-mail) (E-mail)" , "IPCDN (E-mail) (E-mail)" Cc: "Richard Woundy (E-mail)" Date: Mon, 24 Feb 2003 17:41:37 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C2DC55.4830A0B4" Subject: [ipcdn] draft-ietf-ipcdn-qos-mib-08.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C2DC55.4830A0B4 Content-Type: text/plain; charset="iso-8859-1" Here is the proposed draft-ietf-ipcdn-qos-mib-08.txt This version address all issues raised from the intermin IPCDN working group meeting 2/13/2003. Please get comment back to me asap, because posting of this version needs to be done by 2/28/2003. Thanks, Will Murwin ______________________________ William Murwin Broadband Communications Sector Motorola Inc. Email: W.Murwin@motorola.com Tel: (508) 851-8385 <> <> ------_=_NextPart_000_01C2DC55.4830A0B4 Content-Type: text/plain; name="draft-ietf-ipcdn-qos-mib-08.txt" Content-Disposition: attachment; filename="draft-ietf-ipcdn-qos-mib-08.txt" Content-Transfer-Encoding: quoted-printable =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= IPCDN Working Group Michael = Patrick=0A= William = Murwin=0A= Motorola BCS=0A= =0A= =0A= =0A= Data Over Cable System Interface Specification=0A= Quality of Service=0A= Management Information Base (DOCSIS-QOS MIB)=0A= =0A= March 1, 2003=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Status of this Memo=0A= =0A= This document is an Internet-Draft and is in full conformance = with=0A= all the provisions of Section 10 of RFC2026. Internet-Drafts are=0A= working documents of the Internet Engineering Task Force (IETF), = its=0A= Areas, and its Working Groups. Note that other groups may also=0A= distribute working documents as Internet-Drafts.=0A= =0A= Internet-Drafts are draft documents valid for a maximum of six = months=0A= and may be updated, replaced, or obsoleted by other documents at = any=0A= time. It is inappropriate to use Internet-Drafts as reference=0A= material or to cite them other than as a "work in progress".=0A= =0A= The list of current Internet-Drafts can be accessed at=0A= http://www.ietf.org/ietf/1id-abstracts.txt=0A= =0A= The list of Internet-Draft Shadow Directories can be accessed at=0A= http://www.ietf.org/shadow.html.=0A= =0A= =0A= Copyright (c) The Internet Society 2003. All Rights Reserved.=0A= =0A= =0A= Abstract=0A= =0A= This document defines a basic set of managed objects for = SNMP-based=0A= management of extended QOS features of Cable Modems (CMs) and = Cable=0A= Modem Termination Systems (CMTSs) conforming to the Data over = Cable=0A= System (DOCSIS) standard version 1.1 and 2.0.=0A= =0A= =0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 1]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= Table of Contents=0A= =0A= =0A= Status of this Memo............................... 1=0A= Abstract.......................................... 1=0A= =0A= 1. Introduction...................................... 3=0A= 1.1 The Internet-Standard Management Framework... 3=0A= 1.2 Glossary..................................... 3=0A= =0A= 2. Overview.......................................... 5=0A= 2.1 Textual Conventions.......................... 5=0A= 2.2 MIB Organization............................ 5=0A= 2.2.1 docsQosPktClassTable................. 9=0A= 2.2.2 docsQosParamSetTable................. 9=0A= 2.2.2.1 Interoperation with DOCSIS 1.0....... 11=0A= 2.2.3 docsQosServiceFlowTable.............. 12=0A= 2.2.4 docsQosServiceFlowStatsTable......... 13=0A= 2.2.5 docsQosUpstreamStatsTable............ 14=0A= 2.2.6 docsQosDynamicServiceStatsTable...... 14=0A= 2.2.7 docsQosServiceFlowLogTable........... 14=0A= 2.2.8 docsQosServiceClassTable............. 15=0A= 2.2.9 docsQosServiceClassPolicyTable....... 15=0A= 2.2.10 docsQosPHSTable...................... 15=0A= 2.2.11 docsQosCmtsMacToSrvFlowTable......... 16=0A= =0A= 3. Externally Administered Classification............ 16=0A= =0A= 4. Definitions....................................... 20=0A= =0A= 5. Security Considerations........................... 78=0A= =0A= 6. Intellectual Property............................. 79=0A= =0A= 7. Acknowledgement................................... 80=0A= =0A= 8. Normative References.............................. 80=0A= =0A= 9. Informative References............................ 81=0A= =0A= 10. Author's Address.................................. 81=0A= =0A= 11. Full Copyright Statement.......................... 82=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 2]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= 1. Introduction=0A= =0A= This memo is a product of the IPCDN working group within the = Internet=0A= Engineering Task Force. Comments are solicited and should be=0A= addressed to the working group's mailing list at ipcdn@ietf.org=0A= and/or the author.=0A= =0A= =0A= 1.1 The Internet-Standard Management Framework=0A= =0A= For a detailed overview of the documents that describe the = current=0A= Internet-Standard Management Framework, please refer to section 7 = of=0A= RFC 3410 [12].=0A= =0A= Managed objects are accessed via a virtual information store, = termed=0A= the Management Information Base or MIB. MIB objects are = generally=0A= accessed through the Simple Network Management Protocol (SNMP).=0A= Objects in the MIB are defined using the mechanisms defined in = the=0A= Structure of Management Information (SMI). This memo specifies a = MIB=0A= module that is compliant to the SMIv2, which is described in STD = 58,=0A= RFC 2578 [1], STD 58, RFC 2579 [2] and STD 58, RFC 2580 [3].=0A= =0A= 1.2 Glossary=0A= =0A= =0A= =0A= Active QPS Active Qos Parameter Set. The set of QOS = parameters=0A= that describe the current level service provided to = a=0A= Service Flow.=0A= =0A= Active SF Active Service Flow. An SF with a non-empty Active=0A= QPS.=0A= =0A= Admitted QPS Admitted Qos Parameter Set. The set of QOS = parameters=0A= that describe a level of service which the Service=0A= Flow is not currently using, but which it is=0A= guaranteed to receive upon the SF's request to = make=0A= the set Active.=0A= =0A= Admitted SF A Service Flow with a non-empty Admitted QPS.=0A= =0A= CATV Cable TV=0A= =0A= CM Cable Modem, a modem connecting a subscriber's LAN = the=0A= CATF RF network. DOCSIS CMs operate as a MAC layer=0A= bridge between the home LAN and the RF network.=0A= =0A= CMTS Cable Modem Termination System, the "head-end" = device=0A= providing connectivity between the RF network and = the=0A= Internet.=0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 3]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= Downstream The direction from the head end towards the=0A= subscriber.=0A= =0A= DSA Dynamic Service Addition, a DOCSIS MAC management=0A= message requesting the dynamic creation of a new=0A= Service Flow. New SFs are created with a three-=0A= message exchange of a DSA-REQ, DSA-RSP, and = DSA-ACK.=0A= =0A= DSC Dynamic Service Change, a DOCSIS MAC management=0A= message requesting a change to the attributes of a=0A= Service Flow. SFs are changed with a = three-message=0A= exchange of a DSC-REQ, DSC-RSP, and DSC-ACK.=0A= =0A= DSD Dynamic Service Delete, a DOCSIS MAC management=0A= message requesting the deletion of a Service Flow. = SFs=0A= are deleted with a two-message exchange of a = DSD-REQ=0A= and DSD-ACK.=0A= =0A= Head-end The origination point in most cable systems of the=0A= subsriber video signals. It is generally also the=0A= location of the CMTS.=0A= =0A= PHS Payload Header Suppression, a feature of DOCSIS = 1.1=0A= and 2.0 in which header bytes that are common in a=0A= sequence of packets of a Service Flow are replaced = by=0A= a one-byte PHSI Index (PHSI) when transmitting the=0A= packet on the RF network.=0A= =0A= Provisioned QPS A QOS Parameter Set describing an envelope of = service=0A= within which a Service Flow is authorized to = request=0A= admission. All existing service flows must have a=0A= non-empty Provisioned QPS, hence all SFs are=0A= considered to be "Provisioned".=0A= =0A= SCN Service Class Name -- a named set of QOS = parameters.=0A= A Service Flow may or may not be associated with a=0A= single named Service Class. A Service Class has as = an=0A= attribute a Qos Parameter Set that is used as the=0A= default set of values for all Service Flows = belonging=0A= to the Service Class.=0A= =0A= SID Service ID. A 16-bit integer assigned by the CMTS = for=0A= an Upstream Service Flow with a non-empty Active = QOS=0A= Parameter Set.=0A= =0A= SF Service Flow. A unidirectional stream of packets=0A= between the CM and CMTS. SFs are characterized as=0A= upstream or downstream. The SF is the fundamental=0A= unit of service provided on a DOCSIS CATV network.=0A= =0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 4]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= SFID Service Flow ID. A 32-bit unsigned integer = assigned=0A= by the CMTS to each Service Flows=0A= =0A= Upstream The direction from a subscriber CM to the head-end=0A= CMTS.=0A= =0A= =0A= =0A= =0A= 2. Overview=0A= =0A= This MIB provides a set of objects required for the management of=0A= DOCSIS 1.1 and 2.0 compliant Cable Modems (CM) and Cable Modem=0A= Termination Systems (CMTS). The specification is derived from the=0A= DOCSIS 1.1 Radio Frequency Interface specification [4]. Please = note=0A= that the referenced DOCSIS standard only requires Cable Modems to=0A= process IPv4 customer traffic. Design choices in this MIB reflect=0A= those requirements. Future versions of the DOCSIS standard are=0A= expected to require support for IPv6 as well.=0A= =0A= The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL = NOT",=0A= "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in = this=0A= document are to be interpreted as described in [7].=0A= =0A= =0A= 2.1 Textual Conventions=0A= =0A= The textual convention "DocsRfMacIfDirection" is defined to = indicate=0A= the direction of a packet classifier relative to an interface. It=0A= takes the values of either downstream(1) or upstream(2).=0A= =0A= The textual convention "DocsBitRate" corresponds to the bits per=0A= second as defined for QOS Parameter Sets in DOCSIS 1.1 and 2.0. = This=0A= definition includes all bits of the Ethernet MAC frame as = transmitted=0A= on the RF network, starting with the Destination Address and = ending=0A= with the Ethernet FCS. It does NOT includes bits in the DOCSIS = MAC=0A= header.=0A= =0A= =0A= =0A= =0A= =0A= 2.2 MIB Organization=0A= =0A= =0A= The structure of the MIB is summarized below:=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 5]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= docsQosMIB=0A= docsQosMIBObjects=0A= docsQosPktClassTable=0A= docsQosPktClassEntry=0A= docsQosPktClassId=0A= docsQosPktClassDirection=0A= docsQosPktClassPriority=0A= docsQosPktClassIpTosLow=0A= docsQosPktClassIpTosHigh=0A= docsQosPktClassIpTosMask=0A= docsQosPktClassIpProtocol=0A= docsQosPktClassInetAddressType=0A= docsQosPktClassInetSourceAddr=0A= docsQosPktClassInetSourceMask=0A= docsQosPktClassInetDestAddr=0A= docsQosPktClassInetDestMask=0A= docsQosPktClassSourcePortStart=0A= docsQosPktClassSourcePortEnd=0A= docsQosPktClassDestPortStart=0A= docsQosPktClassDestPortEnd=0A= docsQosPktClassDestMacAddr=0A= docsQosPktClassDestMacMask=0A= docsQosPktClassSourceMacAddr=0A= docsQosPktClassEnetProtocolType=0A= docsQosPktClassEnetProtocol=0A= docsQosPktClassUserPriLow=0A= docsQosPktClassUserPriHigh=0A= docsQosPktClassVlanId=0A= docsQosPktClassStateActive=0A= docsQosPktClassPkts=0A= docsQosPktClassBitMap=0A= docsQosParamSetTable=0A= docsQosParamSetEntry=0A= docsQosParamSetServiceClassName=0A= docsQosParamSetPriority=0A= docsQosParamSetMaxTrafficRate=0A= docsQosParamSetMaxTrafficBurst=0A= docsQosParamSetMinReservedRate=0A= docsQosParamSetMinReservedPkt=0A= docsQosParamSetActiveTimeout=0A= docsQosParamSetAdmittedTimeout=0A= docsQosParamSetMaxConcatBurst=0A= docsQosParamSetSchedulingType=0A= docsQosParamSetNomPollInterval=0A= docsQosParamSetTolPollJitter=0A= docsQosParamSetUnsolicitGrantSize=0A= docsQosParamSetNomGrantInterval=0A= docsQosParamSetTolGrantJitter=0A= docsQosParamSetGrantsPerInterval=0A= docsQosParamSetTosAndMask=0A= docsQosParamSetTosOrMask=0A= =0A= =0A= =0A= Expires September 2003 [Page 6]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= docsQosParamSetMaxLatency=0A= docsQosParamSetType=0A= docsQosParamSetRequestPolicyOct=0A= docsQosParamSetBitMap=0A= docsQosServiceFlowTable=0A= docsQosServiceFlowEntry=0A= docsQosServiceFlowId=0A= docsQosServiceFlowSID=0A= docsQosServiceFlowDirection=0A= docsQosServiceFlowPrimary=0A= docsQosServiceFlowStatsTable=0A= docsQosServiceFlowStatsEntry=0A= docsQosServiceFlowPkts=0A= docsQosServiceFlowOctets=0A= docsQosServiceFlowTimeCreated=0A= docsQosServiceFlowTimeActive=0A= docsQosServiceFlowPHSUnknowns=0A= docsQosServiceFlowPolicedDropPkts=0A= docsQosServiceFlowPolicedDelayPkts=0A= docsQosUpstreamStatsTable=0A= docsQosUpstreamStatsEntry=0A= docsQosSID=0A= docsQosUpstreamFragments=0A= docsQosUpstreamFragDiscards=0A= docsQosUpstreamConcatBursts=0A= docsQosDynamicServiceStatsTable=0A= docsQosDynamicServiceStatsEntry=0A= docsQosIfDirection=0A= docsQosDSAReqs=0A= docsQosDSARsps=0A= docsQosDSAAcks=0A= docsQosDSCReqs=0A= docsQosDSCRsps=0A= docsQosDSCAcks=0A= docsQosDSDReqs=0A= docsQosDSDRsps=0A= docsQosDynamicAdds=0A= docsQosDynamicAddFails=0A= docsQosDynamicChanges=0A= docsQosDynamicChangeFails=0A= docsQosDynamicDeletes=0A= docsQosDynamicDeleteFails=0A= docsQosDCCReqs=0A= docsQosDCCRsps=0A= docsQosDCCAcks=0A= docsQosDCCs=0A= docsQosDCCFails=0A= docsQosServiceFlowLogTable=0A= docsQosServiceFlowLogEntry=0A= docsQosServiceFlowLogIndex=0A= docsQosServiceFlowLogIfIndex=0A= =0A= =0A= =0A= Expires September 2003 [Page 7]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= docsQosServiceFlowLogSFID=0A= docsQosServiceFlowLogCmMac=0A= docsQosServiceFlowLogPkts=0A= docsQosServiceFlowLogOctets=0A= docsQosServiceFlowLogTimeDeleted=0A= docsQosServiceFlowLogTimeCreated=0A= docsQosServiceFlowLogTimeActive=0A= docsQosServiceFlowLogDirection=0A= docsQosServiceFlowLogPrimary=0A= docsQosServiceFlowLogServiceClassName=0A= docsQosServiceFlowLogPolicedDropPkts=0A= docsQosServiceFlowLogPolicedDelayPkts=0A= docsQosServiceFlowLogControl=0A= docsQosServiceClassTable=0A= docsQosServiceClassEntry=0A= docsQosServiceClassName=0A= docsQosServiceClassStatus=0A= docsQosServiceClassMaxTrafficRate=0A= docsQosServiceClassMaxTrafficBurst=0A= docsQosServiceClassMinReservedRate=0A= docsQosServiceClassMinReservedPkt=0A= docsQosServiceClassMaxConcatBurst=0A= docsQosServiceClassNomPollInterval=0A= docsQosServiceClassTolPollJitter=0A= docsQosServiceClassUnsolicitGrantSize=0A= docsQosServiceClassNomGrantInterval=0A= docsQosServiceClassTolGrantJitter=0A= docsQosServiceClassGrantsPerInterval=0A= docsQosServiceClassMaxLatency=0A= docsQosServiceClassActiveTimeout=0A= docsQosServiceClassAdmittedTimeout=0A= docsQosServiceClassSchedulingType=0A= docsQosServiceClassRequestPolicy=0A= docsQosServiceClassTosAndMask=0A= docsQosServiceClassTosOrMask=0A= docsQosServiceClassDirection=0A= docsQosServiceClassStorageType=0A= docsQosServiceClassPolicyTable=0A= docsQosServiceClassPolicyEntry=0A= docsQosServiceClassPolicyIndex=0A= docsQosServiceClassPolicyName=0A= docsQosServiceClassPolicyRulePriority=0A= docsQosServiceClassPolicyStatus=0A= docsQosServiceClassPolicyStorageType=0A= docsQosPHSTable=0A= docsQosPHSEntry=0A= docsQosPHSField=0A= docsQosPHSMask=0A= docsQosPHSSize=0A= docsQosPHSVerify=0A= docsQosPHSIndex=0A= =0A= =0A= =0A= Expires September 2003 [Page 8]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= docsQosCmtsMacToSrvFlowTable=0A= docsQosCmtsMacToSrvFlowEntry=0A= docsQosCmtsCmMac=0A= docsQosCmtsServiceFlowId=0A= docsQosCmtsIfIndex=0A= =0A= =0A= =0A= The MIB is organized as 11 tables. Most tables are implemented in=0A= both the CM and CMTS; the docsQosUpstreamStatsTable and=0A= docsQosServiceFlowLogTable are implemented on the CMTS only.=0A= =0A= =0A= 2.2.1 docsQosPktClassTable=0A= =0A= The docsQosPktClassTable reports the Service Flow Classifiers=0A= implemented by the managed device. The table is indexed by the = tuple=0A= { ifIndex, docsQosServiceFlowId, docsQosPktClassId }. The = ifIndex=0A= corresponds to an CATV MAC interface. Each CATV MAC interfaces has = a=0A= set of Service Flows, identified with a docsQosServiceFlowId = value=0A= that is unique for that interface. Each service flow may have a=0A= number of packet classifiers that map packets to the flow. The=0A= ClassifierId for the classifier is unique only within a = particular=0A= service flow.=0A= =0A= The semantics of packet classification are provided in [4]. = Briefly,=0A= the DOCSIS MAC interface calls for matching packets based on = values=0A= within the 802.2 (LLC), 802.3, IP, and/or UDP/TCP headers. = Packets=0A= which map more than one classifier are prioritized according to = their=0A= docsQosPktClassPriority value. The docsQosServiceFlowId (an index=0A= object) indicates to which service flow the packet is classified.=0A= =0A= The docsQosPktClassTable is distinct from the docsDevIpFilterTable = of=0A= [9] in that docsQosPktClassTable is intended only to reflect the=0A= state of the Service Flow Classifiers. Service Flow Classifiers = may=0A= be created only via a CM configuration file or from the Dynamic=0A= Service Addition (DSA) messages. For this reason,=0A= docsQosPktClassTable is read-only.=0A= =0A= The docsDevIpFilterTable is intended for external policy-based=0A= administration of packet classifiers. See the section = "Externally=0A= Administered Classification", below.=0A= =0A= =0A= 2.2.2 docsQosParamSetTable=0A= =0A= The docsQosParamSetTable reports the values of Qos Parameter Set = as=0A= defined in Section C.2.2 of [4].=0A= =0A= In general, a Service Flow is associated with three different Qos=0A= Parameter Sets (QPSs): an "active" QPS, an "admitted" QPS, and a=0A= =0A= =0A= =0A= Expires September 2003 [Page 9]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= "provisioned" or "authorized" QPS. The relationship of these = three=0A= sets is represented below:=0A= =0A= =0A= =0A= =0A= =0A= +---------------------+=0A= | Provisioned |=0A= | |=0A= | +---------------+ |=0A= | | Admitted | |=0A= | | | |=0A= | | +---------+ | |=0A= | | | Active | | |=0A= | | | | | |=0A= | | +---------+ | |=0A= | | | |=0A= | +---------------+ |=0A= | |=0A= +---------------------+=0A= =0A= Figure 1: Qos Parameter Sets=0A= =0A= =0A= =0A= The Provisioned QPS describes the maximum service envelope for = which=0A= the SF is authorized. The Admitted QPS is the set of services for=0A= which a service flow has requested admission to the DOCSIS RF=0A= network, but which is not yet active. The Admitted QPS is used = during=0A= the two-phase process of IP Telephony service flow admission to = admit=0A= the bandwidth for a bidirectional voice call when the far end is=0A= ringing. Since ringing may occur for up to four minutes, this=0A= permits the bandwidth to be reserved but not actually consumed = during=0A= this interval. The Active QPS is the set of services actually = being=0A= used by the Service Flow. The DOCSIS v1.1 specification [4] = defines=0A= what it means for a QPS envelope to be "within" another. In = general,=0A= an inner QPS is considered to be "within" an outer QPS when all = QOS=0A= parameters represent demands of equal or fewer resources of the=0A= network.=0A= =0A= In addition to their use as attributes of a Service Flow, a QPS = is=0A= also an attribute of a Service Class. A DOCSIS CM configuration = file=0A= or DSA message may request the creation of a new SF and give only = the=0A= Service Class Name. The CMTS "expands the macro" of a Service = Class=0A= Name creation by populating the Provisioned, Admitted, and/or = Active=0A= QPSs of the Service Flow with the QPS of the Service Class Name. = All=0A= of the QPSs of a Service Flow must be expansions of the same = Service=0A= Class, and in this case the SF is said to "belong" to the Service=0A= Class. Changing the contents of a Service Class' QPS does not = affect=0A= the QPS of any Service Flow earlier expanded from that Service = Class=0A= =0A= =0A= =0A= Expires September 2003 [Page 10]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= name. Only the CMTS implements docsQosServiceClassTable.=0A= =0A= See [4] section 8 for a full description and the theory of = operation=0A= of Docsis 1.1 QOS operation.=0A= =0A= =0A= =0A= The docsQosParamSetTable sets are indexed by { ifIndex,=0A= docsQosServiceFlowId, docsQosParamSetType}. ifIndex indicates a=0A= particular "DOCSIS MAC Domain". docsQosServiceFlowId uniquely=0A= identifies a service flow on that MAC domain. The=0A= docsQosParamSetType indicates whether the row describes an = active,=0A= admitted, or provisioned Qos Parameter Set.=0A= =0A= The docsQosParamSetTable is read-only, because it indicates the = Qos=0A= Parameter Set contents as defined by DOCSIS signaling. The=0A= docsQosServiceClassTable is read-create to permit managers to = define=0A= a template of Qos Parameters that can be referenced by DOCSIS = modems=0A= when creating their Qos Parameter Sets.=0A= =0A= =0A= 2.2.2.1 Interoperation with DOCSIS 1.0=0A= =0A= The DOCSIS 1.0 DOCS-IF-MIB [10] specifies a docsIfQosProfileTable = to=0A= describe the set of Class Of Service (COS) parameters associated = with=0A= a COS "profile". The docsIfCmServiceTable, which contains one = entry=0A= per SID, references this table with a docsIfCmServiceQosProfile=0A= number.=0A= =0A= The DOCSIS 1.1 and 2.0 CM registration process allows a modem to=0A= register as operating either with DOCSIS 1.0, DOCSIS 1.1, or = DOCSIS=0A= 2.0 functionality. For ease of expression, we call a modem=0A= registering with DOCSIS 1.0 functionality a "DOCSIS 1.0 modem",=0A= regardless of the modem's capabilities.=0A= =0A= A CMTS or CM supporting both DOCSIS 1.0, DOCSIS 1.1, and DOCSIS = 2.0=0A= implements both the tables of [10] and the tables of this MIB. = The=0A= interoperation goal is that before modem registration, the DOCSIS = 1.0=0A= MIB [10] applies. After registration, either the DOCSIS 1.0 or = DOCSIS=0A= 1.1/2.0 MIB applies, depending on the mode with which the modem=0A= registered. The specific interoperation rules are:=0A= =0A= =0A= 1. When a CM initially ranges, the CM implements a row in the=0A= DOCS-IF-MIB docsIfCmServiceTable and the CMTS implements a = row=0A= in the DOCS-IF-MIB docsIfCmtsServiceTable corresponding to = the=0A= default upstream Service ID (SID) used for = pre-registration=0A= upstream traffic. For historical compatibility a row may be=0A= created for the docsIfQosProfileTable with default values,=0A= which may be referenced by the docsIfCmServiceTable = entries.=0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 11]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= 2. Both a CMTS and CM implementing this MIB MUST NOT implement=0A= docsQosParamSetTable or docsQosServiceFlowTable rows until=0A= after the CM registers with DOCSIS 1.1 or 2.0 modem = operation.=0A= =0A= =0A= 3. When a modem registers with the CMTS as a "DOCSIS 1.1" or=0A= "DOCSIS 2.0" modem, any exclusively-referenced row in = DOCS-IF-=0A= MIB docsQosProfileTable representing the modems upstream = Qos=0A= profile for pre-registration traffic MUST be removed.=0A= Multiply-referenced rows may remain. The=0A= docsQosIfCmServiceQosProfile object in the CM's row of=0A= docsIfCmServiceTable MUST be set to zero. The=0A= docsIfCmServiceTable row for the DOCSIS 1.1 or DOCSIS 2.0 = modem=0A= continues to exist, and the various statistic objects in = that=0A= row are incremented. The CMTS should retain the=0A= docsIfCmtsServiceTable entry for the DOCSIS 1.1 or DOCSIS = 2.0=0A= CM.=0A= =0A= =0A= 4. When a DOCSIS 1.1 or DOCSIS 2.0 modem registers, both the = CMTS=0A= and CM represent all service flows described in the modem=0A= configuration file in docsQosParamSetTable and=0A= docsQosServiceFlowTable.=0A= =0A= =0A= 5. At the CMTS, the Docsis 1.0 MIB objects=0A= docsIfCmtsServiceInPackets and docsIfCmtsServiceInOctets for = a=0A= SID assigned to a Docsis 1.1 or Docsis 2.0 modem count only = the=0A= pre-registration packets/bytes of those modems.=0A= =0A= =0A= 6. DOCSIS 1.0 modems do not have entries in the = DOCS-IETF-QOS-MIB.=0A= =0A= =0A= =0A= 2.2.3 docsQosServiceFlowTable=0A= =0A= The docsQosServiceFlowTable provides read-only information about = all=0A= of the service flows known by the device. It is indexed by the=0A= combination of { ifIndex, dosQosServiceFlowId }, where ifIndex=0A= corresponds to a CATV MAC interface and docsQosServiceFlowId is = the=0A= 32- bit integer assigned by the CMTS controlling the MAC domain. = A=0A= CM typically has only a single CATV MAC interface, while a CMTS = may=0A= have several. See [10] for a description of the ifIndex = numbering=0A= for DOCSIS devices.=0A= =0A= The table indicates whether a given SF is in the upstream or=0A= downstream direction, and whether it is the "primary" SF in that=0A= direction. The primary SF carries traffic that is not otherwise=0A= classified to any other SF in that direction.=0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 12]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= 2.2.4 docsQosServiceFlowStatsTable=0A= =0A= The docsQosServiceFlowStatsTable provides statistics for all=0A= currently existing SFs known by the managed device. It provides=0A= basic packet and octet counters, as well as certain other = SF-specific=0A= stats such as the time at which the flow was created and how many=0A= seconds it has been active.=0A= =0A= The table also provides objects which can be used to fine-tune=0A= admission control decisions, namely the number of packets dropped = or=0A= delayed due to QOS policing decisions enforced by the managed = device.=0A= =0A= The model of the service flows stats table is that there exists a=0A= service flow Classification function followed by a service flow=0A= maximum rate Policing function for packets transmitted onto the=0A= Docsis RF network, as depicted below=0A= =0A= =0A= +----------+=0A= +------------+ clsfy 1 -----+ | Per-SF | = forwarded=0A= Pkts | |-----------> | | Maximum |---> for = Docsis=0A= ----->| Classify | clsfy 2 SF1 |--> | Rate | RF = Network=0A= | Function |-----------> | | Policing | = transmission=0A= | | -----+ | Function |=0A= | | | |----+=0A= | | | | |=0A= | | +----------+ = Dropped=0A= +------------+ | ^=0A= +----+ Delayed=0A= =0A= Packets intended for transmission onto the Docsis RF network=0A= (upstream or downstream) are first classified to a service flow = by=0A= matching one of several possible classifiers associated with that=0A= service flow. The docsQosPktClassPkts count includes the number = of=0A= packets that match the classifier, regardless of the eventual=0A= disposition of the packet.=0A= =0A= DOCSIS requires that each service flow be policed to maintain a=0A= maximum rate of transmission. This is performed by either dropping = or=0A= delaying a packet on that service flow. The=0A= docsQosServiceFlowPolicedDropPkts object counts the number of = service=0A= flow packets dropped by the policing function. The=0A= docsQosServiceFlowPolicedDelayPkts counts the number of packet=0A= delayed but still forwarded. The docsQosServiceFlowPkts object=0A= counts the total number of packets forwarded beyond the policing=0A= function intended for eventual transmission onto the DOCSIS RF=0A= network. Although packets may be latter dropped by other = functions=0A= (e.g. a transmit queue overflow on a DOCSIS hardware = transmitter),=0A= the docsQos MIB per service-flow counters are not affected in = this=0A= case.=0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 13]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= 2.2.5 docsQosUpstreamStatsTable=0A= =0A= This table provides statistics that are measured only at the CMTS = in=0A= the upstream direction. These include a count of the number of=0A= fragmentation headers received, fragments discarded, and the = number=0A= of concatenation headers received.=0A= =0A= =0A= 2.2.6 docsQosDynamicServiceStatsTable=0A= =0A= This table provides read-only stats on the operation of the = Dynamic=0A= Service state machines as specified in section 9.4 of [4]. It=0A= provides a set of 14 counters *in each direction* for a Docsis = MAC=0A= layer interface. That is, each Docsis MAC layer interface has one = row=0A= for downstream stats, and a second row for upstream stats.=0A= =0A= Eight of the counters are DSx packet type counts, one counter for=0A= each of the eight DSx packet types. For example, the = docsQosDSAReqs=0A= object in the upstream row at the CMTS counts the number of = DSA-REQ=0A= messages received by the CMTS from that interface. The=0A= docsQosDSAReqs object in the downstream row at the CMTS counts = the=0A= number of DSA-REQ messages transmitted by the CMTS on that = interface.=0A= =0A= The remaining six counters per (interface, direction) combination=0A= count the number of successful and unsuccessful *transactions* = that=0A= were initiated on the interface and direction. For example, the=0A= upstream docsQosDynamicAdds on a CMTS is the number of = successfully=0A= completed CM-initiated dynamic additions, because at the CMTS a = CM-=0A= initiated DSA starts in the upstream direction. The downstream=0A= docsQosDynamicAdds at a CMTS is the number of successful CMTS-=0A= initiated DSA transactions.=0A= =0A= Dynamic service transactions can fail for a number of reasons, as=0A= listed in the state machines of section 9.4. Rather than include=0A= still more counters for each different failure reason, they are=0A= grouped into a single count, e.g docsQosDynamicAddFails. Again, = this=0A= object exists in both directions, so that locally originated vs=0A= remotely originated transaction failures are counted separately.=0A= Further troubleshooting of transaction failures will require = vendor-=0A= specific queries and operation.=0A= =0A= =0A= 2.2.7 docsQosServiceFlowLogTable=0A= =0A= This table contains a log of the Service Flows no longer existing = in=0A= the docsQosServiceFlowTable. It is intended to be periodically = polled=0A= by traffic monitoring and billing agents. It is implemented only = at=0A= the CMTS.=0A= =0A= It contains a chronological log of SF session statistics, including = a=0A= total count of packets and octets transferred on the SF. It = includes=0A= =0A= =0A= =0A= Expires September 2003 [Page 14]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= time stamps of the SF creation and deletion time, as well as its=0A= number of active seconds. The active second count is the count of=0A= seconds that the SF had a non-empty Active Qos Parameter Set, i.e. = it=0A= was eligible to pass data. For unicast SFs, it includes the CM = MAC=0A= address associated with the flow for billing reference purposes.=0A= =0A= The maximum number of log records kept by a CMTS, and the = duration=0A= that a log record is maintained in the table is vendor-specific. = An=0A= explicit control object is provided so that the monitoring=0A= application can explicitly delete records it has read.=0A= =0A= =0A= 2.2.8 docsQosServiceClassTable=0A= =0A= This table defines the Service Class Name and references a Qos=0A= Parameter Set for each Service Class defined in a CMTS. It is=0A= indexed by the Service Class Name string itself. The table is = read-=0A= create on a CMTS, and is not implemented in a CM. Each entry of = the=0A= docsQosServiceClassTable should define a template for flows in a=0A= given direction (upstream or downstream). Some parameters of the=0A= docsQosServiceClassTable are specific to a particular direction, = and=0A= so their values are not-applicable when used as a template for = flows=0A= in the other direction.=0A= =0A= =0A= =0A= 2.2.9 docsQosServiceClassPolicyTable=0A= =0A= =0A= The docsQosServiceClassPolicyTable can be referenced by the=0A= docsDevFilterPolicyTable of [9] in order to have a "policy" that=0A= classifies packets to a named Service Class. This is one mechanism = by=0A= which "external" entities (like an SNMP manager) may control the=0A= classification of packet for QOS purposes. Entries are indexed by = a=0A= small integer docsQosServiceClassPolicyIndex. They provide a = Service=0A= Class Name and a Rule Priority. A policy referencing a row of = this=0A= table intends the packet to be forwarded on a Service Flow=0A= "belonging" to the named Service Class. See the section = "Externally=0A= Administered Classification", below.=0A= =0A= This table is implemented on both the CM and CMTS, and is = read-create=0A= on both.=0A= =0A= =0A= 2.2.10 docsQosPHSTable=0A= =0A= The Payload Header Suppression (PHS) feature of DOCSIS 1.1 and = 2.0=0A= permits packets to replace the unchanging bytes of the Ethernet, = IP,=0A= and UDP headers with a one-byte index when transmitting on the = cable=0A= network. This is especially useful for IP Telephony packets, = where=0A= such suppression can result in almost twice the number of calls=0A= =0A= =0A= =0A= Expires September 2003 [Page 15]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= supported within the same upstream channel.=0A= =0A= Each entry of the table corresponds to a PHS Rule as described in=0A= section 8.4 of [4]. The rules are identified by their = corresponding=0A= service flow ID and docsQosPktClassId. A PHS rule is associated = with=0A= exactly one classifier. The table is therefore indexed by the = tuple=0A= { ifIndex, docsQosServiceFlowId, docsQosPktClassId}.=0A= =0A= This table is read-only, and MUST be implemented on both the CM = and=0A= CMTS when PHS is supported.=0A= =0A= =0A= 2.2.11 docsQosCmtsMacToSrvFlowTable=0A= =0A= The docsQosCmtsMacToSrvFlowTable provides describes the mapping of = CM=0A= mac addresses to the Service Flow Ids that are uniquely = identified=0A= with that CM. External applications may collect statistics on = all=0A= packets flowing through a CM by determining the SFID of all of = its=0A= flows, and then collecting the statistics of packets and bytes = for=0A= each flow.=0A= =0A= Downstream multicast service flows are not indicated in the=0A= docsQosCmtsMacToSrvFlowTable because they are not associated with=0A= only one CM.=0A= =0A= =0A= =0A= =0A= 3. Externally Administered Classification=0A= =0A= Docsis 1.1 and 2.0 provides rich semantics for the classification = of=0A= packets to service flows with it Service Flow Classifier table.=0A= Service Flow Classifiers may be created statically in the DOCSIS = CM=0A= configuration file, or may be created dynamically with Dynamic=0A= Service Addition (DSA) and Dynamic Service Change (DSC) DOCSIS = MAC=0A= messages.=0A= =0A= Several major issues arose with the concept of externally=0A= administered classification, i.e. should an external SNMP manager = be=0A= permitted to create classification rows? One problem was the co-=0A= ordination of classifier IDs, since such an approach would = require=0A= either separate classifier ID number spaces or objects to = co-ordinate=0A= both internal and external classifier ID assignments. A more = serious=0A= problem, however, was the requirement that external creation of = SF=0A= Classifiers would require "knowledge" of the individual Service = Flow=0A= ID for service flows by external applications. It was strongly = felt=0A= by the committee that SFIDs should remain an internal Docsis = object,=0A= and not be transmitted as part of protocol flows, e.g. for IP = packet=0A= telephony signaling. Docsis 1.1 introduced the concept of named=0A= Service Classes for ease of administration within a domain of CMs = and=0A= CMTSs. What was desired was to permit external classification of=0A= =0A= =0A= =0A= Expires September 2003 [Page 16]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= packets to a Service Class, not a particular Service Flow.=0A= =0A= The DOCSIS committee therefore decided to use the already-defined = IP=0A= Packet Filter Table [9] for the external classification of = packets=0A= for QOS purposes. The docsDevIpPacketFilterTable defines similar=0A= packet matching criteria as docsQosPktClassTable, but it matches = a=0A= packet to an arbitrary "policy set" instead of a particular = Service=0A= Flow. One of the policies in the policy set then selects the = Service=0A= Class of the SF on which to forward the packet. The=0A= docsQosServiceClassPolicyTable of this MIB defines the Service = Class=0A= Name to which a packet is classified.=0A= =0A= The interaction of external and internal packet classification is=0A= depicted below.=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 17]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= =0A= =0A= |=0A= | Outbound Pkt=0A= V=0A= docsDevIpFilterTable------> docsDevFilterPolicyTable=0A= | |=0A= | V=0A= | docsQosServiceClassPolicyTable=0A= | |=0A= | Pkt | ServiceClassName,=0A= | | = ServiceClassPolicyRulePriority=0A= V V=0A= +--------------------------------------------------------+=0A= | | DOCSIS MAC LAYER ENTITY | |=0A= | | | Select any |=0A= | V | SFID Y in SCN|=0A= | docsQosPktClassTable <---------------| |=0A= | | | |=0A= | | docsQosPktClassPriority, | |=0A= | | SFID X | |=0A= | V V |=0A= | ----------------------------------------+ |=0A= | | Select the SFID associated with the | |=0A= | | higher of docsQosPktClassPriority or | |=0A= | | docsQosServiceClassPolicyRulePriority | |=0A= | +---------------------------------------+ |=0A= | | |=0A= | V |=0A= | | | | | |=0A= | | | ... | | Service Flows |=0A= | +----+ +----+ |=0A= | SFID X SFID Y |=0A= +--------------------------------------------------------+=0A= =0A= Figure 2: Docsis Packet Classification=0A= =0A= =0A= The processing of an outgoing packet proceeds as follows:=0A= =0A= 1. The packet is first checked for matches with rows of = the=0A= docsDevIpFilterTable. If it matches, the matching row=0A= provides a docsDevFilterPolicyId integer.=0A= =0A= 2. The docsDevFilterPolicyId indexes into one (or more) = rows=0A= of docsDevFilterPolicyTable. Each row provides an=0A= arbitrary RowPointer (docsDevFilterPolicyPtr),=0A= corresponding to a policy to be applied to the packet.=0A= =0A= 3. This MIB defines a docsQosServiceClassPolicyTable = whose=0A= entries may be pointed to by docsDevFilterPolicyPtr in=0A= =0A= =0A= =0A= Expires September 2003 [Page 18]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= order to administratively classify packets to a named=0A= DOCSIS Service Class. The = docsQosServiceClassPolicyEntry=0A= provides a Service Class Name (SCN) as=0A= docsQosServiceClassPolicyName and a classification = rule=0A= priority as docsQosServiceClassPolicyRulePriority. = These=0A= are submitted to the device's Docsis MAC Layer entity as = a=0A= special form of the MAC_DATA.request primitive, as=0A= described in Section E.2.1 of [4].=0A= =0A= 4. The MAC Layer selects an SFID ("Y") of an active = Service=0A= Flow belonging to the named class, choosing an SF=0A= arbitrarily if there is more than one.=0A= =0A= 5. The packet is then classified according to the=0A= docsQosPktClassTable, which may classify the packet to = a=0A= different SFID "X". Associated with the classifier is = a=0A= docsQosPktClassPriority.=0A= =0A= 6. In the event of a conflict between the SCN-determined = SFID=0A= and the classified SFID, the greater of=0A= docsQosPktClassPriority and=0A= docsQosServiceClassPolicyRulePriority determines which=0A= SFID is selected to forward the packet.=0A= =0A= A packet which does not match a = docsQosServiceClassPolicyEntry=0A= is directly submitted to the Docsis MAC layer, where the=0A= docsQosPktClassTable selects the SID on which it is to be=0A= forwarded.=0A= =0A= By convention (in [4]), the "internal" = docsQosPktClassPriority=0A= values should be in the range of 64-191, while the = "external"=0A= priorities may be either in the range 192-255 to override = the=0A= internal classification or the range 0-63 to be overridden = by=0A= internal classification.=0A= =0A= This classification mechanism applies both upstream from the = CM=0A= and downstream from the CMTS.=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 19]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= 4. Definitions=0A= =0A= --=0A= -- Docsis QOS Extensions MIB=0A= --=0A= =0A= DOCS-IETF-QOS-MIB DEFINITIONS ::=3D BEGIN=0A= =0A= IMPORTS=0A= MODULE-IDENTITY,=0A= OBJECT-TYPE,=0A= Integer32,=0A= Counter32,=0A= Unsigned32,=0A= Counter64=0A= FROM SNMPv2-SMI=0A= =0A= TEXTUAL-CONVENTION,=0A= MacAddress,=0A= RowStatus,=0A= TruthValue,=0A= DisplayString,=0A= TimeStamp,=0A= StorageType=0A= FROM SNMPv2-TC=0A= =0A= OBJECT-GROUP,=0A= MODULE-COMPLIANCE=0A= FROM SNMPv2-CONF=0A= =0A= ifIndex,=0A= InterfaceIndex=0A= FROM IF-MIB=0A= =0A= docsIfMib=0A= FROM DOCS-IF-MIB=0A= =0A= InetAddressType,=0A= InetAddress,=0A= InetPortNumber=0A= FROM INET-ADDRESS-MIB;=0A= =0A= docsQosMIB MODULE-IDENTITY=0A= LAST-UPDATED "200303010000Z" -- March 1, 2003=0A= ORGANIZATION "IETF IPCDN Working Group"=0A= CONTACT-INFO=0A= "=0A= Co-Author: Michael Patrick=0A= Postal: Motorola BCS=0A= 20 Cabot Blvd, MS M2-330=0A= Mansfield, MA 02048-1193=0A= =0A= =0A= =0A= Expires September 2003 [Page 20]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= U.S.A.=0A= Phone: +1 508 851 8402=0A= E-mail: michael.patrick@motorola.com=0A= =0A= Co-Author: William Murwin=0A= Postal: Motorola BCS=0A= 20 Cabot Blvd, MS M2-330=0A= Mansfield, MA 02048-1193=0A= U.S.A.=0A= Phone: +1 508 851 8385=0A= E-mail: w.murwin@motorola.com"=0A= =0A= DESCRIPTION=0A= "This is the management information for=0A= Quality Of Service (QOS) for DOCSIS 1.1 and 2.0."=0A= =0A= REVISION "200303010000Z" -- March 1, 2003=0A= DESCRIPTION=0A= "Initial version, published as RFC xxxx."=0A= ::=3D { docsIfMib xx } -- xx to be assignrd by IANA=0A= =0A= docsQosMIBObjects OBJECT IDENTIFIER ::=3D { docsQosMIB 1 }=0A= =0A= -- Textual Conventions=0A= DocsQosRfMacIfDirection ::=3D TEXTUAL-CONVENTION=0A= STATUS current=0A= DESCRIPTION "Indicates a direction on an RF MAC interface.=0A= =0A= The value downstream(1) is from Cable Modem=0A= Termination System to Cable Modem.=0A= =0A= The value upstream(2) is from Cable Modem to=0A= Cable Modem Termination System."=0A= SYNTAX INTEGER {=0A= downstream(1),=0A= upstream(2)=0A= }=0A= =0A= DocsQosBitRate ::=3D TEXTUAL-CONVENTION=0A= DISPLAY-HINT "d"=0A= STATUS current=0A= DESCRIPTION "The rate of traffic in unit of bits per second.=0A= Used to specify traffic rate for QOS."=0A= SYNTAX Unsigned32=0A= =0A= DocsQosSchedulingType ::=3D TEXTUAL-CONVENTION=0A= STATUS current=0A= DESCRIPTION "The scheduling service provided by a CMTS for = an=0A= upstream service flow. If the parameter is = omitted=0A= from an upstream QOS Parameter Set, this object = takes=0A= the value of bestEffort (2). This parameter must = be=0A= =0A= =0A= =0A= Expires September 2003 [Page 21]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= reported as undefined (1) for downstream QOS = Parameter=0A= Sets."=0A= SYNTAX INTEGER {=0A= undefined (1),=0A= bestEffort (2),=0A= nonRealTimePollingService(3),=0A= realTimePollingService(4),=0A= unsolictedGrantServiceWithAD(5),=0A= unsolictedGrantService(6)=0A= }=0A= =0A= -----------------------------------------------------------------------=0A= --=0A= -- Packet Classifier Table=0A= --=0A= docsQosPktClassTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosPktClassEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table describes the packet classification=0A= configured on the CM or CMTS.=0A= The model is that a packet either received=0A= as input from an interface or transmitted=0A= for output on an interface may be compared=0A= against an ordered list of rules pertaining to=0A= the packet contents. Each rule is a row of this=0A= table. A matching rule provides a service flow=0A= id to to which the packet is classified.=0A= All rules need to match for a packet to match=0A= a classifier.=0A= =0A= The objects in this row correspond to a set of=0A= Classifier Encoding parameters in a DOCSIS=0A= MAC management message. The = docsQosPktClassBitMap=0A= indicates which particular parameters were = present=0A= in the classifier as signaled in the DOCSIS = message.=0A= If the referenced parameter was not present=0A= in the signaled DOCSIS 1.1 and 2.0 Classifier, = the=0A= corresponding object in this row reports a=0A= value as specified in the DESCRIPTION section.=0A= "=0A= ::=3D { docsQosMIBObjects 1 }=0A= =0A= =0A= docsQosPktClassEntry OBJECT-TYPE=0A= SYNTAX DocsQosPktClassEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "An entry in this table provides a single packet=0A= classifier rule. The index ifIndex is an ifType=0A= of docsCableMaclayer(127)."=0A= =0A= =0A= =0A= Expires September 2003 [Page 22]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= INDEX {=0A= ifIndex,=0A= docsQosServiceFlowId,=0A= docsQosPktClassId=0A= }=0A= ::=3D { docsQosPktClassTable 1 }=0A= =0A= =0A= =0A= DocsQosPktClassEntry ::=3D SEQUENCE {=0A= docsQosPktClassId Unsigned32,=0A= docsQosPktClassDirection DocsQosRfMacIfDirection,=0A= docsQosPktClassPriority Integer32,=0A= docsQosPktClassIpTosLow OCTET STRING,=0A= docsQosPktClassIpTosHigh OCTET STRING,=0A= docsQosPktClassIpTosMask OCTET STRING,=0A= docsQosPktClassIpProtocol Integer32,=0A= docsQosPktClassInetAddressType InetAddressType,=0A= docsQosPktClassInetSourceAddr InetAddress,=0A= docsQosPktClassInetSourceMask InetAddress,=0A= docsQosPktClassInetDestAddr InetAddress,=0A= docsQosPktClassInetDestMask InetAddress,=0A= docsQosPktClassSourcePortStart InetPortNumber,=0A= docsQosPktClassSourcePortEnd InetPortNumber,=0A= docsQosPktClassDestPortStart InetPortNumber,=0A= docsQosPktClassDestPortEnd InetPortNumber,=0A= docsQosPktClassDestMacAddr MacAddress,=0A= docsQosPktClassDestMacMask MacAddress,=0A= docsQosPktClassSourceMacAddr MacAddress,=0A= docsQosPktClassEnetProtocolType INTEGER,=0A= docsQosPktClassEnetProtocol Integer32,=0A= docsQosPktClassUserPriLow Integer32,=0A= docsQosPktClassUserPriHigh Integer32,=0A= docsQosPktClassVlanId Integer32,=0A= docsQosPktClassStateActive TruthValue,=0A= docsQosPktClassPkts Counter64,=0A= docsQosPktClassBitMap BITS=0A= }=0A= =0A= docsQosPktClassId OBJECT-TYPE=0A= SYNTAX Unsigned32 (1..65535)=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Index assigned to packet classifier entry by=0A= the CMTS which is unique per service flow."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.3.2"=0A= ::=3D { docsQosPktClassEntry 1 }=0A= =0A= docsQosPktClassDirection OBJECT-TYPE=0A= SYNTAX DocsQosRfMacIfDirection=0A= MAX-ACCESS read-only=0A= =0A= =0A= =0A= Expires September 2003 [Page 23]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= STATUS current=0A= DESCRIPTION "Indicates the direction to which the classifier=0A= is applied."=0A= ::=3D { docsQosPktClassEntry 2 }=0A= =0A= docsQosPktClassPriority OBJECT-TYPE=0A= SYNTAX Integer32 (0..255)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The value specifies the order of evaluation=0A= of the classifiers.=0A= The higher the value the higher the priority.=0A= The value of 0 is used as default in=0A= provisioned service flows classifiers.=0A= The default value of 64 is used for dynamic=0A= service flow classifiers.=0A= If the referenced parameter is not present=0A= in a classifier, this object reports the default = value=0A= as defined above."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.3.5"=0A= ::=3D { docsQosPktClassEntry 3 }=0A= =0A= docsQosPktClassIpTosLow OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(1))=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The low value of a range of TOS byte values.=0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value of = 0."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.1"=0A= ::=3D { docsQosPktClassEntry 4 }=0A= =0A= docsQosPktClassIpTosHigh OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(1))=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The 8-bit high value of a range of TOS byte=0A= values.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value of = 0."=0A= REFERENCE "SP-RFIv1.1-I07-010829, Appendix C.2.1.5.1"=0A= ::=3D { docsQosPktClassEntry 5 }=0A= =0A= docsQosPktClassIpTosMask OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(1))=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The mask value is bitwise ANDed with TOS byte=0A= in an IP packet and this value is used check=0A= range checking of TosLow and TosHigh.=0A= =0A= =0A= =0A= Expires September 2003 [Page 24]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value of = 0."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.1"=0A= ::=3D { docsQosPktClassEntry 6 }=0A= =0A= docsQosPktClassIpProtocol OBJECT-TYPE=0A= SYNTAX Integer32 (0..258)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object indicates the value of the IP=0A= Protocol field required for IP packets to match=0A= this rule.=0A= =0A= The value 256 matches traffic with any IP = Protocol=0A= value. The value 257 by convention matches both = TCP=0A= and UDP.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value of = 258."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.2"=0A= ::=3D { docsQosPktClassEntry 7 }=0A= =0A= docsQosPktClassInetAddressType OBJECT-TYPE=0A= SYNTAX InetAddressType=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The type of the internet address for=0A= docsQosPktClassInetSourceAddr,=0A= docsQosPktClassInetSourceMask,=0A= docsQosPktClassInetDestAddr, and=0A= docsQosPktClassInetDestMask.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= ipv4(1)."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.3"=0A= ::=3D { docsQosPktClassEntry 8 }=0A= =0A= docsQosPktClassInetSourceAddr OBJECT-TYPE=0A= SYNTAX InetAddress=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object specifies the value of the IP=0A= Source Address required for packets to match=0A= this rule. An IP packet matches the rule when=0A= the packet ip source address bitwise ANDed=0A= with the docsQosPktClassInetSourceMask value=0A= equals the docsQosPktClassInetSourceAddr value.=0A= =0A= The address type of this object is specified by=0A= docsQosPktClassInetAddressType.=0A= =0A= =0A= =0A= Expires September 2003 [Page 25]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= '00000000'H."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.3"=0A= ::=3D { docsQosPktClassEntry 9 }=0A= =0A= docsQosPktClassInetSourceMask OBJECT-TYPE=0A= SYNTAX InetAddress=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object specifies which bits of a packet's=0A= IP Source Address that are compared to match=0A= this rule.=0A= An IP packet matches the rule when the packet=0A= source address bitwise ANDed with the=0A= docsQosPktClassInetSourceMask value equals the=0A= docsQosIpPktClassInetSourceAddr value.=0A= =0A= The address type of this object is specified by=0A= docsQosPktClassInetAddressType.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= 'FFFFFFFF'H."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.4"=0A= ::=3D { docsQosPktClassEntry 10 }=0A= =0A= docsQosPktClassInetDestAddr OBJECT-TYPE=0A= SYNTAX InetAddress=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object specifies the value of the IP=0A= Destination Address required for packets to = match=0A= this rule. An IP packet matches the rule when=0A= the packet ip destination address=0A= bitwise ANDed with the=0A= docsQosPktClassInetDestMask value=0A= equals the docsQosPktClassInetDestAddr value.=0A= =0A= The address type of this object is specified by=0A= docsQosPktClassInetAddressType.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= '00000000'H."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.5"=0A= ::=3D { docsQosPktClassEntry 11 }=0A= =0A= docsQosPktClassInetDestMask OBJECT-TYPE=0A= SYNTAX InetAddress=0A= MAX-ACCESS read-only=0A= =0A= =0A= =0A= Expires September 2003 [Page 26]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= STATUS current=0A= DESCRIPTION "This object specifies which bits of a packet's=0A= IP Destination Address that are compared to=0A= match this rule.=0A= An IP packet matches the rule when the packet=0A= destination address bitwise ANDed with the=0A= docsQosPktClassInetDestMask value equals the=0A= docsQosIpPktClassInetDestAddr value.=0A= =0A= The address type of this object is specified by=0A= docsQosPktClassInetAddressType.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= 'FFFFFFFF'H."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.6"=0A= ::=3D { docsQosPktClassEntry 12 }=0A= =0A= docsQosPktClassSourcePortStart OBJECT-TYPE=0A= SYNTAX InetPortNumber=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object specifies the low end inclusive=0A= range of TCP/UDP source port numbers to which=0A= a packet is compared. This object is irrelevant=0A= for non-TCP/UDP IP packets.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value of = 0."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.7"=0A= ::=3D { docsQosPktClassEntry 13 }=0A= =0A= docsQosPktClassSourcePortEnd OBJECT-TYPE=0A= SYNTAX InetPortNumber=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object specifies the high end inclusive=0A= range of TCP/UDP source port numbers to which=0A= a packet is compared. This object is irrelevant=0A= for non-TCP/UDP IP packets.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= 65535."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.8"=0A= ::=3D { docsQosPktClassEntry 14 }=0A= =0A= docsQosPktClassDestPortStart OBJECT-TYPE=0A= SYNTAX InetPortNumber=0A= MAX-ACCESS read-only=0A= STATUS current=0A= =0A= =0A= =0A= Expires September 2003 [Page 27]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= DESCRIPTION "This object specifies the low end inclusive=0A= range of TCP/UDP destination port numbers to=0A= which a packet is compared.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value of = 0."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.9"=0A= ::=3D { docsQosPktClassEntry 15 }=0A= =0A= docsQosPktClassDestPortEnd OBJECT-TYPE=0A= SYNTAX InetPortNumber=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object specifies the high end inclusive=0A= range of TCP/UDP destination port numbers to = which=0A= a packet is compared.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= 65535."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.10"=0A= ::=3D { docsQosPktClassEntry 16 }=0A= =0A= docsQosPktClassDestMacAddr OBJECT-TYPE=0A= SYNTAX MacAddress=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "An Ethernet packet matches an entry when its=0A= destination MAC address bitwise ANDed with=0A= docsQosPktClassDestMacMask equals the value of=0A= docsQosPktClassDestMacAddr.=0A= =0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= '000000000000'H.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.6.1"=0A= ::=3D { docsQosPktClassEntry 17 }=0A= =0A= docsQosPktClassDestMacMask OBJECT-TYPE=0A= SYNTAX MacAddress=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "An Ethernet packet matches an entry when its=0A= destination MAC address bitwise ANDed with=0A= docsQosPktClassDestMacMask equals the value of=0A= docsQosPktClassDestMacAddr.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= =0A= =0A= =0A= Expires September 2003 [Page 28]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= '000000000000'H.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.6.1"=0A= ::=3D { docsQosPktClassEntry 18 }=0A= =0A= docsQosPktClassSourceMacAddr OBJECT-TYPE=0A= SYNTAX MacAddress=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "An Ethernet packet matches this entry when its=0A= source MAC address equals the value of=0A= this object.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value = of=0A= 'FFFFFFFFFFFF'H.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.6.2"=0A= ::=3D { docsQosPktClassEntry 19 }=0A= =0A= docsQosPktClassEnetProtocolType OBJECT-TYPE=0A= SYNTAX INTEGER {=0A= none(0),=0A= ethertype(1),=0A= dsap(2),=0A= mac(3),=0A= all(4)=0A= }=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object indicates the format of the layer 3=0A= protocol id in the Ethernet packet. A value of=0A= none(0) means that the rule does not use the=0A= layer 3 protocol type as a matching criteria.=0A= =0A= A value of ethertype(1) means that the rule=0A= applies only to frames which contains an=0A= EtherType value. Ethertype values are contained=0A= in packets using the Dec-Intel-Xerox (DIX)=0A= encapsulation or the RFC1042 Sub-Network Access=0A= Protocol (SNAP) encapsulation formats.=0A= =0A= A value of dsap(2) means that the rule applies=0A= only to frames using the IEEE802.3=0A= encapsulation format with a Destination Service=0A= Access Point (DSAP) other=0A= than 0xAA (which is reserved for SNAP).=0A= =0A= A value of mac(3) means that the rule applies=0A= only to MAC management messages for MAC = management=0A= messages.=0A= =0A= =0A= =0A= Expires September 2003 [Page 29]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= A value of all(4) means that the rule matches=0A= all Ethernet packets.=0A= =0A= If the Ethernet frame contains an 802.1P/Q Tag=0A= header (i.e. EtherType 0x8100), this object=0A= applies to the embedded EtherType field within=0A= the 802.1P/Q header.=0A= =0A= If the referenced parameter is not present=0A= in a classifier, this object reports the value of = 0.=0A= =0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.6.3"=0A= ::=3D { docsQosPktClassEntry 20 }=0A= =0A= docsQosPktClassEnetProtocol OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "If docsQosEthPktClassProtocolType is none(0),=0A= this object is ignored when considering whether=0A= a packet matches the current rule.=0A= =0A= If dosQosPktClassEnetProtocolType is = ethertype(1),=0A= this object gives the 16-bit value of the=0A= EtherType that the packet must match in order to=0A= match the rule.=0A= =0A= If docsQosPktClassEnetProtocolType is dsap(2), = the=0A= lower 8 bits of this object's value must match = the=0A= DSAP byte of the packet in order to match the=0A= rule.=0A= =0A= If docsQosPktClassEnetProtocolType is mac(3), = the=0A= lower 8 bits of this object value represent a=0A= lower bound (inclusive) of MAC management = message=0A= type codes matched, and the upper 8 bits of this=0A= object value represent the upper bound = (inclusive)=0A= of matched MAC message type codes. Certain=0A= message type codes are excluded from matching, = as=0A= specified in the reference.=0A= =0A= If the Ethernet frame contains an 802.1P/Q Tag = header=0A= (i.e. EtherType 0x8100), this object applies to = the=0A= embedded EtherType field within the 802.1P/Q = header.=0A= =0A= If the referenced parameter is not present in = the=0A= classifier, the value of this object is reported as = 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.6.3"=0A= ::=3D { docsQosPktClassEntry 21 }=0A= =0A= =0A= =0A= Expires September 2003 [Page 30]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= docsQosPktClassUserPriLow OBJECT-TYPE=0A= SYNTAX Integer32 (0..7)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object applies only to Ethernet frames=0A= using the 802.1P/Q tag header (indicated with=0A= EtherType 0x8100). Such frames include a 16-bit=0A= Tag that contains a 3 bit Priority field and=0A= a 12 bit VLAN number.=0A= =0A= Tagged Ethernet packets must have a 3-bit=0A= Priority field within the range of=0A= docsQosPktClassPriLow and docsQosPktClassPriHigh = in=0A= order to match this rule.=0A= =0A= If the referenced parameter is not present in = the=0A= classifier, the value of this object is reported as = 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.7.1"=0A= ::=3D { docsQosPktClassEntry 22 }=0A= =0A= docsQosPktClassUserPriHigh OBJECT-TYPE=0A= SYNTAX Integer32 (0..7)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object applies only to Ethernet frames=0A= using the 802.1P/Qtag header (indicated with=0A= EtherType 0x8100). Such frames include a 16-bit=0A= Tag that contains a 3 bit Priority field and=0A= a 12 bit VLAN number.=0A= =0A= Tagged Ethernet packets must have a 3-bit=0A= Priority field within the range of=0A= docsQosPktClassPriLow and=0A= docsQosPktClassPriHigh in order to match this=0A= rule.=0A= =0A= If the referenced parameter is not present in = the=0A= classifier, the value of this object is reported=0A= as 7.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.7.1"=0A= ::=3D { docsQosPktClassEntry 23 }=0A= =0A= docsQosPktClassVlanId OBJECT-TYPE=0A= SYNTAX Integer32 (0..4095)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object applies only to Ethernet frames=0A= using the 802.1P/Q tag header.=0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 31]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= If this object's value is nonzero, tagged=0A= packets must have a VLAN Identifier that matches=0A= the value in order to match the rule.=0A= =0A= Only the least significant 12 bits of this = object's=0A= value are valid.=0A= =0A= If the referenced parameter is not present in = the=0A= classifier, the value of this object is reported=0A= as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.7.2"=0A= ::=3D { docsQosPktClassEntry 24 }=0A= =0A= docsQosPktClassStateActive OBJECT-TYPE=0A= SYNTAX TruthValue=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object indicates whether or not the = classifier=0A= is enabled to classify packets to a Service = Flow.=0A= =0A= If the referenced parameter is not present in = the=0A= classifier, the value of this object is reported=0A= as true(1)."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.3.6"=0A= ::=3D { docsQosPktClassEntry 25 }=0A= =0A= docsQosPktClassPkts OBJECT-TYPE=0A= SYNTAX Counter64=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object counts the number of packets that = have=0A= been classified using this entry. This=0A= includes all packets delivered to a service flow=0A= maximum rate policing function, whether or not = that=0A= function drops the packets.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosPktClassEntry 26 }=0A= =0A= =0A= docsQosPktClassBitMap OBJECT-TYPE=0A= SYNTAX BITS { -- Reference = SP-RFIv1.1-I09-020830=0A= rulePriority(0), -- Appendix C.2.1.3.4=0A= activationState(1), -- Appendix C.2.1.3.6=0A= ipTos(2), -- Appendix C.2.1.5.1=0A= ipProtocol(3), -- Appendix C.2.1.5.2=0A= ipSourceAddr(4), -- Appendix C.2.1.5.3=0A= ipSourceMask(5), -- Appendix C.2.1.5.4=0A= =0A= =0A= =0A= Expires September 2003 [Page 32]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= ipDestAddr(6), -- Appendix C.2.1.5.5=0A= ipDestMask(7), -- Appendix C.2.1.5.6=0A= sourcePortStart(8), -- Appendix C.2.1.5.7=0A= sourcePortEnd(9), -- Appendix C.2.1.5.8=0A= destPortStart(10), -- Appendix C.2.1.5.9=0A= destPortEnd(11), -- Appendix C.2.1.5.10=0A= destMac(12), -- Appendix C.2.1.6.1=0A= sourceMac(13), -- Appendix C.2.1.6.2=0A= ethertype(14), -- Appendix C.2.1.6.3=0A= userPri(15), -- Appendix C.2.1.7.1=0A= vlanId(16) -- Appendix C.2.1.7.2=0A= }=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION=0A= "This object indicates which parameter encodings = were=0A= actually present in the DOCSIS packet classifier=0A= encoding signaled in the DOCSIS message that=0A= created or modified the classifier. Note that=0A= Dynamic Service Change messages have replace=0A= semantics, so that all non-default parameters = must=0A= be present whether the classifier is being = created=0A= or changed.=0A= =0A= A bit of of this object is set to 1 if the = parameter=0A= indicated by the comment was present in the = classifier=0A= encoding, and 0 otherwise.=0A= =0A= Note that BITS are encoded most significant bit=0A= first, so that if e.g. bits 6 and 7 are set, this = object=0A= is encoded as the octet string '030000'H.=0A= "=0A= ::=3D { docsQosPktClassEntry 27 }=0A= =0A= --=0A= -- QOS Parameter Set Table=0A= --=0A= docsQosParamSetTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosParamSetEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table describes the set of DOCSIS 1.1 and = 2.0=0A= QOS parameters defined in a managed device.=0A= =0A= The ifIndex index specifies a DOCSIS MAC Domain.=0A= The docsQosServiceFlowId index specifies a = particular=0A= Service Flow.=0A= The docsQosParamSetType index indicates whether=0A= the active, admitted, or provisioned QOS = Parameter=0A= Set is being described by the row.=0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 33]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= Only the QOS Parameter Sets of Docsis 1.1 and = 2.0=0A= service flows are represented in this table.=0A= Docsis 1.0 QOS service profiles are not=0A= represented in this table.=0A= =0A= Each row corresponds to a DOCSIS QOS Parameter = Set=0A= as signaled via DOCSIS MAC management messages.=0A= Each object in the row corresponds to one or=0A= part of one DOCSIS 1.1 Service Flow Encoding.=0A= The docsQosParamSetBitMap object in the row = indicates=0A= which particular parameters were signaled in=0A= the original registration or dynamic service=0A= request message that created the QOS Parameter = Set.=0A= =0A= In many cases, even if a QOS Parameter Set = parameter=0A= was not signaled, the DOCSIS specification calls=0A= for a default value to be used. That default = value=0A= is reported as the value of the corresponding = object=0A= in this row.=0A= =0A= Many objects are not applicable depending on=0A= the service flow direction or upstream = scheduling=0A= type. The object value reported in this case=0A= is specified in the DESCRIPTION clause.=0A= "=0A= ::=3D { docsQosMIBObjects 2 }=0A= =0A= -- docsQosParamSetEntry { docsQosParamSetTable 1 } was=0A= -- removed in an initial and unimplemented version of this mib.=0A= =0A= docsQosParamSetEntry OBJECT-TYPE=0A= SYNTAX DocsQosParamSetEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION=0A= "A unique set of QOS parameters."=0A= INDEX {=0A= ifIndex, docsQosServiceFlowId, docsQosParamSetType=0A= }=0A= ::=3D { docsQosParamSetTable 1 }=0A= =0A= DocsQosParamSetEntry ::=3D SEQUENCE {=0A= docsQosParamSetServiceClassName DisplayString,=0A= docsQosParamSetPriority Integer32,=0A= docsQosParamSetMaxTrafficRate DocsQosBitRate,=0A= docsQosParamSetMaxTrafficBurst Unsigned32,=0A= docsQosParamSetMinReservedRate DocsQosBitRate,=0A= docsQosParamSetMinReservedPkt Integer32,=0A= docsQosParamSetActiveTimeout Integer32,=0A= docsQosParamSetAdmittedTimeout Integer32,=0A= docsQosParamSetMaxConcatBurst Integer32,=0A= =0A= =0A= =0A= Expires September 2003 [Page 34]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= docsQosParamSetSchedulingType DocsQosSchedulingType,=0A= docsQosParamSetNomPollInterval Unsigned32,=0A= docsQosParamSetTolPollJitter Unsigned32,=0A= docsQosParamSetUnsolicitGrantSize Integer32,=0A= docsQosParamSetNomGrantInterval Unsigned32,=0A= docsQosParamSetTolGrantJitter Unsigned32,=0A= docsQosParamSetGrantsPerInterval Integer32,=0A= docsQosParamSetTosAndMask OCTET STRING,=0A= docsQosParamSetTosOrMask OCTET STRING,=0A= docsQosParamSetMaxLatency Unsigned32,=0A= docsQosParamSetType INTEGER,=0A= docsQosParamSetRequestPolicyOct OCTET STRING,=0A= docsQosParamSetBitMap BITS=0A= }=0A= =0A= docsQosParamSetServiceClassName OBJECT-TYPE=0A= SYNTAX DisplayString=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Refers to the Service Class Name that the=0A= parameter set values were derived.=0A= =0A= If the referenced parameter is not present in = the=0A= corresponding DOCSIS QOS Parameter Set, the = default=0A= value of this object is a zero length string.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.3.4"=0A= ::=3D { docsQosParamSetEntry 4 }=0A= =0A= docsQosParamSetPriority OBJECT-TYPE=0A= SYNTAX Integer32 (0..7)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The relative priority of a service flow.=0A= Higher numbers indicate higher priority.=0A= This priority should only be used to = differentiate=0A= service flow with identical parameter sets.=0A= =0A= If the referenced parameter is not present in = the=0A= corresponding DOCSIS QOS Parameter Set, the = default=0A= value of this object is 0. If the parameter is=0A= not applicable, the reported value is 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.1"=0A= ::=3D { docsQosParamSetEntry 5 }=0A= =0A= docsQosParamSetMaxTrafficRate OBJECT-TYPE=0A= SYNTAX DocsQosBitRate=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Maximum sustained traffic rate allowed for this=0A= =0A= =0A= =0A= Expires September 2003 [Page 35]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= service flow in bits/sec. Must count all MAC = frame=0A= data PDU from the bytes following the MAC header = HCS to=0A= the end of the CRC. The number of bytes=0A= forwarded is limited during any time interval.=0A= The value 0 means no maximum traffic rate is=0A= enforced. This object applies to both upstream = and=0A= downstream service flows.=0A= =0A= If the referenced parameter is not present in = the=0A= corresponding DOCSIS QOS Parameter Set, the = default=0A= value of this object is 0. If the parameter is=0A= not applicable, it is reported as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.2"=0A= ::=3D { docsQosParamSetEntry 6 }=0A= =0A= docsQosParamSetMaxTrafficBurst OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the token bucket size in bytes=0A= for this parameter set. The value is calculated=0A= from the byte following the MAC header HCS to=0A= the end of the CRC. This object is applied in=0A= conjunction with docsQosParamSetMaxTrafficRate = to=0A= calculate maximum sustained traffic rate.=0A= =0A= If the referenced parameter is not present in = the=0A= corresponding DOCSIS QOS Parameter Set, the = default=0A= value of this object for scheduling types=0A= bestEffort (2), nonRealTimePollingService(3),=0A= and realTimePollingService(4) is 3044.=0A= =0A= If this parameter is not applicable, it is = reported=0A= as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.3"=0A= ::=3D { docsQosParamSetEntry 7 }=0A= =0A= docsQosParamSetMinReservedRate OBJECT-TYPE=0A= SYNTAX DocsQosBitRate=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the guaranteed minimum rate in=0A= bits/sec for this parameter set. The value is=0A= calculated from the byte following the MAC=0A= header HCS to the end of the CRC. The default=0A= value of 0 has the meaning that no bandwidth=0A= is reserved.=0A= If the referenced parameter is not present in = the=0A= corresponding DOCSIS QOS Parameter Set, the = default=0A= =0A= =0A= =0A= Expires September 2003 [Page 36]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= value of this object is 0. If the parameter=0A= is not applicable, it is reported as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.4"=0A= ::=3D { docsQosParamSetEntry 8 }=0A= =0A= docsQosParamSetMinReservedPkt OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies an assumed minimum packet size in=0A= bytes for which the = docsQosParamSetMinReservedRate=0A= will be provided. The value is calculated from=0A= the byte following the MAC header HCS to the=0A= end of the CRC.=0A= =0A= If the referenced parameter is omitted from a=0A= DOCSIS QOS parameter set, the default value is=0A= CMTS implementation dependent. In this case, the=0A= CMTS reports the default value it is using and = the=0A= CM reports a value of 0. If the referenced=0A= parameter is not applicable to the direction or=0A= scheduling type of the service flow, both CMTS = and=0A= CM report this object's value as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.5"=0A= ::=3D { docsQosParamSetEntry 9 }=0A= =0A= docsQosParamSetActiveTimeout OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= UNITS "seconds"=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the maximum duration in seconds that=0A= resources remain unused on an active service=0A= flow before CMTS signals that both active and=0A= admitted parameters set are null.=0A= The default value of 0 signifies an=0A= infinite amount of time.=0A= =0A= If the referenced parameter is not present in = the=0A= corresponding DOCSIS QOS Parameter Set, the = default=0A= value of this object is 0.=0A= "=0A= =0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.6"=0A= ::=3D { docsQosParamSetEntry 10 }=0A= =0A= docsQosParamSetAdmittedTimeout OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= UNITS "seconds"=0A= =0A= =0A= =0A= Expires September 2003 [Page 37]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the maximum duration in seconds that=0A= resources remain in admitted state before=0A= resources must be released.=0A= The value of 0 signifies an infinite amount=0A= of time.=0A= =0A= If the referenced parameter is not present in = the=0A= corresponding DOCSIS QOS Parameter Set, the=0A= default value of this object is 200.=0A= "=0A= =0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.7"=0A= DEFVAL { 200 }=0A= ::=3D { docsQosParamSetEntry 11 }=0A= =0A= docsQosParamSetMaxConcatBurst OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the maximum concatenated burst in=0A= bytes which an upstream service flow is = allowed.=0A= The value is calculated from the FC byte of the=0A= Concatenation MAC Header to the last CRC byte in=0A= of the last concatenated MAC frame, inclusive.=0A= The value of 0 specifies no maximum burst.=0A= =0A= If the referenced parameter is not present in = the=0A= corresponding DOCSIS QOS Parameter Set, the = default=0A= value of this object for scheduling types=0A= bestEffort(2), nonRealTimePollingService(3), and=0A= realTimePollingService(4) is 1522. If the = parameter=0A= is not applicable, this object's value is = reported=0A= as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.1"=0A= ::=3D { docsQosParamSetEntry 12 }=0A= =0A= =0A= docsQosParamSetSchedulingType OBJECT-TYPE=0A= SYNTAX DocsQosSchedulingType=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the upstream scheduling service used = for=0A= upstream service flow.=0A= =0A= If the referenced parameter is not present in = the=0A= corresponding DOCSIS QOS Parameter Set of an=0A= upstream service flow, the default value of this=0A= object is bestEffort(2). For QOS parameter sets = of=0A= =0A= =0A= =0A= Expires September 2003 [Page 38]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= downstream service flows, this object's value is=0A= reported as undefined(1).=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.2"=0A= ::=3D { docsQosParamSetEntry 13 }=0A= =0A= docsQosParamSetNomPollInterval OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the nominal interval in microseconds=0A= between successive unicast request=0A= opportunities on an upstream service flow.=0A= =0A= This object applies only to upstream service = flows=0A= with DocsQosSchedulingType of value=0A= nonRealTimePollingService(3),=0A= realTimePollingService(4), and=0A= unsolictedGrantServiceWithAD(5). The parameter = is=0A= mandatory for realTimePollingService(4). If the=0A= parameter is omitted with=0A= nonRealTimePollingService(3), the CMTS uses an=0A= implementation dependent value. If the = parameter=0A= is omitted with unsolictedGrantServiceWithAD(5),=0A= the CMTS uses as a default value the value of = the=0A= Nominal Grant Interval parameter. In all cases,=0A= the CMTS reports the value it is using when the=0A= parameter is applicable. The CM reports the=0A= signaled parameter value if it was signaled,=0A= and 0 otherwise.=0A= =0A= If the referenced parameter is not applicable to=0A= the direction or scheduling type of the=0A= corresponding DOCSIS QOS Parameter Set, both=0A= CMTS and CM report this object's value as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.4"=0A= ::=3D { docsQosParamSetEntry 15 }=0A= =0A= docsQosParamSetTolPollJitter OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the maximum amount of time in=0A= microseconds that the unicast request interval=0A= may be delayed from the nominal periodic=0A= schedule on an upstream service flow.=0A= =0A= This parameter is applicable only to upstream=0A= =0A= =0A= =0A= Expires September 2003 [Page 39]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= service flows with a DocsQosSchedulingType of=0A= realTimePollingService(4) or=0A= unsolictedGrantServiceWithAD(5).=0A= =0A= If the referenced parameter is applicable but = not=0A= present in the corresponding DOCSIS QOS = Parameter=0A= Set, the CMTS uses an implementation dependent=0A= value and reports the value it is using.=0A= The CM reports a value of 0 in this case.=0A= =0A= If the parameter is not applicable to the=0A= direction or upstream scheduling type of the=0A= service flow, both CMTS and CM report this=0A= object's value as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.5"=0A= ::=3D { docsQosParamSetEntry 16 }=0A= =0A= docsQosParamSetUnsolicitGrantSize OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the unsolicited grant size in bytes.=0A= The grant size includes the entire MAC frame=0A= data PDU from the Frame Control byte to end of=0A= the MAC frame.=0A= =0A= The referenced parameter is applicable only=0A= for upstream flows with a DocsQosSchedulingType = of=0A= of unsolicitedGrantServicewithAD(5) or=0A= unsolicitedGrantService(6), and is mandatory=0A= when applicable. Both CMTS and CM report=0A= the signaled value of the parameter in this=0A= case.=0A= =0A= If the referenced parameter is not applicable to=0A= the direction or scheduling type of the=0A= corresponding DOCSIS QOS Parameter Set, both=0A= CMTS and CM report this object's value as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.6"=0A= ::=3D { docsQosParamSetEntry 17 }=0A= =0A= docsQosParamSetNomGrantInterval OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the nominal interval in microseconds=0A= between successive data grant opportunities=0A= on an upstream service flow.=0A= =0A= =0A= =0A= Expires September 2003 [Page 40]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= The referenced parameter is applicable only=0A= for upstream flows with a DocsQosSchedulingType = of=0A= of unsolicitedGrantServicewithAD(5) or=0A= unsolicitedGrantService(6), and is mandatory=0A= when applicable. Both CMTS and CM report the=0A= signaled value of the parameter in this case.=0A= =0A= If the referenced parameter is not applicable to=0A= the direction or scheduling type of the=0A= corresponding DOCSIS QOS Parameter Set, both=0A= CMTS and CM report this object's value as 0.=0A= "=0A= =0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.7"=0A= ::=3D { docsQosParamSetEntry 18 }=0A= =0A= docsQosParamSetTolGrantJitter OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the maximum amount of time in=0A= microseconds that the transmission opportunities=0A= may be delayed from the nominal periodic = schedule.=0A= =0A= The referenced parameter is applicable only=0A= for upstream flows with a DocsQosSchedulingType = of=0A= of unsolicitedGrantServicewithAD(5) or=0A= unsolicitedGrantService(6), and is mandatory=0A= when applicable. Both CMTS and CM report the=0A= signaled value of the parameter in this case.=0A= =0A= If the referenced parameter is not applicable to=0A= the direction or scheduling type of the=0A= corresponding DOCSIS QOS Parameter Set, both=0A= CMTS and CM report this object's value as 0.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.8"=0A= ::=3D { docsQosParamSetEntry 19 }=0A= =0A= docsQosParamSetGrantsPerInterval OBJECT-TYPE=0A= SYNTAX Integer32 (0..127)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the number of data grants per Nominal=0A= Grant Interval=0A= (docsQosParamSetNomGrantInterval).=0A= =0A= The referenced parameter is applicable only=0A= for upstream flows with a DocsQosSchedulingType = of=0A= of unsolicitedGrantServicewithAD(5) or=0A= =0A= =0A= =0A= Expires September 2003 [Page 41]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= unsolicitedGrantService(6), and is mandatory=0A= when applicable. Both CMTS and CM report the=0A= signaled value of the parameter in this case.=0A= =0A= If the referenced parameter is not applicable to=0A= the direction or scheduling type of the=0A= corresponding DOCSIS QOS Parameter Set, both=0A= CMTS and CM report this object's value as 0.=0A= "=0A= =0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.9"=0A= ::=3D { docsQosParamSetEntry 20 }=0A= =0A= docsQosParamSetTosAndMask OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(1))=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the AND mask for IP TOS byte for = overwriting=0A= IP packets TOS value. The IP packets TOS byte = is=0A= bitwise ANDed with docsQosParamSetTosAndMask and=0A= result is bitwise ORed with = docsQosParamSetTosORMask=0A= and result is written to IP packet TOS byte.=0A= A value of 'FF'H for docsQosParamSetTosAndMask = and=0A= a value of '00'H for docsQosParamSetTosOrMask = means=0A= that IP Packet TOS byte is not overwritten.=0A= =0A= This combination is reported if the referenced=0A= parameter is not present in a QOS Parameter Set.=0A= =0A= Even though the this object is only enforced by = the=0A= Cable Modem Termination System (CMTS),=0A= Cable Modems must report the value as signaled = in=0A= the referenced parameter."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.10"=0A= ::=3D { docsQosParamSetEntry 21 }=0A= =0A= docsQosParamSetTosOrMask OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(1))=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies the OR mask for IP TOS byte.=0A= See the description of docsQosParamSetTosAndMask=0A= for further details."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.10"=0A= ::=3D { docsQosParamSetEntry 22 }=0A= =0A= docsQosParamSetMaxLatency OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-only=0A= STATUS current=0A= =0A= =0A= =0A= Expires September 2003 [Page 42]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= DESCRIPTION "Specifies the maximum latency between the=0A= reception of a packet by the CMTS on its NSI=0A= and the forwarding of the packet to the RF=0A= interface. A value of 0 signifies no maximum=0A= latency enforced. This object only applies to=0A= downstream service flows.=0A= =0A= If the referenced parameter is not present in = the=0A= corresponding downstream DOCSIS QOS Parameter = Set,=0A= the default value is 0. This parameter is=0A= not applicable to upstream DOCSIS QOS Parameter = Sets,=0A= and its value is reported as 0 in this case.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.7.1"=0A= ::=3D { docsQosParamSetEntry 23 }=0A= =0A= =0A= docsQosParamSetType OBJECT-TYPE=0A= SYNTAX INTEGER {=0A= active (1),=0A= admitted (2),=0A= provisioned (3)=0A= }=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Defines the type of the QOS parameter set = defined=0A= by this row. active(1) indicates the Active QOS=0A= parameter set, describing the service currently=0A= being provided by the Docsis MAC domain to the=0A= service flow. admitted(2) indicates the Admitted=0A= QOS Parameter Set, describing services reserved = by=0A= by the Docsis MAC domain for use by the service = flow.=0A= provisioned (3) describes the QOS Parameter Set=0A= defined in the DOCSIS CM Configuration file for=0A= the service flow."=0A= REFERENCE "SP-RFIv1.1-I09-020830, 8.1.5"=0A= ::=3D { docsQosParamSetEntry 24 }=0A= =0A= docsQosParamSetRequestPolicyOct OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(4))=0A= -- A 32-bit mask represented most significant = byte=0A= -- first. The 32 bit integer represented in this = manner=0A= -- equals the binary value of the referenced = integer=0A= -- parameter of the DOCSIS RFI specification.=0A= -- The BITS syntax is not used in order to avoid=0A= -- the confusion caused by different bit = numbering=0A= -- conventions.=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Specifies which transmit interval opportunities=0A= the CM omits for upstream transmission requests = and=0A= =0A= =0A= =0A= Expires September 2003 [Page 43]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= packet transmissions. This object takes its=0A= default value for downstream service flows.=0A= =0A= Unless otherwise indicated, a bit value of 1 = means=0A= that a CM must *not* use that opportunity for=0A= upstream transmission.=0A= =0A= Calling bit 0 the least significant bit of the=0A= least significant (4th) octet, and increasing=0A= bit number with significance, the bit = definitions=0A= are as defined below:=0A= =0A= broadcastReqOpp(0):=0A= all CMs broadcast request opportunities=0A= =0A= priorityReqMulticastReq(1):=0A= priority request multicast request = opportunities=0A= =0A= reqDataForReq(2):=0A= request/data opportunities for requests=0A= =0A= reqDataForData(3):=0A= request/data opportunities for data=0A= =0A= piggybackReqWithData(4):=0A= piggyback requests with data=0A= =0A= concatenateData(5):=0A= concatenate data=0A= =0A= fragmentData(6):=0A= fragment data=0A= =0A= suppresspayloadheaders(7):=0A= suppress payload headers=0A= =0A= dropPktsExceedUGSize(8):=0A= A value of 1 mean that service flow must = drop=0A= packet that do not fit in the Unsolicited=0A= Grant size=0A= =0A= If the referenced parameter is not present in=0A= a QOS Parameter Set, the value of this object is=0A= reported as '00000000'H.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.3"=0A= ::=3D { docsQosParamSetEntry 25 }=0A= =0A= docsQosParamSetBitMap OBJECT-TYPE=0A= -- Each bit corresponds to a = parameter=0A= -- from SP-RFI-v1.1-I07-010829, = Appendix C=0A= =0A= =0A= =0A= Expires September 2003 [Page 44]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= SYNTAX BITS { -- in the indicated section number.=0A= trafficPriority(0), -- C.2.2.5.1=0A= maxTrafficRate(1), -- C.2.2.5.2=0A= maxTrafficBurst(2), -- C.2.2.5.3=0A= minReservedRate(3), -- C.2.2.5.4=0A= minReservedPkt(4), -- C.2.2.5.5=0A= activeTimeout(5), -- C.2.2.5.6=0A= admittedTimeout(6), -- C.2.2.5.7=0A= maxConcatBurst(7), -- C.2.2.6.1=0A= schedulingType(8), -- C.2.2.6.2=0A= requestPolicy(9), -- C.2.2.6.3=0A= nomPollInterval(10), -- C.2.2.6.4=0A= tolPollJitter(11), -- C.2.2.6.5=0A= unsolicitGrantSize(12), -- C.2.2.6.6=0A= nomGrantInterval(13), -- C.2.2.6.7=0A= tolGrantJitter(14), -- C.2.2.6.8=0A= grantsPerInterval(15), -- C.2.2.6.9=0A= tosOverwrite(16), -- C.2.2.6.10=0A= maxLatency(17) -- C.2.2.7.1=0A= }=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object indicates the set of QOS Parameter=0A= Set parameters actually signaled in the=0A= DOCSIS registration or dynamic service request=0A= message that created or modified the QOS Parameter = Set.=0A= A bit is set to 1 when the parameter described=0A= by the indicated reference section is present=0A= in the original request.=0A= =0A= Note that when Service Class names are expanded,=0A= the registration or dynamic response message may=0A= contain parameters as expanded by the CMTS based=0A= on a stored service class. These expanded=0A= parameters are *not* indicated by a 1 bit in = this=0A= object.=0A= =0A= Note that even though some QOS Parameter Set=0A= parameters may not be signaled in a message=0A= (so that the paramater's bit in this object is = 0)=0A= the DOCSIS specification calls for default=0A= values to be used. These default values are=0A= reported as the corresponding object's value in=0A= the row.=0A= =0A= Note that BITS objects are encoded most=0A= significant bit first. For example, if bits=0A= 1 and 16 are set, the value of this object=0A= is the octet string '400080'H.=0A= =0A= "=0A= =0A= =0A= =0A= Expires September 2003 [Page 45]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= ::=3D { docsQosParamSetEntry 26 }=0A= =0A= --=0A= -- Service Flow Table=0A= --=0A= docsQosServiceFlowTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosServiceFlowEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table describes the set of Docsis-QOS=0A= Service Flows in a managed device. "=0A= ::=3D { docsQosMIBObjects 3 }=0A= =0A= docsQosServiceFlowEntry OBJECT-TYPE=0A= SYNTAX DocsQosServiceFlowEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Describes a service flow.=0A= An entry in the table exists for each=0A= Service Flow ID. The ifIndex is an=0A= ifType of docsCableMaclayer(127)."=0A= INDEX {=0A= ifIndex,=0A= docsQosServiceFlowId=0A= }=0A= ::=3D { docsQosServiceFlowTable 1 }=0A= =0A= DocsQosServiceFlowEntry ::=3D SEQUENCE {=0A= docsQosServiceFlowId Unsigned32,=0A= docsQosServiceFlowSID Unsigned32,=0A= docsQosServiceFlowDirection = DocsQosRfMacIfDirection,=0A= docsQosServiceFlowPrimary TruthValue=0A= }=0A= =0A= docsQosServiceFlowId OBJECT-TYPE=0A= SYNTAX Unsigned32 (1..4294967295)=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "An index assigned to a service flow by CMTS."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.3.2"=0A= ::=3D { docsQosServiceFlowEntry 1 }=0A= =0A= docsQosServiceFlowSID OBJECT-TYPE=0A= SYNTAX Unsigned32 (0..16383)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Service Identifier (SID) assigned to an=0A= admitted or active service flow. This object=0A= reports a value of 0 if a Service Id is not=0A= associated with the service flow. Only active=0A= or admitted upstream service flows will have a=0A= =0A= =0A= =0A= Expires September 2003 [Page 46]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= Service Id (SID)."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.3.3"=0A= ::=3D { docsQosServiceFlowEntry 2 }=0A= =0A= docsQosServiceFlowDirection OBJECT-TYPE=0A= SYNTAX DocsQosRfMacIfDirection=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The direction of the service flow."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.1/2"=0A= ::=3D { docsQosServiceFlowEntry 3 }=0A= =0A= docsQosServiceFlowPrimary OBJECT-TYPE=0A= SYNTAX TruthValue=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Object reflects whether service flow is the = primary=0A= or a secondary service flow.=0A= =0A= A primary service flow is the default service = flow=0A= for otherwise unclassified traffic and all MAC=0A= messages."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Section 8.1 "=0A= ::=3D { docsQosServiceFlowEntry 4 }=0A= =0A= --=0A= -- Service Flow Stats Table=0A= --=0A= docsQosServiceFlowStatsTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosServiceFlowStatsEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table describes statistics associated with = the=0A= Service Flows in a managed device. "=0A= ::=3D { docsQosMIBObjects 4 }=0A= =0A= docsQosServiceFlowStatsEntry OBJECT-TYPE=0A= SYNTAX DocsQosServiceFlowStatsEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Describes a set of service flow statistics.=0A= An entry in the table exists for each=0A= Service Flow ID. The ifIndex is an=0A= ifType of docsCableMaclayer(127)."=0A= INDEX {=0A= ifIndex,=0A= docsQosServiceFlowId=0A= }=0A= ::=3D { docsQosServiceFlowStatsTable 1 }=0A= =0A= DocsQosServiceFlowStatsEntry ::=3D SEQUENCE {=0A= =0A= =0A= =0A= Expires September 2003 [Page 47]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= docsQosServiceFlowPkts Counter64,=0A= docsQosServiceFlowOctets Counter64,=0A= docsQosServiceFlowTimeCreated TimeStamp,=0A= docsQosServiceFlowTimeActive Counter32,=0A= docsQosServiceFlowPHSUnknowns Counter32,=0A= docsQosServiceFlowPolicedDropPkts Counter32,=0A= docsQosServiceFlowPolicedDelayPkts Counter32=0A= }=0A= =0A= docsQosServiceFlowPkts OBJECT-TYPE=0A= SYNTAX Counter64=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Packet Data PDUs classified to = this=0A= service flow and forwarded beyond a service flow=0A= maximum rate policing function.=0A= This object does not count MAC-specific=0A= management messages.=0A= CMs not classifying downstream packets may = report=0A= this object's value as 0.=0A= =0A= Particularly for UGS flows, packets sent on the=0A= primary service flow in violation of the UGS = grant=0A= size should be counted only on the primary = service=0A= flow's counters.=0A= =0A= Unclassified upstream user data packets (i.e. = non=0A= MAC-management) forwarded to the default = upstream=0A= service flow should be incremented for this = object.=0A= =0A= This object does include packets counted by=0A= docsQosServiceFlowPolicedDelayPkts, but does not = include=0A= packets counted by = docsQosServiceFlowPolicedDropPkts.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosServiceFlowStatsEntry 1 }=0A= =0A= docsQosServiceFlowOctets OBJECT-TYPE=0A= SYNTAX Counter64=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of octets from the byte after the MAC=0A= header HCS to the end of the CRC for all packets = counted=0A= in the docsQosServiceFlowPkts object for this = row.=0A= Note that this counts the octets after payload = header=0A= suppression has been applied. CMs not classifying = to a=0A= downstream service flow may report this object's=0A= value as 0 for that flow.=0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 48]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosServiceFlowStatsEntry 2 }=0A= =0A= docsQosServiceFlowTimeCreated OBJECT-TYPE=0A= SYNTAX TimeStamp=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The value of sysUpTime when the service flow=0A= was created."=0A= ::=3D { docsQosServiceFlowStatsEntry 3 }=0A= =0A= docsQosServiceFlowTimeActive OBJECT-TYPE=0A= SYNTAX Counter32=0A= UNITS "seconds"=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of seconds that the service flow=0A= has been active.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosServiceFlowStatsEntry 4 }=0A= =0A= docsQosServiceFlowPHSUnknowns OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of packets received on the service = flow=0A= with an unknown payload header suppression = index.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosServiceFlowStatsEntry 5 }=0A= =0A= docsQosServiceFlowPolicedDropPkts OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Packet Data PDUs classified to = this=0A= service flow dropped due to:=0A= (1) implementation-dependent excessive delay = while=0A= enforcing the Maximum Sustained Traffic = Rate; or=0A= (2) UGS packets dropped due to exceeding the=0A= Unsolicited Grant Size with a=0A= Request/Transmission policy that requires = such=0A= packets to be dropped.=0A= Classified packets dropped due to other reasons = must be=0A= =0A= =0A= =0A= Expires September 2003 [Page 49]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= counted in ifOutDiscards for interface of this=0A= service flow.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosServiceFlowStatsEntry 6 }=0A= =0A= docsQosServiceFlowPolicedDelayPkts OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "This object counts only packets delayed in order = to=0A= maintain the Maximum Sustained Traffic Rate. This = object=0A= will always report a value of 0 for UGS flows = because the=0A= Maximum Sustained Traffic Rate does not apply.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosServiceFlowStatsEntry 7 }=0A= =0A= --=0A= -- Upstream Service Flow Stats Table (CMTS ONLY)=0A= --=0A= docsQosUpstreamStatsTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosUpstreamStatsEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table describes statistics associated with=0A= upstream service flows. All counted frames must=0A= be received without an FCS error."=0A= ::=3D { docsQosMIBObjects 5 }=0A= =0A= docsQosUpstreamStatsEntry OBJECT-TYPE=0A= SYNTAX DocsQosUpstreamStatsEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Describes a set of upstream service flow = statistics.=0A= An entry in the table exists for each=0A= upstream Service Flow in a managed device.=0A= The ifIndex is an ifType of = docsCableMaclayer(127)."=0A= INDEX {=0A= ifIndex,=0A= docsQosSID=0A= }=0A= ::=3D { docsQosUpstreamStatsTable 1 }=0A= =0A= DocsQosUpstreamStatsEntry ::=3D SEQUENCE {=0A= docsQosSID Unsigned32,=0A= docsQosUpstreamFragments Counter32,=0A= =0A= =0A= =0A= Expires September 2003 [Page 50]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= docsQosUpstreamFragDiscards Counter32,=0A= docsQosUpstreamConcatBursts Counter32=0A= }=0A= =0A= docsQosSID OBJECT-TYPE=0A= SYNTAX Unsigned32 (1..16383)=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Identifies a service id for an admitted or = active=0A= upstream service flow."=0A= ::=3D { docsQosUpstreamStatsEntry 1 }=0A= =0A= docsQosUpstreamFragments OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of fragmentation headers received on = an=0A= upstream service flow, regardless of whether=0A= the fragment was correctly reassembled into a=0A= valid packet.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosUpstreamStatsEntry 2 }=0A= =0A= docsQosUpstreamFragDiscards OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of upstream fragments discarded and = not=0A= assembled into a valid upstream packet.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosUpstreamStatsEntry 3 }=0A= =0A= docsQosUpstreamConcatBursts OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of concatenation headers received on = an=0A= upstream service flow.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosUpstreamStatsEntry 4 }=0A= =0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 51]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= --=0A= -- Dynamic Service Stats Table=0A= --=0A= docsQosDynamicServiceStatsTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosDynamicServiceStatsEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table describes statistics associated with = the=0A= Dynamic Service Flows in a managed device. "=0A= ::=3D { docsQosMIBObjects 6 }=0A= =0A= docsQosDynamicServiceStatsEntry OBJECT-TYPE=0A= SYNTAX DocsQosDynamicServiceStatsEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Describes a set of dynamic service flow = statistics.=0A= Two entries exist for each Docsis mac layer=0A= interface for the upstream and downstream = direction.=0A= On the CMTS, the downstream direction row = indicates=0A= messages transmitted or transactions originated=0A= by the CMTS. The upstream direction row = indicates=0A= messages received or transaction originated by = the=0A= CM. On the CM, the downstream direction row=0A= indicates messages received or transactions=0A= originated by the CMTS. The upstream direction=0A= row indicates messages transmitted by the CM or=0A= transactions originated by the CM.=0A= The ifIndex is an ifType of = docsCableMaclayer(127)."=0A= INDEX {=0A= ifIndex,=0A= docsQosIfDirection=0A= }=0A= ::=3D { docsQosDynamicServiceStatsTable 1 }=0A= =0A= DocsQosDynamicServiceStatsEntry ::=3D SEQUENCE {=0A= docsQosIfDirection = DocsQosRfMacIfDirection,=0A= docsQosDSAReqs Counter32,=0A= docsQosDSARsps Counter32,=0A= docsQosDSAAcks Counter32,=0A= docsQosDSCReqs Counter32,=0A= docsQosDSCRsps Counter32,=0A= docsQosDSCAcks Counter32,=0A= docsQosDSDReqs Counter32,=0A= docsQosDSDRsps Counter32,=0A= docsQosDynamicAdds Counter32,=0A= docsQosDynamicAddFails Counter32,=0A= docsQosDynamicChanges Counter32,=0A= docsQosDynamicChangeFails Counter32,=0A= docsQosDynamicDeletes Counter32,=0A= docsQosDynamicDeleteFails Counter32,=0A= docsQosDCCReqs Counter32,=0A= =0A= =0A= =0A= Expires September 2003 [Page 52]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= docsQosDCCRsps Counter32,=0A= docsQosDCCAcks Counter32,=0A= docsQosDCCs Counter32,=0A= docsQosDCCFails Counter32=0A= }=0A= =0A= docsQosIfDirection OBJECT-TYPE=0A= SYNTAX DocsQosRfMacIfDirection=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "The direction of interface."=0A= ::=3D { docsQosDynamicServiceStatsEntry 1 }=0A= =0A= docsQosDSAReqs OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Service Addition Requests,=0A= including retries.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 2 }=0A= =0A= docsQosDSARsps OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Service Addition = Responses,=0A= including retries.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 3 }=0A= =0A= docsQosDSAAcks OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Service Addition = Acknowledgements,=0A= including retries.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 4 }=0A= =0A= docsQosDSCReqs OBJECT-TYPE=0A= SYNTAX Counter32=0A= =0A= =0A= =0A= Expires September 2003 [Page 53]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Service Change Requests,=0A= including retries.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 5 }=0A= =0A= docsQosDSCRsps OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Service Change Responses,=0A= including retries.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 6 }=0A= =0A= docsQosDSCAcks OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Service Change = Acknowledgements,=0A= including retries.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 7 }=0A= =0A= docsQosDSDReqs OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Service Delete Requests,=0A= including retries.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 8 }=0A= =0A= docsQosDSDRsps OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Service Delete Responses,=0A= =0A= =0A= =0A= Expires September 2003 [Page 54]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= including retries.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 9 }=0A= =0A= docsQosDynamicAdds OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of successful Dynamic Service = Addition=0A= transactions.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 10 }=0A= =0A= docsQosDynamicAddFails OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of failed Dynamic Service Addition=0A= transactions.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 11 }=0A= =0A= docsQosDynamicChanges OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of successful Dynamic Service Change=0A= transactions.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 12 }=0A= =0A= docsQosDynamicChangeFails OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of failed Dynamic Service Change=0A= transactions.=0A= =0A= This counter's last discontinuity is the=0A= =0A= =0A= =0A= Expires September 2003 [Page 55]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 13 }=0A= =0A= docsQosDynamicDeletes OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of successful Dynamic Service Delete=0A= transactions.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 14 }=0A= =0A= docsQosDynamicDeleteFails OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of failed Dynamic Service Delete=0A= transactions.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 15 }=0A= =0A= =0A= docsQosDCCReqs OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Channel Change Request = messages=0A= traversing an interface. This count is nonzero only = on=0A= downstream direction rows. This count should=0A= include number of retries.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 16 }=0A= =0A= docsQosDCCRsps OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Channel Change Response = messages=0A= traversing an interface. This count is nonzero=0A= only on upstream direction rows. This count = should=0A= include number of retries.=0A= =0A= =0A= =0A= Expires September 2003 [Page 56]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 17 }=0A= =0A= docsQosDCCAcks OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of Dynamic Channel Change = Acknowledgement=0A= messages traversing an interface. This count=0A= is nonzero only on downstream direction rows.=0A= This count should include number of retries.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 18 }=0A= =0A= docsQosDCCs OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of successful Dynamic Channel Change=0A= transactions. This count is nonzero only on = downstream=0A= direction rows.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 19 }=0A= =0A= docsQosDCCFails OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of failed Dynamic Channel Change=0A= transactions. This count is nonzero only on=0A= downstream direction rows.=0A= =0A= This counter's last discontinuity is the=0A= ifCounterDiscontinuityTime for same ifIndex that=0A= indexes this object."=0A= ::=3D { docsQosDynamicServiceStatsEntry 20 }=0A= =0A= =0A= --=0A= -- Service Flow Log Table (CMTS ONLY)=0A= --=0A= docsQosServiceFlowLogTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosServiceFlowLogEntry=0A= =0A= =0A= =0A= Expires September 2003 [Page 57]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table contains a log of the disconnected=0A= Service Flows in a managed device."=0A= ::=3D { docsQosMIBObjects 7 }=0A= =0A= docsQosServiceFlowLogEntry OBJECT-TYPE=0A= SYNTAX DocsQosServiceFlowLogEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "The information regarding a single disconnected=0A= service flow."=0A= INDEX {=0A= docsQosServiceFlowLogIndex=0A= }=0A= ::=3D { docsQosServiceFlowLogTable 1 }=0A= =0A= DocsQosServiceFlowLogEntry ::=3D SEQUENCE {=0A= docsQosServiceFlowLogIndex Unsigned32,=0A= docsQosServiceFlowLogIfIndex InterfaceIndex,=0A= docsQosServiceFlowLogSFID Unsigned32,=0A= docsQosServiceFlowLogCmMac MacAddress,=0A= docsQosServiceFlowLogPkts Counter64,=0A= docsQosServiceFlowLogOctets Counter64,=0A= docsQosServiceFlowLogTimeDeleted TimeStamp,=0A= docsQosServiceFlowLogTimeCreated TimeStamp,=0A= docsQosServiceFlowLogTimeActive Counter32,=0A= docsQosServiceFlowLogDirection = DocsQosRfMacIfDirection,=0A= docsQosServiceFlowLogPrimary TruthValue,=0A= docsQosServiceFlowLogServiceClassName DisplayString,=0A= docsQosServiceFlowLogPolicedDropPkts Counter32,=0A= docsQosServiceFlowLogPolicedDelayPkts Counter32,=0A= docsQosServiceFlowLogControl INTEGER=0A= }=0A= =0A= docsQosServiceFlowLogIndex OBJECT-TYPE=0A= SYNTAX Unsigned32 (1..4294967295)=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Unique index for a logged service flow."=0A= ::=3D { docsQosServiceFlowLogEntry 1 }=0A= =0A= docsQosServiceFlowLogIfIndex OBJECT-TYPE=0A= SYNTAX InterfaceIndex=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The ifIndex of ifType docsCableMaclayer(127)=0A= on the CMTS where the service flow was = present."=0A= ::=3D { docsQosServiceFlowLogEntry 2 }=0A= =0A= docsQosServiceFlowLogSFID OBJECT-TYPE=0A= =0A= =0A= =0A= Expires September 2003 [Page 58]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= SYNTAX Unsigned32 (1..4294967295)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The index assigned to the service flow by the = CMTS."=0A= ::=3D { docsQosServiceFlowLogEntry 3 }=0A= =0A= docsQosServiceFlowLogCmMac OBJECT-TYPE=0A= SYNTAX MacAddress=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The MAC address for the cable modem associated = with=0A= the service flow."=0A= ::=3D { docsQosServiceFlowLogEntry 4 }=0A= =0A= docsQosServiceFlowLogPkts OBJECT-TYPE=0A= SYNTAX Counter64=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of packets counted on this service = flow=0A= after payload header suppression."=0A= ::=3D { docsQosServiceFlowLogEntry 5 }=0A= =0A= docsQosServiceFlowLogOctets OBJECT-TYPE=0A= SYNTAX Counter64=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The number of octets counted on this service = flow=0A= after payload header suppression."=0A= ::=3D { docsQosServiceFlowLogEntry 6 }=0A= =0A= docsQosServiceFlowLogTimeDeleted OBJECT-TYPE=0A= SYNTAX TimeStamp=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The value of sysUpTime when the service flow=0A= was deleted."=0A= ::=3D { docsQosServiceFlowLogEntry 7 }=0A= =0A= docsQosServiceFlowLogTimeCreated OBJECT-TYPE=0A= SYNTAX TimeStamp=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The value of sysUpTime when the service flow=0A= was created."=0A= ::=3D { docsQosServiceFlowLogEntry 8 }=0A= =0A= docsQosServiceFlowLogTimeActive OBJECT-TYPE=0A= SYNTAX Counter32=0A= UNITS "seconds"=0A= MAX-ACCESS read-only=0A= STATUS current=0A= =0A= =0A= =0A= Expires September 2003 [Page 59]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= DESCRIPTION "The total time that service flow was active."=0A= ::=3D { docsQosServiceFlowLogEntry 9 }=0A= =0A= docsQosServiceFlowLogDirection OBJECT-TYPE=0A= SYNTAX DocsQosRfMacIfDirection=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The value of docsQosServiceFlowDirection=0A= for the service flow."=0A= ::=3D { docsQosServiceFlowLogEntry 10 }=0A= =0A= docsQosServiceFlowLogPrimary OBJECT-TYPE=0A= SYNTAX TruthValue=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The value of docsQosServiceFlowPrimary for the=0A= service flow."=0A= ::=3D { docsQosServiceFlowLogEntry 11 }=0A= =0A= docsQosServiceFlowLogServiceClassName OBJECT-TYPE=0A= SYNTAX DisplayString=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The value of docsQosParamSetServiceClassName for=0A= the provisioned QOS Parameter Set of the=0A= service flow."=0A= ::=3D { docsQosServiceFlowLogEntry 12 }=0A= =0A= docsQosServiceFlowLogPolicedDropPkts OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The final value of = docsQosServiceFlowPolicedDropPkts=0A= for the service flow."=0A= ::=3D { docsQosServiceFlowLogEntry 13 }=0A= =0A= docsQosServiceFlowLogPolicedDelayPkts OBJECT-TYPE=0A= SYNTAX Counter32=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The final value of = docsQosServiceFlowPolicedDelayPkts=0A= for the service flow."=0A= ::=3D { docsQosServiceFlowLogEntry 14 }=0A= =0A= docsQosServiceFlowLogControl OBJECT-TYPE=0A= SYNTAX INTEGER {=0A= active(1),=0A= destroy(6)=0A= }=0A= =0A= MAX-ACCESS read-write=0A= =0A= =0A= =0A= Expires September 2003 [Page 60]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= STATUS current=0A= DESCRIPTION "Setting this object to the value destroy(6) = removes=0A= this entry from the table.=0A= Reading this object return the value active(1)."=0A= ::=3D { docsQosServiceFlowLogEntry 15 }=0A= =0A= --=0A= -- Service Class Table (CMTS ONLY)=0A= --=0A= docsQosServiceClassTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosServiceClassEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table describes the set of Docsis-QOS=0A= Service Classes in a CMTS. "=0A= ::=3D { docsQosMIBObjects 8 }=0A= =0A= docsQosServiceClassEntry OBJECT-TYPE=0A= SYNTAX DocsQosServiceClassEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "A provisioned service class on a CMTS.=0A= Each entry defines a template for certain=0A= DOCSIS QOS Parameter Set values. When a CM=0A= creates or modifies an Admitted QOS Parameter Set for = a=0A= Service Flow, it may reference a Service Class=0A= Name instead of providing explicit QOS Parameter=0A= Set values. In this case, the CMTS populates=0A= the QOS Parameter Set with the applicable=0A= corresponding values from the named Service Class.=0A= Subsequent changes to a Service Class row do *not*=0A= affect the QOS Parameter Set values of any service = flows=0A= already admitted.=0A= =0A= A service class template applies to only=0A= a single direction, as indicated in the=0A= docsQosServiceClassDirection object.=0A= "=0A= INDEX {=0A= docsQosServiceClassName=0A= }=0A= ::=3D { docsQosServiceClassTable 1 }=0A= =0A= DocsQosServiceClassEntry ::=3D SEQUENCE {=0A= docsQosServiceClassName DisplayString,=0A= docsQosServiceClassStatus RowStatus,=0A= docsQosServiceClassPriority Integer32,=0A= docsQosServiceClassMaxTrafficRate DocsQosBitRate,=0A= docsQosServiceClassMaxTrafficBurst Unsigned32,=0A= docsQosServiceClassMinReservedRate DocsQosBitRate,=0A= docsQosServiceClassMinReservedPkt Integer32,=0A= =0A= =0A= =0A= Expires September 2003 [Page 61]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= docsQosServiceClassMaxConcatBurst Integer32,=0A= docsQosServiceClassNomPollInterval Unsigned32,=0A= docsQosServiceClassTolPollJitter Unsigned32,=0A= docsQosServiceClassUnsolicitGrantSize Integer32,=0A= docsQosServiceClassNomGrantInterval Unsigned32,=0A= docsQosServiceClassTolGrantJitter Unsigned32,=0A= docsQosServiceClassGrantsPerInterval Integer32,=0A= docsQosServiceClassMaxLatency Unsigned32,=0A= docsQosServiceClassActiveTimeout Integer32,=0A= docsQosServiceClassAdmittedTimeout Integer32,=0A= docsQosServiceClassSchedulingType DocsQosSchedulingType,=0A= docsQosServiceClassRequestPolicy OCTET STRING,=0A= docsQosServiceClassTosAndMask OCTET STRING,=0A= docsQosServiceClassTosOrMask OCTET STRING,=0A= docsQosServiceClassDirection DocsQosRfMacIfDirection,=0A= docsQosServiceClassStorageType StorageType=0A= }=0A= =0A= docsQosServiceClassName OBJECT-TYPE=0A= SYNTAX DisplayString (SIZE(2..15))=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Service Class Name. DOCSIS specifies that the=0A= maximum size is 16 ASCII characters including=0A= a terminating zero. The terminating zero is not=0A= represented in this DisplayString syntax object.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.3.4"=0A= ::=3D { docsQosServiceClassEntry 1 }=0A= =0A= docsQosServiceClassStatus OBJECT-TYPE=0A= SYNTAX RowStatus=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Used to create or delete rows in this table.=0A= There is no restriction on the ability=0A= to change values in this row while the row is = active.=0A= Inactive rows need not be timed out."=0A= ::=3D { docsQosServiceClassEntry 2 }=0A= =0A= docsQosServiceClassPriority OBJECT-TYPE=0A= SYNTAX Integer32 (0..7)=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetPriority."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 3 }=0A= =0A= docsQosServiceClassMaxTrafficRate OBJECT-TYPE=0A= SYNTAX DocsQosBitRate=0A= MAX-ACCESS read-create=0A= =0A= =0A= =0A= Expires September 2003 [Page 62]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetMaxTrafficRate."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 4 }=0A= =0A= docsQosServiceClassMaxTrafficBurst OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetMaxTrafficBurst."=0A= DEFVAL { 3044 }=0A= ::=3D { docsQosServiceClassEntry 5 }=0A= =0A= docsQosServiceClassMinReservedRate OBJECT-TYPE=0A= SYNTAX DocsQosBitRate=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSEtMinReservedRate."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 6 }=0A= =0A= docsQosServiceClassMinReservedPkt OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetMinReservedPkt."=0A= ::=3D { docsQosServiceClassEntry 7 }=0A= =0A= docsQosServiceClassMaxConcatBurst OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetMaxConcatBurst."=0A= DEFVAL { 1522 }=0A= ::=3D { docsQosServiceClassEntry 8 }=0A= =0A= docsQosServiceClassNomPollInterval OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetNomPollInterval."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 9 }=0A= =0A= docsQosServiceClassTolPollJitter OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetTolPollJitter."=0A= =0A= =0A= =0A= Expires September 2003 [Page 63]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 10 }=0A= =0A= docsQosServiceClassUnsolicitGrantSize OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetUnsolicitGrantSize."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 11 }=0A= =0A= docsQosServiceClassNomGrantInterval OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetNomGrantInterval."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 12 }=0A= =0A= docsQosServiceClassTolGrantJitter OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetTolGrantJitter."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 13 }=0A= =0A= docsQosServiceClassGrantsPerInterval OBJECT-TYPE=0A= SYNTAX Integer32 (0..127)=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetGrantsPerInterval."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 14 }=0A= =0A= docsQosServiceClassMaxLatency OBJECT-TYPE=0A= SYNTAX Unsigned32=0A= UNITS "microseconds"=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetClassMaxLatency."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.7.1"=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 15 }=0A= =0A= docsQosServiceClassActiveTimeout OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= UNITS "seconds"=0A= MAX-ACCESS read-create=0A= =0A= =0A= =0A= Expires September 2003 [Page 64]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetActiveTimeout."=0A= DEFVAL { 0 }=0A= ::=3D { docsQosServiceClassEntry 16 }=0A= =0A= docsQosServiceClassAdmittedTimeout OBJECT-TYPE=0A= SYNTAX Integer32 (0..65535)=0A= UNITS "seconds"=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetAdmittedTimeout."=0A= DEFVAL { 200 }=0A= ::=3D { docsQosServiceClassEntry 17 }=0A= =0A= docsQosServiceClassSchedulingType OBJECT-TYPE=0A= SYNTAX DocsQosSchedulingType=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetSchedulingType."=0A= DEFVAL { bestEffort }=0A= ::=3D { docsQosServiceClassEntry 18 }=0A= =0A= docsQosServiceClassRequestPolicy OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(4))=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetRequestPolicyOct."=0A= DEFVAL { '00000000'H } -- no bits are set=0A= ::=3D { docsQosServiceClassEntry 19 }=0A= =0A= docsQosServiceClassTosAndMask OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(1))=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetTosAndMask."=0A= DEFVAL { 'FF'H }=0A= ::=3D { docsQosServiceClassEntry 20 }=0A= =0A= docsQosServiceClassTosOrMask OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(1))=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Template for docsQosParamSetTosOrMask."=0A= DEFVAL { '00'H }=0A= ::=3D { docsQosServiceClassEntry 21 }=0A= =0A= docsQosServiceClassDirection OBJECT-TYPE=0A= SYNTAX DocsQosRfMacIfDirection=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Specifies whether the service class template=0A= =0A= =0A= =0A= Expires September 2003 [Page 65]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= applies to upstream or downstream service = flows."=0A= DEFVAL { upstream }=0A= ::=3D { docsQosServiceClassEntry 22 }=0A= =0A= docsQosServiceClassStorageType OBJECT-TYPE=0A= SYNTAX StorageType=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "This object defines whether this row is kept in=0A= volatile storage and lost upon reboot or if this=0A= row is backed up by non-volatile or permanent=0A= storage. 'permanent' entries need not allow=0A= writable access to any object."=0A= DEFVAL { nonVolatile }=0A= ::=3D { docsQosServiceClassEntry 23 }=0A= =0A= --=0A= -- Service Class PolicyTable=0A= --=0A= docsQosServiceClassPolicyTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosServiceClassPolicyEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table describes the set of Docsis-QOS=0A= Service Class Policies.=0A= =0A= This table is an adjunct to the=0A= docsDevFilterPolicy table. Entries in=0A= docsDevFilterPolicy table can point to=0A= specific rows in this table.=0A= =0A= This table permits mapping a packet to a service=0A= class name of an active service flow so long as=0A= a classifier does not exist at a higher=0A= priority.=0A= "=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix E.2.1"=0A= ::=3D { docsQosMIBObjects 9 }=0A= =0A= docsQosServiceClassPolicyEntry OBJECT-TYPE=0A= SYNTAX DocsQosServiceClassPolicyEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "A service class name policy entry."=0A= INDEX {=0A= docsQosServiceClassPolicyIndex=0A= }=0A= ::=3D { docsQosServiceClassPolicyTable 1 }=0A= =0A= DocsQosServiceClassPolicyEntry ::=3D SEQUENCE {=0A= docsQosServiceClassPolicyIndex Unsigned32,=0A= =0A= =0A= =0A= Expires September 2003 [Page 66]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= docsQosServiceClassPolicyName DisplayString,=0A= docsQosServiceClassPolicyRulePriority Integer32,=0A= docsQosServiceClassPolicyStatus RowStatus,=0A= docsQosServiceClassPolicyStorageType StorageType=0A= }=0A= =0A= docsQosServiceClassPolicyIndex OBJECT-TYPE=0A= SYNTAX Unsigned32 (1..2147483647)=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "Index value to uniquely identify an entry in=0A= this table."=0A= ::=3D { docsQosServiceClassPolicyEntry 1 }=0A= =0A= docsQosServiceClassPolicyName OBJECT-TYPE=0A= SYNTAX DisplayString=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Service Class Name to identify the name of the=0A= service class flow to which the packet should be=0A= directed."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix E.2.1"=0A= ::=3D { docsQosServiceClassPolicyEntry 2 }=0A= =0A= docsQosServiceClassPolicyRulePriority OBJECT-TYPE=0A= SYNTAX Integer32 (0..255)=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Service Class Policy rule priority for the=0A= entry."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.3.5"=0A= ::=3D { docsQosServiceClassPolicyEntry 3 }=0A= =0A= docsQosServiceClassPolicyStatus OBJECT-TYPE=0A= SYNTAX RowStatus=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "Used to create or delete rows in this table.=0A= This object should not be deleted if it is=0A= reference by an entry in docsDevFilterPolicy.=0A= The reference should be deleted first.=0A= There is no restriction on the ability=0A= to change values in this row while the row is = active.=0A= Inactive rows need not be timed out."=0A= ::=3D { docsQosServiceClassPolicyEntry 4 }=0A= =0A= docsQosServiceClassPolicyStorageType OBJECT-TYPE=0A= SYNTAX StorageType=0A= MAX-ACCESS read-create=0A= STATUS current=0A= DESCRIPTION "This object defines whether this row is kept in=0A= =0A= =0A= =0A= Expires September 2003 [Page 67]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= volatile storage and lost upon reboot or if this=0A= row is backed up by non-volatile or permanent=0A= storage. 'permanent' entries need not allow=0A= writable access to any object."=0A= DEFVAL { nonVolatile }=0A= ::=3D { docsQosServiceClassPolicyEntry 5 }=0A= =0A= --=0A= -- Payload Header Suppression(PHS) Table=0A= --=0A= docsQosPHSTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosPHSEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table describes set of payload header=0A= suppression entries."=0A= ::=3D { docsQosMIBObjects 10 }=0A= =0A= docsQosPHSEntry OBJECT-TYPE=0A= SYNTAX DocsQosPHSEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "A payload header suppression entry.=0A= The ifIndex is an ifType of = docsCableMaclayer(127).=0A= The index docsQosServiceFlowId selects one=0A= service flow from the cable MAC layer = interface.=0A= The docsQosPktClassId index matches an=0A= index of the docsQosPktClassTable.=0A= "=0A= INDEX {=0A= ifIndex,=0A= docsQosServiceFlowId,=0A= docsQosPktClassId=0A= }=0A= ::=3D { docsQosPHSTable 1 }=0A= =0A= DocsQosPHSEntry ::=3D SEQUENCE {=0A= docsQosPHSField OCTET STRING,=0A= docsQosPHSMask OCTET STRING,=0A= docsQosPHSSize Integer32,=0A= docsQosPHSVerify TruthValue,=0A= docsQosPHSIndex Integer32=0A= }=0A= =0A= -- docsQosPHSIndex { docsQosPHSEntry 1 } was=0A= -- moved to docsQosPHSIndex { docsQosPHSEntry 7 }=0A= -- in an ealier revisions of the mib.=0A= =0A= docsQosPHSField OBJECT-TYPE=0A= SYNTAX OCTET STRING (SIZE(0..255))=0A= MAX-ACCESS read-only=0A= =0A= =0A= =0A= Expires September 2003 [Page 68]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= STATUS current=0A= DESCRIPTION "Payload header suppression field defines the=0A= bytes of the header which must be=0A= suppressed/restored by the sending/receiving=0A= device.=0A= =0A= The number of octets in this object should be=0A= the same as the value of docsQosPHSSize."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.10.1"=0A= ::=3D { docsQosPHSEntry 2 }=0A= =0A= docsQosPHSMask OBJECT-TYPE=0A= SYNTAX OCTET STRING(SIZE(0..32))=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Payload header suppression mask defines the=0A= bit mask which used in combination with the=0A= docsQosPHSField defines which bytes in header=0A= must be suppressed/restored by the sending or=0A= receiving device.=0A= =0A= Each bit of this bit mask corresponds to a byte=0A= in the docsQosPHSField, with the least=0A= significant bit corresponding to first byte of=0A= the docsQosPHSField.=0A= =0A= Each bit of the bit mask specifies whether of=0A= not the corresponding byte should be suppressed=0A= in the packet. A bit value of '1' indicates that=0A= the byte should be suppressed by the sending=0A= device and restored by the receiving device.=0A= A bit value of '0' indicates that=0A= the byte should not be suppressed by the sending=0A= device or restored by the receiving device.=0A= =0A= If the bit mask does not contain a bit for each=0A= byte in the docsQosPHSField then the bit mask is=0A= extended with bit values of '1' to be the=0A= necessary length."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.10.3"=0A= ::=3D { docsQosPHSEntry 3 }=0A= =0A= docsQosPHSSize OBJECT-TYPE=0A= SYNTAX Integer32 (0..255)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Payload header suppression size specifies the=0A= number of bytes in the header to be suppressed=0A= and restored.=0A= =0A= The value of this object must match the number=0A= =0A= =0A= =0A= Expires September 2003 [Page 69]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= of bytes in the docsQosPHSField."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.10.4"=0A= ::=3D { docsQosPHSEntry 4 }=0A= =0A= docsQosPHSVerify OBJECT-TYPE=0A= SYNTAX TruthValue=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Payload header suppression verification value of=0A= 'true' the sender must verify docsQosPHSField=0A= is the same as what is contained in the packet=0A= to be suppressed."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.10.5"=0A= ::=3D { docsQosPHSEntry 5 }=0A= =0A= docsQosPHSIndex OBJECT-TYPE=0A= SYNTAX Integer32 (1..255)=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "Payload header suppression index uniquely=0A= references the PHS rule for a given service = flow."=0A= REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.10.2"=0A= ::=3D { docsQosPHSEntry 6 }=0A= =0A= =0A= --=0A= -- docsQosCmtsMacToSrvFlowTable (CMTS Only)=0A= --=0A= docsQosCmtsMacToSrvFlowTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF DocsQosCmtsMacToSrvFlowEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "This table provide for referencing the service = flows=0A= associated with a particular cable modem. This = allows=0A= for indexing into other docsQos tables that are=0A= indexed by docsQosServiceFlowId and ifIndex."=0A= ::=3D { docsQosMIBObjects 11 }=0A= =0A= docsQosCmtsMacToSrvFlowEntry OBJECT-TYPE=0A= SYNTAX DocsQosCmtsMacToSrvFlowEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "An entry is created by CMTS for each service = flow=0A= connected to this CMTS."=0A= INDEX {=0A= docsQosCmtsCmMac,=0A= docsQosCmtsServiceFlowId=0A= }=0A= ::=3D { docsQosCmtsMacToSrvFlowTable 1 }=0A= =0A= DocsQosCmtsMacToSrvFlowEntry ::=3D SEQUENCE {=0A= =0A= =0A= =0A= Expires September 2003 [Page 70]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= docsQosCmtsCmMac MacAddress,=0A= docsQosCmtsServiceFlowId Unsigned32,=0A= docsQosCmtsIfIndex InterfaceIndex=0A= }=0A= =0A= docsQosCmtsCmMac OBJECT-TYPE=0A= SYNTAX MacAddress=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "The MAC address for the referenced CM."=0A= ::=3D { docsQosCmtsMacToSrvFlowEntry 1 }=0A= =0A= docsQosCmtsServiceFlowId OBJECT-TYPE=0A= SYNTAX Unsigned32 (1..4294967295)=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION "An index assigned to a service flow by CMTS."=0A= ::=3D { docsQosCmtsMacToSrvFlowEntry 2 }=0A= =0A= docsQosCmtsIfIndex OBJECT-TYPE=0A= SYNTAX InterfaceIndex=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION "The ifIndex of ifType docsCableMacLayter(127)=0A= on the CMTS that is connected to the Cable = Modem."=0A= ::=3D { docsQosCmtsMacToSrvFlowEntry 3 }=0A= =0A= =0A= --=0A= -- Placeholder for notifications/traps.=0A= --=0A= docsQosNotification OBJECT IDENTIFIER ::=3D { docsQosMIB 2 }=0A= =0A= =0A= --=0A= -- Conformance definitions=0A= --=0A= docsQosConformance OBJECT IDENTIFIER ::=3D { docsQosMIB 3 }=0A= docsQosGroups OBJECT IDENTIFIER ::=3D { docsQosConformance 1 = }=0A= docsQosCompliances OBJECT IDENTIFIER ::=3D { docsQosConformance 2 = }=0A= =0A= docsQosCompliance MODULE-COMPLIANCE=0A= STATUS current=0A= DESCRIPTION=0A= "The compliance statement for MCNS Cable Modems and=0A= Cable Modem Termination Systems that implement DOCSIS=0A= Service Flows."=0A= =0A= MODULE -- docsQosMIB=0A= MANDATORY-GROUPS { docsQosBaseGroup }=0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 71]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= GROUP docsQosCmtsGroup=0A= DESCRIPTION=0A= "This group is mandatory for only Cable Modem = Termination=0A= Systems (CMTS) and not implemented for Cable Modems."=0A= =0A= GROUP docsQosParamSetGroup=0A= DESCRIPTION=0A= "This group is mandatory for Cable Modem Termination=0A= Systems (CMTS) and Cable Modems. Cable modems only = implement=0A= objects in this group as read-only."=0A= =0A= GROUP docsQosSrvClassPolicyGroup=0A= DESCRIPTION=0A= "This group is optional for Cable Modem Termination=0A= Systems (CMTS) and Cable Modems. This group only needs = to=0A= be implement if policy based service flow = classification=0A= is implemented. See docsDevPolicyTable in=0A= DOCS-CABLE-DEVICE-MIB for more details. "=0A= =0A= GROUP docsQosServiceClassGroup=0A= DESCRIPTION=0A= "The docsQosServiceClassTable group of objects."=0A= =0A= OBJECT docsQosPktClassPkts=0A= DESCRIPTION=0A= "This object only needs to be implemented in entries=0A= that are classifying packets and not policing packets."=0A= =0A= OBJECT docsQosPktClassInetAddressType=0A= SYNTAX InetAddressType { ipv4(1) }=0A= DESCRIPTION=0A= "An implementation is only required to support IPv4=0A= address."=0A= =0A= OBJECT docsQosPktClassInetSourceAddr=0A= SYNTAX InetAddress (SIZE(4))=0A= DESCRIPTION=0A= "An implementation is only required to support IPv4=0A= address."=0A= =0A= OBJECT docsQosPktClassInetSourceMask=0A= SYNTAX InetAddress (SIZE(4))=0A= DESCRIPTION=0A= "An implementation is only required to support IPv4=0A= address."=0A= =0A= OBJECT docsQosPktClassInetDestAddr=0A= SYNTAX InetAddress (SIZE(4))=0A= DESCRIPTION=0A= "An implementation is only required to support IPv4=0A= address."=0A= =0A= =0A= =0A= Expires September 2003 [Page 72]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= =0A= OBJECT docsQosPktClassInetDestMask=0A= SYNTAX InetAddress (SIZE(4))=0A= DESCRIPTION=0A= "An implementation is only required to support IPv4=0A= address."=0A= =0A= OBJECT docsQosServiceClassStorageType=0A= SYNTAX StorageType { nonVolatile(3) }=0A= DESCRIPTION=0A= "An implementation is only required to support = nonvolatile=0A= storage."=0A= =0A= OBJECT docsQosServiceClassPolicyStorageType=0A= SYNTAX StorageType { nonVolatile(3) }=0A= DESCRIPTION=0A= "An implementation is only required to support = nonvolatile=0A= storage."=0A= =0A= ::=3D { docsQosCompliances 1 }=0A= =0A= docsQosBaseGroup OBJECT-GROUP=0A= OBJECTS {=0A= docsQosPktClassDirection,=0A= docsQosPktClassPriority,=0A= docsQosPktClassIpTosLow,=0A= docsQosPktClassIpTosHigh,=0A= docsQosPktClassIpTosMask,=0A= docsQosPktClassIpProtocol,=0A= docsQosPktClassSourcePortStart,=0A= docsQosPktClassSourcePortEnd,=0A= docsQosPktClassDestPortStart,=0A= docsQosPktClassDestPortEnd,=0A= docsQosPktClassDestMacAddr,=0A= docsQosPktClassDestMacMask,=0A= docsQosPktClassSourceMacAddr,=0A= docsQosPktClassEnetProtocolType,=0A= docsQosPktClassEnetProtocol,=0A= docsQosPktClassUserPriLow,=0A= docsQosPktClassUserPriHigh,=0A= docsQosPktClassVlanId,=0A= docsQosPktClassStateActive,=0A= docsQosPktClassPkts,=0A= docsQosPktClassBitMap,=0A= docsQosPktClassInetAddressType,=0A= docsQosPktClassInetSourceAddr,=0A= docsQosPktClassInetSourceMask,=0A= docsQosPktClassInetDestAddr,=0A= docsQosPktClassInetDestMask,=0A= =0A= docsQosServiceFlowSID,=0A= =0A= =0A= =0A= Expires September 2003 [Page 73]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= docsQosServiceFlowDirection,=0A= docsQosServiceFlowPrimary,=0A= =0A= docsQosServiceFlowPkts, -- not sure if CM should implement=0A= docsQosServiceFlowOctets,=0A= docsQosServiceFlowTimeCreated,=0A= docsQosServiceFlowTimeActive,=0A= docsQosServiceFlowPHSUnknowns,=0A= docsQosServiceFlowPolicedDropPkts,=0A= docsQosServiceFlowPolicedDelayPkts,=0A= =0A= docsQosDSAReqs,=0A= docsQosDSARsps,=0A= docsQosDSAAcks,=0A= docsQosDSCReqs,=0A= docsQosDSCRsps,=0A= docsQosDSCAcks,=0A= docsQosDSDReqs,=0A= docsQosDSDRsps,=0A= docsQosDynamicAdds,=0A= docsQosDynamicAddFails,=0A= docsQosDynamicChanges,=0A= docsQosDynamicChangeFails,=0A= docsQosDynamicDeletes,=0A= docsQosDynamicDeleteFails,=0A= docsQosDCCReqs,=0A= docsQosDCCRsps,=0A= docsQosDCCAcks,=0A= docsQosDCCs,=0A= docsQosDCCFails,=0A= =0A= docsQosPHSField,=0A= docsQosPHSMask,=0A= docsQosPHSSize,=0A= docsQosPHSVerify,=0A= docsQosPHSIndex=0A= }=0A= STATUS current=0A= DESCRIPTION=0A= "Group of objects implemented in both Cable Modems and=0A= Cable Modem Termination Systems."=0A= ::=3D { docsQosGroups 1 }=0A= =0A= docsQosParamSetGroup OBJECT-GROUP=0A= OBJECTS {=0A= docsQosParamSetServiceClassName,=0A= docsQosParamSetPriority,=0A= docsQosParamSetMaxTrafficRate,=0A= docsQosParamSetMaxTrafficBurst,=0A= docsQosParamSetMinReservedRate,=0A= docsQosParamSetMinReservedPkt,=0A= =0A= =0A= =0A= Expires September 2003 [Page 74]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= docsQosParamSetActiveTimeout,=0A= docsQosParamSetAdmittedTimeout,=0A= docsQosParamSetMaxConcatBurst,=0A= docsQosParamSetSchedulingType,=0A= docsQosParamSetNomPollInterval,=0A= docsQosParamSetTolPollJitter,=0A= docsQosParamSetUnsolicitGrantSize,=0A= docsQosParamSetNomGrantInterval,=0A= docsQosParamSetTolGrantJitter,=0A= docsQosParamSetGrantsPerInterval,=0A= docsQosParamSetTosAndMask,=0A= docsQosParamSetTosOrMask,=0A= docsQosParamSetMaxLatency,=0A= docsQosParamSetRequestPolicyOct,=0A= docsQosParamSetBitMap=0A= }=0A= STATUS current=0A= DESCRIPTION=0A= "Group of objects implemenented in both Cable Modems and=0A= Cable Modem Termination Systems for QOS parameter sets."=0A= ::=3D { docsQosGroups 2 }=0A= =0A= =0A= docsQosCmtsGroup OBJECT-GROUP=0A= OBJECTS {=0A= =0A= docsQosUpstreamFragments,=0A= docsQosUpstreamFragDiscards,=0A= docsQosUpstreamConcatBursts,=0A= =0A= docsQosServiceFlowLogIfIndex,=0A= docsQosServiceFlowLogSFID,=0A= docsQosServiceFlowLogCmMac,=0A= docsQosServiceFlowLogPkts,=0A= docsQosServiceFlowLogOctets,=0A= docsQosServiceFlowLogTimeDeleted,=0A= docsQosServiceFlowLogTimeCreated,=0A= docsQosServiceFlowLogTimeActive,=0A= docsQosServiceFlowLogDirection,=0A= docsQosServiceFlowLogPrimary,=0A= docsQosServiceFlowLogServiceClassName,=0A= docsQosServiceFlowLogPolicedDropPkts,=0A= docsQosServiceFlowLogPolicedDelayPkts,=0A= docsQosServiceFlowLogControl,=0A= =0A= docsQosCmtsIfIndex -- docsQosCmtsMacToSrvFlowTable = required=0A= =0A= }=0A= STATUS current=0A= DESCRIPTION=0A= "Mandatory group of objects implemented only in the CMTS."=0A= =0A= =0A= =0A= Expires September 2003 [Page 75]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= ::=3D { docsQosGroups 3 }=0A= =0A= docsQosSrvClassPolicyGroup OBJECT-GROUP=0A= OBJECTS {=0A= docsQosServiceClassPolicyName,=0A= docsQosServiceClassPolicyRulePriority,=0A= docsQosServiceClassPolicyStatus,=0A= docsQosServiceClassPolicyStorageType=0A= }=0A= STATUS current=0A= DESCRIPTION=0A= "Group of objects implemented in both Cable Modems and=0A= Cable Modem Termination Systems when supporting policy = based=0A= service flows."=0A= ::=3D { docsQosGroups 4 }=0A= =0A= docsQosServiceClassGroup OBJECT-GROUP=0A= OBJECTS {=0A= docsQosServiceClassStatus,=0A= docsQosServiceClassPriority,=0A= docsQosServiceClassMaxTrafficRate,=0A= docsQosServiceClassMaxTrafficBurst,=0A= docsQosServiceClassMinReservedRate,=0A= docsQosServiceClassMinReservedPkt,=0A= docsQosServiceClassMaxConcatBurst,=0A= docsQosServiceClassNomPollInterval,=0A= docsQosServiceClassTolPollJitter,=0A= docsQosServiceClassUnsolicitGrantSize,=0A= docsQosServiceClassNomGrantInterval,=0A= docsQosServiceClassTolGrantJitter,=0A= docsQosServiceClassGrantsPerInterval,=0A= docsQosServiceClassMaxLatency,=0A= docsQosServiceClassActiveTimeout,=0A= docsQosServiceClassAdmittedTimeout,=0A= docsQosServiceClassSchedulingType,=0A= docsQosServiceClassRequestPolicy,=0A= docsQosServiceClassTosAndMask,=0A= docsQosServiceClassTosOrMask,=0A= docsQosServiceClassDirection,=0A= docsQosServiceClassStorageType=0A= }=0A= STATUS current=0A= DESCRIPTION=0A= "The docsQosServiceClassTable objects. If a CMTS implements=0A= expansion of Service Class Names in a QOS Parameter Set,=0A= this group is mandatory on the CMTS. If the CMTS does not=0A= support Service Class Names, this group may be = unimplemented=0A= in the CMTS. This group is not implemented on the CM.=0A= "=0A= ::=3D { docsQosGroups 5 }=0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 76]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= END=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 77]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= 5. Security Considerations=0A= =0A= =0A= This MIB relates to a agent which will provide metropolitan = public=0A= internet access. As such, improper manipulation of the objects=0A= represented by this MIB may result in denial of service to a = large=0A= number of end-users [9]. Manipulation of the=0A= docsQosServiceClassTable and docsQosServiceClassPolicyTable may = allow=0A= an end-user to increase their service levels, or affect other = end-=0A= users in either a positive or negative manner. In addition,=0A= manipulation of docsQosServiceFlowLogControl could allow an = attacker=0A= to remove logs of packet and byte counts forwarded on a service = flow.=0A= If such logs were used for billing, the attacker would obtain = free=0A= service.=0A= =0A= There are a number of management objects defined in this MIB = module=0A= with a MAX-ACCESS clause of read-write and/or read-create. Such=0A= objects may be considered sensitive or vulnerable in some network=0A= environments. The support for SET operations in a non-secure=0A= environment without proper protection can have a negative effect = on=0A= network operations. These are the tables and objects and their=0A= sensitivity/vulnerability:=0A= =0A= o The docsQosServiceClassTable provides a template of QOS=0A= parameters such as maximum rate limits for a named service=0A= class. Changing these parameters would allow an attacker = to=0A= obtain unauthorized class of service.=0A= =0A= o The docsQosServiceClassPolicyTable applies CMTS vendor=0A= proprietary policies for packet forwarding, including=0A= dropping, scheduling, notification, or other policies.=0A= Changing this table could allow an attacker to deny = service=0A= to all subscribers of the CMTS or grant the attacker=0A= unauthorized forwarding policies.=0A= =0A= o The docsQosServiceFlowLogControl object controls the = deletion=0A= of entries in the docsQosServiceFlowLogTable, which acts as = a=0A= historical "detail record" of DOCSIS service flow packets = and=0A= bytes transmitted. Such records may be used for billing=0A= purposes, so the unauthorized deletion of the records can=0A= result in free service.=0A= =0A= Some of the readable objects in this MIB module (i.e., objects with = a=0A= MAX-ACCESS other than not-accessible) may be considered sensitive = or=0A= vulnerable in some network environments. It is thus important to=0A= control even GET access to these objects and possibly to even = encrypt=0A= the values of these objects when sending them over the network = via=0A= SNMP. These are the tables and objects and their=0A= sensitivity/vulnerability:=0A= =0A= o Unauthorized SNMP GET access of the docsQosPktClassTable = or=0A= =0A= =0A= =0A= Expires September 2003 [Page 78]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= docsQosPHSTable can allow an attacker to learn IP = addresses=0A= permitted to have enhanced quality of service, for = possible=0A= spoofing. This table typically contains the IP addresses=0A= involved in voice-over-IP sessions, for example.=0A= =0A= o Unauthorized SNMP GET access of the docsQosParamSetTable=0A= allows an attacker to learn the names of service classes=0A= which are permitted to have enhanced QOS service, and the=0A= values of that enhanced service. That name can be = referenced=0A= in an unauthorized DOCSIS cable modem configuration file = to=0A= obtain enhanced service.=0A= =0A= o Unauthorized SNMP GET access of the = docsQosServiceFlowTable=0A= can tell an attacker when service flows are active, e.g.=0A= when a voice-over-IP call is in progress.=0A= =0A= o Unauthorized SNMP GET access of the=0A= docsQosServiceFlowStatsTable, docsQosUpstreamStatsTable,=0A= docsQosDynamicServiceStatsTable, = docsQosServiceFlogLogTable,=0A= and docsQosCmtsMacToSrvFlowTable can tell an attacker the=0A= volume of traffic to and from any service flow in the = system,=0A= resulting in loss of privacy of the amount and direction = of=0A= data transfer.=0A= =0A= SNMP versions prior to SNMPv3 did not include adequate security.=0A= Even if the network itself is secure (for example by using = IPSec),=0A= even then, there is no control as to who on the secure network is=0A= allowed to access and GET/SET (read/change/create/delete) the = objects=0A= in this MIB module. It is RECOMMENDED that implementers consider = the=0A= security features as provided by the SNMPv3 framework (see [12],=0A= section 8), including full support for the SNMPv3 cryptographic=0A= mechanisms (for authentication and privacy). Further, deployment = of=0A= SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is=0A= RECOMMENDED to deploy SNMPv3 and to enable cryptographic = security.=0A= It is then a customer/operator responsibility to ensure that the = SNMP=0A= entity giving access to an instance of this MIB module, is = properly=0A= configured to give access to the objects only to those principals=0A= (users) that have legitimate rights to indeed GET or SET=0A= (change/create/delete) them.=0A= =0A= =0A= =0A= 6. Intellectual Property=0A= =0A= The IETF takes no position regarding the validity or scope of any=0A= intellectual property or other rights that might be claimed to=0A= pertain to the implementation or use of the technology described = in=0A= this document or the extent to which any license under such = rights=0A= might or might not be available; neither does it represent that = it=0A= has made any effort to identify any such rights. Information on = the=0A= IETF's procedures with respect to rights in standards-track and=0A= =0A= =0A= =0A= Expires September 2003 [Page 79]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= standards-related documentation can be found in BCP-11. Copies = of=0A= claims of rights made available for publication and any assurances = of=0A= licenses to be made available, or the result of an attempt made = to=0A= obtain a general license or permission for the use of such=0A= proprietary rights by implementers or users of this specification = can=0A= be obtained from the IETF Secretariat.=0A= =0A= The IETF invites any interested party to bring to its attention = any=0A= copyrights, patents or patent applications, or other proprietary=0A= rights which may cover technology that may be required to = practice=0A= this standard. Please address the information to the IETF = Executive=0A= Director.=0A= =0A= =0A= =0A= 7. Acknowledgement=0A= =0A= Funding for the RFC Editor function is currently provided by the=0A= Internet Society.=0A= =0A= =0A= =0A= 8. Normative References=0A= =0A= [1] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Structure = of=0A= Management Information for Version 2 (SMIv2)", STD 58,=0A= RFC 2578, April 1999.=0A= =0A= [2] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Textual=0A= Conventions for SMIv2", STD 58, RFC 2579, April 1999.=0A= =0A= [3] McCloghrie, K., Perkins, D. and J. Schoenwaelder, = "Conformance=0A= Statements for SMIv2", STD 58, RFC 2580, April 1999.=0A= =0A= [4] "Data-Over-Cable Service Interface Specifications:=0A= Radio Frequency Interface Specification = SP-RFIv1.1-I09-020830",=0A= DOCSIS, August 2002, http://www.cablemodem.com/.=0A= =0A= [5] L. Steinberg, "Techniques for Managing Asynchronously = Generated=0A= Alerts", RFC 1224, May 1991.=0A= =0A= [6] "Data-Over-Cable Service Interface Specifications: Operations=0A= Support System Interface Specification = SP-OSSIv1.1-I06-020830",=0A= DOCSIS, August 2002, http://www.cablemodem.com/.=0A= =0A= [7] Bradner, S., "Key words for use in RFCs to Indicate = Requirement=0A= Levels", RFC2119, March 1997.=0A= =0A= [8] "Data-Over-Cable Service Interface Specifications: Baseline=0A= Privacy Plus Interface Specification SP-BPI+-I07-020830",=0A= DOCSIS, August 2002, http://www.cablemodem.com/.=0A= =0A= =0A= =0A= Expires September 2003 [Page 80]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= [9] St. Johns, M., "Cable Device Management Information Base for=0A= DOCSIS compliant Cable Modems and Cable Modem Termination=0A= Systems", RFC 2669, August 1999.=0A= =0A= [10] St. Johns, M., "Radio Frequency (RF) Interface Management=0A= Information Base for MCNS/DOCSIS compliant RF interfaces",=0A= RFC 2670, August 1999.=0A= =0A= [11] Daniele, M. et. al.,"Textual Conventions for Internet = Network=0A= Addresses", RFC 2851, June 2000.=0A= =0A= =0A= =0A= 9. Informative References=0A= =0A= [12] Case, J., Mundy, R., Partain, D. and B. Stewart,=0A= "Introduction and Applicability Statements for Internet-=0A= Standard Management Framework", RFC 3410, December 2002.=0A= =0A= =0A= =0A= 10. Author's Address=0A= =0A= Michael Patrick=0A= Motorola Broadband Communications Sector=0A= 20 Cabot Blvd., MS M2-330=0A= Mansfield, MA 02048=0A= Phone: (508) 851-8402=0A= Email: michael.patrick@motorola.com=0A= =0A= William Murwin=0A= Motorola Broadband Communications Sector=0A= 20 Cabot Blvd., MS M2-330=0A= Mansfield, MA 02048=0A= Phone: (508) 851-8385=0A= Email: w.murwin@motorola.com=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 81]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= INTERNET-DRAFT March 2003=0A= =0A= =0A= =0A= 11. Full Copyright Statement=0A= =0A= Copyright (C) The Internet Society (2003). All Rights Reserved.=0A= =0A= This document and translations of it may be copied and furnished = to=0A= others, and derivative works that comment on or otherwise explain = it=0A= or assist in its implementation may be prepared, copied, = published=0A= and distributed, in whole or in part, without restriction of any=0A= kind, provided that the above copyright notice and this paragraph = are=0A= included on all such copies and derivative works. However, this=0A= document itself may not be modified in any way, such as by = removing=0A= the copyright notice or references to the Internet Society or = other=0A= Internet organizations, except as needed for the purpose of=0A= developing Internet standards in which case the procedures for=0A= copyrights defined in the Internet Standards process must be=0A= followed, or as required to translate it into languages other = than=0A= English.=0A= =0A= The limited permissions granted above are perpetual and will not = be=0A= revoked by the Internet Society or its successors or assigns.=0A= =0A= This document and the information contained herein is provided on = an=0A= "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET = ENGINEERING=0A= TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, = INCLUDING=0A= BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION=0A= HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF=0A= MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Expires September 2003 [Page 82]=0A= =0A= =0A= =0A= =0A= ------_=_NextPart_000_01C2DC55.4830A0B4 Content-Type: application/octet-stream; name="qos_08.mib" Content-Disposition: attachment; filename="qos_08.mib" Content-Transfer-Encoding: quoted-printable -- -- Docsis QOS Extensions MIB -- DOCS-IETF-QOS-MIB DEFINITIONS ::=3D BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32, Unsigned32, Counter64=09 FROM SNMPv2-SMI TEXTUAL-CONVENTION, MacAddress, RowStatus, TruthValue, DisplayString, TimeStamp, StorageType=09 FROM SNMPv2-TC OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF ifIndex, InterfaceIndex FROM IF-MIB docsIfMib FROM DOCS-IF-MIB InetAddressType, InetAddress, InetPortNumber=09 FROM INET-ADDRESS-MIB; docsQosMIB MODULE-IDENTITY LAST-UPDATED "200303010000Z" -- March 1, 2003 ORGANIZATION "IETF IPCDN Working Group" CONTACT-INFO " Co-Author: Michael Patrick Postal: Motorola BCS 20 Cabot Blvd, MS M2-330 Mansfield, MA 02048-1193 U.S.A. Phone: +1 508 851 8402 E-mail: michael.patrick@motorola.com Co-Author: William Murwin Postal: Motorola BCS 20 Cabot Blvd, MS M2-330 Mansfield, MA 02048-1193 U.S.A. Phone: +1 508 851 8385 E-mail: w.murwin@motorola.com" DESCRIPTION =20 "This is the management information for Quality Of Service (QOS) for DOCSIS 1.1 and 2.0." REVISION "200303010000Z" -- March 1, 2003 DESCRIPTION "Initial version, published as RFC xxxx." ::=3D { docsIfMib xx } -- xx to be assignrd by IANA =20 docsQosMIBObjects OBJECT IDENTIFIER ::=3D { docsQosMIB 1 } -- Textual Conventions DocsQosRfMacIfDirection ::=3D TEXTUAL-CONVENTION STATUS current DESCRIPTION "Indicates a direction on an RF MAC interface.=20 The value downstream(1) is from Cable Modem=20 Termination System to Cable Modem. =20 The value upstream(2) is from Cable Modem to=20 Cable Modem Termination System." SYNTAX INTEGER { downstream(1), upstream(2) } DocsQosBitRate ::=3D TEXTUAL-CONVENTION =20 DISPLAY-HINT "d" =20 STATUS current DESCRIPTION "The rate of traffic in unit of bits per second. Used to specify traffic rate for QOS." SYNTAX Unsigned32 DocsQosSchedulingType ::=3D TEXTUAL-CONVENTION STATUS current DESCRIPTION "The scheduling service provided by a CMTS for an upstream service flow. If the parameter is omitted from an upstream QOS Parameter Set, this object = takes the value of bestEffort (2). This parameter must be reported as undefined (1) for downstream QOS = Parameter Sets." SYNTAX INTEGER { undefined (1), bestEffort (2), nonRealTimePollingService(3), realTimePollingService(4), unsolictedGrantServiceWithAD(5), unsolictedGrantService(6) } ----------------------------------------------------------------------- -- -- Packet Classifier Table -- docsQosPktClassTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsQosPktClassEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table describes the packet classification configured on the CM or CMTS. =20 The model is that a packet either received as input from an interface or transmitted=20 for output on an interface may be compared=20 against an ordered list of rules pertaining to the packet contents. Each rule is a row of this table. A matching rule provides a service flow id to to which the packet is classified.=20 All rules need to match for a packet to match=20 a classifier.=20 The objects in this row correspond to a set of Classifier Encoding parameters in a DOCSIS MAC management message. The docsQosPktClassBitMap indicates which particular parameters were present in the classifier as signaled in the DOCSIS = message. If the referenced parameter was not present in the signaled DOCSIS 1.1 and 2.0 Classifier, the corresponding object in this row reports a=20 value as specified in the DESCRIPTION section. " ::=3D { docsQosMIBObjects 1 } =20 docsQosPktClassEntry OBJECT-TYPE SYNTAX DocsQosPktClassEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table provides a single packet classifier rule. The index ifIndex is an ifType of docsCableMaclayer(127)." INDEX {=20 ifIndex,=20 docsQosServiceFlowId, docsQosPktClassId } ::=3D { docsQosPktClassTable 1 } DocsQosPktClassEntry ::=3D SEQUENCE { docsQosPktClassId Unsigned32, docsQosPktClassDirection DocsQosRfMacIfDirection, docsQosPktClassPriority Integer32, docsQosPktClassIpTosLow OCTET STRING, docsQosPktClassIpTosHigh OCTET STRING, docsQosPktClassIpTosMask OCTET STRING, docsQosPktClassIpProtocol Integer32, docsQosPktClassInetAddressType InetAddressType, docsQosPktClassInetSourceAddr InetAddress, docsQosPktClassInetSourceMask InetAddress, docsQosPktClassInetDestAddr InetAddress, docsQosPktClassInetDestMask InetAddress, =20 docsQosPktClassSourcePortStart InetPortNumber, docsQosPktClassSourcePortEnd InetPortNumber, docsQosPktClassDestPortStart InetPortNumber, docsQosPktClassDestPortEnd InetPortNumber, docsQosPktClassDestMacAddr MacAddress, docsQosPktClassDestMacMask MacAddress, docsQosPktClassSourceMacAddr MacAddress, docsQosPktClassEnetProtocolType INTEGER, =20 docsQosPktClassEnetProtocol Integer32, docsQosPktClassUserPriLow Integer32, docsQosPktClassUserPriHigh Integer32, docsQosPktClassVlanId Integer32, docsQosPktClassStateActive TruthValue, docsQosPktClassPkts Counter64, docsQosPktClassBitMap BITS } docsQosPktClassId OBJECT-TYPE SYNTAX Unsigned32 (1..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Index assigned to packet classifier entry by=20 the CMTS which is unique per service flow." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.3.2" ::=3D { docsQosPktClassEntry 1 } docsQosPktClassDirection OBJECT-TYPE SYNTAX DocsQosRfMacIfDirection MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the direction to which the classifier=20 is applied." ::=3D { docsQosPktClassEntry 2 } docsQosPktClassPriority OBJECT-TYPE SYNTAX Integer32 (0..255) MAX-ACCESS read-only STATUS current DESCRIPTION "The value specifies the order of evaluation of the classifiers. The higher the value the higher the priority. The value of 0 is used as default in=20 provisioned service flows classifiers.=20 The default value of 64 is used for dynamic=20 service flow classifiers. If the referenced parameter is not present in a classifier, this object reports the default = value as defined above." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.3.5" ::=3D { docsQosPktClassEntry 3 } docsQosPktClassIpTosLow OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1)) MAX-ACCESS read-only STATUS current DESCRIPTION "The low value of a range of TOS byte values. If the referenced parameter is not present in a classifier, this object reports the value of = 0." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.1" ::=3D { docsQosPktClassEntry 4 } docsQosPktClassIpTosHigh OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1)) MAX-ACCESS read-only STATUS current DESCRIPTION "The 8-bit high value of a range of TOS byte values. If the referenced parameter is not present in a classifier, this object reports the value of = 0." REFERENCE "SP-RFIv1.1-I07-010829, Appendix C.2.1.5.1" ::=3D { docsQosPktClassEntry 5 } docsQosPktClassIpTosMask OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1)) MAX-ACCESS read-only STATUS current DESCRIPTION "The mask value is bitwise ANDed with TOS byte=20 in an IP packet and this value is used check=20 range checking of TosLow and TosHigh. If the referenced parameter is not present in a classifier, this object reports the value of = 0." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.1" ::=3D { docsQosPktClassEntry 6 } docsQosPktClassIpProtocol OBJECT-TYPE SYNTAX Integer32 (0..258) MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the value of the IP Protocol field required for IP packets to match this rule.=20 The value 256 matches traffic with any IP Protocol=20 value. The value 257 by convention matches both TCP and UDP.=20 If the referenced parameter is not present in a classifier, this object reports the value of = 258." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.2" ::=3D { docsQosPktClassEntry 7 } docsQosPktClassInetAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The type of the internet address for docsQosPktClassInetSourceAddr,=20 docsQosPktClassInetSourceMask,=20 docsQosPktClassInetDestAddr, and docsQosPktClassInetDestMask. If the referenced parameter is not present in a classifier, this object reports the value of=20 ipv4(1)." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.3" ::=3D { docsQosPktClassEntry 8 } docsQosPktClassInetSourceAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "This object specifies the value of the IP=20 Source Address required for packets to match this rule. An IP packet matches the rule when the packet ip source address bitwise ANDed with the docsQosPktClassInetSourceMask value equals the docsQosPktClassInetSourceAddr value. The address type of this object is specified by=20 docsQosPktClassInetAddressType.=09 If the referenced parameter is not present in a classifier, this object reports the value of=20 '00000000'H." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.3" ::=3D { docsQosPktClassEntry 9 } docsQosPktClassInetSourceMask OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "This object specifies which bits of a packet's IP Source Address that are compared to match this rule.=20 An IP packet matches the rule when the packet=20 source address bitwise ANDed with the docsQosPktClassInetSourceMask value equals the=20 docsQosIpPktClassInetSourceAddr value. The address type of this object is specified by=20 docsQosPktClassInetAddressType. If the referenced parameter is not present in a classifier, this object reports the value of=20 'FFFFFFFF'H." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.4" ::=3D { docsQosPktClassEntry 10 } docsQosPktClassInetDestAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "This object specifies the value of the IP=20 Destination Address required for packets to match this rule. An IP packet matches the rule when the packet ip destination address=20 bitwise ANDed with the=20 docsQosPktClassInetDestMask value equals the docsQosPktClassInetDestAddr value. The address type of this object is specified by=20 docsQosPktClassInetAddressType. If the referenced parameter is not present in a classifier, this object reports the value of=20 '00000000'H." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.5" ::=3D { docsQosPktClassEntry 11 } docsQosPktClassInetDestMask OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "This object specifies which bits of a packet's IP Destination Address that are compared to=20 match this rule.=20 An IP packet matches the rule when the packet=20 destination address bitwise ANDed with the docsQosPktClassInetDestMask value equals the=20 docsQosIpPktClassInetDestAddr value. The address type of this object is specified by=20 docsQosPktClassInetAddressType. If the referenced parameter is not present in a classifier, this object reports the value of=20 'FFFFFFFF'H." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.6" ::=3D { docsQosPktClassEntry 12 } docsQosPktClassSourcePortStart OBJECT-TYPE SYNTAX InetPortNumber MAX-ACCESS read-only STATUS current DESCRIPTION "This object specifies the low end inclusive range of TCP/UDP source port numbers to which a packet is compared. This object is irrelevant for non-TCP/UDP IP packets. If the referenced parameter is not present in a classifier, this object reports the value of = 0." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.7" ::=3D { docsQosPktClassEntry 13 } docsQosPktClassSourcePortEnd OBJECT-TYPE SYNTAX InetPortNumber MAX-ACCESS read-only STATUS current DESCRIPTION "This object specifies the high end inclusive range of TCP/UDP source port numbers to which a packet is compared. This object is irrelevant for non-TCP/UDP IP packets. If the referenced parameter is not present in a classifier, this object reports the value of=20 65535." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.8" ::=3D { docsQosPktClassEntry 14 } docsQosPktClassDestPortStart OBJECT-TYPE SYNTAX InetPortNumber MAX-ACCESS read-only STATUS current DESCRIPTION "This object specifies the low end inclusive range of TCP/UDP destination port numbers to which a packet is compared. If the referenced parameter is not present in a classifier, this object reports the value of = 0." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.9" ::=3D { docsQosPktClassEntry 15 } docsQosPktClassDestPortEnd OBJECT-TYPE SYNTAX InetPortNumber MAX-ACCESS read-only STATUS current DESCRIPTION "This object specifies the high end inclusive range of TCP/UDP destination port numbers to which a packet is compared. If the referenced parameter is not present in a classifier, this object reports the value of=20 65535." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.5.10" ::=3D { docsQosPktClassEntry 16 } docsQosPktClassDestMacAddr OBJECT-TYPE SYNTAX MacAddress MAX-ACCESS read-only STATUS current DESCRIPTION "An Ethernet packet matches an entry when its=20 destination MAC address bitwise ANDed with=20 docsQosPktClassDestMacMask equals the value of=20 docsQosPktClassDestMacAddr. =20 If the referenced parameter is not present in a classifier, this object reports the value of=20 '000000000000'H. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.6.1" ::=3D { docsQosPktClassEntry 17 } docsQosPktClassDestMacMask OBJECT-TYPE SYNTAX MacAddress MAX-ACCESS read-only STATUS current DESCRIPTION "An Ethernet packet matches an entry when its=20 destination MAC address bitwise ANDed with=20 docsQosPktClassDestMacMask equals the value of=20 docsQosPktClassDestMacAddr. If the referenced parameter is not present in a classifier, this object reports the value of=20 '000000000000'H. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.6.1" ::=3D { docsQosPktClassEntry 18 } docsQosPktClassSourceMacAddr OBJECT-TYPE SYNTAX MacAddress MAX-ACCESS read-only STATUS current DESCRIPTION "An Ethernet packet matches this entry when its=20 source MAC address equals the value of=20 this object. If the referenced parameter is not present in a classifier, this object reports the value of=20 'FFFFFFFFFFFF'H. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.6.2" ::=3D { docsQosPktClassEntry 19 } docsQosPktClassEnetProtocolType OBJECT-TYPE SYNTAX INTEGER { none(0), ethertype(1), dsap(2), mac(3), all(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the format of the layer 3=20 protocol id in the Ethernet packet. A value of=20 none(0) means that the rule does not use the=20 layer 3 protocol type as a matching criteria. A value of ethertype(1) means that the rule applies only to frames which contains an=20 EtherType value. Ethertype values are contained in packets using the Dec-Intel-Xerox (DIX) encapsulation or the RFC1042 Sub-Network Access Protocol (SNAP) encapsulation formats. A value of dsap(2) means that the rule applies only to frames using the IEEE802.3 encapsulation format with a Destination Service Access Point (DSAP) other=20 than 0xAA (which is reserved for SNAP). A value of mac(3) means that the rule applies=20 only to MAC management messages for MAC management messages. A value of all(4) means that the rule matches all Ethernet packets.=20 If the Ethernet frame contains an 802.1P/Q Tag=20 header (i.e. EtherType 0x8100), this object applies to the embedded EtherType field within=20 the 802.1P/Q header. If the referenced parameter is not present in a classifier, this object reports the value of = 0. =20 " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.6.3" ::=3D { docsQosPktClassEntry 20 } docsQosPktClassEnetProtocol OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "If docsQosEthPktClassProtocolType is none(0),=20 this object is ignored when considering whether=20 a packet matches the current rule. If dosQosPktClassEnetProtocolType is ethertype(1), this object gives the 16-bit value of the EtherType that the packet must match in order to match the rule. If docsQosPktClassEnetProtocolType is dsap(2), the lower 8 bits of this object's value must match the DSAP byte of the packet in order to match the rule. If docsQosPktClassEnetProtocolType is mac(3), the lower 8 bits of this object value represent a lower bound (inclusive) of MAC management message type codes matched, and the upper 8 bits of this object value represent the upper bound (inclusive) of matched MAC message type codes. Certain message type codes are excluded from matching, as specified in the reference. If the Ethernet frame contains an 802.1P/Q Tag = header=20 (i.e. EtherType 0x8100), this object applies to the = embedded EtherType field within the 802.1P/Q = header. If the referenced parameter is not present in the classifier, the value of this object is reported as = 0. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.6.3" ::=3D { docsQosPktClassEntry 21 } docsQosPktClassUserPriLow OBJECT-TYPE SYNTAX Integer32 (0..7) MAX-ACCESS read-only STATUS current DESCRIPTION "This object applies only to Ethernet frames=20 using the 802.1P/Q tag header (indicated with=20 EtherType 0x8100). Such frames include a 16-bit=20 Tag that contains a 3 bit Priority field and a 12 bit VLAN number. Tagged Ethernet packets must have a 3-bit Priority field within the range of=20 docsQosPktClassPriLow and docsQosPktClassPriHigh in = order to match this rule. If the referenced parameter is not present in the classifier, the value of this object is reported as = 0. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.7.1" ::=3D { docsQosPktClassEntry 22 } docsQosPktClassUserPriHigh OBJECT-TYPE SYNTAX Integer32 (0..7) MAX-ACCESS read-only STATUS current DESCRIPTION "This object applies only to Ethernet frames=20 using the 802.1P/Qtag header (indicated with=20 EtherType 0x8100). Such frames include a 16-bit=20 Tag that contains a 3 bit Priority field and a 12 bit VLAN number. Tagged Ethernet packets must have a 3-bit Priority field within the range of=20 docsQosPktClassPriLow and=20 docsQosPktClassPriHigh in order to match this rule. If the referenced parameter is not present in the classifier, the value of this object is reported=20 as 7. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.7.1" ::=3D { docsQosPktClassEntry 23 } docsQosPktClassVlanId OBJECT-TYPE SYNTAX Integer32 (0..4095) MAX-ACCESS read-only STATUS current DESCRIPTION "This object applies only to Ethernet frames=20 using the 802.1P/Q tag header. If this object's value is nonzero, tagged packets must have a VLAN Identifier that matches the value in order to match the rule. Only the least significant 12 bits of this object's value are valid.=20 If the referenced parameter is not present in the classifier, the value of this object is reported=20 as 0. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.7.2" ::=3D { docsQosPktClassEntry 24 } docsQosPktClassStateActive OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates whether or not the classifier is enabled to classify packets to a Service Flow. If the referenced parameter is not present in the classifier, the value of this object is reported=20 as true(1)." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.3.6" ::=3D { docsQosPktClassEntry 25 } docsQosPktClassPkts OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts the number of packets that have been classified using this entry. This=20 includes all packets delivered to a service flow=20 maximum rate policing function, whether or not that function drops the packets. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." ::=3D { docsQosPktClassEntry 26 } docsQosPktClassBitMap OBJECT-TYPE SYNTAX BITS { -- Reference = SP-RFIv1.1-I09-020830 rulePriority(0), -- Appendix C.2.1.3.4 activationState(1), -- Appendix C.2.1.3.6 ipTos(2), -- Appendix C.2.1.5.1 ipProtocol(3), -- Appendix C.2.1.5.2 ipSourceAddr(4), -- Appendix C.2.1.5.3 ipSourceMask(5), -- Appendix C.2.1.5.4 ipDestAddr(6), -- Appendix C.2.1.5.5 ipDestMask(7), -- Appendix C.2.1.5.6 sourcePortStart(8), -- Appendix C.2.1.5.7 sourcePortEnd(9), -- Appendix C.2.1.5.8 destPortStart(10), -- Appendix C.2.1.5.9 destPortEnd(11), -- Appendix C.2.1.5.10 destMac(12), -- Appendix C.2.1.6.1 sourceMac(13), -- Appendix C.2.1.6.2 ethertype(14), -- Appendix C.2.1.6.3 userPri(15), -- Appendix C.2.1.7.1 vlanId(16) -- Appendix C.2.1.7.2 } MAX-ACCESS read-only STATUS current DESCRIPTION=20 "This object indicates which parameter encodings = were actually present in the DOCSIS packet classifier encoding signaled in the DOCSIS message that created or modified the classifier. Note that Dynamic Service Change messages have replace semantics, so that all non-default parameters must be present whether the classifier is being created or changed. A bit of of this object is set to 1 if the = parameter indicated by the comment was present in the = classifier=20 encoding, and 0 otherwise. Note that BITS are encoded most significant bit first, so that if e.g. bits 6 and 7 are set, this = object is encoded as the octet string '030000'H. " ::=3D { docsQosPktClassEntry 27 } =20 -- -- QOS Parameter Set Table -- docsQosParamSetTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsQosParamSetEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table describes the set of DOCSIS 1.1 and 2.0 QOS parameters defined in a managed device. =20 The ifIndex index specifies a DOCSIS MAC Domain. The docsQosServiceFlowId index specifies a = particular Service Flow.=20 The docsQosParamSetType index indicates whether the active, admitted, or provisioned QOS Parameter=20 Set is being described by the row. Only the QOS Parameter Sets of Docsis 1.1 and 2.0 service flows are represented in this table. =20 Docsis 1.0 QOS service profiles are not=20 represented in this table. Each row corresponds to a DOCSIS QOS Parameter Set as signaled via DOCSIS MAC management messages. Each object in the row corresponds to one or=20 part of one DOCSIS 1.1 Service Flow Encoding. The docsQosParamSetBitMap object in the row = indicates which particular parameters were signaled in=20 the original registration or dynamic service request message that created the QOS Parameter Set. In many cases, even if a QOS Parameter Set = parameter was not signaled, the DOCSIS specification calls for a default value to be used. That default value is reported as the value of the corresponding = object in this row. Many objects are not applicable depending on the service flow direction or upstream scheduling type. The object value reported in this case is specified in the DESCRIPTION clause. " ::=3D { docsQosMIBObjects 2 } -- docsQosParamSetEntry { docsQosParamSetTable 1 } was=20 -- removed in an initial and unimplemented version of this mib. =20 docsQosParamSetEntry OBJECT-TYPE SYNTAX DocsQosParamSetEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique set of QOS parameters." INDEX {=20 ifIndex, docsQosServiceFlowId, docsQosParamSetType } ::=3D { docsQosParamSetTable 1 } DocsQosParamSetEntry ::=3D SEQUENCE { =20 docsQosParamSetServiceClassName DisplayString, docsQosParamSetPriority Integer32, docsQosParamSetMaxTrafficRate DocsQosBitRate, docsQosParamSetMaxTrafficBurst Unsigned32, docsQosParamSetMinReservedRate DocsQosBitRate, docsQosParamSetMinReservedPkt Integer32, docsQosParamSetActiveTimeout Integer32, docsQosParamSetAdmittedTimeout Integer32, docsQosParamSetMaxConcatBurst Integer32, docsQosParamSetSchedulingType DocsQosSchedulingType, docsQosParamSetNomPollInterval Unsigned32, docsQosParamSetTolPollJitter Unsigned32, docsQosParamSetUnsolicitGrantSize Integer32, docsQosParamSetNomGrantInterval Unsigned32, docsQosParamSetTolGrantJitter Unsigned32, docsQosParamSetGrantsPerInterval Integer32, docsQosParamSetTosAndMask OCTET STRING, docsQosParamSetTosOrMask OCTET STRING, docsQosParamSetMaxLatency Unsigned32, docsQosParamSetType INTEGER, docsQosParamSetRequestPolicyOct OCTET STRING, docsQosParamSetBitMap BITS } docsQosParamSetServiceClassName OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION "Refers to the Service Class Name that the=20 parameter set values were derived. If the referenced parameter is not present in the corresponding DOCSIS QOS Parameter Set, the default = value of this object is a zero length string. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.3.4" ::=3D { docsQosParamSetEntry 4 } docsQosParamSetPriority OBJECT-TYPE SYNTAX Integer32 (0..7) MAX-ACCESS read-only STATUS current DESCRIPTION "The relative priority of a service flow. Higher numbers indicate higher priority. This priority should only be used to differentiate service flow with identical parameter sets. If the referenced parameter is not present in the corresponding DOCSIS QOS Parameter Set, the default = value of this object is 0. If the parameter is not applicable, the reported value is 0. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.1" ::=3D { docsQosParamSetEntry 5 } docsQosParamSetMaxTrafficRate OBJECT-TYPE SYNTAX DocsQosBitRate MAX-ACCESS read-only STATUS current DESCRIPTION "Maximum sustained traffic rate allowed for this=20 service flow in bits/sec. Must count all MAC frame=20 data PDU from the bytes following the MAC header = HCS to the end of the CRC. The number of bytes=20 forwarded is limited during any time interval. The value 0 means no maximum traffic rate is=20 enforced. This object applies to both upstream and downstream service flows. If the referenced parameter is not present in the corresponding DOCSIS QOS Parameter Set, the default value of this object is 0. If the parameter is not applicable, it is reported as 0. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.2" ::=3D { docsQosParamSetEntry 6 } docsQosParamSetMaxTrafficBurst OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the token bucket size in bytes for this parameter set. The value is calculated=20 from the byte following the MAC header HCS to=20 the end of the CRC. This object is applied in=20 conjunction with docsQosParamSetMaxTrafficRate to=20 calculate maximum sustained traffic rate. If the referenced parameter is not present in the corresponding DOCSIS QOS Parameter Set, the default value of this object for scheduling types bestEffort (2), nonRealTimePollingService(3), and realTimePollingService(4) is 3044.=20 If this parameter is not applicable, it is reported as 0. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.3" ::=3D { docsQosParamSetEntry 7 } docsQosParamSetMinReservedRate OBJECT-TYPE SYNTAX DocsQosBitRate MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the guaranteed minimum rate in bits/sec for this parameter set. The value is=20 calculated from the byte following the MAC=20 header HCS to the end of the CRC. The default value of 0 has the meaning that no bandwidth=20 is reserved. If the referenced parameter is not present in the corresponding DOCSIS QOS Parameter Set, the default value of this object is 0. If the parameter is not applicable, it is reported as 0. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.4" ::=3D { docsQosParamSetEntry 8 } docsQosParamSetMinReservedPkt OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies an assumed minimum packet size in=20 bytes for which the docsQosParamSetMinReservedRate=20 will be provided. The value is calculated from the byte following the MAC header HCS to the=20 end of the CRC.=20 =20 If the referenced parameter is omitted from a DOCSIS QOS parameter set, the default value is CMTS implementation dependent. In this case, the CMTS reports the default value it is using and the CM reports a value of 0. If the referenced parameter is not applicable to the direction or scheduling type of the service flow, both CMTS and CM report this object's value as 0. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.5" ::=3D { docsQosParamSetEntry 9 } docsQosParamSetActiveTimeout OBJECT-TYPE SYNTAX Integer32 (0..65535) UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the maximum duration in seconds that=20 resources remain unused on an active service flow before CMTS signals that both active and admitted parameters set are null. The default value of 0 signifies an infinite amount of time. =20 If the referenced parameter is not present in the corresponding DOCSIS QOS Parameter Set, the default value of this object is 0. " =20 REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.6" ::=3D { docsQosParamSetEntry 10 } docsQosParamSetAdmittedTimeout OBJECT-TYPE SYNTAX Integer32 (0..65535) UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the maximum duration in seconds that=20 resources remain in admitted state before=20 resources must be released. The value of 0 signifies an infinite amount=20 of time. If the referenced parameter is not present in the corresponding DOCSIS QOS Parameter Set, the=20 default value of this object is 200. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.5.7" DEFVAL { 200 } ::=3D { docsQosParamSetEntry 11 } docsQosParamSetMaxConcatBurst OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the maximum concatenated burst in bytes which an upstream service flow is allowed.=20 The value is calculated from the FC byte of the Concatenation MAC Header to the last CRC byte in=20 of the last concatenated MAC frame, inclusive. The value of 0 specifies no maximum burst. If the referenced parameter is not present in the corresponding DOCSIS QOS Parameter Set, the default value of this object for scheduling types bestEffort(2), nonRealTimePollingService(3), and realTimePollingService(4) is 1522. If the parameter=20 is not applicable, this object's value is reported as 0. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.1" ::=3D { docsQosParamSetEntry 12 } docsQosParamSetSchedulingType OBJECT-TYPE SYNTAX DocsQosSchedulingType MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the upstream scheduling service used for=20 upstream service flow.=20 If the referenced parameter is not present in the corresponding DOCSIS QOS Parameter Set of an upstream service flow, the default value of this object is bestEffort(2). For QOS parameter sets of downstream service flows, this object's value is reported as undefined(1). " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.2" ::=3D { docsQosParamSetEntry 13 } docsQosParamSetNomPollInterval OBJECT-TYPE SYNTAX Unsigned32=20 UNITS "microseconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the nominal interval in microseconds=20 between successive unicast request opportunities on an upstream service flow. This object applies only to upstream service flows with DocsQosSchedulingType of value nonRealTimePollingService(3), realTimePollingService(4), and unsolictedGrantServiceWithAD(5). The parameter is mandatory for realTimePollingService(4). If the parameter is omitted with nonRealTimePollingService(3), the CMTS uses an implementation dependent value. If the parameter is omitted with unsolictedGrantServiceWithAD(5), the CMTS uses as a default value the value of the Nominal Grant Interval parameter. In all cases, the CMTS reports the value it is using when the parameter is applicable. The CM reports the=20 signaled parameter value if it was signaled,=20 and 0 otherwise. =20 If the referenced parameter is not applicable to the direction or scheduling type of the corresponding DOCSIS QOS Parameter Set, both CMTS and CM report this object's value as 0. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.4" ::=3D { docsQosParamSetEntry 15 } docsQosParamSetTolPollJitter OBJECT-TYPE SYNTAX Unsigned32=20 UNITS "microseconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the maximum amount of time in microseconds that the unicast request interval may be delayed from the nominal periodic schedule on an upstream service flow. This parameter is applicable only to upstream service flows with a DocsQosSchedulingType of realTimePollingService(4) or unsolictedGrantServiceWithAD(5). If the referenced parameter is applicable but not present in the corresponding DOCSIS QOS Parameter Set, the CMTS uses an implementation dependent=20 value and reports the value it is using. The CM reports a value of 0 in this case. If the parameter is not applicable to the direction or upstream scheduling type of the service flow, both CMTS and CM report this object's value as 0. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.5" ::=3D { docsQosParamSetEntry 16 } docsQosParamSetUnsolicitGrantSize OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the unsolicited grant size in bytes.=20 The grant size includes the entire MAC frame=20 data PDU from the Frame Control byte to end of the MAC frame. The referenced parameter is applicable only=20 for upstream flows with a DocsQosSchedulingType of of unsolicitedGrantServicewithAD(5) or unsolicitedGrantService(6), and is mandatory when applicable. Both CMTS and CM report the signaled value of the parameter in this case. =20 If the referenced parameter is not applicable to the direction or scheduling type of the corresponding DOCSIS QOS Parameter Set, both CMTS and CM report this object's value as 0. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.6" ::=3D { docsQosParamSetEntry 17 } docsQosParamSetNomGrantInterval OBJECT-TYPE SYNTAX Unsigned32 UNITS "microseconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the nominal interval in microseconds=20 between successive data grant opportunities=20 on an upstream service flow. The referenced parameter is applicable only=20 for upstream flows with a DocsQosSchedulingType of of unsolicitedGrantServicewithAD(5) or unsolicitedGrantService(6), and is mandatory when applicable. Both CMTS and CM report the signaled value of the parameter in this case. If the referenced parameter is not applicable to the direction or scheduling type of the corresponding DOCSIS QOS Parameter Set, both CMTS and CM report this object's value as 0. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.7" ::=3D { docsQosParamSetEntry 18 } docsQosParamSetTolGrantJitter OBJECT-TYPE SYNTAX Unsigned32=20 UNITS "microseconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the maximum amount of time in microseconds that the transmission opportunities may be delayed from the nominal periodic schedule.=20 The referenced parameter is applicable only=20 for upstream flows with a DocsQosSchedulingType of of unsolicitedGrantServicewithAD(5) or unsolicitedGrantService(6), and is mandatory when applicable. Both CMTS and CM report the signaled value of the parameter in this case. If the referenced parameter is not applicable to the direction or scheduling type of the corresponding DOCSIS QOS Parameter Set, both CMTS and CM report this object's value as 0. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.8" ::=3D { docsQosParamSetEntry 19 } docsQosParamSetGrantsPerInterval OBJECT-TYPE SYNTAX Integer32 (0..127) MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the number of data grants per Nominal=20 Grant Interval=20 (docsQosParamSetNomGrantInterval). The referenced parameter is applicable only=20 for upstream flows with a DocsQosSchedulingType of of unsolicitedGrantServicewithAD(5) or unsolicitedGrantService(6), and is mandatory when applicable. Both CMTS and CM report the signaled value of the parameter in this case. If the referenced parameter is not applicable to the direction or scheduling type of the corresponding DOCSIS QOS Parameter Set, both CMTS and CM report this object's value as 0. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.9" ::=3D { docsQosParamSetEntry 20 } docsQosParamSetTosAndMask OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1)) MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the AND mask for IP TOS byte for = overwriting IP packets TOS value. The IP packets TOS byte is=20 bitwise ANDed with docsQosParamSetTosAndMask and=20 result is bitwise ORed with = docsQosParamSetTosORMask and result is written to IP packet TOS byte.=20 A value of 'FF'H for docsQosParamSetTosAndMask and a value of '00'H for docsQosParamSetTosOrMask means = that IP Packet TOS byte is not overwritten. =09 This combination is reported if the referenced parameter is not present in a QOS Parameter Set. =09 Even though the this object is only enforced by the Cable Modem Termination System (CMTS), Cable Modems must report the value as signaled in=20 the referenced parameter." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.10" ::=3D { docsQosParamSetEntry 21 } docsQosParamSetTosOrMask OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1)) MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the OR mask for IP TOS byte. See the description of docsQosParamSetTosAndMask for further details." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.10" ::=3D { docsQosParamSetEntry 22 } docsQosParamSetMaxLatency OBJECT-TYPE SYNTAX Unsigned32 UNITS "microseconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the maximum latency between the reception of a packet by the CMTS on its NSI=20 and the forwarding of the packet to the RF interface. A value of 0 signifies no maximum latency enforced. This object only applies to downstream service flows. If the referenced parameter is not present in the corresponding downstream DOCSIS QOS Parameter Set,=20 the default value is 0. This parameter is not applicable to upstream DOCSIS QOS Parameter = Sets, and its value is reported as 0 in this case. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.7.1" ::=3D { docsQosParamSetEntry 23 } docsQosParamSetType OBJECT-TYPE SYNTAX INTEGER { active (1),=20 admitted (2), provisioned (3) } MAX-ACCESS not-accessible STATUS current DESCRIPTION "Defines the type of the QOS parameter set defined by this row. active(1) indicates the Active QOS parameter set, describing the service currently being provided by the Docsis MAC domain to the=20 service flow. admitted(2) indicates the Admitted QOS Parameter Set, describing services reserved by by the Docsis MAC domain for use by the service = flow. provisioned (3) describes the QOS Parameter Set defined in the DOCSIS CM Configuration file for the service flow." REFERENCE "SP-RFIv1.1-I09-020830, 8.1.5" ::=3D { docsQosParamSetEntry 24 } docsQosParamSetRequestPolicyOct OBJECT-TYPE SYNTAX OCTET STRING (SIZE(4)) -- A 32-bit mask represented most significant byte=20 -- first. The 32 bit integer represented in this = manner -- equals the binary value of the referenced = integer -- parameter of the DOCSIS RFI specification. -- The BITS syntax is not used in order to avoid -- the confusion caused by different bit numbering -- conventions. MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies which transmit interval opportunities=20 the CM omits for upstream transmission requests and = packet transmissions. This object takes its default value for downstream service flows. Unless otherwise indicated, a bit value of 1 means that a CM must *not* use that opportunity for=20 upstream transmission. Calling bit 0 the least significant bit of the=20 least significant (4th) octet, and increasing bit number with significance, the bit definitions are as defined below: broadcastReqOpp(0): all CMs broadcast request opportunities priorityReqMulticastReq(1): priority request multicast request = opportunities reqDataForReq(2): request/data opportunities for requests reqDataForData(3): request/data opportunities for data piggybackReqWithData(4): =20 piggyback requests with data =20 concatenateData(5): concatenate data fragmentData(6): fragment data suppresspayloadheaders(7):=20 suppress payload headers dropPktsExceedUGSize(8): A value of 1 mean that service flow must drop packet that do not fit in the Unsolicited=20 Grant size=20 If the referenced parameter is not present in=20 a QOS Parameter Set, the value of this object is reported as '00000000'H. "=20 REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.6.3" ::=3D { docsQosParamSetEntry 25 } docsQosParamSetBitMap OBJECT-TYPE -- Each bit corresponds to a parameter -- from SP-RFI-v1.1-I07-010829, = Appendix C SYNTAX BITS { -- in the indicated section number. trafficPriority(0), -- C.2.2.5.1 maxTrafficRate(1), -- C.2.2.5.2 maxTrafficBurst(2), -- C.2.2.5.3 minReservedRate(3), -- C.2.2.5.4 minReservedPkt(4), -- C.2.2.5.5 activeTimeout(5), -- C.2.2.5.6 admittedTimeout(6), -- C.2.2.5.7 maxConcatBurst(7), -- C.2.2.6.1 schedulingType(8), -- C.2.2.6.2 requestPolicy(9), -- C.2.2.6.3 nomPollInterval(10), -- C.2.2.6.4 tolPollJitter(11), -- C.2.2.6.5 unsolicitGrantSize(12), -- C.2.2.6.6 nomGrantInterval(13), -- C.2.2.6.7 tolGrantJitter(14), -- C.2.2.6.8 grantsPerInterval(15), -- C.2.2.6.9 tosOverwrite(16), -- C.2.2.6.10 maxLatency(17) -- C.2.2.7.1 } MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the set of QOS Parameter Set parameters actually signaled in the=20 DOCSIS registration or dynamic service request message that created or modified the QOS Parameter = Set.=20 A bit is set to 1 when the parameter described by the indicated reference section is present in the original request. =20 =20 Note that when Service Class names are expanded, the registration or dynamic response message may contain parameters as expanded by the CMTS based on a stored service class. These expanded parameters are *not* indicated by a 1 bit in this object. Note that even though some QOS Parameter Set=20 parameters may not be signaled in a message (so that the paramater's bit in this object is 0) the DOCSIS specification calls for default values to be used. These default values are reported as the corresponding object's value in the row.=20 Note that BITS objects are encoded most significant bit first. For example, if bits 1 and 16 are set, the value of this object=20 is the octet string '400080'H. =20 " ::=3D { docsQosParamSetEntry 26 } -- -- Service Flow Table -- docsQosServiceFlowTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsQosServiceFlowEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table describes the set of Docsis-QOS=20 Service Flows in a managed device. " ::=3D { docsQosMIBObjects 3 } =20 docsQosServiceFlowEntry OBJECT-TYPE SYNTAX DocsQosServiceFlowEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Describes a service flow. An entry in the table exists for each=20 Service Flow ID. The ifIndex is an =20 ifType of docsCableMaclayer(127)." INDEX {=20 ifIndex,=20 docsQosServiceFlowId=20 } ::=3D { docsQosServiceFlowTable 1 } DocsQosServiceFlowEntry ::=3D SEQUENCE { =20 docsQosServiceFlowId Unsigned32, docsQosServiceFlowSID Unsigned32, docsQosServiceFlowDirection DocsQosRfMacIfDirection, docsQosServiceFlowPrimary TruthValue } docsQosServiceFlowId OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS not-accessible STATUS current DESCRIPTION "An index assigned to a service flow by CMTS." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.3.2" ::=3D { docsQosServiceFlowEntry 1 } docsQosServiceFlowSID OBJECT-TYPE SYNTAX Unsigned32 (0..16383) MAX-ACCESS read-only STATUS current DESCRIPTION "Service Identifier (SID) assigned to an=20 admitted or active service flow. This object reports a value of 0 if a Service Id is not=20 associated with the service flow. Only active=20 or admitted upstream service flows will have a Service Id (SID)." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.3.3" ::=3D { docsQosServiceFlowEntry 2 } docsQosServiceFlowDirection OBJECT-TYPE SYNTAX DocsQosRfMacIfDirection MAX-ACCESS read-only STATUS current DESCRIPTION "The direction of the service flow." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.1/2" ::=3D { docsQosServiceFlowEntry 3 } docsQosServiceFlowPrimary OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "Object reflects whether service flow is the primary = or a secondary service flow. A primary service flow is the default service flow for otherwise unclassified traffic and all MAC=20 messages." REFERENCE "SP-RFIv1.1-I09-020830, Section 8.1 " ::=3D { docsQosServiceFlowEntry 4 } -- -- Service Flow Stats Table -- docsQosServiceFlowStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsQosServiceFlowStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table describes statistics associated with = the =20 Service Flows in a managed device. " ::=3D { docsQosMIBObjects 4 } =20 docsQosServiceFlowStatsEntry OBJECT-TYPE SYNTAX DocsQosServiceFlowStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Describes a set of service flow statistics. An entry in the table exists for each=20 Service Flow ID. The ifIndex is an =20 ifType of docsCableMaclayer(127)." INDEX {=20 ifIndex,=20 docsQosServiceFlowId=20 } ::=3D { docsQosServiceFlowStatsTable 1 } DocsQosServiceFlowStatsEntry ::=3D SEQUENCE { docsQosServiceFlowPkts Counter64, docsQosServiceFlowOctets Counter64, docsQosServiceFlowTimeCreated TimeStamp, docsQosServiceFlowTimeActive Counter32, docsQosServiceFlowPHSUnknowns Counter32, docsQosServiceFlowPolicedDropPkts Counter32, docsQosServiceFlowPolicedDelayPkts Counter32 } docsQosServiceFlowPkts OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Packet Data PDUs classified to this=20 service flow and forwarded beyond a service flow maximum rate policing function. This object does not count MAC-specific management messages. CMs not classifying downstream packets may report=20 this object's value as 0. =09 Particularly for UGS flows, packets sent on the primary service flow in violation of the UGS grant=20 size should be counted only on the primary service=20 flow's counters. =09 =20 Unclassified upstream user data packets (i.e. non=20 MAC-management) forwarded to the default upstream service flow should be incremented for this object. This object does include packets counted by=20 docsQosServiceFlowPolicedDelayPkts, but does not = include packets counted by = docsQosServiceFlowPolicedDropPkts. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." ::=3D { docsQosServiceFlowStatsEntry 1 } docsQosServiceFlowOctets OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of octets from the byte after the MAC=20 header HCS to the end of the CRC for all packets counted=20 in the docsQosServiceFlowPkts object for this row.=20 Note that this counts the octets after payload = header suppression has been applied. CMs not classifying = to a downstream service flow may report this object's=20 value as 0 for that flow. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." ::=3D { docsQosServiceFlowStatsEntry 2 } docsQosServiceFlowTimeCreated OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when the service flow=20 was created." ::=3D { docsQosServiceFlowStatsEntry 3 } docsQosServiceFlowTimeActive OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The number of seconds that the service flow has been active. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." ::=3D { docsQosServiceFlowStatsEntry 4 } docsQosServiceFlowPHSUnknowns OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of packets received on the service flow with an unknown payload header suppression index. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." ::=3D { docsQosServiceFlowStatsEntry 5 } docsQosServiceFlowPolicedDropPkts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Packet Data PDUs classified to this service flow dropped due to: (1) implementation-dependent excessive delay while enforcing the Maximum Sustained Traffic Rate; or (2) UGS packets dropped due to exceeding the=20 Unsolicited Grant Size with a=20 Request/Transmission policy that requires such=20 packets to be dropped. Classified packets dropped due to other reasons must be counted in ifOutDiscards for interface of this=20 service flow. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." ::=3D { docsQosServiceFlowStatsEntry 6 } docsQosServiceFlowPolicedDelayPkts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object counts only packets delayed in order to = maintain the Maximum Sustained Traffic Rate. This object=20 will always report a value of 0 for UGS flows because the Maximum Sustained Traffic Rate does not apply. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object."=09 ::=3D { docsQosServiceFlowStatsEntry 7 } -- -- Upstream Service Flow Stats Table (CMTS ONLY) -- docsQosUpstreamStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsQosUpstreamStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table describes statistics associated with =20 upstream service flows. All counted frames must=20 be received without an FCS error." ::=3D { docsQosMIBObjects 5 } =20 docsQosUpstreamStatsEntry OBJECT-TYPE SYNTAX DocsQosUpstreamStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Describes a set of upstream service flow = statistics. An entry in the table exists for each=20 upstream Service Flow in a managed device.=20 The ifIndex is an ifType of = docsCableMaclayer(127)." INDEX {=20 ifIndex,=20 docsQosSID=20 } ::=3D { docsQosUpstreamStatsTable 1 } DocsQosUpstreamStatsEntry ::=3D SEQUENCE { docsQosSID Unsigned32, docsQosUpstreamFragments Counter32, docsQosUpstreamFragDiscards Counter32, docsQosUpstreamConcatBursts Counter32 } docsQosSID OBJECT-TYPE SYNTAX Unsigned32 (1..16383) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Identifies a service id for an admitted or active=20 upstream service flow." ::=3D { docsQosUpstreamStatsEntry 1 } docsQosUpstreamFragments OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of fragmentation headers received on an upstream service flow, regardless of whether the fragment was correctly reassembled into a=20 valid packet.=20 =09 This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." ::=3D { docsQosUpstreamStatsEntry 2 } docsQosUpstreamFragDiscards OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of upstream fragments discarded and not=20 assembled into a valid upstream packet. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." ::=3D { docsQosUpstreamStatsEntry 3 } docsQosUpstreamConcatBursts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of concatenation headers received on an=20 upstream service flow. =20 This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." ::=3D { docsQosUpstreamStatsEntry 4 } -- -- Dynamic Service Stats Table -- docsQosDynamicServiceStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsQosDynamicServiceStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table describes statistics associated with = the =20 Dynamic Service Flows in a managed device. " ::=3D { docsQosMIBObjects 6 } =20 docsQosDynamicServiceStatsEntry OBJECT-TYPE SYNTAX DocsQosDynamicServiceStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Describes a set of dynamic service flow = statistics. Two entries exist for each Docsis mac layer=20 interface for the upstream and downstream = direction. On the CMTS, the downstream direction row = indicates messages transmitted or transactions originated by the CMTS. The upstream direction row indicates messages received or transaction originated by the CM. On the CM, the downstream direction row=20 indicates messages received or transactions originated by the CMTS. The upstream direction=20 row indicates messages transmitted by the CM or transactions originated by the CM. The ifIndex is an ifType of = docsCableMaclayer(127)." INDEX {=20 ifIndex,=20 docsQosIfDirection=20 } ::=3D { docsQosDynamicServiceStatsTable 1 } DocsQosDynamicServiceStatsEntry ::=3D SEQUENCE { docsQosIfDirection DocsQosRfMacIfDirection, docsQosDSAReqs Counter32, docsQosDSARsps Counter32, docsQosDSAAcks Counter32, docsQosDSCReqs Counter32, docsQosDSCRsps Counter32, docsQosDSCAcks Counter32, docsQosDSDReqs Counter32, docsQosDSDRsps Counter32, docsQosDynamicAdds Counter32, docsQosDynamicAddFails Counter32, docsQosDynamicChanges Counter32, docsQosDynamicChangeFails Counter32, docsQosDynamicDeletes Counter32, docsQosDynamicDeleteFails Counter32, docsQosDCCReqs Counter32, docsQosDCCRsps Counter32, docsQosDCCAcks Counter32, docsQosDCCs Counter32, docsQosDCCFails Counter32 } docsQosIfDirection OBJECT-TYPE SYNTAX DocsQosRfMacIfDirection MAX-ACCESS not-accessible STATUS current DESCRIPTION "The direction of interface." ::=3D { docsQosDynamicServiceStatsEntry 1 } docsQosDSAReqs OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Dynamic Service Addition Requests, including retries. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object."=20 ::=3D { docsQosDynamicServiceStatsEntry 2 } docsQosDSARsps OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Dynamic Service Addition Responses, including retries. =09 This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object."=20 ::=3D { docsQosDynamicServiceStatsEntry 3 } docsQosDSAAcks OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Dynamic Service Addition = Acknowledgements, including retries. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object."=20 ::=3D { docsQosDynamicServiceStatsEntry 4 } docsQosDSCReqs OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Dynamic Service Change Requests, including retries. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object."=20 ::=3D { docsQosDynamicServiceStatsEntry 5 } docsQosDSCRsps OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Dynamic Service Change Responses, including retries. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object."=20 ::=3D { docsQosDynamicServiceStatsEntry 6 } docsQosDSCAcks OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Dynamic Service Change = Acknowledgements, including retries. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." ::=3D { docsQosDynamicServiceStatsEntry 7 } docsQosDSDReqs OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Dynamic Service Delete Requests, including retries. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object."=20 ::=3D { docsQosDynamicServiceStatsEntry 8 } docsQosDSDRsps OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Dynamic Service Delete Responses, including retries. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object."=20 ::=3D { docsQosDynamicServiceStatsEntry 9 } docsQosDynamicAdds OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of successful Dynamic Service Addition transactions. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." ::=3D { docsQosDynamicServiceStatsEntry 10 } docsQosDynamicAddFails OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of failed Dynamic Service Addition transactions. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." ::=3D { docsQosDynamicServiceStatsEntry 11 } docsQosDynamicChanges OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of successful Dynamic Service Change transactions. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." ::=3D { docsQosDynamicServiceStatsEntry 12 } docsQosDynamicChangeFails OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of failed Dynamic Service Change transactions. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." ::=3D { docsQosDynamicServiceStatsEntry 13 } docsQosDynamicDeletes OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of successful Dynamic Service Delete transactions. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object."=20 ::=3D { docsQosDynamicServiceStatsEntry 14 } docsQosDynamicDeleteFails OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of failed Dynamic Service Delete transactions. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object."=20 ::=3D { docsQosDynamicServiceStatsEntry 15 } docsQosDCCReqs OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Dynamic Channel Change Request = messages traversing an interface. This count is nonzero only = on downstream direction rows. This count should=20 include number of retries. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." ::=3D { docsQosDynamicServiceStatsEntry 16 } docsQosDCCRsps OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Dynamic Channel Change Response = messages traversing an interface. This count is nonzero=20 only on upstream direction rows. This count should=20 include number of retries. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." =20 ::=3D { docsQosDynamicServiceStatsEntry 17 } docsQosDCCAcks OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Dynamic Channel Change = Acknowledgement messages traversing an interface. This count=20 is nonzero only on downstream direction rows. This count should include number of retries. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." ::=3D { docsQosDynamicServiceStatsEntry 18 } docsQosDCCs OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of successful Dynamic Channel Change transactions. This count is nonzero only on = downstream=20 direction rows. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." ::=3D { docsQosDynamicServiceStatsEntry 19 } docsQosDCCFails OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of failed Dynamic Channel Change transactions. This count is nonzero only on=20 downstream direction rows. This counter's last discontinuity is the=20 ifCounterDiscontinuityTime for same ifIndex that=20 indexes this object." ::=3D { docsQosDynamicServiceStatsEntry 20 } -- -- Service Flow Log Table (CMTS ONLY) -- docsQosServiceFlowLogTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsQosServiceFlowLogEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains a log of the disconnected Service Flows in a managed device." ::=3D { docsQosMIBObjects 7 } =20 docsQosServiceFlowLogEntry OBJECT-TYPE SYNTAX DocsQosServiceFlowLogEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The information regarding a single disconnected=20 service flow." INDEX {=20 docsQosServiceFlowLogIndex } ::=3D { docsQosServiceFlowLogTable 1 } DocsQosServiceFlowLogEntry ::=3D SEQUENCE { docsQosServiceFlowLogIndex Unsigned32, docsQosServiceFlowLogIfIndex InterfaceIndex, =20 docsQosServiceFlowLogSFID Unsigned32, docsQosServiceFlowLogCmMac MacAddress, docsQosServiceFlowLogPkts Counter64, docsQosServiceFlowLogOctets Counter64, =20 docsQosServiceFlowLogTimeDeleted TimeStamp, =20 docsQosServiceFlowLogTimeCreated TimeStamp, docsQosServiceFlowLogTimeActive Counter32, docsQosServiceFlowLogDirection DocsQosRfMacIfDirection, docsQosServiceFlowLogPrimary TruthValue, docsQosServiceFlowLogServiceClassName DisplayString, docsQosServiceFlowLogPolicedDropPkts Counter32, docsQosServiceFlowLogPolicedDelayPkts Counter32, docsQosServiceFlowLogControl INTEGER } docsQosServiceFlowLogIndex OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Unique index for a logged service flow." ::=3D { docsQosServiceFlowLogEntry 1 } docsQosServiceFlowLogIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-only STATUS current DESCRIPTION "The ifIndex of ifType docsCableMaclayer(127)=20 on the CMTS where the service flow was present." ::=3D { docsQosServiceFlowLogEntry 2 } docsQosServiceFlowLogSFID OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS read-only STATUS current DESCRIPTION "The index assigned to the service flow by the = CMTS." ::=3D { docsQosServiceFlowLogEntry 3 } docsQosServiceFlowLogCmMac OBJECT-TYPE SYNTAX MacAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The MAC address for the cable modem associated = with=20 the service flow." ::=3D { docsQosServiceFlowLogEntry 4 } docsQosServiceFlowLogPkts OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of packets counted on this service flow=20 after payload header suppression." ::=3D { docsQosServiceFlowLogEntry 5 } docsQosServiceFlowLogOctets OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of octets counted on this service flow=20 after payload header suppression." ::=3D { docsQosServiceFlowLogEntry 6 } docsQosServiceFlowLogTimeDeleted OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when the service flow=20 was deleted." ::=3D { docsQosServiceFlowLogEntry 7 } docsQosServiceFlowLogTimeCreated OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when the service flow=20 was created." ::=3D { docsQosServiceFlowLogEntry 8 } docsQosServiceFlowLogTimeActive OBJECT-TYPE SYNTAX Counter32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The total time that service flow was active." ::=3D { docsQosServiceFlowLogEntry 9 } docsQosServiceFlowLogDirection OBJECT-TYPE SYNTAX DocsQosRfMacIfDirection MAX-ACCESS read-only STATUS current DESCRIPTION "The value of docsQosServiceFlowDirection=20 for the service flow." ::=3D { docsQosServiceFlowLogEntry 10 } docsQosServiceFlowLogPrimary OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "The value of docsQosServiceFlowPrimary for the=20 service flow." ::=3D { docsQosServiceFlowLogEntry 11 } docsQosServiceFlowLogServiceClassName OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION "The value of docsQosParamSetServiceClassName for the provisioned QOS Parameter Set of the=20 service flow." ::=3D { docsQosServiceFlowLogEntry 12 } docsQosServiceFlowLogPolicedDropPkts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The final value of = docsQosServiceFlowPolicedDropPkts for the service flow." ::=3D { docsQosServiceFlowLogEntry 13 } docsQosServiceFlowLogPolicedDelayPkts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The final value of = docsQosServiceFlowPolicedDelayPkts for the service flow." ::=3D { docsQosServiceFlowLogEntry 14 } docsQosServiceFlowLogControl OBJECT-TYPE SYNTAX INTEGER { active(1),=20 destroy(6) } MAX-ACCESS read-write STATUS current DESCRIPTION "Setting this object to the value destroy(6) removes this entry from the table.=20 Reading this object return the value active(1)." ::=3D { docsQosServiceFlowLogEntry 15 } -- -- Service Class Table (CMTS ONLY) -- docsQosServiceClassTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsQosServiceClassEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table describes the set of Docsis-QOS=20 Service Classes in a CMTS. " ::=3D { docsQosMIBObjects 8 } =20 docsQosServiceClassEntry OBJECT-TYPE SYNTAX DocsQosServiceClassEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A provisioned service class on a CMTS.=20 Each entry defines a template for certain=20 DOCSIS QOS Parameter Set values. When a CM=20 creates or modifies an Admitted QOS Parameter Set for a Service Flow, it may reference a Service Class Name instead of providing explicit QOS Parameter Set values. In this case, the CMTS populates the QOS Parameter Set with the applicable=20 corresponding values from the named Service Class. Subsequent changes to a Service Class row do *not*=20 affect the QOS Parameter Set values of any service = flows already admitted. =20 A service class template applies to only a single direction, as indicated in the=20 docsQosServiceClassDirection object. " INDEX {=20 docsQosServiceClassName=20 } ::=3D { docsQosServiceClassTable 1 } DocsQosServiceClassEntry ::=3D SEQUENCE { docsQosServiceClassName DisplayString, docsQosServiceClassStatus RowStatus, docsQosServiceClassPriority Integer32, docsQosServiceClassMaxTrafficRate DocsQosBitRate, docsQosServiceClassMaxTrafficBurst Unsigned32, docsQosServiceClassMinReservedRate DocsQosBitRate, docsQosServiceClassMinReservedPkt Integer32, docsQosServiceClassMaxConcatBurst Integer32, docsQosServiceClassNomPollInterval Unsigned32, docsQosServiceClassTolPollJitter Unsigned32, docsQosServiceClassUnsolicitGrantSize Integer32, docsQosServiceClassNomGrantInterval Unsigned32, docsQosServiceClassTolGrantJitter Unsigned32, docsQosServiceClassGrantsPerInterval Integer32, docsQosServiceClassMaxLatency Unsigned32, docsQosServiceClassActiveTimeout Integer32, docsQosServiceClassAdmittedTimeout Integer32, docsQosServiceClassSchedulingType DocsQosSchedulingType, docsQosServiceClassRequestPolicy OCTET STRING, docsQosServiceClassTosAndMask OCTET STRING, docsQosServiceClassTosOrMask OCTET STRING, docsQosServiceClassDirection DocsQosRfMacIfDirection, docsQosServiceClassStorageType StorageType=09 } docsQosServiceClassName OBJECT-TYPE SYNTAX DisplayString (SIZE(2..15)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Service Class Name. DOCSIS specifies that the maximum size is 16 ASCII characters including=20 a terminating zero. The terminating zero is not represented in this DisplayString syntax object. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.3.4" ::=3D { docsQosServiceClassEntry 1 } docsQosServiceClassStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "Used to create or delete rows in this table. There is no restriction on the ability=20 to change values in this row while the row is active.=20 Inactive rows need not be timed out." ::=3D { docsQosServiceClassEntry 2 } docsQosServiceClassPriority OBJECT-TYPE SYNTAX Integer32 (0..7) MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSetPriority." DEFVAL { 0 } ::=3D { docsQosServiceClassEntry 3 } docsQosServiceClassMaxTrafficRate OBJECT-TYPE SYNTAX DocsQosBitRate MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSetMaxTrafficRate." DEFVAL { 0 } ::=3D { docsQosServiceClassEntry 4 } docsQosServiceClassMaxTrafficBurst OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSetMaxTrafficBurst." DEFVAL { 3044 } ::=3D { docsQosServiceClassEntry 5 } docsQosServiceClassMinReservedRate OBJECT-TYPE SYNTAX DocsQosBitRate MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSEtMinReservedRate." DEFVAL { 0 } ::=3D { docsQosServiceClassEntry 6 } docsQosServiceClassMinReservedPkt OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSetMinReservedPkt." ::=3D { docsQosServiceClassEntry 7 } docsQosServiceClassMaxConcatBurst OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSetMaxConcatBurst." DEFVAL { 1522 } ::=3D { docsQosServiceClassEntry 8 } docsQosServiceClassNomPollInterval OBJECT-TYPE SYNTAX Unsigned32=20 UNITS "microseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSetNomPollInterval." DEFVAL { 0 } ::=3D { docsQosServiceClassEntry 9 } docsQosServiceClassTolPollJitter OBJECT-TYPE SYNTAX Unsigned32=20 UNITS "microseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSetTolPollJitter." DEFVAL { 0 } ::=3D { docsQosServiceClassEntry 10 } docsQosServiceClassUnsolicitGrantSize OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSetUnsolicitGrantSize." DEFVAL { 0 } ::=3D { docsQosServiceClassEntry 11 } docsQosServiceClassNomGrantInterval OBJECT-TYPE SYNTAX Unsigned32 UNITS "microseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSetNomGrantInterval." DEFVAL { 0 } ::=3D { docsQosServiceClassEntry 12 } docsQosServiceClassTolGrantJitter OBJECT-TYPE SYNTAX Unsigned32=20 UNITS "microseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSetTolGrantJitter." DEFVAL { 0 } ::=3D { docsQosServiceClassEntry 13 } docsQosServiceClassGrantsPerInterval OBJECT-TYPE SYNTAX Integer32 (0..127) MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSetGrantsPerInterval." DEFVAL { 0 } ::=3D { docsQosServiceClassEntry 14 } docsQosServiceClassMaxLatency OBJECT-TYPE SYNTAX Unsigned32 UNITS "microseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSetClassMaxLatency." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.7.1" DEFVAL { 0 } ::=3D { docsQosServiceClassEntry 15 } docsQosServiceClassActiveTimeout OBJECT-TYPE SYNTAX Integer32 (0..65535) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSetActiveTimeout." DEFVAL { 0 } ::=3D { docsQosServiceClassEntry 16 } docsQosServiceClassAdmittedTimeout OBJECT-TYPE SYNTAX Integer32 (0..65535) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSetAdmittedTimeout." DEFVAL { 200 } ::=3D { docsQosServiceClassEntry 17 } docsQosServiceClassSchedulingType OBJECT-TYPE SYNTAX DocsQosSchedulingType MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSetSchedulingType." DEFVAL { bestEffort } ::=3D { docsQosServiceClassEntry 18 } docsQosServiceClassRequestPolicy OBJECT-TYPE SYNTAX OCTET STRING (SIZE(4)) MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSetRequestPolicyOct." DEFVAL { '00000000'H } -- no bits are set ::=3D { docsQosServiceClassEntry 19 } docsQosServiceClassTosAndMask OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1)) MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSetTosAndMask." DEFVAL { 'FF'H } ::=3D { docsQosServiceClassEntry 20 } docsQosServiceClassTosOrMask OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1)) MAX-ACCESS read-create STATUS current DESCRIPTION "Template for docsQosParamSetTosOrMask." DEFVAL { '00'H } ::=3D { docsQosServiceClassEntry 21 } docsQosServiceClassDirection OBJECT-TYPE SYNTAX DocsQosRfMacIfDirection MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies whether the service class template applies to upstream or downstream service flows." DEFVAL { upstream } ::=3D { docsQosServiceClassEntry 22 } docsQosServiceClassStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This object defines whether this row is kept in volatile storage and lost upon reboot or if this=20 row is backed up by non-volatile or permanent=20 storage. 'permanent' entries need not allow=20 writable access to any object." DEFVAL { nonVolatile } ::=3D { docsQosServiceClassEntry 23 } -- -- Service Class PolicyTable -- docsQosServiceClassPolicyTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsQosServiceClassPolicyEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table describes the set of Docsis-QOS=20 Service Class Policies. =20 This table is an adjunct to the docsDevFilterPolicy table. Entries in=20 docsDevFilterPolicy table can point to=20 specific rows in this table. This table permits mapping a packet to a service class name of an active service flow so long as=20 a classifier does not exist at a higher priority. " REFERENCE "SP-RFIv1.1-I09-020830, Appendix E.2.1" ::=3D { docsQosMIBObjects 9 } =20 docsQosServiceClassPolicyEntry OBJECT-TYPE SYNTAX DocsQosServiceClassPolicyEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A service class name policy entry." INDEX {=20 docsQosServiceClassPolicyIndex=20 } ::=3D { docsQosServiceClassPolicyTable 1 } DocsQosServiceClassPolicyEntry ::=3D SEQUENCE { docsQosServiceClassPolicyIndex Unsigned32, =20 docsQosServiceClassPolicyName DisplayString, docsQosServiceClassPolicyRulePriority Integer32, docsQosServiceClassPolicyStatus RowStatus, docsQosServiceClassPolicyStorageType StorageType =20 } docsQosServiceClassPolicyIndex OBJECT-TYPE SYNTAX Unsigned32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Index value to uniquely identify an entry in this table."=20 ::=3D { docsQosServiceClassPolicyEntry 1 } docsQosServiceClassPolicyName OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-create STATUS current DESCRIPTION "Service Class Name to identify the name of the=20 service class flow to which the packet should be directed."=20 REFERENCE "SP-RFIv1.1-I09-020830, Appendix E.2.1" ::=3D { docsQosServiceClassPolicyEntry 2 } docsQosServiceClassPolicyRulePriority OBJECT-TYPE SYNTAX Integer32 (0..255) MAX-ACCESS read-create STATUS current DESCRIPTION "Service Class Policy rule priority for the entry." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.1.3.5" ::=3D { docsQosServiceClassPolicyEntry 3 } docsQosServiceClassPolicyStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "Used to create or delete rows in this table. This object should not be deleted if it is reference by an entry in docsDevFilterPolicy. The reference should be deleted first. There is no restriction on the ability=20 to change values in this row while the row is active.=20 Inactive rows need not be timed out." ::=3D { docsQosServiceClassPolicyEntry 4 } =09 docsQosServiceClassPolicyStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This object defines whether this row is kept in volatile storage and lost upon reboot or if this=20 row is backed up by non-volatile or permanent=20 storage. 'permanent' entries need not allow=20 writable access to any object." DEFVAL { nonVolatile } ::=3D { docsQosServiceClassPolicyEntry 5 } -- -- Payload Header Suppression(PHS) Table -- docsQosPHSTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsQosPHSEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table describes set of payload header suppression entries." ::=3D { docsQosMIBObjects 10 } =20 docsQosPHSEntry OBJECT-TYPE SYNTAX DocsQosPHSEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A payload header suppression entry. The ifIndex is an ifType of = docsCableMaclayer(127). The index docsQosServiceFlowId selects one service flow from the cable MAC layer interface. The docsQosPktClassId index matches an index of the docsQosPktClassTable. "=20 INDEX {=20 ifIndex,=20 docsQosServiceFlowId, docsQosPktClassId } ::=3D { docsQosPHSTable 1 } DocsQosPHSEntry ::=3D SEQUENCE { docsQosPHSField OCTET STRING, docsQosPHSMask OCTET STRING, docsQosPHSSize Integer32, docsQosPHSVerify TruthValue, docsQosPHSIndex Integer32 } -- docsQosPHSIndex { docsQosPHSEntry 1 } was -- moved to docsQosPHSIndex { docsQosPHSEntry 7 } -- in an ealier revisions of the mib.=20 docsQosPHSField OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..255)) MAX-ACCESS read-only STATUS current DESCRIPTION "Payload header suppression field defines the=20 bytes of the header which must be=20 suppressed/restored by the sending/receiving=20 device. The number of octets in this object should be the same as the value of docsQosPHSSize." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.10.1" ::=3D { docsQosPHSEntry 2 } docsQosPHSMask OBJECT-TYPE SYNTAX OCTET STRING(SIZE(0..32)) MAX-ACCESS read-only STATUS current DESCRIPTION "Payload header suppression mask defines the=20 bit mask which used in combination with the docsQosPHSField defines which bytes in header must be suppressed/restored by the sending or receiving device. Each bit of this bit mask corresponds to a byte in the docsQosPHSField, with the least=20 significant bit corresponding to first byte of the docsQosPHSField. Each bit of the bit mask specifies whether of not the corresponding byte should be suppressed in the packet. A bit value of '1' indicates that the byte should be suppressed by the sending=20 device and restored by the receiving device.=20 A bit value of '0' indicates that=20 the byte should not be suppressed by the sending device or restored by the receiving device. If the bit mask does not contain a bit for each byte in the docsQosPHSField then the bit mask is extended with bit values of '1' to be the necessary length." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.10.3" ::=3D { docsQosPHSEntry 3 } docsQosPHSSize OBJECT-TYPE SYNTAX Integer32 (0..255) MAX-ACCESS read-only STATUS current DESCRIPTION "Payload header suppression size specifies the=20 number of bytes in the header to be suppressed and restored. The value of this object must match the number of bytes in the docsQosPHSField." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.10.4" ::=3D { docsQosPHSEntry 4 } docsQosPHSVerify OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "Payload header suppression verification value of 'true' the sender must verify docsQosPHSField=20 is the same as what is contained in the packet to be suppressed." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.10.5" ::=3D { docsQosPHSEntry 5 } docsQosPHSIndex OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS current DESCRIPTION "Payload header suppression index uniquely=20 references the PHS rule for a given service flow." REFERENCE "SP-RFIv1.1-I09-020830, Appendix C.2.2.10.2" ::=3D { docsQosPHSEntry 6 } -- -- docsQosCmtsMacToSrvFlowTable (CMTS Only) -- docsQosCmtsMacToSrvFlowTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsQosCmtsMacToSrvFlowEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provide for referencing the service = flows=20 associated with a particular cable modem. This = allows=20 for indexing into other docsQos tables that are=20 indexed by docsQosServiceFlowId and ifIndex." ::=3D { docsQosMIBObjects 11 } =20 docsQosCmtsMacToSrvFlowEntry OBJECT-TYPE SYNTAX DocsQosCmtsMacToSrvFlowEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry is created by CMTS for each service flow=20 connected to this CMTS."=20 INDEX {=20 docsQosCmtsCmMac, docsQosCmtsServiceFlowId } ::=3D { docsQosCmtsMacToSrvFlowTable 1 } DocsQosCmtsMacToSrvFlowEntry ::=3D SEQUENCE { =20 docsQosCmtsCmMac MacAddress, docsQosCmtsServiceFlowId Unsigned32, docsQosCmtsIfIndex InterfaceIndex } docsQosCmtsCmMac OBJECT-TYPE SYNTAX MacAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The MAC address for the referenced CM." ::=3D { docsQosCmtsMacToSrvFlowEntry 1 } docsQosCmtsServiceFlowId OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS not-accessible STATUS current DESCRIPTION "An index assigned to a service flow by CMTS." ::=3D { docsQosCmtsMacToSrvFlowEntry 2 } docsQosCmtsIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-only STATUS current DESCRIPTION "The ifIndex of ifType docsCableMacLayter(127)=20 on the CMTS that is connected to the Cable Modem." ::=3D { docsQosCmtsMacToSrvFlowEntry 3 } -- -- Placeholder for notifications/traps. -- docsQosNotification OBJECT IDENTIFIER ::=3D { docsQosMIB 2 } -- -- Conformance definitions -- docsQosConformance OBJECT IDENTIFIER ::=3D { docsQosMIB 3 } docsQosGroups OBJECT IDENTIFIER ::=3D { docsQosConformance 1 } docsQosCompliances OBJECT IDENTIFIER ::=3D { docsQosConformance 2 } docsQosCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for MCNS Cable Modems and Cable Modem Termination Systems that implement DOCSIS Service Flows." MODULE -- docsQosMIB MANDATORY-GROUPS { docsQosBaseGroup } GROUP docsQosCmtsGroup DESCRIPTION "This group is mandatory for only Cable Modem Termination Systems (CMTS) and not implemented for Cable Modems." GROUP docsQosParamSetGroup DESCRIPTION "This group is mandatory for Cable Modem Termination Systems (CMTS) and Cable Modems. Cable modems only = implement objects in this group as read-only." GROUP docsQosSrvClassPolicyGroup DESCRIPTION "This group is optional for Cable Modem Termination Systems (CMTS) and Cable Modems. This group only needs to=20 be implement if policy based service flow classification is implemented. See docsDevPolicyTable in DOCS-CABLE-DEVICE-MIB for more details. " GROUP docsQosServiceClassGroup DESCRIPTION "The docsQosServiceClassTable group of objects." =20 OBJECT docsQosPktClassPkts DESCRIPTION "This object only needs to be implemented in entries that are classifying packets and not policing packets." OBJECT docsQosPktClassInetAddressType SYNTAX InetAddressType { ipv4(1) } DESCRIPTION "An implementation is only required to support IPv4 address." OBJECT docsQosPktClassInetSourceAddr SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 address." =09 OBJECT docsQosPktClassInetSourceMask SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 address."=20 =20 OBJECT docsQosPktClassInetDestAddr SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 address." =20 OBJECT docsQosPktClassInetDestMask SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 address." OBJECT docsQosServiceClassStorageType SYNTAX StorageType { nonVolatile(3) } DESCRIPTION "An implementation is only required to support nonvolatile storage." =09 OBJECT docsQosServiceClassPolicyStorageType SYNTAX StorageType { nonVolatile(3) } DESCRIPTION "An implementation is only required to support nonvolatile storage." ::=3D { docsQosCompliances 1 } docsQosBaseGroup OBJECT-GROUP OBJECTS { docsQosPktClassDirection, docsQosPktClassPriority, docsQosPktClassIpTosLow, docsQosPktClassIpTosHigh, docsQosPktClassIpTosMask, docsQosPktClassIpProtocol, docsQosPktClassSourcePortStart, docsQosPktClassSourcePortEnd, docsQosPktClassDestPortStart, docsQosPktClassDestPortEnd, docsQosPktClassDestMacAddr, docsQosPktClassDestMacMask, docsQosPktClassSourceMacAddr, docsQosPktClassEnetProtocolType, docsQosPktClassEnetProtocol, docsQosPktClassUserPriLow, docsQosPktClassUserPriHigh, docsQosPktClassVlanId, docsQosPktClassStateActive, docsQosPktClassPkts, docsQosPktClassBitMap, docsQosPktClassInetAddressType, docsQosPktClassInetSourceAddr, docsQosPktClassInetSourceMask, docsQosPktClassInetDestAddr, docsQosPktClassInetDestMask, docsQosServiceFlowSID, docsQosServiceFlowDirection, docsQosServiceFlowPrimary,=20 docsQosServiceFlowPkts, -- not sure if CM should implement docsQosServiceFlowOctets, docsQosServiceFlowTimeCreated, docsQosServiceFlowTimeActive, docsQosServiceFlowPHSUnknowns, docsQosServiceFlowPolicedDropPkts, docsQosServiceFlowPolicedDelayPkts,=09 docsQosDSAReqs, docsQosDSARsps, docsQosDSAAcks, docsQosDSCReqs, docsQosDSCRsps, docsQosDSCAcks, docsQosDSDReqs, docsQosDSDRsps, docsQosDynamicAdds, docsQosDynamicAddFails, docsQosDynamicChanges, docsQosDynamicChangeFails, docsQosDynamicDeletes, docsQosDynamicDeleteFails, docsQosDCCReqs, docsQosDCCRsps, docsQosDCCAcks, docsQosDCCs, docsQosDCCFails, docsQosPHSField, docsQosPHSMask, docsQosPHSSize, docsQosPHSVerify,=20 docsQosPHSIndex } STATUS current DESCRIPTION "Group of objects implemented in both Cable Modems and=20 Cable Modem Termination Systems." ::=3D { docsQosGroups 1 } docsQosParamSetGroup OBJECT-GROUP OBJECTS { docsQosParamSetServiceClassName, docsQosParamSetPriority, docsQosParamSetMaxTrafficRate, docsQosParamSetMaxTrafficBurst, docsQosParamSetMinReservedRate, docsQosParamSetMinReservedPkt, docsQosParamSetActiveTimeout, docsQosParamSetAdmittedTimeout, docsQosParamSetMaxConcatBurst, docsQosParamSetSchedulingType, docsQosParamSetNomPollInterval, docsQosParamSetTolPollJitter, docsQosParamSetUnsolicitGrantSize, docsQosParamSetNomGrantInterval, docsQosParamSetTolGrantJitter, docsQosParamSetGrantsPerInterval, docsQosParamSetTosAndMask, docsQosParamSetTosOrMask, docsQosParamSetMaxLatency, docsQosParamSetRequestPolicyOct, docsQosParamSetBitMap } STATUS current DESCRIPTION "Group of objects implemenented in both Cable Modems and=20 Cable Modem Termination Systems for QOS parameter sets." ::=3D { docsQosGroups 2 } docsQosCmtsGroup OBJECT-GROUP OBJECTS { docsQosUpstreamFragments, docsQosUpstreamFragDiscards, docsQosUpstreamConcatBursts, docsQosServiceFlowLogIfIndex, =20 docsQosServiceFlowLogSFID, docsQosServiceFlowLogCmMac, docsQosServiceFlowLogPkts, docsQosServiceFlowLogOctets,=20 docsQosServiceFlowLogTimeDeleted, =20 docsQosServiceFlowLogTimeCreated, docsQosServiceFlowLogTimeActive, docsQosServiceFlowLogDirection, docsQosServiceFlowLogPrimary, docsQosServiceFlowLogServiceClassName, docsQosServiceFlowLogPolicedDropPkts, docsQosServiceFlowLogPolicedDelayPkts, docsQosServiceFlowLogControl, docsQosCmtsIfIndex -- docsQosCmtsMacToSrvFlowTable required } STATUS current DESCRIPTION "Mandatory group of objects implemented only in the CMTS." ::=3D { docsQosGroups 3 } docsQosSrvClassPolicyGroup OBJECT-GROUP OBJECTS { docsQosServiceClassPolicyName, docsQosServiceClassPolicyRulePriority, docsQosServiceClassPolicyStatus, docsQosServiceClassPolicyStorageType } STATUS current DESCRIPTION "Group of objects implemented in both Cable Modems and=20 Cable Modem Termination Systems when supporting policy based service flows." ::=3D { docsQosGroups 4 } docsQosServiceClassGroup OBJECT-GROUP OBJECTS { docsQosServiceClassStatus, docsQosServiceClassPriority, docsQosServiceClassMaxTrafficRate, docsQosServiceClassMaxTrafficBurst, docsQosServiceClassMinReservedRate, docsQosServiceClassMinReservedPkt, docsQosServiceClassMaxConcatBurst, docsQosServiceClassNomPollInterval, docsQosServiceClassTolPollJitter, docsQosServiceClassUnsolicitGrantSize, docsQosServiceClassNomGrantInterval, docsQosServiceClassTolGrantJitter, docsQosServiceClassGrantsPerInterval, docsQosServiceClassMaxLatency, docsQosServiceClassActiveTimeout, docsQosServiceClassAdmittedTimeout, docsQosServiceClassSchedulingType, docsQosServiceClassRequestPolicy, docsQosServiceClassTosAndMask, docsQosServiceClassTosOrMask, docsQosServiceClassDirection, docsQosServiceClassStorageType } STATUS current DESCRIPTION "The docsQosServiceClassTable objects. If a CMTS implements expansion of Service Class Names in a QOS Parameter Set, this group is mandatory on the CMTS. If the CMTS does not support Service Class Names, this group may be unimplemented in the CMTS. This group is not implemented on the CM. " ::=3D { docsQosGroups 5 } END ------_=_NextPart_000_01C2DC55.4830A0B4-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Mon Feb 24 21:55:33 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04292 for ; Mon, 24 Feb 2003 21:55:33 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1P34M211975 for ipcdn-archive@odin.ietf.org; Mon, 24 Feb 2003 22:04:22 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1P34Bp11955; Mon, 24 Feb 2003 22:04:11 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1P33Wp11927 for ; Mon, 24 Feb 2003 22:03:32 -0500 Received: from snowmass.tci.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04274 for ; Mon, 24 Feb 2003 21:54:12 -0500 (EST) Received: from mms02-relaya.tci.com (mms02-relaya.broadband.att.com [147.191.89.206]) by snowmass.tci.com (8.12.2/8.12.2) with ESMTP id h1P2w384010695; Mon, 24 Feb 2003 19:58:03 -0700 (MST) Received: from 147.191.89.203 by mms02-RelayB.tci.com with ESMTP ( Tumbleweed MMS SMTP Relay (MMS v5.5.0)); Mon, 24 Feb 2003 19:57:56 -0600 Received: by entexchimc01.broadband.att.com with Internet Mail Service ( 5.5.2653.19) id ; Mon, 24 Feb 2003 19:58:34 -0700 Message-ID: <6732623D2548D61193C90002A5C88DCC05663725@entmaexch02.broadband.att.com> From: "Woundy, Richard" To: "IPCDN WG (E-mail)" cc: "Jean-Francois Mule (E-mail)" , "Woundy, Richard" Date: Mon, 24 Feb 2003 19:57:47 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) X-WSS-ID: 1244043E156743-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [ipcdn] FW: Internet-Draft Cutoff Dates for San Francisco, CA (March 16-2 1, 2003) Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Folks, Just a reminder that the official internet-draft cutoff for existing drafts is March 3rd, 2003 at 09:00 ET. For many folks, that implies that the cut-off date is this Friday. I am hoping that we will be able to discuss the PacketCable/IPCableCom MIBs in San Francisco. Note: I made many updates to the www.ipcdn.org website today. New meeting materials have been posted , internet-drafts and their status have been updated , and new MIB review guidelines have been linked . -- Rich -----Original Message----- From: Internet-Drafts Administrator [mailto:internet-drafts@ietf.org] Sent: Friday, February 21, 2003 8:42 AM Subject: Internet-Draft Cutoff Dates for San Francisco, CA (March 16-21, 2003) NOTE: There are two (2) Internet-Draft Cutoff dates February 24th: Cutoff for Initial Submissions (new documents) All initial submissions(-00) must be submitted by Monday, February 24th, at 09:00 ET. Initial submissions received after this time will NOT be made available in the Internet-Drafts directory, and will have to be resubmitted. As before, all initial submissions (-00.txt) with a filename beginning with a draft-ietf MUST be approved by the appropriate WG Chair prior to processing and announcing. WG Chair approval must be received by Monday, February 24th. Please do NOT wait until the last minute to submit. Be advised: NO placeholders. Updates to initial submissions received the week of February 24th will NOT be accepted. March 3rd: FINAL Internet-Draft Cutoff All revised Internet-Draft submissions must be submitted by Monday, March 3rd, 2003 at 09:00 ET. Internet-Drafts received after this time will NOT be announced NOR made available in the Internet-Drafts Directories. We will begin accepting Internet-Draft submissions the week of the meeting, though announcements will NOT be sent until the IETF meeting is over. Thank you for your understanding and cooperation. Please do not hesitate to contact us if you have any questions or concenrs. FYI: These and other significant dates can be found at http://www.ietf.org/meetings/cutoff_dates_56.html _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Wed Feb 26 08:27:19 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03629 for ; Wed, 26 Feb 2003 08:27:19 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1QDaZh07870 for ipcdn-archive@odin.ietf.org; Wed, 26 Feb 2003 08:36:35 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QDaSp07855; Wed, 26 Feb 2003 08:36:28 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QDZwp07834 for ; Wed, 26 Feb 2003 08:35:58 -0500 Received: from titan.arrisi.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03606; Wed, 26 Feb 2003 08:25:56 -0500 (EST) From: Wilson.Sawyer@arrisi.com Subject: RE: [ipcdn] RE: Tos field - SubMgt and other IPCDN MIBs To: ipcdn@ietf.org Cc: bwijnen@lucent.com, "Erik Nordmark (E-mail)" , ipcdn-admin@ietf.org, "Thomas Narten (E-mail)" X-Mailer: Lotus Notes Release 5.0.9 November 16, 2001 Message-ID: Date: Wed, 26 Feb 2003 08:28:25 -0500 X-MIMETrack: Serialize by Router on Titan/Arris(Release 5.0.9a |January 7, 2002) at 02/26/2003 08:29:30 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Colleagues: Page 3 of RFC 3260 seems to consign the last remnants of "TOS byte" to the dustbin of history. Consequently, per Erik & Bert's point, I'm proposing to change docsSubMgtPktFilterTosValue and docsSubMgtPktFilterTosMask from type OCTET STRING (SIZE(1)) to be: docsSubMgtPktFilterDscpValue SYNTAX Dscp -- 0..63 RFC 3289: DIFFSERV-DSCP-TC docsSubMgtPktFilterDscpMask SYNTAX Dscp That is, these are now 6-bit fields instead of 8 bits. The Mask is a slight misuse of the 'Dscp' Textual Convention, but I think it's intuitive enough. For consistency across IPCDN, there are several other MIBs which may want to consider similar changes: Docsis device MIB: docsDevFilterIpTos/Mask, docsDevFilterTosTable, ... QoS MIB docsQosPktClassIpTosLow docsQosPktClassIpTosHigh docsQosPktClassIpTosMask PacketCable event management MTA MIB (introduced in glossary; doesn't appear to be used) PacketCable Signaling MIB pktcSigDefCallSigTos pktcSigDefMediaStreamTos (I didn't look at the cablehome mibs) Comments? Suggestions? - Wilson _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From mailnull@www1.ietf.org Wed Feb 26 15:56:56 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24896 for ; Wed, 26 Feb 2003 15:56:55 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1QL6Zv09969 for ipcdn-archive@odin.ietf.org; Wed, 26 Feb 2003 16:06:35 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QL6Yp09961; Wed, 26 Feb 2003 16:06:34 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1QL5pp09878 for ; Wed, 26 Feb 2003 16:05:51 -0500 Received: from peacock.tci.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24844 for ; Wed, 26 Feb 2003 15:55:40 -0500 (EST) Received: from mms01-relayb.tci.com (mms01-relayb.broadband.att.com [147.191.90.1]) by peacock.tci.com (8.12.2/8.12.2) with ESMTP id h1QKxVJD005282 for ; Wed, 26 Feb 2003 13:59:31 -0700 (MST) Received: from 147.191.89.203 by mms01-relayb.tci.com with ESMTP ( Tumbleweed MMS SMTP Relay (MMS v5.5.0)); Wed, 26 Feb 2003 13:59:22 -0600 Received: by entexchimc01.broadband.att.com with Internet Mail Service ( 5.5.2653.19) id ; Wed, 26 Feb 2003 14:00:02 -0700 Message-ID: <6732623D2548D61193C90002A5C88DCC05663733@entmaexch02.broadband.att.com> From: "Woundy, Richard" To: "IPCDN WG (E-mail)" Date: Wed, 26 Feb 2003 13:59:18 -0700 Importance: high X-Priority: 1 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) X-WSS-ID: 1243F52091908-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [ipcdn] FW: 56th IETF - Agenda Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP over Cable Data Network List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit The IPCDN working group will be meeting at the IETF in San Francisco on March 19th, between 1-3PM PT. See . We should focus on finishing the DOCSIS MIBs, and reviewing the PacketCable MIBs. Note that the deadline for submitting drafts for this IETF meeting is March 3rd at 9AM ET. For some folks, the effective deadline is this weekend. -- Rich Agenda of the Fifty-sixth IETF March 16-21, 2003 WEDNESDAY, March 19, 2003 ... 1300-1500 Afternoon Sessions I INT ipcdn IP over Cable Data Network WG INT magma Multicast & Anycast Group Membership WG OPS aaa Authentication, Authorization and Accounting WG SEC inch Extended Incident Handling WG SUB ppvpn Provider Provisioned Virtual Private Networks WG TSV avt Audio/Video Transport WG TSV ieprep Internet Emergency Preparedness WG _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn