All IP Addresses Are Equal? "dot-zero" Addresses Are Less Equal
• 4 min read
In theory, all IP addresses are the same, and you can allocate them at random without a problem. 192.168.1.2 is certainly not better or worse than 192.168.1.15, right? But, in practice, certain IP addresses are regarded as "special" by some implementations and do not yield the same user experience.…
“These are all good points. I especially like the idea of search suggestions. Another useful refinement would be to default search results newest first and oldest last. At the moment, documents and pages are mixed together and not ordered by date. This can make searching for the one document you want a real slog.”
As an example, searching "IP address" returns the RIPE NCC Activity Plan 2012 :-)
Many people visiting RIPE Web site have a RIPE Access account. Are there plans to use their search history to provide context, which helps a lot in Web search? (And also raises a lot of touchy privacy issues. IMHO, "anonymous" users, those not logged in RIPE Access must be excluded of this feature. But the privacy issue also holds for logged-in users.)
I'm not sure about the consequences. Does it mean that Afrinic could lose its accreditation?
I like the IP address 2610:a1:1072::1:42 since the name is an IDN. But, alas, no DNSSEC.
"They may also receive more spam and phishing e-mails, since modern e-mail security protocols rely on DNSSEC as well." I would like to see email servers use SPF, DKIM and DMARC records only if they have been validated with DNSSEC but I strongly doubt it is the case today.
Developping something new (no installed base) and mission-critical in C, today, is a bit strange. Why not using a safer language?
Nice and useful article. For OpenDNSSEC, the important parameter is named Jitter and is enabled by default. Check that you have something like "<Policy name="default">...<Signatures>... <Jitter>PT12H</Jitter>" It would be nice to document here how it is done for other signing programs.
Great survey, thanks for this work. Indeed, the variations in EDE are funny. For bogus.bortzmeyer.fr, Unbound (and 1.1.1.1) say "9 (DNSKEY Missing)", 9.9.9.9 say "10 (RRSIGs Missing)" and Knot-Resolver say "12 (NSEC Missing)"
"The IP to CO2 Intensity API allows you to query an IP address" The second link actually goes to a service that takes a host name, not an IP address.
A good thing about the IETF is that it is open and discussions are public so here is the link to the discussion inside the IETF about this article: https://mailarchive.ietf.org/arch/msg/ietf/M2vDMHuj063n5jvcUydcr0oRWy0/
Showing 54 comment(s)