= Сообщение: 1968 из 7124 ====================================== FTSC_PUBLIC = От : Stephen Hurd 1:103/1 29 Feb 16 23:59:30 Кому : mark lewis 29 Feb 16 23:59:30 Тема : FSP-1040.001 draft 0 FGHI : area://FTSC_PUBLIC?msgid=71.fido-ftscpubl@1:103/1+1b3a11a9 На : area://FTSC_PUBLIC?msgid=1:3634/12.73+56d4768f = Кодировка сообщения определена как: CP866 ================================== Ответ: area://FTSC_PUBLIC?msgid=1:3634/12.73+56d514fd ============================================================================== Re: FSP-1040.001 draft 0 By: mark lewis to Stephen Hurd on Mon Feb 29 2016 11:18 am
> with a PKT extension... this is, however, probably outside the range of this > document... i dunno...
Yeah, it was pretty clear it was outside the realm of "Type 2 compatible packet formats" and, if anyone actually uses it, should be documented in a different spec (since by definition it applies to non-type-2 packets).
> SH> Yeah, but it's not the mailers that do the negotiation, it's the > SH> tossers/packers. > > i don't see how they can do that without some sort of special PKTs addressed > to > the tosser where the tossers can communicate back and forth on their own > similar to the way operators can send areafix messages to the tossers and > the way that offline mail users can communicate with a BBS' offline mail
Basically, when you parse a packet, you save the capability word associated with the node. When it comes time to packetize, you look at your saved copy of *their* capability word, and pick the highest packet format that they support and use that format.
> :) that's ok, i can wait... i'd rather be able to point to certain things in > the most recent posted as they progress... personally i think it is a good > document so far... just a few tweaks here and there to enable it to stand > closer to being on its own...
I plan to post the next draft in a couple days to give slow routes time to provide feedback.
> SH> Anyway, the message body is defined as NUL terminated unlimited length > SH> and that's it. Other standards already define control paragraphs, and > SH> the rest of the things that are defined are presentation details, not > SH> packing details. No packer should need to worry about soft CRs for > SH> example. > > true... i agree... FTS-0001 covers more than just mail packers, though...
Yeah, but this is very much *not* a replacement for FTS-0001. I'm not the guy who's going to take that job on. No sir. This FSP is just for software dealing with packets. --- SBBSecho 2.32-FreeBSD * Origin: BBSDev.net - The BBS Developers Network (1:103/1)
