From mailman-admin@ietf.org  Sun Dec  1 10:20:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07584
	for <nat-archive@lists.ietf.org>; Sun, 1 Dec 2002 10:20:42 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB1FN1v04363
	for <nat-archive@lists.ietf.org>; Sun, 1 Dec 2002 10:23:01 -0500
Date: Sun, 01 Dec 2002 10:23:01 -0500
Message-ID: <20021201152301.8899.60130.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: nat-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

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.

***************************************************************************


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

        * the IETF plenary session,
        * any IETF working group or portion thereof,
        * the IESG, or any member thereof on behalf of the IESG,
        * the IAB or any member thereof on behalf of the IAB,
        * any IETF mailing list, including the IETF list itself, any
working
            group or design team list, or any other list functioning
under IETF
            auspices,
        * the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

   
***************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.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%40lists.ietf.org


From mailnull@www1.ietf.org  Mon Dec  2 00:33:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24893
	for <nat-archive@odin.ietf.org>; Mon, 2 Dec 2002 00:33:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB25ZdJ24310
	for nat-archive@odin.ietf.org; Mon, 2 Dec 2002 00:35:39 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB25SRv23952;
	Mon, 2 Dec 2002 00:28:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB25NHv23819
	for <nat@optimus.ietf.org>; Mon, 2 Dec 2002 00:23:17 -0500
Received: from wiprom2mx2.wipro.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24571
	for <nat@ietf.org>; Mon, 2 Dec 2002 00:20:17 -0500 (EST)
Received: from m2vwall5.wipro.com (m2vwall5.wipro.com [10.115.50.5])
	by wiprom2mx2.wipro.com (8.11.3/8.11.3) with SMTP id gB25N1b13910
	for <nat@ietf.org>; Mon, 2 Dec 2002 10:53:01 +0530 (IST)
Received: from blr-m3-msg.wipro.com ([10.114.50.99]) by blr-m1-bh2.wipro.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 2 Dec 2002 10:52:56 +0530
Received: from wipro.com ([10.114.5.250]) by blr-m3-msg.wipro.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 2 Dec 2002 10:52:55 +0530
Message-ID: <3DEAEE78.409@wipro.com>
Date: Mon, 02 Dec 2002 10:54:08 +0530
From: "Sam K. Sankoorikal" <sam.kuruvilla@wipro.com>
Reply-To: sam.kuruvilla@wipro.com
Organization: Wipro Technologies
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rajiv Raghunarayan <raraghun@cisco.com>, Rohit.Rohit@worldwidepackets.com,
        nat@ietf.org
Subject: Re: [NAT] Clarification required
References: <3DE89D04.5020503@wipro.com> <3DE8AF97.A9882A6@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Dec 2002 05:22:55.0659 (UTC) FILETIME=[DE91AFB0:01C299C2]
Content-Transfer-Encoding: 7bit
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Rajiv,

        Thanks for the elabourate mail. Everything is very clearly 
explained. However, your mail fails to give reason for why the OID 
natConfAddrMapEntryType has to remain read-create. I have pointed out 
reasons why it can be changed to read-only and yet give out the relevant 
information to the user. Infact, in the natConfAddrMapTable every other 
attribute  needs to be read-create, but how do we specify the 
natConfAddrMapEntryType in the case of dynamic? Please give me an 
example for such a possibility.

        Please be kind enough to let me know reasons for why it has to 
remain a read-create OID. In my view: if it remains a read-create OID 
then the user is forced to set a value while creating the row, which 
will have to be rejected at the agent end, if it is specified as dynamic 
[NAT or NAPT] mapping.

Thanks and Regards,
Sam.

Rajiv Raghunarayan wrote:

