Text 1831, 179 rader
Skriven 2004-04-17 07:22:00 av Scott Little (3:712/848)
Ärende: FSP-1015.001 -> FTS-1025.001.rc3 (diff)
===============================================
5,13c5,13
< Publication:    FSP-1015
< Revision:       1
< Title:          Simple E-Mail Attach Transport (S.E.A.T.)
< Author:         Charles Cruden,
<                 Vincent Danen,
<                 Brent Shellenberg
<                 Ramon van der Winkel
< Revision Date:  20 April 2000
< Expiry Date:    20 April 2002
-+-
> Publication:  FTS-1025
> Revision:     1, RC-3
> Title:        Simple E-Mail Attach Transport (S.E.A.T.)
> Author:       Charles Cruden,
>               Vincent Danen,
>               Brent Shellenberg
>               Ramon van der Winkel
> Issue Date:   15 April 2004
> Review Date:  15 May 2004
16,23c16,23
<                 1. The Purpose
<                 2. Reading this document
<                 3. Implementation
<                 4. Specifying compliancy
<                 5. Required implementation
<                 6. Recommended implementation
<                 7. Optional implementation
<                 8. Last Notes
-+-
>               1. The Purpose
>               2. Reading this document
>               3. Implementation
>               4. Specifying compliancy
>               5. Required implementation
>               6. Recommended implementation
>               7. Optional implementation
>               8. Last Notes
30c30
<   This document is a Fidonet Standards Proposal (FSP).
-+-
>   This document is a Fidonet Technical Standard (FTS).
33,34c33
<   the Fidonet community, and requests discussion and suggestions for
<   improvements.
-+-
>   the Fidonet community.
70,74c69,70
<   what a properly formatted S.E.A.T. message looks like. Unlike other
<   technical documents, this approach makes it easier to get a visual
<   idea of how the whole thing works. Any paragraph that contains a
<   pipe character (|) prior to the start of a line, indicates that the
<   information in that portion of the document is new to this revision.
-+-
>   what a properly formatted S.E.A.T. message looks like, making it
>   easier to get a visual idea of how the whole thing works.
252,256c248,257
<     The CRC value expected here is one which does NOT invert the bits
<     at the end of calculation.  Implementers are referred to the CRC
<     routines provided as part of the JAM API for sample
<     implementations. These can often be located in a file called
<     JAMAPI.ZIP.
-+-
>     The algorithm used here is based on the polynomial 0x04C11DB7 (or
>     the reflected version, 0xEDB88320), with an initial CRC value of
>     0xFFFFFFFF and finalised by an XOR with 0xFFFFFFFF.  This is
>     compatible with [JAM], PKZIP, Zmodem, Ethernet and many others.
>
>     Implementers are referred to [ISO 3309] or [ITU-T V.42] for the
>     formal CRC32 specification, [RFC 1952] or [RFC 2823] for sample
>     code, and "A PAINLESS GUIDE TO CRC ERROR DETECTION ALGORITHMS"
>     [Williams93] for a detailed explanation of table-driven CRC
>     algorithms.
429,430c430,431
<   first method is similar the ACK procedures for dealing with getting a
<   resend of an individual file segment. The second method is for
-+-
>   first method is similar the ACK procedures for dealing with getting
>   a resend of an individual file segment. The second method is for
479,480c480,481
<   sending system (as in the case of echomail bundles or TIC files). SEAT
<   provides a method for the sender to tell the receiver that the
-+-
>   sending system (as in the case of echomail bundles or TIC files).
>   SEAT provides a method for the sender to tell the receiver that the
768,769c769,770
<     FILEMASK.EXT may contain any valid DOS filename or wildcards, and may
<     be accompanied by a password such as:
-+-
>     FILEMASK.EXT may contain any valid DOS filename or wildcards, and
>     may be accompanied by a password such as:
788,792c789,793
<     are referred to RFC 1321 for an implementation of MD5.)  Nearly all
<     errors in  transmission will be detected by discrepancies in the
<     value given here and the one calculated on the reconstructed message.
<     This field can be used in addition to the Ftn-Crc32 field for
<     verifying a file has arrived intact.  It should not be used in
-+-
>     are referred to RFC 1321 for an implementation of MD5.)  Nearly
>     all errors in  transmission will be detected by discrepancies in
>     the value given here and the one calculated on the reconstructed
>     message. This field can be used in addition to the Ftn-Crc32 field
>     for verifying a file has arrived intact.  It should not be used in
865,866c866,867
< A. Author contact data
< ----------------------
-+-
> A. References
> -------------
868,870c869,893
<   Charles Cruden
<   Fidonet: 1:342/806
<   E-mail:  cruden@cs.ualberta.ca
-+-
>   JAM
>     "Joaquim-Andrew-Mats Message Base Proposal" Revision 1, 1993.
>
>   ISO 3309
>     International Organization for Standardization, "Information
>     Processing Systems--Data Communication High-Level Data Link
>     Control Procedure--Frame Structure", ISO 3309, October 1984,
>     3rd Edition.
>
>   ITU-T V.42
>     International Telecommunications Union, Error-correcting
>     Procedures for DCEs Using Asynchronous-to-Synchronous Conversion,
>     ITU-T Recommendation V.42, 1994, Rev. 1.
>
>   RFC 1952
>     "GZIP file format specification version 4.3"
>
>   RFC 2823
>     "PPP over Simple Data Link (SDL) using SONET/SDH with ATM-like
>     framing"
>
>   Williams93
>     "A PAINLESS GUIDE TO CRC ERROR DETECTION ALGORITHMS" version 3.
>     Ross N. Williams, 19 August 1993
>     ftp://ftp.rocksoft.com/papers/crc_v3.txt
872,874d894
<   Vincent Danen
<   Fidonet: 1:140/14
<   E-mail:  vdanen@accessweb.com
876,878c896,897
<   Brent Shellenberg
<   Fidonet: 1:229/606
<   E-mail:  brents@shaw.wave.ca
-+-
> B. Author contact data
> ----------------------
880,882c899,900
<   Ramon van der Winkel
<   Fidonet: n/a
<   E-mail:  ramon@wsd.wline.se
-+-
>   Charles Cruden
>   Fidonet: 1:342/806
885c903
< B. History
-+-
> C. History
888,889c906,910
<   Rev.1, 20002004: First release as FSP
<
-+-
>   Rev.1, 20040515: Initial release (was: FSP-1015.001).
>                    FTSC changes:
>                      * Fixed formatting & removed FSP annotations.
>                      * Added references for CRC32 algorithm.
>                      * Removed obsolete author contact information.
892d912
<



-- Scott Little  [fidonet#3:712/848 / sysgod@sysgod.org]

--- GoldED+/W32 1.1.5-31012
 * Origin: Cyberia: 100% Grade "A" mansteak baby. (3:712/848)