Re: blogs.cisco.com not available via IPv6

2013-12-09 Thread Jay Hennigan
On 12/5/13 5:39 PM, Rogan Schlassa wrote: > Please dont reply back with such legal disclaimers. It is basically SPAM > and of course nonsense. > > The thought that you can send a email and force your companies terms on us > is ridiculous. > > If CISCO forces that in your sig then for one tell the

Re: blogs.cisco.com not available via IPv6

2013-12-07 Thread jamie rishaw
*Has a Rick Perry "Oops." moment*. Thanks, Jared. ..Again. :) -j

Re: blogs.cisco.com not available via IPv6

2013-12-07 Thread Jared Mauch
t;> 111 Wood Avenue South >>>>> Iselin, New Jersey 08830 >>>>> United States >>>>> Cisco.com >>>>> >>>>> >>>>> >>>>> Think before you print. >>>>> This email may contain

Re: blogs.cisco.com not available via IPv6

2013-12-07 Thread Michael Smith
On Dec 7, 2013, at 8:26 AM, jamie rishaw wrote: > (A little late but) it's reachable for me -- Funny tho that something at > cisco is IPv6 via a v4<->v6 (2001::) :-) > > jamie Huh? 2001:4800::/29 is owned by Rackspace. It's native all the way from "here" anyway. Mike

Re: blogs.cisco.com not available via IPv6

2013-12-07 Thread jamie rishaw
United States > >>> Cisco.com > >>> > >>> > >>> > >>> Think before you print. > >>> This email may contain confidential and privileged material for the > >>>sole > >>> use of the intended recipient

Re: blogs.cisco.com not available via IPv6

2013-12-05 Thread Geraint Jones
fidential and privileged material for the >>>sole >>> use of the intended recipient. Any review, use, distribution or >>>disclosure >>> by others is strictly prohibited. If you are not the intended >>>recipient (or >>> authorized to recei

Re: blogs.cisco.com not available via IPv6

2013-12-05 Thread Richard Porter
ate legal information go to: >> http://www.cisco.com/web/about/doing_business/legal/cri/index.html >> >> >> >> >> >> -Original Message- >> From: Jared Mauch [mailto:ja...@puck.nether.net] >> Sent: Wednesday, December 04, 2013 9:23 AM >

RE: blogs.cisco.com not available via IPv6

2013-12-05 Thread Rogan Schlassa
ive for the recipient), please contact the sender by > reply email and delete all copies of this message. > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/index.html > > > > > > -Original Message----- > From: Jared

RE: blogs.cisco.com not available via IPv6

2013-12-05 Thread John Stuppi (jstuppi)
/cri/index.html -Original Message- From: Jared Mauch [mailto:ja...@puck.nether.net] Sent: Wednesday, December 04, 2013 9:23 AM To: Henri Wahl Cc: NANOG list Subject: Re: blogs.cisco.com not available via IPv6 I'm seeing it down via IPv6: * Trying 2600:1407:9:295::90... * Connected to

Re: blogs.cisco.com not available via IPv6

2013-12-05 Thread Mark Townsley
cts confirmed that they were made aware of this 12 hours > ago and it's being worked on. > > Frank > > -Original Message- > From: Jared Mauch [mailto:ja...@puck.nether.net] > Sent: Wednesday, December 04, 2013 8:23 AM > To: Henri Wahl > Cc: NANOG list > Sub

RE: blogs.cisco.com not available via IPv6

2013-12-04 Thread Frank Bulk
My Cisco IPv6 contacts confirmed that they were made aware of this 12 hours ago and it's being worked on. Frank -Original Message- From: Jared Mauch [mailto:ja...@puck.nether.net] Sent: Wednesday, December 04, 2013 8:23 AM To: Henri Wahl Cc: NANOG list Subject: Re: blogs.cisco.co

Re: blogs.cisco.com not available via IPv6

2013-12-04 Thread Jared Mauch
I'm seeing it down via IPv6: * Trying 2600:1407:9:295::90... * Connected to www.cisco.com (2600:1407:9:295::90) port 80 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.30.0 > Host: www.cisco.com > Accept: */* > < HTTP/1.1 200 OK * Server Apache is not blacklisted * About to connect() to blogs.cisc