RE: RNET: Random Network Endpoint Technology
Stephen Kent <kent@bbn.com> Mon, 23 June 2008 14:37 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 1E0BA3A698E; Mon, 23 Jun 2008 07:37:54 -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 A8BD13A698A for <ietf@core3.amsl.com>; Mon, 23 Jun 2008 07:37:52 -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.299, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 5lBHyQbqOnVN for <ietf@core3.amsl.com>; Mon, 23 Jun 2008 07:37:51 -0700 (PDT)
Received: from mx11.bbn.com (mx11.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id 9C2E13A6943 for <ietf@ietf.org>; Mon, 23 Jun 2008 07:37:51 -0700 (PDT)
Received: from dhcp89-089-071.bbn.com ([128.89.89.71]) by mx11.bbn.com with esmtp (Exim 4.60) (envelope-from <kent@bbn.com>) id 1KAnAz-0001ij-3y; Mon, 23 Jun 2008 10:37:49 -0400
Mime-Version: 1.0
Message-Id: <p0624050bc48565693905@[128.89.89.71]>
In-Reply-To: <BLU120-W25A3AE11ED3FB3DEA0AB30CAA40@phx.gbl>
References: <BLU120-W25A3AE11ED3FB3DEA0AB30CAA40@phx.gbl>
Date: Mon, 23 Jun 2008 10:38:16 -0400
To: Chad Giffin <typosity@hotmail.com>
From: Stephen Kent <kent@bbn.com>
Subject: RE: RNET: Random Network Endpoint Technology
Cc: IETF <ietf@ietf.org>
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="===============2031429760=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
Chad, Your message of 4/8 ended with a list of changes needed to IPv6 implementations to implement RNET. Changes to processing logic are just as serious as change to the format. Steve ------- 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. 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 The following changes need be made to the IP Version 6 Protocol Logic, in hosts, in order to impliment this technology: 1) encryption routines 2) generation of RNET Route requests 3) recognization of RNET errors 4) routines to acquire keys from the RNET Centralized Server 5) storage of the IP address of the RNET Centralized Server 6) storage of the host's unique key 7) storage of the RNET Global Key 8) an additional flag in the IP Stack to identify the assigned host address as being an RNET Host address so that the IP Stack is aware of the protocol to follow in initiating connections. This allows differentiation from RNET Host addressess and regular IPs
_______________________________________________ IETF mailing list IETF@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- RE: RNET: Random Network Endpoint Technology Stephen Kent
- RE: RNET: Random Network Endpoint Technology Chad Giffin
- RE: RNET: Random Network Endpoint Technology Chad Giffin
- RNET: Random Network Endpoint Technology Chad Giffin
- RE: RNET: Random Network Endpoint Technology Dan Wing
- Re: RNET: Random Network Endpoint Technology Hannes Tschofenig
- Re: RNET: Random Network Endpoint Technology Melinda Shore
- RE: RNET: Random Network Endpoint Technology Tschofenig, Hannes (NSN - FI/Espoo)
- Re: RNET: Random Network Endpoint Technology Melinda Shore