I think that rel="sitemap" ought to be in the IANA Link Relations registry.

More details at:

https://github.com/protocol-registries/link-relations/issues/72

#IANA #Standards #WebDev #SemanticWeb #HTML

RE: https://oldbytes.space/@drscriptt/116219403988667257

I’m trying to use data from IANA to dynamically create things that use / act on the list of networks / addresses published by #IANA. E.g.

• route statements
• firewall rules
• ACL entries in BIND (named) config files
• etc

The data exists in a (mostly) portable format. Why shouldn’t I use it?

Isn’t that one of the points of publishing data like this?

TIL that #xsltproc (on my system) only supports #XSLT version 1.1.

I learned this because the `replace( … )` function apparently requires XSLT version 2.0.

I want the `replace( … )` function because #IANA put two comma separated addresses in one record while all the others are a single address.

The node the addresses are in is named “address” which seems singular to me.

But IANA put `192.0.0.170/32, 192.0.0.171/32 ` in an <address/> node.

Thanks IANA. 😒

<registry>
<registry>
<!-- … -->
<record>
<address>…</address>
<!-- … -->
</record>
<!-- … -->
</registry>
</registry>

No, I have no idea why <registry/> is nested the way that it is.

https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xml

Oh, hey, #IANA assigned a new block of ASNs to #AFRINIC. A good sign that the #Internet #connectivity in #Africa is growing! Keep up the good work! Details here....

#ASN #BGP

#IANA's Well-Known URIs ( https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml ) show how modern infrastructure is expected to work. #Automation, #ZeroTouch provisioning, and #ZeroTrust rely on predictable /.well-known/* endpoints and assume trustworthy #DNS resolution.

Discovery has moved up the stack and spans multiple layers while DNS remains the foundation. Failures surface elsewhere, when DNS is the root cause, making troubleshooting harder and turning “boring DNS” into a prerequisite for automation and architectures.

Just scraping the #IANA assigned TLDs and the corresponding documented #nameservers. What I don't get is, why so many companies apply for a #TLD. It's not particularly cheap to apply for one of those ngTLDs, yet compared to the company sizes, it's probably pennies. Is it a prestige investment? Is it a digital resource to grab, before someone else does it?

Other than #Microsoft, #Google, and #AWS, I've rarely seen any ngTLD representing a corporation's name to actually be used in practice.

Does anyone in the #infosec community share their view?

#askfedi #askmasto #askinfosec #DNS

RE: https://chaos.social/@joergi/115594789795742237

Please answer if you know about TLDs/IANA:

if you really wanna #unplugtrump and don't want to have a domain in the US for anti-censorship:
if you look at https://www.iana.org/domains/root/db/chanel.html
the Sponsoring Organisation & Administrative Contact are in the EU, which is good
but the Technical Contact is in the US.

So is it then really save? and: the complete IANA /ICANN are in the US - so does it matter at all?

#trump #sovereignty #digitalsovereignty #digitalAutonomy #tld #domain #domains #iana #ICANN

The conclusion is inescapable: Allowing an armed group to control a country's internet is not a "local issue." It is a direct threat to global security, endangering everyone from people on the ground to ships at sea.

ccTLDs are public infrastructure, not spoils of war. #ICANN #IANA, stop enabling this dangerous precedent. Your silence has consequences. #FreeDotYE

What if a militia owned your country's internet?

In Yemen, Houthis seized .YE in 2014-2015, weaponizing .gov.ye for threats & phishing, even costing kids' lives via botched aid.

ICANN calls it a "local issue." Our new blog exposes the digital ghost state & demands action.

Read:
https://freethedotye.org/blog/when-militia-owns-ye/

#FreeDotYE #ICANN
#IANA #internet #DigitalRights