NYSERNet used to resell Sprintlink service, but that hasn't been the case for a rather long time. At present, the schools in Rochester have connections to multiple commercial ISPs, as well as connections to the NYSERNet research and education backbone. The NYSERNet network connects them to the global R&E infrastructure via Abilene, CA*net 4 and other similar backbones. The NYC dark fiber project is also a NYSERNet activity, but a separate one.
It is perhaps worth pointing out that NYSERNet never actually ran the Sprintlink network nor the Pennsauken NAP, and that providing bandwidth for Quake games probably wasn't at the top of the priority list for your school's network administrators. . .
I'd settle for getting the incoming phone number (caller ID) in Morse. That way I could decide whether to answer or not without having to look at the screen. ..
Yes, but for some reason the SeaPC as discussed in the article reverts to the relatively pedestrian hold-it-in-your-hands technology, rather than the heads-up display and chord controller. Regardless of which one works better, the WetPC is clearly much geekier;)
How long is that beautiful shiny black plastic going to stay shiny? About 15 minutes. And how fast will the pearly white keys get covered with ick? I'm sure it will look nice as long as nobody uses or carries it. . .
You saw it here first:
http://slashdot.org/articles/99/07/17/2312225.shtm l
Actually a somewhat vague article, but it was clear that these are completely unrelated projects; the astronaut assistants will operate inside spacecraft.
I wonder if the NRO would be upset if someone
launched such a nanosat and then wandered over to
one of their spysats and started taking video. . .
Of course, for big satellites you can already get
some idea of what they look like
from the ground, but the nanosat obviously does much, much better.
Voice over IP isn't really mature yet, but there are usable implementations (both commercial and free). The main competing protocols are the Session Initiation Protocol (SIP) created by the IETF, and H.323, created by ISO. SIP is much simpler and easier to understand, but H.323 has a lead in deployment. Take a look at: Internet Telephony for a very good overview of the issues and technology, The Session Initiation Protocol page for SIP info and comparisons with H.323, The OpenH323 Project for a free implementation of H.323, and Vovida for a set of free implementations under development for both protocols. On the commercial side, Computer Telephony magazine has loads of information about VoIP and related topics, including a feature article this month about SIP.
- The ICMP Time Exceeded message contains only the IP header and the first 8 octets of the packet, so the transfer will be very inefficient (perhaps not a problem for some applications, but transferring MP3's 8 bytes at a time would get old pretty quickly).
- Some sites already rate-limit ICMP messages to avoid some kinds of DoS attacks, which although it wouldn't prevent this channel, would restrict the bandwidth still further.
I'm not sure if there is any way around these, but the channel would still be useful for low-bandwidth communication.
The Web100 Project is working on putting automatic TCP tuning into the stack. This will allow a TCP connection to use all of the available bandwidth, without breaking any of the internal algorithms or stomping on other connections. It is already possible to tune most TCP implementations by measuring the bandwidth*delay product and tweaking the socket buffer size; the NLANR TCP Tuning page has instructions.
Slashdot Mirror
NYSERNet used to resell Sprintlink service, but that hasn't been the case for a rather long time. At present, the schools in Rochester have connections to multiple commercial ISPs, as well as connections to the NYSERNet research and education backbone. The NYSERNet network connects them to the global R&E infrastructure via Abilene, CA*net 4 and other similar backbones. The NYC dark fiber project is also a NYSERNet activity, but a separate one.
It is perhaps worth pointing out that NYSERNet never actually ran the Sprintlink network nor the Pennsauken NAP, and that providing bandwidth for Quake games probably wasn't at the top of the priority list for your school's network administrators. . .
I'd settle for getting the incoming phone number (caller ID) in Morse. That way I could decide whether to answer or not without having to look at the screen. . .
Yes, but for some reason the SeaPC as discussed in the article reverts to the relatively pedestrian hold-it-in-your-hands technology, rather than the heads-up display and chord controller. Regardless of which one works better, the WetPC is clearly much geekier ;)
How long is that beautiful shiny black plastic going to stay shiny? About 15 minutes. And how fast will the pearly white keys get covered with ick? I'm sure it will look nice as long as nobody uses or carries it. . .
The referenced article gives few details, but I'm willing to bet that the WetPC beats the SeaPC hands down (literally).
You saw it here first: http://slashdot.org/articles/99/07/17/2312225.shtm l
Actually a somewhat vague article, but it was clear that these are completely unrelated projects; the astronaut assistants will operate inside spacecraft.
I wonder if the NRO would be upset if someone launched such a nanosat and then wandered over to one of their spysats and started taking video. . .
Of course, for big satellites you can already get some idea of what they look like from the ground, but the nanosat obviously does much, much better.
Voice over IP isn't really mature yet, but there are usable implementations (both commercial and free). The main competing protocols are the Session Initiation Protocol (SIP) created by the IETF, and H.323, created by ISO. SIP is much simpler and easier to understand, but H.323 has a lead in deployment.
Take a look at:
Internet Telephony for a very good overview of the issues and technology,
The Session Initiation Protocol page for SIP info and comparisons with H.323,
The OpenH323 Project for a free implementation of H.323, and
Vovida for a set of free implementations under development for both protocols. On the commercial side, Computer Telephony magazine has loads of information about VoIP and related topics, including a feature article this month about SIP.
- The ICMP Time Exceeded message contains only the IP header and the first 8 octets of the packet, so the transfer will be very inefficient (perhaps not a problem for some applications, but transferring MP3's 8 bytes at a time would get old pretty quickly).
- Some sites already rate-limit ICMP messages to avoid some kinds of DoS attacks, which although it wouldn't prevent this channel, would restrict the bandwidth still further.
I'm not sure if there is any way around these, but the channel would still be useful for low-bandwidth communication.
The Web100 Project is working on putting automatic TCP tuning into the stack. This will allow a TCP connection to use all of the available bandwidth, without breaking any of the internal algorithms or stomping on other connections. It is already possible to tune most TCP implementations by measuring the bandwidth*delay product and tweaking the socket buffer size; the NLANR TCP Tuning page has instructions.