draft-dodd-token-rail-01.txt IP over Token-Rail Lance Dodd
Category: Experimental 1 April 2005
Transmission of IP Datagrams over Token-Rail Ethernet
draft-dodd-token-rail-01.txt
Status of this Memo
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
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.
Abstract
This memo describes an experimental method for the transmission of
IP datagrams over 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.
Overview and Rationale
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.
Internet Draft draft-dodd-token-rail01.txt IP over Token-Rail [Page 1]
Category: Experimental 1 April 2005
Table of Contents
1. Introduction............................................... 1
1.1 Advantage ........................................... 1
1.2 Topology............................................. 1
1.3 Standards............................................ 1
1.4 Physical Deployment.................................. 1
1.5 Collision Avoidance.................................. 1
1.6 Switching ........................................... 1
1.7 Service ............................................. 1
2. Frame Format and encoding.................................. 2
2.1 Alphabet............................................. 2
2.2 Numbers.............................................. 2
2.3 Symbols.............................................. 2
3. Discussion................................................. 3
4 Security .................................................. 3
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 point-to-point paths along a parallel bus
topology. The packet format and header information is analogous to current token ring
systems.
1.3 Switches may be incorporated into the rail network to provide queuing and QOS,
at the cost of latency. Bridges are acceptable in the provisioning of connections, but
due to safety and conductor stability, the bridges should not be transparent in
Nature.
1.4 Standards and policies are apparently easily manageable as all carriers are
government subsidized.This can be misleading however as it may cause additional
latency and congestion of links.
1.5 There is limited space available to the carriers, it is allotted in continuous Right
of Way, across great distances. This will require better compression/decompression of
packet data as usage increases.
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/station topology.
Internet Draft draft-dodd-token-rail01.txt IP over Token-Rail Page [2]
Category: Experimental 1 April 2005
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 ........
Internet Draft draft-dodd-token-rail01.txt IP over Token-Rail Page [3]
Category: Experimental 1 April 2005
3. Discussion
Multiple types of service can be provided with a prioritized switch.
The physical implementation of connectivity to the token-rail network 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).
By use of a S.T.A.T.I.O.N or Single Token Asynchronous Transit Input Output Nexus,
user datagrams may be encoded encapsulated and tokenized for transport. The R.A.I.L or
Random Access Information Link can be algorithmically or randomly assigned. The
C.A.B.O.O.S.E or Communication Application Out of Service Endpoint, indicates the end
of the transmission. Monitoring and traffic flow may be managed by the engineer or the
conductor by use of proprietary, out of band management protocols.
Authentication may be addresses by a per-session T.I.C.k.E.T or Token Identity Certificate Ensuring Trust.
4. Security Considerations
Security is not generally a problem in normal operation,
but special measures (such as data encryption) must be taken to limit
R.A.I.L. access and prevent collisions
Especially when tokens are present on the R.A.I.L.
draft-dodd-token-rail-01.txt
Author's Address
Lance Dodd
TrainBridge Networks
UPAC Labs Division
McGirk , MO 65055
Phone: ..... ..... ..... .---- ..--- .---- ..---
EMail: lancedod@earthlink.net
Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM 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.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights 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; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat 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 on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Internet Draft draft-dodd-token-rail01.txt IP over Token-Rail Page [4]