- Test - lists.nanog.org

Re: And we thought the text part of the Starr Report would be bad
by Roger Fajman 24 Sep '98

24 Sep '98

> > > For modem to modem communications, start and stop bits were used > > > up through 2400 baud when one bit = one tone. The method of one > > > bit = one tone was dropped for other forms of encoding when modems > > > started supporting connection speeds in excess of 2400 baud. > > > > I assume you mean 2400 bps modems, i.e., v.22bis? Admittedly, it's been a > > while since I used one, but my recollection is that 2400 bps modems operate > > at 600 baud, with 4 bits/baud using QAM. > > This matches my recollection. I think it was 1200 bps that was the > last 1 bit per baud modem. > > Cheers, > -- jra Yes and no. The Bell 202 was 1200 bps, one bit per baud, half duplex on a switched line. The Bell 212 was 1200 bps, 600 baud, 2 bits per baud, full duplex. So was the Vadic 3400, which preceded the 212.

1 0

ORG MIA
by cache22＠via.webkorner.com 24 Sep '98

24 Sep '98

now .org is missing from a.root-servers.net... ; <<>> DiG 2.2 <<>> @a.root-servers.net org. soa ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10 ;; flags: qr rd; Ques: 1, Ans: 0, Auth: 11, Addit: 11 ;; QUESTIONS: ;; org, type = SOA, class = IN ;; AUTHORITY RECORDS: org. 172800 NS H.ROOT-SERVERS.NET. org. 172800 NS B.ROOT-SERVERS.NET. org. 172800 NS C.ROOT-SERVERS.NET. org. 172800 NS D.ROOT-SERVERS.NET. org. 172800 NS E.ROOT-SERVERS.NET. org. 172800 NS I.ROOT-SERVERS.NET. org. 172800 NS F.ROOT-SERVERS.NET. org. 172800 NS G.ROOT-SERVERS.NET. org. 172800 NS J.GTLD-SERVERS.NET. org. 172800 NS K.GTLD-SERVERS.NET. org. 172800 NS A.ROOT-SERVERS.NET. ;; ADDITIONAL RECORDS: H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53 B.ROOT-SERVERS.NET. 3600000 A 128.9.0.107 C.ROOT-SERVERS.NET. 3600000 A 192.33.4.12 D.ROOT-SERVERS.NET. 3600000 A 128.8.10.90 E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10 I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17 F.ROOT-SERVERS.NET. 3600000 A 192.5.5.241 G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4 J.GTLD-SERVERS.NET. 518400 A 198.41.0.21 K.GTLD-SERVERS.NET. 518400 A 195.8.99.11 A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4 ;; Total query time: 270 msec ;; FROM: via to SERVER: a.root-servers.net 198.41.0.4 ;; WHEN: Wed Sep 23 23:17:43 1998 ;; MSG SIZE sent: 21 rcvd: 402 ; <<>> DiG 2.2 <<>> @b.root-servers.net org. soa ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10 ;; flags: qr aa rd; Ques: 1, Ans: 1, Auth: 11, Addit: 11 ;; QUESTIONS: ;; org, type = SOA, class = IN ;; ANSWERS: org. 86400 SOA A.ROOT-SERVERS.NET. hostmaster.INTERNIC.NET. ( 1998092200 ; serial 1800 ; refresh (30 mins) 900 ; retry (15 mins) 604800 ; expire (7 days) 86400 ) ; minimum (1 day) ;; AUTHORITY RECORDS: org. 518400 NS B.ROOT-SERVERS.NET. org. 518400 NS C.ROOT-SERVERS.NET. org. 518400 NS D.ROOT-SERVERS.NET. org. 518400 NS E.ROOT-SERVERS.NET. org. 518400 NS I.ROOT-SERVERS.NET. org. 518400 NS F.ROOT-SERVERS.NET. org. 518400 NS G.ROOT-SERVERS.NET. org. 518400 NS J.GTLD-SERVERS.NET. org. 518400 NS K.GTLD-SERVERS.NET. org. 518400 NS A.ROOT-SERVERS.NET. org. 518400 NS H.ROOT-SERVERS.NET. ;; ADDITIONAL RECORDS: B.ROOT-SERVERS.NET. 3600000 A 128.9.0.107 C.ROOT-SERVERS.NET. 3600000 A 192.33.4.12 D.ROOT-SERVERS.NET. 3600000 A 128.8.10.90 E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10 I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17 F.ROOT-SERVERS.NET. 3600000 A 192.5.5.241 G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4 J.GTLD-SERVERS.NET. 518400 A 198.41.0.21 K.GTLD-SERVERS.NET. 518400 A 195.8.99.11 A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4 H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53 ;; Total query time: 341 msec ;; FROM: via to SERVER: b.root-servers.net 128.9.0.107 ;; WHEN: Wed Sep 23 23:18:44 1998 ;; MSG SIZE sent: 21 rcvd: 458 for comparison... ; <<>> DiG 2.2 <<>> @a.root-servers.net gov. soa ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10 ;; flags: qr aa rd; Ques: 1, Ans: 1, Auth: 9, Addit: 9 ;; QUESTIONS: ;; gov, type = SOA, class = IN ;; ANSWERS: gov. 86400 SOA A.ROOT-SERVERS.NET. GARY\.BORGOYNE.FED.gov. ( 1998092300 ; serial 3600 ; refresh (1 hour) 900 ; retry (15 mins) 604800 ; expire (7 days) 86400 ) ; minimum (1 day) ;; AUTHORITY RECORDS: gov. 86400 NS I.ROOT-SERVERS.NET. gov. 86400 NS E.ROOT-SERVERS.NET. gov. 86400 NS D.ROOT-SERVERS.NET. gov. 86400 NS B.ROOT-SERVERS.NET. gov. 86400 NS C.ROOT-SERVERS.NET. gov. 86400 NS A.ROOT-SERVERS.NET. gov. 86400 NS H.ROOT-SERVERS.NET. gov. 86400 NS G.ROOT-SERVERS.NET. gov. 86400 NS F.ROOT-SERVERS.NET. ;; ADDITIONAL RECORDS: I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17 E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10 D.ROOT-SERVERS.NET. 3600000 A 128.8.10.90 B.ROOT-SERVERS.NET. 3600000 A 128.9.0.107 C.ROOT-SERVERS.NET. 3600000 A 192.33.4.12 A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4 H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53 G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4 F.ROOT-SERVERS.NET. 3600000 A 192.5.5.241 ;; Total query time: 5301 msec ;; FROM: via to SERVER: a.root-servers.net 198.41.0.4 ;; WHEN: Wed Sep 23 23:17:31 1998 ;; MSG SIZE sent: 21 rcvd: 379 ; <<>> DiG 2.2 <<>> @b.root-servers.net gov. soa ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10 ;; flags: qr aa rd; Ques: 1, Ans: 1, Auth: 9, Addit: 9 ;; QUESTIONS: ;; gov, type = SOA, class = IN ;; ANSWERS: gov. 86400 SOA A.ROOT-SERVERS.NET. GARY\.BORGOYNE.FED.gov. ( 1998092300 ; serial 3600 ; refresh (1 hour) 900 ; retry (15 mins) 604800 ; expire (7 days) 86400 ) ; minimum (1 day) ;; AUTHORITY RECORDS: gov. 86400 NS A.ROOT-SERVERS.NET. gov. 86400 NS H.ROOT-SERVERS.NET. gov. 86400 NS G.ROOT-SERVERS.NET. gov. 86400 NS F.ROOT-SERVERS.NET. gov. 86400 NS I.ROOT-SERVERS.NET. gov. 86400 NS E.ROOT-SERVERS.NET. gov. 86400 NS D.ROOT-SERVERS.NET. gov. 86400 NS B.ROOT-SERVERS.NET. gov. 86400 NS C.ROOT-SERVERS.NET. ;; ADDITIONAL RECORDS: A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4 H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53 G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4 F.ROOT-SERVERS.NET. 3600000 A 192.5.5.241 I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17 E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10 D.ROOT-SERVERS.NET. 3600000 A 128.8.10.90 B.ROOT-SERVERS.NET. 3600000 A 128.9.0.107 C.ROOT-SERVERS.NET. 3600000 A 192.33.4.12 ;; Total query time: 320 msec ;; FROM: via to SERVER: b.root-servers.net 128.9.0.107 ;; WHEN: Wed Sep 23 23:19:08 1998 ;; MSG SIZE sent: 21 rcvd: 379

1 0

WEATHER: Puerto Rico/Hurricane Georges
by Sean Donelan 24 Sep '98

24 Sep '98

37 dead. I'll concentrate on Puerto Rico because DRA has some customers on that island. I'm not sure of the Internet or telecommunication situation on other islands. Official reports are light to moderate damage. Electrical power has been restored to some parts of Puerto Rico, but 1 million people are still without power. Primary power generation facilities were not damaged, but the transmission network was damaged throughout the island. Telephone service was disrupted in several areas. Mayaguez and other areas are affected. Internet circuits through those central offices have also been affected. The storm track is currently Cuba on Sep 24, and Florida late on Sep 24 or early Sep 25. -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation

2 1

Re: And we thought the text part of the Starr Report would be bad
by Jerry Scharf 23 Sep '98

23 Sep '98

> As you would expect, they only get the real experts to speak: > > "While Bergman was confident ABCNews.com's plans to stream the video in its > entirety would go fine, Martin Hall of the IP Multicast Initiative says > the real problems would occur at the user's > end of the line. > > The standard T1 connection of an Internet service provider handles a > maximum of 53 dialup connections pumping data to a user, he said, but a > 54th user could cause a major problem." > The number of dialups on a T1, the number of bytes in a framed ATM cell. I see a telco conspiracy here. (:-) for the humor impaied) jerry

