,

// new TLDs that are being proposed

DELEGATE

E-DELEGATE

L-DELEGATE

EDGE -> this TLD was OBSOLETED with -> ?????

E-EDGE -> this TLD was OBSOLETED with -> ?????

L-EDGE -> this TLD was OBSOLETED with -> ?????

LNL

E-LNL

L-LNL

LNE

E-LNE

L-LNE

LNF

E-LNF

L-LNF

E-ELE

E-EFE

E-ENE

E-ILLI

E-IFFI

E-INNI

// end of new TLDs

,

// the RFCs that you SHOULD read

RFC 4501 - DNS URI

RFC 7553 - URI record

RFC 2915 - NAPTR record

RFC 3401 - NAPTR record

RFC 3402 - NAPTR record

RFC 3403 - NAPTR record

RFC 3404 - NAPTR record

RFC 5205 - HIP record

RFC 8005 - HIP DNS

RFC 6742 - ILNP DNS

// end of RFCs

,

// DNS - URL and URN as per RFC 4501 https://tools.ietf.org/html/rfc4501 ,

dns://89.235.241.251:35353/ALTERNATE-IN-NEW-NAME-INTERNET.E-DELEGATE?class=IN;type=A

dns://89.235.241.251:35353/?class=IN;type=A

can we have an http server (tln-tix-tllix.delegate.yiff.fi) that
will make an DNS query to 89.235.241.251:35353
and then
when DNS query is received (3 or 4 times -> iterable ROOT NS only)
make an (FULL URN) or (COMPLETE URN) http 301 redirect to
EEEEEEE-FFFFFFF-LLLLLLL-YYYYYYY-UUUUUUU-NNNNNNN-HHHHHHH(.)EEEEEEE-FFFFFFF-LLLLLLL-YYYYYYY-UUUUUUU-NNNNNNN-HHHHHHH
is this possible?????
aka
let this http server (tln-tix-tllix.delegate.yiff.fi) be an ENTRY POINT
to our DNS based network
can we FREAKING have this?????
aka
as per these two RFCs
-- https://tools.ietf.org/html/draft-josefsson-dns-url-13 ,
-- https://tools.ietf.org/html/rfc4501 ,

// end of as per RFC

,

// DNS - IN NAPTR and IN URI as per RFC 7553 https://tools.ietf.org/html/rfc7553 ,

_service._proto.name. TTL class URI priority weight target

_ftp._tcp.example.net. 1 IN URI 115 114 "ftp://ftp-1.example.com/public/"

_domain._udp.delegate.yiff.fi. 1 IN URI 115 114 "domain://non-existent-domain.delegate.yiff.fi:35353/_index_/"

// end of as per RFC

,