From owner-Big-Internet@munnari.OZ.AU Fri Feb 11 04:20:51 1994 Received: from murtoa.cs.mu.OZ.AU by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA19991; Fri, 11 Feb 1994 04:20:51 +1100 (from owner-Big-Internet@munnari.OZ.AU) Return-Path: Received: from mailing-list by murtoa.cs.mu.OZ.AU (8.5/1.0) id EAA18615; Fri, 11 Feb 1994 04:19:44 +1100 Received: from munnari.oz.au by murtoa.cs.mu.OZ.AU (8.5/1.0) with SMTP id EAA18612; Fri, 11 Feb 1994 04:15:24 +1100 Received: from uu2.psi.com by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA19689; Fri, 11 Feb 1994 04:16:12 +1100 (from craig@aland.bbn.com) Received: from port13.sunnyvale.ca.pub-ip.psi.net by uu2.psi.com (5.65b/4.0.071791-PSI/PSINet) via SMTP; id AA19876 for big-internet@munnari.oz.au; Thu, 10 Feb 94 12:16:01 -0500 Received: from localhost by aland.bbn.com (8.6.4/3.1.090690-BBN) id JAA28450; Thu, 10 Feb 1994 09:15:17 -0800 Message-Id: <199402101715.JAA28450@aland.bbn.com> To: big-internet@munnari.OZ.AU Subject: the Make.Money.Fast note From: Craig Partridge Date: Thu, 10 Feb 94 09:15:15 -0800 Sender: craig@aland.bbn.com In the hopes of forestalling much flaming about this unfortunate posting. I just got off the phone with the folks at CMU, who are following up on this posting. At this point, they don't know even if it was Mr. Schreiner or someone who found his account logged in on some console and decided to play a prank on him. In any case, the matter is in good hands and being handled professionally. Craig PS: If you feel some need to reply to this post, kindly do so privately and spare Big-Internet. [Archiver's note: the message in question has been deleted from tghe archives, it had nothing whatever to do with B-I .. kre] From owner-Big-Internet@munnari.OZ.AU Fri Feb 11 05:40:57 1994 Received: from murtoa.cs.mu.OZ.AU by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA22429; Fri, 11 Feb 1994 05:40:57 +1100 (from owner-Big-Internet@munnari.OZ.AU) Return-Path: Received: from mailing-list by murtoa.cs.mu.OZ.AU (8.5/1.0) id FAA18698; Fri, 11 Feb 1994 05:39:46 +1100 Received: from munnari.oz.au by murtoa.cs.mu.OZ.AU (8.5/1.0) with SMTP id FAA18695; Fri, 11 Feb 1994 05:28:02 +1100 Received: from uu2.psi.com by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA22137; Fri, 11 Feb 1994 05:28:52 +1100 (from craig@aland.bbn.com) Received: from port13.sunnyvale.ca.pub-ip.psi.net by uu2.psi.com (5.65b/4.0.071791-PSI/PSINet) via SMTP; id AA27384 for big-internet@munnari.oz.au; Thu, 10 Feb 94 13:28:39 -0500 Received: from localhost by aland.bbn.com (8.6.4/3.1.090690-BBN) id KAA28687; Thu, 10 Feb 1994 10:27:24 -0800 Message-Id: <199402101827.KAA28687@aland.bbn.com> To: Craig Partridge Cc: big-internet@munnari.OZ.AU Subject: Re: the Make.Money.Fast note In-Reply-To: Your message of Thu, 10 Feb 94 09:15:15 -0800. <199402101715.JAA28450@aland.bbn.com> From: Craig Partridge Date: Thu, 10 Feb 94 10:27:23 -0800 Sender: craig@aland.bbn.com Hi folks: One last note. Apparently it was a case of someone hacking Mr. Schreiner's account and sending out the posting so he'd get grief. So, kindly spare Mr. Schreiner from the usual flames -- let's try to convince him the Internet is actually understanding to its victims... Thanks! Craig From owner-Big-Internet@munnari.OZ.AU Sun Feb 13 13:54:52 1994 Received: from murtoa.cs.mu.OZ.AU by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA14337; Sun, 13 Feb 1994 13:26:00 +1100 (from owner-Big-Internet@munnari.OZ.AU) Return-Path: Received: from mailing-list by murtoa.cs.mu.OZ.AU (8.5/1.0) id NAA01851; Sun, 13 Feb 1994 13:24:42 +1100 Received: from munnari.oz.au by murtoa.cs.mu.OZ.AU (8.5/1.0) with SMTP id NAA01837; Sun, 13 Feb 1994 13:07:55 +1100 Received: from wraith.internode.com.au by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA13820; Sun, 13 Feb 1994 13:08:30 +1100 (from simon@internode.com.au) Received: by wraith.internode.com.au (5.64+1.3.1+0.50/UA-5.23) id AA29215; Sun, 13 Feb 1994 12:35:35 +1030 From: Simon Hackett Message-Id: <9402130205.AA29215@wraith.internode.com.au> Subject: current "state of play" for the IP:ng candidates? To: big-internet@munnari.OZ.AU Date: Sun, 13 Feb 94 12:35:34 CST X-Mailer: ELM [version 2.4dev PL17] Folks, Does anyone have handy a reasonably current summary of each of the major contenders for IP:tng, and a brief idea of where the process is up to at this point? If you do, I'd love to hear from you! I'm not looking for major dissertations, just a few sentences about each contender, a few sentences about their current technical status, and a few more sentences about the current status of the overall decision making process. I suspect that this might be something useful or at least interesting to various people, so perhaps sending that summary to the list rather than just to me would be the best. I've not been able to follow the process very closely for a while... Failing that, pointers to a summary of each contender (in terms of the name of a relevant internet draft, etc) would also be very helpful. Thanks! Simon Hackett ------------------------------------------------------------------------ "Simon Hackett, Internode Systems Pty Ltd" Phone: +61 8 373 1020 Fax: +61 8 373 4911 Mail: PO Box 69, Daw Park, SA 5041 AUSTRALIA From owner-Big-Internet@munnari.OZ.AU Tue Feb 15 14:47:31 1994 Received: from murtoa.cs.mu.OZ.AU by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA14645; Tue, 15 Feb 1994 13:27:04 +1100 (from owner-Big-Internet@munnari.OZ.AU) Return-Path: Received: from mailing-list by murtoa.cs.mu.OZ.AU (8.5/1.0) id NAA04266; Tue, 15 Feb 1994 13:25:31 +1100 Received: from munnari.oz.au by murtoa.cs.mu.OZ.AU (8.5/1.0) with SMTP id NAA04252; Tue, 15 Feb 1994 13:14:45 +1100 Received: from pucc.Princeton.EDU by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA12990; Tue, 15 Feb 1994 12:46:42 +1100 (from @PUCC.PRINCETON.EDU:CAROLINE@TWNMOCTL.BITNET) Received: from PUCC.PRINCETON.EDU by pucc.Princeton.EDU (IBM VM SMTP V2R2) with BSMTP id 8787; Mon, 14 Feb 94 20:46:57 EST Received: from TWNMOCTL.BITNET (NJE origin CAROLINE@TWNMOCTL) by PUCC.PRINCETON.EDU (LMail V1.1d/1.7f) with BSMTP id 7752; Mon, 14 Feb 1994 20:46:58 -0500 Date: Tue, 8 Feb 94 11:00 +08 From: CAROLINE%TWNMOCTL.BITNET@pucc.Princeton.EDU To: big-internet@munnari.OZ.AU Message-Id: <6405DE54E51F2012BB@TWNMOCTL.BITNET> X-Envelope-To: big-internet@munnari.oz.au X-Vms-To: IN%"big-internet@munnari.oz.au" Hi, Please add me in this list. Thank you. Lily Chen Telecommunication Labs From owner-Big-Internet@munnari.OZ.AU Thu Feb 17 07:00:08 1994 Received: from murtoa.cs.mu.OZ.AU by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA09751; Thu, 17 Feb 1994 06:07:39 +1100 (from owner-Big-Internet@munnari.OZ.AU) Return-Path: Received: from mailing-list by murtoa.cs.mu.OZ.AU (8.5/1.0) id GAA06368; Thu, 17 Feb 1994 06:06:09 +1100 Received: from munnari.oz.au by murtoa.cs.mu.OZ.AU (8.5/1.0) with SMTP id FAA06360; Thu, 17 Feb 1994 05:57:25 +1100 Received: from mundamutti.cs.mu.OZ.AU by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA09241; Thu, 17 Feb 1994 05:56:56 +1100 (from kre@munnari.OZ.AU) Received: from babyoil.ftp.com by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA07573; Thu, 17 Feb 1994 05:08:56 +1100 (from solensky@tri-flow.ftp.com) Received: from tri-flow.ftp.com by babyoil.ftp.com with SMTP id AA28205; Wed, 16 Feb 94 13:09:06 -0500 Received: from solensky.fenway.ftp.com by tri-flow.ftp.com.ftp.com (5.0/SMI-SVR4) id AA01563; Wed, 16 Feb 94 13:08:35 EST Date: Wed, 16 Feb 94 13:08:35 EST Message-Id: <9402161808.AA01563@tri-flow.ftp.com.ftp.com> To: ipv4-ale@babyoil.ftp.com Subject: New growth charts From: solensky@tri-flow.ftp.com (Frank T Solensky) Cc: kre@munnari.OZ.AU, scottw@nic.ddn.mil Reply-To: ipv4-ale@ftp.com Sender: solensky@tri-flow.ftp.com Repository: slick-50.ftp.com Originating-Client: fenway.ftp.com Content-Length: 3118 Resent-To: Big-Internet@munnari.OZ.AU Resent-From: Big-Internet-Request@munnari.OZ.AU Resent-Date: Thu, 17 Feb 1994 05:56:22 +1100 Resent-Message-Id: <6027.761424982@munnari.OZ.AU> Resent-Sender: kre@munnari.OZ.AU There's a couple of new growth charts available in: research.ftp.com:pub/ale/nsf-netnumbers-9402.ps munnari.oz.au:big-internet/nsf-netnumbers-9402.ps The first one charts out the assigned and allocated Class B and Class C network numbers and are based off the IP Allocation Reports from IANA. The raw numbers are the sum of the "assigned" and "allocated" columns in that report and are intended to track the proportion of the address space which has been handed out. There's two possible problems with the data in this chart. The text at the top of the allocation report mentions that when the NIC receives information about a network number being assigned out of an allocated block, it is counted as "assigned" and subtracted from the "allocated" count.. I'm assuming that adding the 'assigned' and 'allocated' columns in the same row would show the total allocated count for that month, but I don't know for a fact that the count stays in the same row. (Scott Williamson: is this valid? If not, is there some way to get a history of the total allocated numbers?) The second issue is that it drops those networks with "unknown dates" from the totals. This includes a total of 47 Class B net numbers and 6553 Class C numbers. If these were to get lumped in at the beginning instead, it would move the curve up by a constant amount across a linearly-scaled graph, so it won't affect what these curves look like in a major way. The second graph is the NSFNet PRDB size over time. The three lines represent the size of the table with classful networks (the status quo) and rough estimates of the table sizes with campus-level and provider-level CIDRization. Full provider-level aggregation looks like that the routing tables would return to their current sizes at about the end of 1995. Again, though, these are based on _very_ rough estimates of what CIDR will accomplish: the campus-level aggregations are based on the ASCII 'organization address' strings in the PRDB and are still susceptible to "Rd."/"Road" sorts of mismatches; the provider-level aggregation is based only on the highest priority AS id in the record -- it doesn't match up the same AS ids appearing in a different order into a single mask nor does it care about policy differences. Maybe these two factors would be a wash, maybe not. Any and all suggestions on what other things may need to be taken into account would be greatly appreciated. Both of these charts use only those datapoints after the start of 1992 to form the trend lines -- this is approximately when the policy of handing out groups of Class C addresses rather than single Class Bs came into being. And, as always, neither attempt to anticipate new technology developments that might result in large blocks of numbers being consumed. Back on the first graph again, it's worth noting that while the trend of Class B numbers seems to be a pretty good fit right now, the actual Class C numbers is heavily driven by the two big jumps in the historic data. Another big jump in the future could push that trend line up closer to its upper bound. -- Frank From owner-Big-Internet@munnari.OZ.AU Wed Feb 23 12:10:15 1994 Received: from murtoa.cs.mu.OZ.AU by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA03897; Wed, 23 Feb 1994 12:10:15 +1100 (from owner-Big-Internet@munnari.OZ.AU) Return-Path: Received: from mailing-list by murtoa.cs.mu.OZ.AU (8.5/1.0) id MAA13815; Wed, 23 Feb 1994 12:08:44 +1100 Received: from munnari.oz.au by murtoa.cs.mu.OZ.AU (8.5/1.0) with SMTP id MAA13812; Wed, 23 Feb 1994 12:00:10 +1100 Received: from uu2.psi.com by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA29124; Wed, 23 Feb 1994 10:19:35 +1100 (from craig@aland.bbn.com) Received: from port13.sunnyvale.ca.pub-ip.psi.net by uu2.psi.com (5.65b/4.0.071791-PSI/PSINet) via SMTP; id AA25703 for big-internet@munnari.oz.au; Tue, 22 Feb 94 18:18:50 -0500 Received: from localhost by aland.bbn.com (8.6.4/3.1.090690-BBN) id PAA16383; Tue, 22 Feb 1994 15:17:54 -0800 Message-Id: <199402222317.PAA16383@aland.bbn.com> To: big-internet@munnari.OZ.AU Subject: 2nd Integrated Services BOF Reply-To: Craig Partridge From: Craig Partridge Date: Tue, 22 Feb 94 15:17:52 -0800 Sender: craig@aland.bbn.com Hi folks: You may have noticed that there are 2 Integrated Services BOFs on Monday afternoon. The hope is that the final agenda will show that those meetings are of the Integrated Services WG (we're awaiting IESG approval), and I've been trying to lie low until the WG charter is approved. However, I think we're getting close enough to IETF that IPng'ers should be warned that the second meeting (1600-1800 Monday) is to be devoted to discussing what requirements, if any, support for integrated services will place on IPng. The outcome will be a list of recommendations to the directorate. While this meeting may seem to be putting the cart before the horse (the WG will have barely started its work on devising an integrated services architecture), the IPng area directors have made it clear that if there are any requirements that integrated services impose, we need to give those requirements to the IPng directorate soon. Furthermore, my informal discussions with the folks who have been working on integrated services suggest that while there's still considerable diversity of opinion about many pieces of the architecture, there may be basic concensus about the kinds of information the IPng datagram headers should contain. Also, since the situation is that the failure to make a recommendation is likely as harmful as making a recommendation that is wrong, I'm planning discourage arguments like "we don't know enough yet" and rather ask folks to support their views (for or against a given recommendation) based on what we know. (I.e., statements like "well, we don't know everything, but from what we know, feature X does not appear to require support in the IPng header for these reasons...." are preferred). We'll then incorporate the weasel words (if needed) in our recommendations to the directorate. We expect to e-mail some background materials to the (proto)-WG list over the next few weeks. For those interested, the list is INT-SERV-REQUEST@ISI.EDU Thanks! Craig proposed chair, INT SERV WG PS: Oh yes, the first meeting -- that's a WG organization meeting. A chance to go over the charter, discuss how we're going to achieve our goals, and in general, plan.