Comments and questions on March 1995 draft of Frame Relay DTE MIB
Alan Bartky <alan@xylan.com> Mon, 31 July 1995 18:13 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20385; 31 Jul 95 14:13 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa20381; 31 Jul 95 14:13 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa20019; 31 Jul 95 14:13 EDT
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id ab20229; 31 Jul 95 14:12 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id ab20219; 31 Jul 95 14:10 EDT
Received: from xylan.XYLAN.COM by CNRI.Reston.VA.US id aa19913; 31 Jul 95 14:10 EDT
Received: from omni.xylan.com by xylan.com (4.1/SMI-4.1 (xylan-mgw 1.0)) id AA02696; Mon, 31 Jul 95 11:11:01 PDT
Received: from bluejay.UUCP by omni.xylan.com (4.1/SMI-4.1 (omni 1.1)) id AA11204; Mon, 31 Jul 95 11:10:48 PDT
Received: from robin.xidc by irvine.XYLAN.COM (4.1/SMI-4.1) id AA22395; Mon, 31 Jul 95 11:01:49 PDT
Date: Mon, 31 Jul 1995 11:01:49 -0700
X-Orig-Sender: iplpdn-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Alan Bartky <alan@xylan.com>
Message-Id: <9507311801.AA22395@irvine.XYLAN.COM>
To: cbrown@baynetworks.com, charles@acc.com, fred@cisco.com
Subject: Comments and questions on March 1995 draft of Frame Relay DTE MIB
Cc: iplpdn@CNRI.Reston.VA.US, artb@xylan.com
To editors/authors of Draft Frame Relay MIB First, let me introduce myself. My name is Alan K. Bartky and I am a new engineer here at XYLAN corp. Before this I was in charge of standards at Sync Research Inc. where I was co-author of the SDLC MIB (RFC-1747), Editor of Data Link Switching (RFC-1795) and participated in the drafting the 802.2 LLC MIB and SNA Network Addressable Unit MIB. I also was technical representative to the Frame Relay Forum for Sync. We are starting on new projects here at XYLAN and need to be involved in any work regarding Frame Relay MIB work going on. First let me start by asking a few questions. What is the current status of the Frame Relay DTE MIB? Is there a draft version newer than the March 95 version (draft version 4)? Is there a group working on it? If so, how do I and/or other engineers at XYLAN subscribe to the mail exploder in order to contribute to the work in progress? Thats it for questions. Here are some comments on the March version (I apologize if there is a new version, where these comments may not apply). 1) frDlcmiState has added ccitt_933_A(5) since RFC1315. This is surely needed, but it has two problems. First the CCITT is now called the ITU-T. Also all other ITU-T values in RFC1315, just use Q9xx as a value. I would rename this to Q933_A(5). 2) frDlcmiStatus has also been added. Unfortunately it was added as {frDlcmiEntry 3}. This causes all the original RFC1315 table entries to change numbers. It was always my understanding in my working in MIB working groups that MIB objects should always be added to an end of the table to help backwards compatability with previous MIBs/implementations, and deleted objects would have to change to "obsolete" status. My recommendation would be to change this object to {frDlcmiEntry 12} and to change frDlcmiRowStatus to {frDlcmiEntry 13}. 3) There are references all over the place for "Draft" American Standard T1.617. I don`t believe this is a draft standard anymore. The MIB needs to be brought up to the times as far as indicating which references are to Draft or "Real" National or International Standards. Thats all I have for now. One thing would surely help (and should probably be added as introductory text to the next RFC) is what has changed between this MIB and RFC1315. I'll have more comments as I get more into this. Regards, Alan ********************************************************** Alan K. Bartky Email:alan@xylan.com Principal Software Engineer Voice:(714) 597-8042 XYLAN Corporation FAX: (714) 597-8342 15707 Rockfield Avenue Suite 155F Irvine CA. 92718 **********************************************************