NAT-based solution (sessions can survive
>> failover).
> What do people think about Fred Templin's IRON multihomed tunneling
> approach (or LISP, I guess it can do it)? IRON should give you
> multihoming with stable IPv4 and IPv6 PA prefixes, even for incoming
> traffic. It'
>> o Trust model (how much trust is put in whom so that connectivity works)
>> o How much state where
>> o Security implications (where are the weak links, vectors for attack)
>> o Traffic engineering (ingress and egress) features
>> o Session survivability on rerouting (manual and due to outages)
On Sat, Aug 20, 2011 at 2:37 PM, Daniel Roesen wrote:
> On Sat, Aug 20, 2011 at 01:57:36PM -0700, Randy Bush wrote:
>> as you can see, i am interested in
>> o loc/id separation
>> o rounting table scaling
>> o deployability on the internet
>> o current state of development
>>
>> what did i
On Sat, Aug 20, 2011 at 01:57:36PM -0700, Randy Bush wrote:
> as you can see, i am interested in
> o loc/id separation
> o rounting table scaling
> o deployability on the internet
> o current state of development
>
> what did i miss? what major attributes interest you?
o Trust model (how
i am told that the following session has been accepted for the nanog
agenda.
A Comparison of Approaches to Loc/ID, Routing Scaling, and the
Universe
Abstract:
This session looks at and contrasts:
LISP (Dino Farinacci)
ILNP (Saleem Bhatti)
RFC 6296 (Fred Baker
ate)
> with will be much smaller than the network as a whole?
Why would you assume this to be true if LISP also promises to make
multi-homing end-sites cheaper and easier, and independent of the
ISP's willingness to provide BGP without extra cost? You see, if
every SOHO network and "
you want to give ops feedback to the ietf, well ...
i suggest a loc/id session at the next nanog, 20-30 mins each for
LISP
ILNP
6296
where each is explained at an architectural level in some detail with
also a predeterimied list of questions such as "how does this address
loc/id separ
On Jul 14, 2011, at 10:49 AM, Randy Bush wrote:
> not to quibble but i thought 6296 was stateless.
AFAICT, the translators themselves are just rewriting addresses and not paying
attention to 'connections', which is all to the good. But then we get to this:
-
5.2. Recommendations for App
> I also view RFC6296 as a perpetuation of the clear violation of the
> end-to-end principle (i.e., ' . . . functions placed at low levels of
> a system may be redundant or of little value when compared with the
> cost of providing them at that low level . . .') embodied in the
> abomination of NAT
On Jul 13, 2011, at 11:02 PM, Ronald Bonica wrote:
> - enumerate the operational problems solved by LISP
Separation of locator/ID is a fundamental architectural principle which
transcends transport-specific (i.e., IPv4/IPv6) considerations. It allows for
node/application/services agility,
On Jul 13, 2011, at 12:02 PM, Ronald Bonica wrote:
> At this point, it might be interesting to do the following:
>
> - enumerate the operational problems solved by LISP
> - enumerate the subset of those problems also solved by RFC 6296
> - execute a cost/benefit analysis on both
tural purity.
At this point, it might be interesting to do the following:
- enumerate the operational problems solved by LISP
- enumerate the subset of those problems also solved by RFC 6296
- execute a cost/benefit analysis on both solutions
Ron
> -
t: TXT=73700 bytes) (Status: EXPERIMENTAL)
>>
>> which also could be considered to be in the loc/id space
>>
>> randy
>
> No, that's a misuse of "loc/id" since no identification is involved,
> even at the network layer -- but it is in the "reduce issues
On Wed, Jul 13, 2011 at 11:09, Fred Baker wrote:
> I think ILNP is a great solution. My concern with it is that the needed
> changes to TCP and UDP are not likely to happen.
I guess I should clarify: I think ILNP is elegant. But the real
Internet evolves incrementally, and only as needed. Othe
;loc/id" since no identification is involved,
>> even at the network layer -- but it is in the "reduce issues in global
>> routing and local renumbering" space (that's part of what LISP does).
>>
>> Cameron: As for ILNP, it's going to be difficult to g
On Jul 13, 2011, at 10:39 AM, Scott Brim wrote:
> Cameron: As for ILNP, it's going to be difficult to get from where
> things are now to a world where ILNP is not just useless overhead.
> When you finally do, considering what it gives you, will the journey
> have been worth it?
On Jul 13, 2011 7:50 AM, "Seth Mos" wrote:
>
> Op 13-7-2011 16:09, Randy Bush schreef:
> > > btw, a litte birdie told me to take another look at
>
> The free Open Source FreeBSD based pfSense firewall supports this. Not
> everyone can get BGP, specifically calling out residential connections
here.
2011. (Format: TXT=73700 bytes) (Status: EXPERIMENTAL)
> >
> > which also could be considered to be in the loc/id space
> >
> > randy
>
> No, that's a misuse of "loc/id" since no identification is involved,
> even at the network layer -- but it is in the "
Op 13-7-2011 16:09, Randy Bush schreef:
> > btw, a litte birdie told me to take another look at
The free Open Source FreeBSD based pfSense firewall supports this. Not
everyone can get BGP, specifically calling out residential connections here.
As a 1:1 NAT mechanism it works pretty well, I can re
o be in the loc/id space
>
> randy
No, that's a misuse of "loc/id" since no identification is involved,
even at the network layer -- but it is in the "reduce issues in global
routing and local renumbering" space (that's part of what LISP does).
Cameron: As
btw, a litte birdie told me to take another look at
6296 IPv6-to-IPv6 Network Prefix Translation. M. Wasserman, F. Baker.
June 2011. (Format: TXT=73700 bytes) (Status: EXPERIMENTAL)
which also could be considered to be in the loc/id space
randy
On Wed, Jul 13, 2011 at 2:27 AM, Randy Bush wrote:
>> I fear that at its worst and most successful, LISP ensures ipv4 is the
>> backbone transport media to the detriment of ipv6 and at its best, it
>> is a distraction for folks that need to be making ipv6 work, for real.
&g
>> i will not dispute this, not my point. but i have to respect dino and
>> the lisp fanboys (and, yes, they are all boys) for actually *doing*
>> something after 30 years of loc/id blah blah blah (as did hip). putting
>> their, well dino's, code where their mouth
On Jul 12, 2011 5:21 PM, "Randy Bush" wrote:
>
> > W.R.T. to LISP, in defense of the IETF or the IRTF, i do not believe
> > "the IETF" has told the world that LISP is the best fit for the
> > Internet or solves any specific problem well.
> >
> &g
> W.R.T. to LISP, in defense of the IETF or the IRTF, i do not believe
> "the IETF" has told the world that LISP is the best fit for the
> Internet or solves any specific problem well.
>
> The IETF has never said the "Internet Architecture" is going to LISP
iable 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
able 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
>
> On Mon, Apr 11, 2011 at 10:49 AM, Christina Klam wrote:
- - ---
Jason
- Original Message -
> From: "harbor235"
> http://www.lisp4.net/
So, for The Rest Of Us, 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. :-)
Cheers,
-- jra
Dear Christina,
On 11 Apr 2011, at 16:49, Christina Klam wrote:
> 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 I
Thank you all.
On Apr 11, 2011, at 11:07 AM, Luigi Iannone wrote:
> 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
>
> On 11, A
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
On 11, Apr, 2011, at 16:49 , Christina Klam wrote:
> All,
>
> One of our ISP is planning to do a LISP deployment.
On 04/11/2011 05:02 PM, harbor235 wrote:
> http://www.lisp4.net/
Agreed, this is the best starting point.
I'm working on a draft about LISP deployment, feedback is always welcome:
http://tools.ietf.org/html/draft-jakab-lisp-deployment
-Lori
> Mike
>
> On Mon, Apr 11,
On Mon, Apr 11, 2011 at 10:49:25AM -0400,
Christina Klam wrote
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
http://www.lisp4.net/
Mike
On Mon, Apr 11, 2011 at 10:49 AM, Christina Klam wrote:
> 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
>
>
>
>
>
>
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
On Sep 30, 2010, at 17:15 , Job W. J. Snijders wrote:
> Dear Cameron & everybody,
>
> On Wed, Sep 29, 2010 at 8:32 PM, Job W. J. Snijders
> wrote:
>
>>>> The fact that LISP does help in IPv6 Transition solutions (due to its
>>>> inherent AF agnost
Sorry guys,
> Have you already joined the LISP Beta Network? All you need is a
> router that can run the LISP images (871, 1841, 2821, 7200 etc)
>
> It's completely open, and the guys behind
> lisp-supp...@external.cisco.com can hook you up for free,
The correct
Dear Cameron & everybody,
On Wed, Sep 29, 2010 at 8:32 PM, Job W. J. Snijders wrote:
>>> The fact that LISP does help in IPv6 Transition solutions (due to its
>>> inherent AF agnostic design), is compelling. As you say, real end 2 end is
>>> the goal - and LISP h
Dear Cameron,
On Wed, Sep 29, 2010 at 3:27 AM, Cameron Byrne wrote:
>> The fact that LISP does help in IPv6 Transition solutions (due to its
inherent AF agnostic design), is compelling. As you say, real edge 2 edge is
the goal - and LISP helps here, regardless of the AF. (you'll will
a...@puck.nether.net wrote:
>>>
>>>> It's working over LISP:
>>>>
>>>> http://www.lisp4.facebook.com/
>>>> -----
>
>>> Wow, that's cool. I didn't know LISP had progressed that fa
Hi Cameron,
On 24 sep 2010, at 02:56, Cameron Byrne wrote:
> On Thu, Sep 23, 2010 at 5:33 PM, Scott Weeks wrote:
>> On Sep 23, 2010, at 5:50 PM, "Scott Weeks" wrote:
>>> --- ja...@puck.nether.net wrote:
>>
>>> It's working o
On Thu, Sep 23, 2010 at 5:33 PM, Scott Weeks wrote:
> On Sep 23, 2010, at 5:50 PM, "Scott Weeks" wrote:
>> --- ja...@puck.nether.net wrote:
>
>> It's working over LISP:
>>
>> http://www.lisp4.facebook.com/
>> --
On Sep 23, 2010, at 5:50 PM, "Scott Weeks" wrote:
> --- ja...@puck.nether.net wrote:
> It's working over LISP:
>
> http://www.lisp4.facebook.com/
> -
>
> LISP as in Locator/ID Separation Protocol?
---
Yes.
Jared Mauch
On Sep 23, 2010, at 5:50 PM, "Scott Weeks" wrote:
>
>
> --- ja...@puck.nether.net wrote:
> From: Jared Mauch
>
> It's working over LISP:
>
> http://www.lisp4.facebook.com/
> -----
>
>
--- ja...@puck.nether.net wrote:
From: Jared Mauch
It's working over LISP:
http://www.lisp4.facebook.com/
-
LISP as in Locator/ID Separation Protocol?
scott
It's working over LISP:
http://www.lisp4.facebook.com/
On Sep 23, 2010, at 3:39 PM, Ernie Rubi wrote:
> Anyone else having trouble? We're colo'ed at the NOTA in Miami and directly
> peer with them - even though our session hasn't gone down we still can't
>
aches propose to attach
locators to hosts while other prefer to attach locators only to routers.
The latter approach is the solution chosen by the proponents of the
Locator/Identifier Separation Protocol (LISP). LISP is a router-based
solution to solve the scaling problems of the Internet archite
47 matches
Mail list logo
