[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [RAM] Ivip (was ViP ...) placement



The note on the list comparing lvip with Mobile IP suggested a question in my mind.

In LISP. the TR (the device provides I and E functionality) is providing service directly to a specific set of customers. Its capacity is tied to those customers, and it is operated either by those customers or by the ISP associated with those customers. If we assume that there is value in having this, one can envision how the capability gets paid for.

If there is a rendezvous point somewhere off in the net, advertising a short prefix, and then disagregating that prefix into tunnels, that device is operated by someone. But that someone is not the customer whose blocks are being advertised, nor is it the ISP serving those customers. This leads to both authentication questions (how do you know this rendezvous box is allowed to issue that advertisement) and business model questions (how does it get paid for?

While conceptually decomposing the devices and separating the deployment is attractive, I fear that there are issues raised by such a separation that require attention.

Yours,
Joel


_______________________________________________ RAM mailing list RAM at iab.org https://www1.ietf.org/mailman/listinfo/ram