A slight call to order (Re: Internic address allocation policy )

Date: Mon, 20 Mar 1995 11:21:12 -0600 (CST)

  > From: karl@mcs.com (Karl Denninger)
  > To: nanog@merit.edu

  > > > Taking a relatively small chunk of the remaining address space
  > > > (say, 210.*.*.*) gives us 64k addresses to hand out in convenient
  > >
  > > That's 16M addresses, not 64K addresses. We should not equivocate "addre
sses"
  > > and "Class C networks". 210.*.*.* has 2^24 (minus subnet zero and broadc
ast
  > > lossage) addresses -- 16M. 210.*.*.* has 2^16 "Class C networks" -- 64K.
  We
  > > must not assume that every customer will get a Class C -- many will get j
ust a
  > > subnet since they will only have a handful of hosts. I know of several
  > > providers who are chopping things up on nybble boundaries (16 hosts/net,
or
  > > actually 14 with the subnet zero and broadcast taken out).
  >
  > Not me!
  >
  > I consider a "Class B equivalent" to be 256 NETWORKS, by the common use of
  > the term, but 65K *addresses*.

1 Class-B-sized prefix = 256 Class-C-sized prefixes.
A "network" could be a Class A, B, C, etc., network, or a CIDR network,
etc.

  > Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity
  > Modem: [+1 312 248-0900] | (shell, PPP, SLIP, leased) in Chicagoland
  > Voice: [+1 312 248-8649] | 6 POPs online through Chicago, all 28.8
  > Fax: [+1 312 248-9865] | Email to "info@mcs.net" for more information
  > ISDN: Surf at Smokin' Speed | WWW: http://www.mcs.net, gopher: gopher.mcs.
net