Hi Dino,

I mostly agree with all of your comments regarding the current text (with
some nuances of course), but I think that we can carry on that discussion
on London. However, let me address something here.


On Wed, Feb 19, 2014 at 8:34 AM, Dino Farinacci <[email protected]> wrote:

> > http://tools.ietf.org/html/draft-rodrigueznatal-lisp-sdn-00
>
> Alberto, enclosed are my comments. The draft text comes first and is
> indented and my comments follow.
>
> > Abstract
> >
> >    This document describes extensions for the Locator/ID Separation
> >    Protocol (LISP) to make it more suitable to be used on Software
> >    Defined Networking (SDN) scenarios.
>
> As others have said this draft is probably mis-titled. SDN, in
> understandable form, is a mechanism to program network devices. This spec
> says nothing about the programmability and more about how to do map-cache
> lookups locally in the xTR and how to what lookup-key should be used for
> mapping database lookups


My idea with the draft is to address all the extensions (with all the
required technical detail) to enhance LISP+SDN deployments, that's the
reason for the name. Please keep in mind that this is just a -00 version
and most of the content is still to be written. Despite the fact that the
text now refers mostly to flow aspects, my intention is to address other
points (such Publish/Subscribe mechanism, etc) on the near future.

I would prefer to keep all SDN related stuff here to avoid the
proliferation of drafts. If in the future we see that some parts (like what
you call "LISP granular map-caches") require too much technical detail,
then we should consider the spin-off of those parts to different drafts and
keep this draft as a "SDN umbrella" (as Michiel suggested).

At this point this draft is a tool to work on all the SDN specific aspects
of LISP and to generate some discussion.

Let's talk in London ;)

Alberto
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp

Reply via email to