I hate to say it, but the ball is largely in Microsoft's court. They control the majority of the desktop corporate/personal e-mail client market. Any new standard that comes into play will need their blessing, unless someone can wrench control away from them.
I really liked the hashcash system (http://www.hashcash.org/), but MS Zombie (tm) makes this less and less useful.
I wonder how well some kind of public-key trust system would work. After seeing how powerful social networking relationships can be on a much smaller scale (Friendster), maybe this could work. Direct relationships would be weighted heaviest, and the weight would decay exponentially for each level removed. Each trust relationship would add to a score, with the qualifying score to be specified by the receiving end. I'd even be willing to pay the likes of Verisign to run such a thing! Exceptions would likely need to be made for business -- hiring, information requests, etc.
Nah, the spammers would end up just compromising the PC, stealing the unencrypted secret key, and would then spam that persons trust network.
How you spend money for yourself, and how you spend money for your company are two completely different things.
Bill may have spent many millions on his own home, but he was notorious for flying coach, and only in '97 did he buy a personal jet, with his own money.
I don't know who is footing the bill for google's new toy, but google has definitely always been about excess.
Your sysadmin type may have been right. It's a major PITA to have to worry about hosts files on many servers, and can increase troubleshooting time down the road.
As long as he was being anal-retentive though, he really should have insisted on a backup DNS server.
And depending on how anal-retentive the backup program was, he could have been right to blame it at least partially. A program that is "functioning within specifications" can still have its head up its ass.
If you, hypothetically, bought a single connection to either Level 3 or Cogent, and expected it to be reliable, and were bit by the recent de-peering event, then the problem is that you designed an un-reliable solution.
If you must buy a single dedicated Internet connection, then buy it from someone who has the redundancy built into their network _AND_ transit agreements.
If any regulation happens, it shouldn't be to interfere with the business arrangements between Tier 1 providers, it should probably be in the form of a waiver or notice to consumers of single-homed transit.
The problem I've noticed is that most consumers don't seem to realize the redundancy lost in single-homed transit. DIA is DIA they think. Even after the recent de-peering event, many are more confused than before because of all the misinformation.
Like the previous poster said, any important applications or networks should be multi-homed.
A couple solutions that would have avoided outage:
Single link without BGP: Your organization could have purchased its DIA from an ISP that was multi-homed.
Dual links with BGP: Your organization could have purchased a small amount of DIA (relative to your main pipe) from another provider, weighted/prefixed it less desirable than your primary connectivity, and not lost connectivity to L3/Cogent. You could have possibly even worked a deal with your vendor because of its use as last-resort/emergency connectivity.
I thought the same thing until I RTFA. It's the submitter that should be plonked for the misleading headline.
It's not about storing your VM's disk image on an iPod. They just happened to use an iPod as the portable storage device -- probably because it's the most common, compact, portable storage device with large capacity. i.e. people carry these things on their person, compared to other drives of their size.
They are researching the idea of taking your computing environment with you wherever you go, and productizing it.
Not a new idea, but it's interesting to hear that someone like IBM is researching it.
If you're a CLEC, you do have access to such things under UNE provisions, however the FCC has been meddling in that too.
This probably won't be the end of third-party DSL, just the end of CHEAP third-party DSL.
CLECs can still co-locate their DSLAMs in incumbent COs and lease last-mile loops to their customers, and provide their own DSL.
Smaller ISPs, like VISI which the grandparent mentions, will be greatly affected. Right now they are re-selling the Qwest/Frontier DSL product offerings. If this is re-classified by the FCC, Qwest and Frontier will cut them out and their DSL business will evaporate overnight.
This is a shame because, as many of you probably know, smaller ISPs are great for support and customized solutions for SMB and home customers.
Earthlink and Speakeasy could concievably offer their own DSL product as a CLEC, if that's not what they're already doing anyway.
I'm only commenting on the subject of this article, that the FCC may force VoIP providers to provide location identification information.
There are flaws with every idea, but GPS seems like a natural one since it's already used for the same purpose in newer cell phones, another FCC mandate that was imposed on the cell phone industry. The cell phone industry hasn't gone away because of it.
GPS would probably be more controversial than Intel's processor ID, might have signal reception problems, and might add a few dollars to the cost; but it might be exactly what VoIP vendors need to comply with FCC regulations. And it might not.:)
Not true. Text from my Sanyo telephone: "Turning location on will allow the network to detect your position, making some Sprint applications easier to use. Turning location off will hide your location from everyone except 911. Ever if location is turned on in this handset, no service may use your location without your express permission."
and an interesting tidbit I found on google (url http://clinton4.nara.gov/WH/EOP/OSTP/html/0053_4.h tml) " Enhanced-911: The FCC will soon require that all new cellular phones be equipped with more accurate location determination technology to improve responses to emergency 911 calls. Removing SA will boost the accuracy of GPS to such a degree that it could become the method of choice for implementing the 911 requirement. A GPS-based solution might be simpler and more economical than alternative techniques such as radio tower triangulation, leading to lower consumer costs."
As far as time synchronization, I'm ignorant to modern standards, but I do recall a company that sold NTP servers that synchronized with cellular towers using CDMA vs. GPS, which indicates that cell phones do this as well. It's quite possible that the GPS enabled ones use GPS instead.
If the FCC requires them to do something, then they'll have to either conform or fight the FCC.
If major cell phone manufacturers are doing this already, it doesn't seem like much of an obstacle in the long term for commercial VoIP vendors to issue one with their service, especially if it helps them avoid being sued by its users or penalized by the FCC.
Enterprise computing. There's something to be said about the vendor of your server being the same vendor as your operating system, not even accounting for how well it performs.
You could roll ham radio into a new bundle called "FreeInternet" and sell it to your average consumer. Let me know how this business model works for you.
Laughable, but this is the type of network you're proposing; but without the operator intelligence to keep the thing from falling in on itself.
I betcha we're doing very rough aproximations,
and then sticking the results in a tight feedback loop that spends that 3-4 seconds adjusting and readjusting our position relative to the object.
Equifax has their own certificate.
They have a certificate signed to them
saying that they are an authorized CA.
When you install Equifax certs you actually
install two certs. You install your site
cert signed by Equifax, and you install
the Equifax CA cert designating them as
a valid CA. This is good since in the
past a new CA, like Thawte, would require
new web browsers to be distributed with
information for that CA included. Old
SSL web server implementations, however,
don't always support CA certs. The OpenSSL
library is one piece of software that
doesn't in older versions. Any web servers
depending on this would need to be upgraded
to use an Equifax cert. This isn't exactly
new though.
I have a couple boxes called "Aardvarks."
They store 1.8GB on a standard VHS tape.
You connect the aardvark to your VCR using
RCA cables for video in/out. Then you connect
the unit to your computer using a parallel
cable.
You train the aardvark to control your VCR
by pointing your remote at it and pressing
play when it asks you to do so in setup.
It then writes a file containing the data
it needs to play back for Play. You then
point the aardvark at your VCR so it can
control it.
It's a nifty little device that stored a
huge amount of data (at that time.) It did
have one problem though. It would over-estimate
the amount of time required for a VHS tape to
rewind when it would go to do a verify, etc.
It would end up rewinding the tape in 2 minutes
and then calculating that it would take about 16
hours or so. Pretty annoying.
The guy that made these things pretty much
dropped off the face of the earth from what
I can tell.
Another design flaw is that the device has
this scary screen where you can see
how close you're coming to not being able
to restore your data. It shows you when it
uses error correction code, and it uses it
QUITE often.
Slashdot Mirror
So use a layer 3 switch, and if you'd like, bond multiple ports to your Linux-based router using LACP.
These words are easy enough to say, but... :)
I hate to say it, but the ball is largely in Microsoft's court. They control the majority of the desktop corporate/personal e-mail client market. Any new standard that comes into play will need their blessing, unless someone can wrench control away from them.
I really liked the hashcash system (http://www.hashcash.org/), but MS Zombie (tm) makes this less and less useful.
I wonder how well some kind of public-key trust system would work. After seeing how powerful social networking relationships can be on a much smaller scale (Friendster), maybe this could work. Direct relationships would be weighted heaviest, and the weight would decay exponentially for each level removed. Each trust relationship would add to a score, with the qualifying score to be specified by the receiving end. I'd even be willing to pay the likes of Verisign to run such a thing! Exceptions would likely need to be made for business -- hiring, information requests, etc.
Nah, the spammers would end up just compromising the PC, stealing the unencrypted secret key, and would then spam that persons trust network.
Resistance is futile. Learn to love spam!
How you spend money for yourself, and how you spend money for your company are two completely different things. Bill may have spent many millions on his own home, but he was notorious for flying coach, and only in '97 did he buy a personal jet, with his own money. I don't know who is footing the bill for google's new toy, but google has definitely always been about excess.
Your sysadmin type may have been right. It's a major PITA to have to worry about hosts files on many servers, and can increase troubleshooting time down the road.
As long as he was being anal-retentive though, he really should have insisted on a backup DNS server.
And depending on how anal-retentive the backup program was, he could have been right to blame it at least partially. A program that is "functioning within specifications" can still have its head up its ass.
So tell the mines to only communicate after one of their neighbors detonates.
If you, hypothetically, bought a single connection to either Level 3 or Cogent, and expected it to be reliable, and were bit by the recent de-peering event, then the problem is that you designed an un-reliable solution.
If you must buy a single dedicated Internet connection, then buy it from someone who has the redundancy built into their network _AND_ transit agreements.
If any regulation happens, it shouldn't be to interfere with the business arrangements between Tier 1 providers, it should probably be in the form of a waiver or notice to consumers of single-homed transit.
The problem I've noticed is that most consumers don't seem to realize the redundancy lost in single-homed transit. DIA is DIA they think. Even after the recent de-peering event, many are more confused than before because of all the misinformation.
Like the previous poster said, any important applications or networks should be multi-homed.
A couple solutions that would have avoided outage:
Single link without BGP:
Your organization could have purchased its DIA from an ISP that was multi-homed.
Dual links with BGP:
Your organization could have purchased a small amount of DIA (relative to your main pipe) from another provider, weighted/prefixed it less desirable than your primary connectivity, and not lost connectivity to L3/Cogent. You could have possibly even worked a deal with your vendor because of its use as last-resort/emergency connectivity.
I thought the same thing until I RTFA. It's the submitter that should be plonked for the misleading headline.
It's not about storing your VM's disk image on an iPod. They just happened to use an iPod as the portable storage device -- probably because it's the most common, compact, portable storage device with large capacity. i.e. people carry these things on their person, compared to other drives of their size.
They are researching the idea of taking your computing environment with you wherever you go, and productizing it.
Not a new idea, but it's interesting to hear that someone like IBM is researching it.
If you're a CLEC, you do have access to such things under UNE provisions, however the FCC has been meddling in that too.
This probably won't be the end of third-party DSL, just the end of CHEAP third-party DSL.
CLECs can still co-locate their DSLAMs in incumbent COs and lease last-mile loops to their customers, and provide their own DSL.
Smaller ISPs, like VISI which the grandparent mentions, will be greatly affected. Right now they are re-selling the Qwest/Frontier DSL product offerings. If this is re-classified by the FCC, Qwest and Frontier will cut them out and their DSL business will evaporate overnight.
This is a shame because, as many of you probably know, smaller ISPs are great for support and customized solutions for SMB and home customers.
Earthlink and Speakeasy could concievably offer their own DSL product as a CLEC, if that's not what they're already doing anyway.
500lbs is hardly anything considering all the geeks they have working for them. Or is that just between sergey and larry?
I'm only commenting on the subject of this article, that the FCC may force VoIP providers to provide location identification information.
:)
There are flaws with every idea, but GPS seems like a natural one since it's already used for the same purpose in newer cell phones, another FCC mandate that was imposed on the cell phone industry. The cell phone industry hasn't gone away because of it.
GPS would probably be more controversial than Intel's processor ID, might have signal reception problems, and might add a few dollars to the cost; but it might be exactly what VoIP vendors need to comply with FCC regulations. And it might not.
Not true. Text from my Sanyo telephone:
h tml)
"Turning location on will allow the network to detect your position, making some Sprint applications easier to use. Turning location off will hide your location from everyone except 911. Ever if location is turned on in this handset, no service may use your location without your express permission."
and an interesting tidbit I found on google (url http://clinton4.nara.gov/WH/EOP/OSTP/html/0053_4.
" Enhanced-911: The FCC will soon require that all new cellular phones be equipped with more accurate location determination technology to improve responses to emergency 911 calls. Removing SA will boost the accuracy of GPS to such a degree that it could become the method of choice for implementing the 911 requirement. A GPS-based solution might be simpler and more economical than alternative techniques such as radio tower triangulation, leading to lower consumer costs."
As far as time synchronization, I'm ignorant to modern standards, but I do recall a company that sold NTP servers that synchronized with cellular towers using CDMA vs. GPS, which indicates that cell phones do this as well. It's quite possible that the GPS enabled ones use GPS instead.
If the FCC requires them to do something, then they'll have to either conform or fight the FCC.
If major cell phone manufacturers are doing this already, it doesn't seem like much of an obstacle in the long term for commercial VoIP vendors to issue one with their service, especially if it helps them avoid being sued by its users or penalized by the FCC.
With the universal adoption of GPS, it wouldn't be hard to put a GPS receiver on a USB key-fob and relay the information in some standardized fashion.
;)
It's being bundled into cell phones these days for the same purpose.
Just don't bundle it into the computer itself, or the conspiracy theorists may become the conspiracy realists.
Glad to be of service.
It would be nice if EVERYone could moderate the actual stories so bunk like this would never show up on the front page.
... and?
FYI- If your PC had the correct time, it would match exactly.
Enterprise computing. There's something to be said about the vendor of your server being the same vendor as your operating system, not even accounting for how well it performs.
Don't worry -- your Britney Spears albums will sound virtually the same in 2-bit mono gameboy sound... at least to me.
Sounds like you need a new bank.
Check out:
http://www.yoyoyo.net/mnbanks.jpg
Perhaps it's a bit like "the oracle" in the matrix trilogy. The numbers aren't meant to be taken seriously, just to have an influence of some kind.
Present lack of jobs in the field combined with vast future declines sound like quite the deterrent for a college student that is pursuing the field.
You could roll ham radio into a new bundle called "FreeInternet" and sell it to your average consumer. Let me know how this business model works for you.
Laughable, but this is the type of network you're proposing; but without the operator intelligence to keep the thing from falling in on itself.
Then explain Tiger Woods.
Equifax has their own certificate. They have a certificate signed to them saying that they are an authorized CA. When you install Equifax certs you actually install two certs. You install your site cert signed by Equifax, and you install the Equifax CA cert designating them as a valid CA. This is good since in the past a new CA, like Thawte, would require new web browsers to be distributed with information for that CA included. Old SSL web server implementations, however, don't always support CA certs. The OpenSSL library is one piece of software that doesn't in older versions. Any web servers depending on this would need to be upgraded to use an Equifax cert. This isn't exactly new though.
I have a couple boxes called "Aardvarks."
They store 1.8GB on a standard VHS tape.
You connect the aardvark to your VCR using
RCA cables for video in/out. Then you connect
the unit to your computer using a parallel
cable.
You train the aardvark to control your VCR
by pointing your remote at it and pressing
play when it asks you to do so in setup.
It then writes a file containing the data
it needs to play back for Play. You then
point the aardvark at your VCR so it can
control it.
It's a nifty little device that stored a
huge amount of data (at that time.) It did
have one problem though. It would over-estimate
the amount of time required for a VHS tape to
rewind when it would go to do a verify, etc.
It would end up rewinding the tape in 2 minutes
and then calculating that it would take about 16
hours or so. Pretty annoying.
The guy that made these things pretty much
dropped off the face of the earth from what
I can tell.
Another design flaw is that the device has
this scary screen where you can see
how close you're coming to not being able
to restore your data. It shows you when it
uses error correction code, and it uses it
QUITE often.