Re: [netlmm] Network-based mobility - NETLMM DT Solution Vs Asolutionbased on MIP6

"James Kempf" <kempf@docomolabs-usa.com> Fri, 27 October 2006 08:10 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdMnD-0001C5-9r; Fri, 27 Oct 2006 04:10:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdMnB-00011k-DP for netlmm@ietf.org; Fri, 27 Oct 2006 04:10:17 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225] helo=fridge.docomolabs-usa.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdMn8-0005gM-Vd for netlmm@ietf.org; Fri, 27 Oct 2006 04:10:17 -0400
Message-ID: <1a0401c6f99f$ab8d7a90$5f6015ac@dcml.docomolabsusa.com>
From: James Kempf <kempf@docomolabs-usa.com>
To: Roberts Phil-APR042 <Phil.Roberts@motorola.com>, "Narayanan, Vidya" <vidyan@qualcomm.com>, netlmm@ietf.org
References: <9018559E7B637042AFBA86C7BE62706FC76C01@de01exm67.ds.mot.com>
Subject: Re: [netlmm] Network-based mobility - NETLMM DT Solution Vs Asolutionbased on MIP6
Date: Fri, 27 Oct 2006 01:12:36 -0700
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc:
X-BeenThere: netlmm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NETLMM working group discussion list <netlmm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/netlmm>
List-Post: <mailto:netlmm@ietf.org>
List-Help: <mailto:netlmm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=subscribe>
Errors-To: netlmm-bounces@ietf.org

Folowing up on Phil's note, we haven't heard much comment on this thread 
from proponents of a pure PMIP solution. I'd like to distinguish between 
Vidya's comments and Phil's response which, I assume, are about the 
technical desirability of using the MIP6 Mobiity Header format to implement 
the NETLMM architecture and the two PMIP drafts that will be presented in 
the MIP6 WG. I'll let Phil and Vidya and anyone else who cares to comment 
work through the technical issues on that, I'm more interested in the two 
PMIP drafts.

Perhaps one of the authors of the two PMIP drafts that are to be presented 
in the MIP6 WG meeting would care to comment why they believe that PMIP is 
technically superior to the DT NETLMM solution? Arguments about probability 
of deployment or other such are interesting, but most decisions about 
alternatives in IETF are premised intitially on technical arguments. 
References to the WG's problem statement and goals drafts 
(draft-ietf-netlmm-nohost-ps-05.txt and draft-ietf-netlmm-nohost-req-05.txt, 
now with the IESG for publication approval) pointing out the superiority of 
PMIP for satisfying the goals that the WG has agreed to are likely to be 
especially convincing. The only comment I've heard so far is that the DT 
draft introduces unnecessary new terminology.

            jak 


_______________________________________________
netlmm mailing list
netlmm@ietf.org
https://www1.ietf.org/mailman/listinfo/netlmm