ipv6hackers

1–30 of 327

0 selected

Jun 2

[ipv6hackers] (IETF I-D) Implications of IPv6 Addressing on Security Operations (Fwd: New Version Notification for draft-ietf-opsec-ipv6-addressing-00.txt)

Folks, The IETF OPSEC WG has adopted our IETF ID entitled "Implications of IPv6 Addressing on

unread,

[ipv6hackers] (IETF I-D) Implications of IPv6 Addressing on Security Operations (Fwd: New Version Notification for draft-ietf-opsec-ipv6-addressing-00.txt)

Folks, The IETF OPSEC WG has adopted our IETF ID entitled "Implications of IPv6 Addressing on

Jun 2

Mar 30

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

Hi, folks, FYI -- If you feel like weighing in (for those interested in joining the opsec wg, please

unread,

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

Hi, folks, FYI -- If you feel like weighing in (for those interested in joining the opsec wg, please

Mar 30

Fernando Gont, … Andrew Ruthven13

Feb 7

[ipv6hackers] (IETF I-D); Implications of IPv6 Addressing on Security Operations (Fwd: New Version Notification for draft-gont-opsec-ipv6-addressing-00.txt)

Hi, Andrew, On 7/2/23 02:26, Andrew Ruthven wrote: > Hey, > > On Tue, 2023-02-07 at 01:07 -

unread,

[ipv6hackers] (IETF I-D); Implications of IPv6 Addressing on Security Operations (Fwd: New Version Notification for draft-gont-opsec-ipv6-addressing-00.txt)

Hi, Andrew, On 7/2/23 02:26, Andrew Ruthven wrote: > Hey, > > On Tue, 2023-02-07 at 01:07 -

Feb 7

Fernando Gont, Andrew Walding4

Jan 2

[ipv6hackers] IPv6 in GCP (WTH?): default route

Than you On Mon, Jan 2, 2023 at 10:14 AM Fernando Gont <fern...@gont.com.ar> wrote: > Hi,

unread,

[ipv6hackers] IPv6 in GCP (WTH?): default route

Than you On Mon, Jan 2, 2023 at 10:14 AM Fernando Gont <fern...@gont.com.ar> wrote: > Hi,

Jan 2

12/13/22

[ipv6hackers] Windows 11 now implements RFC 7217 (stable privacy addresses)!

Folks, After over 10 (yes, *ten*) years, we have finally addressed security/privacy issues in the

unread,

[ipv6hackers] Windows 11 now implements RFC 7217 (stable privacy addresses)!

Folks, After over 10 (yes, *ten*) years, we have finally addressed security/privacy issues in the

12/13/22

8/31/22

[ipv6hackers] Mitigating the effects of SLAAC renumbering events (draft-ietf-6man-slaac-renum)

Folks, We have been discussing the potential problems associated with SLAAC renumbering events for a

unread,

[ipv6hackers] Mitigating the effects of SLAAC renumbering events (draft-ietf-6man-slaac-renum)

Folks, We have been discussing the potential problems associated with SLAAC renumbering events for a

8/31/22

8/18/22

[ipv6hackers] Fwd: RFC 9288 on Recommendations on the Filtering of IPv6 Packets Containing IPv6 Extension Headers at Transit Routers

Hi, FYI. RFC 9288, "Recommendations on the Filtering of IPv6 Packets Containing IPv6 Extension

unread,

[ipv6hackers] Fwd: RFC 9288 on Recommendations on the Filtering of IPv6 Packets Containing IPv6 Extension Headers at Transit Routers

Hi, FYI. RFC 9288, "Recommendations on the Filtering of IPv6 Packets Containing IPv6 Extension

8/18/22

6/2/22

[ipv6hackers] IPv6 Addressing Considerations (IETF Internet-Draft)

Hi, We have published a revision of our IETF Internet-Draft "IPv6 Addressing Considerations

unread,

[ipv6hackers] IPv6 Addressing Considerations (IETF Internet-Draft)

Hi, We have published a revision of our IETF Internet-Draft "IPv6 Addressing Considerations

6/2/22

9/16/21

[ipv6hackers] Fwd: [v6ops] RFC 9098 on Operational Implications of IPv6 Packets with Extension Headers

Folks, FYI, just published: RFC 9098 Title: Operational Implications of IPv6 Packets with Extension

unread,

[ipv6hackers] Fwd: [v6ops] RFC 9098 on Operational Implications of IPv6 Packets with Extension Headers

Folks, FYI, just published: RFC 9098 Title: Operational Implications of IPv6 Packets with Extension

9/16/21

7/14/21

[ipv6hackers] Webinar on "IPv6 Network Reconnaissance" (Today, July 14 2021, 16:00 UTC-0300)

Folks, Just in case you find it of use: Webinar: "IPv6 Network Reconnaissance" Speaker:

unread,

[ipv6hackers] Webinar on "IPv6 Network Reconnaissance" (Today, July 14 2021, 16:00 UTC-0300)

Folks, Just in case you find it of use: Webinar: "IPv6 Network Reconnaissance" Speaker:

7/14/21

Fernando Gont, John Mann3

7/6/21

[ipv6hackers] IPv6 Mythology (webinar)

On 22/6/21 19:29, John Mann wrote: > Fernando, > > Was this webinar recorded? Yep: * IPv6

unread,

[ipv6hackers] IPv6 Mythology (webinar)

On 22/6/21 19:29, John Mann wrote: > Fernando, > > Was this webinar recorded? Yep: * IPv6

7/6/21

Fernando Gont, Antonios Atlasis2

6/12/21

[ipv6hackers] Operational Implications of IPv6 Extension Headers (Fwd: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-ehs-packet-drops-08.txt)

Congrats Fernando This is great news Regards On Fri, 11 Jun 2021 at 21:46, Fernando Gont <fernando

unread,

[ipv6hackers] Operational Implications of IPv6 Extension Headers (Fwd: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-ehs-packet-drops-08.txt)

Congrats Fernando This is great news Regards On Fri, 11 Jun 2021 at 21:46, Fernando Gont <fernando

6/12/21

3/3/21

[ipv6hackers] PATCH: Implementation of RFC 8981 for OpenBSD's slaacd(8)

Folks, I've implemented the remaining bits of RFC 8981 for OpenBSD's slaacd(8). (other parts

unread,

[ipv6hackers] PATCH: Implementation of RFC 8981 for OpenBSD's slaacd(8)

Folks, I've implemented the remaining bits of RFC 8981 for OpenBSD's slaacd(8). (other parts

3/3/21

2/28/21

[ipv6hackers] Fwd: RFC 8981 on Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6

Folks, RFC 8981, entitled "Temporary Address Extensions for Stateless Address Autoconfiguration

unread,

[ipv6hackers] Fwd: RFC 8981 on Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6

Folks, RFC 8981, entitled "Temporary Address Extensions for Stateless Address Autoconfiguration

2/28/21

2/13/21

[ipv6hackers] IP protocol 41 feed

Friends, Apologies if you've seen this from me already. This information can be considered safe

unread,

[ipv6hackers] IP protocol 41 feed

Friends, Apologies if you've seen this from me already. This information can be considered safe

2/13/21

2/12/21

[ipv6hackers] Fwd: IPv6 addressing: Gaps? (draft-gont-v6ops-ipv6-addressing-considerations)

Folks, FYI. The intent is to discuss this on the IETF v6ops wg list (https://www.ietf.org/mailman/

unread,

[ipv6hackers] Fwd: IPv6 addressing: Gaps? (draft-gont-v6ops-ipv6-addressing-considerations)

Folks, FYI. The intent is to discuss this on the IETF v6ops wg list (https://www.ietf.org/mailman/

2/12/21

Fernando Gont, no...@null.net2

12/15/20

[ipv6hackers] Fwd: Protocol Action: 'Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6' to Proposed Standard (draft-ietf-6man-rfc4941bis-12.txt)

On Mon Dec 14, 2020 at 03:35:49PM -0300, Fernando Gont wrote: > >It has been four years of work

unread,

[ipv6hackers] Fwd: Protocol Action: 'Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6' to Proposed Standard (draft-ietf-6man-rfc4941bis-12.txt)

On Mon Dec 14, 2020 at 03:35:49PM -0300, Fernando Gont wrote: > >It has been four years of work

12/15/20

12/11/20

[ipv6hackers] Fwd: IPv6 Addressing Considerations

Folks, FYI. Comments welcome! Cheers, Fernando -------- Forwarded Message -------- Subject: IPv6

unread,

[ipv6hackers] Fwd: IPv6 Addressing Considerations

Folks, FYI. Comments welcome! Cheers, Fernando -------- Forwarded Message -------- Subject: IPv6

12/11/20

12/8/20

[ipv6hackers] MItigating slaac-renum problems at CPE routers (Fwd: Pretty Please? - Disposition of draft-ietf-v6ops-cpe-slaac-renum-05)

Folks, You're probably aware about the problems that can arise in SLAAC deployments as a result

unread,

[ipv6hackers] MItigating slaac-renum problems at CPE routers (Fwd: Pretty Please? - Disposition of draft-ietf-v6ops-cpe-slaac-renum-05)

Folks, You're probably aware about the problems that can arise in SLAAC deployments as a result

12/8/20

10/20/20

[ipv6hackers] IETF I-D: "Operational Implications of IPv6 Packets with Extension Headers" (Fwd: [v6ops] WGLC on draft-ietf-v6ops-ipv6-ehs-packet-drops)

Folks, A Working Group Last Call (WGLC) has been started for our IETF ID "Operational

unread,

[ipv6hackers] IETF I-D: "Operational Implications of IPv6 Packets with Extension Headers" (Fwd: [v6ops] WGLC on draft-ietf-v6ops-ipv6-ehs-packet-drops)

Folks, A Working Group Last Call (WGLC) has been started for our IETF ID "Operational

10/20/20

Fernando Gont, … Gert Doering5

10/14/20

[ipv6hackers] CVE-2020-16898: "Bad Neighbor" (IPv6 SLAAC/RDNSS)

Hi, Gert, On 14/10/20 14:42, Gert Doering wrote: > Hi, > > On Wed, Oct 14, 2020 at 07:06:

unread,

[ipv6hackers] CVE-2020-16898: "Bad Neighbor" (IPv6 SLAAC/RDNSS)

Hi, Gert, On 14/10/20 14:42, Gert Doering wrote: > Hi, > > On Wed, Oct 14, 2020 at 07:06:

10/14/20

9/13/20

[ipv6hackers] Fwd: [Int-area] BCP 230, RFC 8900 on IP Fragmentation Considered Fragile

Hi, Folks, FYI, BCP 230, RFC 8900 on IP Fragmentation Considered Fragile * IETF RFC: https://www.rfc-

unread,

[ipv6hackers] Fwd: [Int-area] BCP 230, RFC 8900 on IP Fragmentation Considered Fragile

Hi, Folks, FYI, BCP 230, RFC 8900 on IP Fragmentation Considered Fragile * IETF RFC: https://www.rfc-

9/13/20

6/28/20

[ipv6hackers] (fwd) Adoption Call for "Improving the Robustness of Stateless Address Autoconfiguration (SLAAC) to Flash Renumbering Events"

Folks, The 6man chairs have started a WG call for adoption of our document "Improving the

unread,

[ipv6hackers] (fwd) Adoption Call for "Improving the Robustness of Stateless Address Autoconfiguration (SLAAC) to Flash Renumbering Events"

Folks, The 6man chairs have started a WG call for adoption of our document "Improving the

6/28/20

5/19/20

[ipv6hackers] slaac-renum: New rev of draft-gont-6man-slaac-renum (Fwd: New Version Notification for draft-gont-6man-slaac-renum-08.txt)

Folks, We have posted a revision of draft-gont-6man-slaac-renum. It is available at: https://www.ietf

unread,

[ipv6hackers] slaac-renum: New rev of draft-gont-6man-slaac-renum (Fwd: New Version Notification for draft-gont-6man-slaac-renum-08.txt)

Folks, We have posted a revision of draft-gont-6man-slaac-renum. It is available at: https://www.ietf

5/19/20

4/2/20

[ipv6hackers] FreeBSD implementation of RFC4941bis

Folks, I've also implemented RFC4941bis for FreeBSD. The resulting code is smaller and simpler

unread,

[ipv6hackers] FreeBSD implementation of RFC4941bis

Folks, I've also implemented RFC4941bis for FreeBSD. The resulting code is smaller and simpler

4/2/20

4/2/20

[ipv6hackers] An implementation of RFC4941bis

Folks, I did a patch to the Linux kernel (net-next) to implement the upcoming revision of RFC4941 (

unread,

[ipv6hackers] An implementation of RFC4941bis

Folks, I did a patch to the Linux kernel (net-next) to implement the upcoming revision of RFC4941 (

4/2/20

4/2/20

[ipv6hackers] Fwd: [v6ops] WG Last Call on draft-ietf-v6ops-cpe-slaac-renum

Hello, folks, Long time no hear! I hope all of you and your beloved ones are fine in these crazy

unread,

[ipv6hackers] Fwd: [v6ops] WG Last Call on draft-ietf-v6ops-cpe-slaac-renum

Hello, folks, Long time no hear! I hope all of you and your beloved ones are fine in these crazy

4/2/20

4/1/20

[ipv6hackers] Test (please ignore)

Test -- Fernando Gont SI6 Networks e-mail: fg...@si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2

unread,

[ipv6hackers] Test (please ignore)

Test -- Fernando Gont SI6 Networks e-mail: fg...@si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2

4/1/20

1/29/20

[ipv6hackers] RFC 7112 style fragment handling of major OSs

Group, I hope everybody is well. RFC 8200 sect 4.5 contains a paragraph that mandates (well, with a

unread,

[ipv6hackers] RFC 7112 style fragment handling of major OSs

Group, I hope everybody is well. RFC 8200 sect 4.5 contains a paragraph that mandates (well, with a

1/29/20

1/10/20

[ipv6hackers] SLAAC renumbering problems (Fwd: [v6ops] draft-gont-v6ops-slaac-renum **Call for adoption**)

Folks, A while ago some of us started working on an IETF draft to document and mitigate some issues

unread,

[ipv6hackers] SLAAC renumbering problems (Fwd: [v6ops] draft-gont-v6ops-slaac-renum **Call for adoption**)

Folks, A while ago some of us started working on an IETF draft to document and mitigate some issues

1/10/20

Search

Clear search

Close search

Google apps

Main menu