From owner-nat@livingston.com Mon Jan 3 10:37:50 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02895 for ; Mon, 3 Jan 2000 10:37:50 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id HAA14656; Mon, 3 Jan 2000 07:31:34 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id HAA12699 for nat-outgoing; Mon, 3 Jan 2000 07:27:12 -0800 (PST) Message-ID: <003001bf55fe$7b90bb00$0401a8c0@oleane.com> From: "Peter Lewis" To: Subject: (NAT) VoDSL 2000 Conference Date: Mon, 3 Jan 2000 16:23:02 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002D_01BF5606.CEA9F2E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-nat@livingston.com Precedence: bulk Reply-To: "Peter Lewis" This is a multi-part message in MIME format. ------=_NextPart_000_002D_01BF5606.CEA9F2E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, =20 The VoDSL 2000 Conference will stand in Paris next 28-31 March. Key = speakers, case studies: take a look at: = http://www.upperside.fr/bavodsl.htm =20 Regards ------=_NextPart_000_002D_01BF5606.CEA9F2E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hello,

The VoDSL 2000 Conference will stand = in Paris=20 next 28-31 March. Key speakers, case studies: take a look at: http://www.upperside.fr/bavo= dsl.htm

Regards

------=_NextPart_000_002D_01BF5606.CEA9F2E0-- - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe nat' in the body of the message. From owner-nat@livingston.com Tue Jan 4 00:21:28 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13741 for ; Tue, 4 Jan 2000 00:21:28 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id VAA28372; Mon, 3 Jan 2000 21:19:50 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id VAA22993 for nat-outgoing; Mon, 3 Jan 2000 21:15:47 -0800 (PST) From: "Aravind Rao" To: Subject: (NAT) datagram flow in a NAT enabled host Date: Tue, 4 Jan 2000 10:11:39 +0530 Message-ID: <01bf566d$fdbae050$4502a8c0@arao> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_005B_01BF569C.17731C50" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-nat@livingston.com Precedence: bulk Reply-To: "Aravind Rao" This is a multi-part message in MIME format. ------=_NextPart_000_005B_01BF569C.17731C50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, =20 I wanted to know about the datagram flow path in the TCP/IP stack = on a NAT enabled BSD system. to be more specific,I am not understanding how the datagram flow will be = when the connections are initiated from NAT enabled system itself & how the incoming & outgoing = datagrams are translated. =20 Please clarify my doubt or tell me where I can get more info. Thanks, Aravind. ------=_NextPart_000_005B_01BF569C.17731C50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi all,

I wanted to = know =20 about the datagram flow path in the TCP/IP stack on a NAT enabled BSD=20 system.

to be more specific,I am not = understanding=20 how the datagram flow will be when the connections = are

initiated from NAT enabled=20 system itself & how the incoming & = outgoing=20 datagrams are translated.

Please clarify my doubt or tell = me where I=20 can get more info.

Thanks,

Aravind.

------=_NextPart_000_005B_01BF569C.17731C50-- - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe nat' in the body of the message. From owner-nat@livingston.com Tue Jan 4 09:45:54 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29054 for ; Tue, 4 Jan 2000 09:45:52 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id GAA02050; Tue, 4 Jan 2000 06:40:19 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id GAA05433 for nat-outgoing; Tue, 4 Jan 2000 06:36:16 -0800 (PST) Message-ID: <20000104143512.24871.qmail@web1406.mail.yahoo.com> Date: Tue, 4 Jan 2000 06:35:12 -0800 (PST) From: Pyda Srisuresh Subject: Re: (NAT) datagram flow in a NAT enabled host To: Aravind Rao , nat@livingston.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-nat@livingston.com Precedence: bulk Reply-To: Pyda Srisuresh If you are originating sessions from a NAT device, you could use the external address as source and obviate NAT altogether. NAT function is normally applied to packets in transit. cheers, suresh --- Aravind Rao wrote: > Hi all, > > I wanted to know about the datagram flow path in the TCP/IP stack on a > NAT enabled BSD system. > to be more specific,I am not understanding how the datagram flow will be > when the connections are > initiated from NAT enabled system itself & how the incoming & outgoing > datagrams are translated. > > Please clarify my doubt or tell me where I can get more info. > > Thanks, > Aravind. > > ===== __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://messenger.yahoo.com - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe nat' in the body of the message. From owner-nat@livingston.com Tue Jan 11 05:56:19 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03254 for ; Tue, 11 Jan 2000 05:56:18 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id CAA01204; Tue, 11 Jan 2000 02:51:35 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id CAA06499 for nat-outgoing; Tue, 11 Jan 2000 02:44:53 -0800 (PST) Message-ID: <008501bf5c20$6b51e020$0401a8c0@oleane.com> From: "Peter Lewis" To: Subject: (NAT) SIP 2000 Call for Paper Date: Tue, 11 Jan 2000 11:41:20 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0082_01BF5C28.C79F0D00" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-nat@livingston.com Precedence: bulk Reply-To: "Peter Lewis" This is a multi-part message in MIME format. ------=_NextPart_000_0082_01BF5C28.C79F0D00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable SIP 2000: beyond H.323?=20 Discussing and debating in Paris May 10-12. A CFP is online at: http://www.upperside.fr/basip.htm =20 ------=_NextPart_000_0082_01BF5C28.C79F0D00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

