[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RRG] Nimrod, NIIA, HIP... as a long term solution?

Just as a data point: Some people (e.g. SMA folks at Boeing) are already deploying HIP for specific purposes, and there is at least one IETF standards track WG (P2PSIP) that considers using HIP as a component for their solution. In general, you often (but not necessarily 100% always) can deploy HIP without changing anything underneath or above; we listed some options in our IETF 62 plenary talk in 2005 [1].
Hence, HIP is no longer "long term" in that sense. It not only has been fully specified and implemented (three interoperating open source implementations), but some folks have started to deploy it.
However, HIP as-of-today is not a solution to the routing scalability problem. It is a solution (component) to those folks that need to combine security, mobility, and multi-homing. To help with the routing scalability problem, a large fraction of the community would need to adopt HIP, either directly or through some type of proxying [2]. While that may happen "naturally" (i.e. though market penetration), it is far too early to tell if such wide scale adoption of HIP will ever take place. Anyway, if if anyone is interested in going further into that direction, I guess someone should flesh out the HIP proxy scenarios briefly outlined in [2]. 

--Pekka Nikander
[1] Slides 14-25 of http://www.tml.tkk.fi/~pnr/presentations/IETF62- Plenary-HIP-RG-05-03-10.pdf 
[2] http://tools.ietf.org/html/draft-nikander-ram-generix-proxying-00

On 28 Sep 2007, at 05:33, Robin Whittle wrote:


In the thread "End user network size [ [Q] draft-farinacci-lisp:
IPv4 address depletion]", Heiner Hummel wrote, in part:


But imho the future solution isn't LISP and similars, instead
it will be Nimrod however being put on its feet.


LISP, eFIT-APT, Ivip and TRRP are intended to be incrementally
deployable now or in the next few years - I guess with the idea they
are deployed substantially by 2012.

Heiner, do you have a proposal by which Nimrod:

  http://tools.ietf.org/html/rfc1992

could be incrementally deployed, for IPv4 and IPv6?

If not, then I think that Nimrod should not be compared with LISP
etc. but should be considered as a long-term solution, to be
introduced by means as yet unknown.

Likewise NIAA (Node Identity Internetworking Architecture):

  http://tools.ietf.org/html/draft-schuetz-nid-arch-00

I think that whatever comes out of the LISP etc. discussions needs
to be as compatible as possible with whatever might come next.

  - Robin



--
to unsubscribe send a message to rrg-request@psg.com with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg




--
to unsubscribe send a message to rrg-request@psg.com with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg