LLL
L
L
LL
K
P
LP
char* name = "POS" 
LPLKKKSince no sentient life has been found on Mars, the codethis is a joke, right?
points that would have been allocated for Martian imojis are hereby
allocated for this private use. These addresses are thus called
"Martians", also known as "Bogons" due to them being bogus.
LKKK
LKIPv6 addresses no longer need to be typed as hex values --I mean that seems like it's a joke, right?
instead, the glyph for the script character, symbol, emoji, or
imoji representing that address can be input by the user, and it
will be displayed by the application as the graphic itself. From
the user's perspective, this will also be more compact than the
representation described in RFC 1924 [RFC1924].
LK
Tyes hello computer connect me to
f4
LKLKKKK
To address this need, the high-order bit of the 128-bit code point
space SHALL be reserved to indicate multicast. All valid code points
(i.e., IPv6 addresses) will thus have multicast counterparts. For
example, the code point allocated foris U+1F408. The
multicast group U+8000000000000000000000000001F408 is thus for
content about cats. Note that this is for general cat content --
other code points are allocated for specific cat content, such as joy
cat, grinning cat, pouty cat, etc. For an individual cat like
Garfield, setting the high-order bit to the code point allocated for
:garfield: will indicate that it is multicast content about Garfield.
KSource-specific multicast also plays a role; for example, joining the
:garfield: multicast group and restricting it to a source of
:garfield: results in only receiving content about Garfield, from
Garfield.
T
delete that RFCKOf course this will also drive the need to frequentlyok, I'm convinced. It's a joke
upgrade networking hardware, resulting in a boost to the global
economy, and thus a reduction in global warming.
T
KOne improvement to routing that MAY be considered is for scenicyeah it's a joke
routing as defined by RFC 7511 [RFC7511]. With emojis and imojis
being available for addressing, we can now specify which exact type
of scenery to visit along the way, or even which exact avian carrier
[RFC6214] to ride with. Note that avian carriers as described in RFC
1149 [RFC1149] are not supported, since they only support IPv4.
KTKKKLLT
KKI love it lmao
- Objections to Be Dismissed
Lchar* name = "POS"delete that RFC