Hi Ole,

There are 2 ways to achieve address sharing in MAP-E-04, one is algorithmic 
mapping IPv4 address and PSID into IPv6 prefix, the other is non-algorithmic 
binding of IPv4 address, port-set and IPv6 address. The former is advocating 
the designed algorithm to achieve stateless, while the latter achieves 
IPv4/IPv6 address independence by abandoning the algorithm. It conflicts with 
itself.

Now that the algorithm is still there when EA = 0 (even though not used), MAP-E 
still requires the implementation of the algorithm and planning IPv4 and IPv6 
address together. This increases the cost for operators.

Removing MAP 1:1 mode helps MAP be cleaner as a stateless solution for 
operators.

My vote is to remove MAP 1:1 mode.


Best Regards,
Qi Sun


On 2013-2-14, at 下午6:14, Ole Troan wrote:

>> #25: Maintain or remove MAP1:1 Mode?
> 
> OK, so here is a task for whomever thinks MAP 1:1 mode should be removed.
> 
> - what does "remove MAP 1:1 mode mean"?
> - please suggest text changes to the mechanism that removes 1:1 mode.
> 
> given that my opinion is that 1:1 mode is an unremovable part of MAP, the 
> question just doesn't make sense to me.
> 
> I don't want this issue to be an excuse to block a last call, can we quickly 
> resolve this, and can we agree to drop it if there are no significant 
> contributions within the next week?
> 
> cheers,
> Ole
> 
> 
>> 
>> The WG discussed several times this point (refer to the mailing list
>> archives).
>> 
>> MAP1:1 mode is a particular mode which may re-use some of the provisioning
>> methods defined for MAP.
>> 
>> MAP1:1 vs. Lw4o6:
>> * MAP1:1 is not fully stateless.
>> * Lw4o6 is a standalone specification which provides the same service as
>> MAP1:1.
>> 
>> -- 
>> -------------------------------------+-------------------------------------
>> Reporter:                           |      Owner:  draft-ietf-softwire-
>> [email protected]       |  [email protected]
>>    Type:  defect                   |     Status:  new
>> Priority:  major                    |  Milestone:
>> Component:  map-e                    |    Version:
>> Severity:  -                        |   Keywords:
>> -------------------------------------+-------------------------------------
>> 
>> Ticket URL: <http://trac.tools.ietf.org/wg/softwire/trac/ticket/25>
>> softwire <http://tools.ietf.org/softwire/>
>> 
> 
> _______________________________________________
> Softwires mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/softwires

_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires

Reply via email to