| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: Problem Connects |
> EH> 2. With your array of commands, can you select a LAP-M connection with > EH> MNP5 compression - if not, for what reason? > MNP5 is MNP4 with dumb compression. MNP5's not divisable so > as to provide a seperate compression only method Which part of V.42 allows MNP5 to be disabled above LAP-M connections? By your own reckoning, the error control and data compression mechanisms are independently selectable and inter-compatible. > EH> Curiously of course, V.42 recommendation does not *imply* any support > EH> for compression, > V42bis was accepted as the primary means of data compression > in January 1990 by the then CCITT Did you mis-read my original sentence? V.42 recommendation does not imply *any* support for compression. If compression is implemented then it *may* be negotiated using V.42. V.42bis is a data compression protocol, but its implementation is not a requirement of (and it isn't *implied* by) V.42. It is simply one of the protocols which V.42 can negotiate, if it (V.42bis) is implemented. Edward ---* Origin: inForme // 01606-836633 (2:250/701) SEEN-BY: 50/99 115/500 623/630 625/100 635/503 544 711/410 413 430 808 809 SEEN-BY: 711/932 934 712/515 713/888 714/906 771/1120 800/1 @PATH: 250/701 102 440/1 442/403 255/1 250/107 254/153 106/2000 396/1 @PATH: 3615/50 115/2 25 500 50/99 711/808 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.