TID: FMail-lnx64 2.1.0.18-B20170815
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: UTF-8 2
PID: GED+LNX 1.1.5-b20161221
MSGID: 2:280/464 622b09d7
REPLY: 2:240/1120.29 46810783
Hi Tim,

On 2022-03-10 23:01:40, you wrote to Michiel van der Vlist:

 TS> Well, as long as I have no indication that the result order of the OS
 TS> returned has any semantics at all (rather than beeing random) relying
 TS> on itmay worse than making an enducated guess. If you know some place
 TS> that defines that the order is actually a suggestion on priorities
 TS> that would be fine.

It took some google-ing, but I got your answer.

There is an extensive RFC written about this subject:

https://www.ietf.org/rfc/rfc3484.txt
(See paragraph 10.3 if you are in a hurry ;-))

Windows implements this RFC:

https://docs.microsoft.com/en-us/troubleshoot/windows-server/net
orking/configure-ipv6-in-windows

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 15/0 106/201 124/5016 129/331 153/757 7715 203/0 218/700
SEEN-BY: 221/0 229/110 317 426 428 664 700 266/512 280/464 5003 5555
SEEN-BY: 282/1038 292/854 8125 301/1 310/31 317/3 320/219 341/234
SEEN-BY: 396/45 460/58 712/848 770/1 2452/250
PATH: 280/464 712/848 229/426