RE: [netlmm] Significance of MN-Identifier

Hi Alper,

There were some comments on this from Jari. See the section
on "Acquiring the MN identifier" (Sec 6.6).

The MN-Identifier may not be the real identifier of the MN.
But, the LMA and MAG must be able to identify a MN using
this identifier and exchange it in the signaling messages.

Also, but, it is not the identifier of the MAG. We are
creating a BCE state and that is for a MN. The identifier
of the MAG is used for authenticating and authorizing purposes.
And this identifier changes at each handoff and so what is
stored in the BCE is the MN identifier.

Sri

> -----Original Message-----
> From: Alper Yegin [mailto:alper.yegin@yegin.org] 
> Sent: Monday, September 10, 2007 4:27 AM
> To: netlmm@ietf.org
> Subject: [netlmm] Significance of MN-Identifier
> 
> What's the significance of MN-Identifier as carried in PBU?
> 
> Is it for the sake of identifying the MN during dynamic HNP assignment
> in-band with PMIP?
> 
> If so, given that the HNP may also be assigned during network access
> authentication (out-of band with PMIP, as commonly done in integrated
> bootstrapping scenarios), we shall not mandate that the MN-identifier
> identifies the real MN.
> 
> Another way of using of MN-identifier is to identify the 
> "proxy MN" (MAG)
> with RFC 4285. 
> 
> Alper
> 
> 
> 
> _______________________________________________
> netlmm mailing list
> netlmm@ietf.org
> https://www1.ietf.org/mailman/listinfo/netlmm

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