hi Sentihil and Maoke,
Things come a little confused, let us come to the first email Kris had
sent and I cut some discussion from before emails:
1) Does MAP support this scenario (example):
- (BMR) Rule 1:
Rule IPv6 Prefix: 2001::/40
Rule IPv4 Prefix: 192.0.2.0/24
Rule EA-bits length: 12
- (BMR) Rule 2:
Rule IPv6 Prefix: 2001::/40
Rule IPv4 Prefix: 200.0.2.0/24
Rule EA-bits length: 12
Discussion from before emails:
what is the consequence if the CE has the two rules?
NOTE the delegation is independent of the IPv4 address in use. for
example, we have 2001:0:00xx:y000::/52 for the CE, where xx (8 bits) is
the same as the IPv4 suffix while y (4 bits) is applied for the PSID. if
the source address has been selected from either rule ipv4 prefix, then
the encapsulation or translation is determined and the BR can de-capsulate
or de-translate that without any difficulty because the full IPv4 address
is embedded in the IID part. when the response comes, the destination
address of the IPv4 packet is also determined though they would be
encapsulated with the same IPv6 prefix (not the same IPv6 CE address!).
[Senthil2] I don’t see any issues with correctly
decapsulating/translating the packet on the BR for v6->v4. The issue is
with the v4->v6. You cannot correctly know which of the two IP addresses
to embed. With translation, the communication will definitely fail if you
embed the wrong IP address.
[maoke2] i cannot catch your point. you mean v4->v6 at BR, right?
which IPv4 address to embed is determined by the session initiator. for
example, if a host behind CE makes a connection to 8.8.8.8, and if the CE
happens to have picking up 192.0.2.191 as the src IPv4
address, then the 8.8.8.8 will response 192.0.2.191 definitely. i don't
see that BR needs to choose an IPv4 address to embed: the destination
address in the packet replying to the session initiator is determined.
[Linda]: I think Maoke is right, BR needn't to choose an IPv4 address to
embed because the IPv4 address is already in the inbound packet's
destination address field.
BUT when the encapsulated V6 packet arrived at CE, CE de-capsulated the V6
packet and then check the NAT binding table according to the V4
destination address 192.0.2.191, then translated 192.0.2.191 to
corresponding V4 address of the host behind this CE+Port, and then forward
the V4 packet to the corresponding application at the host. I can't find
any issues at CE. Am i missunderstanding ?
And because there were two V4 address block at this CE, if one V4 address
block had no V4 address to allocate for new sessions, then CE could use
another V4 address block to create new sessions.
So I think if a MAP domain supports several BMRs with same Ruled IPv6
prefix and different Ruled IPv4 prefix is OK. If I misunderstand please
point out without hestitant.
Thanks.
Linda
"Poscic, Kristian (Kristian)" <[email protected]>
发件人: [email protected]
2012-12-11 04:06
收件人
"[email protected]" <[email protected]>
抄送
主题
[Softwires] MAP-E/T overlaping ranges and domains
Can someone clarify a few things for me:
1) Does MAP support this scenario (example):
- (BMR) Rule 1:
Rule IPv6 Prefix: 2001::/40
Rule IPv4 Prefix: 192.0.2.0/24
Rule EA-bits length: 12
- (BMR) Rule 2:
Rule IPv6 Prefix: 2001::/40
Rule IPv4 Prefix: 200.0.2.0/24
Rule EA-bits length: 12
The only difference between these two rules above is the
‘Rule IPv4 Prefix’, everything else is the same. My obvious answer would
be that this scenario is not supported but wanted to be sure that I’m not
missing anything.
This scenario above would result in ambiguity between CEs, i.e. a single
IA-PD that is delegated to a CE can be associated with either of the two
rules above (EA bits can be the same for a CE from 192.0.2.0/24 range and
for a CE from 200.0.2.0/24 range.
In this example above, it is assumed that the delegated prefix (IA-PD)
that DHCPv6 Server is handing out to CEs is 2001::/40 with delegated
prefix length /56.
This makes me believe that each rule must not only be
unique (because the above two rules are unique) but instead each rule must
have a unique ‘Rule IPv6 prefix’ and a unique ‘Rule IPv4 Prefix’ per
‘Rule IPv6 prefix’ (IPv4 uniqueness is important in the downstream
direction where lookup is performed based on IPv4).
2) What constitutes a MAP domain? I’d think a unique ‘Rule IPv6
Prefix’ which (assuming that 1) is correct) would mean that a Domain =
BMR. In other words, can a MAP domain contain a collection of BMRs? The
drafts mention virtual-links, etc…but it would be simpler if we can say
Domain=BMR (not sure if this is accurate though). Of course, nodes
sharing the same set of those rules would be in the same MAP domain.
3) Is overlapping of ‘Rule IPv6 Prefixes’ supported?
For example in the above case, can we have for Rule 2) the ‘Rule IPv6
prefix’ as 2001:0:80::/42.
In this case the ‘Rule IPv6 Prefix’ from Rule 1 overlaps with ‘Rule
IPv6 Prefix’ from Rule 2. I assume that this would not be supported for
the same reason as in 1). I didn’t think about the applicability of this
scenario for now, it is more of a theoretical question.
Thanks,
Kris
_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires
_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires
