Synchronet v3.19b-Win32 (install) has been released (Jan-2022).

You can donate to the Synchronet project using PayPal.

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
ref:fidonet_packets [2017/02/28 17:52] – More links, moved timeline digital manref:fidonet_packets [2017/03/01 12:22] – [Specification Versions] more notes digital man
Line 26: Line 26:
  
 ^ Format   ^ Spec   ^ Version ^ File                                               ^ Notes ^ ^ Format   ^ Spec   ^ Version ^ File                                               ^ Notes ^
-| Type-2   | FTS-1  | 16      | [[http://ftsc.org/docs/fts-0001.016|FTS-0001.016]] | Derived from FSC-1, initially standardized at version 12 | +| Type-2   | FTS-1  | 16      | [[http://ftsc.org/docs/fts-0001.016|FTS-0001.016]] | Derived from FSC-1. Initially standardized at version 12. Supports 3D addresses. | 
-| Type-2e  | FSC-39 | 4       | [[http://ftsc.org/docs/fsc-0039.004|FSC-0039.004]] | The name "Type-2e" is being coined here in this article | +| Type-2e  | FSC-39 | 4       | [[http://ftsc.org/docs/fsc-0039.004|FSC-0039.004]] | Adds 4D address suppoort. The name "Type-2e" is being coined here in this article. | 
-| Type-2+  | FSC-48 | 2       | [[http://ftsc.org/docs/fsc-0048.002|FSC-0048.002]] | Packet header is loosely based on FSC-39 | +| Type-2+  | FSC-48 | 2       | [[http://ftsc.org/docs/fsc-0048.002|FSC-0048.002]] | Packet header is based on FSC-39 with improved backward compatibility with FTS-1. | 
-| Type-2.2 | FSC-45 | 1       | [[http://ftsc.org/docs/fsc-0045.001|FSC-0045.001]] | Packet header differs considerably from other Type-2 formats, but includes full 5D addressing |+| Type-2.2 | FSC-45 | 1       | [[http://ftsc.org/docs/fsc-0045.001|FSC-0045.001]] | Packet header differs considerably from other Type-2 formats. Supports 5D addresses. |
  
 +**NOTES:**
 +  * 3D addresses are normally expressed as "<zone>:<net>/<node>" (e.g. "1:103/705")
 +  * 4D addresses are normally expressed as "<zone>:<net>/<node>[.point]" (e.g. "1:103/705.1")
 +  * 5D addresses are normally expressed as "<zone>:<net>/<node>[.point]@<domain>" (e.g. "1:103/705@fidonet")
 +  * Type-2e (FSC-39) packets are often erroneously referred to as "Type-2+" packets: they are not ((FSC-39 packets lack the ''auxNet'' field specified in FSC-48)).
 ==== Timeline ==== ==== Timeline ====
  
Line 115: Line 120:
   danger that a point is seen as the boss node is eliminated.   danger that a point is seen as the boss node is eliminated.
  
 +Although, according to FSC-48, the ''auxNet'' field is not supposed to be initialized to a non-zero value unless the originating node is a point, some FidoNet mail software (e.g. Squish) will //always// set the ''auxNet'' field to the originating net value in Type-2+ packets.
 +
 +=== prodData ===
 +
 +Although FSC-39 defines this 4-byte field as containing "Whatever" and FSC-48 just says "Product specific filler", both Squish and Husky/areastat place the ASCII characters ''XPKT'' in this field. The significance of the ''XPKT'' string is unknown.
 ===== See Also ===== ===== See Also =====
   * [[http://ftsc.org/docs/fts-0001.016|FTS-1: A Basic FidoNet(r) Technical Standard, Randy Bush, version 16]]   * [[http://ftsc.org/docs/fts-0001.016|FTS-1: A Basic FidoNet(r) Technical Standard, Randy Bush, version 16]]

Trace: