Good point, and having a Consumer CPE spec as a RIPE
standard would help for last mile access requirements. RIPE-501 only aimed for
government and enterprise deployments.
Access is where IPv4 is being depleted rapidly, thus
mentioning how IPv6 can coexist with limited
IPv4 addresses, with the objective of conserving consumer
CPE cost by keeping IPv6 features on CPEs to the minimum, is
needed.
Two approaches should be covered in
access: Tunneling for dual-stack access (such as TSP and 6RD for
v6-in-v4, plus DS-Lite and DSTM for v4-in-v6), as well as
Translation for single stack IPv6-only hosts using protocols such as
NAT64/DNS64. Each protocol's suitability for rapid transition, as well as its
edge network requirements, should be mentioned.
Note that I am affiliated with an access vendor,
gogo6 / Hexago, which runs the global Freenet6 network using tunneling CPEs and
soft clients.
Regards,
-Ahmed
Sent: Saturday, January 08, 2011 1:11 PM
Subject: Re: [ipv6-wg] "Requirements For IPv6 in ICT Equipment"
comment
Greetings to all and happy new year.
We also used this
document to extract basic features (in our environment)
for customer
CPEs.
In my opinion, the "document" format must be preserved as a
single
place to contain the entire information. I guess 'if'
statements like
Jan mentions is one way to achieve the desired
outcome.
Regards,
Kostas Zorbadelos