🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: demon.ip.developers
Article #634

Re: Varied ACCM requests by Demon PPP stack

#634
From: Jim Segrave
Date: Mon, 16 Dec 1996 00:00
20 lines
1517 bytes
In article <32B58EC6.446E@optex.co.uk>,
Will Dean  <will.dean@optex.co.uk> wrote:
> I'm currently developing/debugging a TCP/IP/PPP stack (not for the PC) and I've 
> noticed that Demon equipment is inconsistent in its requests for a PPP ACCM.  
> (Both 0x000A0000 and 0xFFFFFFFF are asked for in different connections.)
> 
> Is anyone aware of the Demon policy on ACCM?  0x000A0000 seems a sensible choice,   
> but 0xFFFFFFFF would add a significant overhead (though only to transmissions 
> from the client)
> 
> I would have thought that the choice of ACCM was a matter of policy, and would 
> therefore be consistent across all equipment.  (The issue seems independent of 
> the ROMP connected to.)

I'm fairly sure the Ascends use 0x000A0000, which is a reasonable
choice. I think the old Morningstar Software/USR rack/SunOS pops
started with the ultra-conservative 0xFFFFFFFF. Have you noticed what
PoP you get the all ones from? Is it always in the range
finch-193..finch254?
Technical Details
Message-ID: <199612161822.SAA27829@jes.noc.nl.demon.net>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <32B58EC6.446E@optex.co.uk>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10bb05,3b32bf2fa9d4136b
X-Google-Attributes: gid10bb05,public
From: Jim Segrave <jes@demon.net>
Subject: Re: Varied ACCM requests by Demon PPP stack
Date: 1996/12/16
Message-ID: <199612161822.SAA27829@jes.noc.nl.demon.net>
X-Deja-AN: 204435175
x-mail2news-path: jes.noc.nl.demon.net
references: <32B58EC6.446E@optex.co.uk>
x-mail2news-user: jes@demon.net
organization: Demon Internet
reply-to: jes@demon.net
newsgroups: demon.ip.developers