From mailman-bounces@ietf.org Wed Dec 1 07:43:17 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23353 for ; Wed, 1 Dec 2004 07:43:17 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZTuc-0007Wc-0f for ipcdn-archive@ietf.org; Wed, 01 Dec 2004 07:48:50 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZSLX-0001Pt-Mb for ipcdn-archive@ietf.org; Wed, 01 Dec 2004 06:08:31 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: ietf.org mailing list memberships reminder From: mailman-owner@ietf.org To: ipcdn-archive@ietf.org X-No-Archive: yes Message-ID: Date: Wed, 01 Dec 2004 05:40:29 -0500 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list X-List-Administrivia: yes Sender: mailman-bounces@ietf.org Errors-To: mailman-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Content-Transfer-Encoding: 7bit This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. ********************************************************************** NOTE WELL: Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: o the IETF plenary session, o any IETF working group or portion thereof, o the IESG, or any member thereof on behalf of the IESG, o the IAB or any member thereof on behalf of the IAB, o any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, o the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3667 and RFC 3668. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3667 for details. ******************************************************************************* If you have questions, problems, comments, etc, send them to mailman-owner@ietf.org. Thanks! Passwords for ipcdn-archive@ietf.org: List Password // URL ---- -------- ipcdn@ietf.org ichuas https://www1.ietf.org/mailman/options/ipcdn/ipcdn-archive%40ietf.org From ipcdn-bounces@ietf.org Wed Dec 1 20:16:38 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19163 for ; Wed, 1 Dec 2004 20:16:38 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZffl-0002jF-Gm for ipcdn-archive@ietf.org; Wed, 01 Dec 2004 20:22:18 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZfNB-0003IQ-5d; Wed, 01 Dec 2004 20:03:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZfAD-0001gV-Gn for ipcdn@megatron.ietf.org; Wed, 01 Dec 2004 19:49:41 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17435 for ; Wed, 1 Dec 2004 19:49:38 -0500 (EST) Received: from ondar.cablelabs.com ([192.160.73.61]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZfFd-0002CK-4H for ipcdn@ietf.org; Wed, 01 Dec 2004 19:55:18 -0500 Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20]) by ondar.cablelabs.com (8.12.10/8.12.10) with ESMTP id iB20n21e000403; Wed, 1 Dec 2004 17:49:02 -0700 (MST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 1 Dec 2004 17:49:02 -0700 Message-ID: Thread-Topic: DRAFT Meeting notes from IETF 61 IPCDN meeting in Washington DC Thread-Index: AcSGETA7YL1c/WVvTxWNSmZECb/jPRR90GvQ From: "Jean-Francois Mule" To: X-Approved: ondar X-Spam-Score: 0.3 (/) X-Scan-Signature: d49da3f50144c227c0d2fac65d3953e6 Cc: "Wijnen, Bert \(Bert\)" , "Richard Woundy @ Comcast" Subject: [ipcdn] DRAFT Meeting notes from IETF 61 IPCDN meeting in Washington DC X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP over Cable Data Network List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1307385538==" Sender: ipcdn-bounces@ietf.org Errors-To: ipcdn-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 715d0e6950aaebd45af78ef9318d0186 This is a multi-part message in MIME format. --===============1307385538== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4D808.B78E4E92" This is a multi-part message in MIME format. ------_=_NextPart_001_01C4D808.B78E4E92 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Below are the draft meeting notes from our IETF 61 meeting. Thanks to Greg Nakanishi for capturing them. Let me know if =20 I missed anything. =20 Jean-Francois. IETF IPCDN Meeting Notes Washington D.C., USA Tuesday November 9, 2004 Reported by Greg Nakanishi (gnakanishi@motorola.com) Edited by Jean-Francois Mule' (jfm@cablelabs.com) --- WG Meeting Summary --- ------------------ Ten to fifteen attendees of the IP over Cable Data Networks WG met at the IETF meeting in Washington DC on November 9, 2004. Total meeting time was about one hour. The meeting materials are consolidated into 1 deck of slides and will be provided as part of the IETF proceedings. They are also posted at http://www.ipcdn.org/meetings.html We won't summarize the content of the meeting in details, please read the slides for the current wg item status. - Summary of decisions made and Action Items (AI) o WG Charter update We are close to finishing the following MIBs (WGLC passed, some have passed IETF Last Call, some are about to be in "publication requested status): - updated IPCDN DOCSIS RF MIB (Proposed Standard) - IPCDN DOCSIS Event Notification MIB (Proposed Standard) - PacketCable/IPCableCom MTA device MIB (Proposed Standard) - PacketCable/IPCableCom MTA signaling MIB (Proposed Standard) The WG charter should be revised to change the following milestones: - IPCDN PacketCable/IPCablecom Management Event MIB (draft 03 is expired, new target date required - Dec04? TBD) - IPCDN DOCSIS Cable Device MIB v2 (draft06 is expired, new editor to be assigned, new target date TBD) - CableHome MIBs (IDs are expired, target completion date of Dec04 is unlikely to be met; new target date TBD). # AI: WG chairs to follow-up with AD Bert Wijnen to revise charter # once commitment is secured from ID authors & editors. o draft-ietf-ipcdn-subscriber-mib-16.txt =20 http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-subscriber-mib-16.t xt Status: RFC Editor Queue Draft 16 addressed all IESG comments; work concluded on this ID, awaiting publication. Many thanks to Wilson Sawyer for his continued work on this work item. No AI. o draft-ietf-ipcdn-qos-mib-10.txt http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-qos-mib-10.txt Status: IETF Last Call started on 2004-11-04; ended on 2004-11-21. # open issue: rooting of the MIB module under mib-2 need to be # addressed; wg chairs to resolve it after IETF Last Call. o draft-ietf-ipcdn-docsisevent-mib-04.txt =20 http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docsisevent-mib-04. txt Status: AD Review ID draft 03 reviewed by MIB doctor Harrie. # AI: chairs to ping AD Bert after IETF to see if AD review is # complete.=20 # AI: Greg N to update the draft per last comments received from # AD and release draft 05 for IETF Last Call. o draft-ietf-ipcdn-docs-rfmibv2-11.txt =20 http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-11.txt # AI: Eduardo to release draft 12 after IETF 61 =20 http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-12.txt # AI: chairs to follow-up on AD review o draft-ietf-ipcdn-bpiplus-mib-14.txt =20 http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-14.txt Status: Draft 14 went through IESG review; 2 DISCUSS Draft 15 to be released after IETF addressing IESG comments. # AI: Eduardo to release draft 15 after IETF 61 # AI: once draft15 is out, chairs to follow-up with AD o DOCSIS Cable Device v2 MIB Update Status: draft expired, need new ID Editor Draft 07 should address all open comments on ID Call for volunteer re-sent on November 3, 2004 # AI: WG chairs to name new editor by December 10 (was Nov 19 but new # volunteers were provided and chairs need more time to assign it) Target date for revised ID: tbd with new editor o draft-ietf-ipcdn-pktc-mtamib-05.txt =20 http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-mtamib-05.txt Status: revised ID needed Draft 05 attempted to address all the MUST fix; one pending issue was actively discussed during the meeting: pktcMtaDevErrorOid table and the syntax of pktcMtaDevErrorOid, pktcMtaDevErrorValue. see MIB doctor comments at: http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01325.html The size limit issue in that table should also be closed on the mailing list. # AI: Jean-Francois to close this one. In the WG meeting, we had consensus that since the OID and its value is provided in the MTA config file by an operator in the form of a character string, it is better to leave the syntax as SnmpAdminString rather than OBJECT IDENTIFIER. It was also requested that the above explanation be mentioned in the doc. # AI: authors to release draft06 addressing open comments. o draft-ietf-ipcdn-pktc-signaling-07.txt =20 http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-signaling-07.t xt Status: all oustanding issues addressed, except for pktcSigDevToneTable enhancements and PktcRingCadence for a fourth octet; New comments on the list need to be closed. Randy Presuhn commented that he could review the updated draft to make sure his comments were addressed. #AI: authors to list close open comments and release draft08 after # IETF 61 - IPCDN WG next steps We briefly discussed the IPCDN WG Next Steps, including: - Finish all DOCSIS MIBs by December 2004 Finish all work on active IDs Risk: Cable Device MIBv2 - Request publication for PacketCable/IPCablecom MTA MIB PacketCable/IPCablecom Signaling MIB - Revise Charter Milestones for a) PacketCable/IPCablecom Management Event MIB (expired draft 03) (we would like to push the work on this ID until 2005 to get implementations and testing under way) b) CableHome MIBs CableHome MIBs - there is no activity on the list. Is there any WG interest to support this work? It was suggested by Greg N that we should update the drafts to the latest CableHome MIBs. ------_=_NextPart_001_01C4D808.B78E4E92 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
Below are the draft = meeting notes from=20 our IETF 61 meeting.
Thanks to Greg Nakanishi for capturing them. Let me know=20 if  
I missed anything.
 
Jean-Francois.
IETF IPCDN Meeting Notes
Washington D.C., USA
Tuesday November 9, 2004

Reported by Greg Nakanishi (gnakanishi@motorola.com)
Edited by Jean-Francois Mule' (jfm@cablelabs.com)


--- WG Meeting Summary
--- ------------------
Ten to fifteen attendees of the IP over Cable Data Networks WG met
at the IETF meeting in Washington DC on November 9, 2004. Total
meeting time was about one hour.

The meeting materials are consolidated into 1 deck of slides and will
be provided as part of the IETF proceedings. They are also posted at
http://www.ipcdn.org/meetings=
.html

We won't summarize the content of the meeting in details, please read
the slides for the current wg item status.


- Summary of decisions made and Action Items =
(AI)

  o WG Charter update
    We are close to finishing the following MIBs (WGLC passed, some
    have passed IETF Last Call, some are about to be in "publication
    requested status):
        - updated IPCDN DOCSIS RF MIB (Proposed Standard)
        - IPCDN DOCSIS Event Notification MIB (Proposed Standard)
        - PacketCable/IPCableCom MTA device MIB (Proposed Standard)
        - PacketCable/IPCableCom MTA signaling MIB (Proposed Standard)

    The WG charter should be revised to change the following
    milestones:
       - IPCDN PacketCable/IPCablecom Management Event MIB
         (draft 03 is expired, new target date required - Dec04? TBD)
       - IPCDN DOCSIS Cable Device MIB v2
         (draft06 is expired, new editor to be assigned, new target
          date TBD)
       - CableHome MIBs
         (IDs are expired, target completion date of Dec04 is unlikely
          to be met; new target date TBD).
# AI: WG chairs to follow-up with AD Bert Wijnen =
to revise charter
# once commitment is secured from ID authors & =
editors.

  o draft-ietf-ipcdn-subscriber-mib-16.txt
    http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-subscribe=
r-mib-16.txt
    Status: RFC Editor Queue
    Draft 16 addressed all IESG comments; work concluded on this ID,
    awaiting publication. Many thanks to Wilson Sawyer for his
    continued work on this work item. No AI.

  o draft-ietf-ipcdn-qos-mib-10.txt
    http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-qos-mib-10.txt
    Status: IETF Last Call started on 2004-11-04; ended on 2004-11-21.
# open issue: rooting of the MIB module under =
mib-2 need to be
# addressed; wg chairs to resolve it after IETF =
Last Call.

  o draft-ietf-ipcdn-docsisevent-mib-04.txt
    http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docsisev=
ent-mib-04.txt
    Status: AD Review
    ID draft 03 reviewed by MIB doctor Harrie.
# AI: chairs to ping AD Bert after IETF to see if =
AD review is
# complete. 
# AI: Greg N to update the draft per last comments =
received from
# AD and release draft 05 for IETF Last =
Call.

  o draft-ietf-ipcdn-docs-rfmibv2-11.txt
    http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv=
2-11.txt
# AI: Eduardo to release draft 12 after IETF =
61
    http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv=
2-12.txt
# AI: chairs to follow-up on AD review


  o draft-ietf-ipcdn-bpiplus-mib-14.txt
    http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv=
2-14.txt
    Status: Draft 14 went through IESG review; 2 DISCUSS
    Draft 15 to be released after IETF addressing IESG comments.
# AI: Eduardo to release draft 15 after IETF =
61
# AI: once draft15 is out, chairs to follow-up =
with AD

  o DOCSIS Cable Device v2 MIB Update
    Status: draft expired, need new ID Editor
    Draft 07 should address all open comments on ID
    Call for volunteer re-sent on November 3, 2004
# AI: WG chairs to name new editor by December 10 =
(was Nov 19 but new
# volunteers were provided and chairs need more =
time to assign it)
    Target date for revised ID: tbd with new editor

  o draft-ietf-ipcdn-pktc-mtamib-05.txt
    http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-mtamib-=
05.txt
    Status: revised ID needed
    Draft 05 attempted to address all the MUST fix; one pending issue
    was actively discussed during the meeting: pktcMtaDevErrorOid
    table and the syntax of pktcMtaDevErrorOid, pktcMtaDevErrorValue.
    see MIB doctor comments at:
    http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01325.html
    The size limit issue in that table should also be closed on the
    mailing list.
# AI: Jean-Francois to close this one.
    In the WG meeting, we had consensus that since the OID and its
    value is provided in the MTA config file by an operator in the
    form of a character string, it is better to leave the syntax
    as SnmpAdminString rather than OBJECT IDENTIFIER. It was also
    requested that the above explanation be mentioned in the doc.
# AI: authors to release draft06 addressing open =
comments.

  o draft-ietf-ipcdn-pktc-signaling-07.txt
    http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-sign=
aling-07.txt
    Status: all oustanding issues addressed, except for
            pktcSigDevToneTable enhancements and PktcRingCadence for a
            fourth octet;
    New comments on the list need to be closed. Randy Presuhn
    commented that he could review the updated draft to make sure his
    comments were addressed.
#AI: authors to list close open comments and =
release draft08 after
#    IETF 61

- IPCDN WG next steps
We briefly discussed the IPCDN WG Next Steps, including:
 - Finish all DOCSIS MIBs by December 2004
   Finish all work on active IDs
   Risk: Cable Device MIBv2
 - Request publication for
   PacketCable/IPCablecom MTA MIB
   PacketCable/IPCablecom Signaling MIB
 - Revise Charter Milestones for

   a) PacketCable/IPCablecom Management Event MIB (expired draft 03)
   (we would like to push the work on this ID until 2005 to get
    implementations and testing under way)

   b) CableHome MIBs
   CableHome MIBs - there is no activity on the list.  Is there any WG
   interest to support this work?  It was suggested by Greg N that we
   should update the drafts to the latest CableHome MIBs.
