Michiel,
I'm afraid that I still disagree.
To date, a major shortcoming in the LISP document set is that explains protocol
machinery in great detail, but never really explains:
- What problem it is trying it solve
- Whether the protocol machinery offered is both necessary and
sufficient to solve the problem
IMHO, the purpose of the introduction and architectural perspective documents
was to remedy this shortcoming. Given that LISP's primary claim was to separate
locator semantics from identifier semantics, it is very appropriate that Noel
should introduce this discussion very early in the document.
Ron
From: Michiel Blokzijl (mblokzij) [mailto:[email protected]]
Sent: Monday, August 05, 2013 9:29 AM
To: Ronald Bonica; Noel Chiappa
Cc: <[email protected]>
Subject: Re: [lisp] Comments on draft-ietf-lisp-introduction-01
Hi Ronald,
Sorry, it was not my intention to "sweep this detail under the carpet".
I think there's nothing wrong with discussing it in general, I just thought
that typically you'd explain the protocol first, and then the limitations when
the reader has a bit more of an understanding of the protocol (sometimes even
in a separate draft, like http://www.ietf.org/rfc/rfc4116.txt, whatever makes
sense I guess). I thought section 4 might be a potential starting point for
people who want to find out what LISP is about without reading all of the
background material. Basically, it was meant more as a structural/ordering
comment.
Also, I should have qualified the "discuss it at all" with "in this draft".
Thank you for your feedback!
Michiel
From: Ronald Bonica <[email protected]<mailto:[email protected]>>
Date: Monday, 5 August 2013 13:58
To: Michiel Blokzijl <[email protected]<mailto:[email protected]>>, Noel
Chiappa <[email protected]<mailto:[email protected]>>
Cc: "<[email protected]<mailto:[email protected]>>"
<[email protected]<mailto:[email protected]>>
Subject: RE: [lisp] Comments on draft-ietf-lisp-introduction-01
Michiel,
I strongly disagree.
LISP's primary claim is separation of locator and identifier semantics.
However, that separation is not perfect. If fact, one might argue that it is no
more perfect that the separation that is achieved by an L3VPN.
If we were to sweep this detail under the carpet, the reader would figure it
out for himself, and wonder about what else might be under that carpet.
Ron
4. LISP Overview
LISP is an incrementally deployable architectural upgrade to the
existing Internet infrastructure, one which provides separation of
location and identity. The separation is usually not perfect, for
reasons which are driven by the deployment philosophy (above), and
explored in a little more detail elsewhere (in [Perspective], Section
"Namespaces-EIDs-Residual").
The first bit is probably OK, the second one I think doesn't add much value
here, apart from saying that "if you want to look at some imperfections, go
here". I'd move it into a later section if you need to discuss it at all.
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp
