Re: [6bed4-devel] 6bed4 at RIPE65, draft status, anycast coming up

[Rick v. R. <ri...@op...>]

Hello Eric,

> Contratulations on getting the addresses.

Thanks :)

I haven't forgotten your input by the way...

Your thought of using STUN actually seems possible, if you add TURN
and apply RFC 6156.  It's not as symmetric though; sent and received
data differ.  Also, the user accounts complicate things for end users.

> I will just repeat my general impression that 6bed4 is a wonderful idea,
> and that attempts to bypass the 6bed4 gateway are likely too much pain
> for too little gain.

Interestingly, your suggestion of Secure Neighbor Discovery is now
playing through my mind... because ideally we'd connect other IPv6
ranges to a 6bed4 peer (provided the other peer can support it
with an interface that just doesn't happen to be the default) and
I'm playing with the thought of using Redirect messages for that,
with some form of security.  This could redirect a 6bed4 peer's
attempt to reach a native address to a 6bed4 address that lives
on the same machine; this bypasses the public service even for
those classes of traffic.


We should have the new addresses setup on Monday, and I hope to
have an adapted tunnel code tested and ready to go at that time
too.  Anytime now :)


Cheers,
 -Rick