IPv6 and gemini

[plugd]

Sean Conner writes:

>> 4. Have servers ensure that if they have an AAAA record they also listen
>> for IPv6 gemini connections.
>>   - Pros: future-proof, no client-side changes necessary.
>>   - Con: some additional work necessary on the server side.
>
>   It depends.  On GLV-1.12556, all that takes is to use an address of "::"
> to listen on all IPv4 and IPv6 interfaces, and that should work with any
> modern IP stack.

I didn't want to presume. :-)

>   There is also a fifth option:
>
> 	5. Have clients attempt to connect to both addresses and use the one
> 	that connects first.
> 	- Pro: should always work
> 	- Con: complicates the client

Ideally this should already have been happening, but determining whether
a server is not listening is difficult, isn't it?  At some point you
have to simply define a timeout.  Which means that, unless you want
false negatives you have to wait a while (say a few seconds at least)
before declaring the connection a failure.  This is okay if it happens
once, but it'd be awful if this were happening for every single
selector.  Which means that clients would also have to implement some
local caching mechanism ...

>
>> Obviously 4 is my favourite because it's less (no) work for me. :)
>
>   I like 4 as well.

Yay!

plugd