Ugh

[kajer@infosec.exchange]

Ugh

https://www.ietf.org/archive/id/draft-thain-ipv8-00.html

[da_667@infosec.exchange]

@kajer 🤮

[kajer@infosec.exchange]

@da_667 JFC this is just IPv6 with more requirements.

[kajer@infosec.exchange]

@da_667 IPv8 == IPv4+IPv4

wtf are these people thjinking?@

[mark@mastodon.fixermark.com]

@kajer I am willing to volunteer for my company's project to change over, but only if I'm allowed to call it "PROJECT MORE CORN!!!"

[kajer@infosec.exchange]

@da_667

holy shit, :RIP: the entire network when you local zone server gets popped.

17.2. Tier 2 - L2 Network Device
L2 devices MUST implement: 802.1Q trunking, VLAN auto- creation on tagged traffic, management VRF (VLAN 4090), OOB VRF (VLAN 4091), switch port OAuth2 binding, LLDP, NetLog8 client, ARP8 (management plane only), ICMPv8 (management plane only), PVRST, Zone Server as PVRST root capability, sticky MAC binding, Zone Server MAC notification.

17.3. Tier 3 - L3 Network Device
L3 devices MUST implement: All Tier 1 requirements, eBGP8, IBGP8, OSPF8, IS-IS8 (available), static routes, VRF (full), XLATE8 (mandatory on edge devices), WHOIS8 resolver, ACL8 gateway enforcement, Zone Server services (if Zone Server role), PVRST root capability, switch port OAuth2 binding support.

17.4. Spanning Tree - PVRST Mandatory
...

[kajer@infosec.exchange]

@da_667

LOLOL

OOB VRF (VLAN 4091)

ummmm, since when is a vlan "out of band"

Yeah, okay it didnt say airgap, and vlan4091 would not be involved in L3 traffic flows, but damn, defining vlan numbers for management ports seems, a little ... strict. Give me my dedicated mgmt0 interface any day.

[winterknight1337@infosec.exchange]

@kajer I actually can’t tell if this is a shitpost or if it’s legit.