=00 ------_=_NextPart_001_01C4D808.B78E4E92-- --===============1307385538== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn --===============1307385538==-- From ipcdn-bounces@ietf.org Mon Dec 6 12:36:21 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02950 for ; Mon, 6 Dec 2004 12:36:21 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbMt3-00023h-9Z for ipcdn-archive@ietf.org; Mon, 06 Dec 2004 12:43:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CbMi8-00065D-MT; Mon, 06 Dec 2004 12:31:44 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CbMYV-0003Y7-3U for ipcdn@megatron.ietf.org; Mon, 06 Dec 2004 12:21:47 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01619 for ; Mon, 6 Dec 2004 12:21:44 -0500 (EST) From: andre.lejeune@Terayon.com Received: from mail.terayon.com ([63.201.251.53]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbMes-0001k6-8I for ipcdn@ietf.org; Mon, 06 Dec 2004 12:28:23 -0500 Received: from scbh01.terayon.com (scbh01.bh.terayon.com [192.168.0.23]) by mail.terayon.com (8.12.11/8.12.11) with ESMTP id iB6HMvYA029706; Mon, 6 Dec 2004 09:22:57 -0800 (envelope-from andre.lejeune@Terayon.com) Received: by scbh01.terayon.com with Internet Mail Service (5.5.2657.72) id ; Mon, 6 Dec 2004 09:21:56 -0800 Message-ID: To: docsis-oss@cablelabs.com Date: Mon, 6 Dec 2004 09:21:01 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0, Antispam-Data: 2004.12.5.11 X-Spam-Score: 1.3 (+) X-Scan-Signature: 827a2a57ca7ab0837847220f447e8d56 Cc: ipcdn@ietf.org Subject: [ipcdn] Outstanding issue with docsDevFilterIpSourcePortLow and similar M IB objects X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP over Cable Data Network List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2143281072==" Sender: ipcdn-bounces@ietf.org Errors-To: ipcdn-bounces@ietf.org X-Spam-Score: 1.3 (+) X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --===============2143281072== Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4DBB7.F5847214" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C4DBB7.F5847214 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, =20 We have noticed a discrepancy between the implementation of docsDevFilterIpSourcePortLow between different modems. The difference probably comes from that fact that what makes sense and what the specification says are different. The spec says: =20 docsDevFilterIpSourcePortLow : 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. =20 However, docsDevFilterIpProtocol can also be set to any (256), which is = not listed above. This means that compliant CMs, should ignore docsDevFilterIpSourcePortLow when the Protocol is set to any. However, = this does not seem to make much sense, as such interpretation makes the = "any" value pretty much useless. =20 Long time ago, this issue was brought up on the IPCDN reflector by = other people. However, it seems it has never been resolved. =20 I would like to propose an ECR to section 7.3.5 of the OSSI spec to = clarify that docsDevFilterIpSourcePortLow and similar MIBs are also applicable = when docsDevFilterIpProtocol is set to any (256) and the IP packet is either = tcp or udp. =20 Would there be an objection to this? =20 Thanks, Andr=E9 =20 NOTICE: This communication contains information which may be = proprietary, privileged or confidential. If you are not the intended recipient (or authorized to receive for the intended recipient), or believe that you = have received this communication in error, please do not print, = copy,retransmit, disseminate, disclose or otherwise use the information. Also, please indicate to the sender that you have received this communication in = error and delete the copy you received. Thank you. ------_=_NextPart_001_01C4DBB7.F5847214 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
We = have noticed a=20 discrepancy between the implementation of docsDevFilterIpSourcePortLow = between=20 different modems. The difference probably comes from that fact that = what makes=20 sense and what the specification says are different. The spec=20 says:
 
docsDevFilterIpSourcePortLow :
    If = docsDevFilterIpProtocol is=20 udp or tcp, this is the
    inclusive lower = bound of the=20 transport-layer source port
    range that is to = be matched,=20 otherwise it is ignored
    during=20 matching.
 
However, docsDevFilterIpProtocol can also be set to any (256), = which is=20 not listed above. This means that compliant CMs, should ignore=20 docsDevFilterIpSourcePortLow when the Protocol is set to any. = However, this=20 does not seem to make much sense, as such interpretation makes the = "any" value=20 pretty much useless.
 
Long=20 time ago, this issue was brought up on the IPCDN reflector by other = people.=20 However, it seems it has never been resolved.
 
I=20 would like to propose an ECR to section 7.3.5 of the OSSI spec to = clarify that=20 docsDevFilterIpSourcePortLow and similar MIBs are also applicable = when=20 docsDevFilterIpProtocol is set to any (256) and the IP packet is either = tcp or=20 udp.
 
Would=20 there be an objection to this?
 
Thanks,
Andr=E9
 

NOTICE: This communication contains = information which may be proprietary, privileged or confidential. If = you are not the intended recipient (or authorized to receive for the = intended recipient), or believe that you have received this = communication in error, please do not print, copy,retransmit, = disseminate, disclose or otherwise use the information. Also, please = indicate to the sender that you have received this communication in = error and delete the copy you received. Thank you.

------_=_NextPart_001_01C4DBB7.F5847214-- --===============2143281072== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn --===============2143281072==-- From ipcdn-bounces@ietf.org Mon Dec 6 12:39:44 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03341 for ; Mon, 6 Dec 2004 12:39:44 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbMwJ-00028n-QI for ipcdn-archive@ietf.org; Mon, 06 Dec 2004 12:46:24 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CbMn1-0007Sf-8E; Mon, 06 Dec 2004 12:36:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CbMjO-0006Px-VM for ipcdn@megatron.ietf.org; Mon, 06 Dec 2004 12:33:03 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02560 for ; Mon, 6 Dec 2004 12:33:00 -0500 (EST) Received: from ondar.cablelabs.com ([192.160.73.61]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbMpm-0001xl-4U for ipcdn@ietf.org; Mon, 06 Dec 2004 12:39:39 -0500 Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20]) by ondar.cablelabs.com (8.12.10/8.12.10) with ESMTP id iB6HWL1e001609; Mon, 6 Dec 2004 10:32:21 -0700 (MST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 6 Dec 2004 10:32:21 -0700 Message-ID: <5259D0D7419C6149B347837A2E64F46F6D0514@srvxchg.cablelabs.com> Thread-Topic: Outstanding issue with docsDevFilterIpSourcePortLow and similar MIB objects Thread-Index: AcTbuCQaNT8wj+5xQi6OXsWqZM7nWwAAU1UQ From: "Matthew Schmitt" To: , "DOCSIS OSS Majordomo List" X-Approved: ondar X-Spam-Score: 1.0 (+) X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb Cc: ipcdn@ietf.org Subject: [ipcdn] RE: Outstanding issue with docsDevFilterIpSourcePortLow and similar MIB objects X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP over Cable Data Network List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1054637803==" Sender: ipcdn-bounces@ietf.org Errors-To: ipcdn-bounces@ietf.org X-Spam-Score: 1.0 (+) X-Scan-Signature: bacfc6c7290e34d410f9bc22b825ce96 This is a multi-part message in MIME format. --===============1054637803== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4DBB9.8A882F30" This is a multi-part message in MIME format. ------_=_NextPart_001_01C4DBB9.8A882F30 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Perhaps it'd be simpler to just say that it only applies when the packet = is TCP/UDP? That's essentially the way that it was worded in the RFI = specification. =20 Matt -----Original Message----- From: andre.lejeune@Terayon.com [mailto:andre.lejeune@Terayon.com]=20 Sent: Monday, December 06, 2004 10:21 AM To: DOCSIS OSS Majordomo List Cc: ipcdn@ietf.org Subject: Outstanding issue with docsDevFilterIpSourcePortLow and = similar MIB objects =09 =09 Hi, =20 We have noticed a discrepancy between the implementation of = docsDevFilterIpSourcePortLow between different modems. The difference = probably comes from that fact that what makes sense and what the = specification says are different. The spec says: =20 docsDevFilterIpSourcePortLow : 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. =20 However, docsDevFilterIpProtocol can also be set to any (256), which is = not listed above. This means that compliant CMs, should ignore = docsDevFilterIpSourcePortLow when the Protocol is set to any. However, = this does not seem to make much sense, as such interpretation makes the = "any" value pretty much useless. =20 Long time ago, this issue was brought up on the IPCDN reflector by = other people. However, it seems it has never been resolved. =20 I would like to propose an ECR to section 7.3.5 of the OSSI spec to = clarify that docsDevFilterIpSourcePortLow and similar MIBs are also = applicable when docsDevFilterIpProtocol is set to any (256) and the IP = packet is either tcp or udp. =20 Would there be an objection to this? =20 Thanks, Andr=E9 =20 NOTICE: This communication contains information which may be = proprietary, privileged or confidential. If you are not the intended = recipient (or authorized to receive for the intended recipient), or = believe that you have received this communication in error, please do = not print, copy,retransmit, disseminate, disclose or otherwise use the = information. Also, please indicate to the sender that you have received = this communication in error and delete the copy you received. Thank you. ------_=_NextPart_001_01C4DBB9.8A882F30 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message
Perhaps it'd be simpler to just say that it only applies when = the packet=20 is TCP/UDP?  That's essentially the way that it was worded in the = RFI=20 specification.
 
Matt
-----Original Message-----
From:=20 andre.lejeune@Terayon.com [mailto:andre.lejeune@Terayon.com] =
Sent:=20 Monday, December 06, 2004 10:21 AM
To: DOCSIS OSS Majordomo=20 List
Cc: ipcdn@ietf.org
Subject: Outstanding issue = with=20 docsDevFilterIpSourcePortLow and similar MIB = objects

Hi,
 
We = have noticed a=20 discrepancy between the implementation of docsDevFilterIpSourcePortLow = between=20 different modems. The difference probably comes from that fact that = what makes=20 sense and what the specification says are different. The spec=20 says:
 
docsDevFilterIpSourcePortLow :
    If = docsDevFilterIpProtocol=20 is udp or tcp, this is the
    inclusive lower = bound of=20 the transport-layer source port
    range that is to = be=20 matched, otherwise it is ignored
    during=20 matching.
 
However, docsDevFilterIpProtocol can also be set to any = (256), which is=20 not listed above. This means that compliant CMs, should ignore=20 docsDevFilterIpSourcePortLow when the Protocol is set to any. = However,=20 this does not seem to make much sense, as such interpretation makes = the "any"=20 value pretty much useless.
 
Long=20 time ago, this issue was brought up on the IPCDN reflector by other = people.=20 However, it seems it has never been resolved.
 
I=20 would like to propose an ECR to section 7.3.5 of the OSSI spec to = clarify that=20 docsDevFilterIpSourcePortLow and similar MIBs are also applicable = when=20 docsDevFilterIpProtocol is set to any (256) and the IP packet is = either tcp or=20 udp.
 
Would there be an objection to this?
 
Thanks,
Andr=E9
 

NOTICE: This communication contains = information=20 which may be proprietary, privileged or confidential. If you are not = the=20 intended recipient (or authorized to receive for the intended = recipient), or=20 believe that you have received this communication in error, please do = not=20 print, copy,retransmit, disseminate, disclose or otherwise use the=20 information. Also, please indicate to the sender that you have = received this=20 communication in error and delete the copy you received. Thank=20 you.

=00 ------_=_NextPart_001_01C4DBB9.8A882F30-- --===============1054637803== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn --===============1054637803==-- From ipcdn-bounces@ietf.org Mon Dec 6 12:43:39 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03760 for ; Mon, 6 Dec 2004 12:43:39 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbN07-0002E8-2y for ipcdn-archive@ietf.org; Mon, 06 Dec 2004 12:50:19 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CbMsH-0000Wn-SA; Mon, 06 Dec 2004 12:42:13 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CbMqT-00007n-4v for ipcdn@megatron.ietf.org; Mon, 06 Dec 2004 12:40:21 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03432 for ; Mon, 6 Dec 2004 12:40:18 -0500 (EST) From: andre.lejeune@Terayon.com Received: from mail.terayon.com ([63.201.251.53]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbMwr-00029V-Es for ipcdn@ietf.org; Mon, 06 Dec 2004 12:46:58 -0500 Received: from scbh01.terayon.com (scbh01.bh.terayon.com [192.168.0.23]) by mail.terayon.com (8.12.11/8.12.11) with ESMTP id iB6HfdDF030625; Mon, 6 Dec 2004 09:41:40 -0800 (envelope-from andre.lejeune@Terayon.com) Received: by scbh01.terayon.com with Internet Mail Service (5.5.2657.72) id ; Mon, 6 Dec 2004 09:40:39 -0800 Message-ID: To: m.schmitt@cablelabs.com, andre.lejeune@Terayon.com, docsis-oss@cablelabs.com Date: Mon, 6 Dec 2004 09:39:39 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0, Antispam-Data: 2004.12.5.11 X-Spam-Score: 1.3 (+) X-Scan-Signature: a4e5f67c5e230eddf754446d1a2201a4 Cc: ipcdn@ietf.org Subject: [ipcdn] RE: Outstanding issue with docsDevFilterIpSourcePortLow and simil ar MIB objects X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP over Cable Data Network List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0202490239==" Sender: ipcdn-bounces@ietf.org Errors-To: ipcdn-bounces@ietf.org X-Spam-Score: 1.3 (+) X-Scan-Signature: 2d133cc328f58695161c98bb4f4dc213 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --===============0202490239== Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4DBBA.8FCB7B36" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C4DBBA.8FCB7B36 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Yeah, I came to the same conclusion as I looked into how that would = affect the code! What do they say about people who think alike ;-) (heuum, = heuum) =20 Andr=E9 -----Original Message----- From: Matthew Schmitt [mailto:m.schmitt@cablelabs.com] Sent: Monday, December 06, 2004 12:32 PM To: andre.lejeune@Terayon.com; DOCSIS OSS Majordomo List Cc: ipcdn@ietf.org Subject: RE: Outstanding issue with docsDevFilterIpSourcePortLow and = similar MIB objects Perhaps it'd be simpler to just say that it only applies when the = packet is TCP/UDP? That's essentially the way that it was worded in the RFI specification. =20 Matt -----Original Message----- From: andre.lejeune@Terayon.com [mailto:andre.lejeune@Terayon.com]=20 Sent: Monday, December 06, 2004 10:21 AM To: DOCSIS OSS Majordomo List Cc: ipcdn@ietf.org Subject: Outstanding issue with docsDevFilterIpSourcePortLow and = similar MIB objects Hi, =20 We have noticed a discrepancy between the implementation of docsDevFilterIpSourcePortLow between different modems. The difference probably comes from that fact that what makes sense and what the specification says are different. The spec says: =20 docsDevFilterIpSourcePortLow : 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. =20 However, docsDevFilterIpProtocol can also be set to any (256), which is = not listed above. This means that compliant CMs, should ignore docsDevFilterIpSourcePortLow when the Protocol is set to any. However, = this does not seem to make much sense, as such interpretation makes the = "any" value pretty much useless. =20 Long time ago, this issue was brought up on the IPCDN reflector by = other people. However, it seems it has never been resolved. =20 I would like to propose an ECR to section 7.3.5 of the OSSI spec to = clarify that docsDevFilterIpSourcePortLow and similar MIBs are also applicable = when docsDevFilterIpProtocol is set to any (256) and the IP packet is either = tcp or udp. =20 Would there be an objection to this? =20 Thanks, Andr=E9 =20 NOTICE: This communication contains information which may be = proprietary, privileged or confidential. If you are not the intended recipient (or authorized to receive for the intended recipient), or believe that you = have received this communication in error, please do not print, = copy,retransmit, disseminate, disclose or otherwise use the information. Also, please indicate to the sender that you have received this communication in = error and delete the copy you received. Thank you. NOTICE: This communication contains information which may be = proprietary, privileged or confidential. If you are not the intended recipient (or authorized to receive for the intended recipient), or believe that you = have received this communication in error, please do not print, = copy,retransmit, disseminate, disclose or otherwise use the information. Also, please indicate to the sender that you have received this communication in = error and delete the copy you received. Thank you. ------_=_NextPart_001_01C4DBBA.8FCB7B36 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message
Yeah,=20 I came to the same conclusion as I looked into how that would affect = the code!=20 What do they say about people who think alike ;-) (heuum,=20 heuum)
 
