Re: [v6ops] slight comments on draft-vanrein-v6ops-6bed4-00

[Jeroen Massar <[e-mail]>]

On 2011-07-27 13:40 , Rick van Rein wrote:
> Hello Washam,
> 
> Thanks for commenting on my 6bed4 proposal.
> 
>> For first glance, i have a rough impression this draft has some
>> similarity with another draft written a while ago at least in terms of
>> udp encapsulation of ipv6. please refer to
>> http://tools.ietf.org/html/draft-lee-softwire-6rd-udp
> 
> I will look it up.  Packing it up in UDP is commonly done, and has
> shown to make a tunnel independent of the router used.  AICCU in
> the SIXXS project does it too, for instance.  And so does TSP from
> RFC 5572.

AICCU is a tool, the protocol that you mean is AYIYA.

Teredo, which is mostly stateless and already deploy would fit your
requirements quite well, especially as you are only connecting a single
host.

As your main 'requirement' is embedded system, you might want to look at
6lowpan and of course simple native IPv6.

But I really wonder why you mention that 'embedded' is so special while
having both a full IPv4 and IPv6 stack in it is actually the heaviest
portion you can have. Stripping the IPv4 stack would serve your purpose
much better.

Also if there is no native IPv6, then let an external device do the IPv6
gatewaying to the Internet.

Also you are forgetting about a VERY important aspect that Teredo does
solve: local traffic between hosts.

As your made-up global IPv6 address is based on the outmost IPv4-NAT IP
address + port (because otherwise the PoP would have to keep state), I
really wonder how you stick that address as a source address in the IPv6
header that is inside the IPv4 packet.

I can only suggest that you look at Teredo which solves most of these
issues with autoconfiguration and not state. Teredo matches most of your
'requirements'...

Greets,
 Jeroen