[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: I-D: Simple Configured Tunnel Setup Procedure
On Mon, 24 Nov 2003, JORDI PALET MARTINEZ wrote:
> My feeling on this is that most of the ISPs will not accept off-band
> procedures, and TSP seems useful to avoid that.
In my opinion if ISP wants to provide tunnel service they have to know in
advance that they will serve something - at least, in order to be able to
track the usage of service. If ISP is using RADIUS or Diameter
authentication for obtaining the customers' tunnel endpoint
addresses, they already had to have some form of agreement. It would be
very easy for the customer just ask IPv6 tunnel service via the
customer care center of ISP. Probably I would use this method to provide
IPv6 for DSL/dial-up or otherwise authenticated users.
Regards,
Janos Mohacsi
Network Engineer, Research Associate
NIIF/HUNGARNET, HUNGARY
Key 00F9AF98: 8645 1312 D249 471B DBAE 21A2 9F52 0D1F 00F9 AF98
> > 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
> >
>
> **********************************
> Madrid 2003 Global IPv6 Summit
> Presentations and videos on line at:
> http://www.ipv6-es.com
>
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
>
>
>
>