Re: [Softwires] Stateless implementation plan

just my personal humble understanding:

basically MAP or 4rd, as it is named, is designed for residual deployment,
i.e., using not-yet-allocated or already-recalled ipv4 addresses for the
ipv4 access of ipv6-enabled networks. its address mapping logic implies
doing the ipv6 address planning as the first step, independent of ipv4.

for the transition of existing ipv4 network without renumbering (or only
renumbering to ipv4-translatable ipv6 addresses), MAP is also applicable
but the operator should pay much attention to the addressing issue. in such
a case, RFC6052/RFC6145 suite is a little better recommended.
- maoke
2012/2/8 Cameron Byrne <cb.list6@gmail.com>

> Are the map and 4rd solutions deployable for existing networks that do not
> have reserves  of ipv4 ?  My assumption is that these solutions target
> existing networks that have meaningful growth and they need a v6 solution.
>
> If yes, how? Any pointers within the reams of drafts I should look for?
>
> In my brief and simple skimming, it appears to me that setting up one of
> these solutions would require me to collapse my existing network to harvest
> back the addresses so that they may be redeployed in map.
>
> What would the deployment process be for an address exhausted network of
> 10 million subs with 10% annual growth be?
>
> Cb
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>
>