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

Re: [lisp] LISP Mobility Architecture

From: Jari Arkko <jari.arkko at piuha.net>
To: "Darrel Lewis (darlewis)" <darlewis at cisco.com>
Cc: Robin Whittle <rw at firstpr.com.au>, lisp at ietf.org
Date: Tue, 01 Sep 2009 21:27:48 +0300
In-reply-to: <C0ACCB7B60E6F14B9AC46D742C1009A150839E at xmb-sjc-213.amer.cisco.com>
References: <7070C816-A8C3-4D21-AFEA-82A70203E573 at lilacglade.org> <08697F25-CB21-404D-8115-B8D61CC7B298 at cisco.com> <BFE1CA06-E22C-4B89-A856-9EAB5AFA5E43 at lilacglade.org> <D399F598-8F02-43B0-81D2-E3BB495CE26F at cisco.com> <4A956451.3010801 at piuha.net> <73740BB1-5C85-4DD0-B0AF-68B20D990C92 at cisco.com><tslab1esosk.fsf at mit.edu> <4A9D641F.3090209 at firstpr.com.au> <C0ACCB7B60E6F14B9AC46D742C1009A150839E at xmb-sjc-213.amer.cisco.com>

Then maybe I need to be clearer. Mobility and many other advancedfeatures are out of scope. For now. When you complete the basespecifications, we can talk about rechartering to add more features.


Jari

Follow-Ups:
- Re: [lisp] LISP Mobility Architecture
  - From: Darrel Lewis (darlewis)

References:
- [lisp] LISP Mobility Architecture
  - From: Margaret Wasserman
- Re: [lisp] LISP Mobility Architecture
  - From: Dino Farinacci
- Re: [lisp] LISP Mobility Architecture
  - From: Margaret Wasserman
- Re: [lisp] LISP Mobility Architecture
  - From: Dino Farinacci
- Re: [lisp] LISP Mobility Architecture
  - From: Jari Arkko
- Re: [lisp] LISP Mobility Architecture
  - From: Dino Farinacci
- Re: [lisp] LISP Mobility Architecture
  - From: Sam Hartman
- Re: [lisp] LISP Mobility Architecture
  - From: Robin Whittle
- Re: [lisp] LISP Mobility Architecture
  - From: Darrel Lewis (darlewis)

Prev by Date: Re: [lisp] LISP Mobility Architecture
Next by Date: Re: [lisp] LISP Mobility Architecture
Previous by thread: Re: [lisp] LISP Mobility Architecture
Next by thread: Re: [lisp] LISP Mobility Architecture
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.