Re: [v6ops] seek comments and contributions to: draft-xiao-v6ops-nd-deployment-guidelines

Isolating hosts would cause a lot of damage in home networks where there is
no operator to control what hosts can do what. At a minimum you need
something like MUD to make this work. E.g., this would completely break
existing Thread (a 6lowpan mesh netwoek) Border routers which rely on
multicast working. It would also break multicast DNS service discovery for
the same reason.

This is not a new insight, and unfortunately the belief that this will work
causes a lot of problems that are hard for end users to diagnose. Please do
not publish this advice.

-- 
mellon@fugue.com

On October 6, 2021 at 04:53:31, Xipengxiao (xipengxiao@huawei.com) wrote:

> Hi folks,
>
>
>
> We published a draft: Isolating Hosts in Layer-2 and Layer-3 to Simplify
> ND and IPv6 First-Hop Deployments,
> https://datatracker.ietf.org/doc/draft-xiao-v6ops-nd-deployment-guidelines/.
> This draft summarizes information from many RFCs and drafts about the
> Neighbor Discovery Protocol. We believe it has value and is well readable.
> Your comments will be greatly appreciated.  We also welcome your further
> contribution to this draft.  Thank you very much.
>
>
>
> •       Background:
>
> •       There are known issues with IPv6 Neighbor Discovery (ND)
> protocol. Multiple solutions exist for the issues. But there is no
> guideline on how to avoid the issues, or how to select the suitable solution
>
> •       Contribution of the draft:
>
> •       Summarize known ND issues
>
> •       Analyze existing solutions to identify how they solve the issues
>
> •       Present an insight: isolating hosts in L2 and L3 will help to
> avoid many ND issues
>
> •       Present guidelines based on above insight to avoid ND issues, and
> recommend solutions for the remaining issues
>
> •       Analyze impact of such guidelines to other IPv6 first-hop
> protocols
>
>
>
> Regards,
>
>
>
> Xipeng Xiao, Ph.D.
>
> +49 162 2047 661
>
> xipengxiao@huawei.com
>
> Dusseldorf, Germany
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>