- Test - lists.nanog.org

Re: NSP ... New Information
by Larry Vaden 09 Jun '97

09 Jun '97

At 01:55 PM 6/9/97 -0500, Jeremy Porter wrote: > >In message <3.0.1.32.19970608231642.00d49e1c(a)texoma.net>, Larry Vaden writes: >>At 10:54 PM 6/8/97 -0500, Jeremy Porter wrote: >>>This means that you should use renumbering technology as much as >>>possible, so that when you can justify a /19 you can get one, >>>until then, find an ISP that is multi-homes and can provide you >>>the IP addresses you need, and consider two connections to them, >>>giving you the benefit of being multi-homed without the cost of >>>the routers needed for full BGP, or needing to justify a /19. >> >>A quick question: >> >>What is the immediate utilization rate required for an ISP's first /19? >> >>Please provide a basis in RFC2050 et al relevant documents for your answer. > >The /19 is required to be utilized in 6 months, as part of slow start. >(Under Internic guidelines, under ARIN this could be changed.) >Check out www.arin.net, www.ripe.net, and www.apnic.net for the >indivdual registries polices. > >--- >Jeremy Porter, Freeside Communications, Inc. jerry(a)fc.net >PO BOX 80315 Austin, Tx 78708 | 1-800-968-8750 | 512-458-9810 >http://www.fc.net Jeremy, that's the way I read it also, but Kim Hubbard of InterNIC says an ISP applying for their first /19 must show 100% immediate utilization of a /19 to obtain one from InterNIC. I don't see the part of RFC2050 which supports Kim's interpretation, especially for a currently multi-homed ISP. Do you or others? Dr. Jon Postel has also been silent in regard to pointing out the authority for the 100% immediate utilization rate. Thanks, Larry Vaden, founder and CEO help-desk 903-813-4500 Internet Texoma, Inc. <http://www.texoma.net> direct 903-870-0365 bringing the real Internet to rural Texomaland fax 903-868-8551 Member ISP/C, TISPA and USIPA pager 903-867-6571

2 1

Re: NSP ... New Information
by Larry Vaden 09 Jun '97

09 Jun '97

At 11:39 AM 6/9/97 PDT, Yakov Rekhter wrote: >Larry, > >> Are you saying that a /19 wouldn't put less load on the _system_ than the >> current situation + another block? >> >> Our /23 and /21 are from UUNET, our primary provider. ACSI is secondary >> provider. >> >> Teach me (read: offer your constructive criticism). I'm willing to learn. >> > >Load on the routing system could be reduced if you would take a block >of addresses from UUNET, and a block of addresses from ACSI, number >some of your customers out of the UUNET block, some of your customers >out of the ACSI block, and then use something along the lines of "auto >injection" (see draft-bates-multihoming-00.txt) to handle fallback >connectivity. > >Yakov. Yakov, Thanks for the constructive input. I'll try to locate the full URL and we're interested in evaluating and following your suggestion. Will this meet the InterNIC guidelines of "no favored connection"? Regards, Larry Vaden, founder and CEO help-desk 903-813-4500 Internet Texoma, Inc. <http://www.texoma.net> direct 903-870-0365 bringing the real Internet to rural Texomaland fax 903-868-8551 Member ISP/C, TISPA and USIPA pager 903-867-6571

1 0

RE: the original thirteen NSFNET regionals
by Tony Hain 09 Jun '97

09 Jun '97

