Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt

On Wed, Nov 4, 2020 at 4:29 AM JORDI PALET MARTINEZ <jordi.palet=
40consulintel.es@dmarc.ietf.org> wrote:

> Exactly!
>
>
>
> In fact, not using it is very bad when you want to offer 5G broadband to
> customers that may not have access to a wireline. If they aren’t able to
> get /48 thru the 5G “modem”, how come they can segment their network? This
> is just creating NAT for IPv6, as if a 5G broadband customer needs to have
> multiple /64 VLANs, they have no other way.
>
>
>
   Gyan> See my response to Lorenzo.  Fixed 5G broadband replacement of
wired broadband would use DHCPV6 PD and get much larger allocations than a
/64 and would follow the BCOP RIPE-690 practices.  One of the reasons for a
much larger allocation is for the value added service at a premium network
slicing capabilities.

> Regards,
>
> Jordi
>
> @jordipalet
>
>
>
>
>
>
>
> El 4/11/20 9:52, "ipv6 en nombre de Lorenzo Colitti" <
> ipv6-bounces@ietf.org en nombre de lorenzo=40google.com@dmarc.ietf.org>
> escribió:
>
>
>
> On Tue, Nov 3, 2020 at 4:27 PM Gyan Mishra <hayabusagsm@gmail.com> wrote:
>
> It's hard to see why this draft is needed anyway. All that is needed
>
> is to remove the "64 bit" statement from the addressing architecture,
> which the WG has consistently failed to reach consensus about.
>
>
>
>     Gyan>  This topic has come up many times over the years in heated
> debate and this is another instance of that.  Agreed.  However, what makes
> this instance different is that we have a major problem to be solved with
> 4G  &  now as 5G is rolled out, segmentation is of utmost importance.  I
> think in the past we have not had a major problem to be solved and so this
> change being proposed did not gain traction,  but now as 5G becomes the
> "norm" as it will compete directly with broadband that customers will start
> using 5G in SOHO as well as other environments.   This is a major issue
> that has come up with the ramp up for 5G IPv6 only deployments.
>
>
>
> There is already a solution to this: use DHCPv6 PD on 5G networks. It's
> been supported since 3GPP release 10 several years ago.
>
> -------------------------------------------------------------------- IETF
> IPv6 working group mailing list ipv6@ietf.org Administrative Requests:
> https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.theipv6company.com
> The IPv6 Company
>
> This electronic message contains information which may be privileged or
> confidential. The information is intended to be for the exclusive use of
> the individual(s) named above and further non-explicilty authorized
> disclosure, copying, distribution or use of the contents of this
> information, even if partially, including attached files, is strictly
> prohibited and will be considered a criminal offense. If you are not the
> intended recipient be aware that any disclosure, copying, distribution or
> use of the contents of this information, even if partially, including
> attached files, is strictly prohibited, will be considered a criminal
> offense, so you must reply to the original sender to inform about this
> communication and delete it.
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
-- 

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

*Gyan Mishra*

*Network Solutions A**rchitect *

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