INTERNET-DRAFT Lance Dodd Category: Experimental K. C. Jones 1 April 2004 Transmission of IP Datagrams over Token-Rail Ethernet draft-dodd-token-rail-00.txt This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC 2026. Internet-Drafts are working documents of the Internet Engineering Task Force(IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Copyright Notice Copyright (C) The Internet Society (2004). All Rights Reserved. Abstract This memo describes an experimental method for the transmission of IP datagrams oven token-rail ethernet. This specification is primarily useful in Metropolitan Area Networks, but can be applied in economies of scale (N, HO, WIDE, O, and others). This is an experimental, not recommended standard. Distribution of this memo is unlimited. Much of the rural United States while enjoying many modern conveniences is still quite limited in the available choices for broadband internet connectivity. This could be remedied by the use of an infrastructure that has existed virtually untapped for its communications potential. The continued advances in DSP technology, multiple frequency encoding and general alloy based metallurgy leads to the inevitable conclusion: using encoded signals transmitted over the information super railway could provide much needed relief to users in rural areas. Dodd, et al. Experimental [Page 1] INTERNET-DRAFT IP over Token-Rail 1 April 2004 Table of Contents 1. Introduction............................................... 2 1.1 Advantage ........................................... 2 1.2 Topology............................................. 2 1.3 Standards............................................ 2 1.4 Physical Deployment.................................. 2 1.5 Collision Avoidance.................................. 2 1.6 Switching ........................................... 2 1.7 Service ..............................................2 2. Frame Format and encoding...................................3 2.1 Alpabet...............................................3 2.2 Numbers...............................................3 2.3 Symbols...............................................3 3. Discussion..................................................3 4 Security ...................................................4 1. Introduction 1.1 Token Rail Ethernet can provide low delay, medium throughput, and low latency service. 1.2 The connection topology is limited to two point-to-point paths. 1.3 Switches may be incorporated into the rail network to provide queuing and QOS, at the cost of latency. 1.4 Standards and policies are easily manageable as all carriers are government subsidized. 1.5 There is limited space available to the carriers, it is allotted in continuous Right of Way across great distances. 1.6 The collision avoidance system is less than perfect but is bears no direct relation to the network unless a physical rail is completely broken 1.7 Connection oriented service are available in some cities, usually based upon a central hub/turntable/switch topology. Dodd, et al. Experimental [Page 2] INTERNET-DRAFT IP over Token-Rail 1 April 2004 2. Frame Format The common frame format is based on the basic ASCII character set with a translation table as follows : 2.1 Alphabet ._ A __. G __ M ... S _.__ Y _... B .... H _. N _ T __.. Z _._. C .. I ___ O .._ U _.. D .___ J .__. P ..._ V . E _._ K __._ Q .__ W .._. F ._.. L ._. R _.._ X 2.2 Numbers .---- 1 -.... 6 ..--- 2 --... 7 ...-- 3 ---.. 8 ....- 4 ----. 9 ..... 5 ----- 0 2.3 Symbols Point (.) .-.-.- (AAA) Comma (,) --..-- (MIM) Question-mark (?) ..--.. (IMI) Colon (:) ---... (OS) Hyphen (-) -....- (BA) Error ........ 3. Discussion Multiple types of service can be provided with a prioritized switch. The physical implementation of connectivity to the token-rail net may be left to the implementer Some accepted examples include: High Analog/Low Analog,( V!CC) Carrier Sense/Carrier Nonsense, High Tty/Low Tty The MTU is variable, and generally increases with signal voltage Typical MTU is not fixed but if receive window is not well tuned to incoming streams, retransmissions will certainly occur. Upon receipt, datagram is aurally or machine scanned into a uuencoded message suitable for transmission an other media (avian Carriers and the like). Dodd, et al. Experimental [Page 3] INTERNET-DRAFT IP over Token-Rail 1 April 2004 4. Security Considerations Security is not generally a problem in normal operation, but special measures (such as data encryption) must be taken to limit rail access and prevent collisions Especially when tokens are present on the rail. Intellectual Property Statement The IETF has been notified of intellectual property rights claimed in regard to some or all of the specification contained in this document. For more information consult the online list of claimed rights. The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. Full Copyright Statement Copyright (C) The Internet Society (2004). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published Dodd, et al. Experimental [Page 4] INTERNET-DRAFT IP over Token-Rail 1 April 2004 and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Expiration Date This memo is filed as Author's Address KCJones% Lance Dodd TrainBridge Networks UPAC Labs Division McGirk , MO 65055 Phone: ..... ..... ..... .---- ..--- .---- ..--- EMail: lancedod@earthlink.net