LISP

All,

One of our ISP is planning to do a LISP deployment. (1) Does anyone know if Sprint uses LISP? (2) Does anyone know of any good guides/documentation of LISP?

Thank you,
Christina Klam

http://www.lisp4.net/

Mike

a message of 12 lines which said:

(1) Does anyone know if Sprint uses LISP?

It is too early, IMHO, to have production deployments of LISP (testing
is OK).

(2) Does anyone know of any good guides/documentation of LISP?

For Cisco users, I like
<http://blog.fryguy.net/2011/04/07/lisp-locator-identifier-separation-protocol-say-what/&gt;

http://www.lisp4.net/

Agreed, this is the best starting point.

I'm working on a draft about LISP deployment, feedback is always welcome:

-Lori

Hi,

I think that the best repository of documentation is lisp4.net.

I would also have a look to
https://datatracker.ietf.org/doc/draft-jakab-lisp-deployment/

Luigi

Thank you all.

Dear Christina,

One of our ISP is planning to do a LISP deployment. (1) Does anyone know if Sprint uses LISP? (2) Does anyone know of any good guides/documentation of LISP?

I cannot answer question 1.

But I do work for an ISP that's rolling out LISP. :slight_smile: Here is some links that
might help answer questions 2:

Some of the following links are slightly dated because some LISP
implementations have been actively developed the last year.

This is a multi-organisation website, to coordinate the LISP beta network
and provide general information: http://www.lisp4.net/

Here is cisco's configuration guide:
http://www.cisco.com/en/US/docs/ios/lisp/configuration/guide LISP_configuration_guide.pdf

Here are some nice blogposts that cover various subjects:

http://blog.fryguy.net/2011/04/07/lisp-locator-identifier-separation-protocol-say-what/
http://blog.fryguy.net/2011/04/08/more-lisp-using-it-to-enable-ipv6-over-ipv4/

http://blog.pattincon.com/lisp-data-plane
http://blog.pattincon.com/practical-lisp-basic-control-plane
http://blog.pattincon.com/lisp

http://blog.snijders-it.nl/2010/11/lisp-getvpn-as-alternative-for.html

http://blog.ine.com/2010/07/05/a-high-level-overview-of-lisp/

Kind regards,

Job

So, for The Rest Of Us<tm>, LISP is an attempt to reduce the impact of PI
space on router tables in the DFZ?

WADR, to hell with them; they have a *lot* more money than I do. :slight_smile:

Cheers,
-- jra

- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

http://www.lisp4.net/

This sounds a lot like LNP in the telco world. Is the goal here to make IP's "portable" ? Or is this a viable way to access IPv6 from either an IPv4 host or an IPv6 host unfortunate enough to not have full IPv6 tables?

And do all of the networks you pass through have to be LISP enabled?

Mike

- - ---------------------------
Jason 'XenoPhage' Frisvold
xenophage@godshell.com
- - ---------------------------
"Any sufficiently advanced magic is indistinguishable from technology."
- - - Niven's Inverse of Clarke's Third Law

- -----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)

iEYEARECAAYFAk2jl6UACgkQ8CjzPZyTUTSmRACeJWp4KxPgZAgIJJBHOXwmPybS
Nb0An1KzzLMxBqHP7Yu4pgW4tcA5EcoK
=HJL5
- -----END PGP SIGNATURE-----

> http://www.lisp4.net/

This sounds a lot like LNP in the telco world. Is the goal here to
make IP's "portable" ?

One of the goals, yes.

Or is this a viable way to access IPv6 from either an IPv4 host or an
IPv6 host unfortunate enough to not have full IPv6 tables?

LISP will not do translation for you, so an IPv6-only host will not be
able to talk to an IPv4-only host by just using LISP. However, solving
the problem of not having full IPv6 tables is possible in two ways: 1)
you use IPv4 locators so basically tunnel the traffic over IPv4; or 2)
use a proxy tunnel router that does have access to full IPv6 tables.

And do all of the networks you pass through have to be LISP enabled?

Ideally, the source and destination networks both have to be LISP
enabled, the core doesn't have to know anything about LISP. It is
however possible for LISP enabled sites to communicate with sites not
deploying LISP, using proxy tunnel routers deployed by third parties.
For more discussion about how this might be deployed see Section 4 of
the LISP deployment document:

Regards,