Forgot your password?
typodupeerror

+ - Monty Python to reunite for movie->

Submitted by dutchwhizzman
dutchwhizzman (817898) writes "The surviving members of Monty Python have announced they will make a new movie. It will be titled "Absolutely Anything". Graham Chapman won't be there to join them anymore, but they think the movie will still be in the spirit of "Life of Brian", "The meaning of Life" and other movies they made in the past."
Link to Original Source

+ - Facebook launches experimental IPv6 site

Submitted by
Sesse
Sesse writes "At Google's IPv6 Implementors' Conference (currently ongoing), Facebook today announced the experimental (non-production) availability of www.v6.facebook.com, giving full access to Facebook properties on IPv6. (m.v6.facebook.com also exists, for mobile users lucky enough to have IPv6 connectivity.) As an extra bonus, Facebook decided to try out Locator/Identifier Separator Protocol (LISP), available at www.lisp6.facebook.com."

Comment: Re:Mac Issue Or IPv6 Issue? (Score 1) 204

by Sesse (#32109052) Attached to: Mac OS X Problem Puts Up a Block To IPv6

With regards to glibc, 2.3.6 is stone old. RFC 3484 support has matured a lot since Etch :-) Actually you need to go to Debian unstable to find a glibc that's patched to prefer NATed IPv4 over 6to4.

I think my rebuttal of your OS X analysis was a bit unclear, so let me try to make it a bit better. First of all, note that the sentence you're quoted does not mention 6to4 in any way. Second, note the part I wrote about “hits that come through”. The User-Agent is recorded every time the experiment is sent out, not only when it comes in. Thus, you can draw a direct correlation of OS X in the User-Agent string less likely to come back; your analysis was “browsers with Mac OS X in the User-Agent string are more commonly using 6to4 addresses”, which just isn't the same. (It's also true, of course, but the “OS X more often is broken” analysis doesn't depend on that at all.) If you did an experiment which only registered IPv6 hits that actually came through, your criticism would have been valid, but that's not how this was done.

/* Steinar */

Comment: Re:6to4 is unreliable (Score 1) 204

by Sesse (#32095570) Attached to: Mac OS X Problem Puts Up a Block To IPv6

Look at the page -- several Linux distributions (Fedora, Ubuntu, Gentoo, SuSE, Mandriva, Debian) now prefer IPv4 over 6to4 pretty unconditionally (unless you're trying to connect to a 6to4 host, but that's pretty obscure for a web server). The rest only prefer IPv4 over 6to4 when the IPv4 is not NAT-ed.

/* Steinar */

Comment: Re:Mac Issue Or IPv6 Issue? (Score 1) 204

by Sesse (#32095552) Attached to: Mac OS X Problem Puts Up a Block To IPv6

No, the reality is that getaddrinfo() on most platforms actually follow RFC3484 and prioritize IPv4 over 6to4. (There's a clear distinction in the RFC between 6to4 and other forms of IPv6.) OS X doesn't and uncritically tries IPv6 -- that is, of course, assuming you don't crash into any of the other resolver bugs they introduced in 10.5.

It should be said that if you follow RFC3484 to the letter, 6to4 will be preferred over NAT-ed IPv4. However, that was most likely just an oversight in the standard (the draft revision makes changes to fix that), and most vendors (certainly Microsoft, and most of the major Linux distros, although not glibc upstream yet) has made that change. However, this is moot with regards to OS X, since they don't actually seem to follow RFC3484 in the first place.

You are also wrong in the Airports are the only CPEs that try to enable 6to4 out of the box -- some Linksys models do this, among others. The Airports are, however, most likely the most common. You're also right in that uncritically enabling this is not a good idea; the CPE should at least have done a routability test first.

Finally, you're assuming the statistics here are based only on the User-Agent string on the dualstack hits that come through. They're not -- please read the experiment design more carefully. There is a direct correlation measured between using OS X (as seen in the User-Agent string that fetches the iframe) and inability to fetch the dualstack image. In no way does this result depend on correlation between OS X and 6to4.

/* Steinar */

Comment: Re:It would be nice if people read the standards.. (Score 1) 204

by Sesse (#32095514) Attached to: Mac OS X Problem Puts Up a Block To IPv6

Hi,

A few errors here:

  • The host has fully working IPv6 connectivity on the AAAA record it advertises. You could easily have checked this given the data in the report.
  • This is a 6to4, not 6over4, which is something completely different.
  • The 6bone has not existed for years.

/* Steinar */

The Internet

+ - SPAM: IPv6 faces trial by fire tonight at IETF meeting

Submitted by alphadogg
alphadogg (971356) writes "The Internet engineering community will be eating its own dog food tonight. For one hour, the 1,250 network experts at the Internet Engineering Task Force meeting in Philadelphia will be able to access the Internet only through IPv6. The IETF created IPv6 in the mid-1990s, but this upgrade to the Internet's main communications protocol has not yet been widely deployed — even by the technology's biggest proponents here. IETF Chair Russ Housley explains tonight's plan and addresses the long term in Network World interview."
Link to Original Source

Uncompensated overtime? Just Say No.

Working...