TZUTC: 0000   
   MSGID: 53590.syncprog@1:103/705 2d902a51   
   REPLY: 15669.dove-syncprog@12:1/2 2d8e806a   
   PID: Synchronet 3.21a-FreeBSD master/1c123cf4a Oct 24 2025 Clang 19.1.7   
   TID: SBBSecho 3.32-Linux master/ec8f7009f Nov 15 2025 GCC 12.2.0   
   BBSID: BBSDEV   
   CHRS: CP437 2   
   FORMAT: flowed   
   NOTE: FSEditor.js v1.105   
     Re: src/tith/standards/TSP-0001.txt   
     By: deon to Deuce on Fri Nov 28 2025 01:47 pm   
      
    > Is this RFC 1464 that you speak of?   
    >   
    > It makes sense when the attribute=value is a "subset" of the think you are   
    > querying, but you are using it twice which seems duplicative(?) to me.   
      
   Yeah, the RFC seems to be written assuming you would pile all the TXT records   
   into a single key and get a big reply and pick them all apart.  This isn't   
   great for UDP DNS resolution since it would quickly grow larger than the MTU   
   and be much more susceptible to packet loss.   
      
   Existing uses generally use a single-letter bit before the = so they're   
   minimally compliant, which I guess makes sense... so n= for sysop name and f=   
   for iflags.  It's mostly there so it doesn't get eaten by strictly comforming   
   DNS servers that would drop a TXT record without an = in it.   
      
    > sysop=deon, and os=linux and bbs=synchronet, etc, but if I was to query   
    > _sysop_alterant.bbs.dege.au, I would have thought it to be a better answer   
    > to just say "deon", since sysop is the attribute I want to get the answer   
    > to.   
      
   Yeah, "n=deon" is about the shortest it can be... updating the doc now.   
      
    > RFC8552 I think is written with this approach in mind. Anyway, no biggie,   
    > just providing feedback in case it might be useful.   
      
   Adding 8552 to references and switching the second _ to a -.   
      
   Definately useful feedback.   
   ---   
    þ Synchronet þ The future of BBSing   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 10/0 1 13/0 102/401 103/705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 129/14 153/7715 154/110 214/22 218/0 1 215 700 810 226/30   
   SEEN-BY: 227/114 229/110 206 317 400 426 428 470 700 705 266/512 280/464   
   SEEN-BY: 291/111 301/1 320/219 322/757 342/200 396/45 460/58 633/280   
   SEEN-BY: 712/848 902/26 5075/35   
   PATH: 103/705 218/700 229/426