@LlanOldDog @larse The dual also exists: I-Ds lingering in "revised I-D needed" after AD reviews :-( or standing in AUTH48 for more than 48 hours 🙄 As a community, we should be more focus & energised indeed.
@ollieatnccgroup It is just an individual draft, i.e., it is not something the IETF is working on it and less a standard. See also https://t.co/B1SEH5NhxY
And for many reasons, I strongly doubt that the IETF will seriously consider it.
There is a recent IETF _DRAFT_ (not standard) about using part of 127/8 as global unicast: draft-schoen-intarea-unicast-127.
But, my latest MacOS and Linux boxes has 127/8 bound to the loopback. How could a 10-year IoT communicate with such an address?
@ollieatnccgroup At least, this IETF _DRAFT_ not standard won't fly with current Linux:
# ping 127.1.1.1
PING 127.1.1.1 (127.1.1.1) 56(84) bytes of data.
64 bytes from 127.1.1.1: icmp_seq=1 ttl=64 time=0.107 ms
When @IETF standards help the EU to have the European Green Certificate (aka coronapass).
https://t.co/eEAE4ov8jT
has more explanations and an online QR code decoder.
I'm quite a fan of the new privacy labels on Apple appstore to see how iOS apps use my data. Data collection is broken down by data used to track users, data linked to users, and data not linked to users. Here's what the 3 meeting apps look like for data linked to the user.
Do We Need a New IP? I.e., a centralized top-down ITU-T style or mode bottom-up with IETF. Good down-to-the-Earth write-up. — RIPE Labs https://t.co/3mUJWLrHqj
Finally, it seems that spotify has started its trip from the legacy Internet to the #IPv6 world: https://t.co/Q3okvevXvB
Thanks to @yogurtboy for the info.
🔔 Come & discuss a variety of #IPv6 topics during our "IPv6 State of Play Day"! Our agenda is already online including @bcp38_ @webernetz@evyncke@NicoSchottelius 🔔
https://t.co/SUQnk7wV6r
Last day, last session, after a big party at Cisco Live Barcelona, and an advanced topic on #IPv6 security: still 80 participants in the room.
Caught my flight back ::1 by 15 minutes...