On Thu, Nov 27, 2014 at 2:23 PM, Tom Taylor <[email protected]>
wrote:
> Just to set the agenda: the definition of the address mapping table entry:
>
> natv2AddressMapEntry OBJECT-TYPE
> SYNTAX Natv2AddressMapEntry
> MAX-ACCESS not-accessible
> STATUS current
> DESCRIPTION
> "Mapping from internal to external address."
> INDEX { natv2AddressMapInstanceIndex,
> natv2AddressMapInternalRealm,
> natv2AddressMapInternalAddressType,
> natv2AddressMapInternalAddress }
> ::= { natv2AddressMapTable 1 }
>
> Natv2AddressMapEntry ::=
> SEQUENCE {
> natv2AddressMapInstanceIndex Natv2InstanceIndex,
> natv2AddressMapInternalRealm SnmpAdminString,
> natv2AddressMapInternalAddressType InetAddressType,
> natv2AddressMapInternalAddress InetAddress,
> natv2AddressMapExternalRealm SnmpAdminString,
> natv2AddressMapExternalAddressType InetAddressType,
> natv2AddressMapExternalAddress InetAddress,
> natv2AddressMapSubscriberIndex Natv2SubscriberIndexOrZero
> }
>
> Now some example numbers:
>
> natv2AddressMapInstanceIndex = 1
> natv2AddressMapInternalRealm = "DS-Lite Group 5"
> natv2AddressMapInternalAddressType = ipv6(2)
> natv2AddressMapInternalAddress = 2001:db8:0:1::1
> natv2AddressMapExternalRealm = "global4"
> natv2AddressMapExternalAddressType = ipv4(1)
> natv2AddressMapExternalAddress = 192.0.2.1
> natv2AddressMapSubscriberIndex = 487231
>
> This entry would be indexed by the combination of
>
> { 1, "DS-Lite Group 5", ipv6(2), 2001:db8:0:1::1 }
>
Ok, so far this is what I expected. I see a mapping from 2001:db8:0:1::1 to
192.0.2.1. However, in DS-Lite that mapping does not necessarily exist. For
example, you could have these two mappings to different external addresses
simultaneously:
{ 2001:db8:0:1::1, 192.0.0.1 } --> 192.0.2.1
{ 2001:db8:0:1::1, 192.0.0.2 } --> 192.0.2.2
Note that this is the same subscriber, same IPv6 address, but different
internal IPv4 addresses mapped to different external IPv4 addresses. As you
can see there is no unique mapping IPv6 --> IPv4.
Simon
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
