>>>> >>>>I read your 4rd draft. As far as I know, the current 4rd draft >>>>supports 3 >>>> models: >>>> >>>> 1. An IPv4 prefix >>>> 2. Full IPv4 address (No port sharing) >>>> 3. IPv4 address and a range of ports >>>> >>>> So case 2 is equal to 4over6. Is my understanding right? >>> >>> yes, the 'service' provided should be the same. >>> I presume 4over6 also could do 1? >> Currently, we only focus on 2 without 1. Because if we use DHCPv4 over >> IPv6 tunnel, DHCPv4 doesnot support prefix assignment, right? >>> >>> the main differences between 4over6 and 4rd for case 2, would be how it >>> is provisioned and that 4over6 wouldn't have any dependency between the >>> tunnel endpoint addresses and the payload addresses. >>> obviously 4rd could be made less dependent of that too, by assigning >>> specific IPv6 addresses for the mapping, independent of the delegated >>> IPv6 prefix used within the end user site. doing that you really keep >>> mapping state in the RIB. but that's definitely one deployment model of >>> 4rd. >> Even for 2, the use cases are different between 4over6 and 4rd because >>of >> the independency of IPv4/IPv6 addresses. For example, 4over6 can assign >> the public IPv4 addresses to a few high-priority hosts distributed in a >> large-scale network withOUT changing the local network devices or the >> current policy of IPv6 address assignment. So we don't need the >> cooperation with the local IPv6 address assignment. >> That's quite important for our CERNET2. > >Classic stateful vs. stateless deployment alternative. I hear the same >for people who end up deploying L2TP for IPv6 over IPv4 instead of 6rd. >It all depends on how much control you need over the two addressing >families and their interaction.
You are right, Mark. So in order to encourage the deployment of IPv6 and make the deployment as simple as possible, we are looking forword to the 4over6 solution in CERNET2. Yong _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
