From mailman-owner@ietf.org Tue Jan 1 05:24:15 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 FAA10378 for ; Tue, 1 Jan 2002 05:24:15 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA13184 for ; Tue, 1 Jan 2002 05:24:17 -0500 (EST) Date: Tue, 1 Jan 2002 05:24:17 -0500 (EST) Message-Id: <200201011024.FAA13184@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 Jan 1 19:26:11 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 TAA16937; Tue, 1 Jan 2002 19:26:11 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA07882; Tue, 1 Jan 2002 19:01:12 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA07856 for ; Tue, 1 Jan 2002 19:01:02 -0500 (EST) Received: from windlord.WWP.COM (mail.worldwidepackets.com [12.46.89.6]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16789 for ; Tue, 1 Jan 2002 19:00:58 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message Subject: RE: [NAT] RE: Re RE: Regarding NAT MIB MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Tue, 1 Jan 2002 16:01:34 -0800 Message-ID: <917063BAB0DDB043AF5FAA73C7A835D41A57E0@windlord.WWP.COM> Thread-Topic: [NAT] RE: Re RE: Regarding NAT MIB Thread-Index: AcGSH66CM5h5IkJpS2upUH9k2Wyc3AA/Q9RA From: "Rohit Rohit" To: "Pyda Srisuresh" , "Rajendra Prasad" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id TAA07857 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: 8bit Hi Suresh, My comments are inline. Please search for [ROHIT]. <... stuff deleted> > --- Rohit Rohit wrote: > > Hi, > > > > The main idea behind dividing the config info in the three > > tables is the modularity and clarity. > > > > There are three steps in configuring the NAT :-> > > > > 1. enable\disable on the particular interface. > > 2. define the type of nat and other protocol specific parameters. > > 3. define the addrMap. > > > > So the three different tables just represent these three steps. > > > This is good. > > I see that each interface configuration is covered by NatInterfaceEntry. > Within NatInterfaceEntry, I see > 1) is covered by natInterfaceStatus, Even though I believe, there should > be 2 fields - One to control the NAT enable/Disable and > the second field to query teh status from NAT device. > > [ROHIT] the same field can is supposed to show the present status. Yup, You are right. Sorry about that. > > As for item 2), this is "natConfServiceType" field in NatConfEntry as below. > NatConfEntry ::= SEQUENCE { > natConfName SnmpAdminString, > natConfServiceType INTEGER, > natConfProtConfigName SnmpAdminString, > natConfStorageType StorageType, > natConfStatus RowStatus > } > So, including natConfName as a field within NatInterfcaeEntry will > do the job, as you say. > > As for item 3, I am confused as to how an address map table is > associated with the Interface. > I understand, natConfig is constituted of: > natConfTable, natConfAddrMapTable, natInterfaceTable, > natConfUdpDefIdleTimeout, natConfIcmpDefIdleTimeout, > natConfOtherDefIdleTimeout, natConfTcpDefIdleTimeout > > Now, How do you associate an Addressmap table with a specific > interface? > > How is NatConfEntry (associated with a specific InterfaceTableEntry) > associated with an AddrMaptable? Thanks. > > [ROHIT] The addrMap Tables have two indexes :-> > natConfName, natConfAddrMapName. > OK. natConfName is currently not an index in AddrMapEntry. I assume, you were suggesting to add this. [ROHIT] natConfName is already an index to the natAddrMapEntry. natConfAddrMapEntry OBJECT-TYPE SYNTAX NatConfAddrMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A description of a NAT entry. This entry contributes to the dynamic or static NAT table of the device." INDEX { natConfName, natConfAddrMapName } ::= { natConfAddrMapTable 1 } I have a somewhat radically different thought on the organization of natconf. Here it goes. Do let me know what you think. * I believe, we can simplify natConfig to consist of just natInterfaceTable and natConfAddrMapTable. I.e., get rid of natConfTable, natConfUdpDefIdleTimeout, natConfIcmpDefIdleTimeout, natConfOtherDefIdleTimeout, and natConfTcpDefIdleTimeout from natConfig. * The natInterfaceTable may be expanded to contain natConfUdpDefIdleTimeout, natConfIcmpDefIdleTimeout, natConfOtherDefIdleTimeout, natConfTcpDefIdleTimeout, natConfServiceType, natConfAddrMapName and natConfProtConfigName fields natConfServiceType will describe the NAT-type for the interface - Traiditional-NAT, Twice-NAT or Bidirectional-NAT. natConfAddrMapName will be the index into the NAT Address map table. natConfProtConfigName will be the index into protocol specific natProtConfTable (for the future) * The natConfAddrMapEntry may be expanded to include AddrMapIndex field. So, all entries of an address map will be identified by natConfAddrMapName, with differing index or rule number. [ROHIT] The suggested approach is towards combining the natConfTable and natInterfaceTable and then adding the pointer to the natConfAddrMapName in the same table. I don't see any problem or issue with the approach. It is just rearranging the config parameters. Whichever approach is more close to the practical implementation, we should go ahead with that. Thanks Rohit <... stuff deleted> regards, suresh __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From daemon@optimus.ietf.org Tue Jan 1 20:24: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 TAA16942 for ; Tue, 1 Jan 2002 19:26:12 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id TAA08249 for nat-archive@odin.ietf.org; Tue, 1 Jan 2002 19:26:15 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA07882; Tue, 1 Jan 2002 19:01:12 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA07856 for ; Tue, 1 Jan 2002 19:01:02 -0500 (EST) Received: from windlord.WWP.COM (mail.worldwidepackets.com [12.46.89.6]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16789 for ; Tue, 1 Jan 2002 19:00:58 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message Subject: RE: [NAT] RE: Re RE: Regarding NAT MIB MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Tue, 1 Jan 2002 16:01:34 -0800 Message-ID: <917063BAB0DDB043AF5FAA73C7A835D41A57E0@windlord.WWP.COM> Thread-Topic: [NAT] RE: Re RE: Regarding NAT MIB Thread-Index: AcGSH66CM5h5IkJpS2upUH9k2Wyc3AA/Q9RA From: "Rohit Rohit" To: "Pyda Srisuresh" , "Rajendra Prasad" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id TAA07857 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: 8bit Hi Suresh, My comments are inline. Please search for [ROHIT]. <... stuff deleted> > --- Rohit Rohit wrote: > > Hi, > > > > The main idea behind dividing the config info in the three > > tables is the modularity and clarity. > > > > There are three steps in configuring the NAT :-> > > > > 1. enable\disable on the particular interface. > > 2. define the type of nat and other protocol specific parameters. > > 3. define the addrMap. > > > > So the three different tables just represent these three steps. > > > This is good. > > I see that each interface configuration is covered by NatInterfaceEntry. > Within NatInterfaceEntry, I see > 1) is covered by natInterfaceStatus, Even though I believe, there should > be 2 fields - One to control the NAT enable/Disable and > the second field to query teh status from NAT device. > > [ROHIT] the same field can is supposed to show the present status. Yup, You are right. Sorry about that. > > As for item 2), this is "natConfServiceType" field in NatConfEntry as below. > NatConfEntry ::= SEQUENCE { > natConfName SnmpAdminString, > natConfServiceType INTEGER, > natConfProtConfigName SnmpAdminString, > natConfStorageType StorageType, > natConfStatus RowStatus > } > So, including natConfName as a field within NatInterfcaeEntry will > do the job, as you say. > > As for item 3, I am confused as to how an address map table is > associated with the Interface. > I understand, natConfig is constituted of: > natConfTable, natConfAddrMapTable, natInterfaceTable, > natConfUdpDefIdleTimeout, natConfIcmpDefIdleTimeout, > natConfOtherDefIdleTimeout, natConfTcpDefIdleTimeout > > Now, How do you associate an Addressmap table with a specific > interface? > > How is NatConfEntry (associated with a specific InterfaceTableEntry) > associated with an AddrMaptable? Thanks. > > [ROHIT] The addrMap Tables have two indexes :-> > natConfName, natConfAddrMapName. > OK. natConfName is currently not an index in AddrMapEntry. I assume, you were suggesting to add this. [ROHIT] natConfName is already an index to the natAddrMapEntry. natConfAddrMapEntry OBJECT-TYPE SYNTAX NatConfAddrMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A description of a NAT entry. This entry contributes to the dynamic or static NAT table of the device." INDEX { natConfName, natConfAddrMapName } ::= { natConfAddrMapTable 1 } I have a somewhat radically different thought on the organization of natconf. Here it goes. Do let me know what you think. * I believe, we can simplify natConfig to consist of just natInterfaceTable and natConfAddrMapTable. I.e., get rid of natConfTable, natConfUdpDefIdleTimeout, natConfIcmpDefIdleTimeout, natConfOtherDefIdleTimeout, and natConfTcpDefIdleTimeout from natConfig. * The natInterfaceTable may be expanded to contain natConfUdpDefIdleTimeout, natConfIcmpDefIdleTimeout, natConfOtherDefIdleTimeout, natConfTcpDefIdleTimeout, natConfServiceType, natConfAddrMapName and natConfProtConfigName fields natConfServiceType will describe the NAT-type for the interface - Traiditional-NAT, Twice-NAT or Bidirectional-NAT. natConfAddrMapName will be the index into the NAT Address map table. natConfProtConfigName will be the index into protocol specific natProtConfTable (for the future) * The natConfAddrMapEntry may be expanded to include AddrMapIndex field. So, all entries of an address map will be identified by natConfAddrMapName, with differing index or rule number. [ROHIT] The suggested approach is towards combining the natConfTable and natInterfaceTable and then adding the pointer to the natConfAddrMapName in the same table. I don't see any problem or issue with the approach. It is just rearranging the config parameters. Whichever approach is more close to the practical implementation, we should go ahead with that. Thanks Rohit <... stuff deleted> regards, suresh __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From nat-admin@ietf.org Thu Jan 3 00:09: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 AAA17742; Thu, 3 Jan 2002 00:09:07 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA05382; Thu, 3 Jan 2002 00:02:04 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA05363 for ; Thu, 3 Jan 2002 00:02:02 -0500 (EST) Received: from web13807.mail.yahoo.com (web13807.mail.yahoo.com [216.136.175.17]) by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA17700 for ; Thu, 3 Jan 2002 00:02:00 -0500 (EST) Message-ID: <20020103050201.48658.qmail@web13807.mail.yahoo.com> Received: from [66.89.112.150] by web13807.mail.yahoo.com via HTTP; Wed, 02 Jan 2002 21:02:01 PST Date: Wed, 2 Jan 2002 21:02:01 -0800 (PST) From: Pyda Srisuresh Subject: RE: [NAT] RE: Re RE: Regarding NAT MIB To: Rohit Rohit , Rajendra Prasad Cc: nat@ietf.org In-Reply-To: <917063BAB0DDB043AF5FAA73C7A835D41A57E0@windlord.WWP.COM> 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 Rohit, Having just two tables to confiure (per-interface table and address-map table) makes the MIB simple and easy to follow. I would suggest the above. Thanks. cheers, suresh --- Rohit Rohit wrote: > Hi Suresh, > > My comments are inline. Please search for [ROHIT]. > > <... stuff deleted> > > --- Rohit Rohit wrote: > > > Hi, > > > > > > The main idea behind dividing the config info in the three > > > tables is the modularity and clarity. > > > > > > There are three steps in configuring the NAT :-> > > > > > > 1. enable\disable on the particular interface. > > > 2. define the type of nat and other protocol specific parameters. > > > 3. define the addrMap. > > > > > > So the three different tables just represent these three steps. > > > > > This is good. > > > > I see that each interface configuration is covered by NatInterfaceEntry. > > Within NatInterfaceEntry, I see > > 1) is covered by natInterfaceStatus, Even though I believe, there should > > be 2 fields - One to control the NAT enable/Disable and > > the second field to query teh status from NAT device. > > > > [ROHIT] the same field can is supposed to show the present status. > > Yup, You are right. Sorry about that. > > > > > As for item 2), this is "natConfServiceType" field in NatConfEntry as > below. > > NatConfEntry ::= SEQUENCE { > > natConfName SnmpAdminString, > > natConfServiceType INTEGER, > > natConfProtConfigName SnmpAdminString, > > natConfStorageType StorageType, > > natConfStatus RowStatus > > } > > So, including natConfName as a field within NatInterfcaeEntry will > > do the job, as you say. > > > > As for item 3, I am confused as to how an address map table is > > associated with the Interface. > > I understand, natConfig is constituted of: > > natConfTable, natConfAddrMapTable, natInterfaceTable, > > natConfUdpDefIdleTimeout, natConfIcmpDefIdleTimeout, > > natConfOtherDefIdleTimeout, natConfTcpDefIdleTimeout > > > > Now, How do you associate an Addressmap table with a specific > > interface? > > > > How is NatConfEntry (associated with a specific InterfaceTableEntry) > > associated with an AddrMaptable? Thanks. > > > > [ROHIT] The addrMap Tables have two indexes :-> > > natConfName, natConfAddrMapName. > > > OK. natConfName is currently not an index in AddrMapEntry. > I assume, you were suggesting to add this. > > [ROHIT] natConfName is already an index to the natAddrMapEntry. > > natConfAddrMapEntry OBJECT-TYPE > SYNTAX NatConfAddrMapEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "A description of a NAT entry. This entry > contributes to the dynamic or static NAT table of > the device." > INDEX { natConfName, natConfAddrMapName } > ::= { natConfAddrMapTable 1 } > > > I have a somewhat radically different thought on the organization > of natconf. Here it goes. Do let me know what you think. > > * I believe, we can simplify natConfig to consist of just > natInterfaceTable and natConfAddrMapTable. > > I.e., get rid of natConfTable, natConfUdpDefIdleTimeout, > natConfIcmpDefIdleTimeout, natConfOtherDefIdleTimeout, and > natConfTcpDefIdleTimeout from natConfig. > > * The natInterfaceTable may be expanded to contain > natConfUdpDefIdleTimeout, natConfIcmpDefIdleTimeout, > natConfOtherDefIdleTimeout, natConfTcpDefIdleTimeout, > natConfServiceType, natConfAddrMapName and > natConfProtConfigName fields > > natConfServiceType will describe the NAT-type for the > interface - Traiditional-NAT, Twice-NAT or Bidirectional-NAT. > > natConfAddrMapName will be the index into the NAT > Address map table. > > natConfProtConfigName will be the index into protocol > specific natProtConfTable (for the future) > > * The natConfAddrMapEntry may be expanded to include > AddrMapIndex field. > > So, all entries of an address map will be identified > by natConfAddrMapName, with differing index or rule number. > > > [ROHIT] The suggested approach is towards combining the natConfTable > and natInterfaceTable and then adding the pointer to the > natConfAddrMapName in the same table. > > I don't see any problem or issue with the approach. It is just > rearranging the config parameters. Whichever approach is more > close to the practical implementation, we should go ahead with that. > > > Thanks > Rohit > > <... stuff deleted> > > regards, > suresh > > __________________________________________________ > Do You Yahoo!? > Send your FREE holiday greetings online! > http://greetings.yahoo.com ===== __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From daemon@optimus.ietf.org Thu Jan 3 00:54:35 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 AAA17746 for ; Thu, 3 Jan 2002 00:09:08 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id AAA05732 for nat-archive@odin.ietf.org; Thu, 3 Jan 2002 00:09:09 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA05382; Thu, 3 Jan 2002 00:02:04 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA05363 for ; Thu, 3 Jan 2002 00:02:02 -0500 (EST) Received: from web13807.mail.yahoo.com (web13807.mail.yahoo.com [216.136.175.17]) by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA17700 for ; Thu, 3 Jan 2002 00:02:00 -0500 (EST) Message-ID: <20020103050201.48658.qmail@web13807.mail.yahoo.com> Received: from [66.89.112.150] by web13807.mail.yahoo.com via HTTP; Wed, 02 Jan 2002 21:02:01 PST Date: Wed, 2 Jan 2002 21:02:01 -0800 (PST) From: Pyda Srisuresh Subject: RE: [NAT] RE: Re RE: Regarding NAT MIB To: Rohit Rohit , Rajendra Prasad Cc: nat@ietf.org In-Reply-To: <917063BAB0DDB043AF5FAA73C7A835D41A57E0@windlord.WWP.COM> 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 Rohit, Having just two tables to confiure (per-interface table and address-map table) makes the MIB simple and easy to follow. I would suggest the above. Thanks. cheers, suresh --- Rohit Rohit wrote: > Hi Suresh, > > My comments are inline. Please search for [ROHIT]. > > <... stuff deleted> > > --- Rohit Rohit wrote: > > > Hi, > > > > > > The main idea behind dividing the config info in the three > > > tables is the modularity and clarity. > > > > > > There are three steps in configuring the NAT :-> > > > > > > 1. enable\disable on the particular interface. > > > 2. define the type of nat and other protocol specific parameters. > > > 3. define the addrMap. > > > > > > So the three different tables just represent these three steps. > > > > > This is good. > > > > I see that each interface configuration is covered by NatInterfaceEntry. > > Within NatInterfaceEntry, I see > > 1) is covered by natInterfaceStatus, Even though I believe, there should > > be 2 fields - One to control the NAT enable/Disable and > > the second field to query teh status from NAT device. > > > > [ROHIT] the same field can is supposed to show the present status. > > Yup, You are right. Sorry about that. > > > > > As for item 2), this is "natConfServiceType" field in NatConfEntry as > below. > > NatConfEntry ::= SEQUENCE { > > natConfName SnmpAdminString, > > natConfServiceType INTEGER, > > natConfProtConfigName SnmpAdminString, > > natConfStorageType StorageType, > > natConfStatus RowStatus > > } > > So, including natConfName as a field within NatInterfcaeEntry will > > do the job, as you say. > > > > As for item 3, I am confused as to how an address map table is > > associated with the Interface. > > I understand, natConfig is constituted of: > > natConfTable, natConfAddrMapTable, natInterfaceTable, > > natConfUdpDefIdleTimeout, natConfIcmpDefIdleTimeout, > > natConfOtherDefIdleTimeout, natConfTcpDefIdleTimeout > > > > Now, How do you associate an Addressmap table with a specific > > interface? > > > > How is NatConfEntry (associated with a specific InterfaceTableEntry) > > associated with an AddrMaptable? Thanks. > > > > [ROHIT] The addrMap Tables have two indexes :-> > > natConfName, natConfAddrMapName. > > > OK. natConfName is currently not an index in AddrMapEntry. > I assume, you were suggesting to add this. > > [ROHIT] natConfName is already an index to the natAddrMapEntry. > > natConfAddrMapEntry OBJECT-TYPE > SYNTAX NatConfAddrMapEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "A description of a NAT entry. This entry > contributes to the dynamic or static NAT table of > the device." > INDEX { natConfName, natConfAddrMapName } > ::= { natConfAddrMapTable 1 } > > > I have a somewhat radically different thought on the organization > of natconf. Here it goes. Do let me know what you think. > > * I believe, we can simplify natConfig to consist of just > natInterfaceTable and natConfAddrMapTable. > > I.e., get rid of natConfTable, natConfUdpDefIdleTimeout, > natConfIcmpDefIdleTimeout, natConfOtherDefIdleTimeout, and > natConfTcpDefIdleTimeout from natConfig. > > * The natInterfaceTable may be expanded to contain > natConfUdpDefIdleTimeout, natConfIcmpDefIdleTimeout, > natConfOtherDefIdleTimeout, natConfTcpDefIdleTimeout, > natConfServiceType, natConfAddrMapName and > natConfProtConfigName fields > > natConfServiceType will describe the NAT-type for the > interface - Traiditional-NAT, Twice-NAT or Bidirectional-NAT. > > natConfAddrMapName will be the index into the NAT > Address map table. > > natConfProtConfigName will be the index into protocol > specific natProtConfTable (for the future) > > * The natConfAddrMapEntry may be expanded to include > AddrMapIndex field. > > So, all entries of an address map will be identified > by natConfAddrMapName, with differing index or rule number. > > > [ROHIT] The suggested approach is towards combining the natConfTable > and natInterfaceTable and then adding the pointer to the > natConfAddrMapName in the same table. > > I don't see any problem or issue with the approach. It is just > rearranging the config parameters. Whichever approach is more > close to the practical implementation, we should go ahead with that. > > > Thanks > Rohit > > <... stuff deleted> > > regards, > suresh > > __________________________________________________ > Do You Yahoo!? > Send your FREE holiday greetings online! > http://greetings.yahoo.com ===== __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From daemon@optimus.ietf.org Thu Jan 3 12:56:52 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 MAA07048 for ; Thu, 3 Jan 2002 12:56:52 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id MAA11849 for nat-archive@odin.ietf.org; Thu, 3 Jan 2002 12:56:54 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA11259; Thu, 3 Jan 2002 12:45:52 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA11223 for ; Thu, 3 Jan 2002 12:45:50 -0500 (EST) Received: from windlord.WWP.COM (mail.worldwidepackets.com [12.46.89.6]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06758 for ; Thu, 3 Jan 2002 12:45:47 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message Subject: RE: [NAT] RE: Re RE: Regarding NAT MIB MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Thu, 3 Jan 2002 09:46:19 -0800 Message-ID: <917063BAB0DDB043AF5FAA73C7A835D41A57E3@windlord.WWP.COM> Thread-Topic: [NAT] RE: Re RE: Regarding NAT MIB Thread-Index: AcGUE9ppTOgVUWF4SkeRIG5SIdlKDAAYca5A From: "Rohit Rohit" To: "Pyda Srisuresh" , "Rajendra Prasad" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id MAA11224 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: 8bit Hi Suresh, I get your point. I will make the changes and send the updated version by the end of this week. Just to make sure that natConfAddrMapEntry will still have two indexes. The first index will be natConfAddrMapName and the second index will be a rule number ( 1..MAX ). Thanks Rohit -----Original Message----- From: Pyda Srisuresh [mailto:srisuresh@yahoo.com] Sent: Wednesday, January 02, 2002 9:02 PM To: Rohit Rohit; Rajendra Prasad Cc: nat@ietf.org Subject: RE: [NAT] RE: Re RE: Regarding NAT MIB Rohit, Having just two tables to confiure (per-interface table and address-map table) makes the MIB simple and easy to follow. I would suggest the above. Thanks. cheers, suresh --- Rohit Rohit wrote: > Hi Suresh, > > My comments are inline. Please search for [ROHIT]. > > <... stuff deleted> > > --- Rohit Rohit wrote: > > > Hi, > > > > > > The main idea behind dividing the config info in the three > > > tables is the modularity and clarity. > > > > > > There are three steps in configuring the NAT :-> > > > > > > 1. enable\disable on the particular interface. > > > 2. define the type of nat and other protocol specific parameters. > > > 3. define the addrMap. > > > > > > So the three different tables just represent these three steps. > > > > > This is good. > > > > I see that each interface configuration is covered by NatInterfaceEntry. > > Within NatInterfaceEntry, I see > > 1) is covered by natInterfaceStatus, Even though I believe, there should > > be 2 fields - One to control the NAT enable/Disable and > > the second field to query teh status from NAT device. > > > > [ROHIT] the same field can is supposed to show the present status. > > Yup, You are right. Sorry about that. > > > > > As for item 2), this is "natConfServiceType" field in NatConfEntry as > below. > > NatConfEntry ::= SEQUENCE { > > natConfName SnmpAdminString, > > natConfServiceType INTEGER, > > natConfProtConfigName SnmpAdminString, > > natConfStorageType StorageType, > > natConfStatus RowStatus > > } > > So, including natConfName as a field within NatInterfcaeEntry will > > do the job, as you say. > > > > As for item 3, I am confused as to how an address map table is > > associated with the Interface. > > I understand, natConfig is constituted of: > > natConfTable, natConfAddrMapTable, natInterfaceTable, > > natConfUdpDefIdleTimeout, natConfIcmpDefIdleTimeout, > > natConfOtherDefIdleTimeout, natConfTcpDefIdleTimeout > > > > Now, How do you associate an Addressmap table with a specific > > interface? > > > > How is NatConfEntry (associated with a specific InterfaceTableEntry) > > associated with an AddrMaptable? Thanks. > > > > [ROHIT] The addrMap Tables have two indexes :-> > > natConfName, natConfAddrMapName. > > > OK. natConfName is currently not an index in AddrMapEntry. > I assume, you were suggesting to add this. > > [ROHIT] natConfName is already an index to the natAddrMapEntry. > > natConfAddrMapEntry OBJECT-TYPE > SYNTAX NatConfAddrMapEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "A description of a NAT entry. This entry > contributes to the dynamic or static NAT table of > the device." > INDEX { natConfName, natConfAddrMapName } > ::= { natConfAddrMapTable 1 } > > > I have a somewhat radically different thought on the organization > of natconf. Here it goes. Do let me know what you think. > > * I believe, we can simplify natConfig to consist of just > natInterfaceTable and natConfAddrMapTable. > > I.e., get rid of natConfTable, natConfUdpDefIdleTimeout, > natConfIcmpDefIdleTimeout, natConfOtherDefIdleTimeout, and > natConfTcpDefIdleTimeout from natConfig. > > * The natInterfaceTable may be expanded to contain > natConfUdpDefIdleTimeout, natConfIcmpDefIdleTimeout, > natConfOtherDefIdleTimeout, natConfTcpDefIdleTimeout, > natConfServiceType, natConfAddrMapName and > natConfProtConfigName fields > > natConfServiceType will describe the NAT-type for the > interface - Traiditional-NAT, Twice-NAT or Bidirectional-NAT. > > natConfAddrMapName will be the index into the NAT > Address map table. > > natConfProtConfigName will be the index into protocol > specific natProtConfTable (for the future) > > * The natConfAddrMapEntry may be expanded to include > AddrMapIndex field. > > So, all entries of an address map will be identified > by natConfAddrMapName, with differing index or rule number. > > > [ROHIT] The suggested approach is towards combining the natConfTable > and natInterfaceTable and then adding the pointer to the > natConfAddrMapName in the same table. > > I don't see any problem or issue with the approach. It is just > rearranging the config parameters. Whichever approach is more > close to the practical implementation, we should go ahead with that. > > > Thanks > Rohit > > <... stuff deleted> > > regards, > suresh > > __________________________________________________ > Do You Yahoo!? > Send your FREE holiday greetings online! > http://greetings.yahoo.com ===== __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From nat-admin@ietf.org Thu Jan 3 12:56:51 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 MAA07043; Thu, 3 Jan 2002 12:56:51 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA11259; Thu, 3 Jan 2002 12:45:52 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA11223 for ; Thu, 3 Jan 2002 12:45:50 -0500 (EST) Received: from windlord.WWP.COM (mail.worldwidepackets.com [12.46.89.6]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06758 for ; Thu, 3 Jan 2002 12:45:47 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message Subject: RE: [NAT] RE: Re RE: Regarding NAT MIB MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Thu, 3 Jan 2002 09:46:19 -0800 Message-ID: <917063BAB0DDB043AF5FAA73C7A835D41A57E3@windlord.WWP.COM> Thread-Topic: [NAT] RE: Re RE: Regarding NAT MIB Thread-Index: AcGUE9ppTOgVUWF4SkeRIG5SIdlKDAAYca5A From: "Rohit Rohit" To: "Pyda Srisuresh" , "Rajendra Prasad" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id MAA11224 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: 8bit Hi Suresh, I get your point. I will make the changes and send the updated version by the end of this week. Just to make sure that natConfAddrMapEntry will still have two indexes. The first index will be natConfAddrMapName and the second index will be a rule number ( 1..MAX ). Thanks Rohit -----Original Message----- From: Pyda Srisuresh [mailto:srisuresh@yahoo.com] Sent: Wednesday, January 02, 2002 9:02 PM To: Rohit Rohit; Rajendra Prasad Cc: nat@ietf.org Subject: RE: [NAT] RE: Re RE: Regarding NAT MIB Rohit, Having just two tables to confiure (per-interface table and address-map table) makes the MIB simple and easy to follow. I would suggest the above. Thanks. cheers, suresh --- Rohit Rohit wrote: > Hi Suresh, > > My comments are inline. Please search for [ROHIT]. > > <... stuff deleted> > > --- Rohit Rohit wrote: > > > Hi, > > > > > > The main idea behind dividing the config info in the three > > > tables is the modularity and clarity. > > > > > > There are three steps in configuring the NAT :-> > > > > > > 1. enable\disable on the particular interface. > > > 2. define the type of nat and other protocol specific parameters. > > > 3. define the addrMap. > > > > > > So the three different tables just represent these three steps. > > > > > This is good. > > > > I see that each interface configuration is covered by NatInterfaceEntry. > > Within NatInterfaceEntry, I see > > 1) is covered by natInterfaceStatus, Even though I believe, there should > > be 2 fields - One to control the NAT enable/Disable and > > the second field to query teh status from NAT device. > > > > [ROHIT] the same field can is supposed to show the present status. > > Yup, You are right. Sorry about that. > > > > > As for item 2), this is "natConfServiceType" field in NatConfEntry as > below. > > NatConfEntry ::= SEQUENCE { > > natConfName SnmpAdminString, > > natConfServiceType INTEGER, > > natConfProtConfigName SnmpAdminString, > > natConfStorageType StorageType, > > natConfStatus RowStatus > > } > > So, including natConfName as a field within NatInterfcaeEntry will > > do the job, as you say. > > > > As for item 3, I am confused as to how an address map table is > > associated with the Interface. > > I understand, natConfig is constituted of: > > natConfTable, natConfAddrMapTable, natInterfaceTable, > > natConfUdpDefIdleTimeout, natConfIcmpDefIdleTimeout, > > natConfOtherDefIdleTimeout, natConfTcpDefIdleTimeout > > > > Now, How do you associate an Addressmap table with a specific > > interface? > > > > How is NatConfEntry (associated with a specific InterfaceTableEntry) > > associated with an AddrMaptable? Thanks. > > > > [ROHIT] The addrMap Tables have two indexes :-> > > natConfName, natConfAddrMapName. > > > OK. natConfName is currently not an index in AddrMapEntry. > I assume, you were suggesting to add this. > > [ROHIT] natConfName is already an index to the natAddrMapEntry. > > natConfAddrMapEntry OBJECT-TYPE > SYNTAX NatConfAddrMapEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "A description of a NAT entry. This entry > contributes to the dynamic or static NAT table of > the device." > INDEX { natConfName, natConfAddrMapName } > ::= { natConfAddrMapTable 1 } > > > I have a somewhat radically different thought on the organization > of natconf. Here it goes. Do let me know what you think. > > * I believe, we can simplify natConfig to consist of just > natInterfaceTable and natConfAddrMapTable. > > I.e., get rid of natConfTable, natConfUdpDefIdleTimeout, > natConfIcmpDefIdleTimeout, natConfOtherDefIdleTimeout, and > natConfTcpDefIdleTimeout from natConfig. > > * The natInterfaceTable may be expanded to contain > natConfUdpDefIdleTimeout, natConfIcmpDefIdleTimeout, > natConfOtherDefIdleTimeout, natConfTcpDefIdleTimeout, > natConfServiceType, natConfAddrMapName and > natConfProtConfigName fields > > natConfServiceType will describe the NAT-type for the > interface - Traiditional-NAT, Twice-NAT or Bidirectional-NAT. > > natConfAddrMapName will be the index into the NAT > Address map table. > > natConfProtConfigName will be the index into protocol > specific natProtConfTable (for the future) > > * The natConfAddrMapEntry may be expanded to include > AddrMapIndex field. > > So, all entries of an address map will be identified > by natConfAddrMapName, with differing index or rule number. > > > [ROHIT] The suggested approach is towards combining the natConfTable > and natInterfaceTable and then adding the pointer to the > natConfAddrMapName in the same table. > > I don't see any problem or issue with the approach. It is just > rearranging the config parameters. Whichever approach is more > close to the practical implementation, we should go ahead with that. > > > Thanks > Rohit > > <... stuff deleted> > > regards, > suresh > > __________________________________________________ > Do You Yahoo!? > Send your FREE holiday greetings online! > http://greetings.yahoo.com ===== __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From daemon@optimus.ietf.org Thu Jan 3 13:43:38 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 NAA07899 for ; Thu, 3 Jan 2002 13:43:38 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA13619 for nat-archive@odin.ietf.org; Thu, 3 Jan 2002 13:43:40 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13427; Thu, 3 Jan 2002 13:36:23 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13398 for ; Thu, 3 Jan 2002 13:36:21 -0500 (EST) Received: from web13802.mail.yahoo.com (web13802.mail.yahoo.com [216.136.175.12]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA07761 for ; Thu, 3 Jan 2002 13:36:18 -0500 (EST) Message-ID: <20020103183620.15209.qmail@web13802.mail.yahoo.com> Received: from [66.89.112.150] by web13802.mail.yahoo.com via HTTP; Thu, 03 Jan 2002 10:36:20 PST Date: Thu, 3 Jan 2002 10:36:20 -0800 (PST) From: Pyda Srisuresh Subject: RE: [NAT] RE: Re RE: Regarding NAT MIB To: Rohit Rohit , Rajendra Prasad Cc: nat@ietf.org In-Reply-To: <917063BAB0DDB043AF5FAA73C7A835D41A57E3@windlord.WWP.COM> 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 Sounds good. Thanks. cheers, suresh --- Rohit Rohit wrote: > Hi Suresh, > > I get your point. > I will make the changes and send the updated > version by the end of this week. > > Just to make sure that natConfAddrMapEntry will still have two indexes. > The first index will be natConfAddrMapName and the second index will > be a rule number ( 1..MAX ). > > Thanks > Rohit > > -----Original Message----- > From: Pyda Srisuresh [mailto:srisuresh@yahoo.com] > Sent: Wednesday, January 02, 2002 9:02 PM > To: Rohit Rohit; Rajendra Prasad > Cc: nat@ietf.org > Subject: RE: [NAT] RE: Re RE: Regarding NAT MIB > > > > Rohit, > > Having just two tables to confiure (per-interface table and > address-map table) makes the MIB simple and easy to follow. > > I would suggest the above. Thanks. > > cheers, > suresh > > --- Rohit Rohit wrote: > > Hi Suresh, > > > > My comments are inline. Please search for [ROHIT]. > > > > <... stuff deleted> > > > --- Rohit Rohit wrote: > > > > Hi, > > > > > > > > The main idea behind dividing the config info in the three > > > > tables is the modularity and clarity. > > > > > > > > There are three steps in configuring the NAT :-> > > > > > > > > 1. enable\disable on the particular interface. > > > > 2. define the type of nat and other protocol specific parameters. > > > > 3. define the addrMap. > > > > > > > > So the three different tables just represent these three steps. > > > > > > > This is good. > > > > > > I see that each interface configuration is covered by NatInterfaceEntry. > > > Within NatInterfaceEntry, I see > > > 1) is covered by natInterfaceStatus, Even though I believe, there > should > > > be 2 fields - One to control the NAT enable/Disable and > > > the second field to query teh status from NAT device. > > > > > > [ROHIT] the same field can is supposed to show the present status. > > > > Yup, You are right. Sorry about that. > > > > > > > > As for item 2), this is "natConfServiceType" field in NatConfEntry as > > below. > > > NatConfEntry ::= SEQUENCE { > > > natConfName SnmpAdminString, > > > natConfServiceType INTEGER, > > > natConfProtConfigName SnmpAdminString, > > > natConfStorageType StorageType, > > > natConfStatus RowStatus > > > } > > > So, including natConfName as a field within NatInterfcaeEntry will > > > do the job, as you say. > > > > > > As for item 3, I am confused as to how an address map table is > > > associated with the Interface. > > > I understand, natConfig is constituted of: > > > natConfTable, natConfAddrMapTable, natInterfaceTable, > > > natConfUdpDefIdleTimeout, natConfIcmpDefIdleTimeout, > > > natConfOtherDefIdleTimeout, natConfTcpDefIdleTimeout > > > > > > Now, How do you associate an Addressmap table with a specific > > > interface? > > > > > > How is NatConfEntry (associated with a specific InterfaceTableEntry) > > > associated with an AddrMaptable? Thanks. > > > > > > [ROHIT] The addrMap Tables have two indexes :-> > > > natConfName, natConfAddrMapName. > > > > > OK. natConfName is currently not an index in AddrMapEntry. > > I assume, you were suggesting to add this. > > > > [ROHIT] natConfName is already an index to the natAddrMapEntry. > > > > natConfAddrMapEntry OBJECT-TYPE > > SYNTAX NatConfAddrMapEntry > > MAX-ACCESS not-accessible > > STATUS current > > DESCRIPTION > > "A description of a NAT entry. This entry > > contributes to the dynamic or static NAT table of > > the device." > > INDEX { natConfName, natConfAddrMapName } > > ::= { natConfAddrMapTable 1 } > > > > > > I have a somewhat radically different thought on the organization > > of natconf. Here it goes. Do let me know what you think. > > > > * I believe, we can simplify natConfig to consist of just > > natInterfaceTable and natConfAddrMapTable. > > > > I.e., get rid of natConfTable, natConfUdpDefIdleTimeout, > > natConfIcmpDefIdleTimeout, natConfOtherDefIdleTimeout, and > > natConfTcpDefIdleTimeout from natConfig. > > > > * The natInterfaceTable may be expanded to contain > > natConfUdpDefIdleTimeout, natConfIcmpDefIdleTimeout, > > natConfOtherDefIdleTimeout, natConfTcpDefIdleTimeout, > > natConfServiceType, natConfAddrMapName and > > natConfProtConfigName fields > > > > natConfServiceType will describe the NAT-type for the > > interface - Traiditional-NAT, Twice-NAT or Bidirectional-NAT. > > > > natConfAddrMapName will be the index into the NAT > > Address map table. > > > > natConfProtConfigName will be the index into protocol > > specific natProtConfTable (for the future) > > > > * The natConfAddrMapEntry may be expanded to include > > AddrMapIndex field. > > > > So, all entries of an address map will be identified > > by natConfAddrMapName, with differing index or rule number. > > > > > > [ROHIT] The suggested approach is towards combining the natConfTable > > and natInterfaceTable and then adding the pointer to the > > natConfAddrMapName in the same table. > > > > I don't see any problem or issue with the approach. It is just > > rearranging the config parameters. Whichever approach is more > > close to the practical implementation, we should go ahead with > that. > > > > > > Thanks > > Rohit > > > > <... stuff deleted> > > > > regards, > > suresh > > > > __________________________________________________ > > Do You Yahoo!? > > Send your FREE holiday greetings online! > > http://greetings.yahoo.com > > > ===== > > > __________________________________________________ > Do You Yahoo!? > Send your FREE holiday greetings online! > http://greetings.yahoo.com ===== __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From nat-admin@ietf.org Thu Jan 3 13:43:37 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 NAA07894; Thu, 3 Jan 2002 13:43:37 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13427; Thu, 3 Jan 2002 13:36:23 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13398 for ; Thu, 3 Jan 2002 13:36:21 -0500 (EST) Received: from web13802.mail.yahoo.com (web13802.mail.yahoo.com [216.136.175.12]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA07761 for ; Thu, 3 Jan 2002 13:36:18 -0500 (EST) Message-ID: <20020103183620.15209.qmail@web13802.mail.yahoo.com> Received: from [66.89.112.150] by web13802.mail.yahoo.com via HTTP; Thu, 03 Jan 2002 10:36:20 PST Date: Thu, 3 Jan 2002 10:36:20 -0800 (PST) From: Pyda Srisuresh Subject: RE: [NAT] RE: Re RE: Regarding NAT MIB To: Rohit Rohit , Rajendra Prasad Cc: nat@ietf.org In-Reply-To: <917063BAB0DDB043AF5FAA73C7A835D41A57E3@windlord.WWP.COM> 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 Sounds good. Thanks. cheers, suresh --- Rohit Rohit wrote: > Hi Suresh, > > I get your point. > I will make the changes and send the updated > version by the end of this week. > > Just to make sure that natConfAddrMapEntry will still have two indexes. > The first index will be natConfAddrMapName and the second index will > be a rule number ( 1..MAX ). > > Thanks > Rohit > > -----Original Message----- > From: Pyda Srisuresh [mailto:srisuresh@yahoo.com] > Sent: Wednesday, January 02, 2002 9:02 PM > To: Rohit Rohit; Rajendra Prasad > Cc: nat@ietf.org > Subject: RE: [NAT] RE: Re RE: Regarding NAT MIB > > > > Rohit, > > Having just two tables to confiure (per-interface table and > address-map table) makes the MIB simple and easy to follow. > > I would suggest the above. Thanks. > > cheers, > suresh > > --- Rohit Rohit wrote: > > Hi Suresh, > > > > My comments are inline. Please search for [ROHIT]. > > > > <... stuff deleted> > > > --- Rohit Rohit wrote: > > > > Hi, > > > > > > > > The main idea behind dividing the config info in the three > > > > tables is the modularity and clarity. > > > > > > > > There are three steps in configuring the NAT :-> > > > > > > > > 1. enable\disable on the particular interface. > > > > 2. define the type of nat and other protocol specific parameters. > > > > 3. define the addrMap. > > > > > > > > So the three different tables just represent these three steps. > > > > > > > This is good. > > > > > > I see that each interface configuration is covered by NatInterfaceEntry. > > > Within NatInterfaceEntry, I see > > > 1) is covered by natInterfaceStatus, Even though I believe, there > should > > > be 2 fields - One to control the NAT enable/Disable and > > > the second field to query teh status from NAT device. > > > > > > [ROHIT] the same field can is supposed to show the present status. > > > > Yup, You are right. Sorry about that. > > > > > > > > As for item 2), this is "natConfServiceType" field in NatConfEntry as > > below. > > > NatConfEntry ::= SEQUENCE { > > > natConfName SnmpAdminString, > > > natConfServiceType INTEGER, > > > natConfProtConfigName SnmpAdminString, > > > natConfStorageType StorageType, > > > natConfStatus RowStatus > > > } > > > So, including natConfName as a field within NatInterfcaeEntry will > > > do the job, as you say. > > > > > > As for item 3, I am confused as to how an address map table is > > > associated with the Interface. > > > I understand, natConfig is constituted of: > > > natConfTable, natConfAddrMapTable, natInterfaceTable, > > > natConfUdpDefIdleTimeout, natConfIcmpDefIdleTimeout, > > > natConfOtherDefIdleTimeout, natConfTcpDefIdleTimeout > > > > > > Now, How do you associate an Addressmap table with a specific > > > interface? > > > > > > How is NatConfEntry (associated with a specific InterfaceTableEntry) > > > associated with an AddrMaptable? Thanks. > > > > > > [ROHIT] The addrMap Tables have two indexes :-> > > > natConfName, natConfAddrMapName. > > > > > OK. natConfName is currently not an index in AddrMapEntry. > > I assume, you were suggesting to add this. > > > > [ROHIT] natConfName is already an index to the natAddrMapEntry. > > > > natConfAddrMapEntry OBJECT-TYPE > > SYNTAX NatConfAddrMapEntry > > MAX-ACCESS not-accessible > > STATUS current > > DESCRIPTION > > "A description of a NAT entry. This entry > > contributes to the dynamic or static NAT table of > > the device." > > INDEX { natConfName, natConfAddrMapName } > > ::= { natConfAddrMapTable 1 } > > > > > > I have a somewhat radically different thought on the organization > > of natconf. Here it goes. Do let me know what you think. > > > > * I believe, we can simplify natConfig to consist of just > > natInterfaceTable and natConfAddrMapTable. > > > > I.e., get rid of natConfTable, natConfUdpDefIdleTimeout, > > natConfIcmpDefIdleTimeout, natConfOtherDefIdleTimeout, and > > natConfTcpDefIdleTimeout from natConfig. > > > > * The natInterfaceTable may be expanded to contain > > natConfUdpDefIdleTimeout, natConfIcmpDefIdleTimeout, > > natConfOtherDefIdleTimeout, natConfTcpDefIdleTimeout, > > natConfServiceType, natConfAddrMapName and > > natConfProtConfigName fields > > > > natConfServiceType will describe the NAT-type for the > > interface - Traiditional-NAT, Twice-NAT or Bidirectional-NAT. > > > > natConfAddrMapName will be the index into the NAT > > Address map table. > > > > natConfProtConfigName will be the index into protocol > > specific natProtConfTable (for the future) > > > > * The natConfAddrMapEntry may be expanded to include > > AddrMapIndex field. > > > > So, all entries of an address map will be identified > > by natConfAddrMapName, with differing index or rule number. > > > > > > [ROHIT] The suggested approach is towards combining the natConfTable > > and natInterfaceTable and then adding the pointer to the > > natConfAddrMapName in the same table. > > > > I don't see any problem or issue with the approach. It is just > > rearranging the config parameters. Whichever approach is more > > close to the practical implementation, we should go ahead with > that. > > > > > > Thanks > > Rohit > > > > <... stuff deleted> > > > > regards, > > suresh > > > > __________________________________________________ > > Do You Yahoo!? > > Send your FREE holiday greetings online! > > http://greetings.yahoo.com > > > ===== > > > __________________________________________________ > Do You Yahoo!? > Send your FREE holiday greetings online! > http://greetings.yahoo.com ===== __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From nat-admin@ietf.org Wed Jan 16 12:41:04 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 MAA15316; Wed, 16 Jan 2002 12:41:04 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA10959; Wed, 16 Jan 2002 12:26:46 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA10933 for ; Wed, 16 Jan 2002 12:26:44 -0500 (EST) Received: from linuxpow.com (IDENT:qmailr@linuxpow.com [12.149.2.10]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA14897 for ; Wed, 16 Jan 2002 12:26:37 -0500 (EST) Date: Wed, 16 Jan 2002 12:26:37 -0500 (EST) Message-Id: <200201161726.MAA14897@ietf.org> Received: (qmail 5343 invoked from network); 16 Jan 2002 16:34:55 -0000 Received: from buystainlessonline.com (HELO ) (nobody@12.149.2.55) by mail.buystainlessonline.com with SMTP; 16 Jan 2002 16:34:55 -0000 To: nat@ietf.org From: "BuyStainlessOnline.com" Subject: [NAT] The Stainless Steel Network MEGA DEAL 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 Unsubscribe by clicking the link at the bottom of this E-mail! It's quick and painless. The Stainless Steel Network is brought to you by www.buystainlessonline.com What BuyStainlessOnline users are doing... ---------------------------------------------------------------------- RECENT INQUIRIES: 904L Round Bar 168' 10mm 60'16mm 49' 25mm NO QUOTE YET 321 Stainless Plate 1/2 x 60 x 96 (7) pcs QUOTED 440C material, .500" dia x 144" long (840) pcs QUOTED 310 16ga 48 x 120 20 sheets QUOTED ------------------------------------------------------------------------ New Items for Sale OFFER #1 (looking for Best Offer) Commodity - Stainless Steel Wire. Grade - AISI 304L. Size - 0.135" Surface finish - Matte (Medium Bright) Condition - Soft Annealed. U.T.S. - 85,000 to 100,000 psi max. Quantity - aprox. 40,000 lbs. Packing - Coils wrapped in HDPE and loaded on Mild Steel Carriers. Remarks : All material is ex-mill in original mill's packaging. OFFER #2 Attention Distributors!!! 3,000,000 Pounds of PRIME 304 COILS for sale The following list of Stainless Steel Hot Rolled Coils is available FOB Ohio for the following PRICES: $.50 per pound (1 LOAD min) $.47 per pound (10 LOAD min) NOTE, these coils are MILL PRIME... Chemical Properties are listed below ------------------------------------------------------------------------ STEEL FIN WIDTH (mm) THICK (mm) Weigth (Pounds) C Cr Cu Mn Mo N Ni P S Si 304 1 950.0 3.00 37,238 0.0450 18.070 0.330 1.470 0.230 0.055 8.090 0.027 0.001 0.350 304 1 946.0 3.00 31,698 0.0470 18.070 0.280 1.320 0.250 0.042 8.040 0.030 0.001 0.360 304 1 1256.0 3.00 49,310 0.0440 18.110 0.240 1.340 0.240 0.042 8.050 0.030 0.001 0.370 304 1 1255.0 3.00 44,451 0.0500 18.290 0.240 1.370 0.250 0.046 8.030 0.031 0.001 0.420 304 1 1254.0 3.00 44,572 0.0500 18.290 0.240 1.370 0.250 0.046 8.030 0.031 0.001 0.420 304 1 1254.0 3.00 46,113 0.0500 18.060 0.320 1.350 0.350 0.042 8.070 0.030 0.001 0.420 304 1 799.5 3.00 31,239 0.0432 18.110 0.250 1.350 0.270 0.042 8.100 0.029 0.001 0.340 304 1 794.0 3.00 30,328 0.0410 18.220 0.280 1.420 0.300 0.047 8.120 0.030 0.001 0.350 304 1 1256.5 3.00 49,583 0.0420 18.110 0.250 1.350 0.270 0.045 8.100 0.029 0.001 0.340 304 1 1254.5 3.00 49,453 0.0420 18.110 0.250 1.350 0.270 0.045 8.100 0.029 0.001 0.340 304 1 1255.0 3.00 48,305 0.0450 18.020 0.320 1.390 0.310 0.046 8.000 0.028 0.001 0.360 304 1 1252.5 6.00 49,449 0.0420 18.030 0.330 1.360 0.240 0.050 8.070 0.025 0.001 0.390 304 1 1251.5 6.00 49,427 0.0410 18.020 0.300 1.350 0.260 0.045 8.090 0.028 0.001 0.380 304 1 1250.5 6.00 49,414 0.0410 18.020 0.300 1.350 0.260 0.045 8.090 0.028 0.001 0.380 304 1 1253.5 6.00 49,414 0.0450 18.080 0.300 1.320 0.250 0.050 8.100 0.031 0.001 0.350 304 1 1255.5 3.00 41,821 0.0430 18.070 0.340 1.390 0.270 0.051 8.100 0.026 0.001 0.480 304 1 1255.5 2.80 49,623 0.0430 18.070 0.340 1.390 0.270 0.051 8.100 0.026 0.001 0.480 304 1 1254.5 2.80 49,438 0.0420 18.090 0.330 1.400 0.330 0.043 8.150 0.026 0.001 0.360 304 1 1254.0 2.80 49,436 0.0420 18.030 0.330 1.360 0.240 0.050 8.070 0.025 0.001 0.390 304 1 1251.0 2.80 48,435 0.0410 18.060 0.270 1.330 0.250 0.051 8.150 0.026 0.001 0.340 304 1 1256.0 2.80 49,387 0.0410 18.060 0.270 1.330 0.250 0.051 8.150 0.026 0.001 0.340 304 1 1254.5 2.80 49,493 0.0410 18.060 0.270 1.330 0.250 0.051 8.150 0.026 0.001 0.340 304 1 1253.5 2.80 48,457 0.0410 18.060 0.270 1.330 0.250 0.051 8.150 0.026 0.001 0.340 304 1 1221.5 6.00 49,074 0.0430 18.060 0.410 1.350 0.240 0.049 8.070 0.027 0.001 0.470 304 1 1254.5 6.00 49,334 0.0430 18.060 0.410 1.350 0.240 0.049 8.070 0.027 0.001 0.470 304 1 1251.0 6.00 48,155 0.0400 18.040 0.320 1.410 0.200 0.050 8.060 0.029 0.001 0.360 34A 1 947.0 4.70 37,310 0.0390 18.130 0.260 1.340 0.190 0.047 8.550 0.027 0.001 0.370 304 1 951.5 3.00 36,565 0.0450 18.050 0.340 1.500 0.270 0.049 8.080 0.031 0.001 0.440 304 1 950.0 3.00 37,200 0.0450 18.050 0.340 1.500 0.270 0.049 8.080 0.031 0.001 0.440 304 1 951.0 3.00 37,299 0.0450 18.050 0.340 1.500 0.270 0.049 8.080 0.031 0.001 0.440 304 1 949.5 3.00 37,337 0.0450 18.050 0.340 1.500 0.270 0.049 8.080 0.031 0.001 0.440 304 1 948.5 3.00 37,260 0.0450 18.050 0.340 1.500 0.270 0.049 8.080 0.031 0.001 0.440 304 1 1252.0 6.00 43,333 0.0450 18.080 0.300 1.320 0.250 0.050 8.100 0.031 0.001 0.350 304 1 1251.5 6.00 49,561 0.0450 18.080 0.300 1.320 0.250 0.050 8.100 0.031 0.001 0.350 304 1 946.5 3.00 37,211 0.0450 18.070 0.330 1.470 0.230 0.055 8.090 0.027 0.001 0.350 304 1 947.5 3.00 37,277 0.0450 18.070 0.330 1.470 0.230 0.055 8.090 0.027 0.001 0.350 304 1 951.5 3.00 37,134 0.0450 18.070 0.330 1.470 0.230 0.055 8.090 0.027 0.001 0.350 304 1 949.0 3.00 36,490 0.0450 18.070 0.330 1.470 0.230 0.055 8.090 0.027 0.001 0.350 304 1 1255.0 3.00 48,450 0.0460 18.030 0.240 1.370 0.210 0.042 8.030 0.029 0.001 0.360 304 1 1256.0 3.00 48,338 0.0460 18.030 0.240 1.370 0.210 0.042 8.030 0.029 0.001 0.360 304 1 1254.5 3.00 49,195 0.0460 18.030 0.240 1.370 0.210 0.042 8.030 0.029 0.001 0.360 304 1 1255.5 3.00 49,449 0.0460 18.030 0.240 1.370 0.210 0.042 8.030 0.029 0.001 0.360 304 1 1256.5 3.00 48,638 0.0450 18.090 0.250 1.360 0.250 0.049 8.070 0.028 0.001 0.370 304 1 1255.5 3.00 47,672 0.0450 18.090 0.250 1.360 0.250 0.049 8.070 0.028 0.001 0.370 304 1 1255.5 3.00 49,482 0.0450 18.090 0.250 1.360 0.250 0.049 8.070 0.028 0.001 0.370 304 1 1254.5 3.00 49,493 0.0450 18.090 0.250 1.360 0.250 0.049 8.070 0.028 0.001 0.370 304 1 1239.0 3.00 49,151 0.0450 18.090 0.250 1.360 0.250 0.049 8.070 0.028 0.001 0.370 304 1 1255.0 6.00 49,475 0.0490 18.030 0.260 1.320 0.280 0.046 8.010 0.031 0.001 0.350 304 1 1254.5 6.00 49,286 0.0490 18.030 0.260 1.320 0.280 0.046 8.010 0.031 0.001 0.350 304 1 1251.5 6.00 48,415 0.0430 18.030 0.250 1.340 0.270 0.050 8.090 0.030 0.001 0.350 304 1 1251.0 6.00 47,824 0.0430 18.030 0.250 1.340 0.270 0.050 8.090 0.030 0.001 0.350 304 1 1252.5 6.00 48,364 0.0430 18.030 0.250 1.340 0.270 0.050 8.090 0.030 0.001 0.350 34A 1 795.0 3.00 28,968 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 34A 1 798.0 3.00 31,367 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 34A 1 797.0 3.00 31,389 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 34A 1 796.5 3.00 31,338 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 34A 1 798.5 3.00 31,550 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 34A 1 797.5 3.00 31,473 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 34A 1 800.0 3.00 30,613 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 34A 1 798.0 3.00 30,988 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 34A 1 796.0 3.00 31,354 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 34A 1 798.0 3.00 29,374 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 304 1 1255.0 3.00 41,960 0.0490 18.030 0.260 1.320 0.280 0.046 8.010 0.031 0.001 0.350 304 1 1253.5 3.00 41,675 0.0490 18.030 0.260 1.320 0.280 0.046 8.010 0.031 0.001 0.350 304 1 1257.0 3.00 43,397 0.0420 18.060 0.300 1.380 0.340 0.048 8.040 0.028 0.001 0.350 304 1 1258.0 3.00 49,409 0.0410 18.030 0.270 1.340 0.250 0.050 8.040 0.027 0.001 0.290 304 1 1253.0 3.00 49,433 0.0410 18.030 0.270 1.340 0.250 0.050 8.040 0.027 0.001 0.290 304 1 1253.0 3.00 49,563 0.0400 18.080 0.270 1.390 0.270 0.050 8.070 0.028 0.001 0.350 304 1 1253.0 3.00 49,497 0.0400 18.080 0.270 1.390 0.270 0.050 8.070 0.028 0.001 0.350 304 1 1256.0 3.00 49,548 0.0400 18.080 0.270 1.390 0.270 0.050 8.070 0.028 0.001 0.350 304 1 1254.5 3.00 48,616 0.0400 18.080 0.270 1.390 0.270 0.050 8.070 0.028 0.001 0.350 304 1 1258.0 3.00 48,580 0.0400 18.080 0.270 1.390 0.270 0.050 8.070 0.028 0.001 0.350 304 1 1254.0 3.00 49,460 0.0420 18.060 0.300 1.380 0.340 0.048 8.040 0.028 0.001 0.350 304 1 1254.0 3.00 48,472 0.0430 18.200 0.260 1.360 0.260 0.043 8.070 0.028 0.001 0.380 34A 1 800.5 3.00 31,534 0.0410 18.030 0.330 1.340 0.250 0.050 8.530 0.029 0.001 0.360 34A 1 798.0 3.00 31,495 0.0410 18.030 0.330 1.340 0.250 0.050 8.530 0.029 0.001 0.360 34A 1 799.0 3.00 31,499 0.0410 18.030 0.330 1.340 0.250 0.050 8.530 0.029 0.001 0.360 34A 1 797.5 3.00 31,561 0.0410 18.030 0.330 1.340 0.250 0.050 8.530 0.029 0.001 0.360 3,343,970 OFFER #3 Stainless Steel SLIT COIL REMNANTS FOB PHILADELPHIA, PRICES LISTED BELOW, NO MINIMUM PURCHASE. This information is provided by BuyStainlessOnline, Inc. www.buystainlessonline.com Please email Sales@buystainlessonline.com or call 215.604.5922 to place orders. All materials are subject to prior sale. Tag Description Finish Thickness Width Quantity Weight Location Sale Price Regular Price 45146 28 GA 304 2B 0.015 18 1 5031 Phila, P.a. USA $1.10 $1.38 30794 26 GA 201 2D 0.020 21.5 1 4158 Phila, P.a. USA $0.88 $1.09 26202 26 GA 301 2B 0.020 1.375 1 418 Phila, P.a. USA $0.63 $0.78 232512E 26 GA 304 2B 0.020 1.5 3 386 Phila, P.a. USA $0.64 $0.80 45062 26 GA 304 POL/VC 0.020 11.75 1 2393 Phila, P.a. USA $0.63 $0.78 229878 26 GA 430 2B 0.020 3.5 2 936 Phila, P.a. USA $0.19 $0.23 22840 26 GA 430 BA 0.020 4.5 1 906 Phila, P.a. USA $0.25 $0.31 29364 24 GA 301 POL 0.024 4 1 1427 Phila, P.a. USA $0.65 $0.81 29363 24 GA 301 POL 0.024 4 1 1430 Phila, P.a. USA $0.65 $0.81 35176 24 GA 301 POL 0.024 6 2 4727 Phila, P.a. USA $0.53 $0.66 29362A 24 GA 304 POL 0.024 1.187 4 1024 Phila, P.a. USA $0.85 $1.06 186896 24 GA 304 2B 0.024 2.75 9 2790 Phila, P.a. USA $0.75 $0.94 19023 24 GA 304 2B 0.024 3.75 2 2762 Phila, P.a. USA $0.71 $0.89 61931 24 GA 304 2B 0.024 9 1 1122 Phila, P.a. USA $0.59 $0.73 29584 22 GA 301 POL 0.028 3.5 1 680 Phila, P.a. USA $0.66 $0.83 32794 22 GA 301 2B 0.028 6.75 1 1578 Phila, P.a. USA $0.54 $0.67 84108C 22 GA 304 POL 0.028 1.125 2 444 Phila, P.a. USA $0.90 $1.13 29362B 22 GA 304 POL 0.028 1.187 6 1229 Phila, P.a. USA $0.85 $1.06 32948 22 GA 304 POL 0.028 3.75 2 2858 Phila, P.a. USA $0.53 $0.66 44796 22 GA 304 POL 0.028 11.25 1 2159 Phila, P.a. USA $0.69 $0.86 224335 22 GA 430 POL 0.028 5.5 1 970 Phila, P.a. USA $0.06 $0.08 45099 22 GA 430 BA 0.028 10 1 2175 Phila, P.a. USA $0.34 $0.42 45098 22 GA 430 BA 0.028 10 1 2376 Phila, P.a. USA $0.34 $0.42 243739 20 GA 304 2D 0.035 1.5 3 1194 Phila, P.a. USA $0.88 $1.09 32943 20 GA 304 POL 0.035 3.125 3 2218 Phila, P.a. USA $0.78 $0.97 46336C 20 GA 304 POL 0.035 3.5 1 1013 Phila, P.a. USA $0.99 $1.23 48418E 20 GA 304 POL 0.035 4.125 1 877 Phila, P.a. USA $0.88 $1.09 49488 20 GA 304 2B 0.036 6.1 1 948 Phila, P.a. USA $0.71 $0.89 232335D 18 GA 304 POL 0.048 1.75 4 1111 Phila, P.a. USA $0.68 $0.84 27329 18 GA 304 AF 0.048 1.875 1 260 Phila, P.a. USA $0.44 $0.55 32953 18 GA 304 POL 0.048 2.5 1 513 Phila, P.a. USA $0.53 $0.66 186895 18 GA 304 AF 0.048 3.5 1 610 Phila, P.a. USA $0.75 $0.94 43255 18 GA 304 POL 0.048 5.25 4 5076 Phila, P.a. USA $0.44 $0.55 212565 18 GA 409 2B 0.048 3.75 1 1143 Phila, P.a. USA $0.09 $0.11 191101C 16 GA 304 POL 0.058 1 2 386 Phila, P.a. USA $0.98 $1.22 191101B 16 GA 304 POL 0.058 2 3 1490 Phila, P.a. USA $0.98 $1.22 44820 16 GA 304 BA 0.058 10 1 7504 Phila, P.a. USA $0.69 $0.86 33017 16 GA 430 2B 0.058 4 1 1249 Phila, P.a. USA $0.25 $0.31 43259 14 GA 304 POL 0.075 2.625 2 2684 Phila, P.a. USA $0.44 $0.55 43258 14 GA 304 POL 0.075 4.5 2 1750 Phila, P.a. USA $0.44 $0.55 43260 14 GA 304 POL 0.075 4.75 2 1977 Phila, P.a. USA $0.44 $0.55 27327 14 GA 409 AF 0.075 4.562 1 550 Phila, P.a. USA $0.31 $0.39 27328 14 GA 409 AF 0.075 4.687 1 531 Phila, P.a. USA $0.31 $0.39 35360 MISC GA 3003 H14 0.075 1 4 319 Phila, P.a. USA $0.50 $0.63 168033B 13 GA 301 2B 0.083 3.75 4 3518 Phila, P.a. USA $0.65 $0.81 168033C 13 GA 301 2B 0.083 5.25 2 2442 Phila, P.a. USA $0.65 $0.81 168033A 13 GA 301 2B 0.083 5.25 2 2419 Phila, P.a. USA $0.65 $0.81 243738 13 GA 304 2B 0.083 2.187 3 4028 Phila, P.a. USA $0.53 $0.66 215992A 12 GA 304 2B 0.105 2.75 1 1190 Phila, P.a. USA $0.50 $0.63 43257 12 GA 304 POL 0.105 6.437 2 3092 Phila, P.a. USA $0.44 $0.55 243494 12 GA 304 2B 0.105 20.9 1 8050 Phila, P.a. USA $0.48 $0.59 41325 11 GA 304 2B 0.120 3 1 1772 Phila, P.a. USA $0.63 $0.78 41326 11 GA 304 2B 0.120 3 1 1772 Phila, P.a. USA $0.63 $0.78 41327 11 GA 304 2B 0.120 3 1 1752 Phila, P.a. USA $0.63 $0.78 41328 11 GA 304 2B 0.120 3 1 1761 Phila, P.a. USA $0.63 $0.78 215992 11 GA 304 2B 0.120 3.125 1 1150 Phila, P.a. USA $0.50 $0.63 47400D 11 GA 304 POL 0.120 8.22 1 4630 Phila, P.a. USA $0.84 $1.05 38870 11 GA 316 #1 0.120 3.625 2 5454 Phila, P.a. USA $0.60 $0.75 49098 11 GA 430 BA 0.120 7.781 1 1828 Phila, P.a. USA $0.31 $0.39 46217I 11 GA 5052 H32 0.120 1.5 2 500 Phila, P.a. USA $1.10 $1.38 45031 11 GA 304 HRAP 0.123 1 2 927 Phila, P.a. USA $0.60 $0.75 47400A 11 GA 304 POL 0.125 2.625 2 1272 Phila, P.a. USA $0.84 $1.05 47400C 11 GA 304 POL 0.125 2.625 4 2538 Phila, P.a. USA $0.84 $1.05 42144 10 GA 316L #1 0.130 8 1 3726 Phila, P.a. USA $0.78 $0.97 45027 3/16" 304L HRAP 0.196 3 1 1745 Phila, P.a. USA $0.60 $0.75 44814A 1/4" 316L #1 0.250 1 1 286 Phila, P.a. USA $0.83 $1.03 44814C 1/4" 316L #1 0.250 1 1 344 Phila, P.a. USA $0.83 $1.03 44814F 1/4" 316L #1 0.250 1.5 2 1690 Phila, P.a. USA $0.83 $1.03 71103F 1/4" 316L #1 0.250 2 1 1620 Phila, P.a. USA $0.56 $0.70 44814B 1/4" 316L #1 0.250 2 5 6140 Phila, P.a. USA $0.83 $1.03 44814D 1/4" 316L #1 0.250 2 5 5635 Phila, P.a. USA $0.83 $1.03 44814E 1/4" 316L #1 0.250 2 4 4530 Phila, P.a. USA $0.83 $1.03 44814G 1/4" 316L #1 0.250 2 2 952 Phila, P.a. USA $0.83 $1.03 44814H 1/4" 316L #1 0.250 4 3 7385 Phila, P.a. USA $0.83 $1.03 www.BuyStainlessOnline.com Your Place for Stainless Today. P 215.604.5922 F 240.358.8483 Click Here to REGISTER! https://www.buystainlessonline.com/registration/registration.php Unsubscribe By clicking below: http://www.buystainlessonline.com/email/mail.php?action=delete&eval=50858&email=nat@ietf.org _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From daemon@optimus.ietf.org Wed Jan 16 13:29:51 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 MAA15321 for ; Wed, 16 Jan 2002 12:41:05 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id MAA11939 for nat-archive@odin.ietf.org; Wed, 16 Jan 2002 12:41:09 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA10959; Wed, 16 Jan 2002 12:26:46 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA10933 for ; Wed, 16 Jan 2002 12:26:44 -0500 (EST) Received: from linuxpow.com (IDENT:qmailr@linuxpow.com [12.149.2.10]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA14897 for ; Wed, 16 Jan 2002 12:26:37 -0500 (EST) Date: Wed, 16 Jan 2002 12:26:37 -0500 (EST) Message-Id: <200201161726.MAA14897@ietf.org> Received: (qmail 5343 invoked from network); 16 Jan 2002 16:34:55 -0000 Received: from buystainlessonline.com (HELO ) (nobody@12.149.2.55) by mail.buystainlessonline.com with SMTP; 16 Jan 2002 16:34:55 -0000 To: nat@ietf.org From: "BuyStainlessOnline.com" Subject: [NAT] The Stainless Steel Network MEGA DEAL 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 Unsubscribe by clicking the link at the bottom of this E-mail! It's quick and painless. The Stainless Steel Network is brought to you by www.buystainlessonline.com What BuyStainlessOnline users are doing... ---------------------------------------------------------------------- RECENT INQUIRIES: 904L Round Bar 168' 10mm 60'16mm 49' 25mm NO QUOTE YET 321 Stainless Plate 1/2 x 60 x 96 (7) pcs QUOTED 440C material, .500" dia x 144" long (840) pcs QUOTED 310 16ga 48 x 120 20 sheets QUOTED ------------------------------------------------------------------------ New Items for Sale OFFER #1 (looking for Best Offer) Commodity - Stainless Steel Wire. Grade - AISI 304L. Size - 0.135" Surface finish - Matte (Medium Bright) Condition - Soft Annealed. U.T.S. - 85,000 to 100,000 psi max. Quantity - aprox. 40,000 lbs. Packing - Coils wrapped in HDPE and loaded on Mild Steel Carriers. Remarks : All material is ex-mill in original mill's packaging. OFFER #2 Attention Distributors!!! 3,000,000 Pounds of PRIME 304 COILS for sale The following list of Stainless Steel Hot Rolled Coils is available FOB Ohio for the following PRICES: $.50 per pound (1 LOAD min) $.47 per pound (10 LOAD min) NOTE, these coils are MILL PRIME... Chemical Properties are listed below ------------------------------------------------------------------------ STEEL FIN WIDTH (mm) THICK (mm) Weigth (Pounds) C Cr Cu Mn Mo N Ni P S Si 304 1 950.0 3.00 37,238 0.0450 18.070 0.330 1.470 0.230 0.055 8.090 0.027 0.001 0.350 304 1 946.0 3.00 31,698 0.0470 18.070 0.280 1.320 0.250 0.042 8.040 0.030 0.001 0.360 304 1 1256.0 3.00 49,310 0.0440 18.110 0.240 1.340 0.240 0.042 8.050 0.030 0.001 0.370 304 1 1255.0 3.00 44,451 0.0500 18.290 0.240 1.370 0.250 0.046 8.030 0.031 0.001 0.420 304 1 1254.0 3.00 44,572 0.0500 18.290 0.240 1.370 0.250 0.046 8.030 0.031 0.001 0.420 304 1 1254.0 3.00 46,113 0.0500 18.060 0.320 1.350 0.350 0.042 8.070 0.030 0.001 0.420 304 1 799.5 3.00 31,239 0.0432 18.110 0.250 1.350 0.270 0.042 8.100 0.029 0.001 0.340 304 1 794.0 3.00 30,328 0.0410 18.220 0.280 1.420 0.300 0.047 8.120 0.030 0.001 0.350 304 1 1256.5 3.00 49,583 0.0420 18.110 0.250 1.350 0.270 0.045 8.100 0.029 0.001 0.340 304 1 1254.5 3.00 49,453 0.0420 18.110 0.250 1.350 0.270 0.045 8.100 0.029 0.001 0.340 304 1 1255.0 3.00 48,305 0.0450 18.020 0.320 1.390 0.310 0.046 8.000 0.028 0.001 0.360 304 1 1252.5 6.00 49,449 0.0420 18.030 0.330 1.360 0.240 0.050 8.070 0.025 0.001 0.390 304 1 1251.5 6.00 49,427 0.0410 18.020 0.300 1.350 0.260 0.045 8.090 0.028 0.001 0.380 304 1 1250.5 6.00 49,414 0.0410 18.020 0.300 1.350 0.260 0.045 8.090 0.028 0.001 0.380 304 1 1253.5 6.00 49,414 0.0450 18.080 0.300 1.320 0.250 0.050 8.100 0.031 0.001 0.350 304 1 1255.5 3.00 41,821 0.0430 18.070 0.340 1.390 0.270 0.051 8.100 0.026 0.001 0.480 304 1 1255.5 2.80 49,623 0.0430 18.070 0.340 1.390 0.270 0.051 8.100 0.026 0.001 0.480 304 1 1254.5 2.80 49,438 0.0420 18.090 0.330 1.400 0.330 0.043 8.150 0.026 0.001 0.360 304 1 1254.0 2.80 49,436 0.0420 18.030 0.330 1.360 0.240 0.050 8.070 0.025 0.001 0.390 304 1 1251.0 2.80 48,435 0.0410 18.060 0.270 1.330 0.250 0.051 8.150 0.026 0.001 0.340 304 1 1256.0 2.80 49,387 0.0410 18.060 0.270 1.330 0.250 0.051 8.150 0.026 0.001 0.340 304 1 1254.5 2.80 49,493 0.0410 18.060 0.270 1.330 0.250 0.051 8.150 0.026 0.001 0.340 304 1 1253.5 2.80 48,457 0.0410 18.060 0.270 1.330 0.250 0.051 8.150 0.026 0.001 0.340 304 1 1221.5 6.00 49,074 0.0430 18.060 0.410 1.350 0.240 0.049 8.070 0.027 0.001 0.470 304 1 1254.5 6.00 49,334 0.0430 18.060 0.410 1.350 0.240 0.049 8.070 0.027 0.001 0.470 304 1 1251.0 6.00 48,155 0.0400 18.040 0.320 1.410 0.200 0.050 8.060 0.029 0.001 0.360 34A 1 947.0 4.70 37,310 0.0390 18.130 0.260 1.340 0.190 0.047 8.550 0.027 0.001 0.370 304 1 951.5 3.00 36,565 0.0450 18.050 0.340 1.500 0.270 0.049 8.080 0.031 0.001 0.440 304 1 950.0 3.00 37,200 0.0450 18.050 0.340 1.500 0.270 0.049 8.080 0.031 0.001 0.440 304 1 951.0 3.00 37,299 0.0450 18.050 0.340 1.500 0.270 0.049 8.080 0.031 0.001 0.440 304 1 949.5 3.00 37,337 0.0450 18.050 0.340 1.500 0.270 0.049 8.080 0.031 0.001 0.440 304 1 948.5 3.00 37,260 0.0450 18.050 0.340 1.500 0.270 0.049 8.080 0.031 0.001 0.440 304 1 1252.0 6.00 43,333 0.0450 18.080 0.300 1.320 0.250 0.050 8.100 0.031 0.001 0.350 304 1 1251.5 6.00 49,561 0.0450 18.080 0.300 1.320 0.250 0.050 8.100 0.031 0.001 0.350 304 1 946.5 3.00 37,211 0.0450 18.070 0.330 1.470 0.230 0.055 8.090 0.027 0.001 0.350 304 1 947.5 3.00 37,277 0.0450 18.070 0.330 1.470 0.230 0.055 8.090 0.027 0.001 0.350 304 1 951.5 3.00 37,134 0.0450 18.070 0.330 1.470 0.230 0.055 8.090 0.027 0.001 0.350 304 1 949.0 3.00 36,490 0.0450 18.070 0.330 1.470 0.230 0.055 8.090 0.027 0.001 0.350 304 1 1255.0 3.00 48,450 0.0460 18.030 0.240 1.370 0.210 0.042 8.030 0.029 0.001 0.360 304 1 1256.0 3.00 48,338 0.0460 18.030 0.240 1.370 0.210 0.042 8.030 0.029 0.001 0.360 304 1 1254.5 3.00 49,195 0.0460 18.030 0.240 1.370 0.210 0.042 8.030 0.029 0.001 0.360 304 1 1255.5 3.00 49,449 0.0460 18.030 0.240 1.370 0.210 0.042 8.030 0.029 0.001 0.360 304 1 1256.5 3.00 48,638 0.0450 18.090 0.250 1.360 0.250 0.049 8.070 0.028 0.001 0.370 304 1 1255.5 3.00 47,672 0.0450 18.090 0.250 1.360 0.250 0.049 8.070 0.028 0.001 0.370 304 1 1255.5 3.00 49,482 0.0450 18.090 0.250 1.360 0.250 0.049 8.070 0.028 0.001 0.370 304 1 1254.5 3.00 49,493 0.0450 18.090 0.250 1.360 0.250 0.049 8.070 0.028 0.001 0.370 304 1 1239.0 3.00 49,151 0.0450 18.090 0.250 1.360 0.250 0.049 8.070 0.028 0.001 0.370 304 1 1255.0 6.00 49,475 0.0490 18.030 0.260 1.320 0.280 0.046 8.010 0.031 0.001 0.350 304 1 1254.5 6.00 49,286 0.0490 18.030 0.260 1.320 0.280 0.046 8.010 0.031 0.001 0.350 304 1 1251.5 6.00 48,415 0.0430 18.030 0.250 1.340 0.270 0.050 8.090 0.030 0.001 0.350 304 1 1251.0 6.00 47,824 0.0430 18.030 0.250 1.340 0.270 0.050 8.090 0.030 0.001 0.350 304 1 1252.5 6.00 48,364 0.0430 18.030 0.250 1.340 0.270 0.050 8.090 0.030 0.001 0.350 34A 1 795.0 3.00 28,968 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 34A 1 798.0 3.00 31,367 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 34A 1 797.0 3.00 31,389 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 34A 1 796.5 3.00 31,338 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 34A 1 798.5 3.00 31,550 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 34A 1 797.5 3.00 31,473 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 34A 1 800.0 3.00 30,613 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 34A 1 798.0 3.00 30,988 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 34A 1 796.0 3.00 31,354 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 34A 1 798.0 3.00 29,374 0.0400 18.010 0.270 1.370 0.200 0.048 8.550 0.028 0.001 0.300 304 1 1255.0 3.00 41,960 0.0490 18.030 0.260 1.320 0.280 0.046 8.010 0.031 0.001 0.350 304 1 1253.5 3.00 41,675 0.0490 18.030 0.260 1.320 0.280 0.046 8.010 0.031 0.001 0.350 304 1 1257.0 3.00 43,397 0.0420 18.060 0.300 1.380 0.340 0.048 8.040 0.028 0.001 0.350 304 1 1258.0 3.00 49,409 0.0410 18.030 0.270 1.340 0.250 0.050 8.040 0.027 0.001 0.290 304 1 1253.0 3.00 49,433 0.0410 18.030 0.270 1.340 0.250 0.050 8.040 0.027 0.001 0.290 304 1 1253.0 3.00 49,563 0.0400 18.080 0.270 1.390 0.270 0.050 8.070 0.028 0.001 0.350 304 1 1253.0 3.00 49,497 0.0400 18.080 0.270 1.390 0.270 0.050 8.070 0.028 0.001 0.350 304 1 1256.0 3.00 49,548 0.0400 18.080 0.270 1.390 0.270 0.050 8.070 0.028 0.001 0.350 304 1 1254.5 3.00 48,616 0.0400 18.080 0.270 1.390 0.270 0.050 8.070 0.028 0.001 0.350 304 1 1258.0 3.00 48,580 0.0400 18.080 0.270 1.390 0.270 0.050 8.070 0.028 0.001 0.350 304 1 1254.0 3.00 49,460 0.0420 18.060 0.300 1.380 0.340 0.048 8.040 0.028 0.001 0.350 304 1 1254.0 3.00 48,472 0.0430 18.200 0.260 1.360 0.260 0.043 8.070 0.028 0.001 0.380 34A 1 800.5 3.00 31,534 0.0410 18.030 0.330 1.340 0.250 0.050 8.530 0.029 0.001 0.360 34A 1 798.0 3.00 31,495 0.0410 18.030 0.330 1.340 0.250 0.050 8.530 0.029 0.001 0.360 34A 1 799.0 3.00 31,499 0.0410 18.030 0.330 1.340 0.250 0.050 8.530 0.029 0.001 0.360 34A 1 797.5 3.00 31,561 0.0410 18.030 0.330 1.340 0.250 0.050 8.530 0.029 0.001 0.360 3,343,970 OFFER #3 Stainless Steel SLIT COIL REMNANTS FOB PHILADELPHIA, PRICES LISTED BELOW, NO MINIMUM PURCHASE. This information is provided by BuyStainlessOnline, Inc. www.buystainlessonline.com Please email Sales@buystainlessonline.com or call 215.604.5922 to place orders. All materials are subject to prior sale. Tag Description Finish Thickness Width Quantity Weight Location Sale Price Regular Price 45146 28 GA 304 2B 0.015 18 1 5031 Phila, P.a. USA $1.10 $1.38 30794 26 GA 201 2D 0.020 21.5 1 4158 Phila, P.a. USA $0.88 $1.09 26202 26 GA 301 2B 0.020 1.375 1 418 Phila, P.a. USA $0.63 $0.78 232512E 26 GA 304 2B 0.020 1.5 3 386 Phila, P.a. USA $0.64 $0.80 45062 26 GA 304 POL/VC 0.020 11.75 1 2393 Phila, P.a. USA $0.63 $0.78 229878 26 GA 430 2B 0.020 3.5 2 936 Phila, P.a. USA $0.19 $0.23 22840 26 GA 430 BA 0.020 4.5 1 906 Phila, P.a. USA $0.25 $0.31 29364 24 GA 301 POL 0.024 4 1 1427 Phila, P.a. USA $0.65 $0.81 29363 24 GA 301 POL 0.024 4 1 1430 Phila, P.a. USA $0.65 $0.81 35176 24 GA 301 POL 0.024 6 2 4727 Phila, P.a. USA $0.53 $0.66 29362A 24 GA 304 POL 0.024 1.187 4 1024 Phila, P.a. USA $0.85 $1.06 186896 24 GA 304 2B 0.024 2.75 9 2790 Phila, P.a. USA $0.75 $0.94 19023 24 GA 304 2B 0.024 3.75 2 2762 Phila, P.a. USA $0.71 $0.89 61931 24 GA 304 2B 0.024 9 1 1122 Phila, P.a. USA $0.59 $0.73 29584 22 GA 301 POL 0.028 3.5 1 680 Phila, P.a. USA $0.66 $0.83 32794 22 GA 301 2B 0.028 6.75 1 1578 Phila, P.a. USA $0.54 $0.67 84108C 22 GA 304 POL 0.028 1.125 2 444 Phila, P.a. USA $0.90 $1.13 29362B 22 GA 304 POL 0.028 1.187 6 1229 Phila, P.a. USA $0.85 $1.06 32948 22 GA 304 POL 0.028 3.75 2 2858 Phila, P.a. USA $0.53 $0.66 44796 22 GA 304 POL 0.028 11.25 1 2159 Phila, P.a. USA $0.69 $0.86 224335 22 GA 430 POL 0.028 5.5 1 970 Phila, P.a. USA $0.06 $0.08 45099 22 GA 430 BA 0.028 10 1 2175 Phila, P.a. USA $0.34 $0.42 45098 22 GA 430 BA 0.028 10 1 2376 Phila, P.a. USA $0.34 $0.42 243739 20 GA 304 2D 0.035 1.5 3 1194 Phila, P.a. USA $0.88 $1.09 32943 20 GA 304 POL 0.035 3.125 3 2218 Phila, P.a. USA $0.78 $0.97 46336C 20 GA 304 POL 0.035 3.5 1 1013 Phila, P.a. USA $0.99 $1.23 48418E 20 GA 304 POL 0.035 4.125 1 877 Phila, P.a. USA $0.88 $1.09 49488 20 GA 304 2B 0.036 6.1 1 948 Phila, P.a. USA $0.71 $0.89 232335D 18 GA 304 POL 0.048 1.75 4 1111 Phila, P.a. USA $0.68 $0.84 27329 18 GA 304 AF 0.048 1.875 1 260 Phila, P.a. USA $0.44 $0.55 32953 18 GA 304 POL 0.048 2.5 1 513 Phila, P.a. USA $0.53 $0.66 186895 18 GA 304 AF 0.048 3.5 1 610 Phila, P.a. USA $0.75 $0.94 43255 18 GA 304 POL 0.048 5.25 4 5076 Phila, P.a. USA $0.44 $0.55 212565 18 GA 409 2B 0.048 3.75 1 1143 Phila, P.a. USA $0.09 $0.11 191101C 16 GA 304 POL 0.058 1 2 386 Phila, P.a. USA $0.98 $1.22 191101B 16 GA 304 POL 0.058 2 3 1490 Phila, P.a. USA $0.98 $1.22 44820 16 GA 304 BA 0.058 10 1 7504 Phila, P.a. USA $0.69 $0.86 33017 16 GA 430 2B 0.058 4 1 1249 Phila, P.a. USA $0.25 $0.31 43259 14 GA 304 POL 0.075 2.625 2 2684 Phila, P.a. USA $0.44 $0.55 43258 14 GA 304 POL 0.075 4.5 2 1750 Phila, P.a. USA $0.44 $0.55 43260 14 GA 304 POL 0.075 4.75 2 1977 Phila, P.a. USA $0.44 $0.55 27327 14 GA 409 AF 0.075 4.562 1 550 Phila, P.a. USA $0.31 $0.39 27328 14 GA 409 AF 0.075 4.687 1 531 Phila, P.a. USA $0.31 $0.39 35360 MISC GA 3003 H14 0.075 1 4 319 Phila, P.a. USA $0.50 $0.63 168033B 13 GA 301 2B 0.083 3.75 4 3518 Phila, P.a. USA $0.65 $0.81 168033C 13 GA 301 2B 0.083 5.25 2 2442 Phila, P.a. USA $0.65 $0.81 168033A 13 GA 301 2B 0.083 5.25 2 2419 Phila, P.a. USA $0.65 $0.81 243738 13 GA 304 2B 0.083 2.187 3 4028 Phila, P.a. USA $0.53 $0.66 215992A 12 GA 304 2B 0.105 2.75 1 1190 Phila, P.a. USA $0.50 $0.63 43257 12 GA 304 POL 0.105 6.437 2 3092 Phila, P.a. USA $0.44 $0.55 243494 12 GA 304 2B 0.105 20.9 1 8050 Phila, P.a. USA $0.48 $0.59 41325 11 GA 304 2B 0.120 3 1 1772 Phila, P.a. USA $0.63 $0.78 41326 11 GA 304 2B 0.120 3 1 1772 Phila, P.a. USA $0.63 $0.78 41327 11 GA 304 2B 0.120 3 1 1752 Phila, P.a. USA $0.63 $0.78 41328 11 GA 304 2B 0.120 3 1 1761 Phila, P.a. USA $0.63 $0.78 215992 11 GA 304 2B 0.120 3.125 1 1150 Phila, P.a. USA $0.50 $0.63 47400D 11 GA 304 POL 0.120 8.22 1 4630 Phila, P.a. USA $0.84 $1.05 38870 11 GA 316 #1 0.120 3.625 2 5454 Phila, P.a. USA $0.60 $0.75 49098 11 GA 430 BA 0.120 7.781 1 1828 Phila, P.a. USA $0.31 $0.39 46217I 11 GA 5052 H32 0.120 1.5 2 500 Phila, P.a. USA $1.10 $1.38 45031 11 GA 304 HRAP 0.123 1 2 927 Phila, P.a. USA $0.60 $0.75 47400A 11 GA 304 POL 0.125 2.625 2 1272 Phila, P.a. USA $0.84 $1.05 47400C 11 GA 304 POL 0.125 2.625 4 2538 Phila, P.a. USA $0.84 $1.05 42144 10 GA 316L #1 0.130 8 1 3726 Phila, P.a. USA $0.78 $0.97 45027 3/16" 304L HRAP 0.196 3 1 1745 Phila, P.a. USA $0.60 $0.75 44814A 1/4" 316L #1 0.250 1 1 286 Phila, P.a. USA $0.83 $1.03 44814C 1/4" 316L #1 0.250 1 1 344 Phila, P.a. USA $0.83 $1.03 44814F 1/4" 316L #1 0.250 1.5 2 1690 Phila, P.a. USA $0.83 $1.03 71103F 1/4" 316L #1 0.250 2 1 1620 Phila, P.a. USA $0.56 $0.70 44814B 1/4" 316L #1 0.250 2 5 6140 Phila, P.a. USA $0.83 $1.03 44814D 1/4" 316L #1 0.250 2 5 5635 Phila, P.a. USA $0.83 $1.03 44814E 1/4" 316L #1 0.250 2 4 4530 Phila, P.a. USA $0.83 $1.03 44814G 1/4" 316L #1 0.250 2 2 952 Phila, P.a. USA $0.83 $1.03 44814H 1/4" 316L #1 0.250 4 3 7385 Phila, P.a. USA $0.83 $1.03 www.BuyStainlessOnline.com Your Place for Stainless Today. P 215.604.5922 F 240.358.8483 Click Here to REGISTER! https://www.buystainlessonline.com/registration/registration.php Unsubscribe By clicking below: http://www.buystainlessonline.com/email/mail.php?action=delete&eval=50858&email=nat@ietf.org _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From nat-admin@ietf.org Fri Jan 18 10:42:32 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 KAA15115; Fri, 18 Jan 2002 10:42:32 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA18033; Fri, 18 Jan 2002 10:32:50 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA18011 for ; Fri, 18 Jan 2002 10:32:48 -0500 (EST) Received: from smtp.263.net ([202.96.44.20]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14683 for ; Fri, 18 Jan 2002 10:32:40 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by smtp.263.net (Postfix) with SMTP id DB4491DF4504A for ; Fri, 18 Jan 2002 23:31:41 +0800 (CST) Message-ID: <000801c1a035$5074b060$5a9370ca@mlrhjf> Reply-To: "maliran" From: "maliran" To: Date: Fri, 18 Jan 2002 23:32:18 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C1A078.5E796BE0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Subject: [NAT] please add me in 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 This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C1A078.5E796BE0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 DQo= ------=_NextPart_000_0005_01C1A078.5E796BE0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w MC4yOTIwLjAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9E WSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPiZuYnNwOzwvRElWPjwvQk9EWT48L0hUTUw+DQo= ------=_NextPart_000_0005_01C1A078.5E796BE0-- _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From daemon@optimus.ietf.org Fri Jan 18 11:45:10 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 KAA15121 for ; Fri, 18 Jan 2002 10:42:32 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id KAA18604 for nat-archive@odin.ietf.org; Fri, 18 Jan 2002 10:42:35 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA18033; Fri, 18 Jan 2002 10:32:50 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA18011 for ; Fri, 18 Jan 2002 10:32:48 -0500 (EST) Received: from smtp.263.net ([202.96.44.20]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14683 for ; Fri, 18 Jan 2002 10:32:40 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by smtp.263.net (Postfix) with SMTP id DB4491DF4504A for ; Fri, 18 Jan 2002 23:31:41 +0800 (CST) Message-ID: <000801c1a035$5074b060$5a9370ca@mlrhjf> Reply-To: "maliran" From: "maliran" To: Date: Fri, 18 Jan 2002 23:32:18 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C1A078.5E796BE0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Subject: [NAT] please add me in 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 This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C1A078.5E796BE0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 DQo= ------=_NextPart_000_0005_01C1A078.5E796BE0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w MC4yOTIwLjAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9E WSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPiZuYnNwOzwvRElWPjwvQk9EWT48L0hUTUw+DQo= ------=_NextPart_000_0005_01C1A078.5E796BE0-- _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From nat-admin@ietf.org Mon Jan 21 17:06:54 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 RAA26536; Mon, 21 Jan 2002 17:06:54 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA28340; Mon, 21 Jan 2002 16:49:38 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA28317 for ; Mon, 21 Jan 2002 16:49:36 -0500 (EST) Received: from localhost ([218.55.130.32]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA25952 for ; Mon, 21 Jan 2002 16:49:16 -0500 (EST) Message-Id: <200201212149.QAA25952@ietf.org> Reply-To: naracom2002@naver.com From: 친구에게 To: nat@ietf.org Mime-Version: 1.0 Content-Type: text/html; charset="ks_c_5601-1987" Date: Tue, 22 Jan 2002 07:04:50 +0900 Subject: [NAT] 안녕하세요[홍보] 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 선불요금제 참조자료집

안녕하세요 저호준이에요
잘지내고 계시져?
좋은정보가 이렇게 멜보내 드려요
한번 꼼꼼히 따져보세요 아마 많은도움될거에요
아래에 파일첨부했으니 읽어보시고요
그럼 또 멜드릴께요








선불요금제서비스는 어느날 갑자기 나온 서비스가 아닌, 선진 여러나라에서는 이미 기존에 실시하고는 서비스로 회사의 입장에서는 안정적이며 미납 걱정이 없는 회원유치를 하여 회사의 안정성을 꾀할 수 있으며, 이에따른 고객은 각종 혜택 및 수당을 받는 것입니다.
즉 선불제요금제란 먼저 일정부분의 통신료를 내고 캐쉬백(현금)과 기타 수당을 받는 요금체계이며, 이로인한 혜택을 고객에게 크게는 35%에 해당되는 부분을 다시 현금으로 돌려드리고 있습니다.
 

1. 악성연체 요금으로 인한 금융 신용불량자의 증가.
2. 인적, 물적으로 많은 관리비용 필요 (요금고지, 채권관리 등).
3. 이동통신 사용자가 사용요금의 인지없이 무분별한 사용으로 인한 과소비 초래.

이러한, 문제로 인해 세계적으로 이동통신은 선불요금제로 전환되고 있습니다.
※ 2002년에는 IMT2000 서비스가 시작되며, 그때는 지금 사용요금의 3~4배에 이르는 서비스 요금이 사용될 것이라고 예측하고 있습니다. 통신시장이 개방되었음에도 불구하고, 외국의 거대통신기업들이 지금 잠잠한것은 바로 이 IMT2000 시대을 기다리며, 우리나라 통신시장을 넘보고 있는 것입니다.

: 개인대리점으로 구성
고정된 지역 대리점을 탈피하여 지역에 상관없이 움직이는 대리점으로 구성
　

일반대리점

KTF 선불대리점

범        위

지역별 한계 지역 제한없이 전국
시        설 매장 임대 (보증금 + 시설비 등) 매장 불필요
담        보 단말기 구매를 위해 담보물 제공 담보 없음
관 리 유 지 관리 인원 및 관리비 과다 지출 없음
수   수   료 관리수수료 회원장려금
시   장   성 시장성이 없다. (포화상태) 무한한 시장성 (초기시장 선점)
해   지   율 고객 이동이 많다.

(대리점간 공용시스템)		 고객이동 없음.

(전용시스템)
     

 ▶ 사용이 불편하다 : 접속번호와  카드번호를 입력한 후 사용하여야 통화가 연결됩니다.
 ▶ 시외전화 : 기업, 회사에서 많이 사용 (약 2조원)  개인은 1가구당 약 4,600원 사용
 ▶ 국제전화 : 기업, 무역회사, 오파상등이 많이 사용 (약1조원) 개인 사용은 미비하다.

     
   ▶ 사용이 편리하다. : 후불 전화 사용과 동일
 ▶ 2,750만명이 넘는 대부분의 고객이 개인으로 구성되어 있습니다.
 ▶ 선불시장은 무한합니다. : 2750만 후불요금 사용고객
 ▶ 1가구당 11만원 이상 사용합니다. (1999년 통계)
