RE: RNET: Randon Network Endpoint Technology

"Dan Wing" <dwing@cisco.com> Thu, 19 June 2008 16:56 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 C6ACA3A6889; Thu, 19 Jun 2008 09:56: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 2DF6A3A6889 for <ietf@core3.amsl.com>; Thu, 19 Jun 2008 09:56:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.504
X-Spam-Level:
X-Spam-Status: No, score=-6.504 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, 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 X+QG9gAVYKqr for <ietf@core3.amsl.com>; Thu, 19 Jun 2008 09:56:28 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id F41A53A685C for <ietf@ietf.org>; Thu, 19 Jun 2008 09:56:27 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,673,1204531200"; d="scan'208";a="58586891"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-2.cisco.com with ESMTP; 19 Jun 2008 09:57:19 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m5JGvJK5011304; Thu, 19 Jun 2008 09:57:19 -0700
Received: from dwingwxp01 ([10.32.240.194]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m5JGvJkx015857; Thu, 19 Jun 2008 16:57:19 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Chad Giffin'" <typosity@hotmail.com>, "'IETF'" <ietf@ietf.org>
References: <BLU120-W3681F56836E94FD82B9038CAAA0@phx.gbl>
Subject: RE: RNET: Randon Network Endpoint Technology
Date: Thu, 19 Jun 2008 09:57:18 -0700
Message-ID: <014701c8d22d$890274e0$c2f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <BLU120-W3681F56836E94FD82B9038CAAA0@phx.gbl>
Thread-Index: AcjSLHX9x6ZmGHLTSluHM8fsf8mdBAAALBrg
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2712; t=1213894639; x=1214758639; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com> |Subject:=20RE=3A=20RNET=3A=20Randon=20Network=20Endpoint=2 0Technology |Sender:=20; bh=vZPVyQWpE3tg1E/96BRlv+8pSUsLe9pqaVotatjBFS8=; b=eeMhSicc6eTKHLSs+LtHiUSB4Bcf98atoA8AgSGsDGO9JGncMQilvus9IC dOubdLU0eWI63PsaGamdLgUTAAVC241yQ/HmaEbO0FUKeDi6edf5igp3O1NB wAnghTKUmf48gFAaQWFk3zA91cyvWw/CgcIVQF88D+hS3z/EMVp8M=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
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

 

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On 
> Behalf Of Chad Giffin
> Sent: Thursday, June 19, 2008 9:49 AM
> To: IETF
> Subject: RNET: Randon Network Endpoint Technology
> 
> 
> 
> Chad Christopher Giffin
> Suite 205
> 123 Mayfair Avenue
> Winnipeg, Manitoba
> Canada   R3L 0A1
> 
> Phone: 1  204  475-1210
> 
> June 18th, 1145h CDT
> 
> To all members of the IETF mailing list;
> 
>      I have posted a description, twice, of the RNET protocol 
> to this mailing list.  I have also provided some updates 
> concerning peer to peer connections between RNET Hosts.
> 
>      I have yet to receive /any/ response (other then an 
> email with an empty body) concerning by postings.

Here is a response, which appeared to have been CC'd to you:
http://www.ietf.org/mail-archive/web/ietf/current/msg51774.html

I agree with Eric; based on the description of RNET, it sounds much like STUN
combined with a rendezvous protocol (e.g., SIP).  RNET is also similar to
HIP's NAT traversal.

STUN is RFC3489 and draft-ietf-behave-rfc3489bis.  SIP is RFC3261.  The use of
STUN with SIP is best described in draft-ietf-sipping-nat-scenarios.  HIP's
NAT traversal is described in draft-ietf-hip-nat-traversal.  

Hope that helps,
-d



>      Please tell me what you, as members of this list, think 
> about RNET.
> 
>      Should it exist?
>      Who should be allowed to use it?
>      Should it exists and remain hidden?
>      Has anything been overlooked in it's design? 
>      How much more work is needed to make this a reality 
> (besides have the Vendors of routing equipment and software 
> incorporate this technology into their IP stacks?)
> 
>      I am a great many people support this technology and we 
> wish it to be a reality.
> 
>      Please provide some response.
>      It need not be too revealing.
>      At least show some support.
> 
>      So many of us would appreciate anonynimity on the 
> Internet to avoid being detected by those who should never 
> know of our identity and/or location.  As well, it will deter 
> quite effificiently crackers from attacking our systems.
> 
>      The end result would simply be that all serious 
> individual users (nodes) of the Internet would have anonymous 
> endpoints and the advertised endpoints would be what is 
> publically accessible.
> 
> 
> Yours Truly,
> 
> Chad Christopher Giffin
> 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