Say "Thank you" to Bill...

[Max Tulyev]

Remi Denis-Courmont wrote:
>> I understand well Bill's and TheBigBrother's(tm) main idea: to mak
>> traffic flow through their servers at least part, at least for a while.
> 
> What?!?
> 

Yep! Is is exactly as I said:

teredo.ipv6.microsoft.com. 3600 IN      A       65.54.227.136
teredo.ipv6.microsoft.com. 3600 IN      A       65.54.227.138
teredo.ipv6.microsoft.com. 3600 IN      A       65.54.227.140
teredo.ipv6.microsoft.com. 3600 IN      A       65.54.227.142
teredo.ipv6.microsoft.com. 3600 IN      A       65.54.227.144
teredo.ipv6.microsoft.com. 3600 IN      A       65.54.227.120
teredo.ipv6.microsoft.com. 3600 IN      A       65.54.227.122
teredo.ipv6.microsoft.com. 3600 IN      A       65.54.227.124
teredo.ipv6.microsoft.com. 3600 IN      A       65.54.227.126

maxtul at office ~ $ whois 65.54.227.136

OrgName:    Microsoft Corp
OrgID:      MSFT
Address:    One Microsoft Way
City:       Redmond
StateProv:  WA
PostalCode: 98052
Country:    US

NetRange:   65.52.0.0 - 65.55.255.255
CIDR:       65.52.0.0/14
NetName:    MICROSOFT-1BLK
NetHandle:  NET-65-52-0-0-1
Parent:     NET-65-0-0-0-0
NetType:    Direct Assignment
NameServer: NS1.MSFT.NET
NameServer: NS5.MSFT.NET
NameServer: NS2.MSFT.NET
NameServer: NS3.MSFT.NET
NameServer: NS4.MSFT.NET
Comment:
RegDate:    2001-02-14
Updated:    2004-12-09

RTechHandle: ZM23-ARIN
RTechName:   Microsoft Corporation
RTechPhone:  +1-425-882-8080
RTechEmail:  noc at microsoft.com


>> But - they really did a bad thing for V6: they made V6 enabled hosting
>> unusable in production :(
> 
> How so?

This is because of IPv6 enabled hosting can't be used as production
service for now.

We are getting a lot of complaints like "Our clients can't see our
site", and investigation shows that Teredo traffic is just filtered out
there. And you know, changing mass hosting is as easy as from ~$1, so we
see decreasing  user base.

And large content projects (at least mine friends) is NOT enabling V6
for such reason.

>> Compare it to Linux/Mac: Have V6 way - use it. V6 is not setuped - fall
>> back to V4.
> Windows has had proper support for source address selection (RFC3484) much earlier than Linux (around kernel 2.6.12 or so and libc 2.4). I think MacOSX still does not have it at all.

I'm happy that Windows has had. But it doesn't work properly. At least
for a number of real clients.

> You should rather blame broken third-party applications that are overriding RFC3484 and force IPv6 all the time.

Which exactly?

>> No tunnels. No security holes (how many people even know
>> they have unfiltered V6 connectivity?!).
> 
> Blame lame firewall filters. If you let random IP protocols and UDP ports numbers out, you should expect this kind of things anyway.

I can't operate as a hosting center and blame the world. Sorry. :(

-- 
WBR,
Max Tulyev (MT6561-RIPE, 2:463/253 at FIDO)