요금상품 일 기본료 월 기본료 국내통화료 
(원/10초)		 비 고
평상 할인 심야
선불 표준 533 원 16,000 원 18 원 15 원 10 원 　
선불 에이스 616 원 18,500 원 15 원 14 원 13 원 　
선불프리 200 1,183 원 35,500 원 17 원 14 원 10 원 200분 무료

  ▶ 요금상품 변경시 적용시점 : 변경과 동시에 변경요금으로 정산되나, 월 1회에 한함.
  ▶ 할 인 시 간
    1) 선불표준, 선불에이스 요금의 경우
       - 평일 (토요일 포함) : 0 ~ 6 시 (심야) / 6 ~ 12 (할인) / 12 ~ 24 (평상)     
       - 공휴일 (일요일 포함) : 0 ~ 6시 (심야) / 6 ~ 24 (할인)
     2) 선불프리 200 요금의 경우
       - 평일 (토요일 포함) : 0 ~ 6 시 (심야) / 6 ~ 8, 21 ~ 24 (할인) / 8 ~ 21 (평상)
       - 공휴일 (일요일 포함) : 0 ~ 6시 (심야) / 6 ~ 24 (할인)


 KTF(한국통신프리텔)의 탄생 당시부터 모든 시스템을 담당해 온  대우정보시스템은 
 기존 전자상거래의 기반부재로 오는 적자요인을 주식회사 나라콤의 네트워크 마케팅을  
 통하여 최단기간 최대회원의 기반확보를 목표로  KTF, 대우정보시스템, 주식회사
 나라콤의 전략적 제휴를 통하여 
 선진국형 선불요금제도
