Ole, > in MAP aggregated mode you have: > 1.1.1.0/24 -> 2001:db8:XXXX::/48
Actually, the so called 'aggregated mode' is original MAP-E, with IPv4 address and PSID embedded in the EA-bits field in End user IPv6 prefix. Let me try to explain what you have 'aggregated'. 1.1.1.1:01 -> 2001:db8:101::/48 (EA-bits: 0x101) 1.1.1.1:02 -> 2001:db8:102::/48 (EA-bits: 0x102) 1.1.1.1:03 -> 2001:db8:103::/48 (EA-bits: 0x103) . . . The IPv4 address and port set are the same in what you called 'MAP 1:1'. However, the corresponding IPv6 addresses are totally different. Because one uses MAP algorithm, the other doesn't. The original MAP-E achieves address sharing by embedding IPv4 suffix and PSID into End User IPv6 prefix. But if the EA-bits is ZERO, PSID is also ZERO. Nothing embedded in the IPv6 prefix. In this case, the so called 'MAP 1:1' abandons the MAP algorithm and uses a per-subscriber stateful kind method to achieve address sharing. That is NOT MAP-E. So I question why 'MAP-E 1:1' bears the MAP-E name. Qi Sun On 2012-11-13, at 下午9:46, Ole Trøan wrote: >> [Yuchi] Actually there is a 'binding' table on the AFTR, which maintains >> matching between v4 A+P and v6 A, and there's no 'mapping with address and >> port' in DS-Lite or Lw4over6 as in MAP. The main point here is not about the >> literal difference between 'binding' and 'mapping', but the difference >> between decoupling v4 & v6 and coupling v4 & v6. > > let us assume we have a 1.1.1.0/24 for address sharing available with 256 > ports per user. > > in MAP 1:1 you'd have: > 1.1.1.1:01/40 -> 2001:db8::1 > 1.1.1.1:02/40 -> 2001:db8::2 > 1.1.1.1:03/40 -> 2001:db8::3 > . > . > . > > 64K rules. > > in MAP aggregated mode you have: > 1.1.1.0/24 -> 2001:db8:XXXX::/48 > > can you please show how the LW46 rules / binding /mapping whatever you call > them look like for 1:1 mode? > > cheers, > Ole > > _______________________________________________ > Softwires mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/softwires _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