Actually to complete the story, MFEnet preceded HEPnet & SPAN as DEC was still developing the DECnet protocol at the time. When Sid put together the proposal for SDSC, it was a clone of the operating and successful MFE Computer Center (down to the floor plans of the building). The CTSS operating system for the Cray at that time included the MFEnet protocol. In that same time frame the MFEnet itself was running out of address space and worked through a transition to TCP by running MFEnet over IP. ---------- From: Hans-Werner Braun [SMTP:hwb@rwac.ucsd.edu] Sent: Monday, June 09, 1997 10:19 AM To: Kent W. England Cc: nanog(a)merit.edu Subject: Re: the original thirteen NSFNET regionals > It's also worth noting that DECNET was a leading contender for the NSFNET. > Sid Karin, director of SDSC, tells the story that he was leaning toward > DECNET until he met a taciturn Teutonic network engineer from Ann Arbor who > convinced Sid among others that a TCP/IP backbone would work. You actually do not quite have your story right. Sid used MFENET (Magnetic Fusion Energy) protocols for the SDSCnet (SDSC consortium) satellite network initially. I was also the networking person at the University of Michigan responsible for the UMichigan-SDSCnet connection (with MFENET protocols) at that time (besides other responsibilities). It did work, and SDSC continued to use it despite the NSFNET using IP. Over time SDSC phased MFENET out and IP in, but besides the reponsibility of the taciturn Teutonic network engineer from Ann Arbor for the NSFNET, I don't think he had much to do with the phaseout of the MFENET usage at SDSC. Sid still claims that he is proud of both his MFENET decision as well as the decision to phase it out, as time moved on.

1 0

re: the original thirteen NSFNET regionals
by Rob Gutierrez 09 Jun '97

09 Jun '97

> >Does anyone remember the NSF-sponsored regional networks? Can you fix > >this table--this is off the top of my head so I am missing a few networks. Does NSI (NASA Science Internet) qualify as one of those? Yeah, it was 1989 when it started (Hi Milo!), but ... :) > Name Region NOC was or is at Now > > BARRnet Bay Area Stanford? Berkeley? BBN WR > ^SU then E. Bayshore Rd., Palo Alto The "NOC" (cough) was in Pine Hall at Stanford next to long-timer Ron Roberts office. After the BBN buyout, NOC duties were officially given to BBN Cambridge, somewhat bypassing the E. Bayshore/Palo Alto NOC office. The western region NOC was supposed to open up (under the capable hands of Chris Tsuboi, now with @Home), but time factors never gave Chris the chance before his departure from BBN-WR. All calls went to Cambridge and were referred to Chris as needed. The NOC office is/was still there as a showcase to visitors in the large conference room. And ... > Network Contact in 1990, where are they now? > > BARRNET Paul Baer > > NEARNET John Rugo Paul Baer was part of the original BARRNet admin staff when William "Bill" Yundt got the ball rolling. Paul came over to BBN after the buyout on a consultant basis, but I don't know if he has stayed on at this present day. Bill Yundt also came over to the BBN side, then went onward with Web TV Networks. John Rugo was running NEARNet when he was asked to run BARRNet after the buyout. After a 2-3 year stint in that position, he went on to be on the senior management team at Cisco in their then new ISP group. The only people left from the original BARRNet at BBN-WR is Vince Fuller and Bill Yundt's admin, Nora Lundin. rob.

9 9

Loss of BGP peering monitoring via SNMP
by Curtis Generous 09 Jun '97

09 Jun '97

We have been caught several times lately with some of our border routers loss of BGP peering going undetected for sometime. Is there a way to enable BGP peering loss monitoring via SNMP from a CISCO router? I've looked at both the public and private MIBS but haven't found anything. I am aware of the 'nocol' package but really was hoping for an SNMP based approach to tie into our net-mgmt packages (sunnet and hpov). TIA --curtis -- Curtis Generous generous(a)uucom.com Phone: (703) 461-1350 UUcom Inc., Suite 250, 4875 Eisenhower Avenue, Alexandria, VA 22304-0797

3 2

Re: Information re: Cyberpromo
by Mark E Larson 09 Jun '97

09 Jun '97

Hmmmm. Let's see. Shutoff peering with AGIS. Tell all their customers to leave. Hoping for some business :) At 11:30 PM 6/2/97 -0700, you wrote: > >AGIS has some 175 or so reseller customers, some of whom are largeish. >A number of those are dual-homed or peer with "nearly everyone" at >one or more exchange points, though. In the last few weeks, I've seen >over 10 midsized ISPs announce they were leaving AGIS, many more are talking >about doing so. Both because of ongoing spam support and their low >quality of service (some inherent, some apparently people attacking >Cyberpromo and/or AGIS after being spammed, unfortunately) I now >recommend to all the ISPs I do or have consulted with that are >AGIS customers that they leave. > >I've never actually seen a large network kill itself before. >It looks like they've got circa 6 months to live at this rate. >This is an interesting process... > >-george william herbert >gherbert(a)crl.com >Disclaimer: I speak for nobody, not even my cats. > > Mark E Larson Chief Engineer Senior Network Architect RUSTnet Inc. ----------------------------------------------- R U S T N E T I N C. A member of the Verio Group http://www.rust.net -----------------------------------------------

1 0

Re: NSP ... New Information
by Bill Sommerfeld 09 Jun '97

09 Jun '97

Date: Mon, 9 Jun 1997 00:34:03 -0400 (EDT) From: Edward Fang <edfang(a)visi.net> This is all great and dandy, but then why does it appear that anybody with a cable modem this side of the sun are using static IP's. Huh? When I switched from dialup ISDN to cable-modem service (MediaOne) I went from a static address to a DHCP address. I've been forcably renumbered at least once since then due to a topology change.

1 0

Re: Top 100 Nameservers (Serving the most Domains)
by Havard.Eidnes＠runit.sintef.no 09 Jun '97

09 Jun '97

Hi, nice report! It's not entirely clear what your data source is; I guess it's the zone files for the domains currently under InterNIC's administration, yes? To prevent anyone from taking this report and relabel it as "The Internet's top 100 name servers (by domains served)" (even in their own minds...), I just want to point out that there exists other TLDs on the Internet than those maintained by the InterNIC, and I know for a fact that some name servers in other areas would be included in your list if you had analyzed the data. Regards, - Håvard

3 2

Notes from June 1997
by sob＠academ.com 09 Jun '97

09 Jun '97

The full agenda page is up and some of the presentations (the InterNIC and ARIN updates as well as the Welcome and Closing) are now available. More to come.

1 0

Top 100 Nameservers (Serving the most Domains)
by Rusty H. Hodge 09 Jun '97

09 Jun '97

