Re: [BEHAVE] FW: I-D Action:draft-arkko-ipv6-only-experience-00.txt

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> Behalf Of Jari Arkko
> Sent: Wednesday, July 07, 2010 1:55 AM
> To: Iljitsch van Beijnum
> Cc: Behave WG
> Subject: Re: [BEHAVE] FW: I-D Action:draft-arkko-ipv6-only-experience-
> 00.txt
> 
> Iljitsch,
> 
> > Good stuff, Jari.
> >
> 
> Thanks for your feedback!
> 
> > However, the title doesn't really cover the content, as NAT64 is not
> mentioned in the title. This could be confusing.
> >
> 
> We'll consider this. There's really multiple components in our setup --
> running on IPv6-only local network, doing our
> local/IETF/googling/facebookking services over IPv6, having a NAT64
> somewhere on the path to the global Internet, and so on.
> 
> > I would also mention that using a dual stack HTTP proxy is an easy
> way for IPv6-only systems to reach IPv4 literals over HTTP.
> >
> 
> Yes it is. We should add more pointers to alternative configurations.
> (Btw, is there a convenient IETF RFC that discusses the IPv6-only web
> proxy setup?)


http://tools.ietf.org/html/draft-wing-behave-http-ip-address-literals-02

-d


> > Too bad you didn't look at bittorrent, this is pretty much a horror
> story.
> >
> 
> Bittorrent and other P2P stuff is on our list of things to do. I would
> love to download^H^H^H^H^H^H^H^H know what happens. Have you tried
> since
> you say its a horror story?
> 
> Jari
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave