> The following is our latest progress on our "bt-translated-ds-lite". It moves > the translation function from tunnel concentrator (AFTR) to initiators (B4s), > and hence reduce the mapping scale on the concentrator to per-customer level. > We have implemented a prototype and deployed it in Hunan province. > > A URL for this Internet-Draft is: > http://www.ietf.org/id/draft-cui-softwire-b4-translated-ds-lite-03.txt
I think this is a good idea in general and that it fits well with the other approaches we've been discussing in softwire for IPv4 over IPv6 mechanisms. I'll read through again and provide detailed comments asap. with regards to document organization, would it be possible to: - merge host 4over6 (draft-cui-softwire-host-4over6-06) with lightweight 4over6 (draft-cui-softwire-b4-translated-ds-lite-03) - merge stateless 4over6 (draft-sun-softwire-stateless-4over6-00) with the MAP effort then we'll have one 'stateless' version of A+P document and one 'stateful' A+P aka DS-lite with A+P extensions. both also handling the case of a full IPv4 address on the B4. cheers, Ole > --------------------------------------------------------------------------------------------------------------------------------------- > > Lightweight 4over6 in access network > draft-cui-softwire-b4-translated-ds-lite-03 > > Abstract > > The dual-stack lite mechanism provide an IPv4 access method over IPv6 > ISP network for end users. Dual-Stack Lite enables an IPv6 provider > to share IPv4 addresses among customers by combining IPv4-in-IPv6 > tunnel and Carrier Grade NAT. However, in dual-stack lite, CGN has > to maintain active NAT sessions, which could become the performance > bottom-neck due to high dynamic s of NAT entries, memory cost and log > issue. This document propose the lightweight 4over6 mechanism which > moves the translation function from tunnel concentrator (AFTR) to > initiators (B4s), and hence reduce the mapping scale on the > concentrator to per-customer level. For NAT44 translation usage, the > mechanism will allocate port restricted IPv4 addresses to initiators > in a flexible way independent of IPv6 network in the middle. > > _______________________________________________ > Softwires mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/softwires _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
