In article <[email protected]>,
Jay Ashworth <[email protected]> wrote:
>----- Original Message -----
>> From: "River Tarnell" <[email protected]>
>> As long as the proxy supports IPv6, it can continue to talk to Apache
>> via IPv4; since WMF's internal network uses RFC1918 addresses, it
>> won't be affected by IPv4 exhaustion.
>It might
No, it won't. The internal network IPs (which are used for
communication between the proxy and the back-end Apache) are not
publicly visible and are completely inconsequential to users.
>how would a 6to4NAT affect blocking?
ISP NATs are a separate issue, and might be interesting; if nothing
else, as one reason (however small) for ISPs to provide IPv6 to end
users. ("Help! I can't edit Wikipedia because my ISP's CGNAT pool was
blocked!".)
The general situation with existing ISPs that use transparent proxies is
that sometimes users just can't edit. Admins try to document such
addresses and avoid blocking them for too long.
>> >> (APNIC runs out of IPv4 space to give to providers somewhere around
>> >> August, statistically; RIPE in Feb or March 2012, ARIN in July
>> >> 2012).
>> >ARIN issued the last 5 available /8s to RIRs *today*; we've been
>> >talking about it all day on NANOG.
>> Not exactly. IANA issued the last 5 /8s to RIRs, of which ARIN is one,
>> today. But George is talking about RIR exhaustion, which is still some
>> months away.
>His phrasing seemed a bit.. insufficiently clear, to me. That was me,
>attempting to clarify.
Okay. I feel your clarification was not very clear ;-)
ARIN didn't issue any /8s today, IANA did. ARIN was one of the
*recipients* of those /8s.
- river.
_______________________________________________
Wikitech-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