7 7

Re: And we thought the text part of the Starr Report would be bad
by Eric Sobocinski 23 Sep '98

23 Sep '98

On Tuesday, 22 Sep 1998 at 22:43 EDT, Robert Szarka <szarka(a)downcity.net> wrote: >At 11:22 AM 9/22/98 , you wrote: >> For modem to modem communications, start and stop bits were used >> up through 2400 baud when one bit = one tone. The method of one >> bit = one tone was dropped for other forms of encoding when modems >> started supporting connection speeds in excess of 2400 baud. > >I assume you mean 2400 bps modems, i.e., v.22bis? Admittedly, it's been a >while since I used one, but my recollection is that 2400 bps modems operate >at 600 baud, with 4 bits/baud using QAM. Your memory about v.22bis at 2400 bps is entirely correct. v.22 at 1200 bps/baud was the last of the 1 bps = 1 baud dialup modem standards. However, v.32/v.32bis/v.32ter/v.34/v.34bis all use trellis coding and additional tricks to get high bit rates out of 2400 baud. It is technically possible to get 2400 bps at 2400 baud from any of these latter standards, though realistically the only place you'll find conditions twisted enough to do that is in the lab. --eric (speaking only on my own authority, as usual)

1 0

Re: the GOV top-level domain
by Sean Donelan 23 Sep '98

23 Sep '98

>GOV. was missing from A.ROOT-SERVERS.NET sometime yesterday, but the >example with a timestampe has scrolled past my scroll buffer.... Apparently it is a "known" bug in bind that crops up from time to time. I haven't been closely monitoring the root name servers so I hadn't noticed it before. -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation

4 4

RE: Frame Relay encap vis-a-vis point-to-point at UUNET
by Chris Fairbanks 23 Sep '98

23 Sep '98

Well, UUnet does terminate T3s into the Cascades. One of our T3s happens to go to UUnet and it is into one of their Cascades at PAIX. It is currently only a fraction circuit. From talking with their installer, they only plug you directly into one of their routers if the circuit is 15mb or higher. We have had this circuit for 9 months now and everything seems to be working great with it. Later, Chris -----Original Message----- From: Deepak Jain [mailto:deepak@ai.net] Sent: Monday, September 21, 1998 3:01 PM To: Jerry Scharf Cc: bjames(a)mis.net; nanog(a)merit.edu Subject: Re: Frame Relay encap vis-a-vis point-to-point at UUNET I have never heard complaints about the Cascades for T-1 termination except where they are terminating too many sessions in the Cascades and the router couldn't handle that many sessions. This was a bigger problem before the 7500 series routers came out and more importantly the RSP4s. Fortunately UUNet doesn't terminate T3s into Cascades or ATM switches (yet...) -Deepak.

