RE: ifType

Malis_A <MALISAB@corp.timeplex.com> Thu, 02 September 1993 19:46 UTC

Date: 02 Sep 1993 12:46:58 -0400 (EDT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Malis_A <MALISAB@corp.timeplex.com>
Subject: RE: ifType
To: Oliver Korfmacher <okorf@netcs.com>
Cc: IF-MIB WG <if-mib@thumper.bellcore.com>, IPLPDN Working Group <iplpdn@ietf.nri.reston.va.us>, PPP WG <ietf-ppp@ucdavis.edu>, SNMP <snmp@lists.psi.com>
Message-Id: <01H2H87AMU7A8WWDBA@mr.timeplex.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Ua-Content-Id: RE: ifType
A1-Type: MAIL

To  : Oliver Korfmacher
Cc  : IF-MIB WG,IPLPDN Working Group,PPP WG,SNMP
Date:  2-SEP-1993 12:46:58.00

Oliver,

>Now, keeping in mind the last discussions "IP over ISDN" 
>giving ppp or rfc1294/Q.922 framing as method of choice,
>a snmp-get can return

>       20      indicating that a plain ISDN link is used
>       22      indicating a synch. data stream over the B-channel
>       23      indicating that ppp is used
>       32      indicating that ISDN is used as access trunk to frame
>               relay networks
>or
>       1       :-)

You should read draft-ietf-ifmib-evolution-02.txt, which defines a method for 
defining a protocol stack underneath IP that was meant for solving just these 
sort of problems.  Depending on how you use the B channel, you would either 
stack 32 over 20 (or 21 if it's Primary Rate) or 23 over 20 (or 21). 

Cheers,
Andy
____________________________________________________________________________
Andrew G. Malis   malis_a@timeplex.com   -or-   malis@maelstrom.timeplex.com
Ascom Timeplex    289 Great Rd., Acton MA 01720  USA         +1 508 266-4522

ifType Jeremy Greene
Re: ifType Frank Kastenholz
Re: ifType James R. (Chuck) Davin
ifType Jeremy Greene
Re: ifType Karl Auerbach
ifType Oliver Korfmacher
RE: ifType Malis_A