= Сообщение: 2346 из 7124 ====================================== FTSC_PUBLIC = От : Alexey Vissarionov 2:5020/545 28 Mar 17 15:28:00 Кому : Michiel van der Vlist 28 Mar 17 15:28:00 Тема : Proposed changes: FTS-5001.006 FGHI : area://FTSC_PUBLIC?msgid=2:5020/545+58da56d1 На : area://FTSC_PUBLIC?msgid=2:280/5555+58da2813 = Кодировка сообщения определена как: CP866 ================================== Ответ: area://FTSC_PUBLIC?msgid=2:280/5555+58dba06a ============================================================================== Good ${greeting_time}, Michiel!
28 Mar 2017 11:06:50, you wrote to me:
FR>>> This method is not to be used to signal that a system is FR>>> IPV4 and IPv6 capable. Additional IPv6 capability should FR>>> be advertised by adding an AAAA record to an already FR>>> listed host name. AV>> Wrong. AV>> INA:192.0.2.123,INA:[2001:db8:f1d0::1234],IBN is a legal AV>> set of flags. MvdV> Maybe, but it is not common practise...
Hmmmm... Well, for now there are no literal IPv6 in the nodelist: % egrep 'INA:\[' ~/fido/etc/nodelist.ndl | wc -l 0
However, the abovequoted paragraph should look like:
==== yum ==== Multihomed systems or systems that are otherwise reacheable by more than one address, _may_ carry two or more INA flags. That can be used to provide some redundance, and the recommended way is to use the INA flags with different server names, each pointing to all IP addresses, so the nodelist entry with INA:fido.example.com,INA:fido.example.net flags may point to NS zone records like: