<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">It seems sketchy to me to even retain client MAC information, no? Genuine question.<div class=""><br class=""></div><div class="">Didn’t we go to a distinct unique identifier system for this very reason?</div><div class=""><br class=""></div><div class="">Am I in the 1990s here or?</div><div class=""><br class=""></div><div class="">We’re just handing out addresses to UEs and things seem to work fine. For me personally, I find the notation of v6 to be very unasthetic, so I tend to just conceal it from myself now.</div><div class=""><br class=""><div class="">
<div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">-LB<br class=""><br class="">Ms. Lady Benjamin PD Cannon of Glencoe, ASCE<br class="">6x7 Networks & 6x7 Telecom, LLC <br class="">CEO <br class=""><a href="mailto:ben@6by7.net" class="">ben@6by7.net</a><br class="">"The only fully end-to-end encrypted global telecommunications company in the world.”</div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">ANNOUNCING: <a href="https://alexmhoulton.wixsite.com/6x7networks" class="">6x7 GLOBAL MARITIME</a></div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><br class="">FCC License KJ6FJJ<br class=""><br class=""></div><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><br class="Apple-interchange-newline" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;"><br class=""></span></div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Mar 19, 2022, at 3:56 PM, Matt Hoppes <<a href="mailto:mattlists@rivervalleyinternet.net" class="">mattlists@rivervalleyinternet.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class=""><br class="">On 3/19/22 6:50 PM, Michael Thomas wrote:<br class=""><blockquote type="cite" class="">On 3/19/22 3:47 PM, Matt Hoppes wrote:<br class=""><blockquote type="cite" class="">It has "features" which are at a minimum problematic and at a maximum show stoppers for network operators.<br class=""><br class="">IPv6 seems like it was designed to be a private network communication stack, and how an ISP would use and distribute it was a second though.<br class=""></blockquote>What might those be? And it doesn't seem to be a show stopper for a lot of very large carriers.<br class=""></blockquote><br class="">Primarily the ability to end-to-end authenticate end devices. The primary and largest glaring issue is that DHCPv6 from the client does not include the MAC address, it includes the (I believe) UUID.<br class=""><br class="">We have to sniff the packets to figure out the MAC so that we can authenticate the client and/or assign an IP address to the client properly.<br class=""><br class="">It depends how you're managing the network. If you're running PPPoE you can encapsulate in that. But PPPoE is very 1990 and has its own set of problems. For those running encapsulated traffic, authentication to the modem MAC via DHCP that becomes broken. And thus far, I have not seen a solution offered to it.<br class=""><br class=""><br class="">Secondly - and less importantly to deployment, IPv6 also provides a layer of problematic tracking for advertisers. Where as before many devices were behind a PAT, now every device has a unique ID -- probably for the life of the device. Marketers can now pinpoint down not just to an IP address that identifies a single NAT interface, but each individual device. This is problematic from a data collection standpoint.<br class=""><br class=""></div></div></blockquote></div><br class=""></div></body></html>