>From the June 7th Zone Files - Domains served by each nameserver... the Top 100: 1. 23799 NS2.NAMESERVERS.NET 2. 23232 NS.NAMESERVERS.NET 3. 22137 NSX.NTX.NET 4. 21897 NSB.NTX.NET 5. 15053 NS2.FREEVIEW.COM 6. 15053 NS1.FREEVIEW.COM 7. 14953 NS2.BEST.COM 8. 13751 NS.GEN.COM 9. 13545 NS3.BEST.COM 10. 12812 NIC.GEN.COM 11. 12317 NS2.MCI.NET 12. 12293 NS1.SECURE.NET 13. 12241 NS2.SECURE.NET 14. 11055 NS.MCI.NET 15. 10385 NS.BEST.COM 16. 9969 NS3.MAILBANK.COM 17. 9969 NS4.MAILBANK.COM 18. 9965 NS1.NOC.NETCOM.NET 19. 9900 PRI2.DNS.PSI.NET 20. 9880 PRI1.DNS.PSI.NET 21. 9520 PRI3.DNS.PSI.NET 22. 9504 NS.DIGEX.NET 23. 9478 NS2.NETCOMI.COM 24. 8998 ZORK.TIAC.NET 25. 8832 SUNDOG.TIAC.NET 26. 7680 NIC.NEAR.NET 27. 7646 NS1.SPRINTLINK.NET 28. 7003 DAFFY.CADVISION.COM 29. 6883 HUEY.CADVISION.COM 30. 6844 NS1.PBI.NET 31. 6551 NS1.NETCOMI.COM 32. 6540 NS2.NOC.NETCOM.NET 33. 6525 DNS2.PRIMEHOST.COM 34. 6404 DNS1.PRIMEHOST.COM 35. 6179 NS1.BEST.COM 36. 6119 HEARSAY.MSPRING.NET 37. 6109 NS1.EARTHLINK.NET 38. 6082 NS3.EARTHLINK.NET 39. 6071 SPEAKEASY.MSPRING.NET 40. 5935 NS2.EARTHLINK.NET 41. 5900 NS4.EARTHLINK.NET 42. 5799 KNOCK.SER.BBNPLANET.NET 43. 5575 NS.DIGIWEB.COM 44. 5365 NS0.NS0.COM 45. 5257 NS2.DIGEX.NET 46. 4690 AUTH02.NS.UU.NET 47. 4649 NS2.DIGIWEB.COM 48. 4600 AUTH03.NS.UU.NET 49. 4597 NS.CLEVER.NET 50. 4582 NS2.PSI.NET 51. 4551 NS2.CLEVER.NET 52. 4512 NS1.WEBCREATIONS.COM 53. 4468 NS2.WEBCREATIONS.COM 54. 4348 NS1.WESTNET.NET 55. 4320 AUTH51.NS.UU.NET 56. 3965 GRAPEVINE.MSPRING.NET 57. 3948 GOSSIP.MSPRING.NET 58. 3942 NS.PSI.NET 59. 3925 NS2.REQUEST.NET 60. 3905 NS1.REQUEST.NET 61. 3890 NS0.DEMON.CO.UK 62. 3882 NIC3.BARRNET.NET 63. 3861 NS2.WEBCOM.COM 64. 3843 NS.IDT.NET 65. 3838 NS.WEBCOM.COM 66. 3827 NS4.EROLS.COM 67. 3794 NS3.EROLS.COM 68. 3675 NS1.OTTAWA.ISTAR.NET 69. 3659 NS2.VALUEWEB.NET 70. 3620 NS.VALUEWEB.NET 71. 3535 NS2.SPRINTLINK.NET 72. 3295 NS1.SOFTAWARE.COM 73. 3241 NS2.ANAWAVE.COM 74. 3225 NS1.ANAWAVE.COM 75. 3184 NS3.ANAWAVE.COM 76. 3150 NS.MR.NET 77. 3073 AUTH00.NS.UU.NET 78. 3053 NS3.NAMESERVERS.NET 79. 3000 WW2.COVESOFT.COM 80. 2923 NS3.NETCOMI.COM 81. 2916 NOC.CERF.NET 82. 2910 NS-1.CSN.NET 83. 2848 NS.UU.NET 84. 2835 DNS1.PRIMENET.NET 85. 2819 NS3.DIGIWEB.COM 86. 2758 NS2.NEWACCOUNT.COM 87. 2754 NS.NEWACCOUNT.COM 88. 2729 NWNEXUS.WA.COM 89. 2675 NS0.PIPEX.NET 90. 2661 DNS2.PRIMENET.NET 91. 2632 NS1.DEMON.CO.UK 92. 2632 NS2.DEMON.NET 93. 2600 NS3.SPRINTLINK.NET 94. 2580 DNS3.PRIMENET.NET 95. 2515 NIC1.INTERNEX.NET 96. 2503 WHITE.555-1212.COM 97. 2468 NS2.WEBSERVICES.NET 98. 2458 AUTH50.NS.UU.NET 99. 2414 DNS2.SIMPLENET.COM 100. 2410 NS1.NEW-YORK.NET 101. 2403 DNS1.SIMPLENET.COM 102. 2396 NS1.WEBSERVICES.NET 103. 2387 NS2.NEW-YORK.NET 104. 2355 NS0.BT.NET 105. 2348 NS1.HK.LINKAGE.NET 106. 2335 NS1.BARRNET.NET 107. 2280 NORTHSHORE.ECOSOFT.COM 108. 2262 NS2.AITCOM.NET 109. 2258 NWFOCUS.WA.COM 110. 2248 NS1.AITCOM.NET 111. 2203 NS2.HOMECOM.COM 112. 2201 NS2.HK.LINKAGE.NET 113. 2198 FOYER.HOMECOM.COM 114. 2196 NS1.INDIRECT.COM 115. 2171 NS.SCCSI.COM 116. 2143 NS2.INDIRECT.COM 117. 2137 NIC2.INTERNEX.NET 118. 2126 NS2.WEB2010.COM 119. 2107 AUTH2.NS.IDT.NET 120. 2105 NS3.NEW-YORK.NET 121. 2103 NS.WEB2010.COM 122. 2052 ARTEMIS.IBERNET.ES 123. 2039 BOLERO.RAHUL.NET 124. 2026 NS2.PROPAGATION.COM 125. 2017 SEC1.DNS.PSI.NET 126. 2015 NS.PROPAGATION.COM 127. 2015 NS2.SOFTAWARE.COM 128. 1985 NS.ONRAMP.NET 129. 1972 UUCP-GW-1.PA.DEC.COM 130. 1946 DNS1.UTELFLA.COM 131. 1925 MACU.MA.MT.NP.ELS-GMS.ATT.NET 132. 1921 NS1.PIPEX.NET 133. 1893 OHCU.OH.MT.NP.ELS-GMS.ATT.NET 134. 1881 NS1.ACCESSONE.COM 135. 1875 ORCU.OR.BR.NP.ELS-GMS.ATT.NET 136. 1869 NBN.NBN.COM 137. 1856 MNC.555-1212.COM 138. 1853 WYCU.WY.BR.NP.ELS-GMS.ATT.NET 139. 1843 AUTH01.NS.UU.NET 140. 1840 NS1.ROCKYMTN.NET 141. 1817 HUSTLE.RAHUL.NET 142. 1808 NS2.ROCKYMTN.NET 143. 1790 NS1.WCO.COM 144. 1765 NS3.SOFTAWARE.COM 145. 1752 NS1.AZLAN.NET 146. 1744 NS2.NW.COM 147. 1742 NOC.NEAR.NET 148. 1740 NS1.NW.COM 149. 1725 NS1.GLOBECOMM.NET 150. 1723 NS2.ONRAMP.NET 151. 1723 NS1.AIMNET.COM 152. 1720 NS2.GLOBECOMM.NET 153. 1701 NS2.WCO.COM 154. 1698 SPRUCE.CIC.NET 155. 1686 UUCP-GW-2.PA.DEC.COM 156. 1680 NS.HOLONET.NET 157. 1678 NS2.ADGRAFIX.COM 158. 1675 NS.CAIS.COM 159. 1666 NS3.ADGRAFIX.COM 160. 1661 NS1.ADGRAFIX.COM 161. 1654 HOMER.ALPHA.NET 162. 1647 NS2.ISC-BR.COM 163. 1646 ACE.GI.NET 164. 1643 NIS.ANS.NET 165. 1638 NS1.NAMESERVE.NET 166. 1636 NS2.NAMESERVE.NET 167. 1633 NS2.HOLONET.NET 168. 1632 WIZARD.PN.COM 169. 1627 NS2.MA.ULTRA.NET 170. 1626 SPARKYJR.SHORE.NET 171. 1623 NS1.MA.ULTRA.NET 172. 1621 NS1.BELLGLOBAL.COM 173. 1603 NS1.OAR.NET 174. 1603 NS2.ACCESSONE.COM 175. 1601 NS3.HOLONET.NET 176. 1596 NS4.SOFTAWARE.COM 177. 1575 NS1.IQUEST.NET 178. 1573 NS.ANS.NET 179. 1565 NS2.AIMNET.COM 180. 1549 DNS3.EE.NET 181. 1547 PHOENIX.AZC.COM 182. 1538 NS1.DELTANET.COM 183. 1535 NS1.AZC.COM 184. 1527 NS.IPRESENT.COM 185. 1507 NS2.AZLAN.NET 186. 1507 NS.UUNET.CA 187. 1505 NS2.FLASH.NET 188. 1499 NS1.FLASH.NET 189. 1492 DNS2.EE.NET 190. 1490 NS.STRUCTURED.NET 191. 1480 AUTH60.NS.UU.NET 192. 1477 NS2.SIRIUS.COM 193. 1477 NS2.NETCORPS.COM 194. 1476 NS0.DELTANET.COM 195. 1466 NS2.MEDIA3.NET 196. 1465 NS1.SIRIUS.COM 197. 1464 NS.MEDIA3.NET 198. 1455 MAIN.NETCORPS.COM 199. 1448 NS1.NI.NET 200. 1446 DNS2.DNAI.COM I've always been curious how well bind runs with 10,000+ domains in it. That's one big named.boot file. -- Rusty Hodge <rusty(a)hodge.com>, San Francisco

2 1