Re: [Nea] What's the relationship betweetn vendor-specific attributes and interoprability?

[yinhan <ayinhan at huawei.com>]

Hi  Mike
 I think it is about the depth of interoperability.
 Vendor-specific attributes should be minor. Additionally,  The NEA Server 
  should not deny the NEA Client because the endpoint can not  provide 
  vendor-specific attribute. If that, the posture validator will only have to interoperate
  well  with the posture collector that can give the vendor-specific  attribute the validator
 requires and and complete the normal function. Therefore, the most attributes should be 
standardized, and the standardized attributes should include the binding of version, 
update time and threads  




> ----- Original Message ----- 
> From: "Mike Fratto" <mfratto at gmail.com>
> To: "Yin Han" <ayinhan at huawei.com>
> Cc: <nea at ietf.org>
> Sent: Thursday, October 19, 2006 9:25 PM
> Subject: Re: [Nea] What's the relationship betweetn vendor-specific attributes and interoprability?
> 
> 
>>>   Therefore, the statment should be added into the charter:"To realize
>>> interoperability, the most attributes are standard in PA-level and PV must
>>> be able to make such assessment that NEA server can permit the NEA cllient
>>> to access the network even though the PC could not provide the
>>> vendor-specific attributes." If we can not reach it, the interoperability
>>> will be impractical.
>> 
>> Yin, I think what your talking about is an implementation and local
>> policy issue, and not a interoperation issue, and therefore not really
>> an issue for standardization.
>> 
>> Whether a foreign computer is allowed to provide it's own posture
>> assessment is a matter of local policy for the trusting company.
>> 
>> That the posture collectors and posture validators can exchange
>> information is a matter of standardization to that point that the
>> formats are standardized for attribute exchange but not necessarily
>> the meaning of those attributes.
>> 
>> RADIUS attribute extensions work in a similar manner and probably
>> provides a decent model to work off of.
>> 
>> mike

_______________________________________________
Nea mailing list
Nea at ietf.org
https://www1.ietf.org/mailman/listinfo/nea