Le 4 avr. 2011 à 14:38, Yong Cui a écrit : ... >>> 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.
This is a requirement for a customizable service. >>> 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. Same view. It can also be viewed as a tradeoff between customizable services and the triple [ease of operation, scalability, investment cost]. > 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. With the customizable service you want, this is clearly a solution. But this of course doesn't prohibit others providers to prefer more standardized services (for residual IPv4 connectivity across IPv6-only) to privilege ease of operation, scalability, and investment costs. The tradeoff could then be summarized as: +----------------------------+--------------------+-----------------+ | | Stateful (4over6) | Stateless (4rd) | +----------------------------+--------------------+-----------------+ | Customizable services | + | - | | -------------------------- | ------------------ | --------------- | | Ease of operation | - | + | | -------------------------- | ------------------ | --------------- | | Scalability | - | + | | -------------------------- | ------------------ | --------------- | | Invetment cost | - | + | | minimization | | | +----------------------------+--------------------+-----------------+ Does this make sense to you? Regards, RD _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
