TZUTC: 1100   
   MSGID: 758.fdn_ipv6@3:633/509 23e586e1   
   REPLY: 2:280/5555 5f8025da   
   PID: Synchronet 3.18c-Linux  Sep 29 2020 GCC 8.3.0   
   TID: SBBSecho 3.11-Linux r3.179 Sep 29 2020 GCC 8.3.0   
   CHRS: ASCII 1   
   NOTE: SlyEdit 1.73 (2020-03-31) (ICE style)   
     Re: New one   
     By: Michiel van der Vlist to Deon George on Fri Oct 09 2020 10:56 am   
      
    DG>> Yeah, but they lay out packets to be sent using filesnames that are   
    DG>> named with a hex value, to represent the destination for the file.   
      
    MV> Some software does that. Your point?   
      
   You asked me to comment why my IPv6 represented my node number using hex   
   values and not decimals values.   
      
    DG>> Why do they need to know? If I went with SLAAC, it would be even more   
   confusing right?   
    MV> SLAAC numbers do not have the "f1d0" marker in the first 16 bits of the   
   host part.   
      
   I know - and it wouldnt represent my node number at all.   
      
    MV> Look, it is just a game among the members of the Fidonet IPv6 club. If   
   you want to be a spoilsport and play your own game by using   
    MV> hex instead of decimal for the node number part, then ... then you are on   
   your own...   
      
   I dont think I'm being a spoil sport, in fact I didnt know that this was a   
   game or there were rules to it? How would 2:5020/11200 represent their node   
   number in your IPv6 f1d0 hex game?   
      
   ...ëîåï   
      
   ... Spring is God's way of saying, One more time!   
   --- SBBSecho 3.11-Linux   
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)   
   SEEN-BY: 1/123 90/1 120/340 123/131 226/30 227/702 229/424 426 550   
   SEEN-BY: 229/664 1016 240/5832 249/206 317 400 317/3 322/757 342/200   
   SEEN-BY: 633/0 267 280 281 410 412 509 640/1384 712/848   
   PATH: 633/509 280 229/426