Re: I-D: Simple Configured Tunnel Setup Procedure

[Pekka Savola <pekkas@netcore.fi>]

Hi,

Thanks for the comments. (Btw, you might want to resubscribe with the 
address you use because the mails bounce to the list admin.)

On Thu, 20 Nov 2003, Marc Blanchet wrote:
> my reading is that:
> - good idea.
> - if you go more into the details which makes a complete solution, you will
> end up redoing either tunnel broker or tunnel broker with TSP.
> - TSP automates the creation of tunnels with no complexity or overhead. and
> it manages the delegation of prefixes, the mobility of the v4 side (i.e.
> change of v4 address), can be part of a boot sequence of a node or router,
> etc... 
> - basically, you need a signaling protocol of some sort to help the two
> parties involved to setup the tunnel (and the various additional needed
> info, such as prefix allocation, ...)

I do not believe there is a need for signaling protocol at all, and I 
think the memo tries to proof-of-concept this.

You can manage the change of v4 address without a protocol; there are
already protocols for prefix delegation and they can be reused, etc.
(Obviously, if there is a need for a simpler prefix delegation
mechanism than DHCPv6, that's a separate issue on its own.)

I considered TSP before starting to write this, but I could not 
justify the signaling protocol overhead and complexity to myself, as 
there clearly didn't seem to be a need for one.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings