Re: [netlmm] RtSol messages and draft-sarikaya-netlmm-prefix-delegation-00.txt

Behcet Sarikaya <behcetsarikaya@yahoo.com> Tue, 15 May 2007 15:35 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 1Hnz3R-0005Ig-Am; Tue, 15 May 2007 11:35:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hnz3Q-0005Ib-LR for netlmm@ietf.org; Tue, 15 May 2007 11:35:12 -0400
Received: from web84112.mail.mud.yahoo.com ([68.142.206.199]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Hnz3P-0002uC-52 for netlmm@ietf.org; Tue, 15 May 2007 11:35:12 -0400
Received: (qmail 69746 invoked by uid 60001); 15 May 2007 15:35:10 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=QU52rW2WAx2EtJ1c87HG/R1TQ+0m91CZO4is9ZdK9pZVJkGvs6YQupLHMT8jlVksnuuQiY69CU1IlpZdneGV0hL7UACT0C3Bi+pwwg4JCnDig86HWHOUkIyTsvsFbBJNuR+LZtQq+AzEusAPLoiTMvfLnU79G9h08oOZ+MSDmvc=;
X-YMail-OSG: I79SqZAVM1lcVWnk4xsGdX77MEOaDtkhXf2C3.kJ2msbDXV9kWjCx6QILbN2iaB5zSj9pH5bIEwgVnTtE5xWE1NOuxrkHE5o8N3qcFZJhjcc62rMOZle1T8uNLU9Fw--
Received: from [206.16.17.212] by web84112.mail.mud.yahoo.com via HTTP; Tue, 15 May 2007 08:35:10 PDT
X-Mailer: YahooMailRC/478 YahooMailWebService/0.7.41.10
Date: Tue, 15 May 2007 08:35:10 -0700
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: [netlmm] RtSol messages and draft-sarikaya-netlmm-prefix-delegation-00.txt
To: Kalin Getov <getov@gmx.de>
MIME-Version: 1.0
Message-ID: <530147.68763.qm@web84112.mail.mud.yahoo.com>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: netlmm@ietf.org
X-BeenThere: netlmm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
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>
Content-Type: multipart/mixed; boundary="===============1074610386=="
Errors-To: netlmm-bounces@ietf.org

Let me refer this question to Sri, as our draft's main purpose is to show how prefix delegation can be used in as many scenarios as possible in PMIP6 and MIP6.

Regards,

Behcet

----- Original Message ----
From: Kalin Getov <getov@gmx.de>
To: Behcet Sarikaya <sarikaya@ieee.org>
Cc: netlmm@ietf.org
Sent: Tuesday, May 15, 2007 6:09:27 AM
Subject: Re: [netlmm] RtSol messages and draft-sarikaya-netlmm-prefix-delegation-00.txt

   Hello Behcet,

thanks for your answer,

yes I was keeping the base draft in mind, where the MAG should get the MN profile after authentication. Maybe in the next revision this will change. Is my assumption (to figs 3&4) that the RAs are sent event triggered after getting the HNP correct?  I mean without the need of small RA transmit intervals and timers.

Greetings,
Kalin




> Hello Kalin,
>   If I understood well, you are talking about the scenarios in Figs. 3&4
> which work as you described. In figs. 1 & 2, MAG does not have MN's profile
> (called policy store), so things start with RtSol.
>   Did I miss something?
> 
> --behcet
> 
> 
> ----- Original Message ----
> From: Kalin Getov <getov@gmx.de>
> To: netlmm@ietf.org
> Sent: Monday, May 14, 2007 7:51:16 AM
> Subject: [netlmm] RtSol messages and
> draft-sarikaya-netlmm-prefix-delegation-00.txt
> 
> 
> Hello all,
> 
> few toughts on the base draft and this
> (draft-sarikaya-netlmm-prefix-delegation-00) one, regarding PMIPv6...
> 
> is there a need to wait until the MN sends a RtSol message to the MAG?
> After a successful L2 access procedure the MAG gets the MN profile, right? If
> there is a HNP saved in the profile the MAG sends RA immediately, getting
> the prefix from it, if I got it correct. If not, the MAG waits until it gets
> the  home prefix from LMA or AAA, as described in 
> 
> draft-sarikaya-netlmm-prefix-delegation-00
> 
> only by initial connecton though, in the standard case (handover) the LMA
> already has a BCE for this MN with assigned HNP and sends it back with the
> PBAck message. One more time, should the MAG wait for RtSol from the MN? I
> prefer the case where the MAG sends the RA to the MN event triggered after
> successfuly getting the HNP in one way or another... This would accelerate
> the handover process also. 
> 
> 

-- 
******************************************
Best Regards
Kalin Getov

getov@gmx.de
******************************************

GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail




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