Re: comments on draft-ietf-iplpdn-frmib-dte-04.txt
Caralyn Brown <cbrown@baynetworks.com> Wed, 10 May 1995 22:55 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13250; 10 May 95 18:55 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa13246; 10 May 95 18:55 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa19264; 10 May 95 18:55 EDT
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13222; 10 May 95 18:55 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa13218; 10 May 95 18:54 EDT
Received: from lobster.wellfleet.com by CNRI.Reston.VA.US id aa19220; 10 May 95 18:54 EDT
Received: from BayNetworks.com (pobox) by lobster (4.1/SMI-4.1) id AA15972; Wed, 10 May 95 18:53:33 EDT
Received: from godiva.wellfleet by BayNetworks.com (4.1/SMI-4.1) id AA28167; Wed, 10 May 95 18:58:18 EDT
Date: Wed, 10 May 1995 18:58:18 -0400
X-Orig-Sender: iplpdn-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Caralyn Brown <cbrown@baynetworks.com>
Message-Id: <9505102258.AA28167@BayNetworks.com>
Received: by godiva.wellfleet (4.1/SMI-4.1) id AA28559; Wed, 10 May 95 18:53:21 EDT
To: Fred Baker <fred@cisco.com>
Cc: John Shriver <jas@shiva.com>, cbrown@baynetworks.com, carvalho@cisco.com, iplpdn@CNRI.Reston.VA.US
Subject: Re: comments on draft-ietf-iplpdn-frmib-dte-04.txt
In-Reply-To: <v02120c12abd573106e49@[171.69.128.114]>
References: <v02120c12abd573106e49@[171.69.128.114]>
On Tue, 9 May, Fred Baker (fred@cisco.com) wrote: > At 3:20 PM 5/9/95, John Shriver wrote: > >The object: > > > > frDlcmiState OBJECT-TYPE > > SYNTAX INTEGER { > > noLmiConfigured (1), > > lmiRev1 (2), > > ansiT1_617_D (3), -- ANSI T1.617 Annex D > > ansiT1_617_B (4), -- ANSI T1.617 Annex B > > ccitt_933_A (5) -- CCITT Q933 Annex A > > } > > MAX-ACCESS read-write > > STATUS current > > DESCRIPTION > > "This variable states which Data Link Connec- > > tion Management scheme is active (and by impli- > > cation, what DLCI it uses) on the Frame Relay > > interface." > > REFERENCE > > "Draft American National Standard T1.617-1991" > > ::= { frDlcmiEntry 2 } > > > >Is missing one value, in my reckoning. ANSI T1.617a-1994 revises > >Annex D in an incompatible way. (Thanks, ANSI! The "element > >identifier" of "Link integrity verification information element" is > >changed from 0x19 to 0x03.) > > What idiot did that? Did they do anything useful with the protocol (tell > you the Bc/Be/throughput values, perhaps) that would justify implementing > it? > > >I'd say it should be revised to: > > > > frDlcmiState OBJECT-TYPE > > SYNTAX INTEGER { > > noLmiConfigured (1), > > lmiRev1 (2), -- Interim LMI Revision 1 > > ansiT1_617_D (3), -- ANSI T1.617-1991 Annex D > > ansiT1_617_B (4), -- ANSI T1.617-1991 Annex B > > ccitt_933_A (5), -- CCITT Q933 Annex A > > ansiT1_617_1994_D (6) -- ANSI T1.617a-1994 Annex D > > } > > MAX-ACCESS read-write > > STATUS current > > DESCRIPTION > > "This variable states which Data Link Connec- > > tion Management scheme is active (and by impli- > > cation, what DLCI it uses) on the Frame Relay > > interface." > > REFERENCE > > "American National Standard T1.617-1991. > > American National Standard T1.617a-1994. > > ITU-T Recommendation Q.933 (03/93)." > > > >(Note also that many of the ANSI standard references are outdated.) > > Caralyn, Charles, your opinions? Anyone else? > Looks like I fell a little behind on my email. Sorry. Anyway, I think I agree that if ansi changed their coding, we probably need to address it in the mib. Let's add the new type as suggested. I assume it's not too late with the latest revision still pending. c -- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Caralyn Brown Voice: 508-436-3835 Bay Networks Internet: cbrown@wellfleet.com 2 Federal Street Billerica, MA 01821 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
- comments on draft-ietf-iplpdn-frmib-dte-04.txt John Shriver
- Re: comments on draft-ietf-iplpdn-frmib-dte-04.txt Fred Baker
- Re: comments on draft-ietf-iplpdn-frmib-dte-04.txt John Shriver
- Re: comments on draft-ietf-iplpdn-frmib-dte-04.txt Rick Cornetti
- Re: comments on draft-ietf-iplpdn-frmib-dte-04.txt Caralyn Brown
- Re: comments on draft-ietf-iplpdn-frmib-dte-04.txt Fred Baker