On Tue, Aug 30, 2011 at 16:30, Michael Foord <[email protected]> wrote:

> On 30/08/2011 14:35, Patrick Ben Koetter wrote:
>
>> I live next to Gert. Should I go over and "shake his hands"… ;)
>>
>> But seriously, this seems to be a problem introduced by XS4all. Is there
>> anything we can/should do about?
>>
>
> I have no idea :-)
>
> The email came in to [email protected] so I thought it should be sent
> to this list, so that someone who understood it could decide whether or not
> it needed our input.
>

[email protected] at least (and [email protected] probably as well) ends up with
the right people, some of whom are very active in the IPv6 community, so I'm
sure they'll resolve it one way or another posthaste.


>
>> p@rick
>>
>>
>>
>>
>> * Michael Foord<[email protected]**>:
>>
>>> Begin forwarded message:
>>>
>>>> From: Mark Mahle<[email protected]>
>>>> Subject: XS4ALL strict IPv6 filtering
>>>> Date: 30 August 2011 13:19:54 GMT+01:00
>>>> To: [email protected]
>>>> Cc: [email protected], Owen Delong<[email protected]>,
>>>> [email protected], [email protected], [email protected]
>>>>
>>>> Hello XS4All Noc,
>>>>
>>>> We are Host Virtual, a cloud provider that provides dual-stack IPv4+IPv6
>>>> services worldwide in 10 locations via AS36236 and AS42210.
>>>>
>>>> It has come to our attention that customers in any of our three EU
>>>> locations, using our RIPE assigned ip space (2a00:dd80::/32) are unable to
>>>> access the XS4all network, including sites such as www.python.org. We
>>>> announce at a minimum, a /48 from each location as per generally accepted
>>>> standards for IPv6 routability.
>>>>
>>>> In previous communication with our peers, we've learned that XS4ALL
>>>> filters its IPv6 traffic based on the strict case at
>>>> http://www.space.net/~gert/**RIPE/ipv6-filters.html<http://www.space.net/~gert/RIPE/ipv6-filters.html>published
>>>>  by Gert Döring.
>>>>
>>>> While we understand and appreciate there has been much discussion on the
>>>> topic we feel this type of strict filtering, based on rules published and
>>>> not updated over 3 years ago are now negatively impacting both XS4ALL's own
>>>> customers, and the end users of high profile sites such as
>>>> www.python.org.
>>>>
>>>> Being a supporter of many open source projects ourselves, and a strong
>>>> supporter of moving IPv6 forward we appeal to you to review this policy.
>>>> With IPv6 adoption now accelerating it's in all of our best interests to
>>>> ensure IPv6 routability.
>>>>
>>>> I appreciate your attention and review of this policy and have included
>>>> relevant parties on the CC.
>>>>
>>>> Thanks
>>>> Mark
>>>>
>>>> --
>>>> Mark Mahle
>>>> +1-877-HOSTED7 x201 :: http://www.hostvirtual.com
>>>>
>>>>
>>>
>>>
>>> --
>>> http://www.voidspace.org.uk/
>>>
>>> May you do good and not evil
>>> May you find forgiveness for yourself and forgive others
>>> May you share freely, never taking more than you give.
>>> -- the sqlite blessing 
>>> http://www.sqlite.org/**different.html<http://www.sqlite.org/different.html>
>>>
>>>
>>>
>>>
>>>
>>> ______________________________**_________________
>>> pydotorg-www mailing list
>>> [email protected]
>>> http://mail.python.org/**mailman/listinfo/pydotorg-www<http://mail.python.org/mailman/listinfo/pydotorg-www>
>>>
>>
>>
>
> --
> http://www.voidspace.org.uk/
>
> May you do good and not evil
> May you find forgiveness for yourself and forgive others
> May you share freely, never taking more than you give.
> -- the sqlite blessing 
> http://www.sqlite.org/**different.html<http://www.sqlite.org/different.html>
>
> ______________________________**_________________
> pydotorg-www mailing list
> [email protected]
> http://mail.python.org/**mailman/listinfo/pydotorg-www<http://mail.python.org/mailman/listinfo/pydotorg-www>
>



-- 
Thomas Wouters <[email protected]>

Hi! I'm a .signature virus! copy me into your .signature file to help me
spread!
_______________________________________________
pydotorg-www mailing list
[email protected]
http://mail.python.org/mailman/listinfo/pydotorg-www

Reply via email to