- KTF 016 선불요금제도 -
를  탄생시켰습니다.

E-mail : corud2@dreamwiz.com
  
귀하의 E-MAIL은 관련 게시판을 통해 알게 되었습니다.
원치 않았던 메일이라면 여기를 눌러 알려 주시면 앞으로는 발송되지 않도록 하겠습니다.

_______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From daemon@ns.ietf.org Mon Jan 21 17:06:59 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 RAA26541 for ; Mon, 21 Jan 2002 17:06:55 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id RAA29377 for nat-archive@odin.ietf.org; Mon, 21 Jan 2002 17:06:57 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA28340; Mon, 21 Jan 2002 16:49:38 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA28317 for ; Mon, 21 Jan 2002 16:49:36 -0500 (EST) Received: from localhost ([218.55.130.32]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA25952 for ; Mon, 21 Jan 2002 16:49:16 -0500 (EST) Message-Id: <200201212149.QAA25952@ietf.org> Reply-To: naracom2002@naver.com From: 친구에게 To: nat@ietf.org Mime-Version: 1.0 Content-Type: text/html; charset="ks_c_5601-1987" Date: Tue, 22 Jan 2002 07:04:50 +0900 Subject: [NAT] 안녕하세요[홍보] 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 선불요금제 참조자료집

안녕하세요 저호준이에요
잘지내고 계시져?
좋은정보가 이렇게 멜보내 드려요
한번 꼼꼼히 따져보세요 아마 많은도움될거에요
아래에 파일첨부했으니 읽어보시고요
그럼 또 멜드릴께요








선불요금제서비스는 어느날 갑자기 나온 서비스가 아닌, 선진 여러나라에서는 이미 기존에 실시하고는 서비스로 회사의 입장에서는 안정적이며 미납 걱정이 없는 회원유치를 하여 회사의 안정성을 꾀할 수 있으며, 이에따른 고객은 각종 혜택 및 수당을 받는 것입니다.
즉 선불제요금제란 먼저 일정부분의 통신료를 내고 캐쉬백(현금)과 기타 수당을 받는 요금체계이며, 이로인한 혜택을 고객에게 크게는 35%에 해당되는 부분을 다시 현금으로 돌려드리고 있습니다.
 

1. 악성연체 요금으로 인한 금융 신용불량자의 증가.
2. 인적, 물적으로 많은 관리비용 필요 (요금고지, 채권관리 등).
3. 이동통신 사용자가 사용요금의 인지없이 무분별한 사용으로 인한 과소비 초래.

이러한, 문제로 인해 세계적으로 이동통신은 선불요금제로 전환되고 있습니다.
※ 2002년에는 IMT2000 서비스가 시작되며, 그때는 지금 사용요금의 3~4배에 이르는 서비스 요금이 사용될 것이라고 예측하고 있습니다. 통신시장이 개방되었음에도 불구하고, 외국의 거대통신기업들이 지금 잠잠한것은 바로 이 IMT2000 시대을 기다리며, 우리나라 통신시장을 넘보고 있는 것입니다.

: 개인대리점으로 구성
고정된 지역 대리점을 탈피하여 지역에 상관없이 움직이는 대리점으로 구성
　

일반대리점

KTF 선불대리점

범        위

지역별 한계 지역 제한없이 전국
시        설 매장 임대 (보증금 + 시설비 등) 매장 불필요
담        보 단말기 구매를 위해 담보물 제공 담보 없음
관 리 유 지 관리 인원 및 관리비 과다 지출 없음
수   수   료 관리수수료 회원장려금
시   장   성 시장성이 없다. (포화상태) 무한한 시장성 (초기시장 선점)
해   지   율 고객 이동이 많다.

(대리점간 공용시스템)		 고객이동 없음.

(전용시스템)
     

 ▶ 사용이 불편하다 : 접속번호와  카드번호를 입력한 후 사용하여야 통화가 연결됩니다.
 ▶ 시외전화 : 기업, 회사에서 많이 사용 (약 2조원)  개인은 1가구당 약 4,600원 사용
 ▶ 국제전화 : 기업, 무역회사, 오파상등이 많이 사용 (약1조원) 개인 사용은 미비하다.

     
   ▶ 사용이 편리하다. : 후불 전화 사용과 동일
 ▶ 2,750만명이 넘는 대부분의 고객이 개인으로 구성되어 있습니다.
 ▶ 선불시장은 무한합니다. : 2750만 후불요금 사용고객
 ▶ 1가구당 11만원 이상 사용합니다. (1999년 통계)
요금상품 일 기본료 월 기본료 국내통화료 
(원/10초)		 비 고
평상 할인 심야
선불 표준 533 원 16,000 원 18 원 15 원 10 원 　
선불 에이스 616 원 18,500 원 15 원 14 원 13 원 　
선불프리 200 1,183 원 35,500 원 17 원 14 원 10 원 200분 무료

  ▶ 요금상품 변경시 적용시점 : 변경과 동시에 변경요금으로 정산되나, 월 1회에 한함.
  ▶ 할 인 시 간
    1) 선불표준, 선불에이스 요금의 경우
       - 평일 (토요일 포함) : 0 ~ 6 시 (심야) / 6 ~ 12 (할인) / 12 ~ 24 (평상)     
       - 공휴일 (일요일 포함) : 0 ~ 6시 (심야) / 6 ~ 24 (할인)
     2) 선불프리 200 요금의 경우
       - 평일 (토요일 포함) : 0 ~ 6 시 (심야) / 6 ~ 8, 21 ~ 24 (할인) / 8 ~ 21 (평상)
       - 공휴일 (일요일 포함) : 0 ~ 6시 (심야) / 6 ~ 24 (할인)


 KTF(한국통신프리텔)의 탄생 당시부터 모든 시스템을 담당해 온  대우정보시스템은 
 기존 전자상거래의 기반부재로 오는 적자요인을 주식회사 나라콤의 네트워크 마케팅을  
 통하여 최단기간 최대회원의 기반확보를 목표로  KTF, 대우정보시스템, 주식회사
 나라콤의 전략적 제휴를 통하여 
 선진국형 선불요금제도
