If your general purpose registers are 32 bits (which is the definition of a 32-bit CPU) and addresses are 64 bits, where do you store the pointers? That's why in most recent chips, pointers are the same size as the integer registers.
"IPv6 encodes IP header options in a way that streamlines the forwarding process. Optional IPv6 header information is conveyed in independent "extension headers" located after the IPv6 header and before the transport-layer header in each packet. Most IPv6 extension headers are not examined or processed by intermediate nodes (in contrast with IPv4). This enables a big improvement in the deployability of optional IPv6 features, compared to IPv4 where IP options typically cause a major performance loss for the packet at every intermediate router."
And I quote: "ARIN will not collect subscription fees for those current ARIN IPv4 subscribers who request and qualify for IPv6 address space.... Those IPv4 subscribers who have already paid fees for IPv6 address space are eligible for a refund of those fees."
Namely, every subscriber, be it a corporation or a household, gets a/48.
That might be how it's supposed to be used, but that has little effect on how ISPs will actually configure their networks. What if an ISP defines all their customers to be part of one/64 "subnet" (which might even be defensible since some broadband equipment is based on bridging) and thus assigns each customer only one address?
It's too bad this article didn't mention that you do not need to wait for your ISP; you can start using IPv6 today with 6to4. Slashdot ran a story about how to configure 6to4 under BSD, and here are the instructions for Linux.
I know someone is going to mention that freenet6 or the 6bone is also easy to use, but they're much less efficient than 6to4.
True capabilities (as found in EROS or E) are completely different, more powerful, and older than the stuff that came out of the POSIX committee; it's unfortunate to see yet another article which confuses this issue.
The upcoming NFSv4 standard will support strong authentication, encryption, and server-side access control. A group at CITI is working on a Linux implementation of NFSv4.
You are paying your ISP to move bits around; that money isn't intended to pay for content.
However, I think micropayment systems that allow charges to be added to your ISP bill might have a better chance of survival because the ISP already has a billing relationship with the user.
Where's the documentation for the DCOP interfaces that apps support? I looked on developer.kde.org and found docs on how to use DCOP, but nothing about what messages are understood by different apps.
To mark a file as freely distributable, an artist would have to sign it with a digital certificate and indicate what kinds of right he would like to grant.
OK, I'll be sure to sign all the MP3s I have as freely distributable. Of course, I didn't actually create those MP3s, but how is Napster supposed to know?
There are some problems, like DV format is not error-free. I don't know how they would recover from dropping blocks of data because of the wrinkled tape
Re:But IPv4 is more profitable!
on
Quake on IPv6
·
· Score: 2
They will probably have to. Right now, ISPs pay ICANN (through some intermediaries) for IPv4 addresses, so they pass those costs on to customers. I predict that IPv6 addresses will be so cheap that some ISPs will start giving their customers as many as they want, and the ISPs that try to ration v6 addresses will lose business.
XScale isn't just an embedded CPU; its predecessor StrongARM was used in the NetWinder desktop machine a few years back. Now that XScale is up to ~700 MHz we might see an ARM comeback in non-embedded systems.
Slashdot Mirror
http://www.fibercycle.com/news_and_events/archives _pr/pr_010221.html
If your general purpose registers are 32 bits (which is the definition of a 32-bit CPU) and addresses are 64 bits, where do you store the pointers? That's why in most recent chips, pointers are the same size as the integer registers.
What you're saying is opposite from this part of The Case for IPv6:
"IPv6 encodes IP header options in a way that streamlines the forwarding process. Optional IPv6 header information is conveyed in independent "extension headers" located after the IPv6 header and before the transport-layer header in each packet. Most IPv6 extension headers are not examined or processed by intermediate nodes (in contrast with IPv4). This enables a big improvement in the deployability of optional IPv6 features, compared to IPv4 where IP options typically cause a major performance loss for the packet at every intermediate router."
And I quote: "ARIN will not collect subscription fees for those current ARIN IPv4 subscribers who request and qualify for IPv6 address space. ... Those IPv4 subscribers who have already paid fees for IPv6 address space are eligible for a refund of those fees."
No, BeOS doesn't do that. It does a full boot every time.
However, EROS works just like you've described.
Namely, every subscriber, be it a corporation or a household, gets a /48.
/64 "subnet" (which might even be defensible since some broadband equipment is based on bridging) and thus assigns each customer only one address?
That might be how it's supposed to be used, but that has little effect on how ISPs will actually configure their networks. What if an ISP defines all their customers to be part of one
It's too bad this article didn't mention that you do not need to wait for your ISP; you can start using IPv6 today with 6to4. Slashdot ran a story about how to configure 6to4 under BSD, and here are the instructions for Linux.
I know someone is going to mention that freenet6 or the 6bone is also easy to use, but they're much less efficient than 6to4.
I'm sure some Slashdotters would find that aspect pretty useful. :-)
True capabilities (as found in EROS or E) are completely different, more powerful, and older than the stuff that came out of the POSIX committee; it's unfortunate to see yet another article which confuses this issue.
The upcoming NFSv4 standard will support strong authentication, encryption, and server-side access control. A group at CITI is working on a Linux implementation of NFSv4.
If you are sharing files using Napster, then you consented to let other people know what you are sharing.
You are paying your ISP to move bits around; that money isn't intended to pay for content.
However, I think micropayment systems that allow charges to be added to your ISP bill might have a better chance of survival because the ISP already has a billing relationship with the user.
The above post is not informative; we're talking about the QuickTime API here, which is codec-independent.
Or at least that's what The Register says. :-)
I read that Google only bought the archives from Deja, but not their code or hardware. So where is that code now?
Where's the documentation for the DCOP interfaces that apps support? I looked on developer.kde.org and found docs on how to use DCOP, but nothing about what messages are understood by different apps.
There are several XML compression formats out there already; it's too bad people haven't decided on one, though.
To mark a file as freely distributable, an artist would have to sign it with a digital certificate and indicate what kinds of right he would like to grant.
OK, I'll be sure to sign all the MP3s I have as freely distributable. Of course, I didn't actually create those MP3s, but how is Napster supposed to know?
Escient makes one.
There are some problems, like DV format is not error-free. I don't know how they would recover from dropping blocks of data because of the wrinkled tape
MPEG-2 can also tolerate lost data.
Yes, what's your point? That's a big honkin' die.
They will probably have to. Right now, ISPs pay ICANN (through some intermediaries) for IPv4 addresses, so they pass those costs on to customers. I predict that IPv6 addresses will be so cheap that some ISPs will start giving their customers as many as they want, and the ISPs that try to ration v6 addresses will lose business.
I don't understand why people are still using 6bone tunnels when 6to4 is easier and more efficient.
The article says WEP can be cracked.
XScale isn't just an embedded CPU; its predecessor StrongARM was used in the NetWinder desktop machine a few years back. Now that XScale is up to ~700 MHz we might see an ARM comeback in non-embedded systems.