Re: [lisp] LISP SDN

Joel,

This is exactly the kind of discussion we wanted to trigger with this draft
submission. Your questions are much appreciated. Most of issues you raised
do not have a clear answer yet. There is ongoing discussion among the draft
authors on how to best address those points. Let me try to provide some
light on what is the plan.

At this point we are focusing on exact match tuple lookups. That's a
reasonable goal that can be achieved somehow easily with a DHT-like Mapping
System. As you pointed wisely, prefix matches on multiple fields increases
hugely the complexity. We would like to cover those too, but currently we
are studying which would be the best way to do so, and if the necessary
trade-offs would make prefix lookup worthwhile. Maybe at some point we will
need to limit prefix lookup to a certain number of fields or to a certain
size of network deployments.

As for MS selection, we assume now that it is preconfigured on the devices.
Currently, we are also only considering the case of an internal deployment
where all the elements are SDN-capable and the whole deployment is
SDN-oriented. How a xTR serving conventional operation and SDN operation
should behave is to further study.

Thanks,
Alberto

On Tue, Feb 18, 2014 at 2:20 AM, Joel M. Halpern <jmh@joelhalpern.com>wrote:

> I would really like to see an answer to how these n-tuple matches are
> supposed to work with prefix matches on various fields.
> What is the match algorithm?
> What assumptions are placed on the mapping system to support these tuples?
> How will the ETR know that the mapping system it is talking to supports
> this capability?  In particular, what if the same device is serving as an
> ETR for conventional operations and for these enhanced operations. Does it
> need to be configured to know which map server handles which mode?  Does it
> guess?  Is the same map server required to handle both?
>
> Yours,
> Joel
>
>
> On 2/17/14, 11:45 AM, Alberto Rodriguez-Natal wrote:
>
>> Dear all,
>>
>> We have submitted a new draft, "SDN extensions for LISP", that you can
>> find here:
>>
>> http://tools.ietf.org/html/draft-rodrigueznatal-lisp-sdn-00
>>
>> We believe that LISP can serve as a southbound protocol for SDN. With
>> this draft we aim to improve vanilla LISP with some extensions to make
>> it even more suitable for SDN scenarios.
>>
>> This draft also complements and provides the foundations for the current
>> LISP NFV draft.
>>
>> http://tools.ietf.org/html/draft-barkai-lisp-nfv-04
>>
>> Your thoughts and feedback on both drafts are more than welcome.
>>
>> Best,
>> Alberto
>>
>>
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp
>>
>>