- KTF 016 선불요금제도 -
를  탄생시켰습니다.

E-mail : corud2@dreamwiz.com
  
귀하의 E-MAIL은 관련 게시판을 통해 알게 되었습니다.
원치 않았던 메일이라면 여기를 눌러 알려 주시면 앞으로는 발송되지 않도록 하겠습니다.

_______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From nat-admin@ietf.org Tue Jan 22 14:42: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 OAA07501; Tue, 22 Jan 2002 14:42:07 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA06212; Tue, 22 Jan 2002 14:21:23 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA06187 for ; Tue, 22 Jan 2002 14:21:21 -0500 (EST) Received: from NS1.US.PRSERV.NET ([64.180.246.83]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA06123 for ; Tue, 22 Jan 2002 14:21:17 -0500 (EST) From: sydney@vkistudios.org Message-Id: <200201221921.OAA06123@ietf.org> Reply-To: seo@vkistudios.org To: nat@ietf.org Mime-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Date: Tue, 22 Jan 2002 11:24:51 -0800 Subject: [NAT] ADV: Professional Internet Marketing 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 Professional Internet Marketing, VKI Studios 1-866-733-8899
1-866-733-8899 

 

_______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From daemon@ns.ietf.org Tue Jan 22 14:42:12 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 OAA07506 for ; Tue, 22 Jan 2002 14:42:07 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id OAA08188 for nat-archive@odin.ietf.org; Tue, 22 Jan 2002 14:42:10 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA06212; Tue, 22 Jan 2002 14:21:23 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA06187 for ; Tue, 22 Jan 2002 14:21:21 -0500 (EST) Received: from NS1.US.PRSERV.NET ([64.180.246.83]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA06123 for ; Tue, 22 Jan 2002 14:21:17 -0500 (EST) From: sydney@vkistudios.org Message-Id: <200201221921.OAA06123@ietf.org> Reply-To: seo@vkistudios.org To: nat@ietf.org Mime-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Date: Tue, 22 Jan 2002 11:24:51 -0800 Subject: [NAT] ADV: Professional Internet Marketing 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 Professional Internet Marketing, VKI Studios 1-866-733-8899
1-866-733-8899 

 

_______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From daemon@optimus.ietf.org Thu Jan 24 22:45:01 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 WAA15243 for ; Thu, 24 Jan 2002 22:45:01 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id WAA12132 for nat-archive@odin.ietf.org; Thu, 24 Jan 2002 22:45:05 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA11313; Thu, 24 Jan 2002 22:27:39 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA11287 for ; Thu, 24 Jan 2002 22:27:38 -0500 (EST) Received: from localhost ([211.117.232.146]) by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA13970 for ; Thu, 24 Jan 2002 22:27:32 -0500 (EST) Message-Id: <200201250327.WAA13970@ietf.org> Reply-To: office7000@yahoo.co.kr From: 창업정보 To: nat@ietf.org Mime-Version: 1.0 Content-Type: text/html; charset="ks_c_5601-1987" Date: Fri, 25 Jan 2002 12:28:15 +0900 Subject: [NAT] [광고] 돈 되는 사업정보입니다 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 귀하의 창업을 돕겠습니다.

 

 귀하의 창업을 돕겠습니다.  

 저희 (주)나래정보에서는 전화정보 창업자를 모십니다.

 본  사업소에서 보유한 아이템을 드릴수도 있습니다.

귀하께서 계획하신 아이템을 수익성 있는 사업으로 만들어 드리겠습니다.

수년간의 기술과 노하우로 최선을 다하며, 고객의 이익과 사업의 발전을 위해 노력하는 기업으로

귀하의 곁에 끝까지 남겠습니다.

전화정보(700, 060, 800, 0600)특징

  1. 특별한 자격을 요하지 않습니다.(사업자 등록증 필요)

  2. 수금의 필요성이 없습니다.(각 통신사 수금대행)

  3. 타 사업보다 운영과 관리가 편리합니다.(전화로 관리가능)

  4. 귀하만의 노하우로 정보를 제공합니다.(아이템제공)

  5. 사업성 타당여부 조사.(시장성 조사 대행)

  6. 창업자금지원.(창업자금의 50%지원, 수익금 창출후에 수금)

  7. 사업의 지속성.(시스템 본사 관리. 사업자는 기획과 광고)

  8. 사업의 안전성.(한국통신, 하나로통신, 데이콤등과 연계하여 사업영위)

  9. 본사의 지원.((주)나래에서 사업자등록신청, 시스템제작, 운영, 관리)

 10. 장비임대.(금3,100,000원으로 장비일체와 프로그램을 제공합니다.)

 

"광고메일대행"  링크해주세요  

가장 빠른 광고효과입니다. 빠른 시간안에 확실한 효과를 보실수 있습니다. 이보다  뛰어난 광고효과를 기대할 수 없습니다. 저희 회원에 한하여 후불로 결재 받습니다.
 
                    

 귀하의 메일주소는 웹서핑중, http://www.xxxxxxxx.com/
에서 알게 된것이며, E-Mail 주소 외에, 다른 정보는 갖고 있지 않습니다.
정통부 권고사항에 의거 제목에 [광고]라고 표기한 메일입니다. 원치 않으면 ,수신거부를 눌러주세요

           

 

_______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From nat-admin@ietf.org Thu Jan 24 23:46: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 WAA15238; Thu, 24 Jan 2002 22:45:01 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA11313; Thu, 24 Jan 2002 22:27:39 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA11287 for ; Thu, 24 Jan 2002 22:27:38 -0500 (EST) Received: from localhost ([211.117.232.146]) by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA13970 for ; Thu, 24 Jan 2002 22:27:32 -0500 (EST) Message-Id: <200201250327.WAA13970@ietf.org> Reply-To: office7000@yahoo.co.kr From: 창업정보 To: nat@ietf.org Mime-Version: 1.0 Content-Type: text/html; charset="ks_c_5601-1987" Date: Fri, 25 Jan 2002 12:28:15 +0900 Subject: [NAT] [광고] 돈 되는 사업정보입니다 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 귀하의 창업을 돕겠습니다.

 

 귀하의 창업을 돕겠습니다.  

 저희 (주)나래정보에서는 전화정보 창업자를 모십니다.

 본  사업소에서 보유한 아이템을 드릴수도 있습니다.

귀하께서 계획하신 아이템을 수익성 있는 사업으로 만들어 드리겠습니다.

수년간의 기술과 노하우로 최선을 다하며, 고객의 이익과 사업의 발전을 위해 노력하는 기업으로

귀하의 곁에 끝까지 남겠습니다.

전화정보(700, 060, 800, 0600)특징

  1. 특별한 자격을 요하지 않습니다.(사업자 등록증 필요)

  2. 수금의 필요성이 없습니다.(각 통신사 수금대행)

  3. 타 사업보다 운영과 관리가 편리합니다.(전화로 관리가능)

  4. 귀하만의 노하우로 정보를 제공합니다.(아이템제공)

  5. 사업성 타당여부 조사.(시장성 조사 대행)

  6. 창업자금지원.(창업자금의 50%지원, 수익금 창출후에 수금)

  7. 사업의 지속성.(시스템 본사 관리. 사업자는 기획과 광고)

  8. 사업의 안전성.(한국통신, 하나로통신, 데이콤등과 연계하여 사업영위)

  9. 본사의 지원.((주)나래에서 사업자등록신청, 시스템제작, 운영, 관리)

 10. 장비임대.(금3,100,000원으로 장비일체와 프로그램을 제공합니다.)

 

"광고메일대행"  링크해주세요  

가장 빠른 광고효과입니다. 빠른 시간안에 확실한 효과를 보실수 있습니다. 이보다  뛰어난 광고효과를 기대할 수 없습니다. 저희 회원에 한하여 후불로 결재 받습니다.
 
                    

 귀하의 메일주소는 웹서핑중, http://www.xxxxxxxx.com/
에서 알게 된것이며, E-Mail 주소 외에, 다른 정보는 갖고 있지 않습니다.
정통부 권고사항에 의거 제목에 [광고]라고 표기한 메일입니다. 원치 않으면 ,수신거부를 눌러주세요

           

 

_______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From daemon@optimus.ietf.org Sat Jan 26 23:57:25 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 XAA17062 for ; Sat, 26 Jan 2002 23:57:25 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id XAA18743 for nat-archive@odin.ietf.org; Sat, 26 Jan 2002 23:57:30 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA18450; Sat, 26 Jan 2002 23:49:06 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA18424 for ; Sat, 26 Jan 2002 23:49:05 -0500 (EST) Received: from smtprelay1.dc3.adelphia.net (smtprelay1.dc3.adelphia.net [24.50.78.4]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16974 for ; Sat, 26 Jan 2002 23:48:58 -0500 (EST) Message-Id: <200201270448.XAA16974@ietf.org> Received: from localhost ([24.51.245.164]) by smtprelay1.dc3.adelphia.net (Netscape Messaging Server 4.15) with ESMTP id GQKXXI00.I2V for ; Sat, 26 Jan 2002 23:32:06 -0500 X-Sender: requestedinfo@stayhomemakecash.com From: Requested Info To: nat@ietf.org Date: Sat, 26 Jan 2002 20:30:13 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Priority: 1 Content-Transfer-Encoding: 7bit Subject: [NAT] Work Smarter Not Harder 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 YOU ARE NEEDED! $300-$2000 PLUS WEEKLY (or more) Simple, pleasant work...you do at home...on the Internet!

Click Here

Dear Friend, Are you seeking a rewarding second income? Would you like to set your own work schedule? Work the hours you choose? Earn extra income for your family? If so, then I may have the answer. Current statistics show that by the year 2010, 40-60% of the American work-force will be working from home. Get a jump on your future and secure a job through us. My company provides a special work-at-home program that is used by thousands of people and businesses across the globe. This job requires no special skill or experience, just a sincere desire to GET STARTED, and EARN MONEY! In fact, your are your own BOSS!

Click Here

YOU CAN EARN GOOD MONEY!!! Potential incomes range from $300 to $2000 weekly or more, depending only on the amount of free time you have available. The effort you invest can make you a substantial income. You'll find this work, done easily and quickly, can double or even triple your income. With just one or two hours per day you will be excitedly surprised at how easy we've made it and how profitable this actually is. You can earn enough money working in your spare time to purchase that new car or boat you've been wanting, pay off credit cards, bills, or even take a vacation. Maybe just add more financial security for yourself or your family. Whatever the reason, you can't go wrong.

Click Here

ALL BUSINESS DONE ON THE INTERNET You can start the same day you receive our programs and instructions and begin receiving money within a matter of days. This position requires no prior experience or special skills and the program is specifically designed to get you up and running as fast as possible. And all work is done over the Internet! No "face-to-face" selling or anything remotely similar is ever needed. Not ever! Just "follow the numbers" and you will be amazed at how much you make! HELP SOLVE YOUR MONEY PROBLEMS There are only a limited number of these positions available and as soon as these are filled, I will cease to offer this program. Your help is needed now! So, if you're a productive, positive person, I am looking forward to hearing from you and seeing you benefit from our program. SIMPLE, EASY, AND PROFITABLE, THIS PROGRAM MAY BE THE BEST WAY TO MAKE AN EXCELLENT INCOME AT HOME. If this sounds like something you might be interested in, please:

Click Here

for very complete information. Thank You. Clark J. Coleman P.S.--Look below at what others are saying! I want to thank you for giving me this opportunity to work from my home. It couldn't have come along at a better time. The work is so simple and the pay is incredible. My wife and I have been working at home together part-time and are exceeding what either of us make at our full-time jobs. Thanks again! B. Roberts ------ Tampa, FL Thanks for everything! I was having trouble making ends meet at my present employment. But thanks to you and your Program, I was able to pay off some old bills and put money in the bank. Now I'm looking forward to taking a well deserved vacation. K. Williams ----- Seattle, WA This message is sent in compliance of the proposed bill SECTION 301. per Section 301, Paragraph (a)(2)(C) of S. 1618. Further transmission to you by the sender of this e-mail may be stopped at no cost to you by sending a reply to : "requestedinfo@stayhomemakecash.com" with the word Remove in the subject line. This message is not intended for residents in the States of Washington, California and Virginia. _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From nat-admin@ietf.org Sat Jan 26 23:57:25 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 XAA17054; Sat, 26 Jan 2002 23:57:20 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA18450; Sat, 26 Jan 2002 23:49:06 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA18424 for ; Sat, 26 Jan 2002 23:49:05 -0500 (EST) Received: from smtprelay1.dc3.adelphia.net (smtprelay1.dc3.adelphia.net [24.50.78.4]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16974 for ; Sat, 26 Jan 2002 23:48:58 -0500 (EST) Message-Id: <200201270448.XAA16974@ietf.org> Received: from localhost ([24.51.245.164]) by smtprelay1.dc3.adelphia.net (Netscape Messaging Server 4.15) with ESMTP id GQKXXI00.I2V for ; Sat, 26 Jan 2002 23:32:06 -0500 X-Sender: requestedinfo@stayhomemakecash.com From: Requested Info To: nat@ietf.org Date: Sat, 26 Jan 2002 20:30:13 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Priority: 1 Content-Transfer-Encoding: 7bit Subject: [NAT] Work Smarter Not Harder 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 YOU ARE NEEDED! $300-$2000 PLUS WEEKLY (or more) Simple, pleasant work...you do at home...on the Internet!

Click Here

Dear Friend, Are you seeking a rewarding second income? Would you like to set your own work schedule? Work the hours you choose? Earn extra income for your family? If so, then I may have the answer. Current statistics show that by the year 2010, 40-60% of the American work-force will be working from home. Get a jump on your future and secure a job through us. My company provides a special work-at-home program that is used by thousands of people and businesses across the globe. This job requires no special skill or experience, just a sincere desire to GET STARTED, and EARN MONEY! In fact, your are your own BOSS!

Click Here

YOU CAN EARN GOOD MONEY!!! Potential incomes range from $300 to $2000 weekly or more, depending only on the amount of free time you have available. The effort you invest can make you a substantial income. You'll find this work, done easily and quickly, can double or even triple your income. With just one or two hours per day you will be excitedly surprised at how easy we've made it and how profitable this actually is. You can earn enough money working in your spare time to purchase that new car or boat you've been wanting, pay off credit cards, bills, or even take a vacation. Maybe just add more financial security for yourself or your family. Whatever the reason, you can't go wrong.

Click Here

ALL BUSINESS DONE ON THE INTERNET You can start the same day you receive our programs and instructions and begin receiving money within a matter of days. This position requires no prior experience or special skills and the program is specifically designed to get you up and running as fast as possible. And all work is done over the Internet! No "face-to-face" selling or anything remotely similar is ever needed. Not ever! Just "follow the numbers" and you will be amazed at how much you make! HELP SOLVE YOUR MONEY PROBLEMS There are only a limited number of these positions available and as soon as these are filled, I will cease to offer this program. Your help is needed now! So, if you're a productive, positive person, I am looking forward to hearing from you and seeing you benefit from our program. SIMPLE, EASY, AND PROFITABLE, THIS PROGRAM MAY BE THE BEST WAY TO MAKE AN EXCELLENT INCOME AT HOME. If this sounds like something you might be interested in, please:

Click Here

for very complete information. Thank You. Clark J. Coleman P.S.--Look below at what others are saying! I want to thank you for giving me this opportunity to work from my home. It couldn't have come along at a better time. The work is so simple and the pay is incredible. My wife and I have been working at home together part-time and are exceeding what either of us make at our full-time jobs. Thanks again! B. Roberts ------ Tampa, FL Thanks for everything! I was having trouble making ends meet at my present employment. But thanks to you and your Program, I was able to pay off some old bills and put money in the bank. Now I'm looking forward to taking a well deserved vacation. K. Williams ----- Seattle, WA This message is sent in compliance of the proposed bill SECTION 301. per Section 301, Paragraph (a)(2)(C) of S. 1618. Further transmission to you by the sender of this e-mail may be stopped at no cost to you by sending a reply to : "requestedinfo@stayhomemakecash.com" with the word Remove in the subject line. This message is not intended for residents in the States of Washington, California and Virginia. _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From daemon@optimus.ietf.org Sun Jan 27 17:48:19 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 RAA04307 for ; Sun, 27 Jan 2002 17:48:19 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id RAA28804 for nat-archive@odin.ietf.org; Sun, 27 Jan 2002 17:48:21 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA28570; Sun, 27 Jan 2002 17:40:04 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA28547 for ; Sun, 27 Jan 2002 17:40:03 -0500 (EST) Date: Sun, 27 Jan 2002 17:40:03 -0500 (EST) Received: from erp_ps.n-phc.com ([211.233.63.33]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA04206 for ; Sun, 27 Jan 2002 17:39:59 -0500 (EST) Received: from cehc.com (unverified [64.86.192.77]) by erp_ps.n-phc.com (EMWAC SMTPRS 0.83) with SMTP id ; Mon, 28 Jan 2002 07:35:30 +0900 Message-ID: <6cc1b30$22ec$365e> Mime-Version: 1.0 X-Priority: 1 (Highest) X-MSMail-Priority: High Importance: High Content-Type: multipart/mixed; boundary="----=_NextPart_19693_2718_12FB.5C327801F40B" To: "nat@ietf.org" From: "" Reply-to: admin@webmasterdirect.org Subject: [NAT] Read this! You definitely need it 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 ------=_NextPart_19693_2718_12FB.5C327801F40B Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 8bit DVD Copy Utility

Copy & Burn DVD's & VHS's w/CD Burner!!!

 

    Why Spend upwards of $4000 on a DVD Burner when we will show you an alternative that will do the exact same thing for only $19.95?

    You heard us right - for the price of just 1 DVD's, we'll show you how to back up and/or create Your Own DVD's!

    Just upgraded to a DVD and still have a ton of VHS tapes lying around? With this program, not only can you burn & copy any DVD you've created, you'll also be able to transfer all your VHS tapes to DVD format as well!!

    Regular Price:

    For a Limited Time Only, get yours today for just ONLY $19.95!!

    ORDER NOW

                                    

You want to know more? Visit us at http://www.copydvd.net

Win $ 5000 NOW !!!
Forward this message to 5 of your friends (put our email: win@ewasher.org in the cc field along with your 5 friends email addresses) and you will be automatically entered in our drawing for $5000.

 


To be opt out from our future mailing please email optout@ewasher.org with the word remove in the subject line

 

To be removed from this mailing list please send an email to remove@ewasher.org with the word remove in the subject line

------=_NextPart_19693_2718_12FB.5C327801F40B-- _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From nat-admin@ietf.org Sun Jan 27 19:10:20 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 RAA04302; Sun, 27 Jan 2002 17:48:18 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA28570; Sun, 27 Jan 2002 17:40:04 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA28547 for ; Sun, 27 Jan 2002 17:40:03 -0500 (EST) Date: Sun, 27 Jan 2002 17:40:03 -0500 (EST) Received: from erp_ps.n-phc.com ([211.233.63.33]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA04206 for ; Sun, 27 Jan 2002 17:39:59 -0500 (EST) Received: from cehc.com (unverified [64.86.192.77]) by erp_ps.n-phc.com (EMWAC SMTPRS 0.83) with SMTP id ; Mon, 28 Jan 2002 07:35:30 +0900 Message-ID: <6cc1b30$22ec$365e> Mime-Version: 1.0 X-Priority: 1 (Highest) X-MSMail-Priority: High Importance: High Content-Type: multipart/mixed; boundary="----=_NextPart_19693_2718_12FB.5C327801F40B" To: "nat@ietf.org" From: "" Reply-to: admin@webmasterdirect.org Subject: [NAT] Read this! You definitely need it 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 ------=_NextPart_19693_2718_12FB.5C327801F40B Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 8bit DVD Copy Utility

Copy & Burn DVD's & VHS's w/CD Burner!!!

 

    Why Spend upwards of $4000 on a DVD Burner when we will show you an alternative that will do the exact same thing for only $19.95?

    You heard us right - for the price of just 1 DVD's, we'll show you how to back up and/or create Your Own DVD's!

    Just upgraded to a DVD and still have a ton of VHS tapes lying around? With this program, not only can you burn & copy any DVD you've created, you'll also be able to transfer all your VHS tapes to DVD format as well!!

    Regular Price:

    For a Limited Time Only, get yours today for just ONLY $19.95!!

    ORDER NOW

                                    

You want to know more? Visit us at http://www.copydvd.net

Win $ 5000 NOW !!!
Forward this message to 5 of your friends (put our email: win@ewasher.org in the cc field along with your 5 friends email addresses) and you will be automatically entered in our drawing for $5000.

 


To be opt out from our future mailing please email optout@ewasher.org with the word remove in the subject line

 

To be removed from this mailing list please send an email to remove@ewasher.org with the word remove in the subject line

------=_NextPart_19693_2718_12FB.5C327801F40B-- _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From nat-admin@ietf.org Tue Jan 29 13:21:21 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 NAA12239; Tue, 29 Jan 2002 13:21:21 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA17942; Tue, 29 Jan 2002 12:58:02 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA17913 for ; Tue, 29 Jan 2002 12:58:00 -0500 (EST) Received: from hutmail.com ([61.79.57.33]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA11382 for ; Tue, 29 Jan 2002 12:57:51 -0500 (EST) Message-Id: <200201291757.MAA11382@ietf.org> Reply-To: turbozet@hutmail.com From: Lee To: Mime-Version: 1.0 Content-Type: text/html; charset="ks_c_5601-1987" Date: Wed, 30 Jan 2002 02:55:55 +0900 X-User: 2.6-hkilfmmu-hojlnt-Ffkiq Subject: [NAT] (광 고)획기적 홍보데이터!! 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


안녕하십니까? 메일데이터를 저렴한 가격에 드립니다. 관심없으시면 메일을 삭제해 주십시오.
본 메일은 정보통신부 권고사항에 의거하여 제목에 [광고]라 표시된 메일입니다.
본 내용은 스팸메일의 유형에 아무것도 속하지 않습니다.(피라미드, 행운의편지, 성인관련홍보 등)
또한 각 사이트의 공개게시판에서 임의추출한 것이므로 귀하의 신용정보와 아무런 연관이 없습니다.

프로그램으로 추출하여 작업한 메일데이터의 특징은 다음과 같습니다.
다음우표제? 안심하십시오. 철저한 작업으로 한메일이 없습니다. (한메일 포함된 것도 있음)
중복메일? 안심하십시오. 중복메일이 없습니다. 수신거부에 편리합니다.
통합? 편리하게 사용하시도록 똑같은 개수로 나누었습니다.
가격? 저렴합니다. 비싸지 않습니다.
호환? 한줄에 하나씩, 그리고 TXT로 저장되어 있습니다.
          어떤 프로그램과도 호환가능합니다.

...등등의 장점이 있습니다.
드라마틱한 홍보를 위한 필수데이터! 이런 기회는 다시오지 않습니다.
사이트를 참고해 주십시오. 건전한 용도로 쓰지 않는 분에게 판매하지 않으며,
각종 이용용도를 접수후, 엄선하여 몇분에게만 판매합니다.

come.to/adver  adver.ox.ro
adver.ce.ro      adver.pe.ky

접속이 느리면 adver2.(ce.ro / pe.ky / ox.ro)로 접속해 주십시오.
공지없이 중단되면 adver3, adver4, 5...이렇게 접속하시면 됩니다.
이유없이 사이트를 비방, 방해하는 사람에게 손해배상을 요구합니다.
본 사이트는 회사나 기업이 아닙니다. 오해마시길 바랍니다.
또한 본 메일은 사용자의 편의를 위해 절대 한번이상 발송하지 않습니다.
따라서 수신거부하실 필요가 없습니다.
문의사항 있으시면 메일주십시오.

_______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From daemon@optimus.ietf.org Tue Jan 29 13:21:26 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 NAA12244 for ; Tue, 29 Jan 2002 13:21:22 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA19778 for nat-archive@odin.ietf.org; Tue, 29 Jan 2002 13:21:24 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA17942; Tue, 29 Jan 2002 12:58:02 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA17913 for ; Tue, 29 Jan 2002 12:58:00 -0500 (EST) Received: from hutmail.com ([61.79.57.33]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA11382 for ; Tue, 29 Jan 2002 12:57:51 -0500 (EST) Message-Id: <200201291757.MAA11382@ietf.org> Reply-To: turbozet@hutmail.com From: Lee To: Mime-Version: 1.0 Content-Type: text/html; charset="ks_c_5601-1987" Date: Wed, 30 Jan 2002 02:55:55 +0900 X-User: 2.6-hkilfmmu-hojlnt-Ffkiq Subject: [NAT] (광 고)획기적 홍보데이터!! 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


안녕하십니까? 메일데이터를 저렴한 가격에 드립니다. 관심없으시면 메일을 삭제해 주십시오.
본 메일은 정보통신부 권고사항에 의거하여 제목에 [광고]라 표시된 메일입니다.
본 내용은 스팸메일의 유형에 아무것도 속하지 않습니다.(피라미드, 행운의편지, 성인관련홍보 등)
또한 각 사이트의 공개게시판에서 임의추출한 것이므로 귀하의 신용정보와 아무런 연관이 없습니다.

프로그램으로 추출하여 작업한 메일데이터의 특징은 다음과 같습니다.
다음우표제? 안심하십시오. 철저한 작업으로 한메일이 없습니다. (한메일 포함된 것도 있음)
중복메일? 안심하십시오. 중복메일이 없습니다. 수신거부에 편리합니다.
통합? 편리하게 사용하시도록 똑같은 개수로 나누었습니다.
가격? 저렴합니다. 비싸지 않습니다.
호환? 한줄에 하나씩, 그리고 TXT로 저장되어 있습니다.
          어떤 프로그램과도 호환가능합니다.

...등등의 장점이 있습니다.
드라마틱한 홍보를 위한 필수데이터! 이런 기회는 다시오지 않습니다.
사이트를 참고해 주십시오. 건전한 용도로 쓰지 않는 분에게 판매하지 않으며,
각종 이용용도를 접수후, 엄선하여 몇분에게만 판매합니다.

come.to/adver  adver.ox.ro
adver.ce.ro      adver.pe.ky

접속이 느리면 adver2.(ce.ro / pe.ky / ox.ro)로 접속해 주십시오.
공지없이 중단되면 adver3, adver4, 5...이렇게 접속하시면 됩니다.
이유없이 사이트를 비방, 방해하는 사람에게 손해배상을 요구합니다.
본 사이트는 회사나 기업이 아닙니다. 오해마시길 바랍니다.
또한 본 메일은 사용자의 편의를 위해 절대 한번이상 발송하지 않습니다.
따라서 수신거부하실 필요가 없습니다.
문의사항 있으시면 메일주십시오.

_______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From nat-admin@ietf.org Thu Jan 31 20:27:45 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 UAA17030; Thu, 31 Jan 2002 20:27:44 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA05249; Thu, 31 Jan 2002 20:20:07 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA05221 for ; Thu, 31 Jan 2002 20:20:06 -0500 (EST) Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16965; Thu, 31 Jan 2002 20:20:01 -0500 (EST) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g111JxR01918; Thu, 31 Jan 2002 17:19:59 -0800 (PST) Message-Id: <200202010119.g111JxR01918@gamma.isi.edu> To: IETF-Announce: ; Cc: rfc-ed@ISI.EDU, nat@ietf.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 31 Jan 2002 17:19:59 -0800 From: RFC Editor Subject: [NAT] RFC 3235 on NAT Friendly Application Design Guidelines 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 --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3235 Title: Network Address Translator (NAT)-Friendly Application Design Guidelines Author(s): D. Senie Status: Informational Date: January 2002 Mailbox: dts@senie.com Pages: 13 Characters: 29588 Updates/Obsoletes/SeeAlso: NONE I-D Tag: draft-ietf-nat-app-guide-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3235.txt This document discusses those things that application designers might wish to consider when designing new protocols. While many common Internet applications will operate cleanly in the presence of Network Address Translators, others suffer from a variety of problems when crossing these devices. Guidelines are presented herein to help ensure new protocols and applications will, to the extent possible, be compatible with NAT (Network Address Translation). This document is a product of the Network Address Translators Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020131171735.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3235 --OtherAccess Content-Type: Message/External-body; name="rfc3235.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020131171735.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat From daemon@ns.ietf.org Thu Jan 31 20:27:50 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 UAA17037 for ; Thu, 31 Jan 2002 20:27:45 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id UAA05551 for nat-archive@odin.ietf.org; Thu, 31 Jan 2002 20:27:48 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA05249; Thu, 31 Jan 2002 20:20:07 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA05221 for ; Thu, 31 Jan 2002 20:20:06 -0500 (EST) Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16965; Thu, 31 Jan 2002 20:20:01 -0500 (EST) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g111JxR01918; Thu, 31 Jan 2002 17:19:59 -0800 (PST) Message-Id: <200202010119.g111JxR01918@gamma.isi.edu> To: IETF-Announce: ; Cc: rfc-ed@ISI.EDU, nat@ietf.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 31 Jan 2002 17:19:59 -0800 From: RFC Editor Subject: [NAT] RFC 3235 on NAT Friendly Application Design Guidelines 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 --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3235 Title: Network Address Translator (NAT)-Friendly Application Design Guidelines Author(s): D. Senie Status: Informational Date: January 2002 Mailbox: dts@senie.com Pages: 13 Characters: 29588 Updates/Obsoletes/SeeAlso: NONE I-D Tag: draft-ietf-nat-app-guide-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3235.txt This document discusses those things that application designers might wish to consider when designing new protocols. While many common Internet applications will operate cleanly in the presence of Network Address Translators, others suffer from a variety of problems when crossing these devices. Guidelines are presented herein to help ensure new protocols and applications will, to the extent possible, be compatible with NAT (Network Address Translation). This document is a product of the Network Address Translators Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <020131171735.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3235 --OtherAccess Content-Type: Message/External-body; name="rfc3235.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <020131171735.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- _______________________________________________ nat mailing list nat@ietf.org https://www1.ietf.org/mailman/listinfo/nat