3 4

Traffic exceeds link capacity.
by jhyang 23 Sep '98

23 Sep '98

We have router which connected 45m hssi(A) with FR switch. That router contains two other interfaces, one is 45m hssi(B) and the other is 100m fddi (C). Because the most of the inbound traffic from (B) and (C) goes to (A) interface, the toal inbound traffic of (B) and (C) cannot exceed 45m. (Is it right ?) But the output rate of interface (A) exceeds 45m, -I can verify them in "sh int <int-name>"-, it increases upto 60~70 mbps. (Not really, but the statistic from CISCO commands.) When the phenomenen occurs, the total inbound traffic of (B) and (C) shows near 45 mbps (about 43.x mbps). My question is: Is it true that it indicates 60~70 mbps ? (Of cause, it has many output drops.) or Is it bug? The cpu load increases upto 99%, and it freezes router for short time -about 1~2 minute-. How to resolve this errors ? Our Router is: CISCO 7507 RSP2 IOS: 11.1.19 (CC) Enable CEF on (A): It is better than not using CEF. But the result doen't matter. (High CPU load, ..) Any Idea ? Thanks in advance --Jaeho Yang.

4 3

Re: Be Afraid -> InterNIC Email Addresses CD: $249
by Andrea Di Lecce 23 Sep '98

23 Sep '98

All, Just got off the phone with one of the admins at DN.NET, who hosts domainsondisc.com and domainsondisk.com. He informed me that they have received about 40 complaints, and have sent out a communication to the offender. If he does not respond in 24 hours, and cease all violations of their AUP, DN.NET will remove the domain. Hopefully it won't get spread around too much in the next 24 hours. I've also notified the upstream netaxs.net, and sent an email to UU.NET to remove the (probably throw-away) dialup account the spam was sent from. FYI. Andrea. ************************************************** Andrea Di Lecce (416) 935-5700 Rogers@Home Network Operations 1 Mount Pleasant Road, Toronto, M4Y 2Y5 **************************************************

1 0

RE: Get out your textbooks for this one!
by Martin, Christian 23 Sep '98

23 Sep '98

Problem 3, I haven't a clue, but problem 4 is the classical Dijkstra/Bellman-Ford algorithm problem. To build the routing table for each node step-by-sptep would consume much paper! -Chris > -----Original Message----- > From: Lutz, Kyle [mailto:Kyle@birchtel.com] > Sent: Wednesday, September 23, 1998 11:15 AM > To: 'nanog(a)merit.edu' > Subject: Get out your textbooks for this one! > > > I have implemented hundreds of networks and designed them > over the years > but I have not a clue on these questions. > > I realize that this is much more towards hardware design, but I know > that many of us have background there. > > Networking design 101 > > > problem 3: clearly illustrate the design of a knockout > > crossbar switch > > that enables an output port to choose packets from 9 input ports > > simultaneously in a 12x12 switch. your switch design must use > > the FEWEST > > number of 2x2 switching elements. > > > > problem 4: consider the network topology given in figure 2. > > the label for > > each of the links in the figure denotes the delay experience > > by any packet > > traversing the link (in either direction). each node is assumed to > > initially know the delays of its outgoing links and all links > > are assumed > > to be bi-directional. clearly show the routing table of > node A step by > > step, from the initial state to the final state (when the > > routing table > > stabilizes), for the following two cases: > > > > o when the routing algorithm is the Distance Vector algorithm > > o when the routing algorithm is the Link State algorithm > > > > __ 3 __B__ 4 __ > > / \ > > A------- 5 -------C\ H > > |\ | \ / > > | 2 | 1 2 > > 1 \ | \ / > > | E 6 / D > > | | 3 > > F------- 9 -------G/ > > > > > >

1 0