On 3/1/11 8:58 PM, Daniel Roesen wrote:
If the chosen approach is DS-Lite, the ISP needs at some point in time
start to provision customers in a way to make sure they'll use DS-Lite
for IPv4 connectivity to conserve IPv4 addresses in a plannable manner.
"plannable manner" means specifically that the DS-Lite provisioned
customer cannot opt-out of using DS-Lite by turning off DS-Lite in the
CPE router and then again get a public IPv4 address via DHCPv4.
Ideally (that's the goal), wether CPE router has to use DS-Lite or just
go for DHCPv4 (dual stack mode) should be signalled by the ISP to the
CPE router device. Or more precise: there should be a way for an ISP to
signal a CPE router that is absolute has to use DS-Lite to obtain IPv4
connectivity as DHCPv4 will fail. The customer should not have to know
what "DS-Lite" is or - even worse - explicitly enable it in the CPE
router GUI in order to get IPv4 connectivity behind a "DS-Lite
connection".
Hi,
That's what one of benefits of A+P architecture is.
See draft-ymbk-aplusp, section 3.3.4. "Overall A+P Architecture"
Our idea is incremental deployment. Today ISP can put PRR in his network
and start shipping out CPEs with A+P semantics deployed (if there would
be any serious implementation and if we would not be delayed for a year
with this draft by "they know who they are").
Idea is that you can allocate public IP with full port range to the
customer and he would not notice the difference. With time you have a
customer base able to share the IP and when you hit the point in your
IPv4 stock that you decide you need to share IP addresses you just send
out a new data-plan possibility (maybe even cheaper) and inform users
that they can enable it with just a flick of the switch on service pages
- you only need to change the behaviour of the encapsulation and
allocate limited set of ports to a customer. This way you still give the
user public IP address but with limited set of prots. You can go even
further and offer CGN-like access, but then that wouldn't be worth more
than 1EUR/month :)
It's there in architecture and it's unique. Current popular transition
ideas tends to enforce violent mass deployment in a single short period
of time, when you need to do switchover.
Cheers, Jan Zorz
_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires
