Xref: utzoo comp.protocols.iso:1638 comp.dcom.modems:9077
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!pacbell.com!att!ucbvax!okeeffe.Berkeley.EDU!sklower
From: sklower@okeeffe.Berkeley.EDU (Keith Sklower)
Newsgroups: comp.protocols.iso,comp.dcom.modems
Subject: Re: Status of HDLC Standard (1/12/90)
Message-ID: <41576@ucbvax.BERKELEY.EDU>
Date: 3 Apr 91 20:28:27 GMT
References: <mskuhn.670597503@faui09> <JH.91Apr3185415@etana.funet.fi>
Sender: nobody@ucbvax.BERKELEY.EDU
Reply-To: sklower@okeeffe.Berkeley.EDU.UUCP (Keith Sklower)
Distribution: comp
Organization: CSRG, UC Berkeley
Lines: 16

In article <JH.91Apr3185415@etana.funet.fi> jh@funet.fi (Juha Heinanen) writes:
}While we are at HDLC, does anyone know when US GOSIP is going to
}define a reasonable variant of HDLC to be used to run CLNP over
}point-to-point links? ... running multiple protocols, some of which are
}non-OSI, is not possible using the current specification.
}--	Juha Heinanen, FUNET, Finland, jh@funet.fi, +358 49 500958

I think you should examine the internet PPP spec.  It uses HDLC framing,
but with different ``addresses'', and could be compatible with standard
LAP_B for an implementation that understood both.  There are hooks left
for running CLNP and XNS traffic, although only the IP details are
completely nailed down.
  Keith Sklower				Computer Science Dept.
  sklower@okeeffe.Berkeley.EDU		570 Evans Hall		
  (415) 642-9587			University of California
  H: (415) 863-0990			Berkeley, CA  94720