I mean.. that's fine... but while you guys are figuring out IPv6, I'm busy invoicing my clients for static IPv4 addresses....

Who's making money and who's losing money?

On 10/23/19 11:41 AM, Zach Underwood wrote:
Matt everytime I see your name doing anything with ipv6 I cringe, get your head out of the sand and learn something about ipv6. The longer you keep at this hating on ipv6 the stupider you look. ipv6 has been around for a while and is not going anywhere.

On Wed, Oct 23, 2019 at 11:29 AM Matt Hoppes <mattli...@rivervalleyinternet.net <mailto:mattli...@rivervalleyinternet.net>> wrote:

    This is true, but that's why you acquire other ISPs, purchase IPv4 on
    the auction block, etc.    And once that runs out, CGNAT is really not
    all that complicated or expensive to deploy.... compared to deploying
    IPv6 which is still very much a "beta" protocol.

    There are client devices that are broken and don't properly handle
    IPv6,
    there is confusion and argument over how best to deploy IPv6, large
    sections of the Internet still don't support IPv6, the the way IPv6 was
    designed and implemented screams of "Engineers" vs "Usability".

    On 10/23/19 11:25 AM, dave wrote:
     > Meh, good luck with that LOL.. We'll be seeing you on the other side
     > Its not that ipv4 is going away at all its that you can just walk
    into
     > the arin store and purchase large public block for your use for
    much longer.
     > IPV6 is plentiful and a green pasture of natural selection.
     >
     >
     >
     > On 10/23/19 8:01 AM, Matt Hoppes wrote:
     >> FUD ALERT!  FUD ALERT!   IPv4 is not going away any time soon, it's
     >> not practical.     There are too many things that rely on IPv4. And
     >> until I can run only one stack I'm not planning to mass deploy
    IPv6.
     >> We have an IPv6 deployment plan, but there is minimal benefit in
    dual
     >> stacking and no financial gain until we need to.
     >>
     >> Right now there is a negative benefit for deploying IPv6 (overhead,
     >> management, no ROI, can't bill customers for static IPs).
     >>
     >> We have a plan, but until it's needed we don't plan to roll  it
    out.
     >> IPv4 will be here for many years to come.
     >>
     >> On 10/23/19 8:54 AM, dave via AF wrote:
     >>>
     >>> Yeah.. No..
     >>> They are more up to date than you think just not ahead
     >>>
     >>> On 10/21/19 2:20 PM, Steve Jones wrote:
     >>>> yeah, no.
     >>>> .gov agencies still run dos
     >>>> 10 years at best til the ones that matter will be organized
    enough
     >>>> to shut down ip4 access
     >>>>
     >>>>
     >>>> On Mon, Oct 21, 2019 at 2:12 PM Dennis Burgess via AF
     >>>> <af@af.afmug.com <mailto:af@af.afmug.com>
    <mailto:af@af.afmug.com <mailto:af@af.afmug.com>>> wrote:
     >>>>
     >>>>     Keep in mind that IPv6 will be necessary within 2-4 years,
    if the
     >>>>     .govs shutdown access via v4 for security reasons.  No
    more FCC/
     >>>>     IRS or any .GOV unless over v6.  Note that the current
    plan is 2-3
     >>>>     years, I have given it an extra year for measure!
     >>>>
     >>>>     V6 should be deployed NOW.   Not later, when you HAVE TO. Then
     >>>>     you will be making mistakes etc.
     >>>>
     >>>>     *LTI-Full_175px*
     >>>>
     >>>>     *Dennis Burgess, Mikrotik Certified Trainer
     >>>>     MTCNA, MTCRE, MTCWE, MTCTCE, MTCINE, MTCSE, HE IPv6 Sage,
    Cambium
     >>>>     ePMP Certified *
     >>>>
     >>>>     Author of "Learn RouterOS- Second Edition”
     >>>>
     >>>>     *Link Technologies, Inc*-- Mikrotik & WISP Support Services
     >>>>
     >>>>     *Office*: 314-735-0270  Website: http://www.linktechs.net
     >>>> <http://www.linktechs.net/>
     >>>>
     >>>>     Create Wireless Coverage’s with www.towercoverage.com
    <http://www.towercoverage.com>
     >>>> <http://www.towercoverage.com>
     >>>>
     >>>>     *From:* AF <af-boun...@af.afmug.com
    <mailto:af-boun...@af.afmug.com>
     >>>> <mailto:af-boun...@af.afmug.com
    <mailto:af-boun...@af.afmug.com>>> *On Behalf Of * Steve Jones
     >>>>     *Sent:* Monday, October 21, 2019 2:07 PM
     >>>>     *To:* AnimalFarm Microwave Users Group <af@af.afmug.com
    <mailto:af@af.afmug.com>
     >>>> <mailto:af@af.afmug.com <mailto:af@af.afmug.com>>>
     >>>>     *Subject:* Re: [AFMUG] Buying new IP space
     >>>>
     >>>>     NAT problems with BGP are why we are looking for more IP space
     >>>>
     >>>>     IP6 is still years out for us
     >>>>
     >>>>     On Mon, Oct 21, 2019 at 1:43 PM Adam Moffett
    <dmmoff...@gmail.com <mailto:dmmoff...@gmail.com>
     >>>> <mailto:dmmoff...@gmail.com <mailto:dmmoff...@gmail.com>>> wrote:
     >>>>
     >>>>         If you're not doing it already, start thinking about dual
     >>>>         stack with IPv4 CGN and IPv6 public IPs.  There's a
    learning
     >>>>         curve, but it's not that bad.
     >>>>
     >>>>         -Adam
     >>>>
     >>>>         On 10/21/2019 12:51 PM, Steve Jones wrote:
     >>>>
     >>>>             Where is the best place to get these? How do we verify
     >>>>             space has a decent reputation so we dont go
    through months
     >>>>             of cleanup and all that stuff?
     >>>>
     >>>>         --         AF mailing list
     >>>> AF@af.afmug.com <mailto:AF@af.afmug.com>
    <mailto:AF@af.afmug.com <mailto:AF@af.afmug.com>>
     >>>> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
     >>>>
     >>>>     --     AF mailing list
     >>>> AF@af.afmug.com <mailto:AF@af.afmug.com>
    <mailto:AF@af.afmug.com <mailto:AF@af.afmug.com>>
     >>>> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
     >>>>
     >>>>
     >>>
     >>>
     >>
     >

-- AF mailing list
    AF@af.afmug.com <mailto:AF@af.afmug.com>
    http://af.afmug.com/mailman/listinfo/af_af.afmug.com



--
Zach Underwood (RHCE,RHCSA,RHCT,UACA)
My website <http://zachunderwood.me>
advance-networking.com <http://advance-networking.com>


--
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com

Reply via email to