Andr=E9
-----Original Message-----
From: Matthew Schmitt=20 [mailto:m.schmitt@cablelabs.com]
Sent: Monday, December 06, = 2004=20 12:32 PM
To: andre.lejeune@Terayon.com; DOCSIS OSS = Majordomo=20 List
Cc: ipcdn@ietf.org
Subject: RE: Outstanding = issue=20 with docsDevFilterIpSourcePortLow and similar MIB = objects

Perhaps it'd be simpler to just say that it only applies = when the=20 packet is TCP/UDP?  That's essentially the way that it was = worded in the=20 RFI specification.
 
Matt
-----Original Message-----
From:=20 andre.lejeune@Terayon.com [mailto:andre.lejeune@Terayon.com]=20
Sent: Monday, December 06, 2004 10:21 AM
To: = DOCSIS OSS=20 Majordomo List
Cc: ipcdn@ietf.org
Subject: = Outstanding=20 issue with docsDevFilterIpSourcePortLow and similar MIB=20 objects

Hi,
 
We have noticed=20 a discrepancy between the implementation of = docsDevFilterIpSourcePortLow=20 between different modems. The difference probably comes from that = fact that=20 what makes sense and what the specification says are different. The = spec=20 says:
 
docsDevFilterIpSourcePortLow :
    If=20 docsDevFilterIpProtocol is udp or tcp, this is=20 the
    inclusive = lower bound of=20 the transport-layer source port
    range that is = to be=20 matched, otherwise it is ignored
    during=20 matching.
 
However, docsDevFilterIpProtocol can also be set to any = (256), which=20 is not listed above. This means that compliant CMs, should ignore=20 docsDevFilterIpSourcePortLow when the Protocol is set to any. = However,=20 this does not seem to make much sense, as such interpretation makes = the=20 "any" value pretty much useless.
 
Long time ago, this issue was brought up on the IPCDN = reflector by=20 other people. However, it seems it has never been=20 resolved.
 
I=20 would like to propose an ECR to section 7.3.5 of the OSSI spec to = clarify=20 that docsDevFilterIpSourcePortLow and similar MIBs are also = applicable=20 when docsDevFilterIpProtocol is set to any (256) and the IP packet = is either=20 tcp or udp.
 
Would there be an objection to this?
 
Thanks,
Andr=E9
 

NOTICE: This communication contains = information=20 which may be proprietary, privileged or confidential. If you are = not the=20 intended recipient (or authorized to receive for the intended = recipient), or=20 believe that you have received this communication in error, please = do not=20 print, copy,retransmit, disseminate, disclose or otherwise use the=20 information. Also, please indicate to the sender that you have = received this=20 communication in error and delete the copy you received. Thank=20 you.

NOTICE: This communication contains = information which may be proprietary, privileged or confidential. If = you are not the intended recipient (or authorized to receive for the = intended recipient), or believe that you have received this = communication in error, please do not print, copy,retransmit, = disseminate, disclose or otherwise use the information. Also, please = indicate to the sender that you have received this communication in = error and delete the copy you received. Thank you.

