From mailman-owner@ietf.org Sat Jun 1 05:07:52 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10572 for ; Sat, 1 Jun 2002 05:07:52 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA17326 for ; Sat, 1 Jun 2002 05:08:18 -0400 (EDT) Date: Sat, 1 Jun 2002 05:08:18 -0400 (EDT) Message-Id: <200206010908.FAA17326@optimus.ietf.org> From: mailman-owner@ietf.org Subject: ietf.org mailing list memberships reminder To: ipcdn-archive@ietf.org X-No-Archive: yes Precedence: bulk X-Mailman-Version: 1.0 Precedence: bulk List-Id: Session Initiation Protocol 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, ipcdn-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@ietf.org. Thanks! Passwords for ipcdn-archive@lists.ietf.org: List Password // URL ---- -------- ipcdn@ietf.org BtQa https://www1.ietf.org/mailman/options/ipcdn/ipcdn-archive@lists.ietf.org From ipcdn-admin@ietf.org Wed Jun 12 07:14:01 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22941 for ; Wed, 12 Jun 2002 07:13:56 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18812; Wed, 12 Jun 2002 07:13:40 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18785 for ; Wed, 12 Jun 2002 07:13:38 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22766; Wed, 12 Jun 2002 07:13:01 -0400 (EDT) Message-Id: <200206121113.HAA22766@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ipcdn@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Wed, 12 Jun 2002 07:13:00 -0400 Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-docs-rfmibv2-02.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over Cable Data Network Working Group of the IETF. Title : Radio Frequency (RF) Interface Management Information Base for DOCSIS 2.0 compliant RF interfaces Author(s) : A. Goren, D. Raftus Filename : draft-ietf-ipcdn-docs-rfmibv2-02.txt Pages : 85 Date : 11-Jun-02 This memo is a draft revision of the standards track RFC-2670. Please see 'Section 9 Changes from RFC2670' for a description of modifications. This document or its successor will obsolete RFC-2670 when accepted. This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP- based management of DOCSIS compliant Radio Frequency (RF) interfaces. This memo specifies a MIB module in a manner that is compliant to the SNMP SMIv2 [5][6][7]. The set of objects are consistent with the SNMP framework and existing SNMP standards. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipcdn-docs-rfmibv2-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020611122710.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipcdn-docs-rfmibv2-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020611122710.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From daemon@optimus.ietf.org Wed Jun 12 07:14:02 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22962 for ; Wed, 12 Jun 2002 07:14:01 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id HAA18917 for ipcdn-archive@odin.ietf.org; Wed, 12 Jun 2002 07:14:36 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18812; Wed, 12 Jun 2002 07:13:40 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18785 for ; Wed, 12 Jun 2002 07:13:38 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22766; Wed, 12 Jun 2002 07:13:01 -0400 (EDT) Message-Id: <200206121113.HAA22766@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ipcdn@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Wed, 12 Jun 2002 07:13:00 -0400 Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-docs-rfmibv2-02.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over Cable Data Network Working Group of the IETF. Title : Radio Frequency (RF) Interface Management Information Base for DOCSIS 2.0 compliant RF interfaces Author(s) : A. Goren, D. Raftus Filename : draft-ietf-ipcdn-docs-rfmibv2-02.txt Pages : 85 Date : 11-Jun-02 This memo is a draft revision of the standards track RFC-2670. Please see 'Section 9 Changes from RFC2670' for a description of modifications. This document or its successor will obsolete RFC-2670 when accepted. This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP- based management of DOCSIS compliant Radio Frequency (RF) interfaces. This memo specifies a MIB module in a manner that is compliant to the SNMP SMIv2 [5][6][7]. The set of objects are consistent with the SNMP framework and existing SNMP standards. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipcdn-docs-rfmibv2-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020611122710.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipcdn-docs-rfmibv2-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020611122710.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Wed Jun 12 09:06:39 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26532 for ; Wed, 12 Jun 2002 09:06:39 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA26781; Wed, 12 Jun 2002 09:06:30 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA26736 for ; Wed, 12 Jun 2002 09:06:29 -0400 (EDT) Received: from scbh01.terayon.com ([63.201.251.8]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26496 for ; Wed, 12 Jun 2002 09:05:51 -0400 (EDT) Received: by SCBH01 with Internet Mail Service (5.5.2653.19) id ; Wed, 12 Jun 2002 06:07:12 -0700 Message-ID: From: "Raftus, David" To: "Ipcdn List (E-mail)" , "Docsis 20 Reflector (E-mail)" , "Docsis Oss Reflector (E-mail)" Subject: FW: [ipcdn] I-D ACTION:draft-ietf-ipcdn-docs-rfmibv2-02.txt Date: Wed, 12 Jun 2002 06:07:09 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C21212.0F0C4990" Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org This 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_01C21212.0F0C4990 Content-Type: text/plain; charset="iso-8859-1" Hi, I'm posting this message in case anyone saw the ipcdn message below and wondered about which version of the RF mib is required by Docsis applications. Both Docsis 1.1 and 2.0 currently require v2_04 of the RF mib. The version of the RF mib (v2_01) last recorded by the IETF expired after a six month period. The IETF cannot simply jump from v2_01 to v2_04, so there will be a series of announcements in the near future to progress from v2_01 to v2_02 to v2_03 to v2_04. Shortly both the IETF and Docsis will be in sync with the latest version - v2_04. Sorry for the confusion, Dave ************************************ David Raftus Imedia Semiconductor 340 Terry Fox Drive, Suite 202 Ottawa Canada K2K 3A2 david.raftus@imedia.com 613.592.1052 ext 222 ************************************ -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: Wednesday, June 12, 2002 7:13 AM Cc: ipcdn@ietf.org Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-docs-rfmibv2-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over Cable Data Network Working Group of the IETF. Title : Radio Frequency (RF) Interface Management Information Base for DOCSIS 2.0 compliant RF interfaces Author(s) : A. Goren, D. Raftus Filename : draft-ietf-ipcdn-docs-rfmibv2-02.txt Pages : 85 Date : 11-Jun-02 This memo is a draft revision of the standards track RFC-2670. Please see 'Section 9 Changes from RFC2670' for a description of modifications. This document or its successor will obsolete RFC-2670 when accepted. This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP- based management of DOCSIS compliant Radio Frequency (RF) interfaces. This memo specifies a MIB module in a manner that is compliant to the SNMP SMIv2 [5][6][7]. The set of objects are consistent with the SNMP framework and existing SNMP standards. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipcdn-docs-rfmibv2-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ------_=_NextPart_000_01C21212.0F0C4990 Content-Type: message/rfc822 To: Subject: Date: Wed, 12 Jun 2002 06:07:12 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_002_01C21212.0F0C4990" ------_=_NextPart_002_01C21212.0F0C4990 Content-Type: text/plain ------_=_NextPart_002_01C21212.0F0C4990 Content-Type: application/octet-stream; name="ATT16682" Content-Disposition: attachment; filename="ATT16682" Content-type: message/external-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020611122710.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-02.txt ------_=_NextPart_002_01C21212.0F0C4990 Content-Type: message/external-body; site="internet-drafts"; dir="draft-ietf-ipcdn-docs-rfmibv2-02.txt"; mode="ftp.ietf.org"; access-type="anon-ftp" ------_=_NextPart_002_01C21212.0F0C4990-- ------_=_NextPart_000_01C21212.0F0C4990-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From daemon@optimus.ietf.org Wed Jun 12 09:06:40 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26542 for ; Wed, 12 Jun 2002 09:06:40 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id JAA26902 for ipcdn-archive@odin.ietf.org; Wed, 12 Jun 2002 09:07:16 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA26781; Wed, 12 Jun 2002 09:06:30 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA26736 for ; Wed, 12 Jun 2002 09:06:29 -0400 (EDT) Received: from scbh01.terayon.com ([63.201.251.8]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26496 for ; Wed, 12 Jun 2002 09:05:51 -0400 (EDT) Received: by SCBH01 with Internet Mail Service (5.5.2653.19) id ; Wed, 12 Jun 2002 06:07:12 -0700 Message-ID: From: "Raftus, David" To: "Ipcdn List (E-mail)" , "Docsis 20 Reflector (E-mail)" , "Docsis Oss Reflector (E-mail)" Subject: FW: [ipcdn] I-D ACTION:draft-ietf-ipcdn-docs-rfmibv2-02.txt Date: Wed, 12 Jun 2002 06:07:09 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C21212.0F0C4990" Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org This 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_01C21212.0F0C4990 Content-Type: text/plain; charset="iso-8859-1" Hi, I'm posting this message in case anyone saw the ipcdn message below and wondered about which version of the RF mib is required by Docsis applications. Both Docsis 1.1 and 2.0 currently require v2_04 of the RF mib. The version of the RF mib (v2_01) last recorded by the IETF expired after a six month period. The IETF cannot simply jump from v2_01 to v2_04, so there will be a series of announcements in the near future to progress from v2_01 to v2_02 to v2_03 to v2_04. Shortly both the IETF and Docsis will be in sync with the latest version - v2_04. Sorry for the confusion, Dave ************************************ David Raftus Imedia Semiconductor 340 Terry Fox Drive, Suite 202 Ottawa Canada K2K 3A2 david.raftus@imedia.com 613.592.1052 ext 222 ************************************ -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: Wednesday, June 12, 2002 7:13 AM Cc: ipcdn@ietf.org Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-docs-rfmibv2-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over Cable Data Network Working Group of the IETF. Title : Radio Frequency (RF) Interface Management Information Base for DOCSIS 2.0 compliant RF interfaces Author(s) : A. Goren, D. Raftus Filename : draft-ietf-ipcdn-docs-rfmibv2-02.txt Pages : 85 Date : 11-Jun-02 This memo is a draft revision of the standards track RFC-2670. Please see 'Section 9 Changes from RFC2670' for a description of modifications. This document or its successor will obsolete RFC-2670 when accepted. This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP- based management of DOCSIS compliant Radio Frequency (RF) interfaces. This memo specifies a MIB module in a manner that is compliant to the SNMP SMIv2 [5][6][7]. The set of objects are consistent with the SNMP framework and existing SNMP standards. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipcdn-docs-rfmibv2-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ------_=_NextPart_000_01C21212.0F0C4990 Content-Type: message/rfc822 To: Subject: Date: Wed, 12 Jun 2002 06:07:12 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_002_01C21212.0F0C4990" ------_=_NextPart_002_01C21212.0F0C4990 Content-Type: text/plain ------_=_NextPart_002_01C21212.0F0C4990 Content-Type: application/octet-stream; name="ATT16682" Content-Disposition: attachment; filename="ATT16682" Content-type: message/external-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020611122710.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-02.txt ------_=_NextPart_002_01C21212.0F0C4990 Content-Type: message/external-body; site="internet-drafts"; dir="draft-ietf-ipcdn-docs-rfmibv2-02.txt"; mode="ftp.ietf.org"; access-type="anon-ftp" ------_=_NextPart_002_01C21212.0F0C4990-- ------_=_NextPart_000_01C21212.0F0C4990-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Wed Jun 12 17:09:44 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13119 for ; Wed, 12 Jun 2002 17:09:44 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA26396; Wed, 12 Jun 2002 17:06:34 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA05048 for ; Wed, 12 Jun 2002 11:20:15 -0400 (EDT) Received: from com21.ie (smtp.com21.ie [193.120.149.66]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01030 for ; Wed, 12 Jun 2002 11:19:39 -0400 (EDT) Received: from com21.ie (bell [192.168.250.122]) by com21.ie (8.11.0/8.11.0) with ESMTP id g5CFCnw07427 for ; Wed, 12 Jun 2002 16:12:49 +0100 (BST) Message-ID: <3D0765B1.1030809@com21.ie> Date: Wed, 12 Jun 2002 16:16:01 +0100 From: Alan Corbett User-Agent: Mozilla/5.0 (X11; U; SunOS 5.7 sun4u; en-US; m18) Gecko/20010307 Netscape6/6.01 X-Accept-Language: en MIME-Version: 1.0 To: ipcdn Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [ipcdn] draft-ietf-ipcdn-subscriber-mib-06.txt some clarifications needed Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org Content-Transfer-Encoding: 7bit Hi All, I have a few questions on the interaction between the docsSubMgtPktFilterTable and the docsSubMgtTcpUdpFilterTable and I would appreciate it if someone could answer them for me. Constraints as stated in Subscriber MIB: ============================= 2.2.4. Row Existence of docsSubMgtTcpUdpFilterTable The docsSubMgtTcpUdpFilterTable exists apart from the docsSubMgtPktFilterTable because its filtering criteria is expected to be applied to a minority of modems relative to docsSubMgtPktFilterTable. It is separate in order to emphasize this expectation to both CMTS vendors and network operators. The rules for row creation are: o Row creation in docsSubMgtTcpUdpFilterTable is disallowed unless the corresponding row in docsSubMgtPktFilterTable already exists (or that row is being created simultaneously in the same SNMP SET message). o Deletion of the row in docsSubMgtPktFilterTable deletes the corresponding row in docsSubMgtTcpUdpFilterTable. o Row creation for docsSubMgtPktFilterTable does not create the corresponding row in docsSubMgtTcpUdpFilterTable. o Row deletion of docsSubMgtTcpUdpFilterTable does not delete the corresponding row in docsSubMgtPktFilterTable. Questions: ======== 1) If the RowStatus of an entry in the docsSubMgtPktFilterTable is Active, are you allowed to modify that entry (other than changing the RowStatus) ? 2) Is creating/modifying/deleting an entry in the docsSubMgtTcpUdpFilterTable considered modifying the 'corresponding' entry (i.e. entry with the same indexes) in the docsSubMgtPktFilterTable ? 3) Are you allowed to put an entry in the docsSubMgtTcpUdpFilterTable into an 'Active' state if the 'corresponding' entry in the docsSubMgtPktFilterTable has a RowStatus of 'NotInService' or 'NotReady' ? 4) If the docsSubMgtPktFilterTable's entry RowStatus is 'NotInService' or 'NotReady' but the corresponding entry in the docsSubMgtTcpUdpFilterTable has a RowStatus of 'Active', should the Tcp & Udp filters be applied ? Thanking you in advance, Alan Corbett -------------------------------------------------------- Software Engineer, phone +353-21-7305883 Com21 email:acorbett@com21.ie _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From daemon@optimus.ietf.org Wed Jun 12 17:09:49 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13129 for ; Wed, 12 Jun 2002 17:09:44 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id RAA26516 for ipcdn-archive@odin.ietf.org; Wed, 12 Jun 2002 17:10:19 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA26396; Wed, 12 Jun 2002 17:06:34 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA05048 for ; Wed, 12 Jun 2002 11:20:15 -0400 (EDT) Received: from com21.ie (smtp.com21.ie [193.120.149.66]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01030 for ; Wed, 12 Jun 2002 11:19:39 -0400 (EDT) Received: from com21.ie (bell [192.168.250.122]) by com21.ie (8.11.0/8.11.0) with ESMTP id g5CFCnw07427 for ; Wed, 12 Jun 2002 16:12:49 +0100 (BST) Message-ID: <3D0765B1.1030809@com21.ie> Date: Wed, 12 Jun 2002 16:16:01 +0100 From: Alan Corbett User-Agent: Mozilla/5.0 (X11; U; SunOS 5.7 sun4u; en-US; m18) Gecko/20010307 Netscape6/6.01 X-Accept-Language: en MIME-Version: 1.0 To: ipcdn Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [ipcdn] draft-ietf-ipcdn-subscriber-mib-06.txt some clarifications needed Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org Content-Transfer-Encoding: 7bit Hi All, I have a few questions on the interaction between the docsSubMgtPktFilterTable and the docsSubMgtTcpUdpFilterTable and I would appreciate it if someone could answer them for me. Constraints as stated in Subscriber MIB: ============================= 2.2.4. Row Existence of docsSubMgtTcpUdpFilterTable The docsSubMgtTcpUdpFilterTable exists apart from the docsSubMgtPktFilterTable because its filtering criteria is expected to be applied to a minority of modems relative to docsSubMgtPktFilterTable. It is separate in order to emphasize this expectation to both CMTS vendors and network operators. The rules for row creation are: o Row creation in docsSubMgtTcpUdpFilterTable is disallowed unless the corresponding row in docsSubMgtPktFilterTable already exists (or that row is being created simultaneously in the same SNMP SET message). o Deletion of the row in docsSubMgtPktFilterTable deletes the corresponding row in docsSubMgtTcpUdpFilterTable. o Row creation for docsSubMgtPktFilterTable does not create the corresponding row in docsSubMgtTcpUdpFilterTable. o Row deletion of docsSubMgtTcpUdpFilterTable does not delete the corresponding row in docsSubMgtPktFilterTable. Questions: ======== 1) If the RowStatus of an entry in the docsSubMgtPktFilterTable is Active, are you allowed to modify that entry (other than changing the RowStatus) ? 2) Is creating/modifying/deleting an entry in the docsSubMgtTcpUdpFilterTable considered modifying the 'corresponding' entry (i.e. entry with the same indexes) in the docsSubMgtPktFilterTable ? 3) Are you allowed to put an entry in the docsSubMgtTcpUdpFilterTable into an 'Active' state if the 'corresponding' entry in the docsSubMgtPktFilterTable has a RowStatus of 'NotInService' or 'NotReady' ? 4) If the docsSubMgtPktFilterTable's entry RowStatus is 'NotInService' or 'NotReady' but the corresponding entry in the docsSubMgtTcpUdpFilterTable has a RowStatus of 'Active', should the Tcp & Udp filters be applied ? Thanking you in advance, Alan Corbett -------------------------------------------------------- Software Engineer, phone +353-21-7305883 Com21 email:acorbett@com21.ie _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Thu Jun 13 22:13:13 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08349 for ; Thu, 13 Jun 2002 22:13:13 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA06479; Thu, 13 Jun 2002 22:13:24 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA06450 for ; Thu, 13 Jun 2002 22:13:22 -0400 (EDT) Received: from mail8.nc.rr.com (fe8.southeast.rr.com [24.93.67.55]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08339 for ; Thu, 13 Jun 2002 22:12:46 -0400 (EDT) Received: from mail pickup service by mail8.nc.rr.com with Microsoft SMTPSVC; Thu, 13 Jun 2002 22:01:31 -0400 Received: from ncmx02.mgw.rr.com ([24.93.67.222]) by mail8.nc.rr.com with Microsoft SMTPSVC(5.5.1877.757.75); Wed, 12 Jun 2002 08:02:27 -0400 Received: from loki.ietf.org (loki.ietf.org [132.151.1.177]) by ncmx02.mgw.rr.com (8.12.2/8.12.2) with ESMTP id g5CC2Ra2015375; Wed, 12 Jun 2002 08:02:27 -0400 (EDT) Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id HAA06713 for ietf-123-outbound.05@ietf.org; Wed, 12 Jun 2002 07:55:01 -0400 (EDT) Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id HAA06284 for ; Wed, 12 Jun 2002 07:13:36 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22766; Wed, 12 Jun 2002 07:13:01 -0400 (EDT) Message-Id: <200206121113.HAA22766@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ipcdn@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Wed, 12 Jun 2002 07:13:00 -0400 Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-docs-rfmibv2-02.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over Cable Data Network Working Group of the IETF. Title : Radio Frequency (RF) Interface Management Information Base for DOCSIS 2.0 compliant RF interfaces Author(s) : A. Goren, D. Raftus Filename : draft-ietf-ipcdn-docs-rfmibv2-02.txt Pages : 85 Date : 11-Jun-02 This memo is a draft revision of the standards track RFC-2670. Please see 'Section 9 Changes from RFC2670' for a description of modifications. This document or its successor will obsolete RFC-2670 when accepted. This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP- based management of DOCSIS compliant Radio Frequency (RF) interfaces. This memo specifies a MIB module in a manner that is compliant to the SNMP SMIv2 [5][6][7]. The set of objects are consistent with the SNMP framework and existing SNMP standards. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipcdn-docs-rfmibv2-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020611122710.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipcdn-docs-rfmibv2-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020611122710.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From daemon@optimus.ietf.org Thu Jun 13 22:13:14 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08359 for ; Thu, 13 Jun 2002 22:13:13 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id WAA06494 for ipcdn-archive@odin.ietf.org; Thu, 13 Jun 2002 22:13:49 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA06479; Thu, 13 Jun 2002 22:13:24 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA06450 for ; Thu, 13 Jun 2002 22:13:22 -0400 (EDT) Received: from mail8.nc.rr.com (fe8.southeast.rr.com [24.93.67.55]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08339 for ; Thu, 13 Jun 2002 22:12:46 -0400 (EDT) Received: from mail pickup service by mail8.nc.rr.com with Microsoft SMTPSVC; Thu, 13 Jun 2002 22:01:31 -0400 Received: from ncmx02.mgw.rr.com ([24.93.67.222]) by mail8.nc.rr.com with Microsoft SMTPSVC(5.5.1877.757.75); Wed, 12 Jun 2002 08:02:27 -0400 Received: from loki.ietf.org (loki.ietf.org [132.151.1.177]) by ncmx02.mgw.rr.com (8.12.2/8.12.2) with ESMTP id g5CC2Ra2015375; Wed, 12 Jun 2002 08:02:27 -0400 (EDT) Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id HAA06713 for ietf-123-outbound.05@ietf.org; Wed, 12 Jun 2002 07:55:01 -0400 (EDT) Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id HAA06284 for ; Wed, 12 Jun 2002 07:13:36 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22766; Wed, 12 Jun 2002 07:13:01 -0400 (EDT) Message-Id: <200206121113.HAA22766@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ipcdn@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Wed, 12 Jun 2002 07:13:00 -0400 Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-docs-rfmibv2-02.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over Cable Data Network Working Group of the IETF. Title : Radio Frequency (RF) Interface Management Information Base for DOCSIS 2.0 compliant RF interfaces Author(s) : A. Goren, D. Raftus Filename : draft-ietf-ipcdn-docs-rfmibv2-02.txt Pages : 85 Date : 11-Jun-02 This memo is a draft revision of the standards track RFC-2670. Please see 'Section 9 Changes from RFC2670' for a description of modifications. This document or its successor will obsolete RFC-2670 when accepted. This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP- based management of DOCSIS compliant Radio Frequency (RF) interfaces. This memo specifies a MIB module in a manner that is compliant to the SNMP SMIv2 [5][6][7]. The set of objects are consistent with the SNMP framework and existing SNMP standards. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipcdn-docs-rfmibv2-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020611122710.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipcdn-docs-rfmibv2-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020611122710.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Fri Jun 14 07:32:08 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25111 for ; Fri, 14 Jun 2002 07:32:08 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA05277; Fri, 14 Jun 2002 07:32:02 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA05250 for ; Fri, 14 Jun 2002 07:32:01 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25074; Fri, 14 Jun 2002 07:31:23 -0400 (EDT) Message-Id: <200206141131.HAA25074@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ipcdn@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Fri, 14 Jun 2002 07:31:22 -0400 Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-docs-rfmibv2-03.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over Cable Data Network Working Group of the IETF. Title : Radio Frequency (RF) Interface Management Information Base for DOCSIS 2.0 compliant RF interfaces Author(s) : A. Goren, D. Raftus Filename : draft-ietf-ipcdn-docs-rfmibv2-03.txt Pages : 86 Date : 13-Jun-02 This memo is a draft revision of the standards track RFC-2670. Please see 'Section 9 Changes from RFC2670' for a description of modifications. This document or its successor will obsolete RFC-2670 when accepted. This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP- based management of DOCSIS compliant Radio Frequency (RF) interfaces. This memo specifies a MIB module in a manner that is compliant to the SNMP SMIv2 [5][6][7]. The set of objects are consistent with the SNMP framework and existing SNMP standards. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-03.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipcdn-docs-rfmibv2-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020613150212.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipcdn-docs-rfmibv2-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020613150212.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From daemon@optimus.ietf.org Fri Jun 14 07:32:09 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25119 for ; Fri, 14 Jun 2002 07:32:09 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id HAA05297 for ipcdn-archive@odin.ietf.org; Fri, 14 Jun 2002 07:32:45 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA05277; Fri, 14 Jun 2002 07:32:02 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA05250 for ; Fri, 14 Jun 2002 07:32:01 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25074; Fri, 14 Jun 2002 07:31:23 -0400 (EDT) Message-Id: <200206141131.HAA25074@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ipcdn@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Fri, 14 Jun 2002 07:31:22 -0400 Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-docs-rfmibv2-03.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over Cable Data Network Working Group of the IETF. Title : Radio Frequency (RF) Interface Management Information Base for DOCSIS 2.0 compliant RF interfaces Author(s) : A. Goren, D. Raftus Filename : draft-ietf-ipcdn-docs-rfmibv2-03.txt Pages : 86 Date : 13-Jun-02 This memo is a draft revision of the standards track RFC-2670. Please see 'Section 9 Changes from RFC2670' for a description of modifications. This document or its successor will obsolete RFC-2670 when accepted. This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP- based management of DOCSIS compliant Radio Frequency (RF) interfaces. This memo specifies a MIB module in a manner that is compliant to the SNMP SMIv2 [5][6][7]. The set of objects are consistent with the SNMP framework and existing SNMP standards. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-03.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipcdn-docs-rfmibv2-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020613150212.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipcdn-docs-rfmibv2-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020613150212.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Wed Jun 19 07:29:45 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13836 for ; Wed, 19 Jun 2002 07:29:45 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18857; Wed, 19 Jun 2002 07:29:28 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18833 for ; Wed, 19 Jun 2002 07:29:26 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13746; Wed, 19 Jun 2002 07:28:44 -0400 (EDT) Message-Id: <200206191128.HAA13746@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ipcdn@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Wed, 19 Jun 2002 07:28:44 -0400 Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-docs-rfmibv2-04.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over Cable Data Network Working Group of the IETF. Title : Radio Frequency (RF) Interface Management Information Base for DOCSIS 2.0 compliant RF interfaces Author(s) : A. Goren, D. Raftus Filename : draft-ietf-ipcdn-docs-rfmibv2-04.txt Pages : 86 Date : 18-Jun-02 This memo is a draft revision of the standards track RFC-2670. Please see 'Section 9 Changes from RFC2670' for a description of modifications. This document or its successor will obsolete RFC-2670 when accepted. This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP- based management of DOCSIS compliant Radio Frequency (RF) interfaces. This memo specifies a MIB module in a manner that is compliant to the SNMP SMIv2 [5][6][7]. The set of objects are consistent with the SNMP framework and existing SNMP standards. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-04.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipcdn-docs-rfmibv2-04.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020618145547.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipcdn-docs-rfmibv2-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020618145547.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From daemon@optimus.ietf.org Wed Jun 19 07:29:45 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13846 for ; Wed, 19 Jun 2002 07:29:45 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id HAA19087 for ipcdn-archive@odin.ietf.org; Wed, 19 Jun 2002 07:30:25 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18857; Wed, 19 Jun 2002 07:29:28 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18833 for ; Wed, 19 Jun 2002 07:29:26 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13746; Wed, 19 Jun 2002 07:28:44 -0400 (EDT) Message-Id: <200206191128.HAA13746@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ipcdn@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Wed, 19 Jun 2002 07:28:44 -0400 Subject: [ipcdn] I-D ACTION:draft-ietf-ipcdn-docs-rfmibv2-04.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over Cable Data Network Working Group of the IETF. Title : Radio Frequency (RF) Interface Management Information Base for DOCSIS 2.0 compliant RF interfaces Author(s) : A. Goren, D. Raftus Filename : draft-ietf-ipcdn-docs-rfmibv2-04.txt Pages : 86 Date : 18-Jun-02 This memo is a draft revision of the standards track RFC-2670. Please see 'Section 9 Changes from RFC2670' for a description of modifications. This document or its successor will obsolete RFC-2670 when accepted. This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP- based management of DOCSIS compliant Radio Frequency (RF) interfaces. This memo specifies a MIB module in a manner that is compliant to the SNMP SMIv2 [5][6][7]. The set of objects are consistent with the SNMP framework and existing SNMP standards. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-04.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipcdn-docs-rfmibv2-04.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020618145547.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ipcdn-docs-rfmibv2-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ipcdn-docs-rfmibv2-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020618145547.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Tue Jun 25 10:39:17 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07797 for ; Tue, 25 Jun 2002 10:39:16 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA15323; Tue, 25 Jun 2002 10:39:31 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA15292 for ; Tue, 25 Jun 2002 10:39:29 -0400 (EDT) Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07763 for ; Tue, 25 Jun 2002 10:38:43 -0400 (EDT) Received: from homail.ho.lucent.com (h135-17-192-10.lucent.com [135.17.192.10]) by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g5PEdPY26566 for ; Tue, 25 Jun 2002 10:39:25 -0400 (EDT) Received: from shrinivaspcho ([135.17.5.202]) by homail.ho.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id KAA04459; Tue, 25 Jun 2002 10:39:24 -0400 (EDT) Reply-To: From: "Shrinivas Samant" To: "IETF Ipcdn" Date: Thu, 25 Jul 2002 10:31:36 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Content-Transfer-Encoding: 7bit Subject: [ipcdn] Membership Query Interval in Passive mode IGMP Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org Content-Transfer-Encoding: 7bit Folks, In the passive mode IGMP, the CMTS determines the Membership Query Interval by looking at the inter-arrival times of the Membership Query messages. Formally: If n<2, MQI = 125 else MQI = MAX(125, MQn - MQn-1) where MQI is the Membership Query Interval in seconds, n is the number of Membership Queries seen and MQn is the epoch time at which the nth Membership Query was seen. Now, if the Router goes down after MQn-1 and comes up again after sometime, MQn - MQn-1, is not an accurately determined Membership Query Interval. Is there an upper limit on the value of MQI? How can we establish the MQI in such a scenario? Any suggestions/comments will help. Thanks, Shrini _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From daemon@optimus.ietf.org Tue Jun 25 10:39:20 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07818 for ; Tue, 25 Jun 2002 10:39:20 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id KAA15376 for ipcdn-archive@odin.ietf.org; Tue, 25 Jun 2002 10:40:05 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA15323; Tue, 25 Jun 2002 10:39:31 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA15292 for ; Tue, 25 Jun 2002 10:39:29 -0400 (EDT) Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07763 for ; Tue, 25 Jun 2002 10:38:43 -0400 (EDT) Received: from homail.ho.lucent.com (h135-17-192-10.lucent.com [135.17.192.10]) by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g5PEdPY26566 for ; Tue, 25 Jun 2002 10:39:25 -0400 (EDT) Received: from shrinivaspcho ([135.17.5.202]) by homail.ho.lucent.com (8.8.8+Sun/EMS-1.5 sol2) id KAA04459; Tue, 25 Jun 2002 10:39:24 -0400 (EDT) Reply-To: From: "Shrinivas Samant" To: "IETF Ipcdn" Date: Thu, 25 Jul 2002 10:31:36 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Content-Transfer-Encoding: 7bit Subject: [ipcdn] Membership Query Interval in Passive mode IGMP Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org Content-Transfer-Encoding: 7bit Folks, In the passive mode IGMP, the CMTS determines the Membership Query Interval by looking at the inter-arrival times of the Membership Query messages. Formally: If n<2, MQI = 125 else MQI = MAX(125, MQn - MQn-1) where MQI is the Membership Query Interval in seconds, n is the number of Membership Queries seen and MQn is the epoch time at which the nth Membership Query was seen. Now, if the Router goes down after MQn-1 and comes up again after sometime, MQn - MQn-1, is not an accurately determined Membership Query Interval. Is there an upper limit on the value of MQI? How can we establish the MQI in such a scenario? Any suggestions/comments will help. Thanks, Shrini _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Wed Jun 26 06:42:54 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10835 for ; Wed, 26 Jun 2002 06:42:54 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA17233; Wed, 26 Jun 2002 06:43:02 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA17194 for ; Wed, 26 Jun 2002 06:43:00 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10670; Wed, 26 Jun 2002 06:42:15 -0400 (EDT) Message-Id: <200206261042.GAA10670@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: ipcdn@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Wed, 26 Jun 2002 06:42:15 -0400 Subject: [ipcdn] I-D ACTION:draft-deketelaere-pktc-ipcdn-eventmess-00.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Management Event MIB for PacketCable/IPCablecom MTAs Author(s) : W. De Ketelaere, E. Nechamkin Filename : draft-deketelaere-pktc-ipcdn-eventmess-00.txt Pages : 26 Date : 25-Jun-02 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it provides a common data and format definition for events and specifies by what means events are transmitted for PacketCable/IPCablecom compliant Multimedia Terminal Adapter devices. This memo specifies a MIB module in a manner that is compliant to the SNMP SMIv2 [5][6][7]. The set of objects are consistent with the SNMP framework and existing SNMP standards A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-deketelaere-pktc-ipcdn-eventmess-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-deketelaere-pktc-ipcdn-eventmess-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-deketelaere-pktc-ipcdn-eventmess-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020625141939.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-deketelaere-pktc-ipcdn-eventmess-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-deketelaere-pktc-ipcdn-eventmess-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020625141939.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From daemon@optimus.ietf.org Wed Jun 26 06:42:55 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10843 for ; Wed, 26 Jun 2002 06:42:55 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id GAA17337 for ipcdn-archive@odin.ietf.org; Wed, 26 Jun 2002 06:43:38 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA17233; Wed, 26 Jun 2002 06:43:02 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA17194 for ; Wed, 26 Jun 2002 06:43:00 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10670; Wed, 26 Jun 2002 06:42:15 -0400 (EDT) Message-Id: <200206261042.GAA10670@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: ipcdn@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Wed, 26 Jun 2002 06:42:15 -0400 Subject: [ipcdn] I-D ACTION:draft-deketelaere-pktc-ipcdn-eventmess-00.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Management Event MIB for PacketCable/IPCablecom MTAs Author(s) : W. De Ketelaere, E. Nechamkin Filename : draft-deketelaere-pktc-ipcdn-eventmess-00.txt Pages : 26 Date : 25-Jun-02 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it provides a common data and format definition for events and specifies by what means events are transmitted for PacketCable/IPCablecom compliant Multimedia Terminal Adapter devices. This memo specifies a MIB module in a manner that is compliant to the SNMP SMIv2 [5][6][7]. The set of objects are consistent with the SNMP framework and existing SNMP standards A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-deketelaere-pktc-ipcdn-eventmess-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-deketelaere-pktc-ipcdn-eventmess-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-deketelaere-pktc-ipcdn-eventmess-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020625141939.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-deketelaere-pktc-ipcdn-eventmess-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-deketelaere-pktc-ipcdn-eventmess-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020625141939.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Thu Jun 27 06:39:54 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09229 for ; Thu, 27 Jun 2002 06:39:54 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA19899; Thu, 27 Jun 2002 06:40:12 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA19872 for ; Thu, 27 Jun 2002 06:40:11 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09140; Thu, 27 Jun 2002 06:39:25 -0400 (EDT) Message-Id: <200206271039.GAA09140@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: ipcdn@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 27 Jun 2002 06:39:25 -0400 Subject: [ipcdn] I-D ACTION:draft-osman-pktc-ipcdn-mtamib-00.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Multimedia Terminal Adapter (MTA) Management Information Base for PacketCable 1.0 compliant devices Author(s) : M. Osman, E. Nechamkin Filename : draft-osman-pktc-ipcdn-mtamib-00.txt Pages : 40 Date : 26-Jun-02 This memo is a draft document of the initial version of the document. This document does not have any predecessors. This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP- based management of PacketCable 1.0 compliant Media Terminal Adapter (MTA) devices. This memo specifies a MIB module in a manner that is compliant to the SNMP SMIv2 [5][6][7]. The set of objects are consistent with the SNMP framework and existing SNMP standards. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-osman-pktc-ipcdn-mtamib-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-osman-pktc-ipcdn-mtamib-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-osman-pktc-ipcdn-mtamib-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020626134808.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-osman-pktc-ipcdn-mtamib-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-osman-pktc-ipcdn-mtamib-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020626134808.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Thu Jun 27 06:40:08 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09302 for ; Thu, 27 Jun 2002 06:40:08 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA19997; Thu, 27 Jun 2002 06:40:35 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA19971 for ; Thu, 27 Jun 2002 06:40:33 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09211; Thu, 27 Jun 2002 06:39:47 -0400 (EDT) Message-Id: <200206271039.GAA09211@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: ipcdn@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 27 Jun 2002 06:39:47 -0400 Subject: [ipcdn] I-D ACTION:draft-channabasappa-pktc-ipcdn-mib-framework-00.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Packetcable/IPCablecom MIB Framework Author(s) : S. Channabasappa, W. De Ketelaere Filename : draft-channabasappa-pktc-ipcdn-mib-framework-00.txt Pages : 32 Date : 26-Jun-02 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it provides information on the management requirements of PacketCable(TM)/IPCablecom specific devices and defines a framework in which PacketCable MIBs are defined. This document does not precede any previously issued document. It is, however, intended to support and complement the actual Packetcable MIB documents, which are issued separately. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-channabasappa-pktc-ipcdn-mib-framework-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-channabasappa-pktc-ipcdn-mib-framework-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-channabasappa-pktc-ipcdn-mib-framework-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020626134849.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-channabasappa-pktc-ipcdn-mib-framework-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-channabasappa-pktc-ipcdn-mib-framework-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020626134849.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From daemon@optimus.ietf.org Thu Jun 27 06:40:09 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09315 for ; Thu, 27 Jun 2002 06:40:09 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id GAA20085 for ipcdn-archive@odin.ietf.org; Thu, 27 Jun 2002 06:40:53 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA19997; Thu, 27 Jun 2002 06:40:35 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA19971 for ; Thu, 27 Jun 2002 06:40:33 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09211; Thu, 27 Jun 2002 06:39:47 -0400 (EDT) Message-Id: <200206271039.GAA09211@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: ipcdn@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 27 Jun 2002 06:39:47 -0400 Subject: [ipcdn] I-D ACTION:draft-channabasappa-pktc-ipcdn-mib-framework-00.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Packetcable/IPCablecom MIB Framework Author(s) : S. Channabasappa, W. De Ketelaere Filename : draft-channabasappa-pktc-ipcdn-mib-framework-00.txt Pages : 32 Date : 26-Jun-02 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it provides information on the management requirements of PacketCable(TM)/IPCablecom specific devices and defines a framework in which PacketCable MIBs are defined. This document does not precede any previously issued document. It is, however, intended to support and complement the actual Packetcable MIB documents, which are issued separately. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-channabasappa-pktc-ipcdn-mib-framework-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-channabasappa-pktc-ipcdn-mib-framework-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-channabasappa-pktc-ipcdn-mib-framework-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020626134849.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-channabasappa-pktc-ipcdn-mib-framework-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-channabasappa-pktc-ipcdn-mib-framework-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020626134849.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From daemon@optimus.ietf.org Thu Jun 27 07:25:58 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09236 for ; Thu, 27 Jun 2002 06:39:54 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id GAA20015 for ipcdn-archive@odin.ietf.org; Thu, 27 Jun 2002 06:40:38 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA19899; Thu, 27 Jun 2002 06:40:12 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA19872 for ; Thu, 27 Jun 2002 06:40:11 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09140; Thu, 27 Jun 2002 06:39:25 -0400 (EDT) Message-Id: <200206271039.GAA09140@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: ipcdn@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 27 Jun 2002 06:39:25 -0400 Subject: [ipcdn] I-D ACTION:draft-osman-pktc-ipcdn-mtamib-00.txt Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Multimedia Terminal Adapter (MTA) Management Information Base for PacketCable 1.0 compliant devices Author(s) : M. Osman, E. Nechamkin Filename : draft-osman-pktc-ipcdn-mtamib-00.txt Pages : 40 Date : 26-Jun-02 This memo is a draft document of the initial version of the document. This document does not have any predecessors. This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP- based management of PacketCable 1.0 compliant Media Terminal Adapter (MTA) devices. This memo specifies a MIB module in a manner that is compliant to the SNMP SMIv2 [5][6][7]. The set of objects are consistent with the SNMP framework and existing SNMP standards. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-osman-pktc-ipcdn-mtamib-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-osman-pktc-ipcdn-mtamib-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-osman-pktc-ipcdn-mtamib-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020626134808.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-osman-pktc-ipcdn-mtamib-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-osman-pktc-ipcdn-mtamib-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020626134808.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn From ipcdn-admin@ietf.org Fri Jun 28 10:58:43 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29606 for ; Fri, 28 Jun 2002 10:58:43 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00666; Fri, 28 Jun 2002 10:59:06 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00631 for ; Fri, 28 Jun 2002 10:59:03 -0400 (EDT) Received: from motgate3.mot.com (motgate3.mot.com [144.189.100.103]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29588 for ; Fri, 28 Jun 2002 10:58:16 -0400 (EDT) Received: [from pobox4.mot.com (pobox4.mot.com [10.64.251.243]) by motgate3.mot.com (motgate3 2.1) with ESMTP id HAA03404 for ; Fri, 28 Jun 2002 07:58:18 -0700 (MST)] Received: [from pa06exr01.gic.gi.com (pa06exr01.gic.gi.com [168.84.176.73]) by pobox4.mot.com (MOT-pobox4 2.0) with ESMTP id HAA17581 for ; Fri, 28 Jun 2002 07:59:00 -0700 (MST)] Received: from ariel.gi.com ([168.84.84.10]) by pa06exr01.gic.gi.com (8.11.6/8.11.6) with ESMTP id g5SEqGE31413 for ; Fri, 28 Jun 2002 09:52:16 -0500 Received: from ntas0028.gi.com ([168.84.84.98]) by GI.COM (PMDF V5.2-31 #46260) with ESMTP id <01KJGGIMSG14G792PX@GI.COM> for ipcdn@ietf.org; Fri, 28 Jun 2002 07:58:48 PDT Received: by ntas0028.gi.com with Internet Mail Service (5.5.2650.21) id ; Fri, 28 Jun 2002 07:54:14 -0400 Content-return: allowed Date: Fri, 28 Jun 2002 10:59:21 -0400 From: "Nakanishi Greg (SD-EX)" Subject: RE: [ipcdn] Membership Query Interval in Passive mode IGMP To: , IETF Ipcdn Message-id: <97DEDE66B3DCD11199D200805FA71BE206A8467D@ntas0027.gi.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="ISO-2022-JP" Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org Shrini, I think the scenario you mention should be a transient condition. Once the router comes up and issues a couple of MQs, the MQI will be "correct" again. greg > -----Original Message----- > From: Shrinivas Samant [mailto:ssamant@lucent.com] > Sent: Thursday, July 25, 2002 7:32 AM > To: IETF Ipcdn > Subject: [ipcdn] Membership Query Interval in Passive mode IGMP > > > Folks, > In the passive mode IGMP, the CMTS determines the Membership > Query Interval > by looking at the inter-arrival times of the Membership Query > messages. > Formally: If n<2, MQI = 125 else MQI = MAX(125, MQn - MQn-1) > where MQI is > the Membership Query Interval in seconds, n is the number of > Membership > Queries seen and MQn is the epoch time at which the nth > Membership Query was > seen. > > Now, if the Router goes down after MQn-1 and comes up again > after sometime, > MQn - MQn-1, is not an accurately determined Membership Query > Interval. > > Is there an upper limit on the value of MQI? How can we > establish the MQI in > such a scenario? > Any suggestions/comments will help. > > Thanks, > > Shrini > > > _______________________________________________ > 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 daemon@optimus.ietf.org Fri Jun 28 10:58:44 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29612 for ; Fri, 28 Jun 2002 10:58:43 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id KAA00744 for ipcdn-archive@odin.ietf.org; Fri, 28 Jun 2002 10:59:30 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00666; Fri, 28 Jun 2002 10:59:06 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00631 for ; Fri, 28 Jun 2002 10:59:03 -0400 (EDT) Received: from motgate3.mot.com (motgate3.mot.com [144.189.100.103]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29588 for ; Fri, 28 Jun 2002 10:58:16 -0400 (EDT) Received: [from pobox4.mot.com (pobox4.mot.com [10.64.251.243]) by motgate3.mot.com (motgate3 2.1) with ESMTP id HAA03404 for ; Fri, 28 Jun 2002 07:58:18 -0700 (MST)] Received: [from pa06exr01.gic.gi.com (pa06exr01.gic.gi.com [168.84.176.73]) by pobox4.mot.com (MOT-pobox4 2.0) with ESMTP id HAA17581 for ; Fri, 28 Jun 2002 07:59:00 -0700 (MST)] Received: from ariel.gi.com ([168.84.84.10]) by pa06exr01.gic.gi.com (8.11.6/8.11.6) with ESMTP id g5SEqGE31413 for ; Fri, 28 Jun 2002 09:52:16 -0500 Received: from ntas0028.gi.com ([168.84.84.98]) by GI.COM (PMDF V5.2-31 #46260) with ESMTP id <01KJGGIMSG14G792PX@GI.COM> for ipcdn@ietf.org; Fri, 28 Jun 2002 07:58:48 PDT Received: by ntas0028.gi.com with Internet Mail Service (5.5.2650.21) id ; Fri, 28 Jun 2002 07:54:14 -0400 Content-return: allowed Date: Fri, 28 Jun 2002 10:59:21 -0400 From: "Nakanishi Greg (SD-EX)" Subject: RE: [ipcdn] Membership Query Interval in Passive mode IGMP To: , IETF Ipcdn Message-id: <97DEDE66B3DCD11199D200805FA71BE206A8467D@ntas0027.gi.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="ISO-2022-JP" Sender: ipcdn-admin@ietf.org Errors-To: ipcdn-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: IP over Cable Data Network X-BeenThere: ipcdn@ietf.org Shrini, I think the scenario you mention should be a transient condition. Once the router comes up and issues a couple of MQs, the MQI will be "correct" again. greg > -----Original Message----- > From: Shrinivas Samant [mailto:ssamant@lucent.com] > Sent: Thursday, July 25, 2002 7:32 AM > To: IETF Ipcdn > Subject: [ipcdn] Membership Query Interval in Passive mode IGMP > > > Folks, > In the passive mode IGMP, the CMTS determines the Membership > Query Interval > by looking at the inter-arrival times of the Membership Query > messages. > Formally: If n<2, MQI = 125 else MQI = MAX(125, MQn - MQn-1) > where MQI is > the Membership Query Interval in seconds, n is the number of > Membership > Queries seen and MQn is the epoch time at which the nth > Membership Query was > seen. > > Now, if the Router goes down after MQn-1 and comes up again > after sometime, > MQn - MQn-1, is not an accurately determined Membership Query > Interval. > > Is there an upper limit on the value of MQI? How can we > establish the MQI in > such a scenario? > Any suggestions/comments will help. > > Thanks, > > Shrini > > > _______________________________________________ > 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