[arin-ppml] Draft Policy 2011-5: Shared Transition Space for IPv4 Address Extension - IAB comment

Tony Hain alh-ietf at tndh.net
Thu Jun 30 09:49:56 EDT 2011

William Herrin wrote:
> On Wed, Jun 29, 2011 at 12:55 PM, Joel Jaeggli <joelja at bogus.com>
> wrote:
> > On Jun 29, 2011, at 8:14 AM, William Herrin wrote:
> >> On Wed, Jun 29, 2011 at 10:59 AM, Alain Durand <adurand at juniper.net>
> wrote:
> >>> On Jun 29, 2011, at 10:35 AM, William Herrin wrote:
> >>>> You'll have to elaborate on that, because while windows firewall
> makes
> >>>> assumptions about what it's allowed to do if it encounters an
> RFC1918
> >>>> address, it makes no assumptions I'm aware of about what it can do
> >>>> with an address that isn't. If anything, the ISP choosing to
> employ
> >>>> RFC1918 addresses would cause Windows to incorrectly configure a
> >>>> permissive firewall.
> >>>
> >>> If [public address] then start 6to4
> >>
> >> Never seen it. And they'd be seriously crazy to enable it by default
> >> -- it would cause incredible brokenness even when the assumptions
> were
> >> met.
> >
> > Sorry it's on by default in windows vista and windows 7...
> As a Linux enthusiast, I enjoy tales of Microsoft doing something
> ignorant. And truly, what could be more foolish than arranging for
> your flagship product to automatically reroute packets through
> low-bandwidth volunteer-run 6to4 gateways?

The braindead concept that 6to4 gateways are required is driven by the
myopic view of the content providers. Look closely at the technology, and
you will find that those are artifacts, not a fundamental requirement of
packet delivery. If the content providers would simply add a local 6to4
router (note I said router, not relay), then add a 2002:: prefix to their
content servers, the packet delivery path would be *-exactly-* the same as
it is for IPv4. 

> Sadly, I must report the story to be false. My Windows 7 laptop did
> not, in fact, install a 6to4 adapter or configure an IPv6 address when
> I reprogrammed my DHCP server to give out a global scope IPv4 address.
> And the Teredo Tunneling interface remained in state "Media
> disconnected." Indeed, only the normal fe80 link local IPv6 address
> configured itself on my machine.
> You are mistaken sir.

Look around, because your symptoms indicate there is an IPv4 firewall
filtering both 6to4 and teredo packets. 


> Regards,
> Bill Herrin
> --
> William D. Herrin ................ herrin at dirtside.com  bill at herrin.us
> 3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
> Falls Church, VA 22042-3004
> _______________________________________________
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.

More information about the ARIN-PPML mailing list