Anyone willing to say what happened? ******************************************************************** Gordon Cook, Editor & Publisher Subscript.: Individ-ascii $85 The COOK Report on Internet Non Profit. $150 431 Greenway Ave, Ewing, NJ 08618 Small Corp & Gov't $200 (609) 882-2572 Corporate $350 Internet: cook@cookreport.com Corporate. Site Lic $650 http://www.netaxs.com/~cook <- Subscription Info & COOK Report Index ******************************************************************** ---------- Forwarded message ---------- To: cook@cookreport.com Subject: MCI and SprintLink are partitioned (fwd) Forwarded message:
From spot.Colorado.EDU!westnet-site-people-request Tue Oct 3 20:48:25 1995 From: Chris Garner <cgarner@westnet.net> Message-Id: <199510040136.TAA06094@dozer.colorado.edu> Subject: MCI and SprintLink are partitioned To: westnet-site-people@westnet.net Date: Tue, 3 Oct 1995 19:36:50 -0600 (MDT) X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 289
MCI and SprintLink are disconnected at the moment. MCI is having a BGP problem with SprintLink. Currently the two networks are partitioned. The problem started just after 7pm (Mountain time) and is still occuring. -- -Chris (cgarner@westnet.net)
Wow, weird. Something I am wondering for quite some time already. My understanding is that the NSFNET infrastructural replacement for a finite amount of time and degrading support percentage is principally giving support to the (former) NSFNET mid-level/regional networks to obtain services for interconnection via some NSP on the competitive market. Secondly, the NSP chosen by the regional network has to interconnect to at least the three primary NAPs, with the principal reason to not partition the overall fabric. Thirdly some RA function to help with waving a wand over the art of routing. As a client of a client of a regional network that receives interconnection funding I have really no way to determine how the second criteria is being met, and the attached message suggests that it may not be. Can someone from the North American Network Operators Group (I think NANOG is the best place for this) please help finding some answers to: . are all three (four?) NAPs really being used (I know they are there, but despite repeated requests to at least one NAP service provider I appear to be unable to get an answer). I do know that the NY NAP is heavily used, including as my traffic to the Bay area sites I need access to traverses it (modulo all the losses in Sprintlink for at least weeks (reported to and confirmed by the regional network that serves SDSC, though from rumors I am hearing Sprintlink is rather not the exception, and many natives in the community starting to get restless] . Is there any evidence that the NAPs are really backing each other up? Did someone test and document it, e.g., with a few "test" networks in a bunch of regional networks? What are the time delays for a switch? Does someone have consecutive traceroute outputs where a switch among the NAPs really happened? . do we have some regular examples from *any* site A initiating a connection from A to B, A to C, and A to D, where the three are verifiably (via traceroute, I guess) would traverse different NAPs (and hopefully only one each)? . Are there routing stability reports accessible online from the RA (or whoever else feels responsible for this) that graph fluctuations at the NAPs, including correlation among them? What are the quality metrics for routing stability? . Do all the NAPs provide online statistics? . Are the NAP and RA regular reports to NSF publicly (hopefully via the Web) available? . Is there any way NANOG can be used to exchange status information about networks, rather than getting comments and rumors second or third hand. I understand that it is painful for a service provider to see problems on their network being posted, but if the alternative is a few bad incidents and rumors spreading that the network is always bad, I'd take a few hits and show I fix things quickly. Even better then posting (e.g, via some mailing list) would be an accessible distributed data base covering all the service pproviders and accessible via the network. Is someone already working on that? Would not NANOG be *the* forum to cooperate on that? I think this is prime NANOG business. Otherwise, who's problem are these? Who is or should be taking responsibility? Am I all off base here?
Anyone willing to say what happened?
******************************************************************** Gordon Cook, Editor & Publisher Subscript.: Individ-ascii $85 The COOK Report on Internet Non Profit. $150 431 Greenway Ave, Ewing, NJ 08618 Small Corp & Gov't $200 (609) 882-2572 Corporate $350 Internet: cook@cookreport.com Corporate. Site Lic $650 http://www.netaxs.com/~cook <- Subscription Info & COOK Report Index ********************************************************************
---------- Forwarded message ---------- To: cook@cookreport.com Subject: MCI and SprintLink are partitioned (fwd)
Forwarded message:
From spot.Colorado.EDU!westnet-site-people-request Tue Oct 3 20:48:25 1995 From: Chris Garner <cgarner@westnet.net> Message-Id: <199510040136.TAA06094@dozer.colorado.edu> Subject: MCI and SprintLink are partitioned To: westnet-site-people@westnet.net Date: Tue, 3 Oct 1995 19:36:50 -0600 (MDT) X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 289
MCI and SprintLink are disconnected at the moment. MCI is having a BGP problem with SprintLink. Currently the two networks are partitioned. The problem started just after 7pm (Mountain time) and is still occuring.
--
-Chris (cgarner@westnet.net)
. are all three (four?) NAPs really being used
Yes. for some value of "used".
. Is there any evidence that the NAPs are really backing each other up?
Not sure this is possible. Perhaps the better question is, are providers using the NAPs to back each other up.
. do we have some regular examples from *any* site A initiating a connection from A to B, A to C, and A to D, where the three are verifiably (via traceroute, I guess) would traverse different NAPs (and hopefully only one each)?
Yes.
. Are there routing stability reports accessible online from the RA (or whoever else feels responsible for this) that graph fluctuations at the NAPs, including correlation among them? What are the quality metrics for routing stability?
Being defined.
. Do all the NAPs provide online statistics?
No.
. Are the NAP and RA regular reports to NSF publicly (hopefully via the Web) available?
http://info.ra.net/papers have the annual report/plan papers
. Is there any way NANOG can be used to exchange status information accessible via the network. Is someone already working on that? Would not NANOG be *the* forum to cooperate on that?
Sounds like a really good idea to me. --bill
. are all three (four?) NAPs really being used Yes. for some value of "used".
That answer is close to meaningless. Please give me your metric.
. Is there any evidence that the NAPs are really backing each other up? Not sure this is possible. Perhaps the better question is, are providers using the NAPs to back each other up.
Let me rephrase. How is the NSF programmatic goal being met of creating three NAPs for redundancy purposes to avoid compartmentalization of the U.S. R&E portion of the Internet, and how is that being verified?
. do we have some regular examples from *any* site A initiating a connection from A to B, A to C, and A to D, where the three are verifiably (via traceroute, I guess) would traverse different NAPs (and hopefully only one each)? Yes.
So, where are they? Say, can you give me two examples for such an A-B/C/D scenario? One from SDSC, one from NSF. Your answers are a bit too flippant to me. Sorry.
. Are there routing stability reports accessible online from the RA (or whoever else feels responsible for this) that graph fluctuations at the NAPs, including correlation among them? What are the quality metrics for routing stability? Being defined.
To be publicly discussed, finished, and available by ...?
. Do all the NAPs provide online statistics? No.
Why not? Will that change? My understanding is that the NAP service providers have contractual obligations for some statistics. I know there is disagreement about what stats are appropriate, but is not there a contractual requirement for at least some baseline?
. Are the NAP and RA regular reports to NSF publicly (hopefully via the Web) available? http://info.ra.net/papers have the annual report/plan papers
Are there any more reporting requirements (quarterly? Monthly?). Waiting a year per report in such a changing environment strikes me as a bit long. If I wanted a comprehensive snapshot of the current state of the NAP-union, where/how would I get it.
. Is there any way NANOG can be used to exchange status information accessible via the network. Is someone already working on that? Would not NANOG be *the* forum to cooperate on that?
Sounds like a really good idea to me.
--bill
. are all three (four?) NAPs really being used Yes. for some value of "used".
That answer is close to meaningless. Please give me your metric.
Since they are neutral exchanges, w/o policy, I can only speak for for my project. I can't speak for any of the other sites that are attached. The RA has active peering sessions at all the NAPS. We do not have active peering sessions with some of the NSP's which are receiving NSF funding through the old regionals. What is your definition of used?
. Is there any evidence that the NAPs are really backing each other up? Not sure this is possible. Perhaps the better question is, are providers using the NAPs to back each other up.
Let me rephrase. How is the NSF programmatic goal being met of creating three NAPs for redundancy purposes to avoid compartmentalization of the U.S. R&E portion of the Internet, and how is that being verified?
That question can't be answered by the NAP operators, since they don't monitor traffic. You have to ask the NSP's.
. do we have some regular examples from *any* site A initiating a connection from A to B, A to C, and A to D, where the three are verifiably (via traceroute, I guess) would traverse different NAPs (and hopefully only one each)? Yes.
So, where are they? Say, can you give me two examples for such an A-B/C/D scenario? One from SDSC, one from NSF. Your answers are a bit too flippant to me. Sorry.
Anywhere to WELL.COM (via the PB NAP) Anywhere to NAP.NET (via the AADS NAP) Anywhere to CERF.NET (via the Sprint NAP) Of course your query presumes symetric routing, which is the exception rather than the rule these days.
. Are there routing stability reports accessible online from the RA (or whoever else feels responsible for this) that graph fluctuations at the NAPs, including correlation among them? What are the quality metrics for routing stability? Being defined.
To be publicly discussed, finished, and available by ...?
Check the RPS schedule w/in IETF.
. Do all the NAPs provide online statistics? No.
Why not? Will that change? My understanding is that the NAP service providers have contractual obligations for some statistics. I know there is disagreement about what stats are appropriate, but is not there a contractual requirement for at least some baseline?
I don't think so.
. Are the NAP and RA regular reports to NSF publicly (hopefully via the Web) available? http://info.ra.net/papers have the annual report/plan papers
Are there any more reporting requirements (quarterly? Monthly?). Waiting a year per report in such a changing environment strikes me as a bit long.
There are quarterly reports, which are not yet online. It's a good suggestion and I'll investigate.
If I wanted a comprehensive snapshot of the current state of the NAP-union, where/how would I get it.
Not enough info. You can dump the in-addr zones to discover who has been assigned an IP address You can see who has signed an MPLA, if they exist. You can check the CERFnet MAP You can check out http://info.ra.net/div7/ra/ep.html All of these have different viewpoints on the "NAP-union" and none have what I think you want. --bill
. are all three (four?) NAPs really being used Yes. for some value of "used". That answer is close to meaningless. Please give me your metric.
Since they are neutral exchanges, w/o policy, I can only speak for for my project. I can't speak for any of the other sites that are attached. The RA has active peering sessions at all the NAPS. We do not have active peering sessions with some of the NSP's which are receiving NSF funding through the old regionals.
What is your definition of used?
Operational traffic with real users crossing the NAP. I don't care (in this context) whether the RA has active peering sessions. That's network management, not use.
. Is there any evidence that the NAPs are really backing each other up? Not sure this is possible. Perhaps the better question is, are providers using the NAPs to back each other up.
Let me rephrase. How is the NSF programmatic goal being met of creating three NAPs for redundancy purposes to avoid compartmentalization of the U.S. R&E portion of the Internet, and how is that being verified?
That question can't be answered by the NAP operators, since they don't monitor traffic. You have to ask the NSP's.
I was/am asking NANOG. Was it your understanding that I sent a personal message to you?
. do we have some regular examples from *any* site A initiating a connection from A to B, A to C, and A to D, where the three are verifiably (via traceroute, I guess) would traverse different NAPs (and hopefully only one each)? Yes.
So, where are they? Say, can you give me two examples for such an A-B/C/D scenario? One from SDSC, one from NSF. Your answers are a bit too flippant to me. Sorry.
Anywhere to WELL.COM (via the PB NAP)
%upeksa[70]/usr/people/hwb 10:50: tr WELL.COM traceroute to WELL.COM (206.15.64.10), 30 hops max, 40 byte packets 1 tigerfish.sdsc.edu (132.249.22.11) 8 ms 8 ms 7 ms 2 mobydick.cerf.net (198.17.46.153) 3 ms 3 ms 4 ms 3 agis.sprint.ep.net (192.157.69.19) 69 ms 69 ms 69 ms 4 trenton-T3.agis.net (204.130.243.49) 72 ms 72 ms 73 ms 5 santaclara.agis.net (204.130.243.34) 83 ms 82 ms 81 ms 6 * * * 7 well.com (206.15.64.10) 90 ms * 87 ms %upeksa[71]/usr/people/hwb 10:51:
Anywhere to NAP.NET (via the AADS NAP)
%upeksa[71]/usr/people/hwb 10:51: tr nap.net traceroute to nap.net (204.95.160.2), 30 hops max, 40 byte packets 1 tigerfish.sdsc.edu (132.249.22.11) 7 ms 7 ms 7 ms 2 mobydick.cerf.net (198.17.46.153) 10 ms 4 ms 8 ms 3 longboard.cerf.net (198.17.46.152) 4 ms 5 ms 10 ms 4 la-sd-ds3.cerf.net (134.24.115.200) 7 ms 7 ms 9 ms 5 ucop-sf-ds3-smds.cerf.net (134.24.9.112) 25 ms 27 ms 29 ms 6 sl-ana-3-S2/6-T1.sprintlink.net (144.228.73.81) 35 ms 36 ms 35 ms 7 sl-ana-2-F0/0.sprintlink.net (144.228.70.2) 89 ms 91 ms 90 ms 8 sl-stk-6-H2/0-T3.sprintlink.net (144.228.10.25) 91 ms 94 ms 92 ms 9 sl-stk-5-F0/0.sprintlink.net (144.228.40.5) 97 ms 89 ms 91 ms 10 144.228.10.53 (144.228.10.53) 89 ms 89 ms 89 ms 11 sl-chi-5-F0/0.sprintlink.net (144.228.50.5) 89 ms 92 ms 93 ms 12 sl-inetconn-1-S0-T1.sprintlink.net (144.228.55.114) 100 ms 101 ms 100 ms 13 beta.inc.net (204.95.160.2) 96 ms 100 ms 101 ms %upeksa[72]/usr/people/hwb 10:51:
Anywhere to CERF.NET (via the Sprint NAP)
%upeksa[72]/usr/people/hwb 10:52: tr stanford.edu traceroute to stanford.edu (36.56.0.151), 30 hops max, 40 byte packets 1 tigerfish.sdsc.edu (132.249.22.11) 7 ms 8 ms 9 ms 2 mobydick.cerf.net (198.17.46.153) 56 ms 4 ms 4 ms 3 longboard.cerf.net (198.17.46.152) 6 ms 3 ms 3 ms 4 la-sd-ds3.cerf.net (134.24.115.200) 7 ms 8 ms 8 ms 5 ucop-sf-ds3-smds.cerf.net (134.24.9.112) 26 ms 30 ms 29 ms 6 border3-hssi1-0.SanFrancisco.mci.net (149.20.64.9) 37 ms 29 ms 33 ms 7 borderx1-fddi0-0.SanFrancisco.mci.net (204.70.2.164) 28 ms 29 ms 27 ms 8 barrnet.SanFrancisco.mci.net (204.70.158.102) 35 ms 29 ms 33 ms 9 su-tk.wr.bbnplanet.net (192.31.48.1) 31 ms 32 ms 30 ms 10 sunet-gateway.stanford.edu (198.31.10.1) 30 ms 29 ms 32 ms 11 Argus.Stanford.EDU (36.56.0.151) 32 ms 31 ms 33 ms %upeksa[73]/usr/people/hwb 10:52: %upeksa[73]/usr/people/hwb 10:52: tr nsipo.nasa.gov traceroute to nsipo.nasa.gov (128.102.32.20), 30 hops max, 40 byte packets 1 tigerfish.sdsc.edu (132.249.22.11) 7 ms 7 ms 7 ms 2 mobydick.cerf.net (198.17.46.153) 4 ms 3 ms 3 ms 3 sl-pen-2-F4/0.sprintlink.net (192.157.69.9) 75 ms 235 ms 71 ms 4 sl-chi-3-H2/0-T3.sprintlink.net (144.228.10.38) 95 ms 95 ms 95 ms 5 sl-chi-6-F0/0.sprintlink.net (144.228.50.6) 95 ms 95 ms 95 ms 6 144.228.10.54 (144.228.10.54) 134 ms 134 ms 134 ms 7 icm-fix-w-H2/0-T3.icp.net (144.228.10.22) 137 ms 140 ms 137 ms 8 arc-nas-gw.arc.nasa.gov (192.203.230.3) 138 ms 139 ms 136 ms 9 nsipo.arc.nasa.gov (128.102.32.20) 138 ms 137 ms 137 ms %upeksa[74]/usr/people/hwb 10:53:
Of course your query presumes symetric routing, which is the exception rather than the rule these days.
. Are there routing stability reports accessible online from the RA (or whoever else feels responsible for this) that graph fluctuations at the NAPs, including correlation among them? What are the quality metrics for routing stability? Being defined.
To be publicly discussed, finished, and available by ...?
Check the RPS schedule w/in IETF.
. Do all the NAPs provide online statistics? No.
Why not? Will that change? My understanding is that the NAP service providers have contractual obligations for some statistics. I know there is disagreement about what stats are appropriate, but is not there a contractual requirement for at least some baseline?
I don't think so.
. Are the NAP and RA regular reports to NSF publicly (hopefully via the Web) available? http://info.ra.net/papers have the annual report/plan papers
Are there any more reporting requirements (quarterly? Monthly?). Waiting a year per report in such a changing environment strikes me as a bit long.
There are quarterly reports, which are not yet online. It's a good suggestion and I'll investigate.
If I wanted a comprehensive snapshot of the current state of the NAP-union, where/how would I get it.
Not enough info. You can dump the in-addr zones to discover who has been assigned an IP address You can see who has signed an MPLA, if they exist. You can check the CERFnet MAP You can check out http://info.ra.net/div7/ra/ep.html
All of these have different viewpoints on the "NAP-union" and none have what I think you want.
Where can I find mapping information from the in-addr zones to attributes like service providers, or even simple things like countries (that uses a consistent data base)?
--bill
Where can I find mapping information from the in-addr zones to attributes like service providers, or even simple things like countries (that uses a consistent data base)?
Check out the RADB or you nearby router's routing tables. These will get you route/AS mappings, and then the NIC's whois will get you AS/name mappings. --asp@uunet.uu.net (Andrew Partan)
. are all three (four?) NAPs really being used
Yes. for some value of "used".
The NewYorsey Nap is being "used". I see approx. 3E4 packets per sec. peak (averaged over a 5 min. period). This is through our gigaswitch. Intra-FDDI is additional.
. Do all the NAPs provide online statistics?
No.
Whoa there, Nellie. Sprint NAP stats are available from http://www.nlanr.net/NAP. 30 days worth on-line, but available since inception (about March-April '95). Ask and you shall receive. MFS also is available, I believe. I don't know about the others. -- Bilal
--bill
. Do all the NAPs provide online statistics?
No.
Whoa there, Nellie. Sprint NAP stats are available from http://www.nlanr.net/NAP. 30 days worth on-line, but available since inception (about March-April '95). Ask and you shall receive.
Good to know. Is this the right place to get a consolidated view of Sprint NAP services? Right now, the Sprint homepage has zero pointers to its NAP information. --bill
Bill: Yup, most of the stuff on the ra page (http://nic.merit.edu/nsf.architecture/Sprint) is useful but outdated. Sprint needs to update the info, especially the fee table :)- I'll also see if we can get a pointer from Sprint's home page to NAP info. Thanks, -- Bilal San Diego Supercomputer Center (!Sprint)
. Do all the NAPs provide online statistics?
No.
Whoa there, Nellie. Sprint NAP stats are available from http://www.nlanr.net/NAP. 30 days worth on-line, but available since inception (about March-April '95). Ask and you shall receive.
Good to know. Is this the right place to get a consolidated view of Sprint NAP services? Right now, the Sprint homepage has zero pointers to its NAP information.
--bill
Hi Bilal! On Wed, 4 Oct 1995, Bilal Chinoy wrote:
Whoa there, Nellie. Sprint NAP stats are available from http://www.nlanr.net/NAP. 30 days worth on-line, but available since inception (about March-April '95). Ask and you shall receive.
This is *really* cool. Dun Liu and I are about to put our RA seen NAP stats up on the web. We found it quite useful to be able to compare our customer-seen NAP performance statistics along side of the MFS NAP-Provider seen performance statistics. For example, there appears to be a strong (perhaps expected) correlation between the MAE-East media load and the latency we see bwetween the RS and its peers. And interestingly enough, we see a point of media utilization after which packet loss increases dramatically. I think that the NANOG community would also benefit from having this data available on the web so such correlations could be made. To approach the completeness of data that was available in the NSFNET days I think we should encourage all NAP participants to post their NAP-related data to the web as well. We have MAE-East and Sprint NAP-provider data, and soon we'll have the RA as a NAP customer providing data as well. What are the chances of other NAP attachees putting up NAP-related data on the web in the same fashion? Bill ------------------------------------------------------------------------- William B. Norton Merit Network Inc. e-mail: wbn@merit.edu phone: (313) 936-2656 WWW: http://home.merit.edu/~wbn
Hans-Werner,
Hans-Werner Braun writes:
. Are there routing stability reports accessible online from the RA (or whoever else feels responsible for this) that graph fluctuations at the NAPs, including correlation among them? What are the quality metrics for routing stability?
Every 15 minutes each route server sends 5 ping packets to each of its peers. The Routing Arbiter has been collecting this information as each route server was installed and established peering sessions. The processed data and proto-type reports were planned to be announced next week. Look for the announcement sometime early next week. In addition, the route servers record the number of BGP updates received from each peer. These reports will also be available sometime next week. We have Bill Norton to thank for setting up the process to gather the data and Dun Liu to thank for processing the data and creating the reports.
. Are the NAP and RA regular reports to NSF publicly (hopefully via the Web) available?
The RA's annual report and plan for the 2nd year are available on the web: http://www.ra.net --Elise
In message <199510041535.IAA23092@upeksa.sdsc.edu>, Hans-Werner Braun writes:
. are all three (four?) NAPs really being used (I know they are there, but despite repeated requests to at least one NAP service provider I appear to be unable to get an answer). I do know that the NY NAP is heavily used, including as my traffic to the Bay area sites I need access to traverses it (modulo all the losses in Sprintlink for at least weeks (reported to and confirmed by the regional network that serves SDSC, though from rumors I am hearing Sprintlink is rather not the exception, and many natives in the community starting to get restless]
We primarily use MaeEast and the Sprint NAP with backup through E144 (FixE), and soon MaeWest. We don't connect to AADS and only use PacBell for customers not reachable by an other means.
. Is there any evidence that the NAPs are really backing each other up? Did someone test and document it, e.g., with a few "test" networks in a bunch of regional networks? What are the time delays for a switch? Does someone have consecutive traceroute outputs where a switch among the NAPs really happened?
Yes there is. The NAPs can back each other up, but traffic can be a real problem if MaeEast goes down. Since adding the gigaswitch, Sprint NAP becomes much more viable as a backup and MaeWest is promising since they too may go with switched FDDI.
. do we have some regular examples from *any* site A initiating a connection from A to B, A to C, and A to D, where the three are verifiably (via traceroute, I guess) would traverse different NAPs (and hopefully only one each)?
There are tons of examples. If the load wasn't split, we'd drown in the traffic load at MaeEast.
. Are there routing stability reports accessible online from the RA (or whoever else feels responsible for this) that graph fluctuations at the NAPs, including correlation among them? What are the quality metrics for routing stability?
We have very reliable statistics on the peering session stability with our peers at every interchange. We also have some very unreliable data (sorry folks, the data reall isn't very good) on prefix stability. On a bad day (a few times a month) we might have a total disconnect time on a given peer of 5-15 minutes over a 24 hour period. This is the worst single peer, not the NAP as a whole. We occasionally (a few times a month) see the entire set of peers drop at MaeEast, we think due to route flap. The normal case is many days, without losing a peering session *anywhere*, interrupted by a loss of a single or small number of peers lasting from a few seconds to a few minutes followed by another few days of uninterrupted peering. The stability of the prefixes announced by those peers is another story. Unfortunately the data collection we have in place has been somewhat broken for a while now. The external route flap reporting is seen as a low priority (not officially supported, you can't get a lower priority), and I haven't had the time to fix it.
. Do all the NAPs provide online statistics?
. Are the NAP and RA regular reports to NSF publicly (hopefully via the Web) available?
You have reporting requirements? Great. We regularly show summary information on internal routing stability and external peer stability (I think that is still publicly available). The more detailed daily summary and the incident logs are not made public, though we should be proud of our record, so I was never able to figure out why. Perhaps you (NSF) can get a copy for reference.
. Is there any way NANOG can be used to exchange status information about networks, rather than getting comments and rumors second or third hand. I understand that it is painful for a service provider to see problems on their network being posted, but if the alternative is a few bad incidents and rumors spreading that the network is always bad, I'd take a few hits and show I fix things quickly. Even better then posting (e.g, via some mailing list) would be an accessible distributed data base covering all the service pproviders and accessible via the network. Is someone already working on that? Would not NANOG be *the* forum to cooperate on that?
This would be great, but I can't see it happenning.
I think this is prime NANOG business. Otherwise, who's problem are these? Who is or should be taking responsibility? Am I all off base here?
We should confirm that there actually was a problem and the problem duration first. Curtis
. Do all the NAPs provide online statistics?
MAE-East & MAE-West do. Check out: http://mfsdatanet.com/MAE/ --asp@uunet.uu.net (Andrew Partan)
participants (8)
-
asp＠uunet.uu.net -
bac＠serendip.sdsc.edu -
bmanning＠ISI.EDU -
Curtis Villamizar -
Elise Gerich -
Gordon Cook -
hwb＠upeksa.sdsc.edu -
William B. Norton