On Wed, May 28, 2014 at 3:29 PM, Ryan Rawdon wrote:
> On May 22, 2014, at 9:18 PM, Matthew Petach wrote:
>
> On Thu, May 22, 2014 at 8:49 AM, Lee Howard wrote:
>
>
>
> On 5/22/14 8:04 AM, "Livingood, Jason"
> wrote:
> [snip]
>
> In his really useful listing of content providers' IPv6 support,
On May 22, 2014, at 9:18 PM, Matthew Petach wrote:
> On Thu, May 22, 2014 at 8:49 AM, Lee Howard wrote:
>
>>
>>
>> On 5/22/14 8:04 AM, "Livingood, Jason"
>> wrote:
>> [snip]
>> In his really useful listing of content providers' IPv6 support,
>> https://www.vyncke.org/ipv6status/ Eric Vynck
On 5/22/14 9:41 PM, "Martin Hannigan" wrote:
>
>
>My job isn't to increase v6. It's to make sure we can serve traffic over
>protocols we are asked to. We are dual stacked which means our customers
>are.
I'm not going to tell you what your job is.
I'm curious, though, whether your customers spec
On 23 May 2014, at 3:29 pm, Christopher Morrow wrote:
> On Fri, May 23, 2014 at 1:24 AM, Julien Goodwin
> wrote:
>> On 23/05/14 11:21, Jared Mauch wrote:
>>> You can't cater to everyones broken network. I can't reach 1.1.1.1 from
>>> here either, but sometimes when I travel I can, even with
On Fri, May 23, 2014 at 1:24 AM, Julien Goodwin wrote:
> On 23/05/14 11:21, Jared Mauch wrote:
>> You can't cater to everyones broken network. I can't reach 1.1.1.1 from
>> here either, but sometimes when I travel I can, even with TTL=1. At some
>> point folks have to fix what's broken.
>
> 1.
On 23/05/14 11:21, Jared Mauch wrote:
> You can't cater to everyones broken network. I can't reach 1.1.1.1 from here
> either, but sometimes when I travel I can, even with TTL=1. At some point
> folks have to fix what's broken.
1.1.1.1 is not private IP space.
BGP routing table entry for 1.1.
On Thu, May 22, 2014 at 8:49 AM, Lee Howard wrote:
>
>
> On 5/22/14 8:04 AM, "Livingood, Jason"
> wrote:
>
> >On 5/21/14, 9:38 PM, "Jared Mauch" wrote:
> >
> >>On May 21, 2014, at 7:17 PM, Ca By wrote:
> >>
> >>> Verizon Wireless is at 50% ipv6 penetration
> >>
> >>I suspect this would go up s
On Thursday, May 22, 2014, Martin Hannigan wrote:
>
>
> On Thursday, May 22, 2014, Rubens Kuhl
> >
> wrote:
>
>> >
>> >
>> > Jared,
>> >
>> > Akamai has been v6 enabled for years. Customers have choices and know
>> best.
>> >
>> > Isn't your network still offering both as customer choices? :-)
>
On Thursday, May 22, 2014, Rubens Kuhl wrote:
> >
> >
> > Jared,
> >
> > Akamai has been v6 enabled for years. Customers have choices and know
> best.
> >
> > Isn't your network still offering both as customer choices? :-)
> >
>
> Making new customers dual-stack by default for the last two years
>
>
> Jared,
>
> Akamai has been v6 enabled for years. Customers have choices and know best.
>
> Isn't your network still offering both as customer choices? :-)
>
Making new customers dual-stack by default for the last two years would
have gone far in increasing IPv6, unless Akamai is only losing
On May 22, 2014, at 9:14 PM, Martin Hannigan wrote:
>
>
> On Thursday, May 22, 2014, Jared Mauch wrote:
>
> On May 22, 2014, at 8:04 AM, Livingood, Jason
> wrote:
>
> > On 5/21/14, 9:38 PM, "Jared Mauch" wrote:
> >
> >> On May 21, 2014, at 7:17 PM, Ca By wrote:
> >>
> >>> Verizon Wirele
On Thursday, May 22, 2014, Jared Mauch wrote:
>
> On May 22, 2014, at 8:04 AM, Livingood, Jason <
> jason_living...@cable.comcast.com > wrote:
>
> > On 5/21/14, 9:38 PM, "Jared Mauch" >
> wrote:
> >
> >> On May 21, 2014, at 7:17 PM, Ca By >
> wrote:
> >>
> >>> Verizon Wireless is at 50% ipv6 pene
On 5/22/14 8:04 AM, "Livingood, Jason"
wrote:
>On 5/21/14, 9:38 PM, "Jared Mauch" wrote:
>
>>On May 21, 2014, at 7:17 PM, Ca By wrote:
>>
>>> Verizon Wireless is at 50% ipv6 penetration
>>
>>I suspect this would go up significantly if Twitter and Instagram would
>>IPv6 enable their services.
On 14-05-22 08:55 AM, Christopher Morrow wrote:
> Coke Classic managed to outlast NewCoke... pattern repeating?
Coke Classic changed as well.
NAT44: the high-fructose corn syrup of IPv4.
M.
--
Michael Brown| The true sysadmin does not adjust his behaviour
Systems Administrator|
On 22May2014Thursday, at 5:55, Christopher Morrow
wrote:
> On Thu, May 22, 2014 at 8:41 AM, Jared Mauch wrote:
>> I remind vendors when I talk to them, "IPv6 first, then IP classic(tm)".
>
> Coke Classic managed to outlast NewCoke... pattern repeating?
its classic for a reason….
/bill
Don't even joke about that, I can't handle another decade of NAT.
--
Josh
On 5/22/14, 8:55 AM, "Christopher Morrow" wrote:
>On Thu, May 22, 2014 at 8:41 AM, Jared Mauch
>wrote:
>> I remind vendors when I talk to them, "IPv6 first, then IP
>>classic(tm)".
>
>Coke Classic managed to outlast
On Thu, May 22, 2014 at 8:41 AM, Jared Mauch wrote:
> I remind vendors when I talk to them, "IPv6 first, then IP classic(tm)".
Coke Classic managed to outlast NewCoke... pattern repeating?
On May 22, 2014, at 8:04 AM, Livingood, Jason
wrote:
> On 5/21/14, 9:38 PM, "Jared Mauch" wrote:
>
>> On May 21, 2014, at 7:17 PM, Ca By wrote:
>>
>>> Verizon Wireless is at 50% ipv6 penetration
>>
>> I suspect this would go up significantly if Twitter and Instagram would
>> IPv6 enable th
On 5/21/14, 9:38 PM, "Jared Mauch" wrote:
>On May 21, 2014, at 7:17 PM, Ca By wrote:
>
>> Verizon Wireless is at 50% ipv6 penetration
>
>I suspect this would go up significantly if Twitter and Instagram would
>IPv6 enable their services. Same for pintarest.
+1
We naturally focus a lot on netwo
On May 21, 2014, at 7:17 PM, Ca By wrote:
> Verizon Wireless is at 50% ipv6 penetration
I suspect this would go up significantly if Twitter and Instagram would IPv6
enable their services. Same for pintarest.
Other folks like bit.ly have briefly toyed with IPv6, and with the
helpdesk.test-ip
20 matches
Mail list logo
