Class B vs. lots of class C's
Vikas Aggarwal <aggarwal@r2d2.jvnc.net> Mon, 08 February 1993 23:49 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20185; 8 Feb 93 18:49 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa20181; 8 Feb 93 18:49 EST
Received: from merit.edu by CNRI.Reston.VA.US id aa26240; 8 Feb 93 18:50 EST
Return-Path: <aggarwal@r2d2.jvnc.net>
Received: from r2d2.jvnc.net by merit.edu (5.65/1123-1.0) id AA02395; Mon, 8 Feb 93 18:44:06 -0500
Received: by r2d2.jvnc.net (5.65/1.34) id AA04571; Mon, 8 Feb 93 18:44:05 -0500
Date: Mon, 08 Feb 1993 18:44:05 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Vikas Aggarwal <aggarwal@r2d2.jvnc.net>
Message-Id: <9302082344.AA04571@r2d2.jvnc.net>
To: njm@merit.edu
Subject: Class B vs. lots of class C's
I remember this discussion a while ago, but don't remember the outcome... A site here has to make a decision between 3 class B's or 50 class C network addresses. Which shall the site apply for ? (routing table size vs. lack of class B's). -vikas (609) 258-2403 vikas@jvnc.net ...rutgers!jvncnet!vikas --------------------------------------------------------------------------
- Class B vs. lots of class C's Vikas Aggarwal
- Re: Class B vs. lots of class C's Dan Long
- Re: Class B vs. lots of class C's epg
- Re: Class B vs. lots of class C's William Manning
- Re: Class B vs. lots of class C's William Manning