------_=_NextPart_001_01C4DBBA.8FCB7B36-- --===============0202490239== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn --===============0202490239==-- From ipcdn-bounces@ietf.org Wed Dec 8 22:49:19 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28697 for ; Wed, 8 Dec 2004 22:49:19 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcFPp-0002am-Dk for ipcdn-archive@ietf.org; Wed, 08 Dec 2004 22:56:29 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CcFCk-00070J-Vr; Wed, 08 Dec 2004 22:42:58 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CcF96-0005gw-B5 for ipcdn@megatron.ietf.org; Wed, 08 Dec 2004 22:39:12 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28117 for ; Wed, 8 Dec 2004 22:39:09 -0500 (EST) Received: from mms-nat.broadcom.com ([63.70.210.58] helo=mms2.broadcom.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcFFz-0002QR-PQ for ipcdn@ietf.org; Wed, 08 Dec 2004 22:46:20 -0500 Received: from 63.70.210.1 by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (MMS v5.6.0)); Wed, 08 Dec 2004 19:37:56 -0800 X-Server-Uuid: 011F2A72-58F1-4BCE-832F-B0D661E896E8 Received: from nt-irva-0740.brcm.ad.broadcom.com ( nt-irva-0740.brcm.ad.broadcom.com [10.8.194.53]) by mon-irva-10.broadcom.com (8.9.1/8.9.1) with ESMTP id TAA10626 for ; Wed, 8 Dec 2004 19:37:56 -0800 (PST) Received: from nt-rmna-0740.brcm.ad.broadcom.com ([10.136.192.33]) by nt-irva-0740.brcm.ad.broadcom.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 8 Dec 2004 19:37:55 -0800 Content-class: urn:content-classes:message MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Wed, 8 Dec 2004 19:37:54 -0800 Message-ID: <24CDBA67F085904999751B3C4F9E8C0B01E76982@NT-RMNA-0740.brcm.ad.broadcom.com> Thread-Topic: Comments on draft-ietf-ipcdn-pktc-signaling-07.txt Thread-Index: AcTRKTpPbAiTIjkwRtuj7S6LGsXKMgMZi0iQ From: "Eugene Nechamkin" To: ipcdn@ietf.org X-OriginalArrivalTime: 09 Dec 2004 03:37:55.0897 (UTC) FILETIME=[7879CA90:01C4DDA0] X-WSS-ID: 6DA9171E0585212247-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Spam-Score: 1.1 (+) X-Scan-Signature: 17e5edc4dfd335965c1d21372171c01c Content-Transfer-Encoding: quoted-printable Subject: [ipcdn] Comments on draft-ietf-ipcdn-pktc-signaling-07.txt X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP over Cable Data Network List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ipcdn-bounces@ietf.org Errors-To: ipcdn-bounces@ietf.org X-Spam-Score: 1.1 (+) X-Scan-Signature: a069a8e8835d39ce36e425c148267a7b Content-Transfer-Encoding: quoted-printable After looking at the Signaling MIB draft-07 (draft-ietf-ipcdn-pktc-signaling-07.txt) more closely, here are some comments/concerns we would like to be addressed for the next release of the draft: 1. PktcCodecType: The following sentence in the DESCRIPTION clause: "Literal Codec Name Column=20 contains the codec name used in the local connection=20 descriptor (LCD) of the NCS messages create connection=20 (CRCX)/modify connection (MDCX) and is also used to=20 identify the codec in the Call Management System (CMS)=20 Provisioning Specification." Should be changed as follows: change/local connection descriptor (LCD)/local connection options (LCO)/ "Literal Codec Name Column=20 contains the codec name used in the local connection=20 options (LCO) of the NCS messages create connection=20 (CRCX)/modify connection (MDCX) and is also used to=20 identify the codec in the Call Management System (CMS)=20 Provisioning Specification." 2. PktcRingCadence: In the DESCRIPTION clause: I. Delete/(Note: A minimum number of octets required to encode the bit-string MUST be used)./ The "note" is not making much sense as each additional '0' bit requires the tone to be encreased by the 50msec, therefore the required time length of the tone will define the actual number of octets, rather than the requirement in the "note". II. change/the former value indicating 'repeatability'=20 and the latter indicating 'non-repeatability'/ the latter value indicating 'repeatability'=20 and the former indicating 'non-repeatability'./ This has been already noticed in some other e-mail but is mentioned here just for the sake of completeness. 3. pktcNcsEndPntConfigTSMax: The existing DESCRIPTION clause is: " This object is used as part of a MTA retransmission=20 algorithm when communicating with a call agent. This object=20 contains the maximum time in seconds since the sending of=20 the initial datagram to a call agent. If more than=20 pktcNcsEndPntConfigTSMax time has elapsed, the endpoint=20 becomes disconnected." =20 The description is incorrect. With the latest NCS specifications you do not become disconnected after TsMax, but only after 2*Thist with no response. The following DESCRCIPTION is proposed instead of the existing one: " This object is used as part of a NCS retransmission=20 algorithm which MTA must follow when communicating with a call agent.=20 This object contains the maximum time in seconds which any datagram can=20 be sent to the callagent for. If more time elapsed than this object contains,=20 then the retransmission must cease." 4. pktcNcsEndPntConfigTdinit: The existing DESCRIPTION clause is: "This object contains the initial number of seconds the MTA =20 waits after a disconnect, before initiating the=20 disconnected procedure with the call agent." =20 The description is incorrect. It is not the actual initial number of seconds but it is the maximum value that the disconnected timer can be initialized to randomly between 0 and TdInit.=20 The following DESCRCIPTION is proposed instead of the existing one: " This object is used as part of a MTA disconnect procedure when=20 communicating with a call agent. The object contains the maxumum=20 value of the randomly generated number which initializes the disconnected timer. When the latter elapses, the MTA initiates=20 the disconnect procedure for the particular endpoint." 5. pktcNcsEndPntConfigTdmin: The existing DESCRIPTION clause is: " This object contains the minimum number of seconds the MTA waits after a disconnect, before initiating the=20 disconnected procedure with the call agent." =20 The description is incorrect. This is only the minimum amount of time to wait to begin the disconnected procedure in the case that local user activity has triggered the sending of the RSIP message. That is the only case that Tdmin applies. The following DESCRCIPTION is proposed instead of the existing one: " This object is used as part of a MTA disconnect procedure when=20 communicating with a call agent. This is the minimum amount of=20 time to wait to begin the disconnected procedure only in the case=20 that local user activity has triggered the sending of the RSIP message." 6. pktcNcsEndPntConfigMinHookFlash pktcNcsEndPntConfigMaxHookFlash pktcNcsEndPntConfigPulseDialMinMakeTime pktcNcsEndPntConfigPulseDialMaxMakeTime pktcNcsEndPntConfigPulseDialMinBreakTime pktcNcsEndPntConfigPulseDialMaxBreakTime Issue: The MIB currently allows for pulse dial and hook flash to overlap. This creates confusion when a change is detected on the line, whether to report a pulse digit or hookflash. Therefore, the MIB must either enforce that the two don't overlap (ie. minHookFlash must be greater than pulseDialMaxMake) or there should be other criteria for the MTA to decide which of the two to report. Standard PSTN telephone interface reports pulse dial only before the connection is established (call setup) and hookflash once a call is up and running. However, from a NCS perspective either DTMF (pulse dial) and hook-flash can be requested at any time independent of connection status. Proposed the following: Add the following sentence to the description clause of the pktcNcsEndPntConfigMinHookFlash: " Because of the possibility for pulse dial and hook flash to overlap, the value of this object MUST be greater than the value in the=20 pktcNcsEndPntConfigPulseDialMaxMakeTime MIB Object." Add the following sentence to the description clause of the pktcNcsEndPntConfigPulseDialMaxMakeTime : " Because of the possibility for pulse dial and hook flash to overlap, the value of this object MUST be less than the value in the pktcNcsEndPntConfigMinHookFlash MIB Object." 7. pktcSigDevToneType: The existing DESCRIPTION clause is: "Unique value ranging from 1 to 21 that will correspond to=20 the different tone types. These tones can be provisioned=20 based on country specific needs. This object defines the=20 type of tone being accessed. The alertingSignal,=20 specialDial, specialInfo, release, congestion and=20 userDefined1-4 tone types are used in the E line package." =20 =20 Issue: The tones alertingSignal, specialDial, specialInfo, release, congestion and userDefined1-4 are not defined in the E line package that we can find. In fact, it is unclear how these tones would be signaling via NCS.=20 Potential solutions: - the last sentence of the descriptoin clause is removed, - remove or clarify the following from the SYNTAX clause of the object: alertingSignal(13),=20 specialDial(14),=20 specialInfo(15),=20 release(16),=20 congestion(17),=20 userDefined1(18),=20 userDefined2(19),=20 userDefined3(20),=20 userDefined4(21) =20 8. pktcSigDevCIDMode, pktcSigDevCallerIdSigProtocol: =20 Existing default values for these two objects are=20 DEFVAL { dtAsETS } -- for pktcSigDevCIDMode DEFVAL { fsk} -- for pktcSigDevCallerIdSigProtocol Issue: The existing default values for the on-hook Caller ID items do not make sense. The DTAS alerting mode is mainly used for off-hook caller ID, not on-hook. There are very few countries that deploy DTAS alerting for on-hook caller ID (Denmark, Brazil) but they require dtmf signalling protocol not fsk.=20 Proposed: the default on-hook caller ID mode (pktcSigDevCIDMode) to change to rpAsETS. Eugene Nechamkin, Broadcom Corp. Ph: (604) 233-8500 _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-bounces@ietf.org Tue Dec 28 13:58:49 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17208 for ; Tue, 28 Dec 2004 13:58:49 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjMjT-000203-94 for ipcdn-archive@ietf.org; Tue, 28 Dec 2004 14:10:11 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CjMVN-0007ep-UK; Tue, 28 Dec 2004 13:55:37 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CjMNe-0006M8-1s for ipcdn@megatron.ietf.org; Tue, 28 Dec 2004 13:47:38 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16531 for ; Tue, 28 Dec 2004 13:47:36 -0500 (EST) Received: from ondar.cablelabs.com ([192.160.73.61]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjMYa-0001i4-VO for ipcdn@ietf.org; Tue, 28 Dec 2004 13:58:58 -0500 Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20]) by ondar.cablelabs.com (8.12.10/8.12.10) with ESMTP id iBSIl21e029892; Tue, 28 Dec 2004 11:47:02 -0700 (MST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: [ipcdn] Update on finding a new editor for IETF IPCDN DOCSIS cable device MIB v2 ID Date: Tue, 28 Dec 2004 11:47:02 -0700 Message-ID: Thread-Topic: [ipcdn] Update on finding a new editor for IETF IPCDN DOCSIS cable device MIB v2 ID Thread-Index: AcSGETA7YL1c/WVvTxWNSmZECb/jPRR90GvQBUBib2A= From: "Jean-Francois Mule" To: X-Approved: ondar X-Spam-Score: 0.0 (/) X-Scan-Signature: 386e0819b1192672467565a524848168 Content-Transfer-Encoding: quoted-printable Cc: DOCSIS OSS Majordomo List , "Richard Woundy @ Comcast" X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP over Cable Data Network List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ipcdn-bounces@ietf.org Errors-To: ipcdn-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db Content-Transfer-Encoding: quoted-printable Folks, Just a quick update on my action item to find a new editor for IETF = IPCDN DOCSIS cable device MIB v2. In short, I have been slow and we only = have a couple of volunteers. To date, we have 4 people on the list (2 = have directly responded to my call for volunteers = ) and = 2 additional names were suggested to me after I followed up with some = folks.=20 I have contacted all the volunteers, and hopefully soon, we'll have = a new editor. If you are now interested, let me know asap. Below is what I believe should be done to advance the ID: + take over the expired draft06 http://www.ipcdn.org/drafts/draft-ietf-ipcdn-device-mibv2-06.txt = + take over the list of known issues, sum it up and publish it as of = today with a current status (some issues raised by mib doctors on = draft06 have been addressed by Rich and others, some are still pending) Here are the MIB doctor comments/concerns applicable to this ID:=20 (resolved by ) (resolved by ) + nail down the open or pending issues in 2 or 3 weeks by either = putting them to bed forever or addressing them in consultation with the = IETF and DOCSIS OSS teams (all emails must be sent to the IETF list and = resolution must get ipcdn wg consensus).=20 + release draft07 addressing all the issues that needed to be = addressed It is imperative that the editor understands the DOCSIS specs and the = CM/CMTS function managed in the MIB objects in question. It is also = imperative that the IETF process be understood at a high level, and, in = particular, that the candidate be willing to read and consider: - ID guidelines http://www.ietf.org/ietf/1id-guidelines.txt - The XML document format for ID editing since the source of the = Internet-draft has now been converted to XML by Rich using RFC2629 = http://xml.resource.org/;=20 - the IDnits and ID Checklist http://www.ietf.org/ID-Checklist.html - the Guidelines for Authors and Reviewers of MIB Documents http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-= 03.txt - and all the other minor things to make the draft compliant with the = laws of the mib doctor kingdom. Did I miss something important? Jean-Francois. > -----Original Message----- > From: Jean-Francois Mule > Sent: Wednesday, November 03, 2004 12:26 PM > To: ipcdn@ietf.org > Subject: [ipcdn] Call for volunteer to be the editor of RFC 2669bis >=20 >=20 > Folks, >=20 > We are hitting a roadblock on the cable dev mib and need a new ID=20 > editor. > =20 > http://www.ipcdn.org/drafts/draft-ietf-ipcdn-device-mibv2-06.t xt is expired. The current status is that numerous comments were received from mib = doctors and a new draft is needed. While some comments have been = addressed in an alpha version of draft 07, we need someone who can take = over the draft and complete the work. While Rich and I can offer = support, we cannot commit to being draft editors anymore on this one. = Rich and I can give more technical details on what's left to address in = draft 07 if needed. Anyone interested? Please let us know via email, or, if you are not = sure yet and want to chat live, ping us and we can organize a call or = chat live at the IETF meeting in Washington DC next week. Thanks, -- Rich and Jean-Fran=E7ois _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-bounces@ietf.org Wed Dec 29 11:38:44 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22335 for ; Wed, 29 Dec 2004 11:38:44 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cjh1d-00033I-B5 for ipcdn-archive@ietf.org; Wed, 29 Dec 2004 11:50:18 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CjglQ-0003j5-MN; Wed, 29 Dec 2004 11:33:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cjgj9-0002x1-JF for ipcdn@megatron.ietf.org; Wed, 29 Dec 2004 11:31:14 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21709 for ; Wed, 29 Dec 2004 11:31:09 -0500 (EST) Received: from ihemail2.lucent.com ([192.11.222.163]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjguH-0002qB-If for ipcdn@ietf.org; Wed, 29 Dec 2004 11:42:43 -0500 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id iBTGUZXX017287 for ; Wed, 29 Dec 2004 10:30:36 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Wed, 29 Dec 2004 17:30:31 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550604F03E@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: Jean-Francois Mule , "Richard Woundy @ Comcast" , david.raftus@terayon.com, Eduardo Cardona Subject: RE: [ipcdn] request for ID publication: DOCSIS RFIv2 mib - 2670b is Date: Wed, 29 Dec 2004 17:30:29 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C4EDC3.B4D0EF36" X-Spam-Score: 1.1 (+) X-Scan-Signature: 96d26af66a470479d19aa000d8b57808 Cc: "Ipcdn \(E-mail\)" X-BeenThere: ipcdn@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IP over Cable Data Network List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ipcdn-bounces@ietf.org Errors-To: ipcdn-bounces@ietf.org X-Spam-Score: 1.1 (+) X-Scan-Signature: 15f738ac3e6f6832676157730a0b6168 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C4EDC3.B4D0EF36 Content-Type: text/plain; charset="iso-8859-1" X-MIME-Autoconverted: from 8bit to quoted-printable by ihemail2.lucent.com id iBTGUZXX017287 Content-Transfer-Encoding: quoted-printable Sorry that it took a (long) while to do AD review. Here are my comments: - my findref tool (prelimenary, borrowed from RFC-Editor) says: !! Missing Reference for citation: [RFC2670] P122 L050: interfaces" [RFC2670]. !! Missing citation for Normative reference: P123 L048: [RFC3291] Daniele, M., Haberman, B., Routhier, S., Sc= hoenwaelder, - my idnits tool, available from: http://ietf.levkowetz.com/tools/idnits/ tells me: $ idnits draft-ietf-ipcdn-docs-rfmibv2-12.txt idnits 1.58 draft-ietf-ipcdn-docs-rfmibv2-12.txt: Checking nits according to http://www.ietf.org/ID-Checklist.html : * The document seems to lack an IANA Considerations section. Checking conformance with RFC 3667/3668 boilerplate... * The document seems to lack an RFC 3668 Section 5, para 1 IPR Disclosu= re Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate e= rror? * The document seems to lack an RFC 3668 Section 5, para 2 IPR Disclosu= re Acknowledgement. * There are 2 instances of lines with non-ascii characters in the docum= ent. Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt = : Nothing found here (but these checks does not cover all of 1id-guidelines.txt yet). Miscellaneous warnings: - Line 501 has weird spacing: '...astPkts inter...' - Line 561 has weird spacing: '...astPkts inte...' - Line 772 has weird spacing: '...astPkts inter...' - Line 843 has weird spacing: '...astPkts inte...' - Line 919 has weird spacing: '...astPkts inte...' - (1 more instance...) Run idnits with the --verbose option for more detailed information. =20 The missing IANA considerations is not good. Section should say that there are no (new) IANA actions to be performed one of non-ascii characters are in the MIB MODULE. not good for compila= tion C:\bwijnen\smicng\work>smicmfm ipcdnDocsIfMIB.mi2 E: f(ipcdnDocsIfMIB.mi2), (36,41) Syntax error ** 1 error and 0 warnings in parsing line 36 is the line LAST-UPDATED "200411221700Z" \xFB- November 22, 2004 after fixing that, compile goes reasonably. except for W: f(rfmibv2.mi2), (4948,1) OBJECT-GROUP "docsIfObsoleteGroup" is not= used in a MODULE-COMPLIANCE in current module now that was already the case in RFC2670. Strange but such is life. Might be good to add a ASN.1 comment about it so we know it has existed for a long time. - Next I did run smidiff: $ smidiff -s -l 6 -m -inamelength-32 ..\ietf\DOCS-IF-MIB ./DOCS-IF-MIB=20 >docs-if-mib-diff.txt I have attached the doc-if-mib-diff.txt file for your perusal... pls ch= eck in detail to make sure that all the changes are indeed intentional. What I find serious issues in there (and those that I checked in more detail) is the following: 1. You have removed and then re-added docsIfObsoleteGroup That was kind of OK if the OID that you used woul have been the same, but it changed from the last subid of 4 to 5. This is forbidden accoring to SMI rules. Why was this done? 2. ./DOCS-IF-MIB:2988 [3] {range-changed} range of type used in=20 `docsIfCmtsModPreambleLen' changed from `(0..1024)' to `(0..1536)' That is acceptable, but since this is a read-create object, you must change the old MODULE-COMPLIANCE statement (i.e. the one you deprecate= d) to describe this OBJECT-TYPE with a limited range. For example: OBJECT docsIfCmtsModPreambleLen SYNTAX Integer32 (0..1024) DESCRIPTION "The range of the values for this MODUL-COMPLIANCE is 0..1024= ." without it, old implementations claiming docsIfBasicCompliance would all of a sudden have to support the new values 1025..1536 as well. 3. ./DOCS-IF-MIB:3018 [3] {range-changed} range of type used in=20 `docsIfCmtsModFECErrorCorrection' changed from `(0..10)' to `(0..16)' That is acceptable, but since this is a read-create object, you must change the old MODULE-COMPLIANCE statement (i.e. the one you deprecate= d) to describe this OBJECT-TYPE with a limited range. For example: OBJECT docsIfCmtsModFECErrorCorrection SYNTAX Integer32 (0..10) DESCRIPTION "The range of the values for this MODUL-COMPLIANCE is 0..10." without it, old implementations claiming docsIfBasicCompliance would all of a sudden have to support the new values 11..16 as well. 4. I see that docsIfCmtsModType has a number of values/enumerations added. The old MODULE-COMPLIANCE statement has not changed, sofar sogood But the new MODULE-COMPLIANCE does not list this object. So can all va= lues (including other(1)) be written ??? 5. ./DOCS-IF-MIB:2400 [3] {range-added} size `(0..512)' added to type use= d in `docsIfCmtsCmStatusEqualizationData' Probably OK. Can you add some text to explain why this is OK? 6. ./DOCS-IF-MIB:2414 [5] {named-number-added} warning: named number `ope= rational' added to type used in `docsIfCmtsCmStatusValue' ./DOCS-IF-MIB:2414 [5] {named-number-added} warning: named number=20 `registeredBPIInitializing' added to type used in `docsIfCmtsCmStatusV= alue' That is OK sinmce it is a read-only object. So when an existing implem= entation does not return the new values, it is still compliant with old MODULE-= COMPLIANCE 7. ./DOCS-IF-MIB:1167 [3] {range-added} size `(0..512)' added to type use= d in `docsIfSigQEqualizationData' you may want to add some text why the range change is OK 8. ./DOCS-IF-MIB:278 [5] {named-number-added} warning: named number=20 `taps12increment17' added to type used in `docsIfDownChannelInterleave= ' is OK since it already has specific syntax in old MODULE-COMPLIANCE 9. ./DOCS-IF-MIB:457 [3] {range-changed} range of type used in `docsIfUpChannelWidth' changed from `(0..20000000)' to `(0..64000000)' is OK since there is already specific syntax in MODULE-COMPLIANCE statements Other comments: - for object: docsIfCmtsQosProfilePermissions I see: "This object specifies permitted methods of creating entries in docsIfQosProfileTable. CreateByManagement(0) is set if entries can be created using SNMP. UpdateByManagement(1) is set if updating entries using SNMP is permitted. CreateByModems(2) is set if entries can be created based on information in REG-REQ MAC messages received from Cable Modems. Information in this object is only applicable if docsIfQosProfileTable is implemented as read-create. Otherwise, this object is implemented as read-only and returns CreateByModems(2). Either CreateByManagement(0) or CreateByModems(1) MUST be set when writing to this object. Note that BITS objects are encoded most significant bit first. For example, if bit 2 is set, the value of this object is the octet string '20'H." 1. The values start with lowercase. So it would be better to be consistent when using the names/labels of the values. 2. I see "Either CreateByManagement(0) or CreateByModems(1)" but the valie for "createByModems" is actually 2 and not 1. You either want to fix it to 2, but probably you mean "updateByManagement(1)" ??=20 3. If the latter,m does that mean that one cannot do a SET for "createByModems" ?? If so, then a WRITE-SYNTAX in the=20 MODULE-COMPLIANCE is the way to express that machine readable. - docsIfCmtsModControl OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "Controls and reflects the status of rows in this table." ::=3D { docsIfCmtsModulationEntry 3 } It would be good to add text to explain which (if any) objects can be=20 changed when the row is active. Pls check if there are other RowStatus objects that lack that text as w= ell. - WHen you deprecate/obsolete objects or groups or module compliance or whatever, then it is good practice to ADD a little text to the DESCRITP= ION clause to explain why the depraction/obsoletion occured and which (if a= ny) other definition should be used instead. - docsIfCmtsCmStatusValue OBJECT-TYPE SYNTAX INTEGER { other(1), ranging(2), rangingAborted(3), rangingComplete(4), ipComplete(5), registrationComplete(6), accessDenied(7), operational(8), -- deprecated registeredBPIInitializing(9) I do not understand why a "deprecated" value gets added when upgrading= from RFC2670 to this new document. ?? - I do not understand (page 104): -- -- RFC XXXX Conformance definitions -- -- ************************************************************ -- * NOTES TO RFC Editor (to be removed prior to publication) * -- * * -- * replace XXXX with the IANA assigned RFC number * -- of this document * -- * * -- ************************************************************ docsIfCompliancesV2 OBJECT IDENTIFIER ::=3D { docsIfConformance 3 = } docsIfGroupsV2 OBJECT IDENTIFIER ::=3D { docsIfConformance 4 = } That is... why do you want to add an extra level here? The above 2 do not seem needed in my view. Not that it is an error, it is just extra "baggage" so to speak that (I think) serves no purpose. Or am I missing something? The following then is more a RFC2670 definition... if you really want to make reference to an RFC. docsIfBasicCompliance MODULE-COMPLIANCE STATUS deprecated DESCRIPTION "The compliance statement for devices that implement MCNS/DOCSIS compliant Radio Frequency Interfaces." - This: docsIfCmtsOptionalGroupV2 OBJECT-GROUP is really a bad name for an OBJECT-GROUP. The fact that a group is optional of not is something that you express in the MODULE-COMPLIANCE. The OBJECT-GROUP macro is just to logically group objects together. The DESCRIPTION clause is also weird: DESCRIPTION "Group of objects implemented optionally in Cable Modem Termination Systems." I would rather see you describe what "logical group of objects" it is. FOr example:=20 "This is a group of counters to monitor mini-slots. These can be implemented in Cable Modem Termination Systems." Might even want to explain what mini-slots are (for the novice reader). =20 - doc header states: Obsoletes: RFC 2670 but abstract says: This document revises RFC 2670. Please see section 10 for a description of the changes from RFC 2670. Make sure that the abstract also states that this doc obsoletes 2670. - The MIB module states: REVISION "200411221700Z" DESCRIPTION "Revision of the IETF RF MIB module for DOCSIS 2.0. This version published as RFC XXXX." You need to list (at least the major) changes to the MIB module. Pls realize that a lot of people extract the MIB module from the docume= nt and then the sect 10 is not always easily available/handy. - I see in docsIfUpstreamChannelEntry For DOCSIS 1.x CM/CMTSs and DOCSIS 2.0 CMs, an entry in this table exists for each ifEntry with an ifType of docsCableUpstreamInterface (129)." while the real label in the IANAifType-MIB is docsCableUpstream (129) - Can you explain why you need the compexity of clone from as described i= n docsIfUpChannelCloneFrom, docsIfUpChannelUpdate and docsIfUpChannelStat= us I really do not understand why you have to make this so complex. - your heading (page heading) dates are out of sync with the front page date. - In Security COnsiderations: The table docsIfCmtsCmStatusTable also contain the MAC and IP addresses of the cable modems that cam be used of thief of service and IP spoofing. s/cam/can/ "of thief of.." ??? is it "for theft of.." ?? I still need to sit down and try to understand all the MIB objects. Bert > -----Original Message----- > From: Jean-Francois Mule [mailto:jf.mule@CableLabs.com] > Sent: Friday, October 29, 2004 22:51 > To: iesg-secretary@ietf.org; bwijnen@lucent.com > Cc: Richard Woundy @ Comcast > Subject: [ipcdn] request for ID publication: DOCSIS RFIv2 mib=20 > - 2670bis >=20 >=20 > We would like to request formal publication for the ID=20 > ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmib > v2-11.txt. >=20 > Bert, please approve - see status below. >=20 > Jean-Fran=E7ois=20 >=20 > > -----Original Message----- > > From: Jean-Francois Mule=20 > > Sent: Thursday, October 28, 2004 3:55 PM > > To: ipcdn@ietf.org > > Cc: Eduardo Cardona; david.raftus@terayon.com; bwijnen@lucent.com > > Subject: RE: [ipcdn] status of ipcdn DOCSIS RFIv2 mib - 2670bis > >=20 > >=20 > > Just to close the loop on this mib, we received no comments=20 > > on this post. It is therefore our intent to request its publication. > >=20 > > -- Rich and Jean-Francois. > >=20 > > > -----Original Message----- > > > From: Jean-Francois Mule > > > Sent: Wednesday, October 06, 2004 1:57 PM > > > To: ipcdn@ietf.org > > > Cc: Eduardo Cardona; david.raftus@terayon.com > > > Subject: [ipcdn] status of ipcdn DOCSIS RFIv2 mib - 2670bis > > >=20 > > >=20 > > >=20 > > > This note provides a brief status update on the ipcdn=20 > > DOCSIS RFIv2=20 > > > mib Internet-Draft. It is also a follow-up from the IETF=20 > > meeting #60=20 > > > in San Diego. > > >=20 > > > --- Brief status > > > The current ID is draft-ietf-ipcdn-docs-rfmibv2-11. > > > =20 > > ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmib > v2-11.txt > A working group last call was issued on 1/23/2004 and ended=20 > on 2/6/2004. The authors believe that draft 11 does address=20 > all the wg comments as well as AD review comments from Bert.=20 > Based on the input received this week from the authors and=20 > the current editor Eduardo, no new comments have been=20 > received since the ID was revised at the end of July 2004. >=20 > --- San Diego wg meeting follow-up > Based on our meeting minutes at=20 http://www.ietf.org/proceedings/04aug/171.htm#rfimib , we wanted to ping = the mailing list to see if another WGLC is needed. If you think a second = WGLC should be issued, please let the ipcdn wg know by sending an email t= o the list by Wednesday October 13, 5pm ET. --- Next steps Pending wg consensus that a new WGLC is not needed and no objection to mo= ve this ID forward, it is the wg chairs intent to submit the ID for publi= cation/IESG review to Bert. Rich and Jean-Francois. IPCDN co-chairs ------_=_NextPart_000_01C4EDC3.B4D0EF36 Content-Type: text/plain; name="docs-if-mib-diff.txt" Content-Disposition: attachment; filename="docs-if-mib-diff.txt" Content-Transfer-Encoding: quoted-printable ./DOCS-IF-MIB:35 [5] {contact-changed} warning: contact of = `DOCS-IF-MIB' changed ./DOCS-IF-MIB:35 [5] {description-changed} warning: description of = module identity definition `DOCS-IF-MIB' changed ./DOCS-IF-MIB:73 [5] {revision-added} warning: revision `2004-11-22 = 17:00' added ..\ietf\DOCS-IF-MIB:28 [6] {previous-definition} info: previous = definition of `DOCS-IF-MIB' ./DOCS-IF-MIB:111 [5] {type-added} warning: type `DocsisVersion' has = been added ./DOCS-IF-MIB:121 [5] {type-added} warning: type `DocsisQosVersion' = has been added ./DOCS-IF-MIB:129 [5] {type-added} warning: type `DocsisUpstreamType' = has been added ./DOCS-IF-MIB:140 [5] {type-added} warning: type = `DocsisUpstreamTypeStatus' has been added ./DOCS-IF-MIB:169 [5] {ref-changed} warning: reference of = `docsIfDownstreamChannelTable' changed ..\ietf\DOCS-IF-MIB:87 [6] {previous-definition} info: previous = definition of `docsIfDownstreamChannelTable' ./DOCS-IF-MIB:218 [5] {ref-changed} warning: reference of = `docsIfDownChannelFrequency' changed ..\ietf\DOCS-IF-MIB:132 [6] {previous-definition} info: previous = definition of `docsIfDownChannelFrequency' ./DOCS-IF-MIB:237 [5] {ref-changed} warning: reference of = `docsIfDownChannelWidth' changed ..\ietf\DOCS-IF-MIB:150 [6] {previous-definition} info: previous = definition of `docsIfDownChannelWidth' ./DOCS-IF-MIB:254 [5] {ref-changed} warning: reference of = `docsIfDownChannelModulation' changed ..\ietf\DOCS-IF-MIB:166 [6] {previous-definition} info: previous = definition of `docsIfDownChannelModulation' ./DOCS-IF-MIB:278 [5] {named-number-added} warning: named number = `taps12increment17' added to type used in `docsIfDownChannelInterleave' ./DOCS-IF-MIB:278 [5] {description-changed} warning: description of = object definition `docsIfDownChannelInterleave' changed ./DOCS-IF-MIB:278 [5] {ref-changed} warning: reference of = `docsIfDownChannelInterleave' changed ..\ietf\DOCS-IF-MIB:188 [6] {previous-definition} info: previous = definition of `docsIfDownChannelInterleave' ./DOCS-IF-MIB:326 [5] {description-changed} warning: description of = object definition `docsIfDownChannelPower' changed ./DOCS-IF-MIB:326 [5] {ref-changed} warning: reference of = `docsIfDownChannelPower' changed ..\ietf\DOCS-IF-MIB:227 [6] {previous-definition} info: previous = definition of `docsIfDownChannelPower' ./DOCS-IF-MIB:383 [5] {description-changed} warning: description of = object definition `docsIfUpstreamChannelTable' changed ..\ietf\DOCS-IF-MIB:252 [6] {previous-definition} info: previous = definition of `docsIfUpstreamChannelTable' ./DOCS-IF-MIB:392 [5] {description-changed} warning: description of = object definition `docsIfUpstreamChannelEntry' changed ..\ietf\DOCS-IF-MIB:261 [6] {previous-definition} info: previous = definition of `docsIfUpstreamChannelEntry' ./DOCS-IF-MIB:438 [5] {description-changed} warning: description of = object definition `docsIfUpChannelFrequency' changed ./DOCS-IF-MIB:438 [5] {ref-changed} warning: reference of = `docsIfUpChannelFrequency' changed ..\ietf\DOCS-IF-MIB:293 [6] {previous-definition} info: previous = definition of `docsIfUpChannelFrequency' ./DOCS-IF-MIB:457 [3] {range-changed} range of type used in = `docsIfUpChannelWidth' changed from `(0..20000000)' to `(0..64000000)' ./DOCS-IF-MIB:456 [5] {description-changed} warning: description of = object definition `docsIfUpChannelWidth' changed ./DOCS-IF-MIB:456 [5] {ref-changed} warning: reference of = `docsIfUpChannelWidth' changed ..\ietf\DOCS-IF-MIB:310 [6] {previous-definition} info: previous = definition of `docsIfUpChannelWidth' ./DOCS-IF-MIB:474 [5] {description-changed} warning: description of = object definition `docsIfUpChannelModulationProfile' changed ./DOCS-IF-MIB:474 [5] {ref-added} warning: reference added to = `docsIfUpChannelModulationProfile' ..\ietf\DOCS-IF-MIB:326 [6] {previous-definition} info: previous = definition of `docsIfUpChannelModulationProfile' ./DOCS-IF-MIB:501 [5] {description-changed} warning: description of = object definition `docsIfUpChannelSlotSize' changed ./DOCS-IF-MIB:501 [5] {ref-changed} warning: reference of = `docsIfUpChannelSlotSize' changed ..\ietf\DOCS-IF-MIB:342 [6] {previous-definition} info: previous = definition of `docsIfUpChannelSlotSize' ./DOCS-IF-MIB:518 [5] {description-changed} warning: description of = object definition `docsIfUpChannelTxTimingOffset' changed ./DOCS-IF-MIB:518 [5] {ref-changed} warning: reference of = `docsIfUpChannelTxTimingOffset' changed ..\ietf\DOCS-IF-MIB:356 [6] {previous-definition} info: previous = definition of `docsIfUpChannelTxTimingOffset' ./DOCS-IF-MIB:541 [5] {ref-changed} warning: reference of = `docsIfUpChannelRangingBackoffStart' changed ..\ietf\DOCS-IF-MIB:371 [6] {previous-definition} info: previous = definition of `docsIfUpChannelRangingBackoffStart' ./DOCS-IF-MIB:557 [5] {ref-changed} warning: reference of = `docsIfUpChannelRangingBackoffEnd' changed ..\ietf\DOCS-IF-MIB:386 [6] {previous-definition} info: previous = definition of `docsIfUpChannelRangingBackoffEnd' ./DOCS-IF-MIB:574 [5] {ref-changed} warning: reference of = `docsIfUpChannelTxBackoffStart' changed ..\ietf\DOCS-IF-MIB:401 [6] {previous-definition} info: previous = definition of `docsIfUpChannelTxBackoffStart' ./DOCS-IF-MIB:590 [5] {ref-changed} warning: reference of = `docsIfUpChannelTxBackoffEnd' changed ..\ietf\DOCS-IF-MIB:416 [6] {previous-definition} info: previous = definition of `docsIfUpChannelTxBackoffEnd' ./DOCS-IF-MIB:815 [5] {description-changed} warning: description of = object definition `docsIfQosProfileEntry' changed ..\ietf\DOCS-IF-MIB:449 [6] {previous-definition} info: previous = definition of `docsIfQosProfileEntry' ./DOCS-IF-MIB:864 [5] {description-changed} warning: description of = object definition `docsIfQosProfIndex' changed ..\ietf\DOCS-IF-MIB:494 [6] {previous-definition} info: previous = definition of `docsIfQosProfIndex' ./DOCS-IF-MIB:874 [5] {description-changed} warning: description of = object definition `docsIfQosProfPriority' changed ./DOCS-IF-MIB:874 [5] {ref-added} warning: reference added to = `docsIfQosProfPriority' ..\ietf\DOCS-IF-MIB:503 [6] {previous-definition} info: previous = definition of `docsIfQosProfPriority' ./DOCS-IF-MIB:891 [5] {units-added} warning: units added to = `docsIfQosProfMaxUpBandwidth' ./DOCS-IF-MIB:891 [5] {ref-added} warning: reference added to = `docsIfQosProfMaxUpBandwidth' ./DOCS-IF-MIB:908 [5] {units-added} warning: units added to = `docsIfQosProfGuarUpBandwidth' ./DOCS-IF-MIB:908 [5] {ref-added} warning: reference added to = `docsIfQosProfGuarUpBandwidth' ./DOCS-IF-MIB:925 [5] {units-added} warning: units added to = `docsIfQosProfMaxDownBandwidth' ./DOCS-IF-MIB:925 [5] {ref-added} warning: reference added to = `docsIfQosProfMaxDownBandwidth' ./DOCS-IF-MIB:943 [5] {status-change} warning: legal status change = from `current' to `deprecated' for `docsIfQosProfMaxTxBurst' ./DOCS-IF-MIB:943 [5] {units-added} warning: units added to = `docsIfQosProfMaxTxBurst' ./DOCS-IF-MIB:943 [5] {description-changed} warning: description of = object definition `docsIfQosProfMaxTxBurst' changed ./DOCS-IF-MIB:943 [5] {ref-added} warning: reference added to = `docsIfQosProfMaxTxBurst' ..\ietf\DOCS-IF-MIB:551 [6] {previous-definition} info: previous = definition of `docsIfQosProfMaxTxBurst' ./DOCS-IF-MIB:1015 [5] {description-changed} warning: description of = object definition `docsIfSignalQualityTable' changed ..\ietf\DOCS-IF-MIB:587 [6] {previous-definition} info: previous = definition of `docsIfSignalQualityTable' ./DOCS-IF-MIB:1027 [5] {description-changed} warning: description of = object definition `docsIfSignalQualityEntry' changed ..\ietf\DOCS-IF-MIB:598 [6] {previous-definition} info: previous = definition of `docsIfSignalQualityEntry' ./DOCS-IF-MIB:1059 [5] {ref-changed} warning: reference of = `docsIfSigQIncludesContention' changed ..\ietf\DOCS-IF-MIB:622 [6] {previous-definition} info: previous = definition of `docsIfSigQIncludesContention' ./DOCS-IF-MIB:1072 [5] {units-added} warning: units added to = `docsIfSigQUnerroreds' ./DOCS-IF-MIB:1072 [5] {description-changed} warning: description of = object definition `docsIfSigQUnerroreds' changed ./DOCS-IF-MIB:1072 [5] {ref-changed} warning: reference of = `docsIfSigQUnerroreds' changed ..\ietf\DOCS-IF-MIB:634 [6] {previous-definition} info: previous = definition of `docsIfSigQUnerroreds' ./DOCS-IF-MIB:1092 [5] {units-added} warning: units added to = `docsIfSigQCorrecteds' ./DOCS-IF-MIB:1092 [5] {description-changed} warning: description of = object definition `docsIfSigQCorrecteds' changed ./DOCS-IF-MIB:1092 [5] {ref-changed} warning: reference of = `docsIfSigQCorrecteds' changed ..\ietf\DOCS-IF-MIB:647 [6] {previous-definition} info: previous = definition of `docsIfSigQCorrecteds' ./DOCS-IF-MIB:1111 [5] {units-added} warning: units added to = `docsIfSigQUncorrectables' ./DOCS-IF-MIB:1111 [5] {description-changed} warning: description of = object definition `docsIfSigQUncorrectables' changed ./DOCS-IF-MIB:1111 [5] {ref-changed} warning: reference of = `docsIfSigQUncorrectables' changed ..\ietf\DOCS-IF-MIB:660 [6] {previous-definition} info: previous = definition of `docsIfSigQUncorrectables' ./DOCS-IF-MIB:1131 [5] {ref-changed} warning: reference of = `docsIfSigQSignalNoise' changed ..\ietf\DOCS-IF-MIB:673 [6] {previous-definition} info: previous = definition of `docsIfSigQSignalNoise' ./DOCS-IF-MIB:1147 [5] {units-changed} warning: units of = `docsIfSigQMicroreflections' changed ./DOCS-IF-MIB:1147 [5] {description-changed} warning: description of = object definition `docsIfSigQMicroreflections' changed ./DOCS-IF-MIB:1147 [5] {ref-changed} warning: reference of = `docsIfSigQMicroreflections' changed ..\ietf\DOCS-IF-MIB:688 [6] {previous-definition} info: previous = definition of `docsIfSigQMicroreflections' ./DOCS-IF-MIB:1167 [3] {to-implicit} implicit type for = `docsIfSigQEqualizationData' replaces type `OctetString' ..\ietf\DOCS-IF-MIB:707 [6] {previous-definition} info: previous = definition of `docsIfSigQEqualizationData' ./DOCS-IF-MIB:1167 [3] {range-added} size `(0..512)' added to type = used in `docsIfSigQEqualizationData' ./DOCS-IF-MIB:1167 [5] {ref-changed} warning: reference of = `docsIfSigQEqualizationData' changed ..\ietf\DOCS-IF-MIB:707 [6] {previous-definition} info: previous = definition of `docsIfSigQEqualizationData' ./DOCS-IF-MIB:1298 [5] {ref-added} warning: reference added to = `docsIfCmCmtsAddress' ./DOCS-IF-MIB:1313 [5] {description-changed} warning: description of = object definition `docsIfCmCapabilities' changed ..\ietf\DOCS-IF-MIB:771 [6] {previous-definition} info: previous = definition of `docsIfCmCapabilities' ./DOCS-IF-MIB:1336 [5] {ref-changed} warning: reference of = `docsIfCmRangingRespTimeout' changed ..\ietf\DOCS-IF-MIB:789 [6] {previous-definition} info: previous = definition of `docsIfCmRangingRespTimeout' ./DOCS-IF-MIB:1349 [5] {description-changed} warning: description of = object definition `docsIfCmRangingTimeout' changed ./DOCS-IF-MIB:1349 [5] {ref-changed} warning: reference of = `docsIfCmRangingTimeout' changed ..\ietf\DOCS-IF-MIB:801 [6] {previous-definition} info: previous = definition of `docsIfCmRangingTimeout' ./DOCS-IF-MIB:1412 [5] {description-changed} warning: description of = object definition `docsIfCmStatusValue' changed ./DOCS-IF-MIB:1412 [5] {ref-changed} warning: reference of = `docsIfCmStatusValue' changed ..\ietf\DOCS-IF-MIB:858 [6] {previous-definition} info: previous = definition of `docsIfCmStatusValue' ./DOCS-IF-MIB:1449 [3] {to-implicit} implicit type for = `docsIfCmStatusCode' replaces type `OctetString' ..\ietf\DOCS-IF-MIB:884 [6] {previous-definition} info: previous = definition of `docsIfCmStatusCode' ./DOCS-IF-MIB:1449 [3] {range-added} size `(0..16)' added to type used = in `docsIfCmStatusCode' ./DOCS-IF-MIB:1449 [5] {description-changed} warning: description of = object definition `docsIfCmStatusCode' changed ./DOCS-IF-MIB:1449 [5] {ref-changed} warning: reference of = `docsIfCmStatusCode' changed ..\ietf\DOCS-IF-MIB:884 [6] {previous-definition} info: previous = definition of `docsIfCmStatusCode' ./DOCS-IF-MIB:1465 [5] {ref-changed} warning: reference of = `docsIfCmStatusTxPower' changed ..\ietf\DOCS-IF-MIB:899 [6] {previous-definition} info: previous defini= tion of `docsIfCmStatusTxPower' ./DOCS-IF-MIB:1488 [5] {description-changed} warning: description of = object definition `docsIfCmStatusLostSyncs' changed ./DOCS-IF-MIB:1488 [5] {ref-changed} warning: reference of = `docsIfCmStatusLostSyncs' changed ..\ietf\DOCS-IF-MIB:921 [6] {previous-definition} info: previous = definition of `docsIfCmStatusLostSyncs' ./DOCS-IF-MIB:1505 [5] {description-changed} warning: description of = object definition `docsIfCmStatusInvalidMaps' changed ./DOCS-IF-MIB:1505 [5] {ref-changed} warning: reference of = `docsIfCmStatusInvalidMaps' changed ..\ietf\DOCS-IF-MIB:933 [6] {previous-definition} info: previous = definition of `docsIfCmStatusInvalidMaps' ./DOCS-IF-MIB:1521 [5] {description-changed} warning: description of = object definition `docsIfCmStatusInvalidUcds' changed ./DOCS-IF-MIB:1521 [5] {ref-changed} warning: reference of = `docsIfCmStatusInvalidUcds' changed ..\ietf\DOCS-IF-MIB:944 [6] {previous-definition} info: previous = definition of `docsIfCmStatusInvalidUcds' ./DOCS-IF-MIB:1538 [5] {description-changed} warning: description of = object definition `docsIfCmStatusInvalidRangingResponses' changed ./DOCS-IF-MIB:1538 [5] {ref-added} warning: reference added to = `docsIfCmStatusInvalidRangingResponses' ..\ietf\DOCS-IF-MIB:958 [6] {previous-definition} info: previous = definition of `docsIfCmStatusInvalidRangingResponses' ./DOCS-IF-MIB:1555 [5] {description-changed} warning: description of = object definition `docsIfCmStatusInvalidRegistrationResponses' changed ./DOCS-IF-MIB:1555 [5] {ref-added} warning: reference added to = `docsIfCmStatusInvalidRegistrationResponses' ..\ietf\DOCS-IF-MIB:969 [6] {previous-definition} info: previous = definition of `docsIfCmStatusInvalidRegistrationResponses' ./DOCS-IF-MIB:1572 [5] {description-changed} warning: description of = object definition `docsIfCmStatusT1Timeouts' changed ./DOCS-IF-MIB:1572 [5] {ref-changed} warning: reference of = `docsIfCmStatusT1Timeouts' changed ..\ietf\DOCS-IF-MIB:978 [6] {previous-definition} info: previous = definition of `docsIfCmStatusT1Timeouts' ./DOCS-IF-MIB:1589 [5] {description-changed} warning: description of = object definition `docsIfCmStatusT2Timeouts' changed ./DOCS-IF-MIB:1589 [5] {ref-changed} warning: reference of = `docsIfCmStatusT2Timeouts' changed ..\ietf\DOCS-IF-MIB:989 [6] {previous-definition} info: previous = definition of `docsIfCmStatusT2Timeouts' ./DOCS-IF-MIB:1605 [5] {description-changed} warning: description of = object definition `docsIfCmStatusT3Timeouts' changed ./DOCS-IF-MIB:1605 [5] {ref-changed} warning: reference of = `docsIfCmStatusT3Timeouts' changed ..\ietf\DOCS-IF-MIB:1000 [6] {previous-definition} info: previous = definition of `docsIfCmStatusT3Timeouts' ./DOCS-IF-MIB:1621 [5] {description-changed} warning: description of = object definition `docsIfCmStatusT4Timeouts' changed ./DOCS-IF-MIB:1621 [5] {ref-changed} warning: reference of = `docsIfCmStatusT4Timeouts' changed ..\ietf\DOCS-IF-MIB:1011 [6] {previous-definition} info: previous = definition of `docsIfCmStatusT4Timeouts' ./DOCS-IF-MIB:1638 [5] {description-changed} warning: description of = object definition `docsIfCmStatusRangingAborteds' changed ./DOCS-IF-MIB:1638 [5] {ref-added} warning: reference added to = `docsIfCmStatusRangingAborteds' ..\ietf\DOCS-IF-MIB:1022 [6] {previous-definition} info: previous = definition of `docsIfCmStatusRangingAborteds' ./DOCS-IF-MIB:1797 [5] {units-added} warning: units added to = `docsIfCmServiceTxSlotsImmed' ./DOCS-IF-MIB:1797 [5] {description-changed} warning: description of = object definition `docsIfCmServiceTxSlotsImmed' changed ./DOCS-IF-MIB:1797 [5] {ref-changed} warning: reference of = `docsIfCmServiceTxSlotsImmed' changed ..\ietf\DOCS-IF-MIB:1094 [6] {previous-definition} info: previous = definition of `docsIfCmServiceTxSlotsImmed' ./DOCS-IF-MIB:1819 [5] {units-added} warning: units added to = `docsIfCmServiceTxSlotsDed' ./DOCS-IF-MIB:1819 [5] {description-changed} warning: description of = object definition `docsIfCmServiceTxSlotsDed' changed ./DOCS-IF-MIB:1819 [5] {ref-changed} warning: reference of = `docsIfCmServiceTxSlotsDed' changed ..\ietf\DOCS-IF-MIB:1110 [6] {previous-definition} info: previous = definition of `docsIfCmServiceTxSlotsDed' ./DOCS-IF-MIB:1839 [5] {description-changed} warning: description of = object definition `docsIfCmServiceTxRetries' changed ./DOCS-IF-MIB:1839 [5] {ref-changed} warning: reference of = `docsIfCmServiceTxRetries' changed ..\ietf\DOCS-IF-MIB:1123 [6] {previous-definition} info: previous = definition of `docsIfCmServiceTxRetries' ./DOCS-IF-MIB:1857 [5] {description-changed} warning: description of = object definition `docsIfCmServiceTxExceededs' changed ./DOCS-IF-MIB:1857 [5] {ref-changed} warning: reference of = `docsIfCmServiceTxExceededs' changed ..\ietf\DOCS-IF-MIB:1137 [6] {previous-definition} info: previous = definition of `docsIfCmServiceTxExceededs' ./DOCS-IF-MIB:1874 [5] {description-changed} warning: description of = object definition `docsIfCmServiceRqRetries' changed ./DOCS-IF-MIB:1874 [5] {ref-changed} warning: reference of = `docsIfCmServiceRqRetries' changed ..\ietf\DOCS-IF-MIB:1149 [6] {previous-definition} info: previous = definition of `docsIfCmServiceRqRetries' ./DOCS-IF-MIB:1892 [5] {description-changed} warning: description of = object definition `docsIfCmServiceRqExceededs' changed ./DOCS-IF-MIB:1892 [5] {ref-changed} warning: reference of = `docsIfCmServiceRqExceededs' changed ..\ietf\DOCS-IF-MIB:1164 [6] {previous-definition} info: previous = definition of `docsIfCmServiceRqExceededs' ./DOCS-IF-MIB:1993 [5] {description-changed} warning: description of = object definition `docsIfCmtsCapabilities' changed ..\ietf\DOCS-IF-MIB:1216 [3] {ref-removed} reference removed from = `docsIfCmtsCapabilities' ..\ietf\DOCS-IF-MIB:1216 [6] {previous-definition} info: previous = definition of `docsIfCmtsCapabilities' ./DOCS-IF-MIB:2011 [5] {ref-changed} warning: reference of = `docsIfCmtsSyncInterval' changed ..\ietf\DOCS-IF-MIB:1234 [6] {previous-definition} info: previous = definition of `docsIfCmtsSyncInterval' ./DOCS-IF-MIB:2025 [5] {ref-changed} warning: reference of = `docsIfCmtsUcdInterval' changed ..\ietf\DOCS-IF-MIB:1247 [6] {previous-definition} info: previous = definition of `docsIfCmtsUcdInterval' ./DOCS-IF-MIB:2053 [5] {description-changed} warning: description of = object definition `docsIfCmtsInsertionInterval' changed ./DOCS-IF-MIB:2053 [5] {ref-changed} warning: reference of = `docsIfCmtsInsertionInterval' changed ..\ietf\DOCS-IF-MIB:1274 [6] {previous-definition} info: previous = definition of `docsIfCmtsInsertionInterval' ./DOCS-IF-MIB:2070 [5] {description-changed} warning: description of = object definition `docsIfCmtsInvitedRangingAttempts' changed ./DOCS-IF-MIB:2070 [5] {ref-changed} warning: reference of = `docsIfCmtsInvitedRangingAttempts' changed ..\ietf\DOCS-IF-MIB:1290 [6] {previous-definition} info: previous = definition of `docsIfCmtsInvitedRangingAttempts' ./DOCS-IF-MIB:2084 [5] {description-changed} warning: description of = object definition `docsIfCmtsInsertInterval' changed ./DOCS-IF-MIB:2084 [5] {ref-changed} warning: reference of = `docsIfCmtsInsertInterval' changed ..\ietf\DOCS-IF-MIB:1303 [6] {previous-definition} info: previous = definition of `docsIfCmtsInsertInterval' ./DOCS-IF-MIB:2145 [5] {description-changed} warning: description of = object definition `docsIfCmtsStatusInvalidRangeReqs' changed ./DOCS-IF-MIB:2145 [5] {ref-added} warning: reference added to = `docsIfCmtsStatusInvalidRangeReqs' ..\ietf\DOCS-IF-MIB:1353 [6] {previous-definition} info: previous = definition of `docsIfCmtsStatusInvalidRangeReqs' ./DOCS-IF-MIB:2163 [5] {description-changed} warning: description of = object definition `docsIfCmtsStatusRangingAborteds' changed ./DOCS-IF-MIB:2163 [5] {ref-added} warning: reference added to = `docsIfCmtsStatusRangingAborteds' ..\ietf\DOCS-IF-MIB:1362 [6] {previous-definition} info: previous = definition of `docsIfCmtsStatusRangingAborteds' ./DOCS-IF-MIB:2180 [5] {description-changed} warning: description of = object definition `docsIfCmtsStatusInvalidRegReqs' changed ./DOCS-IF-MIB:2180 [5] {ref-added} warning: reference added to = `docsIfCmtsStatusInvalidRegReqs' ..\ietf\DOCS-IF-MIB:1371 [6] {previous-definition} info: previous = definition of `docsIfCmtsStatusInvalidRegReqs' ./DOCS-IF-MIB:2199 [5] {description-changed} warning: description of = object definition `docsIfCmtsStatusFailedRegReqs' changed ./DOCS-IF-MIB:2199 [5] {ref-added} warning: reference added to = `docsIfCmtsStatusFailedRegReqs' ..\ietf\DOCS-IF-MIB:1380 [6] {previous-definition} info: previous = definition of `docsIfCmtsStatusFailedRegReqs' ./DOCS-IF-MIB:2217 [5] {description-changed} warning: description of = object definition `docsIfCmtsStatusInvalidDataReqs' changed ..\ietf\DOCS-IF-MIB:1390 [6] {previous-definition} info: previous = definition of `docsIfCmtsStatusInvalidDataReqs' ./DOCS-IF-MIB:2230 [5] {description-changed} warning: description of = object definition `docsIfCmtsStatusT5Timeouts' changed ./DOCS-IF-MIB:2230 [5] {ref-added} warning: reference added to = `docsIfCmtsStatusT5Timeouts' ..\ietf\DOCS-IF-MIB:1399 [6] {previous-definition} info: previous = definition of `docsIfCmtsStatusT5Timeouts' ./DOCS-IF-MIB:2301 [5] {description-changed} warning: description of = object definition `docsIfCmtsCmStatusIndex' changed ..\ietf\DOCS-IF-MIB:1451 [6] {previous-definition} info: previous = definition of `docsIfCmtsCmStatusIndex' ./DOCS-IF-MIB:2311 [5] {ref-added} warning: reference added to = `docsIfCmtsCmStatusMacAddress' ./DOCS-IF-MIB:2325 [5] {status-change} warning: legal status change = from `current' to `deprecated' for `docsIfCmtsCmStatusIpAddress' ./DOCS-IF-MIB:2325 [5] {description-changed} warning: description of = object definition `docsIfCmtsCmStatusIpAddress' changed ..\ietf\DOCS-IF-MIB:1471 [6] {previous-definition} info: previous = definition of `docsIfCmtsCmStatusIpAddress' ./DOCS-IF-MIB:2352 [5] {description-changed} warning: description of = object definition `docsIfCmtsCmStatusUpChannelIfIndex' changed ..\ietf\DOCS-IF-MIB:1493 [6] {previous-definition} info: previous = definition of `docsIfCmtsCmStatusUpChannelIfIndex' ./DOCS-IF-MIB:2365 [5] {description-changed} warning: description of = object definition `docsIfCmtsCmStatusRxPower' changed ./DOCS-IF-MIB:2365 [5] {ref-changed} warning: reference of = `docsIfCmtsCmStatusRxPower' changed ..\ietf\DOCS-IF-MIB:1503 [6] {previous-definition} info: previous = definition of `docsIfCmtsCmStatusRxPower' ./DOCS-IF-MIB:2381 [3] {to-implicit} implicit type for = `docsIfCmtsCmStatusTimingOffset' replaces type `Unsigned32' ..\ietf\DOCS-IF-MIB:1518 [6] {previous-definition} info: previous = definition of `docsIfCmtsCmStatusTimingOffset' ./DOCS-IF-MIB:2381 [3] {range-added} range `(0..4294967295)' added to = type used in `docsIfCmtsCmStatusTimingOffset' ./DOCS-IF-MIB:2381 [5] {description-changed} warning: description of = object definition `docsIfCmtsCmStatusTimingOffset' changed ./DOCS-IF-MIB:2381 [5] {ref-changed} warning: reference of = `docsIfCmtsCmStatusTimingOffset' changed ..\ietf\DOCS-IF-MIB:1518 [6] {previous-definition} info: previous = definition of `docsIfCmtsCmStatusTimingOffset' ./DOCS-IF-MIB:2400 [3] {to-implicit} implicit type for = `docsIfCmtsCmStatusEqualizationData' replaces type `OctetString' ..\ietf\DOCS-IF-MIB:1533 [6] {previous-definition} info: previous = definition of `docsIfCmtsCmStatusEqualizationData' ./DOCS-IF-MIB:2400 [3] {range-added} size `(0..512)' added to type = used in `docsIfCmtsCmStatusEqualizationData' ./DOCS-IF-MIB:2400 [5] {ref-changed} warning: reference of = `docsIfCmtsCmStatusEqualizationData' changed ..\ietf\DOCS-IF-MIB:1533 [6] {previous-definition} info: previous = definition of `docsIfCmtsCmStatusEqualizationData' ./DOCS-IF-MIB:2414 [5] {named-number-added} warning: named number = `operational' added to type used in `docsIfCmtsCmStatusValue' ./DOCS-IF-MIB:2414 [5] {named-number-added} warning: named number = `registeredBPIInitializing' added to type used in = `docsIfCmtsCmStatusValue' ./DOCS-IF-MIB:2414 [5] {description-changed} warning: description of = object definition `docsIfCmtsCmStatusValue' changed ./DOCS-IF-MIB:2414 [5] {ref-changed} warning: reference of = `docsIfCmtsCmStatusValue' changed ..\ietf\DOCS-IF-MIB:1546 [6] {previous-definition} info: previous = definition of `docsIfCmtsCmStatusValue' ./DOCS-IF-MIB:2471 [5] {description-changed} warning: description of = object definition `docsIfCmtsCmStatusUnerroreds' changed ./DOCS-IF-MIB:2471 [5] {ref-changed} warning: reference of = `docsIfCmtsCmStatusUnerroreds' changed ..\ietf\DOCS-IF-MIB:1588 [6] {previous-definition} info: previous = definition of `docsIfCmtsCmStatusUnerroreds' ./DOCS-IF-MIB:2487 [5] {description-changed} warning: description of = object definition `docsIfCmtsCmStatusCorrecteds' changed ./DOCS-IF-MIB:2487 [5] {ref-changed} warning: reference of = `docsIfCmtsCmStatusCorrecteds' changed ..\ietf\DOCS-IF-MIB:1599 [6] {previous-definition} info: previous = definition of `docsIfCmtsCmStatusCorrecteds' ./DOCS-IF-MIB:2505 [5] {description-changed} warning: description of = object definition `docsIfCmtsCmStatusUncorrectables' changed ./DOCS-IF-MIB:2505 [5] {ref-changed} warning: reference of = `docsIfCmtsCmStatusUncorrectables' changed ..\ietf\DOCS-IF-MIB:1611 [6] {previous-definition} info: previous = definition of `docsIfCmtsCmStatusUncorrectables' ./DOCS-IF-MIB:2522 [5] {ref-added} warning: reference added to = `docsIfCmtsCmStatusSignalNoise' ./DOCS-IF-MIB:2538 [5] {description-changed} warning: description of = object definition `docsIfCmtsCmStatusMicroreflections' changed ./DOCS-IF-MIB:2538 [5] {ref-changed} warning: reference of = `docsIfCmtsCmStatusMicroreflections' changed ..\ietf\DOCS-IF-MIB:1635 [6] {previous-definition} info: previous = definition of `docsIfCmtsCmStatusMicroreflections' ./DOCS-IF-MIB:2748 [5] {status-change} warning: legal status change = from `current' to `deprecated' for `docsIfCmtsServiceCmStatusIndex' ./DOCS-IF-MIB:2748 [5] {description-changed} warning: description of = object definition `docsIfCmtsServiceCmStatusIndex' changed ..\ietf\DOCS-IF-MIB:1706 [6] {previous-definition} info: previous = definition of `docsIfCmtsServiceCmStatusIndex' ./DOCS-IF-MIB:2795 [5] {units-added} warning: units added to = `docsIfCmtsServiceInOctets' ./DOCS-IF-MIB:2795 [5] {description-changed} warning: description of = object definition `docsIfCmtsServiceInOctets' changed ..\ietf\DOCS-IF-MIB:1750 [6] {previous-definition} info: previous = definition of `docsIfCmtsServiceInOctets' ./DOCS-IF-MIB:2811 [5] {units-added} warning: units added to = `docsIfCmtsServiceInPackets' ./DOCS-IF-MIB:2811 [5] {description-changed} warning: description of = object definition `docsIfCmtsServiceInPackets' changed ..\ietf\DOCS-IF-MIB:1760 [6] {previous-definition} info: previous = definition of `docsIfCmtsServiceInPackets' ./DOCS-IF-MIB:2855 [5] {description-changed} warning: description of = object definition `docsIfCmtsModulationEntry' changed ..\ietf\DOCS-IF-MIB:1786 [6] {previous-definition} info: previous = definition of `docsIfCmtsModulationEntry' ./DOCS-IF-MIB:2928 [5] {named-number-added} warning: named number = `advPhyShortData' added to type used in = `docsIfCmtsModIntervalUsageCode' ./DOCS-IF-MIB:2928 [5] {named-number-added} warning: named number = `advPhyLongData' added to type used in `docsIfCmtsModIntervalUsageCode' ./DOCS-IF-MIB:2928 [5] {named-number-added} warning: named number = `ugs' added to type used in `docsIfCmtsModIntervalUsageCode' ./DOCS-IF-MIB:2928 [5] {ref-changed} warning: reference of = `docsIfCmtsModIntervalUsageCode' changed ..\ietf\DOCS-IF-MIB:1831 [6] {previous-definition} info: previous = definition of `docsIfCmtsModIntervalUsageCode' ./DOCS-IF-MIB:2961 [5] {named-number-added} warning: named number = `qam8' added to type used in `docsIfCmtsModType' ./DOCS-IF-MIB:2961 [5] {named-number-added} warning: named number = `qam32' added to type used in `docsIfCmtsModType' ./DOCS-IF-MIB:2961 [5] {named-number-added} warning: named number = `qam64' added to type used in `docsIfCmtsModType' ./DOCS-IF-MIB:2961 [5] {named-number-added} warning: named number = `qam128' added to type used in `docsIfCmtsModType' ./DOCS-IF-MIB:2961 [5] {description-changed} warning: description of = object definition `docsIfCmtsModType' changed ./DOCS-IF-MIB:2961 [5] {ref-changed} warning: reference of = `docsIfCmtsModType' changed ..\ietf\DOCS-IF-MIB:1860 [6] {previous-definition} info: previous = definition of `docsIfCmtsModType' ./DOCS-IF-MIB:2988 [3] {range-changed} range of type used in = `docsIfCmtsModPreambleLen' changed from `(0..1024)' to `(0..1536)' ./DOCS-IF-MIB:2987 [5] {units-added} warning: units added to = `docsIfCmtsModPreambleLen' ./DOCS-IF-MIB:2987 [5] {ref-changed} warning: reference of = `docsIfCmtsModPreambleLen' changed ..\ietf\DOCS-IF-MIB:1880 [6] {previous-definition} info: previous = definition of `docsIfCmtsModPreambleLen' ./DOCS-IF-MIB:3002 [5] {ref-added} warning: reference added to = `docsIfCmtsModDifferentialEncoding' ./DOCS-IF-MIB:3018 [3] {range-changed} range of type used in = `docsIfCmtsModFECErrorCorrection' changed from `(0..10)' to `(0..16)' ./DOCS-IF-MIB:3017 [5] {units-added} warning: units added to = `docsIfCmtsModFECErrorCorrection' ./DOCS-IF-MIB:3017 [5] {ref-changed} warning: reference of = `docsIfCmtsModFECErrorCorrection' changed ..\ietf\DOCS-IF-MIB:1903 [6] {previous-definition} info: previous = definition of `docsIfCmtsModFECErrorCorrection' ./DOCS-IF-MIB:3034 [5] {units-added} warning: units added to = `docsIfCmtsModFECCodewordLength' ./DOCS-IF-MIB:3034 [5] {ref-changed} warning: reference of = `docsIfCmtsModFECCodewordLength' changed ..\ietf\DOCS-IF-MIB:1918 [6] {previous-definition} info: previous = definition of `docsIfCmtsModFECCodewordLength' ./DOCS-IF-MIB:3051 [5] {ref-changed} warning: reference of = `docsIfCmtsModScramblerSeed' changed ..\ietf\DOCS-IF-MIB:1933 [6] {previous-definition} info: previous = definition of `docsIfCmtsModScramblerSeed' ./DOCS-IF-MIB:3065 [5] {units-added} warning: units added to = `docsIfCmtsModMaxBurstSize' ./DOCS-IF-MIB:3065 [5] {ref-added} warning: reference added to = `docsIfCmtsModMaxBurstSize' ./DOCS-IF-MIB:3082 [5] {units-added} warning: units added to = `docsIfCmtsModGuardTimeSize' ./DOCS-IF-MIB:3082 [5] {description-changed} warning: description of = object definition `docsIfCmtsModGuardTimeSize' changed ./DOCS-IF-MIB:3082 [5] {ref-changed} warning: reference of = `docsIfCmtsModGuardTimeSize' changed ..\ietf\DOCS-IF-MIB:1957 [6] {previous-definition} info: previous = definition of `docsIfCmtsModGuardTimeSize' ./DOCS-IF-MIB:3097 [5] {ref-changed} warning: reference of = `docsIfCmtsModLastCodewordShortened' changed ..\ietf\DOCS-IF-MIB:1970 [6] {previous-definition} info: previous = definition of `docsIfCmtsModLastCodewordShortened' ./DOCS-IF-MIB:3111 [5] {ref-changed} warning: reference of = `docsIfCmtsModScrambler' changed ..\ietf\DOCS-IF-MIB:1982 [6] {previous-definition} info: previous = definition of `docsIfCmtsModScrambler' ./DOCS-IF-MIB:3255 [5] {description-changed} warning: description of = object definition `docsIfCmtsQosProfilePermissions' changed ..\ietf\DOCS-IF-MIB:1994 [6] {previous-definition} info: previous = definition of `docsIfCmtsQosProfilePermissions' ./DOCS-IF-MIB:3283 [5] {description-changed} warning: description of = object definition `docsIfCmtsMacToCmTable' changed ..\ietf\DOCS-IF-MIB:2018 [6] {previous-definition} info: previous = definition of `docsIfCmtsMacToCmTable' ./DOCS-IF-MIB:345 [5] {node-added} warning: column = `docsIfDownChannelAnnex' has been added ./DOCS-IF-MIB:369 [5] {node-added} warning: column = `docsIfDownChannelStorageType' has been added ./DOCS-IF-MIB:606 [5] {node-added} warning: column = `docsIfUpChannelScdmaActiveCodes' has been added ./DOCS-IF-MIB:622 [5] {node-added} warning: column = `docsIfUpChannelScdmaCodesPerSlot' has been added ./DOCS-IF-MIB:637 [5] {node-added} warning: column = `docsIfUpChannelScdmaFrameSize' has been added ./DOCS-IF-MIB:651 [5] {node-added} warning: column = `docsIfUpChannelScdmaHoppingSeed' has been added ./DOCS-IF-MIB:665 [5] {node-added} warning: column = `docsIfUpChannelType' has been added ./DOCS-IF-MIB:681 [5] {node-added} warning: column = `docsIfUpChannelCloneFrom' has been added ./DOCS-IF-MIB:717 [5] {node-added} warning: column = `docsIfUpChannelUpdate' has been added ./DOCS-IF-MIB:733 [5] {node-added} warning: column = `docsIfUpChannelStatus' has been added ./DOCS-IF-MIB:782 [5] {node-added} warning: column = `docsIfUpChannelPreEqEnable' has been added ./DOCS-IF-MIB:989 [5] {node-added} warning: column = `docsIfQosProfMaxTransmitBurst' has been added ./DOCS-IF-MIB:1007 [5] {node-added} warning: column = `docsIfQosProfStorageType' has been added ./DOCS-IF-MIB:1184 [5] {node-added} warning: column = `docsIfSigQExtUnerroreds' has been added ./DOCS-IF-MIB:1204 [5] {node-added} warning: column = `docsIfSigQExtCorrecteds' has been added ./DOCS-IF-MIB:1224 [5] {node-added} warning: column = `docsIfSigQExtUncorrectables' has been added ./DOCS-IF-MIB:1249 [5] {node-added} warning: scalar = `docsIfDocsisBaseCapability' has been added ./DOCS-IF-MIB:1655 [5] {node-added} warning: column = `docsIfCmStatusDocsisOperMode' has been added ./DOCS-IF-MIB:1672 [5] {node-added} warning: column = `docsIfCmStatusModulationType' has been added ./DOCS-IF-MIB:1688 [5] {node-added} warning: column = `docsIfCmStatusEqualizationData' has been added ./DOCS-IF-MIB:1708 [5] {node-added} warning: column = `docsIfCmStatusUCCs' has been added ./DOCS-IF-MIB:1721 [5] {node-added} warning: column = `docsIfCmStatusUCCFails' has been added ./DOCS-IF-MIB:1909 [5] {node-added} warning: column = `docsIfCmServiceExtTxSlotsImmed' has been added ./DOCS-IF-MIB:1931 [5] {node-added} warning: column = `docsIfCmServiceExtTxSlotsDed' has been added ./DOCS-IF-MIB:2102 [5] {node-added} warning: column = `docsIfCmtsMacStorageType' has been added ./DOCS-IF-MIB:2563 [5] {node-added} warning: column = `docsIfCmtsCmStatusExtUnerroreds' has been added ./DOCS-IF-MIB:2579 [5] {node-added} warning: column = `docsIfCmtsCmStatusExtCorrecteds' has been added ./DOCS-IF-MIB:2596 [5] {node-added} warning: column = `docsIfCmtsCmStatusExtUncorrectables' has been added ./DOCS-IF-MIB:2614 [5] {node-added} warning: column = `docsIfCmtsCmStatusDocsisRegMode' has been added ./DOCS-IF-MIB:2627 [5] {node-added} warning: column = `docsIfCmtsCmStatusModulationType' has been added ./DOCS-IF-MIB:2642 [5] {node-added} warning: column = `docsIfCmtsCmStatusInetAddressType' has been added ./DOCS-IF-MIB:2654 [5] {node-added} warning: column = `docsIfCmtsCmStatusInetAddress' has been added ./DOCS-IF-MIB:2667 [5] {node-added} warning: column = `docsIfCmtsCmStatusValueLastUpdate' has been added ./DOCS-IF-MIB:2676 [5] {node-added} warning: column = `docsIfCmtsCmStatusHighResolutionTimingOffset' has been added ./DOCS-IF-MIB:2825 [5] {node-added} warning: column = `docsIfCmtsServiceNewCmStatusIndex' has been added ./DOCS-IF-MIB:3124 [5] {node-added} warning: column = `docsIfCmtsModByteInterleaverDepth' has been added ./DOCS-IF-MIB:3138 [5] {node-added} warning: column = `docsIfCmtsModByteInterleaverBlockSize' has been added ./DOCS-IF-MIB:3152 [5] {node-added} warning: column = `docsIfCmtsModPreambleType' has been added ./DOCS-IF-MIB:3172 [5] {node-added} warning: column = `docsIfCmtsModTcmErrorCorrectionOn' has been added ./DOCS-IF-MIB:3186 [5] {node-added} warning: column = `docsIfCmtsModScdmaInterleaverStepSize' has been added ./DOCS-IF-MIB:3200 [5] {node-added} warning: column = `docsIfCmtsModScdmaSpreaderEnable' has been added ./DOCS-IF-MIB:3215 [5] {node-added} warning: column = `docsIfCmtsModScdmaSubframeCodes' has been added ./DOCS-IF-MIB:3229 [5] {node-added} warning: column = `docsIfCmtsModChannelType' has been added ./DOCS-IF-MIB:3246 [5] {node-added} warning: column = `docsIfCmtsModStorageType' has been added ./DOCS-IF-MIB:3347 [5] {node-added} warning: scalar = `docsIfCmtsChannelUtilizationInterval' has been added ./DOCS-IF-MIB:3369 [5] {node-added} warning: table = `docsIfCmtsChannelUtilizationTable' has been added ./DOCS-IF-MIB:3378 [5] {node-added} warning: row = `docsIfCmtsChannelUtilizationEntry' has been added ./DOCS-IF-MIB:3398 [5] {node-added} warning: column = `docsIfCmtsChannelUtIfType' has been added ./DOCS-IF-MIB:3409 [5] {node-added} warning: column `docsIfCmtsChannelU= tId' has been added ./DOCS-IF-MIB:3419 [5] {node-added} warning: column = `docsIfCmtsChannelUtUtilization' has been added ./DOCS-IF-MIB:3495 [5] {node-added} warning: table = `docsIfCmtsDownChannelCounterTable' has been added ./DOCS-IF-MIB:3505 [5] {node-added} warning: row = `docsIfCmtsDownChannelCounterEntry' has been added ./DOCS-IF-MIB:3526 [5] {node-added} warning: column = `docsIfCmtsDownChnlCtrId' has been added ./DOCS-IF-MIB:3538 [5] {node-added} warning: column = `docsIfCmtsDownChnlCtrTotalBytes' has been added ./DOCS-IF-MIB:3556 [5] {node-added} warning: column = `docsIfCmtsDownChnlCtrUsedBytes' has been added ./DOCS-IF-MIB:3578 [5] {node-added} warning: column = `docsIfCmtsDownChnlCtrExtTotalBytes' has been added ./DOCS-IF-MIB:3596 [5] {node-added} warning: column = `docsIfCmtsDownChnlCtrExtUsedBytes' has been added ./DOCS-IF-MIB:3631 [5] {node-added} warning: table = `docsIfCmtsUpChannelCounterTable' has been added ./DOCS-IF-MIB:3641 [5] {node-added} warning: row = `docsIfCmtsUpChannelCounterEntry' has been added ./DOCS-IF-MIB:3689 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrId' has been added ./DOCS-IF-MIB:3697 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrTotalMslots' has been added ./DOCS-IF-MIB:3716 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrUcastGrantedMslots' has been added ./DOCS-IF-MIB:3738 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrTotalCntnMslots' has been added ./DOCS-IF-MIB:3757 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrUsedCntnMslots' has been added ./DOCS-IF-MIB:3778 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrExtTotalMslots' has been added ./DOCS-IF-MIB:3797 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrExtUcastGrantedMslots' has been added ./DOCS-IF-MIB:3820 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrExtTotalCntnMslots' has been added ./DOCS-IF-MIB:3839 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrExtUsedCntnMslots' has been added ./DOCS-IF-MIB:3859 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrCollCntnMslots' has been added ./DOCS-IF-MIB:3879 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrTotalCntnReqMslots' has been added ./DOCS-IF-MIB:3898 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrUsedCntnReqMslots' has been added ./DOCS-IF-MIB:3917 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrCollCntnReqMslots' has been added ./DOCS-IF-MIB:3937 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrTotalCntnReqDataMslots' has been added ./DOCS-IF-MIB:3956 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrUsedCntnReqDataMslots' has been added ./DOCS-IF-MIB:3976 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrCollCntnReqDataMslots' has been added ./DOCS-IF-MIB:3996 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrTotalCntnInitMaintMslots' has been added ./DOCS-IF-MIB:4016 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrUsedCntnInitMaintMslots' has been added ./DOCS-IF-MIB:4036 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrCollCntnInitMaintMslots' has been added ./DOCS-IF-MIB:4057 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrExtCollCntnMslots' has been added ./DOCS-IF-MIB:4077 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrExtTotalCntnReqMslots' has been added ./DOCS-IF-MIB:4096 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrExtUsedCntnReqMslots' has been added ./DOCS-IF-MIB:4115 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrExtCollCntnReqMslots' has been added ./DOCS-IF-MIB:4135 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrExtTotalCntnReqDataMslots' has been added ./DOCS-IF-MIB:4154 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrExtUsedCntnReqDataMslots' has been added ./DOCS-IF-MIB:4173 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrExtCollCntnReqDataMslots' has been added ./DOCS-IF-MIB:4194 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrExtTotalCntnInitMaintMslots' has been added ./DOCS-IF-MIB:4213 [5] {node-added} warning: column `docsIfCmtsUpChnlCt= rExtUsedCntnInitMaintMslots' has been added ./DOCS-IF-MIB:4233 [5] {node-added} warning: column = `docsIfCmtsUpChnlCtrExtCollCntnInitMaintMslots' has been added ./DOCS-IF-MIB:4283 [5] {node-added} warning: node = `docsIfCompliancesV2' has been added ./DOCS-IF-MIB:4284 [5] {node-added} warning: node `docsIfGroupsV2' has = been added ./DOCS-IF-MIB:4821 [5] {status-change} warning: legal status change = from `current' to `deprecated' for `docsIfBasicGroup' ..\ietf\DOCS-IF-MIB:2307 [6] {previous-definition} info: previous = definition of `docsIfBasicGroup' ./DOCS-IF-MIB:4861 [5] {status-change} warning: legal status change = from `current' to `deprecated' for `docsIfCmGroup' ..\ietf\DOCS-IF-MIB:2348 [6] {previous-definition} info: previous = definition of `docsIfCmGroup' ./DOCS-IF-MIB:4894 [5] {status-change} warning: legal status change = from `current' to `deprecated' for `docsIfCmtsGroup' ..\ietf\DOCS-IF-MIB:2385 [6] {previous-definition} info: previous = definition of `docsIfCmtsGroup' ..\ietf\DOCS-IF-MIB:2440 [1] {node-removed} group = `docsIfObsoleteGroup' has been deleted ./DOCS-IF-MIB:4948 [5] {node-added} warning: group = `docsIfObsoleteGroup' has been added ./DOCS-IF-MIB:4958 [5] {node-added} warning: group = `docsIfBasicGroupV2' has been added ./DOCS-IF-MIB:5012 [5] {node-added} warning: group `docsIfCmGroupV2' = has been added ./DOCS-IF-MIB:5053 [5] {node-added} warning: group `docsIfCmtsGroupV2' = has been added ./DOCS-IF-MIB:5145 [5] {node-added} warning: group = `docsIfCmtsOptionalGroupV2' has been added ./DOCS-IF-MIB:4286 [5] {status-change} warning: legal status change = from `current' to `deprecated' for `docsIfBasicCompliance' ..\ietf\DOCS-IF-MIB:2080 [6] {previous-definition} info: previous = definition of `docsIfBasicCompliance' ./DOCS-IF-MIB:4504 [5] {description-changed} warning: description of = object refinement `docsIfCmtsModType' changed ..\ietf\DOCS-IF-MIB:2295 [6] {previous-definition} info: previous = definition of `docsIfCmtsModType' ./DOCS-IF-MIB:4516 [5] {node-added} warning: compliance = `docsIfBasicComplianceV2' has been added ------_=_NextPart_000_01C4EDC3.B4D0EF36 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn ------_=_NextPart_000_01C4EDC3.B4D0EF36--