Re: [HOKEY] Change proposal for ERP-AAK - 1: NAS-IdentifierRedefining

This is not a problem.
Since NAI-Identifier defined in RFC2865 is not general either and only used in 
 Access-Request packet to the RADIUS Server, however in our use case,
we need a TLV for SAP to carry CAP lists to the server that may be in another 
domain which is quite different from original usage of NAI-Identifier specified in RFC2865.
Therefore it worth having a new TLV to fix this issue.

Regards!
-Qin
----- Original Message ----- 
From: "Zhen Cao" <zehn.cao@gmail.com>
To: "Glen Zorn" <glenzorn@gmail.com>
Cc: <hokey@ietf.org>
Sent: Tuesday, October 11, 2011 1:30 PM
Subject: Re: [HOKEY] Change proposal for ERP-AAK - 1: NAS-IdentifierRedefining

CAS-Identity would be a new concept and need Type for the TLV, and it
may be not general enough.  I am afraid IETF would be conservative to
agree with this, given we have way to circumvent.

On Tue, Oct 11, 2011 at 1:24 PM, Glen Zorn <glenzorn@gmail.com> wrote:
> On 10/9/2011 9:39 AM, Zhen Cao wrote:
>
>> I think we should be careful adding more semantics to the current
>> tools, otherwise it takes longer to converge.
>
> Sorry, I don't understand.
>
>>
>> How about re-use the NAS-Id and in the string part, make it a
>> FQDN-alike way, then that depends on the implementation only.
>>
>> On Wed, Oct 5, 2011 at 8:03 PM, Glen Zorn <glenzorn@gmail.com> wrote:
>>> On 9/29/2011 4:20 PM, Qin Wu wrote:
>>>
>>>> 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.
>>>>
>>>> "
>>>
>>> OK, but this needs a format specification (FQDN might be good).
>>>
>>>>
>>>> Regards!
>>>> -Qin
>>>>
>>>>
>>>> _______________________________________________
>>>> HOKEY mailing list
>>>> HOKEY@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/hokey
>>>
>>> _______________________________________________
>>> HOKEY mailing list
>>> HOKEY@ietf.org
>>> https://www.ietf.org/mailman/listinfo/hokey
>>>
>>
>>
>>
>
>

-- 
Best regards,
Zhen
_______________________________________________
HOKEY mailing list
HOKEY@ietf.org
https://www.ietf.org/mailman/listinfo/hokey