RE: Random Network Endpoint Technology (RNET)

Chad Giffin <typosity@hotmail.com> Thu, 22 May 2008 22:45 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 513EB3A6AF9; Thu, 22 May 2008 15:45:53 -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 D8C5B3A6AF9 for <ietf@core3.amsl.com>; Thu, 22 May 2008 15:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level:
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599]
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 Pd-fpXz7w7TA for <ietf@core3.amsl.com>; Thu, 22 May 2008 15:45:50 -0700 (PDT)
Received: from blu0-omc2-s26.blu0.hotmail.com (blu0-omc2-s26.blu0.hotmail.com [65.55.111.101]) by core3.amsl.com (Postfix) with ESMTP id C303A3A687A for <ietf@ietf.org>; Thu, 22 May 2008 15:45:50 -0700 (PDT)
Received: from BLU120-W1 ([65.55.111.73]) by blu0-omc2-s26.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 22 May 2008 15:45:50 -0700
Message-ID: <BLU120-W12633DA1A8CA68700A698CAC60@phx.gbl>
X-Originating-IP: [198.163.53.10]
From: Chad Giffin <typosity@hotmail.com>
To: <ietf@ietf.org>
Subject: RE: Random Network Endpoint Technology (RNET)
Date: Thu, 22 May 2008 18:45:50 -0400
Importance: Normal
In-Reply-To: <BLU120-W3397A3BAE407574B5F455ECAED0@phx.gbl>
References: <BLU120-W3397A3BAE407574B5F455ECAED0@phx.gbl>
MIME-Version: 1.0
X-OriginalArrivalTime: 22 May 2008 22:45:50.0517 (UTC) FILETIME=[956FC650:01C8BC5D]
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

> Random Network Endpoint Technology (RNET)
>
>
> The following changes need be made to the IP Version 6 Protocol Logic, in routers, in order to 
> impliment this technology:
>
> 1) encryption routines
> 2) recognization of RNET Route Requests
> 3) generation and recognization of RNET errors
> 4) routing table modifications
> NB: the RNET Host address may be stored in the host address of the route
> entry. The Target Host address may be stored in the Netmask of the
> route entry. The Gateway address may be stored in the gateway of
> route entry. The Route Decay may be stored in the Metric or be
> implimented through some system timer.

For bi-directionality of RNET Routes, we must either add a second reverse RNET Route entry -OR-
an RNET Route entry must contain a fifth element; the gateway address of the RNET Host for the
router.  [There would be no available space in the structure of a regular router entry for this fifth
element so the routing table entries structures would need to be changed]

> 5) routines to acquire keys from the RNET Centralized Server
> 6) storage of the IP address of the RNET Centralized Server
> 7) storage of the router's unique key
> 8) storage of the RNET Global Key
> 9) an additional flag for route entries marking them as RNET Route entries
>
>
> Sincerely,
>
> 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!
http://g.msn.ca/ca55/208
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf