Re: [OPSEC] Adoption Call: draft-gont-opsec-ipv6-addressing

Hi,

I support adoption!

Some Nits -
- Expand SLAAC
- s/each prefix advertised advertised for address/each prefix advertised
for address/
- add reference for Kubernetes and IPv6-enabled VPNs
- s/since sunch IPv6 prefix/since such IPv6 prefix/
- suggest using their instead of his/her

Thanks!
Dhruv

On Mon, Apr 10, 2023 at 5:52 PM Eric Vyncke (evyncke) <evyncke=
40cisco.com@dmarc.ietf.org> wrote:

> Hello Fernando,
>
> No problem at all of course, we all work to improve the security of the
> Internet (which is obviously IPv6 ;-) )
>
> Cheers
>
> -éric
>
> On 10/04/2023, 09:28, "Fernando Gont" <fgont@si6networks.com <mailto:
> fgont@si6networks.com>> wrote:
>
>
> Hello, Eric,
>
>
> On 8/4/23 02:13, Eric Vyncke (evyncke) wrote:
> > May I suggest that this draft, at the bare minimum, has RFC 9099 (an
> > OPSEC document) in its references list? Notably because the draft
> > sections about network correlation is already addressed in RFC 9099
> > section 2.6 and others.
>
>
> This was my bad '' this )and other references) is in our TO-DO list for
> the next rev.
>
>
> Thanks!
>
>
> Fernando
>
>
>
>
>
>
>
>
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com <mailto:fgont@si6networks.com>
> PGP Fingerprint: F242 FF0E A804 AF81 EB10 2F07 7CA1 321D 663B B494
>
>
>
> _______________________________________________
> OPSEC mailing list
> OPSEC@ietf.org
> https://www.ietf.org/mailman/listinfo/opsec
>