>Hi Sam,
>
>A typical NAT config and usage would be as follows:
>
>1. Define the translations/address maps. E.g. local address: 
>   10.0.0.0/24, global address: 64.0.0.0/24 (ports may also be 
>   involved, but I've ignored it for simplicity).
>
>   This is done by the network administrator, based on the
>   addresses available/in use and the network configuration.
>   At this stage, depending on various factors (e.g. ratio of
>   internal hosts v/s available external addresses, future
>   expansion, accessibility necessary for hosts/servers etc.),
>   the network administrator also decides whether the mapping
>   must be static or dynamic, what type of NAT (basic, napt) 
>   needs to be used etc.
>
>2. Depending on the mapping type i.e. static/dynamic (and, of
>   course, implementation) BINDs are created in the BIND table 
>   either immediately or when the traffic flows from/to the 
>   addresses defined in the address map. 
>
>   The BINDs created are based off the address maps defined
>   earlier. E.g. 10.0.0.1 => 64.0.0.1, 10.0.0.2 => 64.0.0.2.
>
>   In case of static address maps, the BINDs are defined and
>   fixed at the time of the address map definition i.e. the
>   number of local address will be equal to the no. of 
>   external addresses and these will have one-to-one mapping
>   as defined above (again ignoring ports for simplicity).
>
>   In case of dynamic address maps, the BINDs are defined
>   only when the traffic flows. The number of local address 
>   needn't be (and usually aren't) same as the no. external
>   addresses. This is, therefore, a dynamic mapping.
>
>>From a MIB perspective, the natConfAddrMapTable represents
>the translation/address mapping definition (step #1 above).
>The entries in this table may be created via SNMP, or any
>other means (CLI, HTTP etc.). The actual BINDs (as created 
>in step #2 above) are represented by the natAddrBind and 
>natAddrPortBind tables in the MIB.
>
>-Rajiv.
>
>>"Sam K. Sankoorikal" wrote:
>>
>>Hi Rajiv,
>>
>>        Good Day!
>>
>>        I have gone through section 4.3 of the NAT-MIB . I quote the
>>section:
>>
>>"  -  Setting  the natConfStatus to 'active'(1) will enable
>>      nat on the interface. Note that the associated entries in the
>>      natConfAddrMapTable and natConfProtTable (if any) must also
>>      be made active.
>>   -  The Address Bind and Address-Port Table will have the entries
>>      created due to this nat configuration. A Management Station may
>>      also, if deemed necessary, create entries Address Bind or a
>>      Address-Port Bind entry and link those entries to the
>>appropriate
>>      address map configured. "
>>
>>The above section does not tell us the values to be set in case you
>>needed to create an entry in the natConfAddrMapTable. ie what value
>>would I have to set natConfAddrMapEntryType to go on and create an
>>entry
>>
>>NatConfAddrMapEntry ::= SEQUENCE {
>>    natConfAddrMapName             SnmpAdminString,
>>    natConfAddrMapIndex            Integer32,
>>    natConfAddrMapEntryType        INTEGER,
>>    natConfAddrMapDirection        INTEGER,
>>    natConfLocalAddrType           InetAddressType,
>>    natConfLocalAddrFrom           InetAddress,
>>    natConfLocalAddrTo             InetAddress,
>>    natConfLocalPortFrom           Integer32,
>>    natConfLocalPortTo             Integer32,
>>    natConfGlobalAddrType          InetAddressType,
>>    natConfGlobalAddrFrom          InetAddress,
>>    natConfGlobalAddrTo            InetAddress,
>>    natConfGlobalPortFrom          Integer32,
>>    natConfGlobalPortTo            Integer32,
>>    natConfProtocol                BITS,
>>    natConfAddrMapStorageType      StorageType,
>>    natConfAddrMapStatus           RowStatus
>>}
>>
>>natConfAddrMapEntryType OBJECT-TYPE
>>    SYNTAX  INTEGER {
>>                static (1),
>>                dynamic (2)
>>            }
>>    MAX-ACCESS  read-create
>>    STATUS      current
>>    DESCRIPTION
>>            "This config parameter can be used to set up static
>>             or dynamic address maps."
>>    ::= { natConfAddrMapEntry 3 }
>>
>>I also quote Rohits' input:
>>Static Address assignment
>>   In the case of static address assignment, there is one-to-one
>>address
>>   mapping for hosts between a private network address and an external
>>   network address for the lifetime of NAT operation.  Static address
>>   assignment ensures that NAT does not have to administer address
>>   management with session flows.
>>Dynamic Address assignment
>>   In this case, external addresses are assigned to private network
>>   hosts or vice versa, dynamically based on usage requirements and
>>   session flow determined heuristically by NAT. When the last session
>>   using an address binding is terminated, NAT would free the binding
>>so
>>   that the global address could be recycled for later use. The exact
>>   nature of address assignment is specific to individual NAT
>>   imp
>>lementations.
>>(The functionality has been described. More could be added on how we
>>would configure the same)
>>
>>Based on the above definition of dynamic NAT it seems that the
>>NatConfAddrMapEntry 's  which are dynamic are created on the fly, on a
>>need basis by the NAT module/protocol and can't be exactly specified
>>as dynamic and created by a user through SNMP. However if we wanted to
>>configure a Static NAT entry then that configuration could be created
>>by the user by specifying other [Direction, Addresses, Ports,
>>protocols] OID value other than the natConfAddrMapEntryType. This
>>value will be derived. Hence I think it would be clearer if the
>>natConfAddrMapEntryType were given a max access of read-only. This is
>>something which cannot be specified by the user. To tell more about
>>the dynamic entries I think by enabling NAT on an interface and
>>running a network application using NAT, then dynamic NAT entries
>>would be created. The same could be repeated for NAPT.
>>
>>natConfAddrMapEntryType OBJECT-TYPE
>>    SYNTAX  INTEGER {
>>                static (1),
>>                dynamic (2)
>>            }
>>    MAX-ACCESS  read-only
>>Thanks and Regards,
>>Sam.
>>
>>--
>> [ ]    Sam K. Sankoorikal.
>>        Home Net Solutions ,
>>        Wipro Technologies
>>        Ganapa Complex,
>>        #53/1 Hosur Rd Madivala,
>>        Bangalore, India 560068
>>        PBX:     +91 80 5502001 extn 3114
>>        sam.kuruvilla@wipro.com
>>
>>                           Name: Wipro_Disclaimer.txt
>>   Wipro_Disclaimer.txt    Type: Plain Text (text/plain)
>>                       Encoding: 7bit
>>
>



_______________________________________________
nat mailing list
nat@ietf.org
https://www1.ietf.org/mailman/listinfo/nat



From nat-admin@ietf.org  Mon Dec  2 01:24:31 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24894
	for <nat-archive@lists.ietf.org>; Mon, 2 Dec 2002 00:33:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB25SRv23952;
	Mon, 2 Dec 2002 00:28:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB25NHv23819
	for <nat@optimus.ietf.org>; Mon, 2 Dec 2002 00:23:17 -0500
Received: from wiprom2mx2.wipro.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24571
	for <nat@ietf.org>; Mon, 2 Dec 2002 00:20:17 -0500 (EST)
Received: from m2vwall5.wipro.com (m2vwall5.wipro.com [10.115.50.5])
	by wiprom2mx2.wipro.com (8.11.3/8.11.3) with SMTP id gB25N1b13910
	for <nat@ietf.org>; Mon, 2 Dec 2002 10:53:01 +0530 (IST)
Received: from blr-m3-msg.wipro.com ([10.114.50.99]) by blr-m1-bh2.wipro.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 2 Dec 2002 10:52:56 +0530
Received: from wipro.com ([10.114.5.250]) by blr-m3-msg.wipro.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 2 Dec 2002 10:52:55 +0530
Message-ID: <3DEAEE78.409@wipro.com>
Date: Mon, 02 Dec 2002 10:54:08 +0530
From: "Sam K. Sankoorikal" <sam.kuruvilla@wipro.com>
Reply-To: sam.kuruvilla@wipro.com
Organization: Wipro Technologies
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rajiv Raghunarayan <raraghun@cisco.com>, Rohit.Rohit@worldwidepackets.com,
        nat@ietf.org
Subject: Re: [NAT] Clarification required
References: <3DE89D04.5020503@wipro.com> <3DE8AF97.A9882A6@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Dec 2002 05:22:55.0659 (UTC) FILETIME=[DE91AFB0:01C299C2]
Content-Transfer-Encoding: 7bit
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Rajiv,

        Thanks for the elabourate mail. Everything is very clearly 
explained. However, your mail fails to give reason for why the OID 
natConfAddrMapEntryType has to remain read-create. I have pointed out 
reasons why it can be changed to read-only and yet give out the relevant 
information to the user. Infact, in the natConfAddrMapTable every other 
attribute  needs to be read-create, but how do we specify the 
natConfAddrMapEntryType in the case of dynamic? Please give me an 
example for such a possibility.

        Please be kind enough to let me know reasons for why it has to 
remain a read-create OID. In my view: if it remains a read-create OID 
then the user is forced to set a value while creating the row, which 
will have to be rejected at the agent end, if it is specified as dynamic 
[NAT or NAPT] mapping.

Thanks and Regards,
Sam.

Rajiv Raghunarayan wrote:

>Hi Sam,
>
>A typical NAT config and usage would be as follows:
>
>1. Define the translations/address maps. E.g. local address: 
>   10.0.0.0/24, global address: 64.0.0.0/24 (ports may also be 
>   involved, but I've ignored it for simplicity).
>
>   This is done by the network administrator, based on the
>   addresses available/in use and the network configuration.
>   At this stage, depending on various factors (e.g. ratio of
>   internal hosts v/s available external addresses, future
>   expansion, accessibility necessary for hosts/servers etc.),
>   the network administrator also decides whether the mapping
>   must be static or dynamic, what type of NAT (basic, napt) 
>   needs to be used etc.
>
>2. Depending on the mapping type i.e. static/dynamic (and, of
>   course, implementation) BINDs are created in the BIND table 
>   either immediately or when the traffic flows from/to the 
>   addresses defined in the address map. 
>
>   The BINDs created are based off the address maps defined
>   earlier. E.g. 10.0.0.1 => 64.0.0.1, 10.0.0.2 => 64.0.0.2.
>
>   In case of static address maps, the BINDs are defined and
>   fixed at the time of the address map definition i.e. the
>   number of local address will be equal to the no. of 
>   external addresses and these will have one-to-one mapping
>   as defined above (again ignoring ports for simplicity).
>
>   In case of dynamic address maps, the BINDs are defined
>   only when the traffic flows. The number of local address 
>   needn't be (and usually aren't) same as the no. external
>   addresses. This is, therefore, a dynamic mapping.
>
>>From a MIB perspective, the natConfAddrMapTable represents
>the translation/address mapping definition (step #1 above).
>The entries in this table may be created via SNMP, or any
>other means (CLI, HTTP etc.). The actual BINDs (as created 
>in step #2 above) are represented by the natAddrBind and 
>natAddrPortBind tables in the MIB.
>
>-Rajiv.
>
>>"Sam K. Sankoorikal" wrote:
>>
>>Hi Rajiv,
>>
>>        Good Day!
>>
>>        I have gone through section 4.3 of the NAT-MIB . I quote the
>>section:
>>
>>"  -  Setting  the natConfStatus to 'active'(1) will enable
>>      nat on the interface. Note that the associated entries in the
>>      natConfAddrMapTable and natConfProtTable (if any) must also
>>      be made active.
>>   -  The Address Bind and Address-Port Table will have the entries
>>      created due to this nat configuration. A Management Station may
>>      also, if deemed necessary, create entries Address Bind or a
>>      Address-Port Bind entry and link those entries to the
>>appropriate
>>      address map configured. "
>>
>>The above section does not tell us the values to be set in case you
>>needed to create an entry in the natConfAddrMapTable. ie what value
>>would I have to set natConfAddrMapEntryType to go on and create an
>>entry
>>
>>NatConfAddrMapEntry ::= SEQUENCE {
>>    natConfAddrMapName             SnmpAdminString,
>>    natConfAddrMapIndex            Integer32,
>>    natConfAddrMapEntryType        INTEGER,
>>    natConfAddrMapDirection        INTEGER,
>>    natConfLocalAddrType           InetAddressType,
>>    natConfLocalAddrFrom           InetAddress,
>>    natConfLocalAddrTo             InetAddress,
>>    natConfLocalPortFrom           Integer32,
>>    natConfLocalPortTo             Integer32,
>>    natConfGlobalAddrType          InetAddressType,
>>    natConfGlobalAddrFrom          InetAddress,
>>    natConfGlobalAddrTo            InetAddress,
>>    natConfGlobalPortFrom          Integer32,
>>    natConfGlobalPortTo            Integer32,
>>    natConfProtocol                BITS,
>>    natConfAddrMapStorageType      StorageType,
>>    natConfAddrMapStatus           RowStatus
>>}
>>
>>natConfAddrMapEntryType OBJECT-TYPE
>>    SYNTAX  INTEGER {
>>                static (1),
>>                dynamic (2)
>>            }
>>    MAX-ACCESS  read-create
>>    STATUS      current
>>    DESCRIPTION
>>            "This config parameter can be used to set up static
>>             or dynamic address maps."
>>    ::= { natConfAddrMapEntry 3 }
>>
>>I also quote Rohits' input:
>>Static Address assignment
>>   In the case of static address assignment, there is one-to-one
>>address
>>   mapping for hosts between a private network address and an external
>>   network address for the lifetime of NAT operation.  Static address
>>   assignment ensures that NAT does not have to administer address
>>   management with session flows.
>>Dynamic Address assignment
>>   In this case, external addresses are assigned to private network
>>   hosts or vice versa, dynamically based on usage requirements and
>>   session flow determined heuristically by NAT. When the last session
>>   using an address binding is terminated, NAT would free the binding
>>so
>>   that the global address could be recycled for later use. The exact
>>   nature of address assignment is specific to individual NAT
>>   imp
>>lementations.
>>(The functionality has been described. More could be added on how we
>>would configure the same)
>>
>>Based on the above definition of dynamic NAT it seems that the
>>NatConfAddrMapEntry 's  which are dynamic are created on the fly, on a
>>need basis by the NAT module/protocol and can't be exactly specified
>>as dynamic and created by a user through SNMP. However if we wanted to
>>configure a Static NAT entry then that configuration could be created
>>by the user by specifying other [Direction, Addresses, Ports,
>>protocols] OID value other than the natConfAddrMapEntryType. This
>>value will be derived. Hence I think it would be clearer if the
>>natConfAddrMapEntryType were given a max access of read-only. This is
>>something which cannot be specified by the user. To tell more about
>>the dynamic entries I think by enabling NAT on an interface and
>>running a network application using NAT, then dynamic NAT entries
>>would be created. The same could be repeated for NAPT.
>>
>>natConfAddrMapEntryType OBJECT-TYPE
>>    SYNTAX  INTEGER {
>>                static (1),
>>                dynamic (2)
>>            }
>>    MAX-ACCESS  read-only
>>Thanks and Regards,
>>Sam.
>>
>>--
>> [ ]    Sam K. Sankoorikal.
>>        Home Net Solutions ,
>>        Wipro Technologies
>>        Ganapa Complex,
>>        #53/1 Hosur Rd Madivala,
>>        Bangalore, India 560068
>>        PBX:     +91 80 5502001 extn 3114
>>        sam.kuruvilla@wipro.com
>>
>>                           Name: Wipro_Disclaimer.txt
>>   Wipro_Disclaimer.txt    Type: Plain Text (text/plain)
>>                       Encoding: 7bit
>>
>



_______________________________________________
nat mailing list
nat@ietf.org
https://www1.ietf.org/mailman/listinfo/nat


From nat-admin@ietf.org  Mon Dec  2 05:36:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09765
	for <nat-archive@lists.ietf.org>; Mon, 2 Dec 2002 05:36:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2AaMv19768;
	Mon, 2 Dec 2002 05:36:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2AXnv19692
	for <nat@optimus.ietf.org>; Mon, 2 Dec 2002 05:33:49 -0500
Received: from wiprom2mx2.wipro.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09704
	for <nat@ietf.org>; Mon, 2 Dec 2002 05:30:57 -0500 (EST)
Received: from m2vwall5.wipro.com (m2vwall5.wipro.com [10.115.50.5])
	by wiprom2mx2.wipro.com (8.11.3/8.11.3) with SMTP id gB2AXfb05772
	for <nat@ietf.org>; Mon, 2 Dec 2002 16:03:41 +0530 (IST)
Received: from blr-m3-msg.wipro.com ([10.114.50.99]) by blr-m1-bh2.wipro.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 2 Dec 2002 16:03:36 +0530
Received: from wipro.com ([10.114.5.250]) by blr-m3-msg.wipro.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 2 Dec 2002 16:03:34 +0530
Message-ID: <3DEB3747.6090200@wipro.com>
Date: Mon, 02 Dec 2002 16:04:47 +0530
From: "Sam K. Sankoorikal" <sam.kuruvilla@wipro.com>
Reply-To: sam.kuruvilla@wipro.com
Organization: Wipro Technologies
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: raraghun@cisco.com, Rohit.Rohit@worldwidepackets.com, nat@ietf.org
Subject: Re: [NAT] Clarification required
References: <Pine.GSO.4.44.0212021105210.27329-100000@cbin2-view1.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Dec 2002 10:33:34.0698 (UTC) FILETIME=[444D54A0:01C299EE]
Content-Transfer-Encoding: 7bit
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Rajiv,

            Well there seems to be some specific cases, as you pointed 
out, where this can to be set to dynamic/static as the case maybe. As 
for your second mail  quoted below:


" I'm not sure if this is cause for confusion, but just in case..
The natConfAddrMapEntryType reflects that static/dynamic nature
of entries in the natAddr*Bind tables, and *not* the nature of
entries in the natConfAddrMapTable. 

-Rajiv."

            Here it seems we are running into a loop. Does this again 
mean that based on what entries we have in the natAddrBindTable the 
value of natConfAddrMapEntryType is decided. But I guess we already have 
natAddrBindType - to decide what types of NatAddrBindEntry are present 
there. Shouldn't it be that the Bind table uses the values in the 
 natConfAddrMapEntryType to decide what type of entry it must hold there??


Thanks for the clarification,
Sam.

Rajiv Raghunarayan wrote:

>Hi Sam,
>
>As we've discussed below, a network admin specifies the address map in the
>natConfAddrMapTable, and at the same time also determines whether this
>needs to be a static map or a dynamic one. A simple rule for this could be
>- if the no. of internal & external addresses is equal use static map,
>else dynamic. And this could potentially be employed and the object
>implemented as read-only by certain implementations. But this certainly
>doesn't address all cases e.g. a customer might want to use dynamic map
>inspite of equal internal & external addr. count. The mib definition would
>need to account for all such cases too. Hence, the natConfAddrMapEntryType
>is a read-create object.
>
>-Rajiv.
>
>On Mon, 2 Dec 2002, Sam K. Sankoorikal wrote:
>
>>Hi Rajiv,
>>
>>        Thanks for the elabourate mail. Everything is very clearly
>>explained. However, your mail fails to give reason for why the OID
>>natConfAddrMapEntryType has to remain read-create. I have pointed out
>>reasons why it can be changed to read-only and yet give out the relevant
>>information to the user. Infact, in the natConfAddrMapTable every other
>>attribute  needs to be read-create, but how do we specify the
>>natConfAddrMapEntryType in the case of dynamic? Please give me an
>>example for such a possibility.
>>
>>        Please be kind enough to let me know reasons for why it has to
>>remain a read-create OID. In my view: if it remains a read-create OID
>>then the user is forced to set a value while creating the row, which
>>will have to be rejected at the agent end, if it is specified as dynamic
>>[NAT or NAPT] mapping.
>>
>>Thanks and Regards,
>>Sam.
>>
>>Rajiv Raghunarayan wrote:
>>
>>>Hi Sam,
>>>
>>>A typical NAT config and usage would be as follows:
>>>
>>>1. Define the translations/address maps. E.g. local address:
>>>  10.0.0.0/24, global address: 64.0.0.0/24 (ports may also be
>>>  involved, but I've ignored it for simplicity).
>>>
>>>  This is done by the network administrator, based on the
>>>  addresses available/in use and the network configuration.
>>>  At this stage, depending on various factors (e.g. ratio of
>>>  internal hosts v/s available external addresses, future
>>>  expansion, accessibility necessary for hosts/servers etc.),
>>>  the network administrator also decides whether the mapping
>>>  must be static or dynamic, what type of NAT (basic, napt)
>>>  needs to be used etc.
>>>
>>>2. Depending on the mapping type i.e. static/dynamic (and, of
>>>  course, implementation) BINDs are created in the BIND table
>>>  either immediately or when the traffic flows from/to the
>>>  addresses defined in the address map.
>>>
>>>  The BINDs created are based off the address maps defined
>>>  earlier. E.g. 10.0.0.1 => 64.0.0.1, 10.0.0.2 => 64.0.0.2.
>>>
>>>  In case of static address maps, the BINDs are defined and
>>>  fixed at the time of the address map definition i.e. the
>>>  number of local address will be equal to the no. of
>>>  external addresses and these will have one-to-one mapping
>>>  as defined above (again ignoring ports for simplicity).
>>>
>>>  In case of dynamic address maps, the BINDs are defined
>>>  only when the traffic flows. The number of local address
>>>  needn't be (and usually aren't) same as the no. external
>>>  addresses. This is, therefore, a dynamic mapping.
>>>
>>>>From a MIB perspective, the natConfAddrMapTable represents
>>>the translation/address mapping definition (step #1 above).
>>>The entries in this table may be created via SNMP, or any
>>>other means (CLI, HTTP etc.). The actual BINDs (as created
>>>in step #2 above) are represented by the natAddrBind and
>>>natAddrPortBind tables in the MIB.
>>>
>>>-Rajiv.
>>>
>>>>"Sam K. Sankoorikal" wrote:
>>>>
>>>>Hi Rajiv,
>>>>
>>>>       Good Day!
>>>>
>>>>       I have gone through section 4.3 of the NAT-MIB . I quote the
>>>>section:
>>>>
>>>>"  -  Setting  the natConfStatus to 'active'(1) will enable
>>>>     nat on the interface. Note that the associated entries in the
>>>>     natConfAddrMapTable and natConfProtTable (if any) must also
>>>>     be made active.
>>>>  -  The Address Bind and Address-Port Table will have the entries
>>>>     created due to this nat configuration. A Management Station may
>>>>     also, if deemed necessary, create entries Address Bind or a
>>>>     Address-Port Bind entry and link those entries to the
>>>>appropriate
>>>>     address map configured. "
>>>>
>>>>The above section does not tell us the values to be set in case you
>>>>needed to create an entry in the natConfAddrMapTable. ie what value
>>>>would I have to set natConfAddrMapEntryType to go on and create an
>>>>entry
>>>>
>>>>NatConfAddrMapEntry ::= SEQUENCE {
>>>>   natConfAddrMapName             SnmpAdminString,
>>>>   natConfAddrMapIndex            Integer32,
>>>>   natConfAddrMapEntryType        INTEGER,
>>>>   natConfAddrMapDirection        INTEGER,
>>>>   natConfLocalAddrType           InetAddressType,
>>>>   natConfLocalAddrFrom           InetAddress,
>>>>   natConfLocalAddrTo             InetAddress,
>>>>   natConfLocalPortFrom           Integer32,
>>>>   natConfLocalPortTo             Integer32,
>>>>   natConfGlobalAddrType          InetAddressType,
>>>>   natConfGlobalAddrFrom          InetAddress,
>>>>   natConfGlobalAddrTo            InetAddress,
>>>>   natConfGlobalPortFrom          Integer32,
>>>>   natConfGlobalPortTo            Integer32,
>>>>   natConfProtocol                BITS,
>>>>   natConfAddrMapStorageType      StorageType,
>>>>   natConfAddrMapStatus           RowStatus
>>>>}
>>>>
>>>>natConfAddrMapEntryType OBJECT-TYPE
>>>>   SYNTAX  INTEGER {
>>>>               static (1),
>>>>               dynamic (2)
>>>>           }
>>>>   MAX-ACCESS  read-create
>>>>   STATUS      current
>>>>   DESCRIPTION
>>>>           "This config parameter can be used to set up static
>>>>            or dynamic address maps."
>>>>   ::= { natConfAddrMapEntry 3 }
>>>>
>>>>I also quote Rohits' input:
>>>>Static Address assignment
>>>>  In the case of static address assignment, there is one-to-one
>>>>address
>>>>  mapping for hosts between a private network address and an external
>>>>  network address for the lifetime of NAT operation.  Static address
>>>>  assignment ensures that NAT does not have to administer address
>>>>  management with session flows.
>>>>Dynamic Address assignment
>>>>  In this case, external addresses are assigned to private network
>>>>  hosts or vice versa, dynamically based on usage requirements and
>>>>  session flow determined heuristically by NAT. When the last session
>>>>  using an address binding is terminated, NAT would free the binding
>>>>so
>>>>  that the global address could be recycled for later use. The exact
>>>>  nature of address assignment is specific to individual NAT
>>>>  imp
>>>>lementations.
>>>>(The functionality has been described. More could be added on how we
>>>>would configure the same)
>>>>
>>>>Based on the above definition of dynamic NAT it seems that the
>>>>NatConfAddrMapEntry 's  which are dynamic are created on the fly, on a
>>>>need basis by the NAT module/protocol and can't be exactly specified
>>>>as dynamic and created by a user through SNMP. However if we wanted to
>>>>configure a Static NAT entry then that configuration could be created
>>>>by the user by specifying other [Direction, Addresses, Ports,
>>>>protocols] OID value other than the natConfAddrMapEntryType. This
>>>>value will be derived. Hence I think it would be clearer if the
>>>>natConfAddrMapEntryType were given a max access of read-only. This is
>>>>something which cannot be specified by the user. To tell more about
>>>>the dynamic entries I think by enabling NAT on an interface and
>>>>running a network application using NAT, then dynamic NAT entries
>>>>would be created. The same could be repeated for NAPT.
>>>>
>>>>natConfAddrMapEntryType OBJECT-TYPE
>>>>   SYNTAX  INTEGER {
>>>>               static (1),
>>>>               dynamic (2)
>>>>           }
>>>>   MAX-ACCESS  read-only
>>>>Thanks and Regards,
>>>>Sam.
>>>>
>>>>--
>>>>[ ]    Sam K. Sankoorikal.
>>>>       Home Net Solutions ,
>>>>       Wipro Technologies
>>>>       Ganapa Complex,
>>>>       #53/1 Hosur Rd Madivala,
>>>>       Bangalore, India 560068
>>>>       PBX:     +91 80 5502001 extn 3114
>>>>       sam.kuruvilla@wipro.com
>>>>
>>>>                          Name: Wipro_Disclaimer.txt
>>>>  Wipro_Disclaimer.txt    Type: Plain Text (text/plain)
>>>>                      Encoding: 7bit
>>>>
>>
>>
>>
>
>




_______________________________________________
nat mailing list
nat@ietf.org
https://www1.ietf.org/mailman/listinfo/nat


From mailnull@www1.ietf.org  Mon Dec  2 05:39:11 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09830
	for <nat-archive@odin.ietf.org>; Mon, 2 Dec 2002 05:39:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB2AfUc20531
	for nat-archive@odin.ietf.org; Mon, 2 Dec 2002 05:41:30 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2AaMv19768;
	Mon, 2 Dec 2002 05:36:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2AXnv19692
	for <nat@optimus.ietf.org>; Mon, 2 Dec 2002 05:33:49 -0500
Received: from wiprom2mx2.wipro.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09704
	for <nat@ietf.org>; Mon, 2 Dec 2002 05:30:57 -0500 (EST)
Received: from m2vwall5.wipro.com (m2vwall5.wipro.com [10.115.50.5])
	by wiprom2mx2.wipro.com (8.11.3/8.11.3) with SMTP id gB2AXfb05772
	for <nat@ietf.org>; Mon, 2 Dec 2002 16:03:41 +0530 (IST)
Received: from blr-m3-msg.wipro.com ([10.114.50.99]) by blr-m1-bh2.wipro.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 2 Dec 2002 16:03:36 +0530
Received: from wipro.com ([10.114.5.250]) by blr-m3-msg.wipro.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 2 Dec 2002 16:03:34 +0530
Message-ID: <3DEB3747.6090200@wipro.com>
Date: Mon, 02 Dec 2002 16:04:47 +0530
From: "Sam K. Sankoorikal" <sam.kuruvilla@wipro.com>
Reply-To: sam.kuruvilla@wipro.com
Organization: Wipro Technologies
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: raraghun@cisco.com, Rohit.Rohit@worldwidepackets.com, nat@ietf.org
Subject: Re: [NAT] Clarification required
References: <Pine.GSO.4.44.0212021105210.27329-100000@cbin2-view1.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Dec 2002 10:33:34.0698 (UTC) FILETIME=[444D54A0:01C299EE]
Content-Transfer-Encoding: 7bit
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Rajiv,

            Well there seems to be some specific cases, as you pointed 
out, where this can to be set to dynamic/static as the case maybe. As 
for your second mail  quoted below:


" I'm not sure if this is cause for confusion, but just in case..
The natConfAddrMapEntryType reflects that static/dynamic nature
of entries in the natAddr*Bind tables, and *not* the nature of
entries in the natConfAddrMapTable. 

-Rajiv."

            Here it seems we are running into a loop. Does this again 
mean that based on what entries we have in the natAddrBindTable the 
value of natConfAddrMapEntryType is decided. But I guess we already have 
natAddrBindType - to decide what types of NatAddrBindEntry are present 
there. Shouldn't it be that the Bind table uses the values in the 
 natConfAddrMapEntryType to decide what type of entry it must hold there??


Thanks for the clarification,
Sam.

Rajiv Raghunarayan wrote:

>Hi Sam,
>
>As we've discussed below, a network admin specifies the address map in the
>natConfAddrMapTable, and at the same time also determines whether this
>needs to be a static map or a dynamic one. A simple rule for this could be
>- if the no. of internal & external addresses is equal use static map,
>else dynamic. And this could potentially be employed and the object
>implemented as read-only by certain implementations. But this certainly
>doesn't address all cases e.g. a customer might want to use dynamic map
>inspite of equal internal & external addr. count. The mib definition would
>need to account for all such cases too. Hence, the natConfAddrMapEntryType
>is a read-create object.
>
>-Rajiv.
>
>On Mon, 2 Dec 2002, Sam K. Sankoorikal wrote:
>
>>Hi Rajiv,
>>
>>        Thanks for the elabourate mail. Everything is very clearly
>>explained. However, your mail fails to give reason for why the OID
>>natConfAddrMapEntryType has to remain read-create. I have pointed out
>>reasons why it can be changed to read-only and yet give out the relevant
>>information to the user. Infact, in the natConfAddrMapTable every other
>>attribute  needs to be read-create, but how do we specify the
>>natConfAddrMapEntryType in the case of dynamic? Please give me an
>>example for such a possibility.
>>
>>        Please be kind enough to let me know reasons for why it has to
>>remain a read-create OID. In my view: if it remains a read-create OID
>>then the user is forced to set a value while creating the row, which
>>will have to be rejected at the agent end, if it is specified as dynamic
>>[NAT or NAPT] mapping.
>>
>>Thanks and Regards,
>>Sam.
>>
>>Rajiv Raghunarayan wrote:
>>
>>>Hi Sam,
>>>
>>>A typical NAT config and usage would be as follows:
>>>
>>>1. Define the translations/address maps. E.g. local address:
>>>  10.0.0.0/24, global address: 64.0.0.0/24 (ports may also be
>>>  involved, but I've ignored it for simplicity).
>>>
>>>  This is done by the network administrator, based on the
>>>  addresses available/in use and the network configuration.
>>>  At this stage, depending on various factors (e.g. ratio of
>>>  internal hosts v/s available external addresses, future
>>>  expansion, accessibility necessary for hosts/servers etc.),
>>>  the network administrator also decides whether the mapping
>>>  must be static or dynamic, what type of NAT (basic, napt)
>>>  needs to be used etc.
>>>
>>>2. Depending on the mapping type i.e. static/dynamic (and, of
>>>  course, implementation) BINDs are created in the BIND table
>>>  either immediately or when the traffic flows from/to the
>>>  addresses defined in the address map.
>>>
>>>  The BINDs created are based off the address maps defined
>>>  earlier. E.g. 10.0.0.1 => 64.0.0.1, 10.0.0.2 => 64.0.0.2.
>>>
>>>  In case of static address maps, the BINDs are defined and
>>>  fixed at the time of the address map definition i.e. the
>>>  number of local address will be equal to the no. of
>>>  external addresses and these will have one-to-one mapping
>>>  as defined above (again ignoring ports for simplicity).
>>>
>>>  In case of dynamic address maps, the BINDs are defined
>>>  only when the traffic flows. The number of local address
>>>  needn't be (and usually aren't) same as the no. external
>>>  addresses. This is, therefore, a dynamic mapping.
>>>
>>>>From a MIB perspective, the natConfAddrMapTable represents
>>>the translation/address mapping definition (step #1 above).
>>>The entries in this table may be created via SNMP, or any
>>>other means (CLI, HTTP etc.). The actual BINDs (as created
>>>in step #2 above) are represented by the natAddrBind and
>>>natAddrPortBind tables in the MIB.
>>>
>>>-Rajiv.
>>>
>>>>"Sam K. Sankoorikal" wrote:
>>>>
>>>>Hi Rajiv,
>>>>
>>>>       Good Day!
>>>>
>>>>       I have gone through section 4.3 of the NAT-MIB . I quote the
>>>>section:
>>>>
>>>>"  -  Setting  the natConfStatus to 'active'(1) will enable
>>>>     nat on the interface. Note that the associated entries in the
>>>>     natConfAddrMapTable and natConfProtTable (if any) must also
>>>>     be made active.
>>>>  -  The Address Bind and Address-Port Table will have the entries
>>>>     created due to this nat configuration. A Management Station may
>>>>     also, if deemed necessary, create entries Address Bind or a
>>>>     Address-Port Bind entry and link those entries to the
>>>>appropriate
>>>>     address map configured. "
>>>>
>>>>The above section does not tell us the values to be set in case you
>>>>needed to create an entry in the natConfAddrMapTable. ie what value
>>>>would I have to set natConfAddrMapEntryType to go on and create an
>>>>entry
>>>>
>>>>NatConfAddrMapEntry ::= SEQUENCE {
>>>>   natConfAddrMapName             SnmpAdminString,
>>>>   natConfAddrMapIndex            Integer32,
>>>>   natConfAddrMapEntryType        INTEGER,
>>>>   natConfAddrMapDirection        INTEGER,
>>>>   natConfLocalAddrType           InetAddressType,
>>>>   natConfLocalAddrFrom           InetAddress,
>>>>   natConfLocalAddrTo             InetAddress,
>>>>   natConfLocalPortFrom           Integer32,
>>>>   natConfLocalPortTo             Integer32,
>>>>   natConfGlobalAddrType          InetAddressType,
>>>>   natConfGlobalAddrFrom          InetAddress,
>>>>   natConfGlobalAddrTo            InetAddress,
>>>>   natConfGlobalPortFrom          Integer32,
>>>>   natConfGlobalPortTo            Integer32,
>>>>   natConfProtocol                BITS,
>>>>   natConfAddrMapStorageType      StorageType,
>>>>   natConfAddrMapStatus           RowStatus
>>>>}
>>>>
>>>>natConfAddrMapEntryType OBJECT-TYPE
>>>>   SYNTAX  INTEGER {
>>>>               static (1),
>>>>               dynamic (2)
>>>>           }
>>>>   MAX-ACCESS  read-create
>>>>   STATUS      current
>>>>   DESCRIPTION
>>>>           "This config parameter can be used to set up static
>>>>            or dynamic address maps."
>>>>   ::= { natConfAddrMapEntry 3 }
>>>>
>>>>I also quote Rohits' input:
>>>>Static Address assignment
>>>>  In the case of static address assignment, there is one-to-one
>>>>address
>>>>  mapping for hosts between a private network address and an external
>>>>  network address for the lifetime of NAT operation.  Static address
>>>>  assignment ensures that NAT does not have to administer address
>>>>  management with session flows.
>>>>Dynamic Address assignment
>>>>  In this case, external addresses are assigned to private network
>>>>  hosts or vice versa, dynamically based on usage requirements and
>>>>  session flow determined heuristically by NAT. When the last session
>>>>  using an address binding is terminated, NAT would free the binding
>>>>so
>>>>  that the global address could be recycled for later use. The exact
>>>>  nature of address assignment is specific to individual NAT
>>>>  imp
>>>>lementations.
>>>>(The functionality has been described. More could be added on how we
>>>>would configure the same)
>>>>
>>>>Based on the above definition of dynamic NAT it seems that the
>>>>NatConfAddrMapEntry 's  which are dynamic are created on the fly, on a
>>>>need basis by the NAT module/protocol and can't be exactly specified
>>>>as dynamic and created by a user through SNMP. However if we wanted to
>>>>configure a Static NAT entry then that configuration could be created
>>>>by the user by specifying other [Direction, Addresses, Ports,
>>>>protocols] OID value other than the natConfAddrMapEntryType. This
>>>>value will be derived. Hence I think it would be clearer if the
>>>>natConfAddrMapEntryType were given a max access of read-only. This is
>>>>something which cannot be specified by the user. To tell more about
>>>>the dynamic entries I think by enabling NAT on an interface and
>>>>running a network application using NAT, then dynamic NAT entries
>>>>would be created. The same could be repeated for NAPT.
>>>>
>>>>natConfAddrMapEntryType OBJECT-TYPE
>>>>   SYNTAX  INTEGER {
>>>>               static (1),
>>>>               dynamic (2)
>>>>           }
>>>>   MAX-ACCESS  read-only
>>>>Thanks and Regards,
>>>>Sam.
>>>>
>>>>--
>>>>[ ]    Sam K. Sankoorikal.
>>>>       Home Net Solutions ,
>>>>       Wipro Technologies
>>>>       Ganapa Complex,
>>>>       #53/1 Hosur Rd Madivala,
>>>>       Bangalore, India 560068
>>>>       PBX:     +91 80 5502001 extn 3114
>>>>       sam.kuruvilla@wipro.com
>>>>
>>>>                          Name: Wipro_Disclaimer.txt
>>>>  Wipro_Disclaimer.txt    Type: Plain Text (text/plain)
>>>>                      Encoding: 7bit
>>>>
>>
>>
>>
>
>




_______________________________________________
nat mailing list
nat@ietf.org
https://www1.ietf.org/mailman/listinfo/nat



From nat-admin@ietf.org  Mon Dec  2 11:48:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25325
	for <nat-archive@lists.ietf.org>; Mon, 2 Dec 2002 11:48:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2GoKv12799;
	Mon, 2 Dec 2002 11:50:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB25t9v25541
	for <nat@optimus.ietf.org>; Mon, 2 Dec 2002 00:55:09 -0500
Received: from sj-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25247
	for <nat@ietf.org>; Mon, 2 Dec 2002 00:52:10 -0500 (EST)
Received: from cbin2-view1.cisco.com (cbin2-view1.cisco.com [64.104.144.11])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gB25stK1003494;
	Sun, 1 Dec 2002 21:54:56 -0800 (PST)
Date: Mon, 2 Dec 2002 11:24:55 +0530 (IST)
From: Rajiv Raghunarayan <raraghun@cisco.com>
To: "Sam K. Sankoorikal" <sam.kuruvilla@wipro.com>
cc: Rohit.Rohit@worldwidepackets.com, <nat@ietf.org>
Subject: Re: [NAT] Clarification required
In-Reply-To: <3DEAEE78.409@wipro.com>
Message-ID: <Pine.GSO.4.44.0212021105210.27329-100000@cbin2-view1.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>

Hi Sam,

As we've discussed below, a network admin specifies the address map in the
natConfAddrMapTable, and at the same time also determines whether this
needs to be a static map or a dynamic one. A simple rule for this could be
- if the no. of internal & external addresses is equal use static map,
else dynamic. And this could potentially be employed and the object
implemented as read-only by certain implementations. But this certainly
doesn't address all cases e.g. a customer might want to use dynamic map
inspite of equal internal & external addr. count. The mib definition would
need to account for all such cases too. Hence, the natConfAddrMapEntryType
is a read-create object.

-Rajiv.

On Mon, 2 Dec 2002, Sam K. Sankoorikal wrote:

> Hi Rajiv,
>
>         Thanks for the elabourate mail. Everything is very clearly
> explained. However, your mail fails to give reason for why the OID
> natConfAddrMapEntryType has to remain read-create. I have pointed out
> reasons why it can be changed to read-only and yet give out the relevant
> information to the user. Infact, in the natConfAddrMapTable every other
> attribute  needs to be read-create, but how do we specify the
> natConfAddrMapEntryType in the case of dynamic? Please give me an
> example for such a possibility.
>
>         Please be kind enough to let me know reasons for why it has to
> remain a read-create OID. In my view: if it remains a read-create OID
> then the user is forced to set a value while creating the row, which
> will have to be rejected at the agent end, if it is specified as dynamic
> [NAT or NAPT] mapping.
>
> Thanks and Regards,
> Sam.
>
> Rajiv Raghunarayan wrote:
>
> >Hi Sam,
> >
> >A typical NAT config and usage would be as follows:
> >
> >1. Define the translations/address maps. E.g. local address:
> >   10.0.0.0/24, global address: 64.0.0.0/24 (ports may also be
> >   involved, but I've ignored it for simplicity).
> >
> >   This is done by the network administrator, based on the
> >   addresses available/in use and the network configuration.
> >   At this stage, depending on various factors (e.g. ratio of
> >   internal hosts v/s available external addresses, future
> >   expansion, accessibility necessary for hosts/servers etc.),
> >   the network administrator also decides whether the mapping
> >   must be static or dynamic, what type of NAT (basic, napt)
> >   needs to be used etc.
> >
> >2. Depending on the mapping type i.e. static/dynamic (and, of
> >   course, implementation) BINDs are created in the BIND table
> >   either immediately or when the traffic flows from/to the
> >   addresses defined in the address map.
> >
> >   The BINDs created are based off the address maps defined
> >   earlier. E.g. 10.0.0.1 => 64.0.0.1, 10.0.0.2 => 64.0.0.2.
> >
> >   In case of static address maps, the BINDs are defined and
> >   fixed at the time of the address map definition i.e. the
> >   number of local address will be equal to the no. of
> >   external addresses and these will have one-to-one mapping
> >   as defined above (again ignoring ports for simplicity).
> >
> >   In case of dynamic address maps, the BINDs are defined
> >   only when the traffic flows. The number of local address
> >   needn't be (and usually aren't) same as the no. external
> >   addresses. This is, therefore, a dynamic mapping.
> >
> >>From a MIB perspective, the natConfAddrMapTable represents
> >the translation/address mapping definition (step #1 above).
> >The entries in this table may be created via SNMP, or any
> >other means (CLI, HTTP etc.). The actual BINDs (as created
> >in step #2 above) are represented by the natAddrBind and
> >natAddrPortBind tables in the MIB.
> >
> >-Rajiv.
> >
> >>"Sam K. Sankoorikal" wrote:
> >>
> >>Hi Rajiv,
> >>
> >>        Good Day!
> >>
> >>        I have gone through section 4.3 of the NAT-MIB . I quote the
> >>section:
> >>
> >>"  -  Setting  the natConfStatus to 'active'(1) will enable
> >>      nat on the interface. Note that the associated entries in the
> >>      natConfAddrMapTable and natConfProtTable (if any) must also
> >>      be made active.
> >>   -  The Address Bind and Address-Port Table will have the entries
> >>      created due to this nat configuration. A Management Station may
> >>      also, if deemed necessary, create entries Address Bind or a
> >>      Address-Port Bind entry and link those entries to the
> >>appropriate
> >>      address map configured. "
> >>
> >>The above section does not tell us the values to be set in case you
> >>needed to create an entry in the natConfAddrMapTable. ie what value
> >>would I have to set natConfAddrMapEntryType to go on and create an
> >>entry
> >>
> >>NatConfAddrMapEntry ::= SEQUENCE {
> >>    natConfAddrMapName             SnmpAdminString,
> >>    natConfAddrMapIndex            Integer32,
> >>    natConfAddrMapEntryType        INTEGER,
> >>    natConfAddrMapDirection        INTEGER,
> >>    natConfLocalAddrType           InetAddressType,
> >>    natConfLocalAddrFrom           InetAddress,
> >>    natConfLocalAddrTo             InetAddress,
> >>    natConfLocalPortFrom           Integer32,
> >>    natConfLocalPortTo             Integer32,
> >>    natConfGlobalAddrType          InetAddressType,
> >>    natConfGlobalAddrFrom          InetAddress,
> >>    natConfGlobalAddrTo            InetAddress,
> >>    natConfGlobalPortFrom          Integer32,
> >>    natConfGlobalPortTo            Integer32,
> >>    natConfProtocol                BITS,
> >>    natConfAddrMapStorageType      StorageType,
> >>    natConfAddrMapStatus           RowStatus
> >>}
> >>
> >>natConfAddrMapEntryType OBJECT-TYPE
> >>    SYNTAX  INTEGER {
> >>                static (1),
> >>                dynamic (2)
> >>            }
> >>    MAX-ACCESS  read-create
> >>    STATUS      current
> >>    DESCRIPTION
> >>            "This config parameter can be used to set up static
> >>             or dynamic address maps."
> >>    ::= { natConfAddrMapEntry 3 }
> >>
> >>I also quote Rohits' input:
> >>Static Address assignment
> >>   In the case of static address assignment, there is one-to-one
> >>address
> >>   mapping for hosts between a private network address and an external
> >>   network address for the lifetime of NAT operation.  Static address
> >>   assignment ensures that NAT does not have to administer address
> >>   management with session flows.
> >>Dynamic Address assignment
> >>   In this case, external addresses are assigned to private network
> >>   hosts or vice versa, dynamically based on usage requirements and
> >>   session flow determined heuristically by NAT. When the last session
> >>   using an address binding is terminated, NAT would free the binding
> >>so
> >>   that the global address could be recycled for later use. The exact
> >>   nature of address assignment is specific to individual NAT
> >>   imp
> >>lementations.
> >>(The functionality has been described. More could be added on how we
> >>would configure the same)
> >>
> >>Based on the above definition of dynamic NAT it seems that the
> >>NatConfAddrMapEntry 's  which are dynamic are created on the fly, on a
> >>need basis by the NAT module/protocol and can't be exactly specified
> >>as dynamic and created by a user through SNMP. However if we wanted to
> >>configure a Static NAT entry then that configuration could be created
> >>by the user by specifying other [Direction, Addresses, Ports,
> >>protocols] OID value other than the natConfAddrMapEntryType. This
> >>value will be derived. Hence I think it would be clearer if the
> >>natConfAddrMapEntryType were given a max access of read-only. This is
> >>something which cannot be specified by the user. To tell more about
> >>the dynamic entries I think by enabling NAT on an interface and
> >>running a network application using NAT, then dynamic NAT entries
> >>would be created. The same could be repeated for NAPT.
> >>
> >>natConfAddrMapEntryType OBJECT-TYPE
> >>    SYNTAX  INTEGER {
> >>                static (1),
> >>                dynamic (2)
> >>            }
> >>    MAX-ACCESS  read-only
> >>Thanks and Regards,
> >>Sam.
> >>
> >>--
> >> [ ]    Sam K. Sankoorikal.
> >>        Home Net Solutions ,
> >>        Wipro Technologies
> >>        Ganapa Complex,
> >>        #53/1 Hosur Rd Madivala,
> >>        Bangalore, India 560068
> >>        PBX:     +91 80 5502001 extn 3114
> >>        sam.kuruvilla@wipro.com
> >>
> >>                           Name: Wipro_Disclaimer.txt
> >>   Wipro_Disclaimer.txt    Type: Plain Text (text/plain)
> >>                       Encoding: 7bit
> >>
> >
>
>
>
>

_______________________________________________
nat mailing list
nat@ietf.org
https://www1.ietf.org/mailman/listinfo/nat


From nat-admin@ietf.org  Mon Dec  2 11:51:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25520
	for <nat-archive@lists.ietf.org>; Mon, 2 Dec 2002 11:51:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2GqSv12876;
	Mon, 2 Dec 2002 11:52:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB27F9v06346
	for <nat@optimus.ietf.org>; Mon, 2 Dec 2002 02:15:09 -0500
Received: from india-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06145
	for <nat@ietf.org>; Mon, 2 Dec 2002 02:12:07 -0500 (EST)
Received: from cbin2-mira-01.cisco.com (localhost [127.0.0.1])
	by india-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gB2Chge6020992;
	Mon, 2 Dec 2002 12:43:43 GMT
Received: from cisco.com (shinjuku-equant-dynamic118.cisco.com [64.104.42.118])
	by cbin2-mira-01.cisco.com (Mirapoint)
	with ESMTP id AEO00005 (AUTH raraghun);
	Mon, 2 Dec 2002 12:37:25 +0530 (IST)
Message-ID: <3DEB07C6.EF620C27@cisco.com>
Date: Mon, 02 Dec 2002 12:42:06 +0530
From: Rajiv Raghunarayan <raraghun@cisco.com>
Organization: Cisco Systems Inc.
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: sam.kuruvilla@wipro.com
CC: Rohit.Rohit@worldwidepackets.com, nat@ietf.org
Subject: Re: [NAT] Clarification required
References: <3DE89D04.5020503@wipro.com> <3DE8AF97.A9882A6@cisco.com> <3DEAEE78.409@wipro.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Sam,

One comment inline..

"Sam K. Sankoorikal" wrote:
> 
> Hi Rajiv,
> 
>         Thanks for the elabourate mail. Everything is very clearly
> explained. However, your mail fails to give reason for why the OID
> natConfAddrMapEntryType has to remain read-create. I have pointed out
> reasons why it can be changed to read-only and yet give out the relevant
> information to the user. Infact, in the natConfAddrMapTable every other
> attribute  needs to be read-create, but how do we specify the
> natConfAddrMapEntryType in the case of dynamic? Please give me an
> example for such a possibility.

I'm not sure if this is cause for confusion, but just in case..
The natConfAddrMapEntryType reflects that static/dynamic nature
of entries in the natAddr*Bind tables, and *not* the nature of
entries in the natConfAddrMapTable. 

-Rajiv.

> 
>         Please be kind enough to let me know reasons for why it has to
> remain a read-create OID. In my view: if it remains a read-create OID
> then the user is forced to set a value while creating the row, which
> will have to be rejected at the agent end, if it is specified as dynamic
> [NAT or NAPT] mapping.
> 
> Thanks and Regards,
> Sam.
> 
> Rajiv Raghunarayan wrote:
> 
> >Hi Sam,
> >
> >A typical NAT config and usage would be as follows:
> >
> >1. Define the translations/address maps. E.g. local address:
> >   10.0.0.0/24, global address: 64.0.0.0/24 (ports may also be
> >   involved, but I've ignored it for simplicity).
> >
> >   This is done by the network administrator, based on the
> >   addresses available/in use and the network configuration.
> >   At this stage, depending on various factors (e.g. ratio of
> >   internal hosts v/s available external addresses, future
> >   expansion, accessibility necessary for hosts/servers etc.),
> >   the network administrator also decides whether the mapping
> >   must be static or dynamic, what type of NAT (basic, napt)
> >   needs to be used etc.
> >
> >2. Depending on the mapping type i.e. static/dynamic (and, of
> >   course, implementation) BINDs are created in the BIND table
> >   either immediately or when the traffic flows from/to the
> >   addresses defined in the address map.
> >
> >   The BINDs created are based off the address maps defined
> >   earlier. E.g. 10.0.0.1 => 64.0.0.1, 10.0.0.2 => 64.0.0.2.
> >
> >   In case of static address maps, the BINDs are defined and
> >   fixed at the time of the address map definition i.e. the
> >   number of local address will be equal to the no. of
> >   external addresses and these will have one-to-one mapping
> >   as defined above (again ignoring ports for simplicity).
> >
> >   In case of dynamic address maps, the BINDs are defined
> >   only when the traffic flows. The number of local address
> >   needn't be (and usually aren't) same as the no. external
> >   addresses. This is, therefore, a dynamic mapping.
> >
> >>From a MIB perspective, the natConfAddrMapTable represents
> >the translation/address mapping definition (step #1 above).
> >The entries in this table may be created via SNMP, or any
> >other means (CLI, HTTP etc.). The actual BINDs (as created
> >in step #2 above) are represented by the natAddrBind and
> >natAddrPortBind tables in the MIB.
> >
> >-Rajiv.
> >
> >>"Sam K. Sankoorikal" wrote:
> >>
> >>Hi Rajiv,
> >>
> >>        Good Day!
> >>
> >>        I have gone through section 4.3 of the NAT-MIB . I quote the
> >>section:
> >>
> >>"  -  Setting  the natConfStatus to 'active'(1) will enable
> >>      nat on the interface. Note that the associated entries in the
> >>      natConfAddrMapTable and natConfProtTable (if any) must also
> >>      be made active.
> >>   -  The Address Bind and Address-Port Table will have the entries
> >>      created due to this nat configuration. A Management Station may
> >>      also, if deemed necessary, create entries Address Bind or a
> >>      Address-Port Bind entry and link those entries to the
> >>appropriate
> >>      address map configured. "
> >>
> >>The above section does not tell us the values to be set in case you
> >>needed to create an entry in the natConfAddrMapTable. ie what value
> >>would I have to set natConfAddrMapEntryType to go on and create an
> >>entry
> >>
> >>NatConfAddrMapEntry ::= SEQUENCE {
> >>    natConfAddrMapName             SnmpAdminString,
> >>    natConfAddrMapIndex            Integer32,
> >>    natConfAddrMapEntryType        INTEGER,
> >>    natConfAddrMapDirection        INTEGER,
> >>    natConfLocalAddrType           InetAddressType,
> >>    natConfLocalAddrFrom           InetAddress,
> >>    natConfLocalAddrTo             InetAddress,
> >>    natConfLocalPortFrom           Integer32,
> >>    natConfLocalPortTo             Integer32,
> >>    natConfGlobalAddrType          InetAddressType,
> >>    natConfGlobalAddrFrom          InetAddress,
> >>    natConfGlobalAddrTo            InetAddress,
> >>    natConfGlobalPortFrom          Integer32,
> >>    natConfGlobalPortTo            Integer32,
> >>    natConfProtocol                BITS,
> >>    natConfAddrMapStorageType      StorageType,
> >>    natConfAddrMapStatus           RowStatus
> >>}
> >>
> >>natConfAddrMapEntryType OBJECT-TYPE
> >>    SYNTAX  INTEGER {
> >>                static (1),
> >>                dynamic (2)
> >>            }
> >>    MAX-ACCESS  read-create
> >>    STATUS      current
> >>    DESCRIPTION
> >>            "This config parameter can be used to set up static
> >>             or dynamic address maps."
> >>    ::= { natConfAddrMapEntry 3 }
> >>
> >>I also quote Rohits' input:
> >>Static Address assignment
> >>   In the case of static address assignment, there is one-to-one
> >>address
> >>   mapping for hosts between a private network address and an external
> >>   network address for the lifetime of NAT operation.  Static address
> >>   assignment ensures that NAT does not have to administer address
> >>   management with session flows.
> >>Dynamic Address assignment
> >>   In this case, external addresses are assigned to private network
> >>   hosts or vice versa, dynamically based on usage requirements and
> >>   session flow determined heuristically by NAT. When the last session
> >>   using an address binding is terminated, NAT would free the binding
> >>so
> >>   that the global address could be recycled for later use. The exact
> >>   nature of address assignment is specific to individual NAT
> >>   imp
> >>lementations.
> >>(The functionality has been described. More could be added on how we
> >>would configure the same)
> >>
> >>Based on the above definition of dynamic NAT it seems that the
> >>NatConfAddrMapEntry 's  which are dynamic are created on the fly, on a
> >>need basis by the NAT module/protocol and can't be exactly specified
> >>as dynamic and created by a user through SNMP. However if we wanted to
> >>configure a Static NAT entry then that configuration could be created
> >>by the user by specifying other [Direction, Addresses, Ports,
> >>protocols] OID value other than the natConfAddrMapEntryType. This
> >>value will be derived. Hence I think it would be clearer if the
> >>natConfAddrMapEntryType were given a max access of read-only. This is
> >>something which cannot be specified by the user. To tell more about
> >>the dynamic entries I think by enabling NAT on an interface and
> >>running a network application using NAT, then dynamic NAT entries
> >>would be created. The same could be repeated for NAPT.
> >>
> >>natConfAddrMapEntryType OBJECT-TYPE
> >>    SYNTAX  INTEGER {
> >>                static (1),
> >>                dynamic (2)
> >>            }
> >>    MAX-ACCESS  read-only
> >>Thanks and Regards,
> >>Sam.
> >>
> >>--
> >> [ ]    Sam K. Sankoorikal.
> >>        Home Net Solutions ,
> >>        Wipro Technologies
> >>        Ganapa Complex,
> >>        #53/1 Hosur Rd Madivala,
> >>        Bangalore, India 560068
> >>        PBX:     +91 80 5502001 extn 3114
> >>        sam.kuruvilla@wipro.com
> >>
> >>                           Name: Wipro_Disclaimer.txt
> >>   Wipro_Disclaimer.txt    Type: Plain Text (text/plain)
> >>                       Encoding: 7bit
> >>
> >
> 
> _______________________________________________
> nat mailing list
> nat@ietf.org
> https://www1.ietf.org/mailman/listinfo/nat
_______________________________________________
nat mailing list
nat@ietf.org
https://www1.ietf.org/mailman/listinfo/nat


From mailnull@www1.ietf.org  Mon Dec  2 11:53:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25597
	for <nat-archive@odin.ietf.org>; Mon, 2 Dec 2002 11:53:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB2GuDS13094
	for nat-archive@odin.ietf.org; Mon, 2 Dec 2002 11:56:13 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2GqSv12876;
	Mon, 2 Dec 2002 11:52:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB27F9v06346
	for <nat@optimus.ietf.org>; Mon, 2 Dec 2002 02:15:09 -0500
Received: from india-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06145
	for <nat@ietf.org>; Mon, 2 Dec 2002 02:12:07 -0500 (EST)
Received: from cbin2-mira-01.cisco.com (localhost [127.0.0.1])
	by india-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gB2Chge6020992;
	Mon, 2 Dec 2002 12:43:43 GMT
Received: from cisco.com (shinjuku-equant-dynamic118.cisco.com [64.104.42.118])
	by cbin2-mira-01.cisco.com (Mirapoint)
	with ESMTP id AEO00005 (AUTH raraghun);
	Mon, 2 Dec 2002 12:37:25 +0530 (IST)
Message-ID: <3DEB07C6.EF620C27@cisco.com>
Date: Mon, 02 Dec 2002 12:42:06 +0530
From: Rajiv Raghunarayan <raraghun@cisco.com>
Organization: Cisco Systems Inc.
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: sam.kuruvilla@wipro.com
CC: Rohit.Rohit@worldwidepackets.com, nat@ietf.org
Subject: Re: [NAT] Clarification required
References: <3DE89D04.5020503@wipro.com> <3DE8AF97.A9882A6@cisco.com> <3DEAEE78.409@wipro.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Sam,

One comment inline..

"Sam K. Sankoorikal" wrote:
> 
> Hi Rajiv,
> 
>         Thanks for the elabourate mail. Everything is very clearly
> explained. However, your mail fails to give reason for why the OID
> natConfAddrMapEntryType has to remain read-create. I have pointed out
> reasons why it can be changed to read-only and yet give out the relevant
> information to the user. Infact, in the natConfAddrMapTable every other
> attribute  needs to be read-create, but how do we specify the
> natConfAddrMapEntryType in the case of dynamic? Please give me an
> example for such a possibility.

I'm not sure if this is cause for confusion, but just in case..
The natConfAddrMapEntryType reflects that static/dynamic nature
of entries in the natAddr*Bind tables, and *not* the nature of
entries in the natConfAddrMapTable. 

-Rajiv.

> 
>         Please be kind enough to let me know reasons for why it has to
> remain a read-create OID. In my view: if it remains a read-create OID
> then the user is forced to set a value while creating the row, which
> will have to be rejected at the agent end, if it is specified as dynamic
> [NAT or NAPT] mapping.
> 
> Thanks and Regards,
> Sam.
> 
> Rajiv Raghunarayan wrote:
> 
> >Hi Sam,
> >
> >A typical NAT config and usage would be as follows:
> >
> >1. Define the translations/address maps. E.g. local address:
> >   10.0.0.0/24, global address: 64.0.0.0/24 (ports may also be
> >   involved, but I've ignored it for simplicity).
> >
> >   This is done by the network administrator, based on the
> >   addresses available/in use and the network configuration.
> >   At this stage, depending on various factors (e.g. ratio of
> >   internal hosts v/s available external addresses, future
> >   expansion, accessibility necessary for hosts/servers etc.),
> >   the network administrator also decides whether the mapping
> >   must be static or dynamic, what type of NAT (basic, napt)
> >   needs to be used etc.
> >
> >2. Depending on the mapping type i.e. static/dynamic (and, of
> >   course, implementation) BINDs are created in the BIND table
> >   either immediately or when the traffic flows from/to the
> >   addresses defined in the address map.
> >
> >   The BINDs created are based off the address maps defined
> >   earlier. E.g. 10.0.0.1 => 64.0.0.1, 10.0.0.2 => 64.0.0.2.
> >
> >   In case of static address maps, the BINDs are defined and
> >   fixed at the time of the address map definition i.e. the
> >   number of local address will be equal to the no. of
> >   external addresses and these will have one-to-one mapping
> >   as defined above (again ignoring ports for simplicity).
> >
> >   In case of dynamic address maps, the BINDs are defined
> >   only when the traffic flows. The number of local address
> >   needn't be (and usually aren't) same as the no. external
> >   addresses. This is, therefore, a dynamic mapping.
> >
> >>From a MIB perspective, the natConfAddrMapTable represents
> >the translation/address mapping definition (step #1 above).
> >The entries in this table may be created via SNMP, or any
> >other means (CLI, HTTP etc.). The actual BINDs (as created
> >in step #2 above) are represented by the natAddrBind and
> >natAddrPortBind tables in the MIB.
> >
> >-Rajiv.
> >
> >>"Sam K. Sankoorikal" wrote:
> >>
> >>Hi Rajiv,
> >>
> >>        Good Day!
> >>
> >>        I have gone through section 4.3 of the NAT-MIB . I quote the
> >>section:
> >>
> >>"  -  Setting  the natConfStatus to 'active'(1) will enable
> >>      nat on the interface. Note that the associated entries in the
> >>      natConfAddrMapTable and natConfProtTable (if any) must also
> >>      be made active.
> >>   -  The Address Bind and Address-Port Table will have the entries
> >>      created due to this nat configuration. A Management Station may
> >>      also, if deemed necessary, create entries Address Bind or a
> >>      Address-Port Bind entry and link those entries to the
> >>appropriate
> >>      address map configured. "
> >>
> >>The above section does not tell us the values to be set in case you
> >>needed to create an entry in the natConfAddrMapTable. ie what value
> >>would I have to set natConfAddrMapEntryType to go on and create an
> >>entry
> >>
> >>NatConfAddrMapEntry ::= SEQUENCE {
> >>    natConfAddrMapName             SnmpAdminString,
> >>    natConfAddrMapIndex            Integer32,
> >>    natConfAddrMapEntryType        INTEGER,
> >>    natConfAddrMapDirection        INTEGER,
> >>    natConfLocalAddrType           InetAddressType,
> >>    natConfLocalAddrFrom           InetAddress,
> >>    natConfLocalAddrTo             InetAddress,
> >>    natConfLocalPortFrom           Integer32,
> >>    natConfLocalPortTo             Integer32,
> >>    natConfGlobalAddrType          InetAddressType,
> >>    natConfGlobalAddrFrom          InetAddress,
> >>    natConfGlobalAddrTo            InetAddress,
> >>    natConfGlobalPortFrom          Integer32,
> >>    natConfGlobalPortTo            Integer32,
> >>    natConfProtocol                BITS,
> >>    natConfAddrMapStorageType      StorageType,
> >>    natConfAddrMapStatus           RowStatus
> >>}
> >>
> >>natConfAddrMapEntryType OBJECT-TYPE
> >>    SYNTAX  INTEGER {
> >>                static (1),
> >>                dynamic (2)
> >>            }
> >>    MAX-ACCESS  read-create
> >>    STATUS      current
> >>    DESCRIPTION
> >>            "This config parameter can be used to set up static
> >>             or dynamic address maps."
> >>    ::= { natConfAddrMapEntry 3 }
> >>
> >>I also quote Rohits' input:
> >>Static Address assignment
> >>   In the case of static address assignment, there is one-to-one
> >>address
> >>   mapping for hosts between a private network address and an external
> >>   network address for the lifetime of NAT operation.  Static address
> >>   assignment ensures that NAT does not have to administer address
> >>   management with session flows.
> >>Dynamic Address assignment
> >>   In this case, external addresses are assigned to private network
> >>   hosts or vice versa, dynamically based on usage requirements and
> >>   session flow determined heuristically by NAT. When the last session
> >>   using an address binding is terminated, NAT would free the binding
> >>so
> >>   that the global address could be recycled for later use. The exact
> >>   nature of address assignment is specific to individual NAT
> >>   imp
> >>lementations.
> >>(The functionality has been described. More could be added on how we
> >>would configure the same)
> >>
> >>Based on the above definition of dynamic NAT it seems that the
> >>NatConfAddrMapEntry 's  which are dynamic are created on the fly, on a
> >>need basis by the NAT module/protocol and can't be exactly specified
> >>as dynamic and created by a user through SNMP. However if we wanted to
> >>configure a Static NAT entry then that configuration could be created
> >>by the user by specifying other [Direction, Addresses, Ports,
> >>protocols] OID value other than the natConfAddrMapEntryType. This
> >>value will be derived. Hence I think it would be clearer if the
> >>natConfAddrMapEntryType were given a max access of read-only. This is
> >>something which cannot be specified by the user. To tell more about
> >>the dynamic entries I think by enabling NAT on an interface and
> >>running a network application using NAT, then dynamic NAT entries
> >>would be created. The same could be repeated for NAPT.
> >>
> >>natConfAddrMapEntryType OBJECT-TYPE
> >>    SYNTAX  INTEGER {
> >>                static (1),
> >>                dynamic (2)
> >>            }
> >>    MAX-ACCESS  read-only
> >>Thanks and Regards,
> >>Sam.
> >>
> >>--
> >> [ ]    Sam K. Sankoorikal.
> >>        Home Net Solutions ,
> >>        Wipro Technologies
> >>        Ganapa Complex,
> >>        #53/1 Hosur Rd Madivala,
> >>        Bangalore, India 560068
> >>        PBX:     +91 80 5502001 extn 3114
> >>        sam.kuruvilla@wipro.com
> >>
> >>                           Name: Wipro_Disclaimer.txt
> >>   Wipro_Disclaimer.txt    Type: Plain Text (text/plain)
> >>                       Encoding: 7bit
> >>
> >
> 
> _______________________________________________
> nat mailing list
> nat@ietf.org
> https://www1.ietf.org/mailman/listinfo/nat
_______________________________________________
nat mailing list
nat@ietf.org
https://www1.ietf.org/mailman/listinfo/nat



From mailnull@www1.ietf.org  Mon Dec  2 11:54:06 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25613
	for <nat-archive@odin.ietf.org>; Mon, 2 Dec 2002 11:54:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB2GuR013109
	for nat-archive@odin.ietf.org; Mon, 2 Dec 2002 11:56:27 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2GoKv12799;
	Mon, 2 Dec 2002 11:50:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB25t9v25541
	for <nat@optimus.ietf.org>; Mon, 2 Dec 2002 00:55:09 -0500
Received: from sj-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25247
	for <nat@ietf.org>; Mon, 2 Dec 2002 00:52:10 -0500 (EST)
Received: from cbin2-view1.cisco.com (cbin2-view1.cisco.com [64.104.144.11])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gB25stK1003494;
	Sun, 1 Dec 2002 21:54:56 -0800 (PST)
Date: Mon, 2 Dec 2002 11:24:55 +0530 (IST)
From: Rajiv Raghunarayan <raraghun@cisco.com>
To: "Sam K. Sankoorikal" <sam.kuruvilla@wipro.com>
cc: Rohit.Rohit@worldwidepackets.com, <nat@ietf.org>
Subject: Re: [NAT] Clarification required
In-Reply-To: <3DEAEE78.409@wipro.com>
Message-ID: <Pine.GSO.4.44.0212021105210.27329-100000@cbin2-view1.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>

Hi Sam,

As we've discussed below, a network admin specifies the address map in the
natConfAddrMapTable, and at the same time also determines whether this
needs to be a static map or a dynamic one. A simple rule for this could be
- if the no. of internal & external addresses is equal use static map,
else dynamic. And this could potentially be employed and the object
implemented as read-only by certain implementations. But this certainly
doesn't address all cases e.g. a customer might want to use dynamic map
inspite of equal internal & external addr. count. The mib definition would
need to account for all such cases too. Hence, the natConfAddrMapEntryType
is a read-create object.

-Rajiv.

On Mon, 2 Dec 2002, Sam K. Sankoorikal wrote:

> Hi Rajiv,
>
>         Thanks for the elabourate mail. Everything is very clearly
> explained. However, your mail fails to give reason for why the OID
> natConfAddrMapEntryType has to remain read-create. I have pointed out
> reasons why it can be changed to read-only and yet give out the relevant
> information to the user. Infact, in the natConfAddrMapTable every other
> attribute  needs to be read-create, but how do we specify the
> natConfAddrMapEntryType in the case of dynamic? Please give me an
> example for such a possibility.
>
>         Please be kind enough to let me know reasons for why it has to
> remain a read-create OID. In my view: if it remains a read-create OID
> then the user is forced to set a value while creating the row, which
> will have to be rejected at the agent end, if it is specified as dynamic
> [NAT or NAPT] mapping.
>
> Thanks and Regards,
> Sam.
>
> Rajiv Raghunarayan wrote:
>
> >Hi Sam,
> >
> >A typical NAT config and usage would be as follows:
> >
> >1. Define the translations/address maps. E.g. local address:
> >   10.0.0.0/24, global address: 64.0.0.0/24 (ports may also be
> >   involved, but I've ignored it for simplicity).
> >
> >   This is done by the network administrator, based on the
> >   addresses available/in use and the network configuration.
> >   At this stage, depending on various factors (e.g. ratio of
> >   internal hosts v/s available external addresses, future
> >   expansion, accessibility necessary for hosts/servers etc.),
> >   the network administrator also decides whether the mapping
> >   must be static or dynamic, what type of NAT (basic, napt)
> >   needs to be used etc.
> >
> >2. Depending on the mapping type i.e. static/dynamic (and, of
> >   course, implementation) BINDs are created in the BIND table
> >   either immediately or when the traffic flows from/to the
> >   addresses defined in the address map.
> >
> >   The BINDs created are based off the address maps defined
> >   earlier. E.g. 10.0.0.1 => 64.0.0.1, 10.0.0.2 => 64.0.0.2.
> >
> >   In case of static address maps, the BINDs are defined and
> >   fixed at the time of the address map definition i.e. the
> >   number of local address will be equal to the no. of
> >   external addresses and these will have one-to-one mapping
> >   as defined above (again ignoring ports for simplicity).
> >
> >   In case of dynamic address maps, the BINDs are defined
> >   only when the traffic flows. The number of local address
> >   needn't be (and usually aren't) same as the no. external
> >   addresses. This is, therefore, a dynamic mapping.
> >
> >>From a MIB perspective, the natConfAddrMapTable represents
> >the translation/address mapping definition (step #1 above).
> >The entries in this table may be created via SNMP, or any
> >other means (CLI, HTTP etc.). The actual BINDs (as created
> >in step #2 above) are represented by the natAddrBind and
> >natAddrPortBind tables in the MIB.
> >
> >-Rajiv.
> >
> >>"Sam K. Sankoorikal" wrote:
> >>
> >>Hi Rajiv,
> >>
> >>        Good Day!
> >>
> >>        I have gone through section 4.3 of the NAT-MIB . I quote the
> >>section:
> >>
> >>"  -  Setting  the natConfStatus to 'active'(1) will enable
> >>      nat on the interface. Note that the associated entries in the
> >>      natConfAddrMapTable and natConfProtTable (if any) must also
> >>      be made active.
> >>   -  The Address Bind and Address-Port Table will have the entries
> >>      created due to this nat configuration. A Management Station may
> >>      also, if deemed necessary, create entries Address Bind or a
> >>      Address-Port Bind entry and link those entries to the
> >>appropriate
> >>      address map configured. "
> >>
> >>The above section does not tell us the values to be set in case you
> >>needed to create an entry in the natConfAddrMapTable. ie what value
> >>would I have to set natConfAddrMapEntryType to go on and create an
> >>entry
> >>
> >>NatConfAddrMapEntry ::= SEQUENCE {
> >>    natConfAddrMapName             SnmpAdminString,
> >>    natConfAddrMapIndex            Integer32,
> >>    natConfAddrMapEntryType        INTEGER,
> >>    natConfAddrMapDirection        INTEGER,
> >>    natConfLocalAddrType           InetAddressType,
> >>    natConfLocalAddrFrom           InetAddress,
> >>    natConfLocalAddrTo             InetAddress,
> >>    natConfLocalPortFrom           Integer32,
> >>    natConfLocalPortTo             Integer32,
> >>    natConfGlobalAddrType          InetAddressType,
> >>    natConfGlobalAddrFrom          InetAddress,
> >>    natConfGlobalAddrTo            InetAddress,
> >>    natConfGlobalPortFrom          Integer32,
> >>    natConfGlobalPortTo            Integer32,
> >>    natConfProtocol                BITS,
> >>    natConfAddrMapStorageType      StorageType,
> >>    natConfAddrMapStatus           RowStatus
> >>}
> >>
> >>natConfAddrMapEntryType OBJECT-TYPE
> >>    SYNTAX  INTEGER {
> >>                static (1),
> >>                dynamic (2)
> >>            }
> >>    MAX-ACCESS  read-create
> >>    STATUS      current
> >>    DESCRIPTION
> >>            "This config parameter can be used to set up static
> >>             or dynamic address maps."
> >>    ::= { natConfAddrMapEntry 3 }
> >>
> >>I also quote Rohits' input:
> >>Static Address assignment
> >>   In the case of static address assignment, there is one-to-one
> >>address
> >>   mapping for hosts between a private network address and an external
> >>   network address for the lifetime of NAT operation.  Static address
> >>   assignment ensures that NAT does not have to administer address
> >>   management with session flows.
> >>Dynamic Address assignment
> >>   In this case, external addresses are assigned to private network
> >>   hosts or vice versa, dynamically based on usage requirements and
> >>   session flow determined heuristically by NAT. When the last session
> >>   using an address binding is terminated, NAT would free the binding
> >>so
> >>   that the global address could be recycled for later use. The exact
> >>   nature of address assignment is specific to individual NAT
> >>   imp
> >>lementations.
> >>(The functionality has been described. More could be added on how we
> >>would configure the same)
> >>
> >>Based on the above definition of dynamic NAT it seems that the
> >>NatConfAddrMapEntry 's  which are dynamic are created on the fly, on a
> >>need basis by the NAT module/protocol and can't be exactly specified
> >>as dynamic and created by a user through SNMP. However if we wanted to
> >>configure a Static NAT entry then that configuration could be created
> >>by the user by specifying other [Direction, Addresses, Ports,
> >>protocols] OID value other than the natConfAddrMapEntryType. This
> >>value will be derived. Hence I think it would be clearer if the
> >>natConfAddrMapEntryType were given a max access of read-only. This is
> >>something which cannot be specified by the user. To tell more about
> >>the dynamic entries I think by enabling NAT on an interface and
> >>running a network application using NAT, then dynamic NAT entries
> >>would be created. The same could be repeated for NAPT.
> >>
> >>natConfAddrMapEntryType OBJECT-TYPE
> >>    SYNTAX  INTEGER {
> >>                static (1),
> >>                dynamic (2)
> >>            }
> >>    MAX-ACCESS  read-only
> >>Thanks and Regards,
> >>Sam.
> >>
> >>--
> >> [ ]    Sam K. Sankoorikal.
> >>        Home Net Solutions ,
> >>        Wipro Technologies
> >>        Ganapa Complex,
> >>        #53/1 Hosur Rd Madivala,
> >>        Bangalore, India 560068
> >>        PBX:     +91 80 5502001 extn 3114
> >>        sam.kuruvilla@wipro.com
> >>
> >>                           Name: Wipro_Disclaimer.txt
> >>   Wipro_Disclaimer.txt    Type: Plain Text (text/plain)
> >>                       Encoding: 7bit
> >>
> >
>
>
>
>

_______________________________________________
nat mailing list
nat@ietf.org
https://www1.ietf.org/mailman/listinfo/nat



From nat-admin@ietf.org  Mon Dec  2 20:42:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21210
	for <nat-archive@lists.ietf.org>; Mon, 2 Dec 2002 20:42:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB31gav19313;
	Mon, 2 Dec 2002 20:42:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2IeFv22001
	for <nat@optimus.ietf.org>; Mon, 2 Dec 2002 13:40:15 -0500
Received: from india-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01641
	for <nat@ietf.org>; Mon, 2 Dec 2002 13:37:20 -0500 (EST)
Received: from cbin2-mira-01.cisco.com (localhost [127.0.0.1])
	by india-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gB308raU012028;
	Tue, 3 Dec 2002 00:08:54 GMT
Received: from cisco.com (rtp-vpn1-433.cisco.com [10.82.225.177])
	by cbin2-mira-01.cisco.com (Mirapoint)
	with ESMTP id AEP02868 (AUTH raraghun);
	Tue, 3 Dec 2002 00:02:40 +0530 (IST)
Message-ID: <3DEBA855.729A7342@cisco.com>
Date: Tue, 03 Dec 2002 00:07:09 +0530
From: Rajiv Raghunarayan <raraghun@cisco.com>
Organization: Cisco Systems Inc.
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: sam.kuruvilla@wipro.com
CC: Rohit.Rohit@worldwidepackets.com, nat@ietf.org
Subject: Re: [NAT] Clarification required
References: <Pine.GSO.4.44.0212021105210.27329-100000@cbin2-view1.cisco.com> <3DEB3747.6090200@wipro.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Sam,

"Sam K. Sankoorikal" wrote:
> 
>             Here it seems we are running into a loop. Does this again
> mean that based on what entries we have in the natAddrBindTable the
> value of natConfAddrMapEntryType is decided. 

No. Whether the entries in the Bind tables are static or dynamic
are decided by the value of natConfAddrMapEntryType.

-Rajiv.

> But I guess we already have
> natAddrBindType - to decide what types of NatAddrBindEntry are present
> there. Shouldn't it be that the Bind table uses the values in the
>  natConfAddrMapEntryType to decide what type of entry it must hold there??
> 
> Thanks for the clarification,
> Sam.
> 
> Rajiv Raghunarayan wrote:
> 
> >Hi Sam,
> >
> >As we've discussed below, a network admin specifies the address map in the
> >natConfAddrMapTable, and at the same time also determines whether this
> >needs to be a static map or a dynamic one. A simple rule for this could be
> >- if the no. of internal & external addresses is equal use static map,
> >else dynamic. And this could potentially be employed and the object
> >implemented as read-only by certain implementations. But this certainly
> >doesn't address all cases e.g. a customer might want to use dynamic map
> >inspite of equal internal & external addr. count. The mib definition would
> >need to account for all such cases too. Hence, the natConfAddrMapEntryType
> >is a read-create object.
> >
> >-Rajiv.
_______________________________________________
nat mailing list
nat@ietf.org
https://www1.ietf.org/mailman/listinfo/nat


From mailnull@www1.ietf.org  Mon Dec  2 20:45:31 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21280
	for <nat-archive@odin.ietf.org>; Mon, 2 Dec 2002 20:45:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB31lwI19600
	for nat-archive@odin.ietf.org; Mon, 2 Dec 2002 20:47:58 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB31gav19313;
	Mon, 2 Dec 2002 20:42:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB2IeFv22001
	for <nat@optimus.ietf.org>; Mon, 2 Dec 2002 13:40:15 -0500
Received: from india-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01641
	for <nat@ietf.org>; Mon, 2 Dec 2002 13:37:20 -0500 (EST)
Received: from cbin2-mira-01.cisco.com (localhost [127.0.0.1])
	by india-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gB308raU012028;
	Tue, 3 Dec 2002 00:08:54 GMT
Received: from cisco.com (rtp-vpn1-433.cisco.com [10.82.225.177])
	by cbin2-mira-01.cisco.com (Mirapoint)
	with ESMTP id AEP02868 (AUTH raraghun);
	Tue, 3 Dec 2002 00:02:40 +0530 (IST)
Message-ID: <3DEBA855.729A7342@cisco.com>
Date: Tue, 03 Dec 2002 00:07:09 +0530
From: Rajiv Raghunarayan <raraghun@cisco.com>
Organization: Cisco Systems Inc.
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: sam.kuruvilla@wipro.com
CC: Rohit.Rohit@worldwidepackets.com, nat@ietf.org
Subject: Re: [NAT] Clarification required
References: <Pine.GSO.4.44.0212021105210.27329-100000@cbin2-view1.cisco.com> <3DEB3747.6090200@wipro.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Sam,

"Sam K. Sankoorikal" wrote:
> 
>             Here it seems we are running into a loop. Does this again
> mean that based on what entries we have in the natAddrBindTable the
> value of natConfAddrMapEntryType is decided. 

No. Whether the entries in the Bind tables are static or dynamic
are decided by the value of natConfAddrMapEntryType.

-Rajiv.

> But I guess we already have
> natAddrBindType - to decide what types of NatAddrBindEntry are present
> there. Shouldn't it be that the Bind table uses the values in the
>  natConfAddrMapEntryType to decide what type of entry it must hold there??
> 
> Thanks for the clarification,
> Sam.
> 
> Rajiv Raghunarayan wrote:
> 
> >Hi Sam,
> >
> >As we've discussed below, a network admin specifies the address map in the
> >natConfAddrMapTable, and at the same time also determines whether this
> >needs to be a static map or a dynamic one. A simple rule for this could be
> >- if the no. of internal & external addresses is equal use static map,
> >else dynamic. And this could potentially be employed and the object
> >implemented as read-only by certain implementations. But this certainly
> >doesn't address all cases e.g. a customer might want to use dynamic map
> >inspite of equal internal & external addr. count. The mib definition would
> >need to account for all such cases too. Hence, the natConfAddrMapEntryType
> >is a read-create object.
> >
> >-Rajiv.
_______________________________________________
nat mailing list
nat@ietf.org
https://www1.ietf.org/mailman/listinfo/nat



From nat-admin@ietf.org  Mon Dec  9 11:09:36 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15492
	for <nat-archive@lists.ietf.org>; Mon, 9 Dec 2002 11:09:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB9G8Mv11539;
	Mon, 9 Dec 2002 11:08:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB9G1av10646
	for <nat@optimus.ietf.org>; Mon, 9 Dec 2002 11:01:36 -0500
Received: from wiprom2mx2.wipro.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15086
	for <nat@ietf.org>; Mon, 9 Dec 2002 10:58:38 -0500 (EST)
Received: from m2vwall5.wipro.com (m2vwall5.wipro.com [10.115.50.5])
	by wiprom2mx2.wipro.com (8.11.3/8.11.3) with SMTP id gB9G1Qb19288
	for <nat@ietf.org>; Mon, 9 Dec 2002 21:31:26 +0530 (IST)
Received: from blr-m3-msg.wipro.com ([10.114.50.99]) by blr-m1-bh1.wipro.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 9 Dec 2002 21:31:21 +0530
Received: from wipro.com ([10.114.5.250]) by blr-m3-msg.wipro.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 9 Dec 2002 21:31:20 +0530
Message-ID: <3DF4BEB8.2060207@wipro.com>
Date: Mon, 09 Dec 2002 21:33:04 +0530
From: "Sam K. Sankoorikal" <sam.kuruvilla@wipro.com>
Reply-To: sam.kuruvilla@wipro.com
Organization: Wipro Technologies
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: raraghun@cisco.com, nat@ietf.org
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-2e44710d-08aa-11d7-ba7f-006067005148"
X-OriginalArrivalTime: 09 Dec 2002 16:01:20.0987 (UTC) FILETIME=[373722B0:01C29F9C]
Subject: [NAT] Clarification reqd
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>


------=_NextPartTM-000-2e44710d-08aa-11d7-ba7f-006067005148
Content-Type: multipart/alternative;
	 boundary="------------030603070700010007060008"

--------------030603070700010007060008
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi Rajiv,

        I have a specific query on the natConfAddrMapName[Seems to a be 
a complex index]: Is there some convention[~default] to be followed when 
using this index while returning a row of this table?
        This a scenario where the natConfAddrMapName may not be have yet 
been given a name by any manager and NAT / NAPT is already enabled on an 
interface. As a result, there are rows already present in this table, 
based on mapping created on the fly by the NAT module, through some UI 
configuration. Is it OK/Safe if the Agent decides to use a name it finds 
convenient and thus be able to return to NAT mapping to any manager 
querying it ?

Some relate questions:

1. Does the agent also have to store the same value in the 
"natConfTable.natConfEntry.natConfAddrMapConfigName".?

2. Can a Manager change only 
natConfTable.natConfEntry.natConfAddrMapConfigName and what is the 
effect on the natConfAddrMapEntry.natConfAddrMapName. This leads to an 
inconsistent state in SNMP if left to the Manager.


Thanks and Regards,
Sam.

-- 
  Sam K. Sankoorikal.
  Home Net Solutions <http://www.wipro.com/homenet> ,
  Wipro Technologies <http://www.wipro.com>
  Ganapa Complex,
  #53/1 Hosur Rd Madivala,
  Bangalore, India 560068
  PBX:     +91 80 5502001 extn 3114
  sam.kuruvilla@wipro.com




--------------030603070700010007060008
Content-Type: multipart/related;
 boundary="------------040405040803020304080503"


--------------040405040803020304080503
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body>
Hi Rajiv,<br>
<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; I have a specific query on the natConfAddrMapName[Seems to a be a
complex index]: Is there some convention[~default] to be followed when using
this index while returning a row of this table?<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;This a scenario where the natConfAddrMapName may not be have yet
been given a name by any manager and NAT / NAPT is already enabled on an
interface. As a result, there are rows already present in this table, based
on mapping created on the fly by the NAT module, through some UI configuration.
Is it OK/Safe if the Agent decides to use a name it finds convenient and
thus be able to return to NAT mapping to any manager querying it ? <br>
<br>
Some relate questions:<br>
<br>
1. Does the agent also have to store the same value in the "natConfTable.natConfEntry.natConfAddrMapConfigName".?<br>
<br>
2. Can a Manager change only natConfTable.natConfEntry.natConfAddrMapConfigName
and what is the effect on the natConfAddrMapEntry.natConfAddrMapName. This
leads to an inconsistent state in SNMP if left to the Manager.<br>
<br>
<br>
Thanks and Regards,<br>
Sam.<br>
<br>
<div class="moz-signature">-- <br>
<title>signature</title>
                      
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
      
<table cellpadding="2" cellspacing="2" border="1" width="20%">
     <tbody>
       <tr>
         <td valign="top"><img
 src="cid:part1.06080500.01090906@wipro.com" alt=" " width="104"
 height="114" align="left">
         </td>
         <td valign="top" width="80%" bgcolor="#ccffff" nowrap="true">&nbsp; 
Sam K. Sankoorikal.<br>
   &nbsp;&nbsp;<a href="http://www.wipro.com/homenet">Home Net Solutions</a>   ,<br>
   &nbsp; <a href="http://www.wipro.com">Wipro Technologies</a><br>
     &nbsp; Ganapa Complex,<br>
     &nbsp; #53/1 Hosur Rd Madivala,<br>
     &nbsp; Bangalore, India 560068<br>
     &nbsp; PBX:&nbsp;&nbsp;&nbsp;&nbsp; +91 80 5502001 extn 3114<br>
 &nbsp; <a class="moz-txt-link-abbreviated" href="mailto:sam.kuruvilla@wipro.com">sam.kuruvilla@wipro.com</a><br>
         </td>
       </tr>
           
  </tbody>   
</table>
   <br>
     </div>
<br>
</body>
</html>

--------------040405040803020304080503
Content-Type: image/jpeg
Content-ID: <part1.06080500.01090906@wipro.com>
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRof
Hh0aHBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwh
MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAAR
CAByAGgDASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAA
AgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK
FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWG
h4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl
5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREA
AgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYk
NOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE
hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk
5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD3DFHp6UZ70UAFA+mKKytS8QWOlRiWdnaP
zfKd4l3eW2M4bHSplJRV2xSkoq7NX/PFR3FxDa273FxKsUMa7nkY4Cj1Ncnqvj3To7SePTZh
Ld4GzcpUEEcsD7V5+mrao0MmhPMZbGcAqhX5twbccHvknmuWrjIQ0WuhhPEJO0df8z1KHxIk
niybRvLAjRAFl3cmTGSuPTBrdV1bcFYEqcHB6GvM9Cguba782dt92CsocnO4gEVKb6cX32wS
GMBg8secZKknOfzH/wCqvHhn8edw5b69Ox3YfDVKiV+p6QevNHevPdJ8eQnVdTuNQuVS1EYe
KFTuOc4CqO5wea6Pw54rtvEj3CW1pcQiHBLSAbSD05HQ+1e9TrRna3U1q4KtSTlJaK2vqb/4
0Gj/AAo9ua2OQKKDRQAf5FFFHTpQBXvbyGwspruckRQqXYgZOPpXjviXVtO1LVTd2SzQNcgG
aOUABnHGQQcHjFd54w8SXWjN9lOnwT2txEQHlfO49CCo/wA815Jd+W0JVpRG45U9wfWvOxVT
mlyHm4yopSVMs+fCZYkywZjlG7cdj79sVBqGtw2OJrdg06MoADdQcg8+nf8ACsGGW4upHiYQ
+VnLPG5Jfpg45wQe/wBafdjT7e1WeXMSDOCECliO2CMdQP8AJxXO8PDmUZarsdWGw/KuZnT6
V47iW6sUuUkEMXmJK6jOVJ+Q9MniqEnioSwCMuyklnCn+EZOP0rz+fWrVh+5hmODwjvwOmTk
fSq8VwZpCY5Rvfna2cLx2OK1p5ThoS5oxs/+H/zPWoY2dF3Wp6AXztVcZYE8nG0eprp9F8ZX
ej28dpZCxhNxMGaa5yd2RgFjn5RwfWvPrO8llcxTnLsny5O1cAdCe3rx1rURWklXyo3llxgM
BwfcnnnI7Z6Yr3MDgY255ammOzCeJ02ij6WjJaJSzIxIBJXofp7UvpXmngnxrrEl3BpmtG3l
jbgXbvsYHnAOeGz26H616Z265rOpTlTdpHmKSlsHWijr9aKzGFISACT2HPelPH1pkwkaF1ic
JKVOxiuQDjgkUAeY+MfEOla55cNvbzPPbsfLuCdoIP3hjqRwPTpXDXdjG0bOibcLkusigL+B
HJ9q6/W9J1ePWjdapbx+dcPtEsC/u5MD25zj15qLUtLgXTHhMIdnVgQzEbseuPzr5rF4/wBj
XSlu/l+pyUMPUrVHN/lY421jjt7RnzHtUb96gKP8Oa5O6eXVL9pvNZhksFZsjknn8jXTX900
NjsAJWRSfmzgdskfjXOWS7/nY9tuD1x7+terhYNc1SW7PUUPhi+pXl0hbggv8pGehpIdNitS
WQEyAY+bnn+lasrGFioxu6k+lQAF3AHLMf1r2KNByXNMxquCdolYFgpGdmD09TXomlx20OkQ
XUxUl0DYY8Zx6frXBGMPG2AucE5I+6fU+tdNBczPYW8TgoEjC7On5114SLjOUXscGLm1C0ep
tWGqIus2huooJrQSqJI/ILqwOB93qcdvp+Fe7ggqCDxjjivB/CsN7N4gtzp9na3VzH+8RLo4
QY756gj1HNe7xlzGpkChiAWCnIB789xWWOfvIMGrJjjRRmiuE7AGfTmj60f56UfSgDmPEcs9
xcpbMDHbRnzNx/iYDrn0Gen+Fcpq15bW1sXUpI6glV6A9sZ6j+VeoOiSLtdQ6jsRnmvEfFXn
Xeu6hNbRz3FtCzHzBFhFUcHBAxjpXzmMyl1MV7ec7p9P66HrZYqc5NS0S6nEasG+1SMzYVjn
KDA9ePx5rKgUxTM4B2/w56iulvLANF510OUxhAf/ANfcgVizWsjq0wj2IOPlP3RxX0mDoTlB
NLRHLjlFVWqeyIdxkYHDFmPock1aS0MZ3XGUAONmMs3tj8DzRY2d1eSYtkkaXsRxn15JFaX9
nPbXCLLswqFSoOevr69/SvVhGTPJq1Yx0uUkt0ublFjB8lBzn65xn8a1aAqoMKoA9hV/SNOX
VdSjszeW9s8nEbThirN2Xj1rdRUFqzinNzaRreE/D0mqanaTSLdi1LkC6s3Aa3lAyN3dQenT
nP1r2xFZY0VmLkAAsRgk+vFY+jeFNJ0K4e5sbd45pE2OfNdhjrwCfWtqvJr1vaSutj0aFN04
2e4H6UUUVgbBR39arXupWOmxLLf31vaRs21XuJVjBb0BYjmm2WqadqW/7Bf2l3s+/wDZ51k2
56Z2k4oAt+wrn/GltNc+FrtYHRSmJX3kgFV5I478CtxbmB7iS3SeNp4wGeNWG5QehI6jOD1r
OvL7QtTjn0m41KykM2YJLdbpQ5J4K4ByD7daFbqCbWqPntJZbqVVlJYKx4MfAbPQ89fYdvWl
37i8UW6WVYy5OMnoMZyO2c59PrXq+reG/DmsDSdP0rV9Ms7e2lcmKCZHkctj7vJy3HU5rZl0
jwtZadc6RbzadZzG2a2JaVBKqnn5snPU55r0frcFFKKCUnZ2PLNNiMGkwGGIvNLhEjBJLZPQ
e/4dqyZm813Y8ZbdjPTmvU/C2gaZot7FNc67p10bddtqqSqME/xkE9cHAA6ZqSXwVocVlqdt
e3ttFNeTNPbTllV4E/hAyeQDnPY1p9cglynmvDVJS5+p59ZeG728fTcGOOLUd628zH5d67vk
PoTt/wA816H4Y8AafBptvPrOnrJqQcyHdIWEeDwBg4PQH61u6PFo+kaLZaal9ZypaoArNInL
Dq3Xgkkn8a2UdJIw6OrqejKcg1yVcTKWkdEdVPDxjq9R3vR160ySSOJC8rqid2ZgB+tNiube
4z5E8UuOvluGx+Vcp0Epoo/nRQBU1PTLPWdOn0+/gSa2nQo6Oobj1GehHUH1FfNngq9uPhr8
Wm0u+bbbvN9iuC2QCjEbJO3H3Tn0Jr6e/wA8V4t8bvA19q1/putaNZTXN1IRaXCQoS2f+Wb8
dAOQT24oA5fQPEWpeEPjhf8A9uyMWvbpra8bJC7XYGNwP7o+Uj/Zrttc0ax8TfHbTraC0hRN
Ht1u7+aNADJJu3IrEdeq9fesH4ueA9UfStC1mGOe/wBSito7PUGgjLNIyrkSYHPXIJ/3a7n4
S6BqOnaBc6vrgmOs6tL5s5nGJAijCA5/E/iKAPIPFMEUPx9ZIIUiQ6pAQsa4GTtJOPUnn6mu
g/aJtoYtY0S5jhiSaaGYSSKoDPtK4ye+M8VmeNrG/wBN+N76rLpt7JaJeQXIkhgZwyALkjHX
ofyrY+OsE2uf8I7qml29xdWUsEoWWOFjgllwCMZBPofQ0AQ+LNG8DaV8JrFBHZxeIZLWCWLy
zm4d2ALFh12kbuo9MVkanp+op8ArS41mBjKuqqLBp1PmRwMhyATyFJBIHTGK9g8AWfh/UvDV
heJpdq2pQwRQXck9kFmWVUUEEsufTBHFZ3xws7q9+HQS0tpZ2jvYnZYlLFVCuM4HbJA/GgDh
fBGh+Bx8J7jUfEqWSXNxJOI5ppNsvyjCiPv154B5NW/gTPqdhp+uX919oGhRQ+Yu/OwyLkts
zxnA5x7UfD/wvoXjD4d3Ghaha+XrtuZWilliZJIVJyhViOV3E5H1rM+GuuXXhW91Twp4qgu4
NIug8LyPG2y2k5BOcYCtnr64NAC+DoLz4xeN7268SXUr6ZaR+b9ijlKoMnCIB2Hcnqce9avx
R8E2XgfT7PxN4Te40qeGdYpRBM2CDkhhk+owRnBB6VmeFU1X4O+M7qPWNOubjR7tPK+22sRc
FQco4/PlTzz376PxK8YD4g2lp4b8I2N9fFpxLPKIGVcgEBefrkk4HAoA9M+Hfiabxd4Ks9Uu
VAustDPtGAXU4JA9wQfxoqTwB4Yfwh4MstJmdXuV3S3DIfl8xjkgH0HA/CigDpx1AArjrPxg
954zjsYtv9lSCe3ik8pgZJ4grFg/3ShHmKAMklCeldfgEEEZGOaozaPZSadDYx28UMdspFrs
jGLc7CgZB0BCsQPrQBztv8QI20eXULnTLi3J0+fUrVCwbz4I2wDxypO5Dgj+LjOKkufF0/kx
2q2RtdY+12lvJbTMHCiUbyQynn5Ekx0OQMip18DaNF4ebR7eERJJBFbTzhQZZYkIJQk9A2Dx
0G44rUg0DTLOJVs7KGBo5TPE+zcVlKFN/J5ODjntxQBl23jix1GO3/s0yt58trGHaPKh5vm8
s4PDqgJb+7kZ9Kjg+IGlSWzXbQ3sNs1m97FI8Q/exK4QkAEnqy4zjIOfWtLS/DWm6Zp1laLC
s7WjtMs0gG9pnDB5Djjc25vpnAqDV/COn6josmnWyR2O62SzWWOPcRArBvK6j5Tgjgg89aAJ
NJ1yTxHZ3zWUMtpNDM1sJLlVdTIAMkbWwwGfWuetPE+vDQodXlks7pbvUFsrWCG3ZXkU3Gzf
ncckxq7Y6D1wK6vQtMk0fS0spL2S6KOxV3ULtUnIQAdh0GSTUkWkadBbWVtFZwpDYuJLWMDi
JgGAK++GYfiaAMibxtp8dmZltb15FFw0sCRgvGtuxSVmOcYDcDBOe2asp4r0qYPsaV1Fxb2o
IiOHkmVWQD/gLgn0FPn8KaFc20VtLpsRhiEiqqsy/K7bnU4PzKzckHINSN4b0d9SGoGxj+1i
VZhJk4EirsD7c7cheOnQCgDA1L4hWKWWpiwgmmuLazluYTLH+6kKP5Y755kwoGMntVx/GNtb
xCJNNvXu/t0djJbRxKG8xoxJnk8gIS3rxg4qvoPgWPS4Lm1vbw39pcMkjwvFtDyrL5vmsck5
LYO0ccVtXPhzS7olntyrtd/bfMjkZG84rsLZB7r8uOmKANX3ooNFAAOlA5UUUUAA6D6UYHpR
RQAH7p+lH8R+lFFAC0n8R+lFFAA3Q/SkHb6UUUAKOp+tIO30oooAX+I0UUUAf//Z
--------------040405040803020304080503--

--------------030603070700010007060008--


------=_NextPartTM-000-2e44710d-08aa-11d7-ba7f-006067005148--

_______________________________________________
nat mailing list
nat@ietf.org
https://www1.ietf.org/mailman/listinfo/nat


From mailnull@www1.ietf.org  Mon Dec  9 11:55:28 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15491
	for <nat-archive@odin.ietf.org>; Mon, 9 Dec 2002 11:09:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB9GC2R11757
	for nat-archive@odin.ietf.org; Mon, 9 Dec 2002 11:12:02 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB9G8Mv11539;
	Mon, 9 Dec 2002 11:08:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB9G1av10646
	for <nat@optimus.ietf.org>; Mon, 9 Dec 2002 11:01:36 -0500
Received: from wiprom2mx2.wipro.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15086
	for <nat@ietf.org>; Mon, 9 Dec 2002 10:58:38 -0500 (EST)
Received: from m2vwall5.wipro.com (m2vwall5.wipro.com [10.115.50.5])
	by wiprom2mx2.wipro.com (8.11.3/8.11.3) with SMTP id gB9G1Qb19288
	for <nat@ietf.org>; Mon, 9 Dec 2002 21:31:26 +0530 (IST)
Received: from blr-m3-msg.wipro.com ([10.114.50.99]) by blr-m1-bh1.wipro.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 9 Dec 2002 21:31:21 +0530
Received: from wipro.com ([10.114.5.250]) by blr-m3-msg.wipro.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 9 Dec 2002 21:31:20 +0530
Message-ID: <3DF4BEB8.2060207@wipro.com>
Date: Mon, 09 Dec 2002 21:33:04 +0530
From: "Sam K. Sankoorikal" <sam.kuruvilla@wipro.com>
Reply-To: sam.kuruvilla@wipro.com
Organization: Wipro Technologies
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: raraghun@cisco.com, nat@ietf.org
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-2e44710d-08aa-11d7-ba7f-006067005148"
X-OriginalArrivalTime: 09 Dec 2002 16:01:20.0987 (UTC) FILETIME=[373722B0:01C29F9C]
Subject: [NAT] Clarification reqd
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>


------=_NextPartTM-000-2e44710d-08aa-11d7-ba7f-006067005148
Content-Type: multipart/alternative;
	 boundary="------------030603070700010007060008"

--------------030603070700010007060008
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi Rajiv,

        I have a specific query on the natConfAddrMapName[Seems to a be 
a complex index]: Is there some convention[~default] to be followed when 
using this index while returning a row of this table?
        This a scenario where the natConfAddrMapName may not be have yet 
been given a name by any manager and NAT / NAPT is already enabled on an 
interface. As a result, there are rows already present in this table, 
based on mapping created on the fly by the NAT module, through some UI 
configuration. Is it OK/Safe if the Agent decides to use a name it finds 
convenient and thus be able to return to NAT mapping to any manager 
querying it ?

Some relate questions:

1. Does the agent also have to store the same value in the 
"natConfTable.natConfEntry.natConfAddrMapConfigName".?

2. Can a Manager change only 
natConfTable.natConfEntry.natConfAddrMapConfigName and what is the 
effect on the natConfAddrMapEntry.natConfAddrMapName. This leads to an 
inconsistent state in SNMP if left to the Manager.


Thanks and Regards,
Sam.

-- 
  Sam K. Sankoorikal.
  Home Net Solutions <http://www.wipro.com/homenet> ,
  Wipro Technologies <http://www.wipro.com>
  Ganapa Complex,
  #53/1 Hosur Rd Madivala,
  Bangalore, India 560068
  PBX:     +91 80 5502001 extn 3114
  sam.kuruvilla@wipro.com




--------------030603070700010007060008
Content-Type: multipart/related;
 boundary="------------040405040803020304080503"


--------------040405040803020304080503
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body>
Hi Rajiv,<br>
<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; I have a specific query on the natConfAddrMapName[Seems to a be a
complex index]: Is there some convention[~default] to be followed when using
this index while returning a row of this table?<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; &nbsp;This a scenario where the natConfAddrMapName may not be have yet
been given a name by any manager and NAT / NAPT is already enabled on an
interface. As a result, there are rows already present in this table, based
on mapping created on the fly by the NAT module, through some UI configuration.
Is it OK/Safe if the Agent decides to use a name it finds convenient and
thus be able to return to NAT mapping to any manager querying it ? <br>
<br>
Some relate questions:<br>
<br>
1. Does the agent also have to store the same value in the "natConfTable.natConfEntry.natConfAddrMapConfigName".?<br>
<br>
2. Can a Manager change only natConfTable.natConfEntry.natConfAddrMapConfigName
and what is the effect on the natConfAddrMapEntry.natConfAddrMapName. This
leads to an inconsistent state in SNMP if left to the Manager.<br>
<br>
<br>
Thanks and Regards,<br>
Sam.<br>
<br>
<div class="moz-signature">-- <br>
<title>signature</title>
                      
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
      
<table cellpadding="2" cellspacing="2" border="1" width="20%">
     <tbody>
       <tr>
         <td valign="top"><img
 src="cid:part1.06080500.01090906@wipro.com" alt=" " width="104"
 height="114" align="left">
         </td>
         <td valign="top" width="80%" bgcolor="#ccffff" nowrap="true">&nbsp; 
Sam K. Sankoorikal.<br>
   &nbsp;&nbsp;<a href="http://www.wipro.com/homenet">Home Net Solutions</a>   ,<br>
   &nbsp; <a href="http://www.wipro.com">Wipro Technologies</a><br>
     &nbsp; Ganapa Complex,<br>
     &nbsp; #53/1 Hosur Rd Madivala,<br>
     &nbsp; Bangalore, India 560068<br>
     &nbsp; PBX:&nbsp;&nbsp;&nbsp;&nbsp; +91 80 5502001 extn 3114<br>
 &nbsp; <a class="moz-txt-link-abbreviated" href="mailto:sam.kuruvilla@wipro.com">sam.kuruvilla@wipro.com</a><br>
         </td>
       </tr>
           
  </tbody>   
</table>
   <br>
     </div>
<br>
</body>
</html>

--------------040405040803020304080503
Content-Type: image/jpeg
Content-ID: <part1.06080500.01090906@wipro.com>
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRof
Hh0aHBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwh
MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAAR
CAByAGgDASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAA
AgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK
FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWG
h4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl
5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREA
AgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYk
NOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE
hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk
5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD3DFHp6UZ70UAFA+mKKytS8QWOlRiWdnaP
zfKd4l3eW2M4bHSplJRV2xSkoq7NX/PFR3FxDa273FxKsUMa7nkY4Cj1Ncnqvj3To7SePTZh
Ld4GzcpUEEcsD7V5+mrao0MmhPMZbGcAqhX5twbccHvknmuWrjIQ0WuhhPEJO0df8z1KHxIk
niybRvLAjRAFl3cmTGSuPTBrdV1bcFYEqcHB6GvM9Cguba782dt92CsocnO4gEVKb6cX32wS
GMBg8secZKknOfzH/wCqvHhn8edw5b69Ox3YfDVKiV+p6QevNHevPdJ8eQnVdTuNQuVS1EYe
KFTuOc4CqO5wea6Pw54rtvEj3CW1pcQiHBLSAbSD05HQ+1e9TrRna3U1q4KtSTlJaK2vqb/4
0Gj/AAo9ua2OQKKDRQAf5FFFHTpQBXvbyGwspruckRQqXYgZOPpXjviXVtO1LVTd2SzQNcgG
aOUABnHGQQcHjFd54w8SXWjN9lOnwT2txEQHlfO49CCo/wA815Jd+W0JVpRG45U9wfWvOxVT
mlyHm4yopSVMs+fCZYkywZjlG7cdj79sVBqGtw2OJrdg06MoADdQcg8+nf8ACsGGW4upHiYQ
+VnLPG5Jfpg45wQe/wBafdjT7e1WeXMSDOCECliO2CMdQP8AJxXO8PDmUZarsdWGw/KuZnT6
V47iW6sUuUkEMXmJK6jOVJ+Q9MniqEnioSwCMuyklnCn+EZOP0rz+fWrVh+5hmODwjvwOmTk
fSq8VwZpCY5Rvfna2cLx2OK1p5ThoS5oxs/+H/zPWoY2dF3Wp6AXztVcZYE8nG0eprp9F8ZX
ej28dpZCxhNxMGaa5yd2RgFjn5RwfWvPrO8llcxTnLsny5O1cAdCe3rx1rURWklXyo3llxgM
BwfcnnnI7Z6Yr3MDgY255ammOzCeJ02ij6WjJaJSzIxIBJXofp7UvpXmngnxrrEl3BpmtG3l
jbgXbvsYHnAOeGz26H616Z265rOpTlTdpHmKSlsHWijr9aKzGFISACT2HPelPH1pkwkaF1ic
JKVOxiuQDjgkUAeY+MfEOla55cNvbzPPbsfLuCdoIP3hjqRwPTpXDXdjG0bOibcLkusigL+B
HJ9q6/W9J1ePWjdapbx+dcPtEsC/u5MD25zj15qLUtLgXTHhMIdnVgQzEbseuPzr5rF4/wBj
XSlu/l+pyUMPUrVHN/lY421jjt7RnzHtUb96gKP8Oa5O6eXVL9pvNZhksFZsjknn8jXTX900
NjsAJWRSfmzgdskfjXOWS7/nY9tuD1x7+terhYNc1SW7PUUPhi+pXl0hbggv8pGehpIdNitS
WQEyAY+bnn+lasrGFioxu6k+lQAF3AHLMf1r2KNByXNMxquCdolYFgpGdmD09TXomlx20OkQ
XUxUl0DYY8Zx6frXBGMPG2AucE5I+6fU+tdNBczPYW8TgoEjC7On5114SLjOUXscGLm1C0ep
tWGqIus2huooJrQSqJI/ILqwOB93qcdvp+Fe7ggqCDxjjivB/CsN7N4gtzp9na3VzH+8RLo4
QY756gj1HNe7xlzGpkChiAWCnIB789xWWOfvIMGrJjjRRmiuE7AGfTmj60f56UfSgDmPEcs9
xcpbMDHbRnzNx/iYDrn0Gen+Fcpq15bW1sXUpI6glV6A9sZ6j+VeoOiSLtdQ6jsRnmvEfFXn
Xeu6hNbRz3FtCzHzBFhFUcHBAxjpXzmMyl1MV7ec7p9P66HrZYqc5NS0S6nEasG+1SMzYVjn
KDA9ePx5rKgUxTM4B2/w56iulvLANF510OUxhAf/ANfcgVizWsjq0wj2IOPlP3RxX0mDoTlB
NLRHLjlFVWqeyIdxkYHDFmPock1aS0MZ3XGUAONmMs3tj8DzRY2d1eSYtkkaXsRxn15JFaX9
nPbXCLLswqFSoOevr69/SvVhGTPJq1Yx0uUkt0ublFjB8lBzn65xn8a1aAqoMKoA9hV/SNOX
VdSjszeW9s8nEbThirN2Xj1rdRUFqzinNzaRreE/D0mqanaTSLdi1LkC6s3Aa3lAyN3dQenT
nP1r2xFZY0VmLkAAsRgk+vFY+jeFNJ0K4e5sbd45pE2OfNdhjrwCfWtqvJr1vaSutj0aFN04
2e4H6UUUVgbBR39arXupWOmxLLf31vaRs21XuJVjBb0BYjmm2WqadqW/7Bf2l3s+/wDZ51k2
56Z2k4oAt+wrn/GltNc+FrtYHRSmJX3kgFV5I478CtxbmB7iS3SeNp4wGeNWG5QehI6jOD1r
OvL7QtTjn0m41KykM2YJLdbpQ5J4K4ByD7daFbqCbWqPntJZbqVVlJYKx4MfAbPQ89fYdvWl
37i8UW6WVYy5OMnoMZyO2c59PrXq+reG/DmsDSdP0rV9Ms7e2lcmKCZHkctj7vJy3HU5rZl0
jwtZadc6RbzadZzG2a2JaVBKqnn5snPU55r0frcFFKKCUnZ2PLNNiMGkwGGIvNLhEjBJLZPQ
e/4dqyZm813Y8ZbdjPTmvU/C2gaZot7FNc67p10bddtqqSqME/xkE9cHAA6ZqSXwVocVlqdt
e3ttFNeTNPbTllV4E/hAyeQDnPY1p9cglynmvDVJS5+p59ZeG728fTcGOOLUd628zH5d67vk
PoTt/wA816H4Y8AafBptvPrOnrJqQcyHdIWEeDwBg4PQH61u6PFo+kaLZaal9ZypaoArNInL
Dq3Xgkkn8a2UdJIw6OrqejKcg1yVcTKWkdEdVPDxjq9R3vR160ySSOJC8rqid2ZgB+tNiube
4z5E8UuOvluGx+Vcp0Epoo/nRQBU1PTLPWdOn0+/gSa2nQo6Oobj1GehHUH1FfNngq9uPhr8
Wm0u+bbbvN9iuC2QCjEbJO3H3Tn0Jr6e/wA8V4t8bvA19q1/putaNZTXN1IRaXCQoS2f+Wb8
dAOQT24oA5fQPEWpeEPjhf8A9uyMWvbpra8bJC7XYGNwP7o+Uj/Zrttc0ax8TfHbTraC0hRN
Ht1u7+aNADJJu3IrEdeq9fesH4ueA9UfStC1mGOe/wBSito7PUGgjLNIyrkSYHPXIJ/3a7n4
S6BqOnaBc6vrgmOs6tL5s5nGJAijCA5/E/iKAPIPFMEUPx9ZIIUiQ6pAQsa4GTtJOPUnn6mu
g/aJtoYtY0S5jhiSaaGYSSKoDPtK4ye+M8VmeNrG/wBN+N76rLpt7JaJeQXIkhgZwyALkjHX
ofyrY+OsE2uf8I7qml29xdWUsEoWWOFjgllwCMZBPofQ0AQ+LNG8DaV8JrFBHZxeIZLWCWLy
zm4d2ALFh12kbuo9MVkanp+op8ArS41mBjKuqqLBp1PmRwMhyATyFJBIHTGK9g8AWfh/UvDV
heJpdq2pQwRQXck9kFmWVUUEEsufTBHFZ3xws7q9+HQS0tpZ2jvYnZYlLFVCuM4HbJA/GgDh
fBGh+Bx8J7jUfEqWSXNxJOI5ppNsvyjCiPv154B5NW/gTPqdhp+uX919oGhRQ+Yu/OwyLkts
zxnA5x7UfD/wvoXjD4d3Ghaha+XrtuZWilliZJIVJyhViOV3E5H1rM+GuuXXhW91Twp4qgu4
NIug8LyPG2y2k5BOcYCtnr64NAC+DoLz4xeN7268SXUr6ZaR+b9ijlKoMnCIB2Hcnqce9avx
R8E2XgfT7PxN4Te40qeGdYpRBM2CDkhhk+owRnBB6VmeFU1X4O+M7qPWNOubjR7tPK+22sRc
FQco4/PlTzz376PxK8YD4g2lp4b8I2N9fFpxLPKIGVcgEBefrkk4HAoA9M+Hfiabxd4Ks9Uu
VAustDPtGAXU4JA9wQfxoqTwB4Yfwh4MstJmdXuV3S3DIfl8xjkgH0HA/CigDpx1AArjrPxg
954zjsYtv9lSCe3ik8pgZJ4grFg/3ShHmKAMklCeldfgEEEZGOaozaPZSadDYx28UMdspFrs
jGLc7CgZB0BCsQPrQBztv8QI20eXULnTLi3J0+fUrVCwbz4I2wDxypO5Dgj+LjOKkufF0/kx
2q2RtdY+12lvJbTMHCiUbyQynn5Ekx0OQMip18DaNF4ebR7eERJJBFbTzhQZZYkIJQk9A2Dx
0G44rUg0DTLOJVs7KGBo5TPE+zcVlKFN/J5ODjntxQBl23jix1GO3/s0yt58trGHaPKh5vm8
s4PDqgJb+7kZ9Kjg+IGlSWzXbQ3sNs1m97FI8Q/exK4QkAEnqy4zjIOfWtLS/DWm6Zp1laLC
s7WjtMs0gG9pnDB5Djjc25vpnAqDV/COn6josmnWyR2O62SzWWOPcRArBvK6j5Tgjgg89aAJ
NJ1yTxHZ3zWUMtpNDM1sJLlVdTIAMkbWwwGfWuetPE+vDQodXlks7pbvUFsrWCG3ZXkU3Gzf
ncckxq7Y6D1wK6vQtMk0fS0spL2S6KOxV3ULtUnIQAdh0GSTUkWkadBbWVtFZwpDYuJLWMDi
JgGAK++GYfiaAMibxtp8dmZltb15FFw0sCRgvGtuxSVmOcYDcDBOe2asp4r0qYPsaV1Fxb2o
IiOHkmVWQD/gLgn0FPn8KaFc20VtLpsRhiEiqqsy/K7bnU4PzKzckHINSN4b0d9SGoGxj+1i
VZhJk4EirsD7c7cheOnQCgDA1L4hWKWWpiwgmmuLazluYTLH+6kKP5Y755kwoGMntVx/GNtb
xCJNNvXu/t0djJbRxKG8xoxJnk8gIS3rxg4qvoPgWPS4Lm1vbw39pcMkjwvFtDyrL5vmsck5
LYO0ccVtXPhzS7olntyrtd/bfMjkZG84rsLZB7r8uOmKANX3ooNFAAOlA5UUUUAA6D6UYHpR
RQAH7p+lH8R+lFFAC0n8R+lFFAA3Q/SkHb6UUUAKOp+tIO30oooAX+I0UUUAf//Z
--------------040405040803020304080503--

--------------030603070700010007060008--


------=_NextPartTM-000-2e44710d-08aa-11d7-ba7f-006067005148--

_______________________________________________
nat mailing list
nat@ietf.org
https://www1.ietf.org/mailman/listinfo/nat



From mailnull@www1.ietf.org  Wed Dec 11 02:46:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28310
	for <nat-archive@odin.ietf.org>; Wed, 11 Dec 2002 02:46:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBB7n1f07889
	for nat-archive@odin.ietf.org; Wed, 11 Dec 2002 02:49:01 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBB7hUv07790;
	Wed, 11 Dec 2002 02:43:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBB7dQv07653
	for <nat@optimus.ietf.org>; Wed, 11 Dec 2002 02:39:26 -0500
Received: from wiprom2mx2.wipro.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28107
	for <nat@ietf.org>; Wed, 11 Dec 2002 02:36:18 -0500 (EST)
Received: from m2vwall5.wipro.com (m2vwall5.wipro.com [10.115.50.5])
	by wiprom2mx2.wipro.com (8.11.3/8.11.3) with SMTP id gBB7d6b29326
	for <nat@ietf.org>; Wed, 11 Dec 2002 13:09:06 +0530 (IST)
Received: from blr-m3-msg.wipro.com ([10.114.50.99]) by blr-m1-bh2.wipro.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 11 Dec 2002 13:09:01 +0530
Received: from wipro.com ([10.114.5.250]) by blr-m3-msg.wipro.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Wed, 11 Dec 2002 13:09:01 +0530
Message-ID: <3DF6EC03.50807@wipro.com>
Date: Wed, 11 Dec 2002 13:10:51 +0530
From: "Sam K. Sankoorikal" <sam.kuruvilla@wipro.com>
Reply-To: sam.kuruvilla@wipro.com
Organization: Wipro Technologies
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: raraghun@cisco.com, nat@ietf.org
Subject: Re: [NAT] Clarification reqd
References: <3DF4BEB8.2060207@wipro.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Dec 2002 07:39:01.0328 (UTC) FILETIME=[5F67A500:01C2A0E8]
Content-Transfer-Encoding: 7bit
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi ,

        I think I mixed up things in my previous mail. I'll try to frame 
it better:* *I have refered to * DEFVAL *as defined in RFC1212. 


        Now consider the following scenario:

                        The natConfTable is used to enable NAT on the 
eth0. This is done by using the DEFVAL of ' 'H for the 
natConfAddrMapName while creating that row. Now if a snmpwalk is 
performed on the natConfAddrMapTable, even with just the "default index 
value" mapping rows can be returned. The returned entries are now 
returned with primary index as ' 'H and secondary index as the value of 
natConfAddrMapIndex( 1 .. 2147483647).
                        Now here is the problem I see: Repeat the above 
steps for eth1.  ie Enable  NAT for eth1(Here also  natConfAddrMapName 
is specified as the DEFVAL). Now if a walk is performed on the 
natConfAddrMapTable there will be a problem in retuning the rows, as 
sorting based on the primary index and secondary index will not be 
possible. ie there could be two entries for each  The problem originated 
since the DEFVAL clause does not seem to provide a correct default. 
Ofcourse the user should have the understanding to use unique values for 
each entry created in the natConfTable. Please let me know your views on 
this and if the scenario is valid, a possible solution for the same.

                        An associated problem with the 
natConfTable.natConfEntry.natConfAddrMapConfigName is that. This table 
decides the Index for the natConfAddrMapTable. Now, assuming that the 
two tables are tightly tied up, any change in the 
natConfTable.natConfEntry.natConfAddrMapConfigName  in the first table 
will result in changes in the second table. I dont believe this is a 
consistent thing to do. Why can't the index be predecided when we know 
that the index is just to indicate to the Manager the interface to which 
the mapping belongs. The primary index in the natConfAddrMapTable could 
be the primary index of the natConfTable. Is there any other purpose in 
having it as a string ? Please highlight the purpose/advantages in 
having it as a string.


Thanks and Regards,
Sam

Sam K. Sankoorikal wrote:

> Hi Rajiv,
>
>         I have a specific query on the natConfAddrMapName[Seems to a 
> be a complex index]: Is there some convention[~default] to be followed 
> when using this index while returning a row of this table?
>         This a scenario where the natConfAddrMapName may not be have 
> yet been given a name by any manager and NAT / NAPT is already enabled 
> on an interface. As a result, there are rows already present in this 
> table, based on mapping created on the fly by the NAT module, through 
> some UI configuration. Is it OK/Safe if the Agent decides to use a 
> name it finds convenient and thus be able to return to NAT mapping to 
> any manager querying it ?
>
> Some relate questions:
>
> 1. Does the agent also have to store the same value in the 
> "natConfTable.natConfEntry.natConfAddrMapConfigName".?
>
> 2. Can a Manager change only 
> natConfTable.natConfEntry.natConfAddrMapConfigName and what is the 
> effect on the natConfAddrMapEntry.natConfAddrMapName. This leads to an 
> inconsistent state in SNMP if left to the Manager.
>
>
> Thanks and Regards,
> Sam.
>


_______________________________________________
nat mailing list
nat@ietf.org
https://www1.ietf.org/mailman/listinfo/nat



From nat-admin@ietf.org  Wed Dec 11 03:40:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28311
	for <nat-archive@lists.ietf.org>; Wed, 11 Dec 2002 02:46:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBB7hUv07790;
	Wed, 11 Dec 2002 02:43:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBB7dQv07653
	for <nat@optimus.ietf.org>; Wed, 11 Dec 2002 02:39:26 -0500
Received: from wiprom2mx2.wipro.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28107
	for <nat@ietf.org>; Wed, 11 Dec 2002 02:36:18 -0500 (EST)
Received: from m2vwall5.wipro.com (m2vwall5.wipro.com [10.115.50.5])
	by wiprom2mx2.wipro.com (8.11.3/8.11.3) with SMTP id gBB7d6b29326
	for <nat@ietf.org>; Wed, 11 Dec 2002 13:09:06 +0530 (IST)
Received: from blr-m3-msg.wipro.com ([10.114.50.99]) by blr-m1-bh2.wipro.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 11 Dec 2002 13:09:01 +0530
Received: from wipro.com ([10.114.5.250]) by blr-m3-msg.wipro.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Wed, 11 Dec 2002 13:09:01 +0530
Message-ID: <3DF6EC03.50807@wipro.com>
Date: Wed, 11 Dec 2002 13:10:51 +0530
From: "Sam K. Sankoorikal" <sam.kuruvilla@wipro.com>
Reply-To: sam.kuruvilla@wipro.com
Organization: Wipro Technologies
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: raraghun@cisco.com, nat@ietf.org
Subject: Re: [NAT] Clarification reqd
References: <3DF4BEB8.2060207@wipro.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Dec 2002 07:39:01.0328 (UTC) FILETIME=[5F67A500:01C2A0E8]
Content-Transfer-Encoding: 7bit
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi ,

        I think I mixed up things in my previous mail. I'll try to frame 
it better:* *I have refered to * DEFVAL *as defined in RFC1212. 


        Now consider the following scenario:

                        The natConfTable is used to enable NAT on the 
eth0. This is done by using the DEFVAL of ' 'H for the 
natConfAddrMapName while creating that row. Now if a snmpwalk is 
performed on the natConfAddrMapTable, even with just the "default index 
value" mapping rows can be returned. The returned entries are now 
returned with primary index as ' 'H and secondary index as the value of 
natConfAddrMapIndex( 1 .. 2147483647).
                        Now here is the problem I see: Repeat the above 
steps for eth1.  ie Enable  NAT for eth1(Here also  natConfAddrMapName 
is specified as the DEFVAL). Now if a walk is performed on the 
natConfAddrMapTable there will be a problem in retuning the rows, as 
sorting based on the primary index and secondary index will not be 
possible. ie there could be two entries for each  The problem originated 
since the DEFVAL clause does not seem to provide a correct default. 
Ofcourse the user should have the understanding to use unique values for 
each entry created in the natConfTable. Please let me know your views on 
this and if the scenario is valid, a possible solution for the same.

                        An associated problem with the 
natConfTable.natConfEntry.natConfAddrMapConfigName is that. This table 
decides the Index for the natConfAddrMapTable. Now, assuming that the 
two tables are tightly tied up, any change in the 
natConfTable.natConfEntry.natConfAddrMapConfigName  in the first table 
will result in changes in the second table. I dont believe this is a 
consistent thing to do. Why can't the index be predecided when we know 
that the index is just to indicate to the Manager the interface to which 
the mapping belongs. The primary index in the natConfAddrMapTable could 
be the primary index of the natConfTable. Is there any other purpose in 
having it as a string ? Please highlight the purpose/advantages in 
having it as a string.


Thanks and Regards,
Sam

Sam K. Sankoorikal wrote:

> Hi Rajiv,
>
>         I have a specific query on the natConfAddrMapName[Seems to a 
> be a complex index]: Is there some convention[~default] to be followed 
> when using this index while returning a row of this table?
>         This a scenario where the natConfAddrMapName may not be have 
> yet been given a name by any manager and NAT / NAPT is already enabled 
> on an interface. As a result, there are rows already present in this 
> table, based on mapping created on the fly by the NAT module, through 
> some UI configuration. Is it OK/Safe if the Agent decides to use a 
> name it finds convenient and thus be able to return to NAT mapping to 
> any manager querying it ?
>
> Some relate questions:
>
> 1. Does the agent also have to store the same value in the 
> "natConfTable.natConfEntry.natConfAddrMapConfigName".?
>
> 2. Can a Manager change only 
> natConfTable.natConfEntry.natConfAddrMapConfigName and what is the 
> effect on the natConfAddrMapEntry.natConfAddrMapName. This leads to an 
> inconsistent state in SNMP if left to the Manager.
>
>
> Thanks and Regards,
> Sam.
>


_______________________________________________
nat mailing list
nat@ietf.org
https://www1.ietf.org/mailman/listinfo/nat


From nat-admin@ietf.org  Sun Dec 15 12:04:10 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06527
	for <nat-archive@lists.ietf.org>; Sun, 15 Dec 2002 12:04:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBFH5ov19135;
	Sun, 15 Dec 2002 12:05:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBF7vov25589
	for <nat@optimus.ietf.org>; Sun, 15 Dec 2002 02:57:50 -0500
Received: from india-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00008
	for <nat@ietf.org>; Sun, 15 Dec 2002 02:54:39 -0500 (EST)
Received: from cbin2-mira-01.cisco.com (localhost [127.0.0.1])
	by india-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gBFDQL6h022533;
	Sun, 15 Dec 2002 13:26:21 GMT
Received: from cisco.com (rtp-vpn2-159.cisco.com [10.82.240.159])
	by cbin2-mira-01.cisco.com (Mirapoint)
	with ESMTP id AGB02210 (AUTH raraghun);
	Sun, 15 Dec 2002 13:20:09 +0530 (IST)
Message-ID: <3DFC3594.7FED32CF@cisco.com>
Date: Sun, 15 Dec 2002 13:26:04 +0530
From: Rajiv Raghunarayan <raraghun@cisco.com>
Organization: Cisco Systems Inc.
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: sam.kuruvilla@wipro.com
CC: nat@ietf.org
Subject: Re: [NAT] Clarification reqd
References: <3DF4BEB8.2060207@wipro.com> <3DF6EC03.50807@wipro.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Sam,

I'm not sure I completely follow your questions, but I've tried
to answer your questions (inline) based on what I understand 
(please correct me if I've misunderstood something).

"Sam K. Sankoorikal" wrote:
> 
> Hi ,
> 
>         I think I mixed up things in my previous mail. I'll try to frame
> it better:* *I have refered to * DEFVAL *as defined in RFC1212.
> 
>         Now consider the following scenario:
> 
>                         The natConfTable is used to enable NAT on the
> eth0. This is done by using the DEFVAL of ' 'H for the
> natConfAddrMapName while creating that row. Now if a snmpwalk is
> performed on the natConfAddrMapTable, even with just the "default index
> value" mapping rows can be returned. 

If an entry is created in the natConfTable and one queries the 
natConfAddrMapTable, entries needn't be returned. Basically, what 
I'm trying to say here is that creation of entries in the 
natConfTable doesn't result in automatic creation of entries in
the natConfAddrMapTable. One needs to explicitly create entries
in the latter.

A typical configuration process would be as follows:

Create generic address mapping entries in the natConfAddrMapTable.
Now when NAT needs to be enabled on a particular interface, create
an entry in the natConfTable and associate it with the appropriate
mapping from the natConfAddrMapTable (via natConfAddrMapConfigName).

> The returned entries are now
> returned with primary index as ' 'H and secondary index as the value of
> natConfAddrMapIndex( 1 .. 2147483647).
>                         Now here is the problem I see: Repeat the above
> steps for eth1.  ie Enable  NAT for eth1(Here also  natConfAddrMapName
> is specified as the DEFVAL). Now if a walk is performed on the
> natConfAddrMapTable there will be a problem in retuning the rows, as
> sorting based on the primary index and secondary index will not be
> possible. ie there could be two entries for each  The problem originated
> since the DEFVAL clause does not seem to provide a correct default.
> Ofcourse the user should have the understanding to use unique values for
> each entry created in the natConfTable. Please let me know your views on
> this and if the scenario is valid, a possible solution for the same.

Not sure I completely understand the scenario, but the basic 
assumption that creation of entries in natConfTable will result in
automatic creation of entries in the natConfAddrMapTable is, imho,
incorrect.

> 
>                         An associated problem with the
> natConfTable.natConfEntry.natConfAddrMapConfigName is that. This table
> decides the Index for the natConfAddrMapTable. 

It's the other way round. What value to be written into the
natConfAddrMapConfigName is decided by the index of 
natConfAddrMapTable i.e. natConfAddrMapName.

> Now, assuming that the
> two tables are tightly tied up, any change in the
> natConfTable.natConfEntry.natConfAddrMapConfigName  in the first table
> will result in changes in the second table. 

No. These two tables are linked, but I'd say loosely linked. Please,
correct me if I'm mistaken, but afaik the draft doesn't imply 
anywhere that changes in the natConfAddrMapConfigName must result 
in changes in the natConfAddrMapTable. If it does, perhaps a 
correction might be required..

> I dont believe this is a
> consistent thing to do. 
> Why can't the index be predecided when we know
> that the index is just to indicate to the Manager the interface to which
> the mapping belongs. The primary index in the natConfAddrMapTable could
> be the primary index of the natConfTable. 

The primary index of the natConfAddrMapTable is used to configure 
an address map. It doesn't tie this address map to any interface.

The index of the natConfTable is used to identify an interface
and associate a certain nat config with this interface (via
the natConfAddrMapConfigName). 

Note that via the existing mechanism one can tie more than one 
interface with the same NAT config without creating multiple
entries in the natConfAddrMapTable (which would be required
if one uses the ifIndex as the primary index of the table).

> Is there any other purpose in
> having it as a string ? Please highlight the purpose/advantages in
> having it as a string.

A number could've been used in place of the string, but the string 
just aids in better readability. 

-Rajiv.

> 
> Thanks and Regards,
> Sam
> 
> Sam K. Sankoorikal wrote:
> 
> > Hi Rajiv,
> >
> >         I have a specific query on the natConfAddrMapName[Seems to a
> > be a complex index]: Is there some convention[~default] to be followed
> > when using this index while returning a row of this table?
> >         This a scenario where the natConfAddrMapName may not be have
> > yet been given a name by any manager and NAT / NAPT is already enabled
> > on an interface. As a result, there are rows already present in this
> > table, based on mapping created on the fly by the NAT module, through
> > some UI configuration. Is it OK/Safe if the Agent decides to use a
> > name it finds convenient and thus be able to return to NAT mapping to
> > any manager querying it ?
> >
> > Some relate questions:
> >
> > 1. Does the agent also have to store the same value in the
> > "natConfTable.natConfEntry.natConfAddrMapConfigName".?
> >
> > 2. Can a Manager change only
> > natConfTable.natConfEntry.natConfAddrMapConfigName and what is the
> > effect on the natConfAddrMapEntry.natConfAddrMapName. This leads to an
> > inconsistent state in SNMP if left to the Manager.
> >
> >
> > Thanks and Regards,
> > Sam.
> >
> 
> _______________________________________________
> nat mailing list
> nat@ietf.org
> https://www1.ietf.org/mailman/listinfo/nat
_______________________________________________
nat mailing list
nat@ietf.org
https://www1.ietf.org/mailman/listinfo/nat


From mailnull@www1.ietf.org  Sun Dec 15 12:06:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06580
	for <nat-archive@odin.ietf.org>; Sun, 15 Dec 2002 12:06:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBFH9Ok19860
	for nat-archive@odin.ietf.org; Sun, 15 Dec 2002 12:09:24 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBFH5ov19135;
	Sun, 15 Dec 2002 12:05:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBF7vov25589
	for <nat@optimus.ietf.org>; Sun, 15 Dec 2002 02:57:50 -0500
Received: from india-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00008
	for <nat@ietf.org>; Sun, 15 Dec 2002 02:54:39 -0500 (EST)
Received: from cbin2-mira-01.cisco.com (localhost [127.0.0.1])
	by india-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gBFDQL6h022533;
	Sun, 15 Dec 2002 13:26:21 GMT
Received: from cisco.com (rtp-vpn2-159.cisco.com [10.82.240.159])
	by cbin2-mira-01.cisco.com (Mirapoint)
	with ESMTP id AGB02210 (AUTH raraghun);
	Sun, 15 Dec 2002 13:20:09 +0530 (IST)
Message-ID: <3DFC3594.7FED32CF@cisco.com>
Date: Sun, 15 Dec 2002 13:26:04 +0530
From: Rajiv Raghunarayan <raraghun@cisco.com>
Organization: Cisco Systems Inc.
X-Mailer: Mozilla 4.51 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: sam.kuruvilla@wipro.com
CC: nat@ietf.org
Subject: Re: [NAT] Clarification reqd
References: <3DF4BEB8.2060207@wipro.com> <3DF6EC03.50807@wipro.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: nat-admin@ietf.org
Errors-To: nat-admin@ietf.org
X-BeenThere: nat@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=unsubscribe>
List-Id: Network Address Translation <nat.ietf.org>
List-Post: <mailto:nat@ietf.org>
List-Help: <mailto:nat-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nat>,
	<mailto:nat-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Sam,

I'm not sure I completely follow your questions, but I've tried
to answer your questions (inline) based on what I understand 
(please correct me if I've misunderstood something).

"Sam K. Sankoorikal" wrote:
> 
> Hi ,
> 
>         I think I mixed up things in my previous mail. I'll try to frame
> it better:* *I have refered to * DEFVAL *as defined in RFC1212.
> 
>         Now consider the following scenario:
> 
>                         The natConfTable is used to enable NAT on the
> eth0. This is done by using the DEFVAL of ' 'H for the
> natConfAddrMapName while creating that row. Now if a snmpwalk is
> performed on the natConfAddrMapTable, even with just the "default index
> value" mapping rows can be returned. 

If an entry is created in the natConfTable and one queries the 
natConfAddrMapTable, entries needn't be returned. Basically, what 
I'm trying to say here is that creation of entries in the 
natConfTable doesn't result in automatic creation of entries in
the natConfAddrMapTable. One needs to explicitly create entries
in the latter.

A typical configuration process would be as follows:

Create generic address mapping entries in the natConfAddrMapTable.
Now when NAT needs to be enabled on a particular interface, create
an entry in the natConfTable and associate it with the appropriate
mapping from the natConfAddrMapTable (via natConfAddrMapConfigName).

> The returned entries are now
> returned with primary index as ' 'H and secondary index as the value of
> natConfAddrMapIndex( 1 .. 2147483647).
>                         Now here is the problem I see: Repeat the above
> steps for eth1.  ie Enable  NAT for eth1(Here also  natConfAddrMapName
> is specified as the DEFVAL). Now if a walk is performed on the
> natConfAddrMapTable there will be a problem in retuning the rows, as
> sorting based on the primary index and secondary index will not be
> possible. ie there could be two entries for each  The problem originated
> since the DEFVAL clause does not seem to provide a correct default.
> Ofcourse the user should have the understanding to use unique values for
> each entry created in the natConfTable. Please let me know your views on
> this and if the scenario is valid, a possible solution for the same.

Not sure I completely understand the scenario, but the basic 
assumption that creation of entries in natConfTable will result in
automatic creation of entries in the natConfAddrMapTable is, imho,
incorrect.

> 
>                         An associated problem with the
> natConfTable.natConfEntry.natConfAddrMapConfigName is that. This table
> decides the Index for the natConfAddrMapTable. 

It's the other way round. What value to be written into the
natConfAddrMapConfigName is decided by the index of 
natConfAddrMapTable i.e. natConfAddrMapName.

> Now, assuming that the
> two tables are tightly tied up, any change in the
> natConfTable.natConfEntry.natConfAddrMapConfigName  in the first table
> will result in changes in the second table. 

No. These two tables are linked, but I'd say loosely linked. Please,
correct me if I'm mistaken, but afaik the draft doesn't imply 
anywhere that changes in the natConfAddrMapConfigName must result 
in changes in the natConfAddrMapTable. If it does, perhaps a 
correction might be required..

> I dont believe this is a
> consistent thing to do. 
> Why can't the index be predecided when we know
> that the index is just to indicate to the Manager the interface to which
> the mapping belongs. The primary index in the natConfAddrMapTable could
> be the primary index of the natConfTable. 

The primary index of the natConfAddrMapTable is used to configure 
an address map. It doesn't tie this address map to any interface.

The index of the natConfTable is used to identify an interface
and associate a certain nat config with this interface (via
the natConfAddrMapConfigName). 

Note that via the existing mechanism one can tie more than one 
interface with the same NAT config without creating multiple
entries in the natConfAddrMapTable (which would be required
if one uses the ifIndex as the primary index of the table).

> Is there any other purpose in
> having it as a string ? Please highlight the purpose/advantages in
> having it as a string.

A number could've been used in place of the string, but the string 
just aids in better readability. 

-Rajiv.

> 
> Thanks and Regards,
> Sam
> 
> Sam K. Sankoorikal wrote:
> 
> > Hi Rajiv,
> >
> >         I have a specific query on the natConfAddrMapName[Seems to a
> > be a complex index]: Is there some convention[~default] to be followed
> > when using this index while returning a row of this table?
> >         This a scenario where the natConfAddrMapName may not be have
> > yet been given a name by any manager and NAT / NAPT is already enabled
> > on an interface. As a result, there are rows already present in this
> > table, based on mapping created on the fly by the NAT module, through
> > some UI configuration. Is it OK/Safe if the Agent decides to use a
> > name it finds convenient and thus be able to return to NAT mapping to
> > any manager querying it ?
> >
> > Some relate questions:
> >
> > 1. Does the agent also have to store the same value in the
> > "natConfTable.natConfEntry.natConfAddrMapConfigName".?
> >
> > 2. Can a Manager change only
> > natConfTable.natConfEntry.natConfAddrMapConfigName and what is the
> > effect on the natConfAddrMapEntry.natConfAddrMapName. This leads to an
> > inconsistent state in SNMP if left to the Manager.
> >
> >
> > Thanks and Regards,
> > Sam.
> >
> 
> _______________________________________________
> nat mailing list
> nat@ietf.org
> https://www1.ietf.org/mailman/listinfo/nat
_______________________________________________
nat mailing list
nat@ietf.org
https://www1.ietf.org/mailman/listinfo/nat



