TID: FMail-W32 2.1.3.7-B20170919   
   TZUTC: 0200   
   CHRS: UTF-8 4   
   PID: GED+W32 1.1.5-b20170303   
   MSGID: 2:280/5555 5d0a0ba3   
   REPLY: 1:3634/12.73 5d095e1b   
   Hello mark,   
      
   On Tuesday June 18 2019 17:53, you wrote to me:   
      
    MV>> What you requested was that binkd could be configured tp transmit   
    MV>> the information. "nodeinfo" can do that. All that is needed is   
    MV>> that the sysops adds the iformation to the "nodeinfo" line in   
    MV>> his/her binkd config.   
      
    ml> that does not cause binkd to transmit a PHN line like other systems   
    ml> do... how hard is this to understand???? :sigh:   
      
   The PHN line obviously is a relic from the POTS age. The "phone" keyword in   
   the config crearly indicate that it was meant for the phone number.   
      
   Binkd is the leading binkp implementation. Instead of sheepishly following   
   others it should lead. Progress is not just adding new stuff, it is also   
   getting rid of archaic ballast. Binkd does not use phone numbers. The PHN line   
   is archaic ballast. The makers of binkp were wise to ommit it. Using it for IP   
   information is improper use. The proper place for IP information is the NDL   
   line. That is were the capability flags are and IP info is conveyed as   
   parameter in an IP related flag. Like this:   
      
   nodeinfo CM,MO,IBN:fido.vlist.eu,RPK,NPK,ENC,NC,PING,IPv6   
      
   The PHN line is archaic ballast. IP info belongs in de NDL line.   
      
   How hard is that to understand?     
      
      
   Cheers, Michiel   
      
   --- Fmail, Binkd, Golded   
    * Origin: http://www.vlist.eu (2:280/5555)   
   SEEN-BY: 1/123 103/705 154/10 203/0 221/0 6 226/17 227/114 229/200   
   SEEN-BY: 229/275 354 426 1014 240/5832 249/307 317 280/464 5003 5555   
   SEEN-BY: 292/854 310/31 342/200 393/68 396/45 423/120 712/848 770/1   
   SEEN-BY: 2452/250 5019/40 5020/1042 5053/58   
   PATH: 280/5555 464 229/426