Re: [v6ops] Flash renumbering

So I think from a Fortune 500 perspective small, mid and large cap
companies representing big business and outages can be catastrophic costing
millions of dollars where a SOHO broadband user community it’s not
catastrophic from a monetary perspective that the SOHO or home user
watching Netflix is has to reboot his CPE from a renumbering event.

The impact on enterprises is more catastrophic then impact to SOHO user
communities and I guess from trickle down to economics perspective, if that
impacts your bottom line and don’t meet your earnings it impacts all
shareholders and of course the trickle down to everybody’s 401k’s.

Bottom line is even though for the broadband subscriber it disappointing to
have to reset your router when your video flix freezes ...but if your 401k
is being impacted by the SLAAC changes proposed I think we all may think
otherwise.

We just have to be a million percent sure that there is no impact to all
use cases.

Kind Regards

Gyan

On Fri, Sep 18, 2020 at 4:56 PM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 19-Sep-20 05:11, Gyan Mishra wrote:
>
> >
>
> > All
>
> >
>
> > I really still feel this use case being Broadband provider PD related
> stale prefix issue  is really a corner case for SOHO users
>
>
>
> Why is that a "corner case"? We can count SOHO networks by the hundreds of
> millions, compared with enterprise networks in millions. They both matter,
> but SOHOs are about two orders of magnitude greater in number.
>
>
>
>    Brian
>
>
>
> > as it does not impact enterprises with manually configured stable prefix
> which is 100% of the enterprise dual stack use case.
>
> >
>
> > From an operations impact there is considerable monetary impact to
> enterprises if the IPv6 standards change proposed by flash renumbering
>  does not take into account the  enterprise stable prefix scenario that
> does not fall into this one size fits all bucket being proposed.
>
> >
>
> > I am worried about adverse effects of the changes being proposed to
> SLAAC standard that could impact enterprises.  We just need to be very
> careful that every used case out there is accounted for.
>
> >
>
> > Gyan
>
> >
>
> > On Fri, Sep 18, 2020 at 11:56 AM Richard Patterson <richard@helix.net.nz
> <mailto:richard@helix.net.nz>> wrote:
>
> >
>
> >     On Fri, 18 Sep 2020 at 08:05, Vasilenko Eduard <
> vasilenko.eduard@huawei.com <mailto:vasilenko.eduard@huawei.com>> wrote:
>
> >
>
> >         Hi Brian,
>
> >
>
> >
>
> >         > SLAAC is only one of the victims of flash renumbering. (If
> there was more
>
> >
>
> >
>
> >         > widespread use of ULAs that might not be true.)
>
> >
>
> >
>
> >         [Ed: ] But How? Subscriber needs access to Global Internet.
>
> >
>
> >
>
> >         Is it possible to connect Google by ULA?
>
> >
>
> >
>
> >     Well if ULAs were used more often for local connectivity, they
> wouldn't be impacted by an outage of the WAN interface causing the GUA
> prefix to change.
>
> >
>
> >
>
> >
>
> >     _______________________________________________
>
> >
>
> >     v6ops mailing list
>
> >
>
> >     v6ops@ietf.org <mailto:v6ops@ietf.org>
>
> >
>
> >     https://www.ietf.org/mailman/listinfo/v6ops
>
> >
>
> > --
>
> >
>
> > <http://www.verizon.com/>
>
> >
>
> > *Gyan Mishra*
>
> >
>
> > /Network Solutions A//rchitect /
>
> >
>
> > /M 301 502-1347
>
> > 13101 Columbia Pike
>
> > /Silver Spring, MD
>
> >
>
> >
>
> >
>
> > _______________________________________________
>
> > v6ops mailing list
>
> > v6ops@ietf.org
>
> > https://www.ietf.org/mailman/listinfo/v6ops
>
> >
>
>
>
> --

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*M 301 502-134713101 Columbia Pike *Silver Spring, MD