Re: [Softwires] I-D Action: draft-ietf-softwire-map-08.txt

Hi Ole ,

IMHO, the Unified CPE defines some functionalities and behaviors of CE side, e.g. tunnel endpoint, NAT44, how to use these functions on CPE etc., which MAP depends on. 

As for the provisioning method, map-dhcp is one of the methods could be used in MAP. The discussion is taking place in the Unified CPE for provisioning. So I think it should be an informative reference in MAP base draft.

Best Regards,
Qi

On 2013-8-13, at 下午5:45, Ole Troan wrote:

> Med,
> 
>> The documents should be cross-references, that's clear. 
>> 
>> If I recall well what was discussed (and which I assumed agreed) in Atlanta, is the unified CPE draft governs the CE side for all softwire flavors. The consequence is provisioning discussion in particular should be removed from MAP, LW4ov6, etc documents ... instead be discussed exclusively in the unified CPE I-D. 
>> 
>> I will refer to Suresh on this point since he was present during that discussion and also because this is a action to preserve the coherency of the overall ongoing specification efforts conducted by the WG.
> 
> the MAP document only specifies how a CE must function and what parameters must be provisioned. there is no provisioning discussion there to remove as far as I can see. MAP as a mechanism should stand on its own.
> 
> the unified CPE effort, if successful, is trying to create a coherent picture of all the different mechanisms to make it possible to support all of them in a single CPE. my understanding of the unified CPE effort was that it was NOT going to define protocol, but only specify how mechanisms co-exist.
> 
> cheers,
> Ole
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires