From ipcdn-admin@ietf.org Mon May 1 17:20:29 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06763 for ; Mon, 1 May 2000 17:20:27 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA03688 for ; Mon, 1 May 2000 17:20:28 -0400 (EDT) Date: Mon, 1 May 2000 17:20:28 -0400 (EDT) Message-Id: <200005012120.RAA03688@optimus.ietf.org> From: ipcdn-admin@ietf.org Subject: Welcome To "IPCDN"! To: ipcdn-archive@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network Welcome to the IPCDN@ietf.org mailing list! Welcome to the relocated IPCDN mailing list. Please use ipcdn@ietf.org for all future postings. The ipcdn@terayon.com will be discontinued effective 1 June 2000. To post to this list, send your email to: ipcdn@ietf.org General information about the mailing list is at: http://www1.ietf.org/mailman/listinfo/ipcdn If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at: http://www1.ietf.org/mailman/options/ipcdn/ipcdn-archive@lists.ietf.org You can also make such adjustments via email by sending a message to: IPCDN-request@ietf.org with the word `help' in the subject or body (don't include the quotes), and you will get back a message with instructions. You must know your password to change your options (including changing the password, itself) or to unsubscribe. It is: BtQa If you forget your password, don't worry, you will receive a monthly reminder telling you what all your ietf.org mailing list passwords are, and how to unsubscribe or change your options. There is also a button on your options page that will email your current password to you. You may also have your password mailed to you automatically off of the Web page noted above. From ipcdn-admin@ietf.org Mon May 1 17:30:51 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06954; Mon, 1 May 2000 17:30:51 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA04128; Mon, 1 May 2000 17:30:01 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA04091 for ; Mon, 1 May 2000 17:29:59 -0400 (EDT) Received: from zipcode.corp.home.net (zipcode.corp.home.net [24.0.26.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06925 for ; Mon, 1 May 2000 17:29:56 -0400 (EDT) Received: from lock.eos.home.net (root@lock.eos.home.net [24.0.16.84]) by zipcode.corp.home.net (8.9.3/8.9.3) with ESMTP id OAA27740; Mon, 1 May 2000 14:29:52 -0700 (PDT) Received: from lock.eos.home.net (stjohns@localhost [127.0.0.1]) by lock.eos.home.net (8.9.1/8.8.5) with ESMTP id OAA00897; Mon, 1 May 2000 14:29:50 -0700 (PDT) Message-Id: <200005012129.OAA00897@lock.eos.home.net> X-Mailer: exmh version 2.0delta 6/3/97 To: ipcdn@terayon.com cc: ipcdn@ietf.org Reply-to: ipcdn@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 01 May 2000 14:29:48 -0700 From: "Mike StJohns" Subject: [ipcdn] List moved Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org Effective 1 May, the IPCDN mailing list has moved from ipcdn@terayon.com to ipcdn@ietf.org. The ipcdn@terayon.com mailing list will be discontinued 1 June. Everyone who had subscribed to the IPCDN mailing list as of 1400PDT on 1 May has been moved over to the new list. Please remember to edit your replys and posts to point to the new list. Thanks - Mike _______________________________________________ IPCDN mailing list IPCDN@ietf.org http://www1.ietf.org/mailman/listinfo/ipcdn From owner-ipcdn@terayon.com Mon May 1 17:39:39 2000 Received: from www.terayon.com (terayon.com [157.22.250.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07115 for ; Mon, 1 May 2000 17:39:38 -0400 (EDT) Received: from redpine.terayon.com (redpine [157.22.250.5]) by www.terayon.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id OAA21381; Mon, 1 May 2000 14:32:47 -0700 (PDT) Received: from mail-serv.terayon.com by redpine.terayon.com via smtpd (for mails.terayon.com [157.22.250.1]) with SMTP; 1 May 2000 21:32:47 UT Received: from tamarind.terayon.com (tamarind.terayon.com [172.20.0.6]) by mail-serv.terayon.com (8.9.3+Sun/8.9.1) with ESMTP id OAA05754; Mon, 1 May 2000 14:32:45 -0700 (PDT) Received: (from root@localhost) by tamarind.terayon.com (8.8.8+Sun/8.8.8) id OAA14008 for ipcdn-outgoing; Mon, 1 May 2000 14:29:42 -0700 (PDT) Message-Id: <200005012129.OAA00897@lock.eos.home.net> X-Mailer: exmh version 2.0delta 6/3/97 To: ipcdn@terayon.com cc: ipcdn@ietf.org Subject: List moved Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 01 May 2000 14:29:48 -0700 From: "Mike StJohns" Sender: owner-ipcdn@terayon.com Precedence: bulk Reply-To: ipcdn@terayon.com Effective 1 May, the IPCDN mailing list has moved from ipcdn@terayon.com to ipcdn@ietf.org. The ipcdn@terayon.com mailing list will be discontinued 1 June. Everyone who had subscribed to the IPCDN mailing list as of 1400PDT on 1 May has been moved over to the new list. Please remember to edit your replys and posts to point to the new list. Thanks - Mike From ipcdn-admin@ietf.org Wed May 10 11:41:59 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28257; Wed, 10 May 2000 11:41:59 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA05917; Wed, 10 May 2000 11:32:31 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA05889 for ; Wed, 10 May 2000 11:32:29 -0400 (EDT) Received: from ftpbox.mot.com (ftpbox.mot.com [129.188.136.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27996 for ; Wed, 10 May 2000 11:32:28 -0400 (EDT) Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by ftpbox.mot.com (ftpbox 2.1) with ESMTP id IAA06884; Wed, 10 May 2000 08:32:25 -0700 (MST)] Received: [from noah.dma.isg.mot.com (noah.dma.isg.mot.com [150.21.2.29]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id IAA20358; Wed, 10 May 2000 08:32:20 -0700 (MST)] Received: from dma.isg.mot.com (mackerel.dma.isg.mot.com [150.21.17.44]) by noah.dma.isg.mot.com (8.8.8+Sun/8.8.8) with ESMTP id LAA12160; Wed, 10 May 2000 11:32:19 -0400 (EDT) Message-Id: <200005101532.LAA12160@noah.dma.isg.mot.com> To: Yost William cc: ljh031@dma.isg.mot.com, ipcdn@ietf.org In-reply-to: Your message of "Tue, 09 May 2000 16:51:49 EDT." <4FA371B64BDAD2119CF40008C7D9ADB302B96D0D@indyexch5.indy.tce.com> Date: Wed, 10 May 2000 11:32:18 -0400 From: "Michael W. Patrick" Subject: [ipcdn] Re: Bit ordering for docsQosParamSetRequestPolicy in QOS-MIB Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org Bill, Yuck. As it stands now, it looks like implementors will have to reverse and shift the bit orders of a binary request policy (lsb=bit 0) when reporting the mib docsQosParamSetRequestPolicy(msb=bit 0). This certainly was not what I intended. My question is, would it be too confusing at this late date to update the MIB to match the implementation, (e.g. by changing docsQosParamSetRequestPolicy to be an integer), or should we leave the qos mib as-is and force the bit swap & shift? -mike >>>>> "Yost" == Yost William writes: > The bit numbering of these bits is the same (as far as bit numbers > go) in the QOS-MIB and the RFI Spec (SP-RFIv1.1-I04-000407), but the > bit ordering is reversed. SNMP defines bit 0 as the most > significant bit in BITS, but the RFI Spec, in section C.2.2.6.3 > defines bit 0 as the LSB of the value field. I assume this is what > you intended, but I just wanted to double check. > Here is a copy of the MIB element definition. > docsQosParamSetRequestPolicy OBJECT-TYPE SYNTAX BITS > { broadcastReqOpp (0), priorityReqMulticastReq (1), reqDataForReq > (2), reqDataForData (3), piggybackReqWithData (4), concatenateData > (5), fragmentData (6), supressPayloadHeaders (7), > dropPktsExceedUGSize (8) } > --- William H. Yost, Thomson Consumer Electronics: (317) 587-4816 > --- . Home of RCA, Proscan, GE electronics . _______________________________________________ IPCDN mailing list IPCDN@ietf.org http://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Wed May 10 11:54:34 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28651; Wed, 10 May 2000 11:54:33 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA06191; Wed, 10 May 2000 11:45:19 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA06166 for ; Wed, 10 May 2000 11:45:17 -0400 (EDT) Received: from dmzraw1.extranet.tce.com (dmzraw1.extranet.tce.com [157.254.234.131]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28348 for ; Wed, 10 May 2000 11:45:15 -0400 (EDT) Received: from smtprelay.tce.com ([157.254.96.114]) by dmzraw1.extranet.tce.com (8.9.3/8.9.1) with ESMTP id KAA25723; Wed, 10 May 2000 10:44:37 -0500 (EST) Received: from indyexch1.indy.tce.com (localhost [127.0.0.1]) by smtprelay.tce.com (8.9.3/8.9.1) with ESMTP id KAA14977; Wed, 10 May 2000 10:44:36 -0500 (EST) Received: by indyexch1.indy.tce.com with Internet Mail Service (5.5.2650.21) id ; Wed, 10 May 2000 10:45:38 -0500 Message-ID: <4FA371B64BDAD2119CF40008C7D9ADB302B96D13@indyexch5.indy.tce.com> From: Yost William To: "'Michael W. Patrick'" Cc: ljh031@dma.isg.mot.com, ipcdn@ietf.org Date: Wed, 10 May 2000 10:45:16 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Subject: [ipcdn] RE: Bit ordering for docsQosParamSetRequestPolicy in QOS-MIB Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org I think the MIB should be changed so it is an Unsigned32 syntax. That would prevent it from being printed as a negative number by some management program. Either that, or an OCTET STRING (SIZE(4)). If you make it an octet string, a management program will probably print it in Hex which is kind of what you want. The octet string is equivalent to the BITS, as far as the SNMP protocol is concerned, so that would be the minimal impact of a change to make I think. It just avoids the built in definition that BITS has of bit 0 being most significant. If you don't change the MIB, I think there is going to be a continuing confusion about what bit means what. --- William H. Yost, Thomson Consumer Electronics: (317) 587-4816 --- . Home of RCA, Proscan, GE electronics . -----Original Message----- From: Michael W. Patrick [mailto:mpatrick@dma.isg.mot.com] Sent: Wednesday, May 10, 2000 10:32 AM To: Yost William Cc: ljh031@dma.isg.mot.com; ipcdn@ietf.org Subject: Re: Bit ordering for docsQosParamSetRequestPolicy in QOS-MIB Bill, Yuck. As it stands now, it looks like implementors will have to reverse and shift the bit orders of a binary request policy (lsb=bit 0) when reporting the mib docsQosParamSetRequestPolicy(msb=bit 0). This certainly was not what I intended. My question is, would it be too confusing at this late date to update the MIB to match the implementation, (e.g. by changing docsQosParamSetRequestPolicy to be an integer), or should we leave the qos mib as-is and force the bit swap & shift? -mike >>>>> "Yost" == Yost William writes: > The bit numbering of these bits is the same (as far as bit numbers > go) in the QOS-MIB and the RFI Spec (SP-RFIv1.1-I04-000407), but the > bit ordering is reversed. SNMP defines bit 0 as the most > significant bit in BITS, but the RFI Spec, in section C.2.2.6.3 > defines bit 0 as the LSB of the value field. I assume this is what > you intended, but I just wanted to double check. > Here is a copy of the MIB element definition. > docsQosParamSetRequestPolicy OBJECT-TYPE SYNTAX BITS > { broadcastReqOpp (0), priorityReqMulticastReq (1), reqDataForReq > (2), reqDataForData (3), piggybackReqWithData (4), concatenateData > (5), fragmentData (6), supressPayloadHeaders (7), > dropPktsExceedUGSize (8) } > --- William H. Yost, Thomson Consumer Electronics: (317) 587-4816 > --- . Home of RCA, Proscan, GE electronics . _______________________________________________ IPCDN mailing list IPCDN@ietf.org http://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Thu May 11 12:59:05 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03054; Thu, 11 May 2000 12:59:04 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA26601; Thu, 11 May 2000 12:56:26 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA26570 for ; Thu, 11 May 2000 12:56:24 -0400 (EDT) Received: from zipcode.corp.home.net (zipcode.corp.home.net [24.0.26.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02940 for ; Thu, 11 May 2000 12:56:22 -0400 (EDT) Received: from key.corp.home.net (key.eos.home.net [24.0.16.83]) by zipcode.corp.home.net (8.9.3/8.9.3) with ESMTP id JAA07107; Thu, 11 May 2000 09:56:10 -0700 (PDT) Message-Id: <4.3.1.2.20000511094836.00cc4700@poptart> X-Sender: stjohns@poptart X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Thu, 11 May 2000 09:54:37 -0700 To: "Michael W. Patrick" , Yost William From: "Mike St. Johns" Subject: Re: [ipcdn] Re: Bit ordering for docsQosParamSetRequestPolicy in QOS-MIB Cc: ljh031@dma.isg.mot.com, ipcdn@ietf.org In-Reply-To: <200005101532.LAA12160@noah.dma.isg.mot.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org Guys - Your confusing the MIB with the implementation - again. The MIB is an abstraction of how things work underneath. the BITS construct just maps a set of true/false values into an underlying construct that can get transmitted across the network. At the agent end, ignore the bit position and concentrate on the bit meaning. In other words, if the suppressPayloadHeaders bit is set in this , do whatever you would normally do for suppressPayloadHeaders. If that's setting the corresponding bit in a MAC request, then so be it, but these things ARE NOT LINKED except by the name's meaning - the assignment of the actual bit position is a transport mapping, nothing more and must not be too closely tied to some other field. We had this same discussion in packet cable on the syslog level meanings of the docsDevEvent priority levels. At 08:32 AM 5/10/00, Michael W. Patrick wrote: >Bill, > >Yuck. As it stands now, it looks like implementors will have >to reverse and shift the bit orders of a binary request policy (lsb=bit 0) >when reporting the mib docsQosParamSetRequestPolicy(msb=bit 0). > >This certainly was not what I intended. > >My question is, would it be too confusing at this late date >to update the MIB to match the implementation, >(e.g. by changing docsQosParamSetRequestPolicy to be an integer), >or should we leave the qos mib as-is and force the bit swap & shift? > >-mike > > > >>>>> "Yost" == Yost William writes: > > > > The bit numbering of these bits is the same (as far as bit numbers > > go) in the QOS-MIB and the RFI Spec (SP-RFIv1.1-I04-000407), but the > > bit ordering is reversed. SNMP defines bit 0 as the most > > significant bit in BITS, but the RFI Spec, in section C.2.2.6.3 > > defines bit 0 as the LSB of the value field. I assume this is what > > you intended, but I just wanted to double check. > > > Here is a copy of the MIB element definition. > > > docsQosParamSetRequestPolicy OBJECT-TYPE SYNTAX BITS > > { broadcastReqOpp (0), priorityReqMulticastReq (1), reqDataForReq > > (2), reqDataForData (3), piggybackReqWithData (4), concatenateData > > (5), fragmentData (6), supressPayloadHeaders (7), > > dropPktsExceedUGSize (8) } > > > --- William H. Yost, Thomson Consumer Electronics: (317) 587-4816 > > --- . Home of RCA, Proscan, GE electronics . > > >_______________________________________________ >IPCDN mailing list >IPCDN@ietf.org >http://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ IPCDN mailing list IPCDN@ietf.org http://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Thu May 11 15:13:49 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06284; Thu, 11 May 2000 15:13:49 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA28519; Thu, 11 May 2000 15:10:55 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA28491 for ; Thu, 11 May 2000 15:10:53 -0400 (EDT) Received: from dmzraw1.extranet.tce.com (dmzraw1.extranet.tce.com [157.254.234.131]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06258 for ; Thu, 11 May 2000 15:10:50 -0400 (EDT) Received: from smtprelay.tce.com ([157.254.96.114]) by dmzraw1.extranet.tce.com (8.9.3/8.9.1) with ESMTP id OAA26153; Thu, 11 May 2000 14:10:16 -0500 (EST) Received: from indyexch1.indy.tce.com (localhost [127.0.0.1]) by smtprelay.tce.com (8.9.3/8.9.1) with ESMTP id OAA22345; Thu, 11 May 2000 14:10:15 -0500 (EST) Received: by indyexch1.indy.tce.com with Internet Mail Service (5.5.2650.21) id ; Thu, 11 May 2000 14:11:26 -0500 Message-ID: <4FA371B64BDAD2119CF40008C7D9ADB302B96D27@indyexch5.indy.tce.com> From: Yost William To: "'Mike St. Johns'" , "Michael W. Patrick" Cc: ljh031@dma.isg.mot.com, ipcdn@ietf.org Subject: RE: [ipcdn] Re: Bit ordering for docsQosParamSetRequestPolicy in QOS-MIB Date: Thu, 11 May 2000 14:11:03 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org I agree if no one ever looked at the data inside the modem, but just looked at a manager which properly displayed the BITS element as a set of enumerated bit values, you would have no problem. But some managers will only show the value as an octet string in hex and you will be looking at a dump of the configuration file and comparing it to what you see in SNMP and there will be an opportunity for misuderstanding where there needn't be. What Mike said below is still true, the agent will have to swap the bits in the word before returning it in an SNMP reply. People make mistakes, and this is just one more place that some implementations may swap the bits and some may not. --- William H. Yost, Thomson Consumer Electronics: (317) 587-4816 --- . Home of RCA, Proscan, GE electronics . -----Original Message----- From: Mike St. Johns [mailto:stjohns@corp.home.net] Sent: Thursday, May 11, 2000 11:55 AM To: Michael W. Patrick; Yost William Cc: ljh031@dma.isg.mot.com; ipcdn@ietf.org Subject: Re: [ipcdn] Re: Bit ordering for docsQosParamSetRequestPolicy in QOS-MIB Guys - Your confusing the MIB with the implementation - again. The MIB is an abstraction of how things work underneath. the BITS construct just maps a set of true/false values into an underlying construct that can get transmitted across the network. At the agent end, ignore the bit position and concentrate on the bit meaning. In other words, if the suppressPayloadHeaders bit is set in this , do whatever you would normally do for suppressPayloadHeaders. If that's setting the corresponding bit in a MAC request, then so be it, but these things ARE NOT LINKED except by the name's meaning - the assignment of the actual bit position is a transport mapping, nothing more and must not be too closely tied to some other field. We had this same discussion in packet cable on the syslog level meanings of the docsDevEvent priority levels. At 08:32 AM 5/10/00, Michael W. Patrick wrote: >Bill, > >Yuck. As it stands now, it looks like implementors will have >to reverse and shift the bit orders of a binary request policy (lsb=bit 0) >when reporting the mib docsQosParamSetRequestPolicy(msb=bit 0). > >This certainly was not what I intended. > >My question is, would it be too confusing at this late date >to update the MIB to match the implementation, >(e.g. by changing docsQosParamSetRequestPolicy to be an integer), >or should we leave the qos mib as-is and force the bit swap & shift? > >-mike > > > >>>>> "Yost" == Yost William writes: > > > > The bit numbering of these bits is the same (as far as bit numbers > > go) in the QOS-MIB and the RFI Spec (SP-RFIv1.1-I04-000407), but the > > bit ordering is reversed. SNMP defines bit 0 as the most > > significant bit in BITS, but the RFI Spec, in section C.2.2.6.3 > > defines bit 0 as the LSB of the value field. I assume this is what > > you intended, but I just wanted to double check. > > > Here is a copy of the MIB element definition. > > > docsQosParamSetRequestPolicy OBJECT-TYPE SYNTAX BITS > > { broadcastReqOpp (0), priorityReqMulticastReq (1), reqDataForReq > > (2), reqDataForData (3), piggybackReqWithData (4), concatenateData > > (5), fragmentData (6), supressPayloadHeaders (7), > > dropPktsExceedUGSize (8) } > > > --- William H. Yost, Thomson Consumer Electronics: (317) 587-4816 > > --- . Home of RCA, Proscan, GE electronics . > > >_______________________________________________ >IPCDN mailing list >IPCDN@ietf.org >http://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ IPCDN mailing list IPCDN@ietf.org http://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Sat May 13 22:37:42 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15899; Sat, 13 May 2000 22:37:42 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA09093; Sat, 13 May 2000 22:36:10 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA09065 for ; Sat, 13 May 2000 22:36:08 -0400 (EDT) Received: from motgate.mot.com (motgate.mot.com [129.188.136.100]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15885 for ; Sat, 13 May 2000 22:36:10 -0400 (EDT) Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate.mot.com (motgate 2.1) with ESMTP id TAA02084 for ; Sat, 13 May 2000 19:36:11 -0700 (MST)] Received: [from noah.dma.isg.mot.com (noah.dma.isg.mot.com [150.21.2.29]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id TAA23349 for ; Sat, 13 May 2000 19:36:11 -0700 (MST)] Received: from dma.isg.mot.com (cabs1.dma.isg.mot.com [150.21.2.34]) by noah.dma.isg.mot.com (8.8.8+Sun/8.8.8) with ESMTP id WAA26716 for ; Sat, 13 May 2000 22:36:10 -0400 (EDT) Message-Id: <200005140236.WAA26716@noah.dma.isg.mot.com> To: ipcdn@ietf.org Subject: Yost William: RE: [ipcdn] Re: Bit ordering for docsQosParamSetRequestPolicy in QOS-MIB Date: Sat, 13 May 2000 22:36:09 -0400 From: "Michael W. Patrick" Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org OK, can I have a straw poll of Docsis vendors please? Do you vote 1) Keep DocsQosParamSetRequestPolicy as in QOS MIB -02, requiring a bit swap and shift when reporting the value of the 24.16 Request/Transmission Policy parameter? 2) Change docsQosParamSetRequestPolicy in a QOS MIB -03 to be an INTEGER matching the binary value of parameter 24.16? -mike ------- Forwarded Message From ipcdn-admin@ietf.org Thu May 11 15:11:05 2000 Received: from mabs2.dma.isg.mot.com (mabs2.dma.isg.mot.com [150.21.2.21]) by noah.dma.isg.mot.com (8.8.8+Sun/8.8.8) with ESMTP id PAA26117; Thu, 11 May 2000 15:11:03 -0400 (EDT) Received: from mothost.mot.com (mothost.mot.com [129.188.137.101]) by mabs2.dma.isg.mot.com (8.8.7/8.8.7) with ESMTP id PAA03382; Thu, 11 May 2000 15:11:01 -0400 (EDT) Received: [from motgate.mot.com (motgate.mot.com [129.188.136.100]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id MAA08761; Thu, 11 May 2000 12:11:00 -0700 (MST)] Received: [from optimus.ietf.org (ietf.org [132.151.1.19]) by motgate.mot.com (motgate 2.1) with ESMTP id MAA17162; Thu, 11 May 2000 12:10:59 -0700 (MST)] Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA28507; Thu, 11 May 2000 15:10:54 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA28491 for ; Thu, 11 May 2000 15:10:53 -0400 (EDT) Received: from dmzraw1.extranet.tce.com (dmzraw1.extranet.tce.com [157.254.234.131]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06258 for ; Thu, 11 May 2000 15:10:50 -0400 (EDT) Received: from smtprelay.tce.com ([157.254.96.114]) by dmzraw1.extranet.tce.com (8.9.3/8.9.1) with ESMTP id OAA26153; Thu, 11 May 2000 14:10:16 -0500 (EST) Received: from indyexch1.indy.tce.com (localhost [127.0.0.1]) by smtprelay.tce.com (8.9.3/8.9.1) with ESMTP id OAA22345; Thu, 11 May 2000 14:10:15 -0500 (EST) Received: by indyexch1.indy.tce.com with Internet Mail Service (5.5.2650.21) id ; Thu, 11 May 2000 14:11:26 -0500 Message-ID: <4FA371B64BDAD2119CF40008C7D9ADB302B96D27@indyexch5.indy.tce.com> From: Yost William To: "'Mike St. Johns'" , "Michael W. Patrick" Cc: ljh031@dma.isg.mot.com, ipcdn@ietf.org Subject: RE: [ipcdn] Re: Bit ordering for docsQosParamSetRequestPolicy in QOS-MIB Date: Thu, 11 May 2000 14:11:03 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org I agree if no one ever looked at the data inside the modem, but just looked at a manager which properly displayed the BITS element as a set of enumerated bit values, you would have no problem. But some managers will only show the value as an octet string in hex and you will be looking at a dump of the configuration file and comparing it to what you see in SNMP and there will be an opportunity for misuderstanding where there needn't be. What Mike said below is still true, the agent will have to swap the bits in the word before returning it in an SNMP reply. People make mistakes, and this is just one more place that some implementations may swap the bits and some may not. - --- William H. Yost, Thomson Consumer Electronics: (317) 587-4816 --- . Home of RCA, Proscan, GE electronics . - -----Original Message----- From: Mike St. Johns [mailto:stjohns@corp.home.net] Sent: Thursday, May 11, 2000 11:55 AM To: Michael W. Patrick; Yost William Cc: ljh031@dma.isg.mot.com; ipcdn@ietf.org Subject: Re: [ipcdn] Re: Bit ordering for docsQosParamSetRequestPolicy in QOS-MIB Guys - Your confusing the MIB with the implementation - again. The MIB is an abstraction of how things work underneath. the BITS construct just maps a set of true/false values into an underlying construct that can get transmitted across the network. At the agent end, ignore the bit position and concentrate on the bit meaning. In other words, if the suppressPayloadHeaders bit is set in this , do whatever you would normally do for suppressPayloadHeaders. If that's setting the corresponding bit in a MAC request, then so be it, but these things ARE NOT LINKED except by the name's meaning - the assignment of the actual bit position is a transport mapping, nothing more and must not be too closely tied to some other field. We had this same discussion in packet cable on the syslog level meanings of the docsDevEvent priority levels. At 08:32 AM 5/10/00, Michael W. Patrick wrote: >Bill, > >Yuck. As it stands now, it looks like implementors will have >to reverse and shift the bit orders of a binary request policy (lsb=bit 0) >when reporting the mib docsQosParamSetRequestPolicy(msb=bit 0). > >This certainly was not what I intended. > >My question is, would it be too confusing at this late date >to update the MIB to match the implementation, >(e.g. by changing docsQosParamSetRequestPolicy to be an integer), >or should we leave the qos mib as-is and force the bit swap & shift? > >-mike > > > >>>>> "Yost" == Yost William writes: > > > > The bit numbering of these bits is the same (as far as bit numbers > > go) in the QOS-MIB and the RFI Spec (SP-RFIv1.1-I04-000407), but the > > bit ordering is reversed. SNMP defines bit 0 as the most > > significant bit in BITS, but the RFI Spec, in section C.2.2.6.3 > > defines bit 0 as the LSB of the value field. I assume this is what > > you intended, but I just wanted to double check. > > > Here is a copy of the MIB element definition. > > > docsQosParamSetRequestPolicy OBJECT-TYPE SYNTAX BITS > > { broadcastReqOpp (0), priorityReqMulticastReq (1), reqDataForReq > > (2), reqDataForData (3), piggybackReqWithData (4), concatenateData > > (5), fragmentData (6), supressPayloadHeaders (7), > > dropPktsExceedUGSize (8) } > > > --- William H. Yost, Thomson Consumer Electronics: (317) 587-4816 > > --- . Home of RCA, Proscan, GE electronics . > > >_______________________________________________ >IPCDN mailing list >IPCDN@ietf.org >http://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ IPCDN mailing list IPCDN@ietf.org http://www1.ietf.org/mailman/listinfo/ipcdn ------- End of Forwarded Message _______________________________________________ IPCDN mailing list IPCDN@ietf.org http://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Mon May 15 09:37:52 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03269; Mon, 15 May 2000 09:37:52 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA04266; Mon, 15 May 2000 09:34:31 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA04235 for ; Mon, 15 May 2000 09:34:29 -0400 (EDT) Received: from dmzraw1.extranet.tce.com (dmzraw1.extranet.tce.com [157.254.234.131]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03231 for ; Mon, 15 May 2000 09:34:27 -0400 (EDT) Received: from smtprelay.tce.com ([157.254.96.114]) by dmzraw1.extranet.tce.com (8.9.3/8.9.1) with ESMTP id IAA03968 for ; Mon, 15 May 2000 08:33:57 -0500 (EST) Received: from indyexch1.indy.tce.com (localhost [127.0.0.1]) by smtprelay.tce.com (8.9.3/8.9.1) with ESMTP id IAA06336 for ; Mon, 15 May 2000 08:33:56 -0500 (EST) Received: by indyexch1.indy.tce.com with Internet Mail Service (5.5.2650.21) id ; Mon, 15 May 2000 08:35:15 -0500 Message-ID: <4FA371B64BDAD2119CF40008C7D9ADB302B96D36@indyexch5.indy.tce.com> From: Yost William To: ipcdn@ietf.org Subject: RE: Yost William: RE: [ipcdn] Re: Bit ordering for docsQosParamSe tRequestPolicy in QOS-MIB Date: Mon, 15 May 2000 08:34:40 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org I vote 2) --- William H. Yost, Thomson Consumer Electronics: (317) 587-4816 --- . Home of RCA, Proscan, GE electronics . -----Original Message----- From: Michael W. Patrick [mailto:mpatrick@dma.isg.mot.com] Sent: Saturday, May 13, 2000 9:36 PM To: ipcdn@ietf.org Subject: Yost William: RE: [ipcdn] Re: Bit ordering for docsQosParamSetRequestPolicy in QOS-MIB OK, can I have a straw poll of Docsis vendors please? Do you vote 1) Keep DocsQosParamSetRequestPolicy as in QOS MIB -02, requiring a bit swap and shift when reporting the value of the 24.16 Request/Transmission Policy parameter? 2) Change docsQosParamSetRequestPolicy in a QOS MIB -03 to be an INTEGER matching the binary value of parameter 24.16? -mike ------- Forwarded Message From ipcdn-admin@ietf.org Thu May 11 15:11:05 2000 Received: from mabs2.dma.isg.mot.com (mabs2.dma.isg.mot.com [150.21.2.21]) by noah.dma.isg.mot.com (8.8.8+Sun/8.8.8) with ESMTP id PAA26117; Thu, 11 May 2000 15:11:03 -0400 (EDT) Received: from mothost.mot.com (mothost.mot.com [129.188.137.101]) by mabs2.dma.isg.mot.com (8.8.7/8.8.7) with ESMTP id PAA03382; Thu, 11 May 2000 15:11:01 -0400 (EDT) Received: [from motgate.mot.com (motgate.mot.com [129.188.136.100]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id MAA08761; Thu, 11 May 2000 12:11:00 -0700 (MST)] Received: [from optimus.ietf.org (ietf.org [132.151.1.19]) by motgate.mot.com (motgate 2.1) with ESMTP id MAA17162; Thu, 11 May 2000 12:10:59 -0700 (MST)] Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA28507; Thu, 11 May 2000 15:10:54 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA28491 for ; Thu, 11 May 2000 15:10:53 -0400 (EDT) Received: from dmzraw1.extranet.tce.com (dmzraw1.extranet.tce.com [157.254.234.131]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06258 for ; Thu, 11 May 2000 15:10:50 -0400 (EDT) Received: from smtprelay.tce.com ([157.254.96.114]) by dmzraw1.extranet.tce.com (8.9.3/8.9.1) with ESMTP id OAA26153; Thu, 11 May 2000 14:10:16 -0500 (EST) Received: from indyexch1.indy.tce.com (localhost [127.0.0.1]) by smtprelay.tce.com (8.9.3/8.9.1) with ESMTP id OAA22345; Thu, 11 May 2000 14:10:15 -0500 (EST) Received: by indyexch1.indy.tce.com with Internet Mail Service (5.5.2650.21) id ; Thu, 11 May 2000 14:11:26 -0500 Message-ID: <4FA371B64BDAD2119CF40008C7D9ADB302B96D27@indyexch5.indy.tce.com> From: Yost William To: "'Mike St. Johns'" , "Michael W. Patrick" Cc: ljh031@dma.isg.mot.com, ipcdn@ietf.org Subject: RE: [ipcdn] Re: Bit ordering for docsQosParamSetRequestPolicy in QOS-MIB Date: Thu, 11 May 2000 14:11:03 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org I agree if no one ever looked at the data inside the modem, but just looked at a manager which properly displayed the BITS element as a set of enumerated bit values, you would have no problem. But some managers will only show the value as an octet string in hex and you will be looking at a dump of the configuration file and comparing it to what you see in SNMP and there will be an opportunity for misuderstanding where there needn't be. What Mike said below is still true, the agent will have to swap the bits in the word before returning it in an SNMP reply. People make mistakes, and this is just one more place that some implementations may swap the bits and some may not. - --- William H. Yost, Thomson Consumer Electronics: (317) 587-4816 --- . Home of RCA, Proscan, GE electronics . - -----Original Message----- From: Mike St. Johns [mailto:stjohns@corp.home.net] Sent: Thursday, May 11, 2000 11:55 AM To: Michael W. Patrick; Yost William Cc: ljh031@dma.isg.mot.com; ipcdn@ietf.org Subject: Re: [ipcdn] Re: Bit ordering for docsQosParamSetRequestPolicy in QOS-MIB Guys - Your confusing the MIB with the implementation - again. The MIB is an abstraction of how things work underneath. the BITS construct just maps a set of true/false values into an underlying construct that can get transmitted across the network. At the agent end, ignore the bit position and concentrate on the bit meaning. In other words, if the suppressPayloadHeaders bit is set in this , do whatever you would normally do for suppressPayloadHeaders. If that's setting the corresponding bit in a MAC request, then so be it, but these things ARE NOT LINKED except by the name's meaning - the assignment of the actual bit position is a transport mapping, nothing more and must not be too closely tied to some other field. We had this same discussion in packet cable on the syslog level meanings of the docsDevEvent priority levels. At 08:32 AM 5/10/00, Michael W. Patrick wrote: >Bill, > >Yuck. As it stands now, it looks like implementors will have >to reverse and shift the bit orders of a binary request policy (lsb=bit 0) >when reporting the mib docsQosParamSetRequestPolicy(msb=bit 0). > >This certainly was not what I intended. > >My question is, would it be too confusing at this late date >to update the MIB to match the implementation, >(e.g. by changing docsQosParamSetRequestPolicy to be an integer), >or should we leave the qos mib as-is and force the bit swap & shift? > >-mike > > > >>>>> "Yost" == Yost William writes: > > > > The bit numbering of these bits is the same (as far as bit numbers > > go) in the QOS-MIB and the RFI Spec (SP-RFIv1.1-I04-000407), but the > > bit ordering is reversed. SNMP defines bit 0 as the most > > significant bit in BITS, but the RFI Spec, in section C.2.2.6.3 > > defines bit 0 as the LSB of the value field. I assume this is what > > you intended, but I just wanted to double check. > > > Here is a copy of the MIB element definition. > > > docsQosParamSetRequestPolicy OBJECT-TYPE SYNTAX BITS > > { broadcastReqOpp (0), priorityReqMulticastReq (1), reqDataForReq > > (2), reqDataForData (3), piggybackReqWithData (4), concatenateData > > (5), fragmentData (6), supressPayloadHeaders (7), > > dropPktsExceedUGSize (8) } > > > --- William H. Yost, Thomson Consumer Electronics: (317) 587-4816 > > --- . Home of RCA, Proscan, GE electronics . > > >_______________________________________________ >IPCDN mailing list >IPCDN@ietf.org >http://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ IPCDN mailing list IPCDN@ietf.org http://www1.ietf.org/mailman/listinfo/ipcdn ------- End of Forwarded Message _______________________________________________ IPCDN mailing list IPCDN@ietf.org http://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ IPCDN mailing list IPCDN@ietf.org http://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Mon May 15 17:57:52 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10702; Mon, 15 May 2000 17:57:52 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA09047; Mon, 15 May 2000 17:55:28 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA09018 for ; Mon, 15 May 2000 17:55:27 -0400 (EDT) Received: from mx-a.awc.net (root@smtp.awc.net [216.205.112.6]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10671 for ; Mon, 15 May 2000 17:55:25 -0400 (EDT) Received: from RHimlin (turbonet-1.nethere.net [216.188.38.169]) by mx-a.awc.net (8.9.1a/8.9.1) with SMTP id RAA19262; Mon, 15 May 2000 17:55:15 -0400 (EDT) From: "Bob Himlin" To: "'Yost William'" , Subject: RE: Yost William: RE: [ipcdn] Re: Bit ordering for docsQosParamSetRequestPolicy in QOS-MIB Date: Mon, 15 May 2000 14:55:11 -0700 Message-ID: <000301bfbeb8$3ef27440$0c52dad1@turbonetcomm.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal In-Reply-To: <4FA371B64BDAD2119CF40008C7D9ADB302B96D36@indyexch5.indy.tce.com> Content-Transfer-Encoding: 7bit Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org Content-Transfer-Encoding: 7bit Seconded. Bob Himlin, TurboNet Communications 15110 Avenue of Science San Diego, CA 92128-3405 rhimlin@turbonet-comm.com -----Original Message----- From: ipcdn-admin@ietf.org [mailto:ipcdn-admin@ietf.org] On Behalf Of Yost William Sent: Monday, May 15, 2000 6:35 AM To: ipcdn@ietf.org Subject: RE: Yost William: RE: [ipcdn] Re: Bit ordering for docsQosParamSetRequestPolicy in QOS-MIB I vote 2) --- William H. Yost, Thomson Consumer Electronics: (317) 587-4816 --- . Home of RCA, Proscan, GE electronics . -----Original Message----- From: Michael W. Patrick [mailto:mpatrick@dma.isg.mot.com] Sent: Saturday, May 13, 2000 9:36 PM To: ipcdn@ietf.org Subject: Yost William: RE: [ipcdn] Re: Bit ordering for docsQosParamSetRequestPolicy in QOS-MIB OK, can I have a straw poll of Docsis vendors please? Do you vote 1) Keep DocsQosParamSetRequestPolicy as in QOS MIB -02, requiring a bit swap and shift when reporting the value of the 24.16 Request/Transmission Policy parameter? 2) Change docsQosParamSetRequestPolicy in a QOS MIB -03 to be an INTEGER matching the binary value of parameter 24.16? -mike ------- Forwarded Message From ipcdn-admin@ietf.org Thu May 11 15:11:05 2000 Received: from mabs2.dma.isg.mot.com (mabs2.dma.isg.mot.com [150.21.2.21]) by noah.dma.isg.mot.com (8.8.8+Sun/8.8.8) with ESMTP id PAA26117; Thu, 11 May 2000 15:11:03 -0400 (EDT) Received: from mothost.mot.com (mothost.mot.com [129.188.137.101]) by mabs2.dma.isg.mot.com (8.8.7/8.8.7) with ESMTP id PAA03382; Thu, 11 May 2000 15:11:01 -0400 (EDT) Received: [from motgate.mot.com (motgate.mot.com [129.188.136.100]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id MAA08761; Thu, 11 May 2000 12:11:00 -0700 (MST)] Received: [from optimus.ietf.org (ietf.org [132.151.1.19]) by motgate.mot.com (motgate 2.1) with ESMTP id MAA17162; Thu, 11 May 2000 12:10:59 -0700 (MST)] Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA28507; Thu, 11 May 2000 15:10:54 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA28491 for ; Thu, 11 May 2000 15:10:53 -0400 (EDT) Received: from dmzraw1.extranet.tce.com (dmzraw1.extranet.tce.com [157.254.234.131]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06258 for ; Thu, 11 May 2000 15:10:50 -0400 (EDT) Received: from smtprelay.tce.com ([157.254.96.114]) by dmzraw1.extranet.tce.com (8.9.3/8.9.1) with ESMTP id OAA26153; Thu, 11 May 2000 14:10:16 -0500 (EST) Received: from indyexch1.indy.tce.com (localhost [127.0.0.1]) by smtprelay.tce.com (8.9.3/8.9.1) with ESMTP id OAA22345; Thu, 11 May 2000 14:10:15 -0500 (EST) Received: by indyexch1.indy.tce.com with Internet Mail Service (5.5.2650.21) id ; Thu, 11 May 2000 14:11:26 -0500 Message-ID: <4FA371B64BDAD2119CF40008C7D9ADB302B96D27@indyexch5.indy.tce.com> From: Yost William To: "'Mike St. Johns'" , "Michael W. Patrick" Cc: ljh031@dma.isg.mot.com, ipcdn@ietf.org Subject: RE: [ipcdn] Re: Bit ordering for docsQosParamSetRequestPolicy in QOS-MIB Date: Thu, 11 May 2000 14:11:03 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org I agree if no one ever looked at the data inside the modem, but just looked at a manager which properly displayed the BITS element as a set of enumerated bit values, you would have no problem. But some managers will only show the value as an octet string in hex and you will be looking at a dump of the configuration file and comparing it to what you see in SNMP and there will be an opportunity for misuderstanding where there needn't be. What Mike said below is still true, the agent will have to swap the bits in the word before returning it in an SNMP reply. People make mistakes, and this is just one more place that some implementations may swap the bits and some may not. - --- William H. Yost, Thomson Consumer Electronics: (317) 587-4816 --- . Home of RCA, Proscan, GE electronics . - -----Original Message----- From: Mike St. Johns [mailto:stjohns@corp.home.net] Sent: Thursday, May 11, 2000 11:55 AM To: Michael W. Patrick; Yost William Cc: ljh031@dma.isg.mot.com; ipcdn@ietf.org Subject: Re: [ipcdn] Re: Bit ordering for docsQosParamSetRequestPolicy in QOS-MIB Guys - Your confusing the MIB with the implementation - again. The MIB is an abstraction of how things work underneath. the BITS construct just maps a set of true/false values into an underlying construct that can get transmitted across the network. At the agent end, ignore the bit position and concentrate on the bit meaning. In other words, if the suppressPayloadHeaders bit is set in this , do whatever you would normally do for suppressPayloadHeaders. If that's setting the corresponding bit in a MAC request, then so be it, but these things ARE NOT LINKED except by the name's meaning - the assignment of the actual bit position is a transport mapping, nothing more and must not be too closely tied to some other field. We had this same discussion in packet cable on the syslog level meanings of the docsDevEvent priority levels. At 08:32 AM 5/10/00, Michael W. Patrick wrote: >Bill, > >Yuck. As it stands now, it looks like implementors will have >to reverse and shift the bit orders of a binary request policy (lsb=bit 0) >when reporting the mib docsQosParamSetRequestPolicy(msb=bit 0). > >This certainly was not what I intended. > >My question is, would it be too confusing at this late date >to update the MIB to match the implementation, >(e.g. by changing docsQosParamSetRequestPolicy to be an integer), >or should we leave the qos mib as-is and force the bit swap & shift? > >-mike > > > >>>>> "Yost" == Yost William writes: > > > > The bit numbering of these bits is the same (as far as bit numbers > > go) in the QOS-MIB and the RFI Spec (SP-RFIv1.1-I04-000407), but the > > bit ordering is reversed. SNMP defines bit 0 as the most > > significant bit in BITS, but the RFI Spec, in section C.2.2.6.3 > > defines bit 0 as the LSB of the value field. I assume this is what > > you intended, but I just wanted to double check. > > > Here is a copy of the MIB element definition. > > > docsQosParamSetRequestPolicy OBJECT-TYPE SYNTAX BITS > > { broadcastReqOpp (0), priorityReqMulticastReq (1), reqDataForReq > > (2), reqDataForData (3), piggybackReqWithData (4), concatenateData > > (5), fragmentData (6), supressPayloadHeaders (7), > > dropPktsExceedUGSize (8) } > > > --- William H. Yost, Thomson Consumer Electronics: (317) 587-4816 > > --- . Home of RCA, Proscan, GE electronics . > > >_______________________________________________ >IPCDN mailing list >IPCDN@ietf.org >http://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ IPCDN mailing list IPCDN@ietf.org http://www1.ietf.org/mailman/listinfo/ipcdn ------- End of Forwarded Message _______________________________________________ IPCDN mailing list IPCDN@ietf.org http://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ IPCDN mailing list IPCDN@ietf.org http://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ IPCDN mailing list IPCDN@ietf.org http://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Mon May 15 20:36:30 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12211; Mon, 15 May 2000 20:36:29 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA10615; Mon, 15 May 2000 20:34:38 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA10377 for ; Mon, 15 May 2000 20:25:52 -0400 (EDT) Received: from zipcode.corp.home.net (zipcode.corp.home.net [24.0.26.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12023 for ; Mon, 15 May 2000 20:25:47 -0400 (EDT) Received: from lock.eos.home.net (root@lock.eos.home.net [24.0.16.84]) by zipcode.corp.home.net (8.9.3/8.9.3) with ESMTP id RAA17245 for ; Mon, 15 May 2000 17:25:40 -0700 (PDT) Received: from lock.eos.home.net (stjohns@localhost [127.0.0.1]) by lock.eos.home.net (8.9.1/8.8.5) with ESMTP id RAA11017 for ; Mon, 15 May 2000 17:25:38 -0700 (PDT) Message-Id: <200005160025.RAA11017@lock.eos.home.net> X-Mailer: exmh version 2.0delta 6/3/97 To: ipcdn@ietf.org Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_-8111811010" Date: Mon, 15 May 2000 17:25:36 -0700 From: "Mike StJohns" Subject: [ipcdn] Revised bare mib - Cable Device Mib Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org This is a multipart MIME message. --==_Exmh_-8111811010 Content-Type: text/plain; charset=us-ascii I've attached the most recent version of the cable device mib, bare of the surrounding internet draft (this will follow shortly). I think its pretty much in good shape, however there's one issue I need input on from the list. Back when we re-did filtering, I added the "continue" object in the filtering set to deal with things where you might want to apply multiple policies (e.g. filtering and TOS marking and IPSEC). To date, this hasn't been used because we haven't yet done TOS marking or any of the QOS stuff. My first inclination is to yank it out as it adds to the complexity of the filtering code, BUT - the above requirements still remain. If we had more experience with the QOS stuff I'd be more confident one way or the other. Right now, I'm leaning towards leaving it in (even though this version of the mib has it marked as deprecated). This mib clean compiles under smicng - with the appropriate options. You'll need to grab a copy of the IPV6-TC mib - see the mib for the RFC number. Comments? Mike --==_Exmh_-8111811010 Content-Type: text/plain ; name="CABLE-DEVICE-MIB2.my"; charset=us-ascii Content-Description: CABLE-DEVICE-MIB2.my Content-Disposition: attachment; filename="CABLE-DEVICE-MIB2.my" DOCS-CABLE-DEVICE-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, IpAddress, Unsigned32, Counter32, Integer32, zeroDotZero, mib-2 FROM SNMPv2-SMI TEXTUAL-CONVENTION, RowStatus, RowPointer, DateAndTime, TruthValue FROM SNMPv2-TC Ipv6Address FROM IPV6-TC -- RFC 2465 OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF SnmpAdminString FROM SNMP-FRAMEWORK-MIB vacmAccessEntry FROM SNMP-VIEW-BASED-ACM-MIB InterfaceIndexOrZero FROM IF-MIB; -- RFC2233 docsDev MODULE-IDENTITY LAST-UPDATED "200005150000Z" -- 15 May 2000, 0000Z ORGANIZATION "IETF IPCDN Working Group" CONTACT-INFO " Michael StJohns Postal: Excite@Home 450 Broadway Redwood City, CA 94063 U.S.A. Phone: +1 650 569 5368 E-mail: stjohns@corp.home.net" DESCRIPTION "This is the MIB Module for MCNS-compliant cable modems and cable-modem termination systems." REVISION "200005150000Z" -- 15 May 2000, 0000Z DESCRIPTION "Modified by Mike StJohns to bring into SNMPv3/IPv6 compliance." REVISION "9908190000Z" DESCRIPTION "Initial version, published as RFC 2669." ::= { mib-2 69 } docsDevMIBObjects OBJECT IDENTIFIER ::= { docsDev 1 } docsDevBase OBJECT IDENTIFIER ::= { docsDevMIBObjects 1 } -- Textual Conventions InterfaceSet ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This is a convenience object for setting the value of a bit set object which depicts a set of interfaces. Upon read this always returns other (1). Upon a valid set, this causes interface bit set object (as indicated in the object description which uses this syntax) in the same row to be set to a bit mask set consisting of the interfaces which match the class type represented by this object. allCpe - all interfaces which face the customer. allNetwork - all interfaces which do not face the customer - e.g. for a CM the HFC MAC interface. allCpeEthernet, allCpeUsb, allCpeFirewire - self-explanatory allExternal - all interfaces which have a external physical instantiation, e.g. CPE Ethernet, HFC MAC, PCI Bus allInternal - all interfaces which point towards either the devices own stack, or towards an application residing on the device self - the interface which points to the devices own stack all - all interfaces. application1-4 - a specific application residing on the CM or CMTS. The specific mapping of which values of this object map to which interfaces is out of scope for this document. Certain of these classes of interfaces may not exist on specific agents, in which case, setting this object to those values results in related interface bit set being set to an empty bit set. all, allCpe and allNetwork MUST be valid settings for this object on any compliant agent and MUST result in at least one interface bit being set in the related bit set." SYNTAX INTEGER { other (1), allCpe (2), allNetwork (3), allCpeEthernet (4), allCpeUsb (5), allCpeFirewire (6), allExternal (7), allInternal (8), all (9), application1 (10), application2 (11), application3 (12), application4 (13) } IpV4orV6Address ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An IP V4 or V6 address expressed as an octet string. The zero length string is equal to both 0.0.0.0 and the IPv6 :0 address." SYNTAX OCTET STRING (SIZE (0 | 4 | 16)) -- -- For the following object, there is no concept in the -- RFI specification corresponding to a backup CMTS. The -- enumeration is provided here in case someone is able -- to define such a role or device. -- docsDevRole OBJECT-TYPE SYNTAX INTEGER { cm(1), cmtsActive(2), cmtsBackup(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "Defines the current role of this device. cm (1) is a Cable Modem, cmtsActive(2) is a Cable Modem Termination System which is controlling the system of cable modems, and cmtsBackup(3) is a CMTS which is currently connected, but not controlling the system (not currently used). In general, if this device is a 'cm', its role will not change during operation or between reboots. If the device is a 'cmts' it may change between cmtsActive and cmtsBackup and back again during normal operation. NB: At this time, the DOCSIS standards do not support the concept of a backup CMTS, cmtsBackup is included for completeness." ::= { docsDevBase 1 } docsDevDateTime OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-write STATUS current DESCRIPTION "The current date and time, with optional timezone information. This is set at boot from the time server. If its impossible to set this from boot, this shall represent elapsed time from boot relative to the standard epoch (e.g. 1 Jan 1970 0000Z). In other words, if this agent has been up for 3 minuntes, and has been unable to set this object from the time server, this object will return 1 Jan 1970 0003Z." ::= { docsDevBase 2 } docsDevResetNow OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Setting this object to true(1) causes the device to reset. Reading this object always returns false(2)." ::= { docsDevBase 3 } docsDevSerialNumber OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The manufacturer's serial number for this device." ::= { docsDevBase 4 } docsDevSTPControl OBJECT-TYPE SYNTAX INTEGER { stEnabled(1), noStFilterBpdu(2), noStPassBpdu(3) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object controls operation of the spanning tree protocol (as distinguished from transparent bridging). If set to stEnabled(1) then the spanning tree protocol is enabled, subject to bridging constraints. If noStFilterBpdu(2), then spanning tree is not active, and Bridge PDUs received are discarded. If noStPassBpdu(3) then spanning tree is not active and Bridge PDUs are transparently forwarded. Note that a device need not implement all of these options, but that noStFilterBpdu(2) is required." ::= { docsDevBase 5 } -- -- The following table provides one level of security for access -- to the device by network management stations. -- Note that access is also constrained by the -- community strings and any vendor-specific security. -- docsDevNmAccessTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevNmAccessEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "This table controls access to SNMP objects by network management stations. If the table is empty, access to SNMP objects is unrestricted. This table exists only on SNMPv1 or v2c agents and does not exist on SNMPv3 agents. See the conformance section for details. Specifically, for v3 agents, the appropriate MIBs and security models apply in lieu of this table. This table is deprecated. Instead, use the SNMP coexistence MIBs from RFC2576, the TARGET and NOTIFICATION MIBs from the SNMP Applications RFC, and the VACM MIBs for SNMPv1 and V2C access. If SNMP-COMMUNITY-MIB is implemented AND populated, then this table and its entries are ignored for the purpose of determining v1 or v2c access. If the SNMP-COMMUNITY-MIB table has no entries, then this table has its normal access control meaning for v1 and v2c access." ::= { docsDevMIBObjects 2 } docsDevNmAccessEntry OBJECT-TYPE SYNTAX DocsDevNmAccessEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "An entry describing access to SNMP objects by a particular network management station. An entry in this table is not readable unless the management station has read-write permission (either implicit if the table is empty, or explicit through an entry in this table. Entries are ordered by docsDevNmAccessIndex. The first matching entry (e.g. matching IP address and community string) is used to derive access." INDEX { docsDevNmAccessIndex } ::= { docsDevNmAccessTable 1 } DocsDevNmAccessEntry ::= SEQUENCE { docsDevNmAccessIndex Integer32, docsDevNmAccessIp IpAddress, docsDevNmAccessIpMask IpAddress, docsDevNmAccessCommunity OCTET STRING, docsDevNmAccessControl INTEGER, docsDevNmAccessInterfaces OCTET STRING, docsDevNmAccessStatus RowStatus } docsDevNmAccessIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "Index used to order the application of access entries." ::= { docsDevNmAccessEntry 1 } docsDevNmAccessIp OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS deprecated DESCRIPTION "The IP address (or subnet) of the network management station. The address 255.255.255.255 is defined to mean any NMS. If traps are enabled for this entry, then the value must be the address of a specific device." DEFVAL { 'ffffffff'h } ::= { docsDevNmAccessEntry 2 } docsDevNmAccessIpMask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS deprecated DESCRIPTION "The IP subnet mask of the network management stations. If traps are enabled for this entry, then the value must be 255.255.255.255." DEFVAL { 'ffffffff'h } ::= { docsDevNmAccessEntry 3 } docsDevNmAccessCommunity OBJECT-TYPE SYNTAX OCTET STRING (SIZE (0..32)) MAX-ACCESS read-create STATUS deprecated DESCRIPTION "The community string to be matched for access by this entry. If set to a zero length string then any community string will match. When read, this object SHOULD return a zero length string." DEFVAL { "public" } ::= { docsDevNmAccessEntry 4 } docsDevNmAccessControl OBJECT-TYPE SYNTAX INTEGER { none(1), read(2), readWrite(3), roWithTraps(4), rwWithTraps(5), trapsOnly(6) } MAX-ACCESS read-create STATUS deprecated DESCRIPTION "Specifies the type of access allowed to this NMS. Setting this object to none(1) causes the table entry to be destroyed. Read(2) allows access by 'get' and 'get-next' PDUs. ReadWrite(3) allows access by 'set' as well. RoWithtraps(4), rwWithTraps(5), and trapsOnly(6) control distribution of Trap PDUs transmitted by this device." DEFVAL { read } ::= { docsDevNmAccessEntry 5 } -- The syntax of the following object was copied from RFC1493, -- dot1dStaticAllowedToGoTo. docsDevNmAccessInterfaces OBJECT-TYPE SYNTAX OCTET STRING (SIZE (1..32)) MAX-ACCESS read-create STATUS deprecated DESCRIPTION "Specifies the set of interfaces from which requests from this NMS will be accepted. Each octet within the value of this object specifies a set of eight interfaces, with the first octet specifying ports 1 through 8, the second octet specifying interfaces 9 through 16, etc. Within each octet, the most significant bit represents the lowest numbered interface, and the least significant bit represents the highest numbered interface. Thus, each interface is represented by a single bit within the value of this object. If that bit has a value of '1' then that interface is included in the set. Note that entries in this table apply only to link-layer interfaces (e.g., Ethernet and CATV MAC). Upstream and downstream channel interfaces must not be specified. The size of this object is the minimum required to represent all configured interfaces for this device." -- DEFVAL is the bitmask corresponding to all interfaces ::= { docsDevNmAccessEntry 6 } docsDevNmAccessStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS deprecated DESCRIPTION "Controls and reflects the status of rows in this table. Rows in this table may be created by either the create-and-go or create-and-wait paradigms. There is no restriction on changing values in a row of this table while the row is active." ::= { docsDevNmAccessEntry 7 } -- -- Procedures for using the following group are described in section -- 3.2.1 of the DOCSIS Radio Frequence Interface Specification -- docsDevSoftware OBJECT IDENTIFIER ::= { docsDevMIBObjects 3 } docsDevSwServer OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-write STATUS deprecated DESCRIPTION "The address of the TFTP server used for software upgrades. If the TFTP server is unknown or is a V6 address, return 0.0.0.0. This entry is deprecated. See docsDevSwServerAddress for its replacement. This object is will have its value modified given a valid SET to docsDevSwServerAddress." ::= { docsDevSoftware 1 } docsDevSwFilename OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..64)) MAX-ACCESS read-write STATUS current DESCRIPTION "The file name of the software image to be loaded into this device. Unless set via SNMP, this is the file name specified by the provisioning server that corresponds to the software version that is desired for this device. If unknown, the string '(unknown)' is returned." ::= { docsDevSoftware 2 } docsDevSwAdminStatus OBJECT-TYPE SYNTAX INTEGER { upgradeFromMgt(1), allowProvisioningUpgrade(2), ignoreProvisioningUpgrade(3) } MAX-ACCESS read-write STATUS current DESCRIPTION "If set to upgradeFromMgt(1), the device will initiate a TFTP software image download using docsDevSwFilename. After successfully receiving an image, the device will set its state to ignoreProvisioningUpgrade(3) and reboot. If the download process is interrupted by a reset or power failure, the device will load the previous image and, after re-initialization, continue to attempt loading the image specified in docsDevSwFilename. If set to allowProvisioningUpgrade(2), the device will use the software version information supplied by the provisioning server when next rebooting (this does not cause a reboot). When set to ignoreProvisioningUpgrade(3), the device will disregard software image upgrade information from the provisioning server. Note that reading this object can return upgradeFromMgt(1). This indicates that a software download is currently in progress, and that the device will reboot after successfully receiving an image. At initial startup, this object has the default value of allowProvisioningUpgrade(2)." ::= { docsDevSoftware 3 } docsDevSwOperStatus OBJECT-TYPE SYNTAX INTEGER { inProgress(1), completeFromProvisioning(2), completeFromMgt(3), failed(4), other(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "InProgress(1) indicates that a TFTP download is underway, either as a result of a version mismatch at provisioning or as a result of a upgradeFromMgt request. CompleteFromProvisioning(2) indicates that the last software upgrade was a result of version mismatch at provisioning. CompleteFromMgt(3) indicates that the last software upgrade was a result of setting docsDevSwAdminStatus to upgradeFromMgt. Failed(4) indicates that the last attempted download failed, ordinarily due to TFTP timeout." REFERENCE "DOCSIS Radio Frequency Interface Specification, Section 8.2, Downloading Cable Modem Operating Software." ::= { docsDevSoftware 4 } docsDevSwCurrentVers OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The software version currently operating in this device. This object should be in the syntax used by the individual vendor to identify software versions. Any CM MUST return a string descriptive of the current software load. For a CMTS, this object SHOULD contain either a human readable representation of the vendor specific designation of the software for the chassis, or of the software for the control processor. If neither of these is applicable, this MUST contain an empty string." ::= { docsDevSoftware 5 } docsDevSwServerAddress OBJECT-TYPE SYNTAX IpV4orV6Address MAX-ACCESS read-write STATUS current DESCRIPTION "The address of the TFTP server used for software upgrades. If the TFTP server is unknown, return the zero length address string (See the TextualConvention). If docsDevSwServer is also implemented in this agent, this object is tied to it. A set of this object to an IPv4 address will result in the value of docsDevSwServer also being set to that address. If this object is set to an IPv6 address, docsDevSwServer is set to 0.0.0.0. If docsDevSwServer is set, this object is also set to that value. Note that if both are set in the same action, the order of which one sets the other is undefined - so both should be the same value." ::= { docsDevSoftware 6 } -- -- The following group describes server access and parameters used for -- initial provisioning and bootstrapping. -- docsDevServer OBJECT IDENTIFIER ::= { docsDevMIBObjects 4 } docsDevServerBootState OBJECT-TYPE SYNTAX INTEGER { operational(1), disabled(2), waitingForDhcpOffer(3), waitingForDhcpResponse(4), waitingForTimeServer(5), waitingForTftp(6), refusedByCmts(7), forwardingDenied(8), other(9), unknown(10) } MAX-ACCESS read-only STATUS current DESCRIPTION "If operational(1), the device has completed loading and processing of configuration parameters and the CMTS has completed the Registration exchange. If disabled(2) then the device was administratively disabled, possibly by being refused network access in the configuration file. If waitingForDhcpOffer(3) then a DHCP Discover has been transmitted and no offer has yet been received. If waitingForDhcpResponse(4) then a DHCP Request has been transmitted and no response has yet been received. If waitingForTimeServer(5) then a Time Request has been transmitted and no response has yet been received. If waitingForTftp(6) then a request to the TFTP parameter server has been made and no response received. If refusedByCmts(7) then the Registration Request/Response exchange with the CMTS failed. If forwardingDenied(8) then the registration process completed, but the network access option in the received configuration file prohibits forwarding. " REFERENCE "DOCSIS Radio Frequency Interface Specification, Figure 7-1, CM Initialization Overview." ::= { docsDevServer 1 } docsDevServerDhcp OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The IP address of the DHCP server that assigned an IP address to this device. Returns 0.0.0.0 if DHCP was not used for IP address assignment, or if this agent was assigned an IPv6 address. Deprecated. This object is replaced by docsDevServerDhcpAddress" ::= { docsDevServer 2 } docsDevServerTime OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The IP address of the Time server (RFC-868). Returns 0.0.0.0 if the time server IP address is unknown, or if the time server was an IPv6 server. Deprecated. This object is replaced by docsDevServerTimeAddress." ::= { docsDevServer 3 } docsDevServerTftp OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The IP address of the TFTP server responsible for downloading provisioning and configuration parameters to this device. Returns 0.0.0.0 if the TFTP server address is unknown or is an IPv6 address. Deprecated. This object is replaced by docsDevServerConfigTftpAddress." ::= { docsDevServer 4 } docsDevServerConfigFile OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The name of the device configuration file read from the TFTP server. Returns an empty string if the configuration file name is unknown." ::= { docsDevServer 5 } docsDevServerDhcpAddress OBJECT-TYPE SYNTAX IpV4orV6Address MAX-ACCESS read-only STATUS current DESCRIPTION "The IP v4 or v6 address of the DHCP server that assigned an IP address to this device. Returns the zero length octet string if DHCP was not used for IP address assignment." ::= { docsDevServer 6 } docsDevServerTimeAddress OBJECT-TYPE SYNTAX IpV4orV6Address MAX-ACCESS read-only STATUS current DESCRIPTION "The IP V4 or V6 address of the Time server (RFC-868). Returns the zero length octet string if the time server IP address is unknown." ::= { docsDevServer 7 } docsDevServerConfigTftpAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP V4 or V6 address of the TFTP server responsible for downloading provisioning and configuration parameters to this device. Returns the zero length octet string if the config server address is unknown." ::= { docsDevServer 8 } -- -- Event Reporting -- docsDevEvent OBJECT IDENTIFIER ::= { docsDevMIBObjects 5 } docsDevEvControl OBJECT-TYPE SYNTAX INTEGER { resetLog(1), useDefaultReporting(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Setting this object to resetLog(1) empties the event log. All data is deleted. Setting it to useDefaultReporting(2) returns all event priorities to their factory-default reporting. Reading this object always returns useDefaultReporting(2)." ::= { docsDevEvent 1 } docsDevEvSyslog OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-write STATUS deprecated DESCRIPTION "The IP address of the Syslog server. If 0.0.0.0, syslog transmission is either inhibited, or if docsDevEvSyslogAddress exists in this agent - may be an IPv6 device. Deprecated. See docsDevEvSyslogAddress" ::= { docsDevEvent 2 } docsDevEvThrottleAdminStatus OBJECT-TYPE SYNTAX INTEGER { unconstrained(1), maintainBelowThreshold(2), stopAtThreshold(3), inhibited(4) } MAX-ACCESS read-write STATUS current DESCRIPTION "Controls the transmission of traps and syslog messages with respect to the trap pacing threshold. unconstrained(1) causes traps and syslog messages to be transmitted without regard to the threshold settings. maintainBelowThreshold(2) causes trap transmission and syslog messages to be suppressed if the number of traps would otherwise exceed the threshold. stopAtThreshold(3) causes trap transmission to cease at the threshold, and not resume until directed to do so. inhibited(4) causes all trap transmission and syslog messages to be suppressed. A single event is always treated as a single event for threshold counting. That is, an event causing both a trap and a syslog message is still treated as a single event. Writing to this object resets the thresholding state. At initial startup, this object has a default value of unconstrained(1)." ::= { docsDevEvent 3 } docsDevEvThrottleInhibited OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "If true(1), trap and syslog transmission is currently inhibited due to thresholds and/or the current setting of docsDevEvThrottleAdminStatus. In addition, this is set to true(1) if transmission is inhibited due to no syslog (docsDevEvSyslog) or trap (docsDevNmAccessEntry) destinations having been set." ::= { docsDevEvent 4 } docsDevEvThrottleThreshold OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION "Number of trap/syslog events per docsDevEvThrottleInterval to be transmitted before throttling. A single event is always treated as a single event for threshold counting. That is, an event causing both a trap and a syslog message is still treated as a single event. At initial startup, this object returns 0." ::= { docsDevEvent 5 } docsDevEvThrottleInterval OBJECT-TYPE SYNTAX Integer32 (1..2147483647) UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "The interval over which the trap threshold applies. At initial startup, this object has a value of 1." ::= { docsDevEvent 6 } -- -- The following table controls the reporting of the various classes of -- events. -- docsDevEvControlTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevEvControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table allows control of the reporting of event classes. For each event priority, a combination of logging and reporting mechanisms may be chosen. The mapping of event types to priorities is vendor-dependent. Vendors may also choose to allow the user to control that mapping through proprietary means." ::= { docsDevEvent 7 } docsDevEvControlEntry OBJECT-TYPE SYNTAX DocsDevEvControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Allows configuration of the reporting mechanisms for a particular event priority." INDEX { docsDevEvPriority } ::= { docsDevEvControlTable 1 } DocsDevEvControlEntry ::= SEQUENCE { docsDevEvPriority INTEGER, docsDevEvReporting BITS } docsDevEvPriority OBJECT-TYPE SYNTAX INTEGER { emergency(1), alert(2), critical(3), error(4), warning(5), notice(6), information(7), debug(8) } MAX-ACCESS not-accessible STATUS current DESCRIPTION "The priority level that is controlled by this entry. These are ordered from most (emergency) to least (debug) critical. Each event with a CM or CMTS has a particular priority level associated with it (as defined by the vendor). During normal operation no event more critical than notice(6) should be generated. Events between warning and emergency should be generated at appropriate levels of problems (e.g. emergency when the box is about to crash)." ::= { docsDevEvControlEntry 1 } docsDevEvReporting OBJECT-TYPE SYNTAX BITS { local(0), traps(1), syslog(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Defines the action to be taken on occurrence of this event class. Implementations may not necessarily support all options for all event classes, but at minimum must allow traps and syslogging to be disabled. If the local(0) bit is set, then log to the internal log, if the traps(1) bit is set, then generate a trap, if the syslog(2) bit is set, then send a syslog message (assuming the syslog address is set)." ::= { docsDevEvControlEntry 2 } docsDevEventTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevEventEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Contains a log of network and device events that may be of interest in fault isolation and troubleshooting." ::= { docsDevEvent 8 } docsDevEventEntry OBJECT-TYPE SYNTAX DocsDevEventEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Describes a network or device event that may be of interest in fault isolation and troubleshooting. Multiple sequential identical events are represented by incrementing docsDevEvCounts and setting docsDevEvLastTime to the current time rather than creating multiple rows. Entries are created with the first occurrance of an event. docsDevEvControl can be used to clear the table. Individual events can not be deleted." INDEX { docsDevEvIndex } ::= { docsDevEventTable 1 } DocsDevEventEntry ::= SEQUENCE { docsDevEvIndex Integer32, docsDevEvFirstTime DateAndTime, docsDevEvLastTime DateAndTime, docsDevEvCounts Counter32, docsDevEvLevel INTEGER, docsDevEvId Unsigned32, docsDevEvText SnmpAdminString } docsDevEvIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Provides relative ordering of the objects in the event log. This object will always increase except when (a) the log is reset via docsDevEvControl, (b) the device reboots and does not implement non-volatile storage for this log, or (c) it reaches the value 2^31. The next entry for all the above cases is 1." ::= { docsDevEventEntry 1 } docsDevEvFirstTime OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION "The value of docsDevDateTime at the time this entry was created." ::= { docsDevEventEntry 2 } docsDevEvLastTime OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION "If multiple events are reported via the same entry, the value of docsDevDateTime that the last event for this entry occurred, otherwise this should have the same value as docsDevEvFirstTime. " ::= { docsDevEventEntry 3 } docsDevEvCounts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of consecutive event instances reported by this entry. This starts at 1 with the creation of this row and increments by 1 for each subsequent duplicate event." ::= { docsDevEventEntry 4 } docsDevEvLevel OBJECT-TYPE SYNTAX INTEGER { emergency(1), alert(2), critical(3), error(4), warning(5), notice(6), information(7), debug(8) } MAX-ACCESS read-only STATUS current DESCRIPTION "The priority level of this event as defined by the vendor. These are ordered from most serious (emergency) to least serious (debug)." ::= { docsDevEventEntry 5 } -- -- Vendors will provide their own enumerations for the following. -- The interpretation of the enumeration is unambiguous for a -- particular value of the vendor's enterprise number in sysObjectID. -- docsDevEvId OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "For this product, uniquely identifies the type of event that is reported by this entry." ::= { docsDevEventEntry 6 } docsDevEvText OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "Provides a human-readable description of the event, including all relevant context (interface numbers, etc.)." ::= { docsDevEventEntry 7 } docsDevEvSyslogAddress OBJECT-TYPE SYNTAX IpV4orV6Address MAX-ACCESS read-write STATUS current DESCRIPTION "The IP V4 or V6 address of the Syslog server. If the address of the server is set to any of the zero length string, the 0.0.0.0 V4 address or the 0: V6 address, syslog transmission is inhibited. By default at agent boot, this object returns the zero length string." ::= { docsDevEvent 9 } docsDevFilter OBJECT IDENTIFIER ::= { docsDevMIBObjects 6 } -- -- Link Level Control Filtering -- docsDevFilterLLCUnmatchedAction OBJECT-TYPE SYNTAX INTEGER { discard(1), accept(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "LLC (Link Level Control) filters can be defined on an inclusive or exclusive basis: CMs can be configured to forward only packets matching a set of layer three protocols, or to drop packets matching a set of layer three protocols. Typical use of these filters is to filter out possibly harmful (given the context of a large metropolitan LAN) protocols. If set to discard(1), any L2 packet which does not match at least one filter in the docsDevFilterLLCTable will be discarded. If set to accept(2), any L2 packet which does not match at least one filter in the docsDevFilterLLCTable will be accepted for further processing (e.g., bridging). In otherwords, if the packet does not match an entry in the table it takes this action, if it does match an entry in the table it takes the opposite of this action. At initial system startup, this object returns accept(2)." ::= { docsDevFilter 1 } docsDevFilterLLCTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevFilterLLCEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of filters to apply to (bridged) LLC traffic. The filters in this table are applied to incoming traffic on the appropriate interface(s) prior to any further processing (e.g. before handing the packet off for level 3 processing, or for bridging). The specific action taken when no filter is matched is controlled by docsDevFilterLLCUnmatchedAction." ::= { docsDevFilter 2 } docsDevFilterLLCEntry OBJECT-TYPE SYNTAX DocsDevFilterLLCEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Describes a single filter to apply to (bridged) LLC traffic received on a specified interface. " INDEX { docsDevFilterLLCIndex } ::= { docsDevFilterLLCTable 1 } DocsDevFilterLLCEntry ::= SEQUENCE { docsDevFilterLLCIndex Integer32, docsDevFilterLLCStatus RowStatus, docsDevFilterLLCIfIndex InterfaceIndexOrZero, docsDevFilterLLCProtocolType INTEGER, docsDevFilterLLCProtocol Integer32, docsDevFilterLLCMatches Counter32, docsDevFilterLLCInterfaces OCTET STRING, docsDevFilterLLCInterfaceSet InterfaceSet } docsDevFilterLLCIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Index used for the identification of filters (note that LLC filter order is irrelevant)." ::= { docsDevFilterLLCEntry 1 } docsDevFilterLLCStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "Controls and reflects the status of rows in this table. There is no restriction on changing any of the associated columns for this row while this object is set to active." ::= { docsDevFilterLLCEntry 2} docsDevFilterLLCIfIndex OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS read-create STATUS deprecated DESCRIPTION "The entry interface to which this filter applies. The value corresponds to ifIndex for either a CATV MAC or another network interface. If the value is zero, the filter applies to all interfaces. In Cable Modems, the default value is the customer side interface. In Cable Modem Termination Systems, this object has to be specified to create a row in this table. DEPRECATED. If the docsDevFilterLLCInterfaces object exists in this agent and row, then the value of this object is ignored for purposes of filtering." ::= { docsDevFilterLLCEntry 3 } docsDevFilterLLCProtocolType OBJECT-TYPE SYNTAX INTEGER { ethertype(1), dsap(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The format of the value in docsDevFilterLLCProtocol: either a two-byte Ethernet Ethertype, or a one-byte 802.2 SAP value. EtherType(1) also applies to SNAP- encapsulated frames." DEFVAL { ethertype } ::= { docsDevFilterLLCEntry 4 } docsDevFilterLLCProtocol OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The layer three protocol for which this filter applies. The protocol value format depends on docsDevFilterLLCProtocolType. Note that for SNAP frames, etherType filtering is performed rather than DSAP=0xAA." DEFVAL { 0 } ::= { docsDevFilterLLCEntry 5 } docsDevFilterLLCMatches OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Counts the number of times this filter was matched." ::= { docsDevFilterLLCEntry 6 } docsDevFilterLLCInterfaces OBJECT-TYPE SYNTAX OCTET STRING (SIZE (1..32)) MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the set of interfaces this filter applies to. Each octet within the value of this object specifies a set of eight interfaces, with the first octet spefifying interfaces 1 through 8, the second octet specifying interfaces 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered interface, and the least significant bit representst the highest numbered interface. Thus, each interface is represented by a single bit within the value of this object. If that bit has a value of '1' then that interface is included in this set. The actual mapping of physical interfaces to interface number is implementation dependent." ::= { docsDevFilterLLCEntry 7 } docsDevFilterLLCInterfaceSet OBJECT-TYPE SYNTAX InterfaceSet MAX-ACCESS read-create STATUS current DESCRIPTION "This is a convenience object for setting the value of docsDevFilterLLCInterfaces. Upon a valid set, this causes docsDevFilterLLCInterfaces in the same row to be set to a bit mask set consisting of the interfaces which match the class type represented by this object. Upon read, this returns 'other' by definition." DEFVAL { allCpe } ::= { docsDevFilterLLCEntry 8 } docsDevFilterIpDefault OBJECT-TYPE SYNTAX INTEGER { discard(1), accept(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The default behavior for (bridged) packets that do not match IP filters is defined by docsDevFilterIpDefault. If set to discard(1), all packets not matching an IP filter will be discarded. If set to accept(2), all packets not matching an IP filter will be accepted for further processing (e.g., bridging). At initial system startup, this object returns accept(2)." ::= { docsDevFilter 3 } docsDevFilterIpTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevFilterIpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An ordered list of filters or classifiers to apply to IP traffic. Filter application is ordered by the filter index, rather than by a best match algorithm (Note that this implies that the filter table may have gaps in the index values). Packets which match no filters will have policy 0 in the docsDevFilterPolicyTable applied to them if it exists. Otherwise, Packets which match no filters are discarded or forwarded according to the setting of docsDevFilterIpDefault. Any IP packet can theoretically match multiple rows of this table. When considering a packet, the table is scanned in row index order (e.g. filter 10 is checked before filter 20). If the packet matches that filter (which means that it matches ALL criteria for that row), actions appropriate to docsDevFilterIpControl and docsDevFilterPolicyId are taken. If the packet was discarded processing is complete. If docsDevFilterIpContinue is set to true, the filter comparison continues with the next row in the table looking for additional matches. If the packet matches no filter in the table, the packet is accepted or dropped for further processing based on the setting of docsDevFilterIpDefault. If the packet is accepted, the actions specified by policy group 0 (e.g. the rows in docsDevFilterPolicyTable which have a value of 0 for docsDevFilterPolicyId) are taken if that policy group exists. Logically, this table is consulted twice during the processing of any IP packet - once upon its acceptance from the L2 entity, and once upon its transmission to the L2 entity. In actuality, for cable modems, IP filtering is generally the only IP processing done for transit traffic. This means that inbound and outbound filtering can generally be done at the same time with one pass through the filter table." ::= { docsDevFilter 4 } docsDevFilterIpEntry OBJECT-TYPE SYNTAX DocsDevFilterIpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Describes a filter to apply to IP traffic received on a specified interface. All identity objects in this table (e.g. source and destination address/mask, protocol, source/dest port, TOS/mask, interface and direction) must match their respective fields in the packet for any given filter to match. To create an entry in this table, docsDevFilterIpIfIndex must be specified." INDEX { docsDevFilterIpIndex } ::= { docsDevFilterIpTable 1 } DocsDevFilterIpEntry ::= SEQUENCE { docsDevFilterIpIndex Integer32, docsDevFilterIpStatus RowStatus, docsDevFilterIpControl INTEGER, docsDevFilterIpIfIndex InterfaceIndexOrZero, docsDevFilterIpDirection INTEGER, docsDevFilterIpBroadcast TruthValue, docsDevFilterIpSaddr IpAddress, docsDevFilterIpSmask IpAddress, docsDevFilterIpDaddr IpAddress, docsDevFilterIpDmask IpAddress, docsDevFilterIpProtocol Integer32, docsDevFilterIpSourcePortLow Integer32, docsDevFilterIpSourcePortHigh Integer32, docsDevFilterIpDestPortLow Integer32, docsDevFilterIpDestPortHigh Integer32, docsDevFilterIpMatches Counter32, docsDevFilterIpTos OCTET STRING, docsDevFilterIpTosMask OCTET STRING, docsDevFilterIpContinue TruthValue, docsDevFilterIpPolicyId Integer32, docsDevFilterIpInterfaces OCTET STRING, docsDevFilterIpInterfaceSet InterfaceSet } docsDevFilterIpIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Index used to order the application of filters. The filter with the lowest index is always applied first." ::= { docsDevFilterIpEntry 1 } docsDevFilterIpStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "Controls and reflects the status of rows in this table. Specifying only this object (with the appropriate index) on a CM is sufficient to create a filter row which matches all inbound packets on the ethernet interface, and results in the packets being discarded. docsDevFilterIpIfIndex (at least) must be specified on a CMTS to create a row. Creation of the rows may be done via either create-and-wait or create-and-go, but the filter is not applied until this object is set to (or changes to) active. There is no restriction in changing any object in a row while this object is set to active." ::= { docsDevFilterIpEntry 2 } docsDevFilterIpControl OBJECT-TYPE SYNTAX INTEGER { discard(1), accept(2), policy(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "If set to discard(1), all packets matching this filter will be discarded and scanning of the remainder of the filter list will be aborted. If set to accept(2), all packets matching this filter will be accepted for further processing (e.g., bridging). If docsDevFilterIpContinue is set to true, see if there are other matches, otherwise done. If set to policy (3), execute the policy entries matched by docsDevIpFilterPolicyId in docsDevIpFilterPolicyTable. If is docsDevFilterIpContinue is set to true, continue scanning the table for other matches, otherwise done." DEFVAL { discard } ::= { docsDevFilterIpEntry 3 } docsDevFilterIpIfIndex OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS read-create STATUS deprecated DESCRIPTION "The entry interface to which this filter applies. The value corresponds to ifIndex for either a CATV MAC or another interface. If the value is zero, the filter applies to all interfaces. Default value in Cable Modems is the index of the customer-side (e.g. ethernet) interface. In Cable Modem Termination Systems, this object MUST be specified to create a row in this table. DEPRECATED. If the docsDevFilterIpInterfaces object exists in this agent and row, then the value of this object is ignored for purposes of filtering AND this object need not be specified to create a row in this table." ::= { docsDevFilterIpEntry 4 } docsDevFilterIpDirection OBJECT-TYPE SYNTAX INTEGER { inbound(1), outbound(2), both(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "Determines whether the filter is applied to inbound(1) traffic, outbound(2) traffic, or traffic in both(3) directions." DEFVAL { inbound } ::= { docsDevFilterIpEntry 5 } docsDevFilterIpBroadcast OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If set to true(1), the filter only applies to multicast and broadcast traffic. If set to false(2), the filter applies to all traffic." DEFVAL { false } ::= { docsDevFilterIpEntry 6 } docsDevFilterIpSaddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The source IP address, or portion thereof, that is to be matched for this filter. The source address is first masked (and'ed) against docsDevFilterIpSmask before being compared to this value. A value of 0 for this object and 0 for the mask matches all IP addresses." DEFVAL { '00000000'h } ::= { docsDevFilterIpEntry 7 } docsDevFilterIpSmask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "A bit mask that is to be applied to the source address prior to matching. This mask is not necessarily the same as a subnet mask, but 1's bits must be leftmost and contiguous." DEFVAL { '00000000'h } ::= { docsDevFilterIpEntry 8 } docsDevFilterIpDaddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The destination IP address, or portion thereof, that is to be matched for this filter. The destination address is first masked (and'ed) against docsDevFilterIpDmask before being compared to this value. A value of 0 for this object and 0 for the mask matches all IP addresses." DEFVAL { '00000000'h } ::= { docsDevFilterIpEntry 9 } docsDevFilterIpDmask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "A bit mask that is to be applied to the destination address prior to matching. This mask is not necessarily the same as a subnet mask, but 1's bits must be leftmost and contiguous." DEFVAL { '00000000'h } ::= { docsDevFilterIpEntry 10 } docsDevFilterIpProtocol OBJECT-TYPE SYNTAX Integer32 (0..256) MAX-ACCESS read-create STATUS current DESCRIPTION "The IP protocol value that is to be matched. For example: icmp is 1, tcp is 6, udp is 17. A value of 256 matches ANY protocol." DEFVAL { 256 } ::= { docsDevFilterIpEntry 11 } docsDevFilterIpSourcePortLow OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "If docsDevFilterIpProtocol is udp or tcp, this is the inclusive lower bound of the transport-layer source port range that is to be matched, otherwise it is ignored during matching." DEFVAL { 0 } ::= { docsDevFilterIpEntry 12 } docsDevFilterIpSourcePortHigh OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "If docsDevFilterIpProtocol is udp or tcp, this is the inclusive upper bound of the transport-layer source port range that is to be matched, otherwise it is ignored during matching." DEFVAL { 65535 } ::= { docsDevFilterIpEntry 13 } docsDevFilterIpDestPortLow OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "If docsDevFilterIpProtocol is udp or tcp, this is the inclusive lower bound of the transport-layer destination port range that is to be matched, otherwise it is ignored during matching." DEFVAL { 0 } ::= { docsDevFilterIpEntry 14 } docsDevFilterIpDestPortHigh OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "If docsDevFilterIpProtocol is udp or tcp, this is the inclusive upper bound of the transport-layer destination port range that is to be matched, otherwise it is ignored during matching." DEFVAL { 65535 } ::= { docsDevFilterIpEntry 15 } docsDevFilterIpMatches OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Counts the number of times this filter was matched. This object is initialized to 0 at boot, or at row creation, and is reset only upon reboot." ::= { docsDevFilterIpEntry 16 } docsDevFilterIpTos OBJECT-TYPE SYNTAX OCTET STRING ( SIZE (1)) MAX-ACCESS read-create STATUS current DESCRIPTION "This is the value to be matched to the packet's TOS (Type of Service) value (after the TOS value is AND'd with docsDevFilterIpTosMask). A value for this object of 0 and a mask of 0 matches all TOS values." DEFVAL { '00'h } ::= { docsDevFilterIpEntry 17 } docsDevFilterIpTosMask OBJECT-TYPE SYNTAX OCTET STRING ( SIZE (1) ) MAX-ACCESS read-create STATUS current DESCRIPTION "The mask to be applied to the packet's TOS value before matching." DEFVAL { '00'h } ::= { docsDevFilterIpEntry 18 } docsDevFilterIpContinue OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS deprecated DESCRIPTION "If this value is set to true, and docsDevFilterIpControl is anything but discard (1), continue scanning and applying policies. Deprecated. Upon read, this object SHOULD return false. The ability to continue scanning the filter list is deprecated and SHOULD NOT be implemented. An attempt to set this object to true SHOULD succeed, but SHOULD NOT actually set the underlying value of the object to true in the agent." DEFVAL { false } ::= { docsDevFilterIpEntry 19 } docsDevFilterIpPolicyId OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "This object points to an entry in docsDevFilterPolicyTable. If docsDevFilterIpControl is set to policy (3), execute all matching policies in docsDevFilterPolicyTable. If no matching policy exists, treat as if docsDevFilterIpControl were set to accept (1). If this object is set to the value of 0, there is no matching policy, and docsDevFilterPolicyTable MUST NOT be consulted." DEFVAL { 0 } ::= { docsDevFilterIpEntry 20 } docsDevFilterIpInterfaces OBJECT-TYPE SYNTAX OCTET STRING (SIZE (1..32)) MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the set of interfaces this filter applies to. Each octet within the value of this object specifies a set of eight interfaces, with the first octet spefifying interfaces 1 through 8, the second octet specifying interfaces 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered interface, and the least significant bit represents the highest numbered interface. Thus, each interface is represented by a single bit within the value of this object. If that bit has a value of '1' then that interface is included in this set." ::= { docsDevFilterIpEntry 21 } docsDevFilterIpInterfaceSet OBJECT-TYPE SYNTAX InterfaceSet MAX-ACCESS read-create STATUS current DESCRIPTION "This is a convenience object for setting the value of docsDevFilterIpInterfaces. Upon read this always returns other (1). Upon a valid set, this causes docsDevFilterIpInterfaces in the same row to be set to a bit mask set consisting of the interfaces which match the class type represented by this object." DEFVAL { allCpe } ::= { docsDevFilterIpEntry 22 } -- -- docsDevFilterPolicyTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevFilterPolicyEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A Table which maps between a policy group ID and a set of policies to be applied. All rows with the same docsDevFilterPolicyId are part of the same policy group and are applied in the order in which they are in this table. docsDevFilterPolicyTable exists to allow multiple policy actions to be applied to any given classified packet. The policy actions are applied in index order For example: Index ID Type Action 1 1 TOS 1 9 5 TOS 1 12 1 IPSEC 3 This says that a packet which matches a filter with policy id 1, first has TOS policy 1 applied (which might set the TOS bits to enable a higher priority), and next has the IPSEC policy 3 applied (which may result in the packet being dumped into a secure VPN to a remote encryptor). Policy ID 0 is reserved for default actions and is applied only to packets which match no filters in docsDevIpFilterTable." ::= { docsDevFilter 5 } docsDevFilterPolicyEntry OBJECT-TYPE SYNTAX DocsDevFilterPolicyEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the docsDevFilterPolicyTable. Entries are created by Network Management. To create an entry, docsDevFilterPolicyId and docsDevFilterPolicyAction must be specified." INDEX { docsDevFilterPolicyIndex } ::= { docsDevFilterPolicyTable 1 } DocsDevFilterPolicyEntry ::= SEQUENCE { docsDevFilterPolicyIndex Integer32, docsDevFilterPolicyId Integer32, docsDevFilterPolicyStatus RowStatus, docsDevFilterPolicyPtr RowPointer } docsDevFilterPolicyIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Index value for the table." ::= { docsDevFilterPolicyEntry 1 } docsDevFilterPolicyId OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "Policy ID for this entry. A policy ID can apply to multiple rows of this table, all relevant policies are executed. Policy 0 (if populated) is applied to all packets which do not match any of the filters. N.B. If docsDevFilterIpPolicyId is set to 0, it DOES NOT match policy 0 of this table. " ::= { docsDevFilterPolicyEntry 2 } -- docsDevFilterPolicyType ::= { docsDevFilterPolicyEntry 3} Removed -- docsDevFilterPolicyAction ::= { docsDevFilterPolicyEntry 4 } removed docsDevFilterPolicyStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "Object used to create an entry in this table." ::= { docsDevFilterPolicyEntry 5 } docsDevFilterPolicyPtr OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "This object points to a row in an applicable filter policy table. Currently, the only standard policy table is docsDevFilterTosTable. Per the textual convention, this object points to the first accessible object in the row. E.g. to point to a row in docsDevFilterTosTable with an index of 21, the value of this object would be the object identifier docsDevTosStatus.21. Vendors must adhere to the same convention when adding vendor specific policy table extensions. The default upon row creation is a null pointer which results in no policy action being taken." DEFVAL { zeroDotZero } ::= { docsDevFilterPolicyEntry 6 } -- -- TOS Policy action table -- docsDevFilterTosTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevFilterTosEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table used to describe Type of Service (TOS) bits processing. This table is an adjunct to the docsDevFilterIpTable, and the docsDevFilterPolicy table. Entries in the latter table can point to specific rows in this (and other) tables and cause specific actions to be taken. This table permits the manipulation of the value of the Type of Service bits in the IP header of the matched packet as follows: Set the tosBits of the packet to (tosBits & docsDevFilterTosAndMask) | docsDevFilterTosOrMask This construct allows you to do a clear and set of all the TOS bits in a flexible manner." ::= { docsDevFilter 6 } docsDevFilterTosEntry OBJECT-TYPE SYNTAX DocsDevFilterTosEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A TOS policy entry." INDEX { docsDevFilterTosIndex } ::= { docsDevFilterTosTable 1 } DocsDevFilterTosEntry ::= SEQUENCE { docsDevFilterTosIndex Integer32, docsDevFilterTosStatus RowStatus, docsDevFilterTosAndMask OCTET STRING (SIZE (1)), docsDevFilterTosOrMask OCTET STRING (SIZE (1)) } docsDevFilterTosIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The unique index for this row. There are no ordering requirements for this table and any valid index may be specified." ::= { docsDevFilterTosEntry 1 } docsDevFilterTosStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The object used to create and delete entries in this table. A row created by specifying just this object results in a row which specifies no change to the TOS bits. A row may be created using either the create-and-go or create-and-wait paradigms. There is no restriction on the ability to change values in this row while the row is active." ::= { docsDevFilterTosEntry 2 } docsDevFilterTosAndMask OBJECT-TYPE SYNTAX OCTET STRING (SIZE (1)) MAX-ACCESS read-create STATUS current DESCRIPTION "This value is bitwise AND'd with the matched packet's TOS bits." DEFVAL { 'ff'h } ::= { docsDevFilterTosEntry 3 } docsDevFilterTosOrMask OBJECT-TYPE SYNTAX OCTET STRING (SIZE (1)) MAX-ACCESS read-create STATUS current DESCRIPTION "After bitwise AND'ing with the above bits, the packet's TOS bits are bitwise OR'd with these bits, and the packet's TOS BITS are set to that value." DEFVAL { '00'h } ::= { docsDevFilterTosEntry 4 } docsDevFilterIpV6AuxTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevFilterIpV6AuxEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table augments docsDevIpFilterTable with objects that allow filtering of IPv6 packets." ::= { docsDevFilter 7 } docsDevFilterIpV6AuxEntry OBJECT-TYPE SYNTAX DocsDevFilterIpV6AuxEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This augments the existing objects in docsDevFilterIpEntry, but by default the objects in this entry have not effect on filtering as docsDevFilterIpType defaults to ipv4 upon row creation." AUGMENTS {docsDevFilterIpEntry } ::= {docsDevFilterIpV6AuxTable 1 } DocsDevFilterIpV6AuxEntry ::= SEQUENCE { docsDevFilterIpType INTEGER, docsDevFilterIpV6Saddr Ipv6Address, docsDevFilterIpV6Smask Ipv6Address, docsDevFilterIpV6Daddr Ipv6Address, docsDevFilterIpV6Dmask Ipv6Address } docsDevFilterIpType OBJECT-TYPE SYNTAX INTEGER { ipv4(1), ipv6(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "This object controls whether this filter entry refers to IP v4 or v6 type packets. If this object is ipv4, then the IpAddress objects docsDevFilterEntry apply, otherwise if this object is ipv6 then the remaining objects in this entry apply." DEFVAL { ipv4 } ::= { docsDevFilterIpV6AuxEntry 1} docsDevFilterIpV6Saddr OBJECT-TYPE SYNTAX Ipv6Address MAX-ACCESS read-create STATUS current DESCRIPTION "The source address IPv6 address or portion thereof that is to be matched for this filter. The packet's source address is first masked (and'ed) aginst docsDevFilterIpV6Smask before being compared to this value. A value of of zero for this object and for the mask matches all IPv6 addresses." DEFVAL { '00000000000000000000000000000000'h } ::= { docsDevFilterIpV6AuxEntry 2 } docsDevFilterIpV6Smask OBJECT-TYPE SYNTAX Ipv6Address MAX-ACCESS read-create STATUS current DESCRIPTION "A bit mask that is to be applied to the packet's source address prior to matching. The mask is not necessarily the same as a subnet mask, the the 1's bits must be leftmost and contiguous." DEFVAL { '00000000000000000000000000000000'h } ::= { docsDevFilterIpV6AuxEntry 3 } docsDevFilterIpV6Daddr OBJECT-TYPE SYNTAX Ipv6Address MAX-ACCESS read-create STATUS current DESCRIPTION "The destination address IPv6 address or portion thereof that is to be matched for this filter. The packet's source address is first masked (and'ed) aginst docsDevFilterIpV6Dmask before being compared to this value. A value of of zero for this object and for the mask matches all IPv6 addresses." DEFVAL { '00000000000000000000000000000000'h } ::= { docsDevFilterIpV6AuxEntry 4 } docsDevFilterIpV6Dmask OBJECT-TYPE SYNTAX Ipv6Address MAX-ACCESS read-create STATUS current DESCRIPTION "A bit mask that is to be applied to the packet's destination address prior to matching. The mask is not necessarily the same as a subnet mask, the the 1's bits must be leftmost and contiguous." DEFVAL { '00000000000000000000000000000000'h } ::= { docsDevFilterIpV6AuxEntry 5 } -- -- CPE IP Management and anti spoofing group. Only implemented on -- Cable Modems. -- docsDevCpe OBJECT IDENTIFIER ::= { docsDevMIBObjects 7} docsDevCpeEnroll OBJECT-TYPE SYNTAX INTEGER { none(1), any(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object controls the population of docsDevFilterCpeTable. If set to none, the filters must be set manually. If set to any, the CM wiretaps the packets originating from the ethernet and enrolls up to docsDevCpeIpMax addresses based on the source IPv4 or v6 addresses of those packets. At initial system startup, default value for this object is any(2)." ::= { docsDevCpe 1 } docsDevCpeIpMax OBJECT-TYPE SYNTAX Integer32 (-1..2147483647) MAX-ACCESS read-write STATUS current DESCRIPTION "This object controls the maximum number of CPEs allowed to be learned behind this device. If set to zero, any number of CPEs may connect up to the maximum permitted for the device. If set to -1, no filtering is done on CPE source addresses, and no entries are made in the docsDevFilterCpeTable via learning. If an attempt is made to set this to a number greater than that permitted for the device, it is set to that maximum. At initial system startup, default value for this object is -1." ::= { docsDevCpe 2 } docsDevCpeTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevCpeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table lists the IP addresses seen (or permitted) as source addresses in packets originating from the customer interface on this device. In addition, this table can be provisioned with the specific addresses permitted for the CPEs via the normal row creation mechanisms. N.B. Management action can add entries in this table and in docsDevCpeIpTable past the value of docsDevCpeIpMax. docsDevCpeIpMax ONLY restricts the ability of the CM to automatically add learned addresses." ::= { docsDevCpe 3 } docsDevCpeEntry OBJECT-TYPE SYNTAX DocsDevCpeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the docsDevFilterCpeTable. There is one entry for each IP CPE seen or provisioned. If docsDevCpeIpMax is set to -1, this table is ignored, otherwise: Upon receipt of an IP packet from the customer interface of the CM, the source IP address is checked against this table. If the address is in the table, packet processing continues. If the address is not in the table, but docsDevCpeEnroll is set to any and the sum of the table sizes of docsDevCpeTable and docsDevCpeV6Table is less than docsDevCpeIpMax, the address is added to the table and packet processing continues. Otherwise, the packet is dropped. The filtering actions specified by this table occur after any LLC filtering (docsDevFilterLLCTable), but prior to any IP filtering (docsDevFilterIpTable, docsDevNmAccessTable)." INDEX { docsDevCpeIp } ::= {docsDevCpeTable 1 } DocsDevCpeEntry ::= SEQUENCE { docsDevCpeIp IpAddress, docsDevCpeSource INTEGER, docsDevCpeStatus RowStatus } docsDevCpeIp OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The IP address to which this entry applies. N.B. Neither the all zeros or all ones addresses may be used as the value of this object." ::= { docsDevCpeEntry 1 } docsDevCpeSource OBJECT-TYPE SYNTAX INTEGER { other(1), manual(2), learned(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object describes how this entry was created. If the value is manual(2), this row was created by a network management action (either configuration, or SNMP set). If set to learned(3), then it was found via looking at the source IP address of a received packet." ::= { docsDevCpeEntry 2 } docsDevCpeStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "Standard object to manipulate rows. To create a row in this table, you only need to specify this object. Management stations SHOULD use the create-and-go mechanism for creating rows in this table." ::= { docsDevCpeEntry 3 } docsDevCpeV6Table OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevCpeV6Entry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table lists the IP V6 addresses seen (or permitted) as source addresses in packets originating from the customer interface on this device. In addition, this table can be provisioned with the specific addresses permitted for the CPEs via the normal row creation mechanisms. N.B. Management action can add entries in this table and in docsDevCpeIpTable past the value of docsDevCpeIpMax. docsDevCpeIpMax ONLY restricts the ability of the CM to automatically add learned addresses. This table exactly mirrors docsDevCpeTable and applies only to IPv6 addresses." ::= { docsDevCpe 4 } docsDevCpeV6Entry OBJECT-TYPE SYNTAX DocsDevCpeV6Entry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the docsDevFilterCpeTable. There is one entry for each IP V6 CPE seen or provisioned. If docsDevCpeIpMax is set to -1, this table is ignored, otherwise: Upon receipt of an IPv6 packet from the customer interface of the CM, the source IP address is checked against this table. If the address is in the table, packet processing continues. If the address is not in the table, but docsDevCpeEnroll is set to any and the sum of the table sizes for docsDevCpeTable and docsDevCpeV6Tble is less than docsDevCpeIpMax, the address is added to the table and packet processing continues. Otherwise, the packet is dropped. The filtering actions specified by this table occur after any LLC filtering (docsDevFilterLLCTable), but prior to any IP filtering (docsDevFilterIpTable, docsDevNmAccessTable)." INDEX { docsDevCpeV6Ip } ::= {docsDevCpeV6Table 1 } DocsDevCpeV6Entry ::= SEQUENCE { docsDevCpeV6Ip Ipv6Address, docsDevCpeV6Source INTEGER, docsDevCpeV6Status RowStatus } docsDevCpeV6Ip OBJECT-TYPE SYNTAX Ipv6Address MAX-ACCESS not-accessible STATUS current DESCRIPTION "The IP address to which this entry applies. N.B. Neither the all zeros or all ones addresses may be used as values for this object." ::= { docsDevCpeV6Entry 1 } docsDevCpeV6Source OBJECT-TYPE SYNTAX INTEGER { other(1), manual(2), learned(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object describes how this entry was created. If the value is manual(2), this row was created by a network management action (either configuration, or SNMP set). If set to learned(3), then it was found via looking at the source IP address of a received packet." ::= { docsDevCpeV6Entry 2 } docsDevCpeV6Status OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "Standard object to manipulate rows. To create a row in this table, you only need to specify this object. Management stations SHOULD use the create-and-go mechanism for creating rows in this table." ::= { docsDevCpeV6Entry 3 } docsDevVacmAccessExtTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevVacmAccessExtEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "" ::= { docsDevMIBObjects 8 } docsDevVacmAccessExtEntry OBJECT-TYPE SYNTAX DocsDevVacmAccessExtEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "" AUGMENTS { vacmAccessEntry } ::= {docsDevVacmAccessExtTable 1 } DocsDevVacmAccessExtEntry ::= SEQUENCE { docsDevVacmAccessInterfaces OCTET STRING, docsDevVacmAccessInterfaceSet InterfaceSet } docsDevVacmAccessInterfaces OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1..32)) MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the set of interfaces this filter applies to. Each octet within the value of this object specifies a set of eight interfaces, with the first octet spefifying interfaces 1 through 8, the second octet specifying interfaces 9 through 16 etc. Within each octet, the most significant bit represents the lowest numbered interface, and the least significant bit represents the highest numbered interface. Thus, each interface is represented by a single bit within the value of this object. If that bit has a value of '1' then that interface is included in this set." ::= { docsDevVacmAccessExtEntry 1 } docsDevVacmAccessInterfaceSet OBJECT-TYPE SYNTAX InterfaceSet MAX-ACCESS read-create STATUS current DESCRIPTION "This is a convenience object for setting the value of docsDevVacmAccessInterfaces. Upon read this always returns other (1). Upon a valid set, this causes docsDevVacmAccessInterfaces in the same row to be set to a bit mask set consisting of the interfaces which match the class type represented by this object." DEFVAL { all } ::= { docsDevVacmAccessExtEntry 2 } -- -- Placeholder for notifications/traps. -- docsDevNotification OBJECT IDENTIFIER ::= { docsDev 2 } -- -- Conformance definitions -- docsDevConformance OBJECT IDENTIFIER ::= { docsDev 3 } docsDevGroups OBJECT IDENTIFIER ::= { docsDevConformance 1 } docsDevCompliances OBJECT IDENTIFIER ::= { docsDevConformance 2 } docsDevBasicCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for MCNS Cable Modems and Cable Modem Termination Systems." MODULE -- docsDev -- conditionally mandatory groups GROUP docsDevBaseGroup DESCRIPTION "Mandatory in Cable Modems, optional in Cable Modem Termination Systems." GROUP docsDevEventGroup DESCRIPTION "Mandatory in Cable Modems, optional in Cable Modem Termination Systems." GROUP docsDevFilterGroup DESCRIPTION "Mandatory in Cable Modems, optional in Cable Modem Termination Systems." GROUP docsDevNmAccessGroup DESCRIPTION "This group is only implemented in devices which do not implement SNMPv3 User Security Model. It SHOULD NOT be implemented by SNMPv3 conformant devices. For devices which do not implement SNMPv3 or later, this group is Mandatory in Cable Modems and is optional in Cable Modem Termination Systems." GROUP docsDevServerGroup DESCRIPTION "This group is implemented only in Cable Modems and is not implemented in Cable Modem Termination Systems." GROUP docsDevSoftwareGroup DESCRIPTION "This group is Mandatory in Cable Modems and optional in Cable Modem Termination Systems." GROUP docsDevCpeGroup DESCRIPTION "This group is Mandatory in Cable Modems, and is not implemented in Cable Modem Termination Systems. A similar capability for CMTS devices may be proposed later after study." OBJECT docsDevSTPControl MIN-ACCESS read-only DESCRIPTION "It is compliant to implement this object as read-only. Devices need only support noStFilterBpdu(2)." OBJECT docsDevEvReporting MIN-ACCESS read-only DESCRIPTION "It is compliant to implement this object as read-only. Devices need only support local(0)." OBJECT docsDevFilterLLCInterfaceSet WRITE-SYNTAX INTEGER { allCpe(2), allNetwork (3), allCpeEthernet (4), allCpeUsb (5), allCpeFirewire (6), allExternal (7), allInternal (8), all (9), application1 (10), application2 (11), application3 (12), application4 (13) } DESCRIPTION "'other' is a return value only and may not be SET." OBJECT docsDevFilterIpInterfaceSet WRITE-SYNTAX INTEGER { allCpe(2), allNetwork (3), allCpeEthernet (4), allCpeUsb (5), allCpeFirewire (6), allExternal (7), allInternal (8), all (9), application1 (10), application2 (11), application3 (12), application4 (13) } DESCRIPTION "'other' is a return value only and may not be SET." ::= { docsDevCompliances 1 } docsDevBaseGroup OBJECT-GROUP OBJECTS { docsDevRole, docsDevDateTime, docsDevResetNow, docsDevSerialNumber, docsDevSTPControl } STATUS current DESCRIPTION "A collection of objects providing device status and control." ::= { docsDevGroups 1 } docsDevNmAccessGroup OBJECT-GROUP OBJECTS { docsDevNmAccessIp, docsDevNmAccessIpMask, docsDevNmAccessCommunity, docsDevNmAccessControl, docsDevNmAccessInterfaces, docsDevNmAccessStatus } STATUS deprecated DESCRIPTION "A collection of objects for controlling access to SNMP objects. Deprecated in favor of SNMPv3 and coexistence MIB." ::= { docsDevGroups 2 } docsDevSoftwareGroup OBJECT-GROUP OBJECTS { -- docsDevSwServer, docsDevSwFilename, docsDevSwAdminStatus, docsDevSwOperStatus, docsDevSwCurrentVers, docsDevSwServerAddress } STATUS current DESCRIPTION "A collection of objects for controlling software downloads." ::= { docsDevGroups 3 } docsDevServerGroup OBJECT-GROUP OBJECTS { docsDevServerBootState, -- docsDevServerDhcp, -- docsDevServerTime, -- docsDevServerTftp, docsDevServerDhcpAddress, docsDevServerTimeAddress, docsDevServerConfigTftpAddress, docsDevServerConfigFile } STATUS current DESCRIPTION "A collection of objects providing status about server provisioning." ::= { docsDevGroups 4 } docsDevEventGroup OBJECT-GROUP OBJECTS { docsDevEvControl, -- docsDevEvSyslog, docsDevEvThrottleAdminStatus, docsDevEvThrottleInhibited, docsDevEvThrottleThreshold, docsDevEvThrottleInterval, docsDevEvReporting, docsDevEvFirstTime, docsDevEvLastTime, docsDevEvCounts, docsDevEvLevel, docsDevEvId, docsDevEvText, docsDevEvSyslogAddress } STATUS current DESCRIPTION "A collection of objects used to control and monitor events." ::= { docsDevGroups 5 } docsDevFilterGroup OBJECT-GROUP OBJECTS { docsDevFilterLLCUnmatchedAction, docsDevFilterIpDefault, docsDevFilterLLCStatus, -- docsDevFilterLLCIfIndex, docsDevFilterLLCProtocolType, docsDevFilterLLCProtocol, docsDevFilterLLCMatches, docsDevFilterLLCInterfaces, docsDevFilterLLCInterfaceSet, docsDevFilterIpControl, -- docsDevFilterIpIfIndex, docsDevFilterIpStatus, docsDevFilterIpDirection, docsDevFilterIpBroadcast, docsDevFilterIpSaddr, docsDevFilterIpSmask, docsDevFilterIpDaddr, docsDevFilterIpDmask, docsDevFilterIpProtocol, docsDevFilterIpSourcePortLow, docsDevFilterIpSourcePortHigh, docsDevFilterIpDestPortLow, docsDevFilterIpDestPortHigh, docsDevFilterIpMatches, docsDevFilterIpInterfaces, docsDevFilterIpInterfaceSet, docsDevFilterIpTos, docsDevFilterIpTosMask, -- docsDevFilterIpContinue, docsDevFilterIpPolicyId, docsDevFilterPolicyId, docsDevFilterPolicyStatus, docsDevFilterPolicyPtr, docsDevFilterTosStatus, docsDevFilterTosAndMask, docsDevFilterTosOrMask } STATUS current DESCRIPTION "A collection of objects to specify filters at link layer and IP layer." ::= { docsDevGroups 6 } docsDevCpeGroup OBJECT-GROUP OBJECTS { docsDevCpeEnroll, docsDevCpeIpMax, docsDevCpeSource, docsDevCpeStatus } STATUS current DESCRIPTION "A collection of objects used to control the number and specific values of IP addresses allowed for associated Customer Premises Equipment (CPE)." ::= { docsDevGroups 7 } docsDevDeprecatedGroup OBJECT-GROUP OBJECTS { docsDevFilterLLCIfIndex, docsDevFilterIpIfIndex, docsDevFilterIpContinue, docsDevSwServer, docsDevServerDhcp, docsDevServerTime, docsDevServerTftp, docsDevEvSyslog } STATUS deprecated DESCRIPTION "These objects have been deprecated to deal with the IPv6, SNMPv3 and redefinition of the CM as a multiple CPE device. They MAY be implemented, but will be removed in the next iteration of this MIB." ::= { docsDevGroups 8 } docsDevIpV6Group OBJECT-GROUP OBJECTS { docsDevFilterIpType, docsDevFilterIpV6Saddr, docsDevFilterIpV6Smask, docsDevFilterIpV6Daddr, docsDevFilterIpV6Dmask, docsDevCpeV6Source, docsDevCpeV6Status } STATUS current DESCRIPTION "These objects were added to deal with the filtering of IPV6 addresses. They MUST be implemented in any IPv6 aware cable modem." ::= { docsDevGroups 9 } docsDevSnmpCoexistGroup OBJECT-GROUP OBJECTS { docsDevVacmAccessInterfaces, docsDevVacmAccessInterfaceSet } STATUS current DESCRIPTION "These objects were added to retain the capability to restrict SNMP access on a per interface basis." ::= { docsDevGroups 10 } END --==_Exmh_-8111811010-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org http://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Tue May 16 14:39:20 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10917; Tue, 16 May 2000 14:39:20 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA25694; Tue, 16 May 2000 14:37:16 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA25665 for ; Tue, 16 May 2000 14:37:14 -0400 (EDT) Received: from dmzraw1.extranet.tce.com (dmzraw1.extranet.tce.com [157.254.234.131]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10872 for ; Tue, 16 May 2000 14:37:13 -0400 (EDT) Received: from smtprelay.tce.com ([157.254.96.114]) by dmzraw1.extranet.tce.com (8.9.3/8.9.1) with ESMTP id NAA19147 for ; Tue, 16 May 2000 13:36:43 -0500 (EST) Received: from indyexch1.indy.tce.com (localhost [127.0.0.1]) by smtprelay.tce.com (8.9.3/8.9.1) with ESMTP id NAA25945 for ; Tue, 16 May 2000 13:36:43 -0500 (EST) Received: by indyexch1.indy.tce.com with Internet Mail Service (5.5.2650.21) id ; Tue, 16 May 2000 13:38:11 -0500 Message-ID: <4FA371B64BDAD2119CF40008C7D9ADB302B96D53@indyexch5.indy.tce.com> From: Yost William To: ipcdn@ietf.org Subject: RE: [ipcdn] Revised bare mib - Cable Device Mib Date: Tue, 16 May 2000 13:37:30 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org The docsDevSnmpCoexistGroup isn't mentioned in a GROUP statement in the MODULE-COMPLIANCE section. Does this mean that group is optional? Should it be mentioned in the MODULE-COMPLIANCE section and declared to be optional or mandatory? ----------- Here is the group -------------------------- docsDevSnmpCoexistGroup OBJECT-GROUP OBJECTS { docsDevVacmAccessInterfaces, docsDevVacmAccessInterfaceSet } STATUS current DESCRIPTION "These objects were added to retain the capability to restrict SNMP access on a per interface basis." ::= { docsDevGroups 10 } --- William H. Yost, Thomson Consumer Electronics: (317) 587-4816 --- . Home of RCA, Proscan, GE electronics . . (There is no letter P in the name Thomson) . -----Original Message----- From: Mike StJohns [mailto:stjohns@corp.home.net] Sent: Monday, May 15, 2000 7:26 PM To: ipcdn@ietf.org Subject: [ipcdn] Revised bare mib - Cable Device Mib I've attached the most recent version of the cable device mib, bare of the surrounding internet draft (this will follow shortly). I think its pretty much in good shape, however there's one issue I need input on from the list. Back when we re-did filtering, I added the "continue" object in the filtering set to deal with things where you might want to apply multiple policies (e.g. filtering and TOS marking and IPSEC). To date, this hasn't been used because we haven't yet done TOS marking or any of the QOS stuff. My first inclination is to yank it out as it adds to the complexity of the filtering code, BUT - the above requirements still remain. If we had more experience with the QOS stuff I'd be more confident one way or the other. Right now, I'm leaning towards leaving it in (even though this version of the mib has it marked as deprecated). This mib clean compiles under smicng - with the appropriate options. You'll need to grab a copy of the IPV6-TC mib - see the mib for the RFC number. Comments? Mike _______________________________________________ IPCDN mailing list IPCDN@ietf.org http://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Tue May 16 15:34:24 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11698; Tue, 16 May 2000 15:34:24 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26287; Tue, 16 May 2000 15:33:42 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26261 for ; Tue, 16 May 2000 15:33:36 -0400 (EDT) Received: from zipcode.corp.home.net (zipcode.corp.home.net [24.0.26.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11688 for ; Tue, 16 May 2000 15:33:34 -0400 (EDT) Received: from lock.eos.home.net (root@lock.eos.home.net [24.0.16.84]) by zipcode.corp.home.net (8.9.3/8.9.3) with ESMTP id MAA05754; Tue, 16 May 2000 12:33:29 -0700 (PDT) Received: from lock.eos.home.net (stjohns@localhost [127.0.0.1]) by lock.eos.home.net (8.9.1/8.8.5) with ESMTP id MAA01978; Tue, 16 May 2000 12:33:26 -0700 (PDT) Message-Id: <200005161933.MAA01978@lock.eos.home.net> X-Mailer: exmh version 2.0delta 6/3/97 To: Yost William cc: ipcdn@ietf.org Subject: Re: [ipcdn] Revised bare mib - Cable Device Mib In-reply-to: Your message of Tue, 16 May 2000 13:37:30 -0500. <4FA371B64BDAD2119CF40008C7D9ADB302B96D53@indyexch5.indy.tce.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 May 2000 12:33:25 -0700 From: "Mike StJohns" Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org I said it clean compiles, I didn't say it was exactly correct! :-) You're correct, I need to add the various group compliance statements. Basically "This group MUST be implemented in any CM that contains an SNMPv3 agent. It MAY be implemented in any CM that supports VACM." is the statement for that group. Note that there's some language for the two reference objects to ensure the default values of the object don't affect normal evaluation. Mike > The docsDevSnmpCoexistGroup isn't mentioned in a GROUP statement in the > MODULE-COMPLIANCE section. Does this mean that group is optional? Should > it be mentioned in the MODULE-COMPLIANCE section and declared to be optional > or mandatory? > > ----------- Here is the group -------------------------- > docsDevSnmpCoexistGroup OBJECT-GROUP > OBJECTS { > docsDevVacmAccessInterfaces, > docsDevVacmAccessInterfaceSet > } > STATUS current > DESCRIPTION > "These objects were added to retain the capability to > restrict SNMP access on a per interface basis." > ::= { docsDevGroups 10 } > > --- William H. Yost, Thomson Consumer Electronics: (317) 587-4816 --- > . Home of RCA, Proscan, GE electronics . > . (There is no letter P in the name Thomson) . > > > -----Original Message----- > From: Mike StJohns [mailto:stjohns@corp.home.net] > Sent: Monday, May 15, 2000 7:26 PM > To: ipcdn@ietf.org > Subject: [ipcdn] Revised bare mib - Cable Device Mib > > > > I've attached the most recent version of the cable device mib, bare of the > surrounding internet draft (this will follow shortly). I think its pretty > much in good shape, however there's one issue I need input on from the list. > > Back when we re-did filtering, I added the "continue" object in the > filtering > set to deal with things where you might want to apply multiple policies > (e.g. > filtering and TOS marking and IPSEC). To date, this hasn't been used > because > we haven't yet done TOS marking or any of the QOS stuff. My first > inclination > is to yank it out as it adds to the complexity of the filtering code, BUT - > the above requirements still remain. If we had more experience with the QOS > > stuff I'd be more confident one way or the other. Right now, I'm leaning > towards leaving it in (even though this version of the mib has it marked as > deprecated). This mib clean compiles under smicng - with the appropriate > options. You'll need to grab a copy of the IPV6-TC mib - see the mib for > the > RFC number. > > Comments? Mike > > > > _______________________________________________ > IPCDN mailing list > IPCDN@ietf.org > http://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ IPCDN mailing list IPCDN@ietf.org http://www1.ietf.org/mailman/listinfo/ipcdn