Random Network Endpoint Technology (RNET)

Chad Giffin <typosity@hotmail.com> Wed, 21 May 2008 21:09 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [] (localhost []) by core3.amsl.com (Postfix) with ESMTP id 6EE473A68A1; Wed, 21 May 2008 14:09:53 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 7E5CF3A68A1 for <ietf@core3.amsl.com>; Wed, 21 May 2008 14:09:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id pNe+BI9PBQUd for <ietf@core3.amsl.com>; Wed, 21 May 2008 14:09:50 -0700 (PDT)
Received: from blu0-omc2-s27.blu0.hotmail.com (blu0-omc2-s27.blu0.hotmail.com []) by core3.amsl.com (Postfix) with ESMTP id 0E5903A687A for <ietf@ietf.org>; Wed, 21 May 2008 14:09:49 -0700 (PDT)
Received: from BLU120-W19 ([]) by blu0-omc2-s27.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 21 May 2008 14:09:54 -0700
Message-ID: <BLU120-W192229D53F40915E68DB3FCAC70@phx.gbl>
X-Originating-IP: []
From: Chad Giffin <typosity@hotmail.com>
To: ietf@ietf.org
Subject: Random Network Endpoint Technology (RNET)
Date: Wed, 21 May 2008 17:09:54 -0400
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 21 May 2008 21:09:54.0794 (UTC) FILETIME=[045864A0:01C8BB87]
Cc: db@db.net, kdc@cc.umanitoba.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1176730993=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

The following is an explanation of how to accomplish setting up a path of communication between two RNET Hosts. Some of you may have already figured this out... now you have the definitive answer.Consider this; You have two RNET Hosts, host A and host B. Both hosts wish to communicate with each other. Since both used un-advertised IP addresses, this seems impossible. The solution is to setup a route path between them so that the routers between them will forward packets destined for each of the two hosts. The operator of host A must contact the operator of host B through some other means of communication. The operator of host A need only acquire the, advertised, IP address of host B's gateway. Once this is done, host A sends an RNET Route Request specifying the host B's address as the target address and directs this request to the gateway of host B. The result is that all the routers in between host A and host B will have setup an RNET Route entry for host A as the RNET Host and with host B as the Target Host. At this point either host may initiate contact with the other as the routers between them will know where to forward their packet(s).I hope this clears up any confusion or misunderstanding (or lack thereof.)If you have any suggestions or comments, please feel free to email me directly at mailto:typosity@hotmail.com.
Chad Christopher Giffin
T-Net Information Systems
(a.k.a. "typo")
If you like crossword puzzles, then you'll love Flexicon, a game which combines four overlapping crossword puzzles into one!
IETF mailing list