BSD has no problems with this kind of use.
To quote the founder of OpenBSD:
But software which OpenBSD uses and redistributes must be free to all (be they people or companies), for any purpose they wish to use it, including modification, use, peeing on, or even integration into baby mulching machines or atomic bombs to be dropped on Australia.
Many ZyXEL CPEs can do IPv6. Check out their NBG4615, which is your typical home wifi/router appliance that supports IPv6. I think all or most of their current ADSL/VDSL CPEs all support IPv6 out of the box too.
Even for a couple of servers that do not have an external firewall filtering packets for my IPv6, there is basically zero packets besides those going to applications hosted on my servers, and they have published DNS records for web and DNS. Some basic PCs I have online see zero packets from random internet hosts on IPv6.
The IPv6 address space is literally too large to crawl within any useful amount of time. If you figure an average LAN will have 18,446,744,073,709,551,616 addresses (a
There will have to be other means to gather active/in-use IP address such as looking at server logs that clients connect to, email headers, DNS records, soliciting traffic from the client machines via some application/trojan/virus, network traffic sniffing, etc. All of these means already exist for IPv4 so there is nothing new there.
The public facing resources of the government agencies need to be IPv6 enabled, not the internal and external workings of the networks within the various organizations. This simply means in most cases, inbound email servers and web servers need to be hosted on machines somewhere in the world that have full IPv6 access, then the respective DNS records need to be in place for said services, which translates to add "AAAA" records. I bet Akamai is loving this mandate because they are a popular choice for government agencies to turn to for IPv6 enabled hosting but Akamai is not the only company that will do IPv6 hosting.
Don't be such a dick. Not everything in the various space programs is strictly for the various space programs.
"This important effort helps advance the knowledge and technologies required to explore space, all while generating the necessary tools that enhance our quality of life on earth."
You're falling into one of the pitfalls of religion/faith: it is not possible for us to comprehend/achieve such lofty goals, therefore don't attempt to. New technologies and science breakthroughs will not only enlighten our lives on Earth but also have potential to greatly expand our travel potential if ideas like quantum entanglement can prove fruitful.
But you're right... its snake oil... fuck all scientists and the human spirit of curiosity and breaking barriers... except Tang, that shit is good.
I sense a bit of sarcasm. When discussing the TSA Freedom Fondle, you need to show more respect. Hey, you blond chick, yes, you with the big frontal lobes... care for a private "security" screening?
The beauty of our society, to disagree completely with reality and yet still benefit from the works of others who do accept the reality and produce advancements in technology and science that can benefit everyone. We allow room for even those that choose to close their eyes and cover their ears.
If real is what you can feel, smell, taste and see, then 'real' is simply electrical signals interpreted by your brain
Does he have a child or wife with with special needs?
Yes, his wife is married to a crazy whiner.
LOL... this is all stupid. Comparing and contrasting the distinctions between two idioti...errr... religions viewpoints is so utterly useless.
PoEoV has been held up in the IETF draft process. The stupid skanks at the ITU-T won't back me until I get a major vendor like Cisco or Juniper involved. But Cisco won't talk to me unless I am willing to sell them my idea so they can name it CiscoVoice-E and Juniper wants to put it in their MX series but have an 18 month screening process before they will even beta it but wont formally adopt it without industry standardization (chicken-or-egg problem, hello!!) Perhaps The Onion will give me some good publicity and get some people interested, they are the ones who introduced me to my current religion after all: Fictionology. Nah nah nah nah nah nah nah nah, BATMAN...
Yes in Minneapolis. The food was good but as a vegetarian the "meat" dish was something I passed on and then I was left hungry at the end. Not complaining though, free food and the presentation very efficiently articulated the overall situation. I wish I had asked a couple more questions that came to mind after I had already left: statusopinion of other non-DNSSEC enhancement technologies like DNSCURVE and secondly Cricket's opinion on DNSSEC proxy tools in general with one example being phreebird by Dan Kaminsky.
Isn't it a bit idiotic to hard code refusal to route addresses reserved for "future use"?
The firmware developers should have expected the "future" would come eventually right?
How should developers have designed the use of that address space? Unicast? Multicast? Anycast? Some-as-yet-unknown-cast? Kind of hard to program that in and for what benefit? Zero return really and one might argue for a net loss as some vendors may have designed its use one way and others may have done something altogether different and incompatible with the first. Then what? Not it's totally screwed up. Not to mention if it's not used but enabled for years and years I bet there would be bugs galore since it would be basically never used by any sizable amount of people. This would only marginally extend the exhaustion time in any case. Would have been better to go with IPv6 as soon as it became official.
Uhhh... we dont use Class C or any "Class" blocks at all anymore. Try
Coincidentally I was just yesterday at a DNSSEC seminar presented by Cricket Liu. While obscenely complicated compared to the more or less basic operation of a non-DNSSEC name server, it is super easy to (and really operationally required IMHO to) automate the entire DNSSEC part of DNS administration. Of course he showed his own employers DNS tool (he works for infoblox.com) but there are other choices and methods of automating and he did not really make it into a big sales pitch for his employer, just a simple screenshot showing its ease of use and a few minutes to describe it.
Anyways, I plan to start really investigating the deployment of DNSSEC now.
The rule on staying alive as a program manager is to give 'em a number or give 'em a date, but never give 'em both at once.
