Issue with InetAddressType

[Margaret Wasserman <mrw@windriver.com>]

Hi All,

An issue came up when reviewing our updates to the TCP & UDP
MIBs that may affect other MIBs.

Due to the changes in the InetAddressType TC to define different
types for global and non-global addresses, it is now necessary
to include InetAddressType variables in places where they were
not previously needed.

To give an example:

	In our TCP MIB, we have a connection table indexed by
	a local address, a remote address and two ports.  In
	previous versions of the MIB, we had one InetAddressType
	index that was stated to apply to both addresses.  

	However, with the new definition of InetAddressType, we
	need to provide two different type variables (a local
	address type, and a remote address type), because it is
	possible to have a connection between a global IPv6 
	address and a non-global IPv6 address (for example).

Other MIBs that use InetAddress and InetAddressType should be
checked for similar issues.

In general, we should probably require a separate InetAddressType
variable for every InetAddress variable.

Thanks,
Margaret