Not sure where we are on this one, but I will re-iterate my support for the 3rd
time (once in the meeting and 2 times on this list).
> On 2 May 2023, at 20:56, Dhruv Dhody wrote:
>
> Hi,
>
> I support adoption!
>
> Some Nits -
> - Expand SLAAC
> - s/each prefix advertised advertised for
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!
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" mailto:fg...@si6networks.com>> wrote:
Hello, Eric,
On 8/4/23 02:13, Eric Vyncke (evyncke) wrote:
> May I
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
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.
Regards
-éric
On 30/03/2023, 10:03, "OPSEC on behalf of Jen
This email starts the OpSec WG adoption call for
draft-gont-opsec-ipv6-addressing
https://datatracker.ietf.org/doc/draft-gont-opsec-ipv6-addressing/.
The call ends on Thu, Apr 13th, 23:59:59 UTC.
Please review the draft and send your comments to the list.
--
SY, Jen Linkova aka Furry
