From f668b435207db36cefef7962e90f1973851ed2b5 Mon Sep 17 00:00:00 2001 From: minima Date: Tue, 11 Jan 2005 15:54:57 +0000 Subject: [PATCH] make the licensing change to the perl Artistic licence recast the aranea protocol document, this is wip. --- COPYING | 498 ++++++++++++------------------------------- html/index.html | 2 +- techdoc/protocol.pod | 210 +++++++++--------- 3 files changed, 232 insertions(+), 478 deletions(-) diff --git a/COPYING b/COPYING index d3744a42..5f221241 100644 --- a/COPYING +++ b/COPYING @@ -1,367 +1,131 @@ -******************************************************************************* - - NO WARRANTY - - BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY -FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN -OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES -PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED -OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF -MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS -TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE -PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, -REPAIR OR CORRECTION. - - IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING -WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR -REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, -INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING -OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED -TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY -YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER -PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE -POSSIBILITY OF SUCH DAMAGES. - - -******************************************************************************* - - - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 - - Copyright (C) 1989, 1991 Free Software Foundation, Inc. - 675 Mass Ave, Cambridge, MA 02139, USA - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - Preamble - - The licenses for most software are designed to take away your -freedom to share and change it. By contrast, the GNU General Public -License is intended to guarantee your freedom to share and change free -software--to make sure the software is free for all its users. This -General Public License applies to most of the Free Software -Foundation's software and to any other program whose authors commit to -using it. (Some other Free Software Foundation software is covered by -the GNU Library General Public License instead.) You can apply it to -your programs, too. - - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -this service if you wish), that you receive source code or can get it -if you want it, that you can change the software or use pieces of it -in new free programs; and that you know you can do these things. - - To protect your rights, we need to make restrictions that forbid -anyone to deny you these rights or to ask you to surrender the rights. -These restrictions translate to certain responsibilities for you if you -distribute copies of the software, or if you modify it. - - For example, if you distribute copies of such a program, whether -gratis or for a fee, you must give the recipients all the rights that -you have. You must make sure that they, too, receive or can get the -source code. And you must show them these terms so they know their -rights. - - We protect your rights with two steps: (1) copyright the software, and -(2) offer you this license which gives you legal permission to copy, -distribute and/or modify the software. - - Also, for each author's protection and ours, we want to make certain -that everyone understands that there is no warranty for this free -software. If the software is modified by someone else and passed on, we -want its recipients to know that what they have is not the original, so -that any problems introduced by others will not reflect on the original -authors' reputations. - - Finally, any free program is threatened constantly by software -patents. We wish to avoid the danger that redistributors of a free -program will individually obtain patent licenses, in effect making the -program proprietary. To prevent this, we have made it clear that any -patent must be licensed for everyone's free use or not licensed at all. - - The precise terms and conditions for copying, distribution and -modification follow. - - GNU GENERAL PUBLIC LICENSE - TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION - - 0. This License applies to any program or other work which contains -a notice placed by the copyright holder saying it may be distributed -under the terms of this General Public License. The "Program", below, -refers to any such program or work, and a "work based on the Program" -means either the Program or any derivative work under copyright law: -that is to say, a work containing the Program or a portion of it, -either verbatim or with modifications and/or translated into another -language. (Hereinafter, translation is included without limitation in -the term "modification".) Each licensee is addressed as "you". - -Activities other than copying, distribution and modification are not -covered by this License; they are outside its scope. The act of -running the Program is not restricted, and the output from the Program -is covered only if its contents constitute a work based on the -Program (independent of having been made by running the Program). -Whether that is true depends on what the Program does. - - 1. You may copy and distribute verbatim copies of the Program's -source code as you receive it, in any medium, provided that you -conspicuously and appropriately publish on each copy an appropriate -copyright notice and disclaimer of warranty; keep intact all the -notices that refer to this License and to the absence of any warranty; -and give any other recipients of the Program a copy of this License -along with the Program. - -You may charge a fee for the physical act of transferring a copy, and -you may at your option offer warranty protection in exchange for a fee. - - 2. You may modify your copy or copies of the Program or any portion -of it, thus forming a work based on the Program, and copy and -distribute such modifications or work under the terms of Section 1 -above, provided that you also meet all of these conditions: - - a) You must cause the modified files to carry prominent notices - stating that you changed the files and the date of any change. - - b) You must cause any work that you distribute or publish, that in - whole or in part contains or is derived from the Program or any - part thereof, to be licensed as a whole at no charge to all third - parties under the terms of this License. - - c) If the modified program normally reads commands interactively - when run, you must cause it, when started running for such - interactive use in the most ordinary way, to print or display an - announcement including an appropriate copyright notice and a - notice that there is no warranty (or else, saying that you provide - a warranty) and that users may redistribute the program under - these conditions, and telling the user how to view a copy of this - License. (Exception: if the Program itself is interactive but - does not normally print such an announcement, your work based on - the Program is not required to print an announcement.) - -These requirements apply to the modified work as a whole. If -identifiable sections of that work are not derived from the Program, -and can be reasonably considered independent and separate works in -themselves, then this License, and its terms, do not apply to those -sections when you distribute them as separate works. But when you -distribute the same sections as part of a whole which is a work based -on the Program, the distribution of the whole must be on the terms of -this License, whose permissions for other licensees extend to the -entire whole, and thus to each and every part regardless of who wrote it. - -Thus, it is not the intent of this section to claim rights or contest -your rights to work written entirely by you; rather, the intent is to -exercise the right to control the distribution of derivative or -collective works based on the Program. - -In addition, mere aggregation of another work not based on the Program -with the Program (or with a work based on the Program) on a volume of -a storage or distribution medium does not bring the other work under -the scope of this License. - - 3. You may copy and distribute the Program (or a work based on it, -under Section 2) in object code or executable form under the terms of -Sections 1 and 2 above provided that you also do one of the following: - - a) Accompany it with the complete corresponding machine-readable - source code, which must be distributed under the terms of Sections - 1 and 2 above on a medium customarily used for software interchange; or, - - b) Accompany it with a written offer, valid for at least three - years, to give any third party, for a charge no more than your - cost of physically performing source distribution, a complete - machine-readable copy of the corresponding source code, to be - distributed under the terms of Sections 1 and 2 above on a medium - customarily used for software interchange; or, - - c) Accompany it with the information you received as to the offer - to distribute corresponding source code. (This alternative is - allowed only for noncommercial distribution and only if you - received the program in object code or executable form with such - an offer, in accord with Subsection b above.) - -The source code for a work means the preferred form of the work for -making modifications to it. For an executable work, complete source -code means all the source code for all modules it contains, plus any -associated interface definition files, plus the scripts used to -control compilation and installation of the executable. However, as a -special exception, the source code distributed need not include -anything that is normally distributed (in either source or binary -form) with the major components (compiler, kernel, and so on) of the -operating system on which the executable runs, unless that component -itself accompanies the executable. - -If distribution of executable or object code is made by offering -access to copy from a designated place, then offering equivalent -access to copy the source code from the same place counts as -distribution of the source code, even though third parties are not -compelled to copy the source along with the object code. - - 4. You may not copy, modify, sublicense, or distribute the Program -except as expressly provided under this License. Any attempt -otherwise to copy, modify, sublicense or distribute the Program is -void, and will automatically terminate your rights under this License. -However, parties who have received copies, or rights, from you under -this License will not have their licenses terminated so long as such -parties remain in full compliance. - - 5. You are not required to accept this License, since you have not -signed it. However, nothing else grants you permission to modify or -distribute the Program or its derivative works. These actions are -prohibited by law if you do not accept this License. Therefore, by -modifying or distributing the Program (or any work based on the -Program), you indicate your acceptance of this License to do so, and -all its terms and conditions for copying, distributing or modifying -the Program or works based on it. - - 6. Each time you redistribute the Program (or any work based on the -Program), the recipient automatically receives a license from the -original licensor to copy, distribute or modify the Program subject to -these terms and conditions. You may not impose any further -restrictions on the recipients' exercise of the rights granted herein. -You are not responsible for enforcing compliance by third parties to -this License. - - 7. If, as a consequence of a court judgment or allegation of patent -infringement or for any other reason (not limited to patent issues), -conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot -distribute so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you -may not distribute the Program at all. For example, if a patent -license would not permit royalty-free redistribution of the Program by -all those who receive copies directly or indirectly through you, then -the only way you could satisfy both it and this License would be to -refrain entirely from distribution of the Program. - -If any portion of this section is held invalid or unenforceable under -any particular circumstance, the balance of the section is intended to -apply and the section as a whole is intended to apply in other -circumstances. - -It is not the purpose of this section to induce you to infringe any -patents or other property right claims or to contest validity of any -such claims; this section has the sole purpose of protecting the -integrity of the free software distribution system, which is -implemented by public license practices. Many people have made -generous contributions to the wide range of software distributed -through that system in reliance on consistent application of that -system; it is up to the author/donor to decide if he or she is willing -to distribute software through any other system and a licensee cannot -impose that choice. - -This section is intended to make thoroughly clear what is believed to -be a consequence of the rest of this License. - - 8. If the distribution and/or use of the Program is restricted in -certain countries either by patents or by copyrighted interfaces, the -original copyright holder who places the Program under this License -may add an explicit geographical distribution limitation excluding -those countries, so that distribution is permitted only in or among -countries not thus excluded. In such case, this License incorporates -the limitation as if written in the body of this License. - - 9. The Free Software Foundation may publish revised and/or new versions -of the General Public License from time to time. Such new versions will -be similar in spirit to the present version, but may differ in detail to -address new problems or concerns. - -Each version is given a distinguishing version number. If the Program -specifies a version number of this License which applies to it and "any -later version", you have the option of following the terms and conditions -either of that version or of any later version published by the Free -Software Foundation. If the Program does not specify a version number of -this License, you may choose any version ever published by the Free Software -Foundation. - - 10. If you wish to incorporate parts of the Program into other free -programs whose distribution conditions are different, write to the author -to ask for permission. For software which is copyrighted by the Free -Software Foundation, write to the Free Software Foundation; we sometimes -make exceptions for this. Our decision will be guided by the two goals -of preserving the free status of all derivatives of our free software and -of promoting the sharing and reuse of software generally. - - NO WARRANTY - - 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY -FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN -OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES -PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED -OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF -MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS -TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE -PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, -REPAIR OR CORRECTION. - - 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING -WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR -REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, -INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING -OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED -TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY -YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER -PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE -POSSIBILITY OF SUCH DAMAGES. - - END OF TERMS AND CONDITIONS - - Appendix: How to Apply These Terms to Your New Programs - - If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make it -free software which everyone can redistribute and change under these terms. - - To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -convey the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. - - - Copyright (C) 19yy - - This program is free software; you can redistribute it and/or modify - it under the terms of the GNU General Public License as published by - the Free Software Foundation; either version 2 of the License, or - (at your option) any later version. - - This program is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU General Public License for more details. - - You should have received a copy of the GNU General Public License - along with this program; if not, write to the Free Software - Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. - -Also add information on how to contact you by electronic and paper mail. - -If the program is interactive, make it output a short notice like this -when it starts in an interactive mode: - - Gnomovision version 69, Copyright (C) 19yy name of author - Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. - This is free software, and you are welcome to redistribute it - under certain conditions; type `show c' for details. - -The hypothetical commands `show w' and `show c' should show the appropriate -parts of the General Public License. Of course, the commands you use may -be called something other than `show w' and `show c'; they could even be -mouse-clicks or menu items--whatever suits your program. - -You should also get your employer (if you work as a programmer) or your -school, if any, to sign a "copyright disclaimer" for the program, if -necessary. Here is a sample; alter the names: - - Yoyodyne, Inc., hereby disclaims all copyright interest in the program - `Gnomovision' (which makes passes at compilers) written by James Hacker. - - , 1 April 1989 - Ty Coon, President of Vice - -This General Public License does not permit incorporating your program into -proprietary programs. If your program is a subroutine library, you may -consider it more useful to permit linking proprietary applications with the -library. If this is what you want to do, use the GNU Library General -Public License instead of this License. + + + + + The "Artistic License" + + Preamble + +The intent of this document is to state the conditions under which a +Package may be copied, such that the Copyright Holder maintains some +semblance of artistic control over the development of the package, +while giving the users of the package the right to use and distribute +the Package in a more-or-less customary fashion, plus the right to make +reasonable modifications. + +Definitions: + + "Package" refers to the collection of files distributed by the + Copyright Holder, and derivatives of that collection of files + created through textual modification. + + "Standard Version" refers to such a Package if it has not been + modified, or has been modified in accordance with the wishes + of the Copyright Holder as specified below. + + "Copyright Holder" is whoever is named in the copyright or + copyrights for the package. + + "You" is you, if you're thinking about copying or distributing + this Package. + + "Reasonable copying fee" is whatever you can justify on the + basis of media cost, duplication charges, time of people involved, + and so on. (You will not be required to justify it to the + Copyright Holder, but only to the computing community at large + as a market that must bear the fee.) + + "Freely Available" means that no fee is charged for the item + itself, though there may be fees involved in handling the item. + It also means that recipients of the item may redistribute it + under the same conditions they received it. + +1. You may make and give away verbatim copies of the source form of the +Standard Version of this Package without restriction, provided that you +duplicate all of the original copyright notices and associated disclaimers. + +2. You may apply bug fixes, portability fixes and other modifications +derived from the Public Domain or from the Copyright Holder. A Package +modified in such a way shall still be considered the Standard Version. + +3. You may otherwise modify your copy of this Package in any way, provided +that you insert a prominent notice in each changed file stating how and +when you changed that file, and provided that you do at least ONE of the +following: + + a) place your modifications in the Public Domain or otherwise make them + Freely Available, such as by posting said modifications to Usenet or + an equivalent medium, or placing the modifications on a major archive + site such as uunet.uu.net, or by allowing the Copyright Holder to include + your modifications in the Standard Version of the Package. + + b) use the modified Package only within your corporation or organization. + + c) rename any non-standard executables so the names do not conflict + with standard executables, which must also be provided, and provide + a separate manual page for each non-standard executable that clearly + documents how it differs from the Standard Version. + + d) make other distribution arrangements with the Copyright Holder. + +4. You may distribute the programs of this Package in object code or +executable form, provided that you do at least ONE of the following: + + a) distribute a Standard Version of the executables and library files, + together with instructions (in the manual page or equivalent) on where + to get the Standard Version. + + b) accompany the distribution with the machine-readable source of + the Package with your modifications. + + c) give non-standard executables non-standard names, and clearly + document the differences in manual pages (or equivalent), together + with instructions on where to get the Standard Version. + + d) make other distribution arrangements with the Copyright Holder. + +5. You may charge a reasonable copying fee for any distribution of this +Package. You may charge any fee you choose for support of this +Package. You may not charge a fee for this Package itself. However, +you may distribute this Package in aggregate with other (possibly +commercial) programs as part of a larger (possibly commercial) software +distribution provided that you do not advertise this Package as a +product of your own. You may embed this Package's interpreter within +an executable of yours (by linking); this shall be construed as a mere +form of aggregation, provided that the complete Standard Version of the +interpreter is so embedded. + +6. The scripts and library files supplied as input to or produced as +output from the programs of this Package do not automatically fall +under the copyright of this Package, but belong to whoever generated +them, and may be sold commercially, and may be aggregated with this +Package. If such scripts or library files are aggregated with this +Package via the so-called "undump" or "unexec" methods of producing a +binary executable image, then distribution of such an image shall +neither be construed as a distribution of this Package nor shall it +fall under the restrictions of Paragraphs 3 and 4, provided that you do +not represent such an executable image as a Standard Version of this +Package. + +7. C subroutines (or comparably compiled subroutines in other +languages) supplied by you and linked into this Package in order to +emulate subroutines and variables of the language defined by this +Package shall not be considered part of this Package, but are the +equivalent of input as in Paragraph 6, provided these subroutines do +not change the language in any way that would cause it to fail the +regression tests for the language. + +8. Aggregation of this Package with a commercial distribution is always +permitted provided that the use of this Package is embedded; that is, +when no overt attempt is made to make this Package's interfaces visible +to the end user of the commercial distribution. Such use shall not be +construed as a distribution of this Package. + +9. The name of the Copyright Holder may not be used to endorse or promote +products derived from this software without specific prior written permission. + +10. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR +IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED +WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. + + The End diff --git a/html/index.html b/html/index.html index a1df95db..ef9866f0 100644 --- a/html/index.html +++ b/html/index.html @@ -86,7 +86,7 @@ Last modified: Mon Dec 29 20:45:18 GMT 2003

