[LAC-TF] FAQ: Grupo2 - Pregunta "d"

[Nicolas Antoniello]

Agregando al comentario de Azael:

Algunos aspectos que podemos desarrollar un poco mas para la  
redacción de esta respuesta pueden ser:

* El hecho de que las redes podrían prescindir del uso de NAT, por lo  
que las aplicaciones tendrían "acceso directo" a dispositivos,  
servidores, clientes o servicios en general, que en el caso de IPv4,  
al ser parte de una red privada (detrás de un NAT) seria mas difícil  
y en algunos casos imposibles de acceder.

* La posibilidad de asignar direcciones a una infinidad de  
dispositivos y servicios "domésticos" o de usuario final (acceso a mi  
heladera, mi equipo de aire acondicionado, iluminación, agenda  
personal (hosteada en un servidor propio), etc...

* Hacer énfasis en la posibilidad de que un sinnúmero de dispositivos  
se comuniquen entre si en forma directa.

* Aplicaciones que aprovechen las ventajas de la movilidad en IPv6  
(aunque hay mucho para desarrollar aun en este "rubro").

* Aplicaciones que hagan uso de los mecanismos de auto-configuración  
para acceder o contactar otros dispositivos.



A continuacion, como ejemplo, cito unas cuantas ventajas que agrega  
IPv6 a Windows Meeting Space (http://technet.microsoft.com/en-us/ 
library/cc507850.aspx), que podriamos re-escribir para extraer  
algunas ventajas.


By using IPv6, Windows Meeting Space gains several advantages:

Ubiquitous addressing: IPv6 allows every Windows Meeting Space  
participant to have a unique global IP address. Though Windows  
Meeting Space is typically used on a single local area network (LAN),  
the feature supports meeting sessions that cross subnets or even span  
the Internet. By allowing each host to have a unique address, IPv6  
ensures that all Windows Meeting Space users can ultimately connect  
to each other without conflict. In the IPv4 world, the lack of  
available addresses has prompted the use of network address  
translation (NAT) devices that assign private, or hidden, addresses  
to each host; unfortunately, these private IPv4 addresses are not  
globally unique or routable, so client hosts cannot communicate with  
each other easily.
Improved connectivity: IPv6 facilitates improved end-to-end  
connectivity, enabling Windows Meeting Space sessions over the  
Internet. Microsoft Windows provides technologies such as Teredo and  
6to4 that enable end-to-end IPv6 connectivity over the existing IPv4  
Internet. Teredo allows IPv6-aware hosts to tunnel traffic to each  
other over the IPv4 Internet; Teredo is able to operate transparently  
through most existing NAT devices and home gateways. Teredo  
connectivity is transparent to IPv6 application developers, meaning  
that developers are freed from the worries of manual NAT traversal.  
On the other hand, IPv4 developers must often build and deploy custom  
NAT traversal techniques within their applications. The 6to4 protocol  
allows an Internet-connected host or router (such as a next- 
generation home gateway device) with a public IPv4 address to tunnel  
traffic over the IPv4 Internet. Again, the presence of 6to4  
connectivity is transparent to application developers.
Automatic address configuration: IPv6 enables Windows Meeting Space  
to deliver a fast and smooth ad-hoc networking experience. For each  
active network interface, clients automatically generate a unique  
link-local IPv6 address (suitable for communicating with other hosts  
on the subnet) without relying on the presence of a router or DHCP  
server to centrally assign addresses on that network. This address  
allocation scheme ensures that hosts can begin to communicate without  
any delay upon creating an ad-hoc wireless network or upon plugging  
into a network hub or switch. Although IPv4 supports ad-hoc  
networking, automatic network setup is traditionally slow.
Native support for security (IPsec): IPv6 provides native support for  
IPsec, allowing Windows Meeting Space to operate efficiently over  
both insecure and secure IP networks. Increasing numbers of  
enterprises are deploying IPsec to enable Server and Domain Isolation.
Compatibility with emerging government and national standards:  
Several government organizations, such as the United States Federal  
government, have mandated a transition to IPv6 for their internal  
systems; likewise, because of the short supply of IPv4 addresses,  
ISPs in various parts of the world—particularly Asia—are deploying  
native IPv6 support to their enterprises and consumers. By using  
IPv6, Windows Meeting Space can be deployed confidently with the  
knowledge that it will be compatible with these technology mandates.

Opiniones??

Saludos,
Nicolas.




On 15/04/2009, at 02:13 PM, Azael Fernandez Alcantara wrote:

> Buenas Tardes,
>
> Con el fin de ir preparando una respuesta:
>
> "En primera instancia, haciendolas independientes de la version del  
> protocolo de Internet, es decir, que no dependan de la dirreccion  
> IP para su funcionamiento, sino de un nombre asociado a una IP."
>
>
> SALUDOS
> ____________________________________
> Azael
>
> On Wed, 8 Apr 2009, Mariela Rocha wrote:
>
>>
>> Estimados:
>>
>> Continuamos con la siguiente pregunta de la FAQ..
>>
>>
>> Sección: Relacionadas al software y aplicaciones
>> Pregunta:
>> d. ¿Cómo lograr aplicaciones que aprovechen las ventajas de IPv6?
>>
>>
>> Esperamos sus opiniones hasta el dia miércoles 15 de Abril.
>>
>> Saludos,
>>
>> Mariela.-
>> _______________________________________________
>> LACTF mailing list
>> LACTF at lacnic.net
>> https://mail.lacnic.net/mailman/listinfo/lactf
> _______________________________________________
> LACTF mailing list
> LACTF at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lactf

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.lacnic.net/pipermail/lactf/attachments/20090415/debbf6b3/attachment.html>