I might suggest NetSwitcher for your various networking issues. It allows you to instantly switch network settings without a reboot and without reconfiguring every single little setting.
I have used it for my notebook for well over a year now and it works like a charm.
Nice on-line FAQ for TCPA/Palladium
on
Coursey on Palladium
·
· Score: 5, Informative
Snipped from an e-mail at work.....
TCPA / Palladium Frequently Asked Questions
Version 0.1 26 June 2002
Ross Anderson
1. What are TCPA and Palladium?
TCPA stands for the Trusted Computing Platform Alliance (TCPA), an initiative
led by Intel. Their website is here. Their stated goal is `a new computing
platform for the next century that will provide for improved trust in the PC
platform.' Palladium appears to be a Microsoft version which will be rolled out
in future versions of Windows, will build on TCPA hardware, and will add some
extra features. The Palladium announcement appears to have been provoked by a
paper I presented on the security issues relating to open source and free
software at a conference on Open Source Software Economics in Toulouse on the
20th June. This paper criticised TCPA as anticompetitive. This has been amply
confirmed by new revelations over the past few days.
Yeah, but let's think about that for a second. BNETD is open source, they add in a CD check. I want to play my pirated game, hmmmm, edit *snip* recompile and hot damn, I'm ready to go, all the features, none of the pain. I am gathering that is what you mean by the no win situation.
If I was Blizzard, why would I ever want to give up the CD-checking code? How would they invalidate CD Keys for the pirated/warez versions if now the server does local checking for validation of the CD keys? The logistics of even contemplating such an update would be a nightmare.
The only thing I could even begin to see is a simple packet forwarding mechanism to send the CD Key to Blizzard's servers and then get a response. It will never happen since you still have the problem of BNETD being open source. *snip* No CD-Key check and voila, suck it down evil Blizzard corporate bastards for not letting me play my pirated game!
Iowa State has a similar deal with the general proximity of AmesLab. Basically whenever AmesLab upgrades, ISU gets the left over. The Internet2 connection is quite nice and the amusing part is that I could get a better connection to Europe than I could to quite a few of the US sites (i.e. Sweden, Norway, Finland). Not quite on the main connection but I have rarely ever have had trouble. I have more trouble with the 10 Mb/s Ethernet in the lab than I do with the outgoing speed. Too bad the Sun machine didn't have a 10/100 card on it *sigh*
ISU has recently been playing with bandwidth limiting with their Cisco routers. Initially, they had a setup where if you violated over 500 MB/day, you were cutoff from Internet access. The problem was that when Nimbda hit, it shut off a large number of computers and hence bogged down tech support. During the spring, they swapped over to a system whereby you get progressively throttled down to a lower and lower connection after passing the limit for a day with the lower limit being 64 kb/s. Once the day rolls around, you are back up to full capacity.
It seemed like an alright tradeoff although I can't really comment as most of my research goes through Internet2 and is immune to the B/W capping by virtue of being in a research office.
MBone is not specifically dedicated to multicasting. MBone just refers to the fact that the routers are multicast enabled. It is just laid on top of Internet2 .
The MBone FAQ can be found here. The page is a bit old but the information is pretty much correct.
Re-designing IP is more trouble than it is worth. First off, it would require deployment everywhere. So either 1) you upgrade every router, computer, etc. along the paths that need to use it or 2) you end up doing tunneling across IP anyway. Second, it works (or at least mostly works:) and provided everybody employs some sort of congestion control, it works quite nicely.
The core problem is just that you have to make everybody play nice in the network which is what the IETF is trying to do. At the same time, you don't need the overhead of TCP (sending/resending lost/late packets). There has already been quite a bit of work on making UDP-based protocols that are TCP-friendly. The problem here is just choosing what attributes to use and what the messages going back and forth should be.
Don't forget that anyone can participate in the IETF working groups. All you have to do is subscribe to the mailing list of the SIP working group and you can add to the discussion.
Slashdot Mirror
I might suggest NetSwitcher for your various networking issues. It allows you to instantly switch network settings without a reboot and without reconfiguring every single little setting.
I have used it for my notebook for well over a year now and it works like a charm.
TCPA / Palladium Frequently Asked Questions
Version 0.1 26 June 2002
Ross Anderson
1. What are TCPA and Palladium?
TCPA stands for the Trusted Computing Platform Alliance (TCPA), an initiative led by Intel. Their website is here. Their stated goal is `a new computing platform for the next century that will provide for improved trust in the PC platform.' Palladium appears to be a Microsoft version which will be rolled out in future versions of Windows, will build on TCPA hardware, and will add some extra features. The Palladium announcement appears to have been provoked by a paper I presented on the security issues relating to open source and free software at a conference on Open Source Software Economics in Toulouse on the 20th June. This paper criticised TCPA as anticompetitive. This has been amply confirmed by new revelations over the past few days.
For the rest:
TCPA/Palladium FAQ
If I was Blizzard, why would I ever want to give up the CD-checking code? How would they invalidate CD Keys for the pirated/warez versions if now the server does local checking for validation of the CD keys? The logistics of even contemplating such an update would be a nightmare.
The only thing I could even begin to see is a simple packet forwarding mechanism to send the CD Key to Blizzard's servers and then get a response. It will never happen since you still have the problem of BNETD being open source. *snip* No CD-Key check and voila, suck it down evil Blizzard corporate bastards for not letting me play my pirated game!
Maybe they can come up with nanobots for the Slashdot editors that automatically proofread all news submissions?
Eheheheheh, the smartass drive was running strong today....
Iowa State has a similar deal with the general proximity of AmesLab. Basically whenever AmesLab upgrades, ISU gets the left over. The Internet2 connection is quite nice and the amusing part is that I could get a better connection to Europe than I could to quite a few of the US sites (i.e. Sweden, Norway, Finland). Not quite on the main connection but I have rarely ever have had trouble. I have more trouble with the 10 Mb/s Ethernet in the lab than I do with the outgoing speed. Too bad the Sun machine didn't have a 10/100 card on it *sigh*
ISU has recently been playing with bandwidth limiting with their Cisco routers. Initially, they had a setup where if you violated over 500 MB/day, you were cutoff from Internet access. The problem was that when Nimbda hit, it shut off a large number of computers and hence bogged down tech support. During the spring, they swapped over to a system whereby you get progressively throttled down to a lower and lower connection after passing the limit for a day with the lower limit being 64 kb/s. Once the day rolls around, you are back up to full capacity.
It seemed like an alright tradeoff although I can't really comment as most of my research goes through Internet2 and is immune to the B/W capping by virtue of being in a research office.
To quote my conversation with my roommate who wished to reproduce the results of his experiment one of the first time this showed up on Slashdot.
Me: So what are you going to do after you are done, i.e. made the Plasmoid Fireball?
The Roommate: We'll just open the door and let it go free like nature intended.
Eheheheh.
MBone is not specifically dedicated to multicasting. MBone just refers to the fact that the routers are multicast enabled. It is just laid on top of Internet2 .
:) and provided everybody employs some sort of congestion control, it works quite nicely.
The MBone FAQ can be found here. The page is a bit old but the information is pretty much correct.
Re-designing IP is more trouble than it is worth. First off, it would require deployment everywhere. So either 1) you upgrade every router, computer, etc. along the paths that need to use it or 2) you end up doing tunneling across IP anyway. Second, it works (or at least mostly works
The core problem is just that you have to make everybody play nice in the network which is what the IETF is trying to do. At the same time, you don't need the overhead of TCP (sending/resending lost/late packets). There has already been quite a bit of work on making UDP-based protocols that are TCP-friendly. The problem here is just choosing what attributes to use and what the messages going back and forth should be.
Don't forget that anyone can participate in the IETF working groups. All you have to do is subscribe to the mailing list of the SIP working group and you can add to the discussion.