home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!decwrl!sdd.hp.com!caen!destroyer!news.itd.umich.edu!pisa.citi.umich.edu!rees
- From: rees@pisa.citi.umich.edu (Jim Rees)
- Newsgroups: comp.protocols.ppp
- Subject: Re: asyncmap rationale (was Re: PPP via intermediate links)
- Date: 13 Nov 1992 17:02:15 GMT
- Organization: University of Michigan CITI
- Lines: 8
- Distribution: world
- Message-ID: <5c58857d.1bc5b@pisa.citi.umich.edu>
- References: <1ck9arINNjro@gap.caltech.edu> <BOB.92Nov3145722@volitans.MorningStar.Com> <BOB.92Nov13105133@volitans.MorningStar.Com>
- Reply-To: Jim.Rees@umich.edu
- NNTP-Posting-Host: pisa.citi.umich.edu
-
- In article <BOB.92Nov13105133@volitans.MorningStar.Com>, bob@MorningStar.Com (Bob Sutterfield) writes:
-
- If the initial asyncmap were 256 "1" bits, what byte range would you
- use for negotiations?
-
- Obviously, the initial negotiation should be done using nothing but 7-bit
- printing ascii characters. Certainly it shouldn't depend on being able to
- send 7f or ff transparently!
-