MSGID: 2:221/1.58@fidonet ef5149f2   
   REPLY: 1:153/7001 60734e81   
   PID: OpenXP/5.0.49 (Win32)   
   CHRS: ASCII 1   
   TZUTC: -0400   
   Hello Maurice Kinal!   
      
    MK> Your suggestion is perfectly valid but to be honest I still   
    MK> believe that a 32-bit hex value for the unixtime or rfc-868   
    MK> (seconds since 1900) is the best choice for uniqueness over   
    MK> the longest span which is much greater than the 3 year   
    MK> period required by the current standard.   
      
   But what if two or more systems process messages at exactly the     
   same time of the day?  A collision seems far more likely than if     
   the respective systems produce random 32 bit strings.   
      
    MK> Also it adds meaning to it beyond what is capable for a   
    MK> randomly generated serial number.  Unfortunetly it has a   
    MK> shelf life that is quickly running out whereas the random   
    MK> one doesn't.   
      
   Right. Therefore, I see two +1's for the random [a-z]|[A-Z]|[0-    
   9] version, and atleast one -1 for the time-serial version.   
      
   --   
     ../|ug   
      
   --- OpenXP 5.0.49   
    * Origin: Mobile? ASIAN_LINK https://preview.tinyurl.com/y6rwskq (2:221/1.58)   
   SEEN-BY: 1/123 18/200 90/1 105/81 114/705 120/340 123/120 131 124/5016   
   SEEN-BY: 129/305 153/250 154/10 203/0 220/70 221/1 6 360 226/17 30   
   SEEN-BY: 227/114 229/101 424 426 452 664 700 1016 1017 230/0 240/5832   
   SEEN-BY: 249/206 317 400 250/5 8 267/800 280/464 5003 282/1038 288/100   
   SEEN-BY: 292/8125 298/25 301/1 305/3 310/31 317/3 322/757 340/1000   
   SEEN-BY: 342/200 396/45 423/81 120 460/58 633/280 712/848 770/1 100   
   SEEN-BY: 770/330 340 772/210 220 230   
   PATH: 221/1 280/464 770/1 317/3 229/426