SIP 2000: beyond H.323? =

Discussing and debating in Paris May = 10-12.

A CFP is online at:

http://www.upperside.fr/basip.= htm

------=_NextPart_000_0082_01BF5C28.C79F0D00-- - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe nat' in the body of the message. From owner-nat@livingston.com Sun Jan 23 11:51:02 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10368 for ; Sun, 23 Jan 2000 11:51:01 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id IAA12375; Sun, 23 Jan 2000 08:48:57 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id IAA23504 for nat-outgoing; Sun, 23 Jan 2000 08:45:21 -0800 (PST) Message-ID: <388B2FA5.21909F02@lucent.com> Date: Sun, 23 Jan 2000 11:43:18 -0500 From: dan raz X-Mailer: Mozilla 4.61 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: nat@livingston.com CC: sugla@lucent.com, Juergen Schoenwaelder , Pyda Srisuresh , Holdrege@lucent.com Subject: (NAT) draft-ietf-nat-snmp-alg-03 - new version Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-nat@livingston.com Precedence: bulk Reply-To: dan raz Content-Transfer-Encoding: 7bit The new version of the SNMP ALG draft, can be found in: http://www.ietf.org/internet-drafts/draft-ietf-nat-snmp-alg-03.txt This a fully revised version. The appearance is quite different: Sections have been moved, some of the text have been moved to an appendix, etc. The Main content changes are: 1. SNMP ALG now addresses ALL versions of SNMP. 2. A full description of alternative solutions has been added. 3. Security issues (especially in the context of SNMPv3) are addressed. 4. The requirements have been clarified. Please send us any additional feedback and comments. Danny -- Danny Raz Tel: 732-949-6712 Room 4G-637 Fax: 732-949-0399 Bell-Labs email: raz@dnrc.bell-labs.com 101 Crawfords Corner Road Holmdel, NJ 07733 - 3030 WWW: http://www.cs.bell-labs.com/~raz - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe nat' in the body of the message. From owner-nat@livingston.com Wed Jan 26 07:18:24 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01440 for ; Wed, 26 Jan 2000 07:18:23 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id EAA01657; Wed, 26 Jan 2000 04:15:50 -0800 (PST) Received: by server.livingston.com (8.9.3/8.9.3/0.5) id EAA13853 for nat-outgoing; Wed, 26 Jan 2000 04:13:28 -0800 (PST) Message-ID: <008c01bf67f6$3f458680$0401a8c0@oleane.com> From: "Peter Lewis" To: Subject: (NAT) SIP 2000 Call for Papaer Date: Wed, 26 Jan 2000 13:09:46 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0089_01BF67FE.9E62EA60" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-nat@livingston.com Precedence: bulk Reply-To: "Peter Lewis" This is a multi-part message in MIME format. ------=_NextPart_000_0089_01BF67FE.9E62EA60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable SIP 2000: Beyond H.323? A scientific committe composed of the most = eminent experts in this technology will review the abstracts submitted = from the Call For Papers: http://www.upperside.fr/basip.htm Take a look at the exhibition list. ------=_NextPart_000_0089_01BF67FE.9E62EA60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

SIP 2000: Beyond H.323? A scientific = committe=20 composed of the most eminent experts in this technology will review the=20 abstracts submitted from the Call For Papers:

http://www.upperside.fr/basip.= htm

Take a look at the exhibition=20 list.

------=_NextPart_000_0089_01BF67FE.9E62EA60-- - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe nat' in the body of the message. From owner-nat@livingston.com Fri Jan 28 12:55:12 2000 Received: from bast.livingston.com (bast.livingston.com [149.198.247.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21572 for ; Fri, 28 Jan 2000 12:55:10 -0500 (EST) Received: from server.livingston.com (server.livingston.com [149.198.1.70]) by bast.livingston.com (8.9.3/8.9.3) with ESMTP id JAA29065; Fri, 28 Jan 2000 09:48:50 -0800 (PST) Received: (from majordom@localhost) by server.livingston.com (8.9.3/8.9.3/0.5) id JAA22986 for nat-outgoing; Fri, 28 Jan 2000 09:46:07 -0800 (PST) Message-Id: <4.2.2.20000128094457.00ac13c0@porky> X-Sender: mhold@porky X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Fri, 28 Jan 2000 09:47:53 -0800 To: nat@livingston.com From: Matt Holdrege Subject: (NAT) SNMP ALG last call Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-nat@livingston.com Precedence: bulk Reply-To: Matt Holdrege OK, the authors seem to have addressed the concerns from the previous last call attempt. So let's try again. Please read draft-ietf-nat-snmp-alg-03.txt and let us know if you have any concerns. If we see no significant comments by February 11th, we'll forward the draft to the IESG. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe nat' in the body of the message.