From mailman-owner@ietf.org Sat Jun 1 06:45:42 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17687 for ; Sat, 1 Jun 2002 06:45:42 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA02043 for ; Sat, 1 Jun 2002 06:46:09 -0400 (EDT) Date: Sat, 1 Jun 2002 06:46:09 -0400 (EDT) Message-Id: <200206011046.GAA02043@optimus.ietf.org> From: mailman-owner@ietf.org Subject: ietf.org mailing list memberships reminder To: nat-archive@ietf.org X-No-Archive: yes Precedence: bulk X-Mailman-Version: 1.0 Precedence: bulk List-Id: Session Initiation Protocol This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, nat-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@ietf.org. Thanks! Passwords for nat-archive@lists.ietf.org: List Password // URL ---- -------- nat@ietf.org qLLL https://www1.ietf.org/mailman/options/nat/nat-archive@lists.ietf.org From nat-admin@ietf.org Tue Jun 18 09:20:55 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16149 for ; Tue, 18 Jun 2002 09:20:55 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA11493; Tue, 18 Jun 2002 09:16:22 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA11472 for ; Tue, 18 Jun 2002 09:16:20 -0400 (EDT) Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15973 for ; Tue, 18 Jun 2002 09:15:41 -0400 (EDT) Received: from bebop.France.Sun.COM ([129.157.174.15]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA07705 for ; Tue, 18 Jun 2002 07:18:23 -0600 (MDT) Received: from sun.com (vpn-129-156-96-161.EMEA.Sun.COM [129.156.96.161]) by bebop.France.Sun.COM (8.11.6+Sun/8.10.2/ENSMAIL,v2.2) with ESMTP id g5IDGFK27410; Tue, 18 Jun 2002 15:16:15 +0200 (MEST) Message-ID: <3D0F32B3.CD58CBD0@sun.com> Date: Tue, 18 Jun 2002 15:16:35 +0200 From: gabriel montenegro Reply-To: gab@sun.com X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: nat@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [NAT] just saw this, an RSIP implementation... Sender: nat-admin@ietf.org Errors-To: nat-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Network Address Translation X-BeenThere: nat@ietf.org Content-Transfer-Encoding: 7bit Just heard about this implementation of RSIP from the Universite Catholique de Louvain in Belgium. Haven't played with it, don't know if it works well or not, but at least it looks good. In case folks are interested: http://openresources.info.ucl.ac.be/rsip/index.php -gabriel _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From daemon@ns.ietf.org Tue Jun 18 09:20:56 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16159 for ; Tue, 18 Jun 2002 09:20:56 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id JAA11677 for nat-archive@odin.ietf.org; Tue, 18 Jun 2002 09:21:35 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA11493; Tue, 18 Jun 2002 09:16:22 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA11472 for ; Tue, 18 Jun 2002 09:16:20 -0400 (EDT) Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15973 for ; Tue, 18 Jun 2002 09:15:41 -0400 (EDT) Received: from bebop.France.Sun.COM ([129.157.174.15]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA07705 for ; Tue, 18 Jun 2002 07:18:23 -0600 (MDT) Received: from sun.com (vpn-129-156-96-161.EMEA.Sun.COM [129.156.96.161]) by bebop.France.Sun.COM (8.11.6+Sun/8.10.2/ENSMAIL,v2.2) with ESMTP id g5IDGFK27410; Tue, 18 Jun 2002 15:16:15 +0200 (MEST) Message-ID: <3D0F32B3.CD58CBD0@sun.com> Date: Tue, 18 Jun 2002 15:16:35 +0200 From: gabriel montenegro Reply-To: gab@sun.com X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: nat@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [NAT] just saw this, an RSIP implementation... Sender: nat-admin@ietf.org Errors-To: nat-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Network Address Translation X-BeenThere: nat@ietf.org Content-Transfer-Encoding: 7bit Just heard about this implementation of RSIP from the Universite Catholique de Louvain in Belgium. Haven't played with it, don't know if it works well or not, but at least it looks good. In case folks are interested: http://openresources.info.ucl.ac.be/rsip/index.php -gabriel _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From nat-admin@ietf.org Thu Jun 27 04:07:23 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05543 for ; Thu, 27 Jun 2002 04:07:23 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA09932; Thu, 27 Jun 2002 04:05:28 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA09908 for ; Thu, 27 Jun 2002 04:05:27 -0400 (EDT) Received: from 21cn.com ([61.140.60.248]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA05468 for ; Thu, 27 Jun 2002 04:04:40 -0400 (EDT) Received: from luwei([61.152.125.82]) by 21cn.com(AIMC 2.9.5.2) with SMTP id jmab3d1b11b0; Thr, 27 Jun 2002 16:00:49 +0800 Date: Thu, 27 Jun 2002 16:0:41 +0800 From: Wei Lu Reply-To: wlu@21cn.com To: "nat@ietf.org" X-mailer: FoxMail 3.11 Release [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: 7bit Message-ID: Content-Transfer-Encoding: 7bit Subject: [NAT] my idea Sender: nat-admin@ietf.org Errors-To: nat-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Network Address Translation X-BeenThere: nat@ietf.org Content-Transfer-Encoding: 7bit Hi, there, I have the following idea. before i start programming, i'd like to ask for ur comments. __________________________________________________________________________________________________________________________ Port Delegation - a Web service to expose the servers behind firewall or Network Address Translation(NAT) Copyright(c) 2002 Wei Lu (wlu@21cn.com). All rights reserved. It aims to address the problem to expose the service in a server behind firewall or NAT can only make active outbound connection to the internet, but the internet can not make inbound connection to it becourse the firewall blocks the inbound access or the server behind NAT has only an un-routable private IP address. Devided into 6 parts: HTTP HTTP Actual Client->Client Proxy---(3)-->request.cgi=>server.cgi <--(1)-->Server Proxy->Actual Server <- <--(2)-->client.cgi <=response.cgi<--(4)--- <- <=,=> means IPC between CGI program in web server. request.cgi communicates server.cgi (response.cgi locates client.cgi) by named pipes(FIFO) with nodes named /tmp/.PD/$ServiceID or /tmp/.PD/$ClientID with the following data structure: struct MessageBlock{ unsigned int PayloadLength; char ID[72]; //ServiceID or ClientID, enough for IPv6 128b address space. char *Payload; //Variable array with length of PayloadLength } ClientID : identification of a session of Actual Client. Client Proxy,Server Proxy and all the CGIs take it as a string, don't care its meaning. A good scheme to generate it is Actual Client's IP:Port by Client Proxy. ServiceID: identification of a port(service) of an Actual Server. Just a string. Process: A) Server registration: Server Proxy GET (1) server.cgi, the response page is very large and never finish opening, from then on, all the incoming data comes from it. The data includes control messages for Server Proxy and incoming requests to Actual Server(tagged with ClientID). server.cgi creates a FIFO, /tmp/.PD/$ServiceID to wait for request.cgi B) Client Establish Request: Actual Client invoke request to Client Proxy. When the session starts, Client Proxy generate ClientID for this session and GET (2) requests to client.cgi with ServiceID and ClientID. (Client Proxy maintains a map of ServiceID to its listerning port to be access by Actual Client). the response page is very large and never finish opening, from then on, all the return data from Actual Server comes through it. client.cgi creates a FIFO, /tmp/.PD/$ClientID to wait for response.cgi. C) Client send data: Client Proxy relays every data blocks from Actual Client by http uploading scheme, POST (3) to request.cgi with ServiceID and ClientID. request.cgi write the uploaded data into FIFO /tmp/.PD/$ServiceID. server.cgi get it and relay to Server Proxy(1) with ClientID. Server Proxy demultiplex data according to ClientID, makes connections to Actual Server when ClientID first occurs. D) Server reponse data: The reponses data from Actual Server will be relayed by Server Proxy by POST(4) to response.cgi with http upload scheme. response messages encapsulated in MessageBlocks with ClientID. response.cgi writes the uploaded data into /tmp/.PD/$ClientID. client.cgi gets it and returns through (2). Client Proxy relays it to Actual Client. _______________________________________________________________________________________________________________________ updating in http://wlu.51.net/PortDelegation/ or http://snap.eu.org/~wlu/PortDelegation/ Wei Lu wlu@21cn.com ..:::::::::::::::::::::::::... Wei Lu (Mr) Apt.301 No.5 Lane 145 Mudan R.d Shanghai 201204 P.R.China 86-13611885232 (cell phone) 86-21-50801913 (office) 86-21-68456252 (home) EMail : wlu@21cn.com ............................... _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From daemon@optimus.ietf.org Thu Jun 27 04:07:23 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05551 for ; Thu, 27 Jun 2002 04:07:23 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id EAA10232 for nat-archive@odin.ietf.org; Thu, 27 Jun 2002 04:08:08 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA09932; Thu, 27 Jun 2002 04:05:28 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA09908 for ; Thu, 27 Jun 2002 04:05:27 -0400 (EDT) Received: from 21cn.com ([61.140.60.248]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA05468 for ; Thu, 27 Jun 2002 04:04:40 -0400 (EDT) Received: from luwei([61.152.125.82]) by 21cn.com(AIMC 2.9.5.2) with SMTP id jmab3d1b11b0; Thr, 27 Jun 2002 16:00:49 +0800 Date: Thu, 27 Jun 2002 16:0:41 +0800 From: Wei Lu Reply-To: wlu@21cn.com To: "nat@ietf.org" X-mailer: FoxMail 3.11 Release [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: 7bit Message-ID: Content-Transfer-Encoding: 7bit Subject: [NAT] my idea Sender: nat-admin@ietf.org Errors-To: nat-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Network Address Translation X-BeenThere: nat@ietf.org Content-Transfer-Encoding: 7bit Hi, there, I have the following idea. before i start programming, i'd like to ask for ur comments. __________________________________________________________________________________________________________________________ Port Delegation - a Web service to expose the servers behind firewall or Network Address Translation(NAT) Copyright(c) 2002 Wei Lu (wlu@21cn.com). All rights reserved. It aims to address the problem to expose the service in a server behind firewall or NAT can only make active outbound connection to the internet, but the internet can not make inbound connection to it becourse the firewall blocks the inbound access or the server behind NAT has only an un-routable private IP address. Devided into 6 parts: HTTP HTTP Actual Client->Client Proxy---(3)-->request.cgi=>server.cgi <--(1)-->Server Proxy->Actual Server <- <--(2)-->client.cgi <=response.cgi<--(4)--- <- <=,=> means IPC between CGI program in web server. request.cgi communicates server.cgi (response.cgi locates client.cgi) by named pipes(FIFO) with nodes named /tmp/.PD/$ServiceID or /tmp/.PD/$ClientID with the following data structure: struct MessageBlock{ unsigned int PayloadLength; char ID[72]; //ServiceID or ClientID, enough for IPv6 128b address space. char *Payload; //Variable array with length of PayloadLength } ClientID : identification of a session of Actual Client. Client Proxy,Server Proxy and all the CGIs take it as a string, don't care its meaning. A good scheme to generate it is Actual Client's IP:Port by Client Proxy. ServiceID: identification of a port(service) of an Actual Server. Just a string. Process: A) Server registration: Server Proxy GET (1) server.cgi, the response page is very large and never finish opening, from then on, all the incoming data comes from it. The data includes control messages for Server Proxy and incoming requests to Actual Server(tagged with ClientID). server.cgi creates a FIFO, /tmp/.PD/$ServiceID to wait for request.cgi B) Client Establish Request: Actual Client invoke request to Client Proxy. When the session starts, Client Proxy generate ClientID for this session and GET (2) requests to client.cgi with ServiceID and ClientID. (Client Proxy maintains a map of ServiceID to its listerning port to be access by Actual Client). the response page is very large and never finish opening, from then on, all the return data from Actual Server comes through it. client.cgi creates a FIFO, /tmp/.PD/$ClientID to wait for response.cgi. C) Client send data: Client Proxy relays every data blocks from Actual Client by http uploading scheme, POST (3) to request.cgi with ServiceID and ClientID. request.cgi write the uploaded data into FIFO /tmp/.PD/$ServiceID. server.cgi get it and relay to Server Proxy(1) with ClientID. Server Proxy demultiplex data according to ClientID, makes connections to Actual Server when ClientID first occurs. D) Server reponse data: The reponses data from Actual Server will be relayed by Server Proxy by POST(4) to response.cgi with http upload scheme. response messages encapsulated in MessageBlocks with ClientID. response.cgi writes the uploaded data into /tmp/.PD/$ClientID. client.cgi gets it and returns through (2). Client Proxy relays it to Actual Client. _______________________________________________________________________________________________________________________ updating in http://wlu.51.net/PortDelegation/ or http://snap.eu.org/~wlu/PortDelegation/ Wei Lu wlu@21cn.com ..:::::::::::::::::::::::::... Wei Lu (Mr) Apt.301 No.5 Lane 145 Mudan R.d Shanghai 201204 P.R.China 86-13611885232 (cell phone) 86-21-50801913 (office) 86-21-68456252 (home) EMail : wlu@21cn.com ............................... _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From nat-admin@ietf.org Thu Jun 27 09:37:06 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17846 for ; Thu, 27 Jun 2002 09:37:06 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA05811; Thu, 27 Jun 2002 09:32:32 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA05787 for ; Thu, 27 Jun 2002 09:32:30 -0400 (EDT) Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17498 for ; Thu, 27 Jun 2002 09:31:45 -0400 (EDT) Received: from mira-sjc5-4.cisco.com (IDENT:mirapoint@mira-sjc5-4.cisco.com [171.71.163.21]) by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g5RDViK5020091; Thu, 27 Jun 2002 06:31:44 -0700 (PDT) Received: from spandex.cisco.com (ssh-rtp-1.cisco.com [161.44.11.166]) by mira-sjc5-4.cisco.com (Mirapoint) with ESMTP id AEG89238; Thu, 27 Jun 2002 06:28:52 -0700 (PDT) Message-Id: <5.1.0.14.0.20020627093006.05680cf0@localhost> X-Sender: mshore@localhost X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 27 Jun 2002 09:31:41 -0400 To: wlu@21cn.com, "nat@ietf.org" From: Melinda Shore Subject: Re: [NAT] my idea In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: nat-admin@ietf.org Errors-To: nat-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Network Address Translation X-BeenThere: nat@ietf.org At 04:00 PM 6/27/02 +0800, Wei Lu wrote: >I have the following idea. before i start programming, i'd like to ask for ur comments. You may want to take a look at TURN, as well as the recently uploaded SPAN-A draft (http://www.ietf.org/internet-drafts/draft-cordell-midcom-span-a-00.txt). One thing that needs to be considered is whether you want to provide technology that allows users to violate local firewall policy. Melinda _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From daemon@optimus.ietf.org Thu Jun 27 09:37:07 2002 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17856 for ; Thu, 27 Jun 2002 09:37:07 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id JAA06390 for nat-archive@odin.ietf.org; Thu, 27 Jun 2002 09:37:50 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA05811; Thu, 27 Jun 2002 09:32:32 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA05787 for ; Thu, 27 Jun 2002 09:32:30 -0400 (EDT) Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17498 for ; Thu, 27 Jun 2002 09:31:45 -0400 (EDT) Received: from mira-sjc5-4.cisco.com (IDENT:mirapoint@mira-sjc5-4.cisco.com [171.71.163.21]) by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g5RDViK5020091; Thu, 27 Jun 2002 06:31:44 -0700 (PDT) Received: from spandex.cisco.com (ssh-rtp-1.cisco.com [161.44.11.166]) by mira-sjc5-4.cisco.com (Mirapoint) with ESMTP id AEG89238; Thu, 27 Jun 2002 06:28:52 -0700 (PDT) Message-Id: <5.1.0.14.0.20020627093006.05680cf0@localhost> X-Sender: mshore@localhost X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 27 Jun 2002 09:31:41 -0400 To: wlu@21cn.com, "nat@ietf.org" From: Melinda Shore Subject: Re: [NAT] my idea In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: nat-admin@ietf.org Errors-To: nat-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Network Address Translation X-BeenThere: nat@ietf.org At 04:00 PM 6/27/02 +0800, Wei Lu wrote: >I have the following idea. before i start programming, i'd like to ask for ur comments. You may want to take a look at TURN, as well as the recently uploaded SPAN-A draft (http://www.ietf.org/internet-drafts/draft-cordell-midcom-span-a-00.txt). One thing that needs to be considered is whether you want to provide technology that allows users to violate local firewall policy. Melinda _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat