r 3
Message #3 
Date: Wed, 24 Apr 1996 08:43:08 +0300 (EET DST)
From: Heikki Hannikainen <oh7lzb@zone.pspt.fi>
To: oh7lzb@oh7rba.pspt.fi
Subject: Re: CluLink protocol, initial specs (fwd)


Okay ... Just a FEW comments about your specs, Heikki. I think FromNode
information can be avoided in some protocol.

....
[snip]
....
 2  - Delete node(s)
      FromNode: Callsign
          - Where the link was lost
      Reason: String[30]
          - Why (eg. "Shutdown", "Disconnected by operator" ...)
      NodeCalls: Callsign(s) of the nodes

What did you thing about some "hard defined" reason ? Shutdown, Disconnect by
operator, Hard disconnect etc ... are the term usually in use. And we can
let the possibility to send some special reason.

This information is completly ignored in DxNet at the present time ... :-))

....
[snip]
....

> 3  - Add user(s)
>      FromNode: Callsign
>      User record:
>        UserCall: Callsign
>        User flags: word-sized bitmask:
>           Bit  Meaning              State:  1                0
>           0    Here status:                 Here             Away
>           1    Privileged user:             Privileged       Not privileged
>           2    System operator:             Operator         Not operator
>           3    Superuser (sysop, pwd given) Superuser        Not superuser
>
> 4  - Delete user(s)
>      FromNode: Callsign
>      User callsigns

FromNode ... Not necessary, because normally only one DxCluster is allowed
at anytime. It it not a problem to look for a user in any of the DxCluster
table.

> 10 - Change user flags
>      FromNode: Callsign
>      FromUser: Callsign
>      User flags: word-sized bitmask


FromNode ... same as above

> 11 - Change user data
>      FromNode: Callsign
>      FromUser: Callsign
>      Data type: Byte:
>                   1 - Name          (Maximum length 22 characters)
>                   2 - QTH           (80 characters)
>                   3 - Coordinates
>                   4 - Home node callsign (for mail forwarding, 9 chars)
>      Data string: String

FromNode ... Absolutly not necessary
                   
> --- 64  - 95  ---  DX cluster messages
>
> 64 - DX info
>      FromNode: Callsign
>      FromUser: Callsign
>      DxFreq: Fixed-point unsigned integer, 4 bytes
>          - Frequency of the DX station in KHz, multiplied by 10 (eg. one
>            decimal included). An integer is used to prevent rounding
>            errors.
>      DxCall: String, max. 16 bytes
>          - Callsign of the DX station. Max. 15 bytes long.
>      Date/Time: Datetime
>      Info: String, max. 81 bytes
>          - Additional information string, max. 80 bytes

FromNode (again:-) ... True, is this case we need it (because of possibility
of limited protocol)

And so on for the next protocol (65, 66, 67 ...)

....
[snip]
....

That's all for now.

------------------------------------------------------
Olivier Le Cam
Email : olecam@imaginet.fr (or f5mzn@imaginet.fr)
AX25  : F5MZN@F6KPF.FBRE.FRA.EU
------------------------------------------------------


(#3) >
