Subject: [HOKEY] Change proposal for ERP-AAK - 1: NAS-Identifier Redefining

From: Qin Wu <[email-masked]>
Date: Thu, 29 Sep 2011 17:20:55 +0800

Hi,
As we discussed on the list to draft-ietf-hokey-erp-aak, NAS Identifier defined in the section 5.32 of RFC2865
is not appropriate to be used in the inter-realm hanover case. Since CAP(s) and/or SAP are not global identifier
and the value they are choosing may conflict with each other, therefore I propose to redefine NAS-Identifier,
in other words, abandon using NAS-Identifer in the draft-ietf-hokey-erp-aak-05, instead, replace it with CAP-Identifier
as belows:

"
   CAP-Identifier: This is carried in a TLV

   payload. The type is TBD. This attribute contains a string identifying the Candidate Access Points prior to the

   arrival of the MH at the Candidate Access Network (CAN).It is used by the SAP to advertise the identifier(s) of

   CAP(s) to the peer and EA server.

"

Regards!
-Qin