Re: [netlmm] timestamp vs seqno redux

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 07 September 2007 13:34 UTC

Return-path: <netlmm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ITdyM-00025z-Qv; Fri, 07 Sep 2007 09:34:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ITdyL-00025u-HY for netlmm@ietf.org; Fri, 07 Sep 2007 09:34:09 -0400
Received: from mail153.messagelabs.com ([216.82.253.51]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1ITdyK-0000eI-9c for netlmm@ietf.org; Fri, 07 Sep 2007 09:34:09 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-5.tower-153.messagelabs.com!1189172047!4661238!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [144.189.100.101]
Received: (qmail 32008 invoked from network); 7 Sep 2007 13:34:07 -0000
Received: from motgate2.mot.com (HELO motgate2.mot.com) (144.189.100.101) by server-5.tower-153.messagelabs.com with SMTP; 7 Sep 2007 13:34:07 -0000
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231]) by motgate2.mot.com (8.12.11/Motorola) with ESMTP id l87DY2QQ023056; Fri, 7 Sep 2007 06:34:06 -0700 (MST)
Received: from az10vts03 (az10vts03.mot.com [10.64.251.244]) by az33exr01.mot.com (8.13.1/Vontu) with SMTP id l87DY1H8013047; Fri, 7 Sep 2007 08:34:01 -0500 (CDT)
Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117]) by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id l87DXw3v012957; Fri, 7 Sep 2007 08:33:59 -0500 (CDT)
Message-ID: <46E15341.4060102@gmail.com>
Date: Fri, 07 Sep 2007 15:33:53 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ahmad Muhanna <amuhanna@nortel.com>
Subject: Re: [netlmm] timestamp vs seqno redux
References: <46DFC1C7.9060103@gmail.com> <01dc01c7f0c0$3e238210$d4f6200a@amer.cisco.com> <46E0784F.2090904@gmail.com> <6FC4416DDE56C44DA0AEE67BC7CA4371169906A0@zrc2hxm2.corp.nortel.com>
In-Reply-To: <6FC4416DDE56C44DA0AEE67BC7CA4371169906A0@zrc2hxm2.corp.nortel.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 000773-1, 06/09/2007), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
X-Spam-Score: -4.0 (----)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: netlmm <netlmm@ietf.org>
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

Ahmad Muhanna wrote:
[...]
>>> But, if the LMA falls back to the seq number based approach and 
>>> if there are no context transfers, there is always an extra round
>>>  trip for each MN registration (at handoff).
>> No, not always an extra round trip necessary.  (For our audience: 
>> in private I've discussed with Ahmad and Sri at least three 
>> possible ways to sync these seqnos and two of them assumed extra 
>> round trips.)
> 
> {Ahmad] Alex, the fact that we did not continue the offline 
> discussion is because you preferred to bring this to the mailing list
>  which is absolutely fine with me. It does not mean that I agreed
> with any of your proposals.

Right, I know, you didn't agree, and I didn't imply you agreed.  I agree
with you on this.

> You keep saying that the SQN can be provided by the LMA via a 
> profile. I want you to be specific here, tell me how that would work.
>  In details.
> 
> My understudying that profile comes from a policy server or whatever.
>  The SQN is a per-MN dynamically always changing. In your response 
> please consider how the LMA will always update the profile with the 
> last SQN.

Ahmad, when first the 'profile' is delivered by the 'policy server' or
whatever to the MAG then the LMA inserts the current seqno in that
profile.  It is not necessary to insert every time, just the first time
the MN authenticates.  This is the same  time when the home prefix (the
one that has to be put in the RA) is delivered in that same profile.

Don't you think this can work?  Why not?  Why can the LMA send to MAG
the home network prefix of the MN but not its current seqno?

Alex

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

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