Hi, All,
I happened to participate in an IPv6 deployment meeting with some large
content provider. Eventually there was a discussion about how to
mitigate some attacks using block-lists, and they argued that they ban
offending addresses (/128 for the IPv6 case), following IPv4 practices.
While they had already deployed IPv6, some of the associated
implications arising from the increased address space seemed to be
non-obvious to them.
So that's what motivated the publication of this document.
* TXT:
https://www.ietf.org/archive/id/draft-gont-opsec-ipv6-addressing-00.txt
* HTML:
https://www.ietf.org/archive/id/draft-gont-opsec-ipv6-addressing-00.html
Comments welcome!
Thanks,
Fernando
-------- Forwarded Message --------
Subject: New Version Notification for
draft-gont-opsec-ipv6-addressing-00.txt
Date: Thu, 02 Feb 2023 19:48:40 -0800
From: [email protected]
To: Fernando Gont <[email protected]>, Guillermo Gont
<[email protected]>
A new version of I-D, draft-gont-opsec-ipv6-addressing-00.txt
has been successfully submitted by Fernando Gont and posted to the
IETF repository.
Name: draft-gont-opsec-ipv6-addressing
Revision: 00
Title: Implications of IPv6 Addressing on Security Operations
Document date: 2023-02-02
Group: Individual Submission
Pages: 8
URL:
https://www.ietf.org/archive/id/draft-gont-opsec-ipv6-addressing-00.txt
Status:
https://datatracker.ietf.org/doc/draft-gont-opsec-ipv6-addressing/
Htmlized:
https://datatracker.ietf.org/doc/html/draft-gont-opsec-ipv6-addressing
Abstract:
The increased address availability provided by IPv6 has concrete
implications on security operations. This document discusses such
implications, and sheds some light on how existing security
operations techniques and procedures might need to be modified
accommodate the increased IPv6 address availability.
The IETF Secretariat
_______________________________________________
OPSEC mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsec
