From: dwing(_at_)cisco(_dot_)com
To: typosity(_at_)hotmail(_dot_)com; ietf(_at_)ietf(_dot_)org
Subject: RE: RNET: Randon Network Endpoint Technology
Date: Thu, 19 Jun 2008 09:57:18 -0700
-----Original Message-----
From: ietf-bounces(_at_)ietf(_dot_)org
[mailto:ietf-bounces(_at_)ietf(_dot_)org] On
Behalf Of Chad Giffin
Sent: Thursday, June 19, 2008 9:49 AM
To: IETF
Subject: RNET: Randon Network Endpoint Technology
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
This message was actually posted by me :-)
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.
I looked, albeit briefly, at STUN and SIP. these protocols are not at all like
what I am suggesting.
RNET will punch through firewalls/NATs without a problem. Peer to Peer
communication using RNET Host Addresses, however, may present a problem when
there are NATs between them. (The answer to this is simply to allow
authenticated RNET Route Requests to be made at every NAT/firewall)
I think you missed the point of RNET. The point being that you have a valid
IPv6 IP address and are able to plug into any part of the internet and use it
from that location. Your address is NOT advertised. The routes made for
communication by your RNET Host decay so as not to polute the internet's
routing tables.
RNET is quite simple, easy to impliment.
RNET Route Requests and RNET Error Messages can be put together under a new IP
protocol, named RNET. All that needs to be done is to have a new protocol
number assigned for this purpose.
Hope that helps,
-d
Thank-you for your response.
I appreciate it greatly.
Yours Truly,
Chad Christopher Giffin
a.k.a. "typo"
_______________________________________________
IETF mailing list
IETF(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf
_________________________________________________________________
Find hidden words, unscramble celebrity names, or try the ultimate crossword
puzzle with Live Search Games. Play now!
http://g.msn.ca/ca55/212
_______________________________________________
IETF mailing list
IETF(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf