[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

technical contact at ATT Wireless

Subject: technical contact at ATT Wireless
From: jared at puck.nether.net (Jared Mauch)
Date: Fri, 29 Jun 2012 10:51:06 -0400
In-reply-to: <CAJEFqDdZgOvKr8euH2Kgb82vsm2znX__PmmLhPvTt28LNF_rbA@mail.gmail.com>
References: <CAJbq31Ht1dTmxa=m7VPvcULKr9z3qp47665XKGSkBXhBmy+-_Q@mail.gmail.com> <CAJAdsD=HfyTLG15nE8+UMzMTOXAPKB2iPPSoOAZXV3h6rADAwA@mail.gmail.com> <CADb+6TBYXvu1vhb=Mgfy6bTa+R_-J0P9Sfyq7UaXeX5MF0==LQ@mail.gmail.com> <CAJEFqDdZgOvKr8euH2Kgb82vsm2znX__PmmLhPvTt28LNF_rbA@mail.gmail.com>

On Jun 29, 2012, at 10:37 AM, Tyler Haske wrote:

> I'm sorry you don't like it, and I know IPv6 will wash all this away
> soon enough, but where I'm working we have no plans to implement IPv6,
> or require our vendors/partners to readdress their networks to get a
> VPN up.

Just because there are no plans, this doesn't mean you shouldn't bring it up.

Even if its a "radar"/"future" issue for their networking team, it does raise
the profile in the asks with others.

- Jared

Follow-Ups:
- technical contact at ATT Wireless
  - From: tyler.haske at gmail.com (Tyler Haske)

References:
- technical contact at ATT Wireless
  - From: mdevlin at aisle10.net (Mike Devlin)
- technical contact at ATT Wireless
  - From: paul4004 at gmail.com (PC)
- technical contact at ATT Wireless
  - From: jmaslak at antelope.net (Joel Maslak)
- technical contact at ATT Wireless
  - From: tyler.haske at gmail.com (Tyler Haske)

Prev by Date: technical contact at ATT Wireless
Next by Date: technical contact at ATT Wireless
Previous by thread: technical contact at ATT Wireless
Next by thread: technical contact at ATT Wireless
Index(es):
- Date
- Thread