Re: Proposed changes to Draft Frame Relay MIB for multiprotocol support.

"Andrew G. Malis" <malis@nexen.com> Thu, 04 January 1996 12:47 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10001; 4 Jan 96 7:47 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09997; 4 Jan 96 7:47 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa05616; 4 Jan 96 7:47 EST
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09989; 4 Jan 96 7:47 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09985; 4 Jan 96 7:46 EST
Received: from guelah.nexen.com by CNRI.Reston.VA.US id aa05598; 4 Jan 96 7:46 EST
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id HAA00786; Thu, 4 Jan 1996 07:25:26 -0500
Received: from phish.nexen.com (phish.nexen.com [204.249.99.14]) by maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id HAA04577; Thu, 4 Jan 1996 07:40:48 -0500
Received: from [204.249.97.32] (malis.nexen.com [204.249.97.32]) by phish.nexen.com (8.6.12/8.6.12) with SMTP id HAA06963; Thu, 4 Jan 1996 07:46:11 -0500
X-Sender: malis@pop.nexen.com
Message-Id: <v02140404ad117a71319d@[204.249.97.32]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 4 Jan 1996 07:46:48 -0500
To: Alan Bartky <alan@xylan.com>
X-Orig-Sender: iplpdn-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Andrew G. Malis" <malis@nexen.com>
Subject: Re: Proposed changes to Draft Frame Relay MIB for multiprotocol support.
Cc: iplpdn@CNRI.Reston.VA.US, alan@xylan.com

Alan,

>Proposed change:
>
>
>     ifInUnknownProtos  Number of unknown or unsupported
>                        upper layer protocol frames received
>                        and discarded.  If only a single
>                        upper layer protocol is present
>                        (i.e. multiprotocol formatting is
>                        not used) then this counter
>                        would be always zero(0).

I like this change.

>Second for the more difficult one.
>...
>Table Entry 1: ifIndex.10, DLCI 40
>Table Entry 2: ifIndex.10, DLCI 41
>Table Entry 3: ifIndex.11, DLCI 40
>Table Entry 4: ifIndex.11, DLCI 41
>Table Entry 5: ifIndex.12, DLCI 41
>Table Entry 6: ifIndex.12, DLCI 42

Sounds like in this case, you're not modeling the FR interface as a
multiaccess interface, but as a collection of virtual point-point
interfaces, one for each DLC.  If you then give each virtual interface
(DLC) its own ifIndex, you can do the mapping in the ifStack table, right?

>P.S. If we decide to add either of these changes we should
>have a references to RFC 1490, FRF.3.1 and T1.617 Annex G
>at the end of the document.

Absolutely.

Andy

__________________________________________________________________________
Andrew G. Malis   Ascom Nexion                      voice: +1 508 266-4522
malis@nexen.com   289 Great Rd., Acton MA 01720 USA   FAX: +1 508 266-2300