They "lose" money because they are required by law to re-sell their existing lines at the same prices they charge their own internal companies, i.e. internet divisions. It's a self-created problem that the babybells do so they can scream about how they're being gouged. By themselves.
perhaps you should do more research instead of toe'ing the ILEC line.
Well, I, for instance, currently operate a public 802.11 node in Seattle. It has a DHCP server listening on it to pass out ip addresses with full internet access. The only access-control on that network is some restrictions in place to keep wireless users from accessing my internal network, and only inbound established tcp sessions allowed.. (to prevent my next door neighbour from running a warez server off my bandwidth.:) The only other piece of "access-control" is an HTTP proxy-authentication piece that wifi users just login with "public/public" to get internet access. No logging, no tracking, nothing, nada. So if you want to hack the gubbmint from my home network, well, then I guess I'm just up shit's creek.
I am willing to accept the fact that not everyone will be kind in their usage of my public offering. By sharing something that I believe everyone should have access to, it makes me feel a bit better knowing that I have helped out the global community as a whole.
ultrasound vision (ala bats, for total darkness and lack of thermal)
protective reflexive kevlar shutters
HUD detailing gps and environmental information
ability to take pictures of views
internal storage for the pictures
internal "eye dart" with some type of munition. (your choice, however if you use a bullet you hafta make a check against stress damage to the eye... er. woops. too much shadowrun for me..)
You have the routers and switches along the path to the destination perform the encryption. Much in the same way current IPSec VPNs are created. This way the encryption remains transparent to the application as well.
*yawn*
First of all, Microsoft does have their own internal network. For all you know, they might be simply announcing an aggregate, and then using IGP to route over their own internal network. And how the hell do you know there's only a single route to that class C? In fact, lets see here now:
(from nitrous looking glass)
BGP routing table entry for 207.46.128.0/18, version 30012368
Paths: (15 available, best #12)
hmm
Microsoft (NETBLK-MICROSOFT-GLOBAL-NET)
One Microsoft Way
Redmond, WA 98103
US
Netname: MICROSOFT-GLOBAL-NET
Netblock: 207.46.0.0 - 207.46.255.255
gee.. they took their/16 and yanked a/18 out of it, and assigned it up there in redmond someplace.
Now how do you know that they didn't put 2 name servers in redmond, and another one maybe in downtown seattle?:P 15 routes into that block alone.. that's pretty redundant. I think the better fuck up on their part is this one:
Domain System inverse mapping provided by:
DNS4.CP.MSFT.NET 207.46.138.11
DNS4.CP.MSFT.NET 207.46.138.11
because let's say that goodnet doesnt peer directly with sprintnet. well, guess what? that means you go through a public interexchange, i.e. mae-east, -west, etc.. and well, they're rather congested, and tend to drop packets whenever its convienent for them. By providing a direct peering relationship for these big providers, you cut out the public interexchange. Also, InterNAP pays its providers to carry it's traffic for as *long* as possible, versus the traditional method where providers attempt to dump traffic at the first public peering point. Trust me, there is a *huge* difference between an internap DS3 and a UUNet DS3. You pay alot more, but if you have traffic/applications that need bandwidth that's low latency and low jitter, use internap. (no, I dont work for them. I'm a network engineer for growing DSL/VoIP provider, and they're a godsend.)
This is nothing new. InterNAP has been doing this for years now. Which is why they're so goddamn expensive. But I must say that they offer the *best* data pipes you can possibly get. They peer with 8-9 of the largest providers in each PNAP and your traffic goes to the provider that has the best route. They do an exhaustive systematic search through the global BGP routing table and pick and choose their routes individually. I would assume their route-maps are freaking gigantic. Their technology is unfortunately not real time... (yet.;) Anyone who knows how BGP works can figure out how they do this.. it seems rather simple (I deal with them on a regular basis) but they came up with it first.
Okay, time for my shameless plug. I'm a network engineer for Bazillion. I handle all the backbone routing and transport facilities. Our DSL side of things is still relatively new, but already we are the fastest growing Covad DSL partner nationwide. If you can tolerate some less than perfect customer service *coughs*, our DSL lines kick ass. Plus, we offer 400 minutes of free domestic long distance. And we're *very* OSS friendly. Honestly, you will get your best service if you are local to Seattle, Chicago, San Diego, Houston, or Phoenix. Any other place and you get stuck on a Covad national circuit, which means you come out in Chicago.. so dont expect the best from that situation, since Covad has some issues with their ATM clouds.
It seems to me that this would somehow indicate the start of an entirely new polictical structure within world affairs. It appears as those this is one of the first drastic foriegn policy changes occuring to the United States brought on by another World body. Just another sign that the United States is no longer the biggest player in this game of chess. The EU will simply replace the position the US had and also push foriegn policy to other countries, with their citizens in mind, not their citizens and everyone else. Oh well.
Slashdot Mirror
They "lose" money because they are required by law to re-sell their existing lines at the same prices they charge their own internal companies, i.e. internet divisions. It's a self-created problem that the babybells do so they can scream about how they're being gouged. By themselves.
perhaps you should do more research instead of toe'ing the ILEC line.
Well, I, for instance, currently operate a public 802.11 node in Seattle. It has a DHCP server listening on it to pass out ip addresses with full internet access. The only access-control on that network is some restrictions in place to keep wireless users from accessing my internal network, and only inbound established tcp sessions allowed.. (to prevent my next door neighbour from running a warez server off my bandwidth. :) The only other piece of "access-control" is an HTTP proxy-authentication piece that wifi users just login with "public/public" to get internet access. No logging, no tracking, nothing, nada. So if you want to hack the gubbmint from my home network, well, then I guess I'm just up shit's creek.
I am willing to accept the fact that not everyone will be kind in their usage of my public offering. By sharing something that I believe everyone should have access to, it makes me feel a bit better knowing that I have helped out the global community as a whole.
dude, its all about:
optical zoom
digital magnification/enhancement
flare compensation
thermal imaging
low-light imaging
ultrasound vision (ala bats, for total darkness and lack of thermal)
protective reflexive kevlar shutters
HUD detailing gps and environmental information
ability to take pictures of views
internal storage for the pictures
internal "eye dart" with some type of munition. (your choice, however if you use a bullet you hafta make a check against stress damage to the eye... er. woops. too much shadowrun for me..)
You have the routers and switches along the path to the destination perform the encryption. Much in the same way current IPSec VPNs are created. This way the encryption remains transparent to the application as well.
*yawn*
/16 and yanked a /18 out of it, and assigned it up there in redmond someplace.
:P 15 routes into that block alone.. that's pretty redundant. I think the better fuck up on their part is this one:
First of all, Microsoft does have their own internal network. For all you know, they might be simply announcing an aggregate, and then using IGP to route over their own internal network. And how the hell do you know there's only a single route to that class C? In fact, lets see here now:
(from nitrous looking glass)
BGP routing table entry for 207.46.128.0/18, version 30012368
Paths: (15 available, best #12)
hmm
Microsoft (NETBLK-MICROSOFT-GLOBAL-NET)
One Microsoft Way
Redmond, WA 98103
US
Netname: MICROSOFT-GLOBAL-NET
Netblock: 207.46.0.0 - 207.46.255.255
gee.. they took their
Now how do you know that they didn't put 2 name servers in redmond, and another one maybe in downtown seattle?
Domain System inverse mapping provided by:
DNS4.CP.MSFT.NET 207.46.138.11
DNS4.CP.MSFT.NET 207.46.138.11
=)
because let's say that goodnet doesnt peer directly with sprintnet. well, guess what? that means you go through a public interexchange, i.e. mae-east, -west, etc.. and well, they're rather congested, and tend to drop packets whenever its convienent for them. By providing a direct peering relationship for these big providers, you cut out the public interexchange. Also, InterNAP pays its providers to carry it's traffic for as *long* as possible, versus the traditional method where providers attempt to dump traffic at the first public peering point. Trust me, there is a *huge* difference between an internap DS3 and a UUNet DS3. You pay alot more, but if you have traffic/applications that need bandwidth that's low latency and low jitter, use internap. (no, I dont work for them. I'm a network engineer for growing DSL/VoIP provider, and they're a godsend.)
This is nothing new. InterNAP has been doing this for years now. Which is why they're so goddamn expensive. But I must say that they offer the *best* data pipes you can possibly get. They peer with 8-9 of the largest providers in each PNAP and your traffic goes to the provider that has the best route. They do an exhaustive systematic search through the global BGP routing table and pick and choose their routes individually. I would assume their route-maps are freaking gigantic. Their technology is unfortunately not real time... (yet. ;) Anyone who knows how BGP works can figure out how they do this.. it seems rather simple (I deal with them on a regular basis) but they came up with it first.
Okay, time for my shameless plug. I'm a network engineer for Bazillion. I handle all the backbone routing and transport facilities. Our DSL side of things is still relatively new, but already we are the fastest growing Covad DSL partner nationwide. If you can tolerate some less than perfect customer service *coughs*, our DSL lines kick ass. Plus, we offer 400 minutes of free domestic long distance. And we're *very* OSS friendly. Honestly, you will get your best service if you are local to Seattle, Chicago, San Diego, Houston, or Phoenix. Any other place and you get stuck on a Covad national circuit, which means you come out in Chicago.. so dont expect the best from that situation, since Covad has some issues with their ATM clouds.
It seems to me that this would somehow indicate the start of an entirely new polictical structure within world affairs. It appears as those this is one of the first drastic foriegn policy changes occuring to the United States brought on by another World body. Just another sign that the United States is no longer the biggest player in this game of chess. The EU will simply replace the position the US had and also push foriegn policy to other countries, with their citizens in mind, not their citizens and everyone else. Oh well.