- Copyright © 1998 by Dirk Koopman G1TLH. All Rights Reserved
+ Copyright © 1998-2004 by Dirk Koopman G1TLH. All Rights Reserved
 $Id$ diff --git a/techdoc/protocol.pod b/techdoc/protocol.pod index 3c3ccdcc..1a017376 100644 --- a/techdoc/protocol.pod +++ b/techdoc/protocol.pod @@ -1,3 +1,4 @@ +# -*- perl -*- =head1 NAME Aranea Orthogonal Communications Protocol @@ -6,7 +7,7 @@ $Revision$ =head1 SYNOPSIS - ,,,,,|,... + ,,,|,... =head1 ABSTRACT @@ -65,24 +66,31 @@ can only be sent escaped. This is described further in the L and L. Most of this document is concerned with the L, however -some L which all implementation should issue and +some L which all implementations should issue and must accept are described. =head1 Applications In the past messaging applications such as DX Cluster software have maintained -a fairly strict division between "nodes" and "users". This protocol attempts +a fairly strict division between Ls and Ls". This protocol attempts to get away from that distinction by allowing any entity to connect to any other. Applications that use this protocol are essentially all peers and therefore -nodes the only real difference between a "node" and a "user" (using this -protocol) is that a "node" has one or more listeners running that will, -potentially, allow incoming connections. A "user" simply becomes an end -point that never uses the L or L slots in the -L. +nodes the only real difference between Ls and Ls is that a "node" has one or more +listeners running that will, +potentially, allow incoming connections, from other Ls, Ls or Ls -The reason for this is that modern clients are more intelligent than simple +Any application that is a sink and/or source of data for Ls, is capable of obeying +the protocol message construction rules and understands how to deduplicate incoming messages +correctly can operate as a routeable entity in this protocol. It is called an L. + +An L is called a L if it accepts connections from Ls and is +prepared to route messages on their behalf to other Ls or L. In addition it +may provide some other, usually simpler, interface (eg simple telnet access) for direct user access. + +The concept of an L has been invented because modern clients are +capable of being intelligent than simple character based connections such as telnet or ax25. They wish to be able to distinguish between the various classes of message, such as: DX spots, announces, talk, logging info etc. It is a pain to have to do it, as now, @@ -90,18 +98,38 @@ by trying to make sense of the (slightly different for each piece of node software) human readable "user" version of the output. Far better to pass on regular, specified, easily computer decodable versions of the message, i.e. in this protocol, and leave -the human presentation to the client software. +the human presentation to the application implementing the L. -Having said that, the protocol allows for traditional, character based, -connections, as in the past. But it is up to applications -to service and control that type of connection and to provide human readable -"user" output. - -One of the legacy, character based connections that will probably have to be -serviced is that of existing PC protocol based nodes. They should be treated -as local clients, B as peers in this protocol. It is likely that, in order +It also helps to modularise the various interfaces that may be implemented such +as the legacy, character based connections of existing PC protocol based nodes. +They should be treated +as local clients, in fact as Ls, B as peers in this protocol. It is likely that, in order to do this, some extra Ls will need to be defined at application level. +=head1 Connection Types + +=head2 User + +A L is a connection to a L (that allows such connections) +that does not occur in protocol. All Ls shall be identified with a name +of up to 12 characters in the set [-0-9A-Z_]. All messages have to be routed via the +L to which this L is connected. + +=head2 Endpoint + +An L is a connection to a L that uses the protocol. From a routing point of +view, it is indistiguishable from a L. The L is responsible for creating and decoding +well formed protocol messages. An L does not route beyond the immediate L(s) to +which it is connected. It may also be a L connected to a L which provides some +addressable service that can be queried. + +=head2 Node + +A L is connected to other Ls. It is responsible for routing messages in protocol +from other Ls or Ls, whether directly connected or not. Optionally, a L +may provide other interfaces, such as direct L connections or legacy PC protocol speaking +DX Clusters. + =head1 Routing Section The application that implements this protocol is essentially a line @@ -114,24 +142,29 @@ AX25. Having said that: in context, L in this protocol could be multi/broadcast, either "as is" or wrapped in some other framing protocol. -Because this is an unreliable, best effort, "please route my packets -through your node" protocol, there is no guarantee that a message +Although the physical transport between Ls is reliable, the actual message +is unreliable, because this is an unreliable, best effort, "please route my packets +through your node" protocol. There is no guarantee that a message will get to the other side of a mesh of nodes. There may be a discontinuity either caused by outage or deliberate filtering. However, as it is envisaged that most L will be flood routed or, -in the case of directed L (those that have L and/or +in the case of directed L (those that have L and/or L fields) down some/most/all interfaces showing a route for that direction, it is unlikely that L will be lost in practice. +Assuming that there is a path between all the Ls in a network, then it is guaranteed +that a message will be delivered everywhere, eventually. It is possible (indeed likely) that +copies of a message +will arrive at Ls more than once. Ls are responsible for deduplicating those messages +using the information in the L. + =head2 Field Description -Only the first three fields in the L are compulsory -and indicate that this is a broadcast to be sent to all nodes coming -from the L. If the message needs to be identified as coming -from a user on a node, then the L field is added. +The first four fields in the L are compulsory. However, +a client connection can -Adding a L and/or L field will restrict the destinations +Adding a L and/or L field will restrict the destinations or recipients that receive this message. The L field is incremented on receipt of a message on a node. @@ -154,11 +187,37 @@ More detailed descriptions of the fields follow: =item B This is a compulsory field. It is the name of the originating node. -The field can contain up to 12 characters in the set [-A-Z0-9_] in +The field can contain up to 12 characters in the set [-A-Z0-9_/] in any order. Higher layers may restrict this further. The field must not be changed by any other node. +=item B + +This is the Group (or Channel) to be used for this data. It is compulsory. There +is always a L + +It is a string of up to 12 characters +in the set [-A-Z0-9_] in any order. Optionally, for extra routing to +a specific end point (node or user), it may have another 12 character +field in the same set, concatenated with the string, separated by a ':' +character. + +This field is used either to indicate particular node destination +or to differentiate this broadcast in some way by making this +message as a member of a L. Any message can be sent +down any L. The names of Ls and their usage +is entirely up to the implementor. + +It is assumed that node names can be differentiated from user +names and L names. + +If the field is set to a particular node destination, it will +be routed (rather than broadcast) to that node. However, any +intervening nodes are free to duplicate the message and send +it down more than one, likely looking, interface - depending on any +network policies that may pertain. + =item B This is a compulsory field. It is a 10 hexadecimal digit string which @@ -192,76 +251,10 @@ Implementations may have an upper limit to this field and may silently drop incoming L with a L count greater than the limit. -=item B -This field is optional. It is the identifier of the originating -user. If it is missing then the message is -assumed to come from the originating node itself. - -It can consist of up to 12 characters in the set [-A-Z0-9_] -in any order. Higher layers may restrict this further. - -=item B - -This field is optional. It is a string of up to 12 characters -in the set [-A-Z0-9_] in any order. - -This field is used either to indicate particular node destination -or to differentiate this broadcast in some way by making this -message as a member of a L. Any message can be sent -down any L. The names of Ls and their usage -is entirely up to the implementor. - -It is assumed that node names can be differentiated from user -names and L names. - -If the field is set to a particular node destination, it will -be routed (rather than broadcast) to that node. However, any -intervening nodes are free to duplicate the message and send -it down more than one, likely looking, interface - depending on any -network policies that may pertain. - -=item B - -This field is optional. It is a string of up to 12 characters -in the set [-A-Z0-9_] in any order. Higher layers may restrict -this further. - -Conventionally this field is used to indicate the user to whom -this message is directed. In an ideal world the L field -will be set, by the originating node, to the identifier of the node -on which this user resides. - -If the L field is not set then this message will be -broadcast. However, should a node become apparent (on route) -then nodes are free to fill in the L field and proceed -with a more directed approach. - -If it becomes apparent (on route) that there may be more than -one possible L destination for a L then a node -may duplicate the message (keeping the same L) and -route it onwards. Because of the L inherent in -the system, it is indeterminate as to which destination will -receive the message. It is possible for all or just some -destinations to receive the message. The tuple (L, -L) will determine uniqueness. - -This field can, in the case where L -is set to the name of a node, be set to a L. If this -is the case then this will cause this message to be sent to -a L on the L node only. =back -=head2 Channel - -Channels are a concept very similar to that on IRC. It is a -way of segregating data flows in a network. In principle, subject -to local policy or application requirements, any data (or -L) can be sent down any channel. - -It is up to the implementation whether to use this feature or not. - =head2 Routing It is assumed that nodes will be connected in a looped network with @@ -307,35 +300,32 @@ duplicated! =head2 Examples # on link startup from GB7BAA (both sides hello) - GB7TLH,3D02350001,0|HELLO,Aranea,1.2,24.123 - GB7BAA,3D02355421,1|HELLO,Aranea,1.1,23.245 + GB7TLH,ROUTE,3D02350001,0|HELLO,Aranea,1.2,24.123 + GB7BAA,ROUTE,3D02355421,1|HELLO,Aranea,1.1,23.245 # on user startup to GB7TLH - GB7TLH,3D042506F2,0,G1TLH|HELLO,PClient,1.3 + GB7TLH,ROUTE,3D042506F2,0,G1TLH|HELLO,PClient,1.3 # on user disconnection - GB7TLH,3D9534F32D,0,G1TLH|BYE + GB7TLH,ROUTE,3D9534F32D,0,G1TLH|BYE # a talk (actually 'text') message to a user (some distance away # from the origin node) - GB7TLH,3D03450019,3,G1TLH,GB7BAA,G8TIC|T,Hiya Mike what's happening? + GB7TLH,G8TIC,3D03450019,3|T,G1TLH,Hiya Mike what's happening? - # a talk/chat/text message to a channel or group - GB7TLH,0413525F23,2,G1TLH,VHF|T,2m is opening on MS + # a talk/chat/text message to a Group + GB7TLH,VHF,0413525F23,2|T,G1TLH,2m is opening on MS # a ping to find the whereabouts and distance of a user from a node # the hex number on the end is the ping ID - GB7TLH,1512346543,0,,,G7BRN|PING,9F4D - - # the same from a user on GB7TLH - GB7TLH,1512346543,0,G1TLH,,G7BRN|PING,23 + GB7TLH,G7BRN,1512346543,0|PING,G1TLH,9F4D # this effectively asks whether the user is on-line on a particular node - GB7TLH,1512346543,0,G1TLH,GB7DJK,G7BRN|PING,35DE + GB7TLH,GB7BAA:G7BRN,1512346543,0|PING,G1TLH,35DE # A possible reply, same ID as ping followed by the no of hops on the - # ping that was received - GB7DJK,1512450534,3,G7BRN,GB7TLH,G1TLH|PONG,35DE,3 + # ping that was received thus telling you how far away it is. + GB7BAA,G1TLH,1512450534,3|PONG,G7BRN,35DE,3 =head1 Command Section @@ -448,7 +438,7 @@ disconnected. =item B - PING, + PING,, Command to send a ping to a node or user. This command is used both by the software and users to determine a) whether a node or user exists and b) how good the path is @@ -460,7 +450,7 @@ will identify this ping using the tuple (L,) as unique. =item B - PONG,, + PONG,,, Command to reply to a ping. This is sent as a reply to an incoming ping command. The is the one supplied and the is the number of @@ -481,7 +471,7 @@ Dirk Koopman, G1TLH, Edjk@tobit.co.ukE =head1 COPYRIGHT AND LICENSE -Copyright 2004 by Dirk Koopman, G1TLH +Copyright 2004-2005 by Dirk Koopman, G1TLH This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. -- 2.43.0