From mailman-owner@ietf.org  Wed Oct 24 15:01:32 2001
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 PAA11664
	for <ipcdn-archive@odin.ietf.org>; Wed, 24 Oct 2001 15:01:32 -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 OAA09899
	for <ipcdn-archive@lists.ietf.org>; Wed, 24 Oct 2001 14:59:47 -0400 (EDT)
Date: Wed, 24 Oct 2001 14:59:47 -0400 (EDT)
Message-Id: <200110241859.OAA09899@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 <sip.ietf.org>

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      
http://www1.ietf.org/mailman/options/ipcdn/ipcdn-archive@lists.ietf.org


From ipcdn-admin@ietf.org  Mon Oct 29 16:53:59 2001
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 QAA28399;
	Mon, 29 Oct 2001 16:53:55 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA02070;
	Mon, 29 Oct 2001 16:50:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA02046
	for <ipcdn@optimus.ietf.org>; Mon, 29 Oct 2001 16:50:25 -0500 (EST)
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28193
	for <ipcdn@ietf.org>; Mon, 29 Oct 2001 16:50:19 -0500 (EST)
Received: from rwoundy-w2k.cisco.com (dhcp-161-44-149-122.cisco.com [161.44.149.122]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id QAA21673 for <ipcdn@ietf.org>; Mon, 29 Oct 2001 16:49:53 -0500 (EST)
Message-Id: <4.3.2.7.2.20011029162250.0199c3f8@funnel.cisco.com>
X-Sender: rwoundy@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 29 Oct 2001 16:51:48 -0500
To: ipcdn@ietf.org
From: Rich Woundy <rwoundy@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [ipcdn] Adopting the latest Interfaces Group MIB (RFC 2863) for the
 DOCSIS RF MIB
Sender: ipcdn-admin@ietf.org
Errors-To: ipcdn-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
X-BeenThere: ipcdn@ietf.org

Folks,

I believe that we should adopt the latest version of the Interfaces Group 
MIB, RFC 2863, for the next version of the DOCSIS RF MIB.

Below are the changes between RFC 2233 and RFC 2863, as identified in 
section 11 of RFC 2863, with some discussion on impact to implementations.

* Added linkUpDownNotificationsGroup.

This is the NOTIFICATION-GROUP for linkUp and linkDown, which were 
notifications already defined in RFC 2233.

* Changed the status of the definition of OwnerString in this MIB to be 
deprecated, because it is only used by ifTestOwner, which is now 
deprecated, and because other MIBs should import OwnerString from RFC 1757 
or its successors.

This appears to be a harmless change.

* Added ifCompliance3 as a replacement for ifCompliance2 to omit the 
ifStackGroup2 group, and add linkUpDownNotificationsGroup.  Also, corrected 
the omission of ifVHCPacketGroup, and typos in the DESCRIPTIONs of 
ifHCPacketGroup and ifFixedLengthGroup.  Obsoleted ifCompliance2.

This appears to be a harmless change.

* Modified syntax of ifStackHigherLayer and ifStackLowerLayer to be 
InterfaceIndexOrZero.

This appears to be a harmless change.

* Added requirement that media-specific MIB designers specify any special 
conditions concerning the counting of framing characters in ifInOctets and 
ifOutOctets.

This seems to refer to the following text on page 25 of RFC 2863:

    ifXxxOctets
       The definitions of ifInOctets and ifOutOctets (and similarly,
       ifHCInOctets and ifHCOutOctets) specify that their values include
       framing characters.  The media-specific MIB designer MUST specify
       any special conditions of the media concerning the inclusion of
       framing characters, especially with respect to frames with errors.

Is this a concern?

* Corrected a typo in the DESCRIPTION of the linkUp notification.

This is an obvious fix.

* Modified the introductory SNMP Network Management Framework boilerplate text.

This is a harmless change.

-- Rich


_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
http://www1.ietf.org/mailman/listinfo/ipcdn


From daemon@optimus.ietf.org  Mon Oct 29 16:54:04 2001
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 QAA28407
	for <ipcdn-archive@odin.ietf.org>; Mon, 29 Oct 2001 16:54:00 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA02181
	for ipcdn-archive@odin.ietf.org; Mon, 29 Oct 2001 16:54:05 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA02070;
	Mon, 29 Oct 2001 16:50:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA02046
	for <ipcdn@optimus.ietf.org>; Mon, 29 Oct 2001 16:50:25 -0500 (EST)
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28193
	for <ipcdn@ietf.org>; Mon, 29 Oct 2001 16:50:19 -0500 (EST)
Received: from rwoundy-w2k.cisco.com (dhcp-161-44-149-122.cisco.com [161.44.149.122]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id QAA21673 for <ipcdn@ietf.org>; Mon, 29 Oct 2001 16:49:53 -0500 (EST)
Message-Id: <4.3.2.7.2.20011029162250.0199c3f8@funnel.cisco.com>
X-Sender: rwoundy@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 29 Oct 2001 16:51:48 -0500
To: ipcdn@ietf.org
From: Rich Woundy <rwoundy@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [ipcdn] Adopting the latest Interfaces Group MIB (RFC 2863) for the
 DOCSIS RF MIB
Sender: ipcdn-admin@ietf.org
Errors-To: ipcdn-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
X-BeenThere: ipcdn@ietf.org

Folks,

I believe that we should adopt the latest version of the Interfaces Group 
MIB, RFC 2863, for the next version of the DOCSIS RF MIB.

Below are the changes between RFC 2233 and RFC 2863, as identified in 
section 11 of RFC 2863, with some discussion on impact to implementations.

* Added linkUpDownNotificationsGroup.

This is the NOTIFICATION-GROUP for linkUp and linkDown, which were 
notifications already defined in RFC 2233.

* Changed the status of the definition of OwnerString in this MIB to be 
deprecated, because it is only used by ifTestOwner, which is now 
deprecated, and because other MIBs should import OwnerString from RFC 1757 
or its successors.

This appears to be a harmless change.

* Added ifCompliance3 as a replacement for ifCompliance2 to omit the 
ifStackGroup2 group, and add linkUpDownNotificationsGroup.  Also, corrected 
the omission of ifVHCPacketGroup, and typos in the DESCRIPTIONs of 
ifHCPacketGroup and ifFixedLengthGroup.  Obsoleted ifCompliance2.

This appears to be a harmless change.

* Modified syntax of ifStackHigherLayer and ifStackLowerLayer to be 
InterfaceIndexOrZero.

This appears to be a harmless change.

* Added requirement that media-specific MIB designers specify any special 
conditions concerning the counting of framing characters in ifInOctets and 
ifOutOctets.

This seems to refer to the following text on page 25 of RFC 2863:

    ifXxxOctets
       The definitions of ifInOctets and ifOutOctets (and similarly,
       ifHCInOctets and ifHCOutOctets) specify that their values include
       framing characters.  The media-specific MIB designer MUST specify
       any special conditions of the media concerning the inclusion of
       framing characters, especially with respect to frames with errors.

Is this a concern?

* Corrected a typo in the DESCRIPTION of the linkUp notification.

This is an obvious fix.

* Modified the introductory SNMP Network Management Framework boilerplate text.

This is a harmless change.

-- Rich


_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
http://www1.ietf.org/mailman/listinfo/ipcdn



