Re: Random Network Endpoint Technology (RNET)

eburger@standardstrack.com Wed, 21 May 2008 21:49 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 [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C3833A67E2; Wed, 21 May 2008 14:49:30 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C2373A67E2 for <ietf@core3.amsl.com>; Wed, 21 May 2008 14:49:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.505
X-Spam-Level:
X-Spam-Status: No, score=-4.505 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, MIME_BASE64_BLANKS=0.041, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3oxbaMEqu1KH for <ietf@core3.amsl.com>; Wed, 21 May 2008 14:49:28 -0700 (PDT)
Received: from smtp05.bis.na.blackberry.com (smtp05.bis.na.blackberry.com [216.9.248.52]) by core3.amsl.com (Postfix) with ESMTP id 20C213A67CE for <ietf@ietf.org>; Wed, 21 May 2008 14:49:27 -0700 (PDT)
Received: from bda380.bisx.prod.on.blackberry (bda380.bisx.prod.on.blackberry [172.20.234.80]) by srs.bis.na.blackberry.com (8.13.7 TEAMON/8.13.7) with ESMTP id m4LLnUsB020856; Wed, 21 May 2008 21:49:30 GMT
Received: from bda380.bisx.prod.on.blackberry (localhost.localdomain [127.0.0.1]) by bda380.bisx.prod.on.blackberry (8.13.4 TEAMON/8.13.4) with ESMTP id m4LLnSDw024470; Wed, 21 May 2008 21:49:28 GMT
X-rim-org-msg-ref-id: 2011766466
Message-ID: <2011766466-1211406567-cardhu_decombobulator_blackberry.rim.net-918969765-@bxe033.bisx.prod.on.blackberry>
X-Priority: Normal
References: <BLU120-W192229D53F40915E68DB3FCAC70@phx.gbl>
In-Reply-To: <BLU120-W192229D53F40915E68DB3FCAC70@phx.gbl>
Sensitivity: Normal
Importance: Normal
To: "Chad Giffin" <typosity@hotmail.com>, ietf@ietf.org
Subject: Re: Random Network Endpoint Technology (RNET)
From: eburger@standardstrack.com
Date: Wed, 21 May 2008 21:49:24 +0000
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: eburger@standardstrack.com
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: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

So we have reinvented STUN?
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Chad Giffin <typosity@hotmail.com>

Date: Wed, 21 May 2008 17:09:54 
To:<ietf@ietf.org>
Cc:db@db.net, kdc@cc.umanitoba.ca
Subject: Random Network Endpoint Technology (RNET)


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 <mailto:typosity@hotmail.com> .
  
 Sincerely,
  
  
 Chad Christopher Giffin
 T-Net Information Systems
 (a.k.a. "typo")



----------------
 _______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf