DNS/TXT records to resolve kulfi://amitu.com

[amitu]

Multiple TXT records for a domain

So this is SPF TXT records are parsed:

Starting with the set of records that were returned by the lookup,
discard records that do not begin with a version section of exactly
"v=spf1". Note that the version section is terminated by either an
SP character or the end of the record. As an example, a record with
a version section of "v=spf10" does not match and is discarded.

If the resultant record set includes no records, check_host()
produces the "none" result. If the resultant record set includes
more than one record, check_host() produces the "permerror" result.

So you can add one or more TXT records on a domain in DNS, and they are effectively returned as single field, each unique TXT record is separated by a new line.

v=kulfi0 http=<id52>

All the TXT records on a domain, that starts with v=kulfi0 http=<id52> belongs to us. Each record can contain <name>=<id52> mapping. If the name is http it means this site is accessible via kulfi:// protocol, and the given id52 should be used to contact it.

Tomorrow we also want to allow mysql kulfi+mysql://foo.com etc, which will work by looking at id52 pointed at by the name mysql.

More then one TXT record lines can start with v=kulfi0 and the name field can also be duplicated with different id52 values. In case of multiple values, we will pick one at random, and if it fails use the fallback.

v=kulfi0 http=<id52-1> http-fallback=<id52-2>

If <protocol>-fallback is provided, the fallback will be used if primary failed for that protocol.

Authenticated DNS: v=kulfi0 ns=<id52>

If the txt record ns (name server) is found, the names that are missing in DNS will be looked up in the ns record over a DNS like protocol on top of kulfi network. Since all requests done in kulfi network have client certificates, this can be used to only allow discovery of services to authenticated users.