Shouldnt an Elvis song's copyright duration be determined by the laws in the country where the work was recorded?
From my knowledge of copyright law, the duration of the copyright that is effective worldwide is specified by the laws in which the copyright was obtained. Thus, this song will expire when US law says it expires, not UK law.
The "Audiophile" business is chock full of snake oil, even moreso than many others. $1000/ft "de-ionized oxygen-free" cables? LOL.
Very true. I completely lost all faith in the audiophile bunch after seeing some of the crap they spout. Especially stuff like this
that actually makes the claim that different digital audio fibre optic cables somehow sound different.
BGP packets unless multihop should have a TTL of exactly 1 and come through a point to point interface.
The current thinking nowadays is that point to point BGP sessions (EBGP) should actually have their TTL set to 255, and the receiving router set to drop bgp packets with a ttl lower than what the originating router sends.
This eliminates pretty much any BGP attack as it's impossible to spoof that high a TTL (every hop in the path drops the TTL by one).
TTLs of one also don't work very well with IBGP sessions.
Of course, setting ingress filters will do wonders at preventing any attacks as a main defence.
I did exactly the same, beginning from about four years ago. I moved from Australia to the Netherlands and use it to keep in touch with Australian radio shows. It works rather well and I can listen to any FM station available in Sydney.
And mine is even simpler. Use the Mozilla keywords feature, and all you have to do is to enter 'g ' in the location bar and you have your results. Saves loading a whole page.
In the Netherlands we are already in an ADSL price war. Providers are offering ADSL connections from around EUR15/month and regularly increase the speeds. In january it's going to reach 2M/320k for around EUR35/month. Most of theses plans are unmetered, and you get a fixed IP address.
For the consumer this is great - lots of choices and decent service.
This sounds a lot like the way that nanobots are assembled in the recent novel Prey.
Anyone interested in nano technology will find this a fascinating novel. A lot of the novel describes some of the science behind nano, and as well as a gripping story, you can actually learn a thing or two.
A lot of the reason why IPv4 won't run out is due to the fact that it's so hard to get any space. With extremely strict assignment rules, of course it will be a while before they are all used up.
Unfortunately, this just means that the ugly hack known as NAT will continue to be used, breaking many applications and protocols, not to mention external reachability of many devices. If there was reachability to all devices, the net would be a lot more useful for controlling embedded devices, but then we'd quickly use up a lot of space more quickly.
Address space is only a part of the reason to move to IPv6. There are plenty of other features which should be reason enough to move over:
- Auto address configuration - No more LAN renumbering/resizing games - Built in tunnelling functions for portable devices - Simpler address hierarchy - Address renumbering is much simpler, and will soon be do-able automatically - Standardised IPSec functionality in all devices
IPv4 will not run out with the current allocation guidelines - but it will continue to have incredibly restricted functionality due to NAT.
Will they be able to propel craft all the way across the oceans by using a relay/tag-team system consisting of sharks with fricking laser beams attached to their fricking heads?
Can you memorize FEDC:BA98:7654:3210:FEDC:BA98:7654:3210?
Why would I want to?
1. This is not an IPv6 address one will see often.
2. Most allocated IP addresses will use the prefix 2001::/16
3. DNS will eliminate most things you have to remember
4. You can manually configure addresses that you want to be remembered. The address 2001:bc4:face::1 is perfectly valid if you wish to use it.
Maintaining easy to remember addresses is not a reason to use a smaller address space. If that was the case, we'd still be dialling with 5 digits, and each business would only have one number with a switchboard person routing external calls.
Backbones should switch over first, proxying ipv4 over ipv6, then propogate downwards.
Please do a bit of research on the interoperability of Ipv6 and Ipv4. A large proportion of the Ipv6 effort has been on efforts to ensure amooth migration and interoperability. You dont need an ultimatum, just let both work then gradually turn off Ipv4-only services. No one will notice if its done correctly.
As for the OS and device makers, simply make dhcp check ipv6 first, then fallback to ipv4. That'll be transparent for all the chuckleheads who would ignore the "switch" thing.
Fyi...
All dual stack implementations today first attempt to use IPv6 versions of protocols, and only if that fails do they resort to Ipv4. All of my boxen for example will do the following:
1. Do DNS lookup
2. Get IPv6 address and IPv4 address for hostname.
3. Attempt to connect to IPv6 address first.
4. Otherwise try Ipv4 address
Any correctly written application will automatically use IPv4 and IPv6 without special intervention. The IPv6 bind() call binds to both v4 and v6, for example.
Cisco is working on hardware support for IPv6 for most platforms. As it becomes more widespread, they will develop full hardware routing for all devices. It's a chicken and egg problem, but a lot of people have decided to start somewhere.From what I've seen, there has been more interest in getting IPv6 running in the last 6 months than there ever has been.
2. There are too many addresses.
NAT doesnt work when you have devices that need to be addresses externally. What NAT-Portfw port is your device 'X' listening on? Hmm?? IPv6 is designed such that address space is _not_ a resource, but a method of being able to access _any_ device attached to the net. I dont _want_ to have to explain to someone why I want an address. I just want the thing to work.
Another benefit is address management. With Ipv6, the days of deciding how big your subnets are will be numbered. Every subnet has trillions of addresses. Nowadays you have to wonder whether your subnet needs a/24,/25,/26, etc. Yuck! With Ipv6, you never have to worry - there's enough space in _one_ subnet to scale indefintely. No more subnet-resizing games.
3. IPv6 addresses are too large.
Ipv6 is designed to be very hierarchial. The top organisations get/32s, the next one down get smaller subnets (/48), etc. The routing table will no longer be populate with tiny piddly subnets (eg/24s today). Go into an aggregate and things will behave.
And as for the routing table size, modern routers have oodles of memory, on average 512Mb RAM. A full BGP table of 130k routes takes up around 64Mb of that at most. IPv6 will have better aggregation, so smaller numbers of routes, and my the time it gets large, standard memory on routers will not have a problem storing the table.
4. The IPv6 header is too large.
3.4% longer if you use a 576 MTU. Use a sensible 1500 byte MTU and your downloads will not be much slower at all. Anyway, the elimination of fragmenting, the simplification of subnetting, and the many other benefits will far outweigh your 20-byte concerns.
See my other post on security too (no more network host scans).
IPv6 is not ready to fully replace IPv4 overnight now, sure. But it's gaining a heck of a lot of momentum and by the time your concerns will actually become enough to be worried about, they will have been either solved or rendered moot.
Another nice thing about IPv6 (at least now), is that it's a return to the good ol' days of the net when everyone was friendly with each other. 15 years ago you askes someone for addresses or transit and you were quite likely to get it for next to nothing. Ask
for addresses or transit/peering with IPv6 today - you're likely to get it, with a friendly response. it's a great community.
IPv6 has a nice advantage over IPv4 that I havent seen mentioned many places before. This is one on security.
One of the major contributing factors to problems such as spammers and crackers is that it's so darn easy to scan subnets in IPv4 for open hosts. It can take under a minute to scan a complete/24 for hosts with open ports.
Now with IPv6 this situation is different. Each subnet has 64 bits of address space. That is, 18446744073709551616 IP addresses per subnet. Now, if someone could portscan at the rate of 100 addresses per second (pretty impressive), then each subnet would take 5.8 billion years[0] to scan for hosts. For one subnet! And to put this in a wider context, each site in ipv6 has 65,000 subnets. Effectively making network scans a thing of the past, and massively increasing security of the 'net.
Of course, one can still scan known hosts (eg from web server logs), but doing that is a heck of a lot harder - you'd need to get them in the first place.
[0] Said with appropriate finger quotes.
To those who say we have enough IPv4 space
on
The Impending IP Crisis
·
· Score: 5, Insightful
There are people who have stated that we've only
used up around 60% of the IPv4 space and we have plenty
more to last for a long time yet.
I want to see IP as more of a general resource like electricity or water. You just plug anything into your wires/pipes, and it gets full access to the resource. Want more things getting water such as a washing machine? Then just run another pipe to it and it's got access. The current hacks of NAT are equivalent to only being allowed to install one tap in your house, and "proxying" the rest with buckets. Why cant it be like a water or electricity supply?
Those saying 'we have plenty of space left' obviously dont realise that the reason for this is that the current allocation policies for IPv4 make it impossible to get space for arbitrary devices. Yes, if you only allocate one IP address per gateway, of course you wont run out for a while. But that then mandates the use of ugly hacks such as NAT. A single tap per house/organisation.
To make full use of the potential of the net, one must be able to freely allocate IP addresses to any devices that want them, no matter how trivial it may seem today. Back when IP was invented, it was never in anyones wildest dreams that there would be an address shortage. There were barely a hundred hosts yet 32 bits of space. Look at what's happened in 20-odd years!
This is just a waste of effort. Virtually all of the free email providers insert the IP address of the sending host in the header. Just follow the white rabbit (IP address) and you will eventually get to the owner.
Any criminal who are serious are going to be a bit more clever - open proxies, fake credit cards, etc to hide their identities. Or just a free email provider in a country that is out of the jurisdiction of the AFP.
Forcing people to pay for email just wont work. People have become used to having free email addresses, and there *will* be ways for people to still get it. Sure, MS may charge, as may yahoo, but many other providers wont.
I've also hacked my own copy of icecast2 to accept connections over IPv6, and now listen to TripleJ and various other Sydney-based radio stations regularly online.
Just playing my part to support the adoption of IPv6..
And just wait till you hear the Dutch. It seems that if any modern language is about to vanish, it's Dutch.
Virtually every conversation you hear the Dutch speak has words and phrases borrowed from English. There are almost no technical dutch terms - all are english. Occasionally a farewell will have a literal 'see you later' thrown in. Quotes from English language TV/movies are a favourite.
So I think french and german are quite safe for a long time - it's the minor european languages which are about to disappear.
Films classified by the Brits, are only for showings in England. Each country in Europe has its own classification.
In Holland, TMR is classified as suitable for anyone 12 years and over due to violence. It's probably the same with many EU countries, as over
here people are quite liberal with their policies.
So...
Europe: Neo kicks the crap out of someone and then says: "Oh fuck! Zion again. It's such a shitty place". Rated "12+" because there's some violence.
The correct precedure for an update should be at minimum:
Lightbulb above head in the weekend (ding!)
Over the following week, research the change, check impact on existing systems, come up with a maintanance strategy, document it, inform people, test it in a lab, plan the implementation, develop a rollback procedure.
Implement change early the following week - never on a Friday, preferably not on Thursday.
Watch throughout the week for problems.
Anything less and you dont deserve to be in that position.
Slashdot Mirror
Shouldnt an Elvis song's copyright duration be determined by the laws in the country where the work was recorded?
From my knowledge of copyright law, the duration of the copyright that is effective worldwide is specified by the laws in which the copyright was obtained. Thus, this song will expire when US law says it expires, not UK law.
Or is someone able to clarify this?
In Soviet Russia^W^W Mexico, the spooks get tracked by YOU!
Very true. I completely lost all faith in the audiophile bunch after seeing some of the crap they spout. Especially stuff like this that actually makes the claim that different digital audio fibre optic cables somehow sound different.
The current thinking nowadays is that point to point BGP sessions (EBGP) should actually have their TTL set to 255, and the receiving router set to drop bgp packets with a ttl lower than what the originating router sends.
This eliminates pretty much any BGP attack as it's impossible to spoof that high a TTL (every hop in the path drops the TTL by one).
TTLs of one also don't work very well with IBGP sessions.
Of course, setting ingress filters will do wonders at preventing any attacks as a main defence.
I did exactly the same, beginning from about four years ago. I moved from Australia to the Netherlands and use it to keep in touch with Australian radio shows. It works rather well and I can listen to any FM station available in Sydney.
I described this system on my weblog.
See how to do it.
The camera used is a still camera and the movie mode only takes 15 second MPEGs. I'm wondering how they can reliably grab a four digit PIN with this?
XBlast!
In the Netherlands we are already in an ADSL price war. Providers are offering ADSL connections from around EUR15/month and regularly increase the speeds. In january it's going to reach 2M/320k for around EUR35/month. Most of theses plans are unmetered, and you get a fixed IP address.
For the consumer this is great - lots of choices and decent service.
This sounds a lot like the way that nanobots are assembled in the recent novel Prey.
Anyone interested in nano technology will find this a fascinating novel. A lot of the novel describes some of the science behind nano, and as well as a gripping story, you can actually learn a thing or two.
A lot of the reason why IPv4 won't run out is due to the fact that it's so hard to get any space. With extremely strict assignment rules, of course it will be a while before they are all used up.
Unfortunately, this just means that the ugly hack known as NAT will continue to be used, breaking many applications and protocols, not to mention external reachability of many devices. If there was reachability to all devices, the net would be a lot more useful for controlling embedded devices, but then we'd quickly use up a lot of space more quickly.
Address space is only a part of the reason to move to IPv6. There are plenty of other features which should be reason enough to move over:
- Auto address configuration
- No more LAN renumbering/resizing games
- Built in tunnelling functions for portable devices
- Simpler address hierarchy
- Address renumbering is much simpler, and will soon be do-able automatically
- Standardised IPSec functionality in all devices
IPv4 will not run out with the current allocation guidelines - but it will continue to have incredibly restricted functionality due to NAT.
Will they be able to propel craft all the way across the oceans by using a relay/tag-team system consisting of sharks with fricking laser beams attached to their fricking heads?
Why do everyone hate the telcos?
I've never had bad phone service.It's always worked.
Oh! Someone from outside the US!
Can you memorize FEDC:BA98:7654:3210:FEDC:BA98:7654:3210?
Why would I want to?
1. This is not an IPv6 address one will see often.
2. Most allocated IP addresses will use the prefix 2001::/16
3. DNS will eliminate most things you have to remember
4. You can manually configure addresses that you want to be remembered. The address 2001:bc4:face::1 is perfectly valid if you wish to use it.
Maintaining easy to remember addresses is not a reason to use a smaller address space. If that was the case, we'd still be dialling with 5 digits, and each business would only have one number with a switchboard person routing external calls.
Backbones should switch over first, proxying ipv4 over ipv6, then propogate downwards.
Please do a bit of research on the interoperability of Ipv6 and Ipv4. A large proportion of the Ipv6 effort has been on efforts to ensure amooth migration and interoperability. You dont need an ultimatum, just let both work then gradually turn off Ipv4-only services. No one will notice if its done correctly.
As for the OS and device makers, simply make dhcp check ipv6 first, then fallback to ipv4. That'll be transparent for all the chuckleheads who would ignore the "switch" thing.
Fyi...
All dual stack implementations today first attempt to use IPv6 versions of protocols, and only if that fails do they resort to Ipv4. All of my boxen for example will do the following:
1. Do DNS lookup
2. Get IPv6 address and IPv4 address for hostname.
3. Attempt to connect to IPv6 address first.
4. Otherwise try Ipv4 address
Any correctly written application will automatically use IPv4 and IPv6 without special intervention. The IPv6 bind() call binds to both v4 and v6, for example.
So, your concerns have already been addressed. :)
1. Cisco routers suck at IPv6.
Cisco is working on hardware support for IPv6 for most platforms. As it becomes more widespread, they will develop full hardware routing for all devices. It's a chicken and egg problem, but a lot of people have decided to start somewhere.From what I've seen, there has been more interest in getting IPv6 running in the last 6 months than there ever has been.
2. There are too many addresses.
NAT doesnt work when you have devices that need to be addresses externally. What NAT-Portfw port is your device 'X' listening on? Hmm?? IPv6 is designed such that address space is _not_ a resource, but a method of being able to access _any_ device attached to the net. I dont _want_ to have to explain to someone why I want an address. I just want the thing to work. /24, /25, /26, etc. Yuck! With Ipv6, you never have to worry - there's enough space in _one_ subnet to scale indefintely. No more subnet-resizing games.
Another benefit is address management. With Ipv6, the days of deciding how big your subnets are will be numbered. Every subnet has trillions of addresses. Nowadays you have to wonder whether your subnet needs a
3. IPv6 addresses are too large.
Ipv6 is designed to be very hierarchial. The top organisations get /32s, the next one down get smaller subnets (/48), etc. The routing table will no longer be populate with tiny piddly subnets (eg /24s today). Go into an aggregate and things will behave.
And as for the routing table size, modern routers have oodles of memory, on average 512Mb RAM. A full BGP table of 130k routes takes up around 64Mb of that at most. IPv6 will have better aggregation, so smaller numbers of routes, and my the time it gets large, standard memory on routers will not have a problem storing the table.
4. The IPv6 header is too large.
3.4% longer if you use a 576 MTU. Use a sensible 1500 byte MTU and your downloads will not be much slower at all. Anyway, the elimination of fragmenting, the simplification of subnetting, and the many other benefits will far outweigh your 20-byte concerns. See my other post on security too (no more network host scans).
IPv6 is not ready to fully replace IPv4 overnight now, sure. But it's gaining a heck of a lot of momentum and by the time your concerns will actually become enough to be worried about, they will have been either solved or rendered moot.
Another nice thing about IPv6 (at least now), is that it's a return to the good ol' days of the net when everyone was friendly with each other. 15 years ago you askes someone for addresses or transit and you were quite likely to get it for next to nothing. Ask for addresses or transit/peering with IPv6 today - you're likely to get it, with a friendly response. it's a great community.
One of the major contributing factors to problems such as spammers and crackers is that it's so darn easy to scan subnets in IPv4 for open hosts. It can take under a minute to scan a complete /24 for hosts with open ports.
Now with IPv6 this situation is different. Each subnet has 64 bits of address space. That is, 18446744073709551616 IP addresses per subnet. Now, if someone could portscan at the rate of 100 addresses per second (pretty impressive), then each subnet would take 5.8 billion years[0] to scan for hosts. For one subnet! And to put this in a wider context, each site in ipv6 has 65,000 subnets. Effectively making network scans a thing of the past, and massively increasing security of the 'net.
Of course, one can still scan known hosts (eg from web server logs), but doing that is a heck of a lot harder - you'd need to get them in the first place.
[0] Said with appropriate finger quotes.
I want to see IP as more of a general resource like electricity or water. You just plug anything into your wires/pipes, and it gets full access to the resource. Want more things getting water such as a washing machine? Then just run another pipe to it and it's got access. The current hacks of NAT are equivalent to only being allowed to install one tap in your house, and "proxying" the rest with buckets. Why cant it be like a water or electricity supply?
Those saying 'we have plenty of space left' obviously dont realise that the reason for this is that the current allocation policies for IPv4 make it impossible to get space for arbitrary devices. Yes, if you only allocate one IP address per gateway, of course you wont run out for a while. But that then mandates the use of ugly hacks such as NAT. A single tap per house/organisation.
To make full use of the potential of the net, one must be able to freely allocate IP addresses to any devices that want them, no matter how trivial it may seem today. Back when IP was invented, it was never in anyones wildest dreams that there would be an address shortage. There were barely a hundred hosts yet 32 bits of space. Look at what's happened in 20-odd years!
Lets not make the same mistake today.
This is just a waste of effort. Virtually all of the free email providers insert the IP address of the sending host in the header. Just follow the white rabbit (IP address) and you will eventually get to the owner.
Any criminal who are serious are going to be a bit more clever - open proxies, fake credit cards, etc to hide their identities. Or just a free email provider in a country that is out of the jurisdiction of the AFP.
Forcing people to pay for email just wont work. People have become used to having free email addresses, and there *will* be ways for people to still get it. Sure, MS may charge, as may yahoo, but many other providers wont.
I've also hacked my own copy of icecast2 to accept connections over IPv6, and now listen to TripleJ and various other Sydney-based radio stations regularly online.
:(
Just playing my part to support the adoption of IPv6..
My IPv6 Ogg Vorbis stream keeps me sane!
Or for those without AAAA DNS working:
http://[2001:618:400::cb12:26db]:8000/live.ogg
Slashcode doesnt support IPv6 html links it seems
And just wait till you hear the Dutch. It seems that if any modern language is about to vanish, it's Dutch.
Virtually every conversation you hear the Dutch speak has words and phrases borrowed from English. There are almost no technical dutch terms - all are english. Occasionally a farewell will have a literal 'see you later' thrown in. Quotes from English language TV/movies are a favourite.
So I think french and german are quite safe for a long time - it's the minor european languages which are about to disappear.
Real music pirates use DVD-Arrrrrrrr!
Keywords are a problem for this?? I find it a heck of a lot faster than scrolling down lists...
Create a bookmark with the follwing URL:
http://www.google.com/search?&q=%s
In the bookmarks manager, go to the properties of this bookmark, and set the keyword to 'g'.
All you have to do now for a google search is to type "g [search term]" in the address bar and hit enter. (without quotes)
Plus the keyboard travel for typing "g " is much smaller than for the arrow keys.
Films classified by the Brits, are only for showings in England. Each country in Europe has its own classification.
In Holland, TMR is classified as suitable for anyone 12 years and over due to violence. It's probably the same with many EU countries, as over here people are quite liberal with their policies.
So...
Europe: Neo kicks the crap out of someone and then says: "Oh fuck! Zion again. It's such a shitty place". Rated "12+" because there's some violence.
- Lightbulb above head in the weekend (ding!)
- Over the following week, research the change, check impact on existing systems, come up with a maintanance strategy, document it, inform people, test it in a lab, plan the implementation, develop a rollback procedure.
- Implement change early the following week - never on a Friday, preferably not on Thursday.
- Watch throughout the week for problems.
Anything less and you dont deserve to be in that position.