[ipv6-wg] Re: [address-policy-wg] DRAFT: RIPE Community Resolution on IPv4 Depletion and Deployment of IPv6

Performance is not an issue when doing peer to peer with the same transition
mechanism (example Teredo to Teredo or 6to4 to 6to4), actually the
performance is better than doing it with IPv4 and using intermediate hosts,
such as MSN or Skype do.

Performance impacts when both hosts doing peer-to-peer (or client-to-server)
are using different types of IPv6 connectivity (example, native vs. 6to4 or
Teredo, or Teredo vs. 6to4). This is solved by deploying 6to4 and Teredo
relays in the ISPs, and is actually something inexpensive that ISPs should
do while they can't provide native access.

Regards,
Jordi




> De: Carlos Friacas <cfriacas at fccn.pt>
> Responder a: <ipv6-wg-admin at ripe.net>
> Fecha: Fri, 19 Oct 2007 09:22:44 +0100 (WEST)
> Para: JORDI PALET MARTINEZ <jordi.palet at consulintel.es>
> CC: <ipv6-wg at ripe.net>
> Asunto: [ipv6-wg] Re: [address-policy-wg] DRAFT: RIPE Community Resolution on
> IPv4 Depletion and Deployment of IPv6
> 
> On Thu, 18 Oct 2007, JORDI PALET MARTINEZ wrote:
> 
>> Well, I don't agree you're not part of the community. Being subscriber and
>> poster to the mailing is a qualifier for being a member :-)
>> 
>> Agree with Florian and you. It is needed to say something to remind vendors
>> that market is already asking for IPv6 support. I don't think they should
>> just wait for the demand to come, because then it will be late. So a warning
>> to them is a good thing. Same for software developers, they should realize
>> that they can take advantage of IPv6 NOW, because even if there are no
>> native access providers yet, transition is available in end-hosts.
> 
> there are NOT ENOUGH native (commercial) access providers
> ...but we should make a small note that some already exist. :-)
> 
> 
>> There is no immediate need for low costs CPEs, of course is good to have,
>> but transition tools in end-hosts already deliver the same, until access
> 
> //transition tools in end-hosts//
> 
> ...and what happens to performance???
> 
> imho, low-cost CPEs are key if one wants to seriously see IPv6 deployed
> significantly. it would be a significant contribution to break
> chicken/egg-type problems...
> 
> 
>> providers provide dual stack, then of course, CPEs with allow dual stack on
>> the WAN link are needed.
>> 
>> Regards,
>> Jordi
> 
> 
> Best Regards,
> 
> -------------------------------------------------------------------------
> Carlos Friac,as                                            See:
> Wide Area Network Working Group (WAN)                      www.gigapix.pt
> FCCN - Fundacao para a Computacao Cientifica Nacional      www.ipv6.eu
> Av. do Brasil, n.101                                       www.6diss.org
> 1700-066 Lisboa, Portugal, Europe                          www.geant2.net
> Tel: +351 218440100 Fax: +351 218472167
> www.fccn.pt
> -------------------------------------------------------------------------
>            The end is near........ see http://ipv4.potaroo.net
>   "Internet is just routes (217118/774), naming (billions) and... people!"
> 
> 
> Aviso de Confidencialidade
> Esta mensagem e' exclusivamente destinada ao seu destinatario, podendo
> conter informacao CONFIDENCIAL, cuja divulgacao esta' expressamente
> vedada nos termos da lei. Caso tenha recepcionado indevidamente esta
> mensagem, solicitamos-lhe que nos comunique esse mesmo facto por esta
> via ou para o telefone +351 218440100 devendo apagar o seu conteudo
> de imediato.
> 
> Warning
> This message is intended exclusively for its addressee.
> It may contain CONFIDENTIAL information protected by law. If this
> message has been received by error, please notify us via e-mail or by
> telephone +351 218440100 and delete it immediately.
> 




**********************************************
The IPv6 Portal: http://www.ipv6tf.org

Bye 6Bone. Hi, IPv6 !
http://www.ipv6day.org

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.