Short: Network architecture standard Path: urmel!Sirius.dfn.de!darwin.sura.net!gatech!swrinde!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!spool.mu.edu!agate!ucbvax!ucdavis!iris From: dlarson@cbmvax.commodore.com (Dale Larson) Newsgroups: comp.sys.amiga.announce Subject: New SANA-II Spec Documents Available Keywords: Draft for Final Comment and Approval Message-ID: <10442@ucdavis.ucdavis.edu> Date: 16 Nov 91 05:48:54 GMT Sender: operator@ucdavis.ucdavis.edu Reply-To: dlarson@cbmvax.commodore.com (Dale Larson) Followup-To: comp.sys.amiga.datacomm,comp.sys.amiga.programmer Organization: Commodore, Amiga Networking Group, New Siberia Office Lines: 87 Approved: zerkle@cs.ucdavis.edu [ For those who don't know already, ab20 is the ftp archive site ] [ ab20.larc.nasa.gov (128.155.23.64). -Dan Z ] From the new documents: --- The SANA-II Network Device Driver Specification is a standard for the interface to any Amiga networking hardware. It is a specification for an Amiga software interface to the data link layer in the ISO 7-Layer Reference Model of Open Systems Interconnection. All Amiga network hardware vendors should supply a SANA-II device driver for their hardware. All protocol writers should talk to SANA-II device drivers rather than to network hardware. Any protocol stack should work with any SANA-II device driver. The standard has been kept simple and straight-forward so that SANA-II device drivers should be easy to write and to use. They should be highly efficient and have low resource usage. Any SANA-II device driver should behave very much like any other SANA-II device driver. Application writers must not use SANA-II Device Drivers directly. Applications must use the API provided by the network protocol software the application supports. It is hoped that a standard network API for all Amigas will be made available by Commodore in the near future. This version of the standard addresses issues from the original SANA-II standard which were raised in the 1991 North American and European Amiga DevCons as well as in the conversion of existing protocols to the use of the standard. This draft reflects several rounds of comments from active implementors of SANA-II software. Most of the changes are simplifications and should be easy to incorporate into any work in progress. The changes should make the writing and use of SANA-II drivers much easier. Commodore's internal versions of the A2065 and other drivers and the AS225 software package are currently compliant with this version of the SANA-II spec. This version of the specification is very solid and will stand as final unless comments containing very compelling objections are received by December 31, 1991. All SANA-II device drivers and software utilizing those drivers should be written to this version of the specification. Distribution of this version of the standard is unlimited. --- The new documents will be distributed in comp.souces.amiga and will be available from ab20 as: /usenet/comp.sources.amiga/volume91/devices/sana-ii-nov7/. Similar names on other archive sites. The documents also are or will be available for download from Bix and ADSP and will be distributed via other Amiga developer support mechanisms. Since the document archive was created, a few errata have been noted: --- SANA-II Network Device Driver Specification Errata to Version of November 7, 1991 for Final Comment and Approval It is important to test as many SANA-II devices as possible against as much SANA-II using software as possible. Commodore is interested in receiving evaluation and/or beta copies of any SANA-II using hardware and software developed by third parties, but makes no assurances regarding any testing which it may or may not perform with such evaluation copies. Evaluation copies should go to the same address as standards comments. The include files should list S2_ADDSTATIONALIAS and S2_DELSTATIONALIAS as invalid commands. The autodocs which indicate that ios2_Type is a pointer to type should be corrected to indicate that ios2_Type is the type, not a pointer. The CopyToBuff()/CopyFromBuff() autodocs should indicate that the length to be copied is a ULONG, not a LONG. The word "effect" in the CMD_FLUSH autodoc should be "affect." The beta a2065.device should properly implement CMD_FLUSH. It does not. -- Please see monthly postings for the disclaimer, the introduction, the charter, and submission instructions. Comments to zerkle@cs.ucdavis.edu. MAIL ALL SUBMISSIONS TO announce@cs.ucdavis.edu (don't auto-post).