RE: [Nea] Charter language on compromised endpoints
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Nea] Charter language on compromised endpoints



Steve,
The text seems okay for addition to the charter itself - it clarifies
the scope of NEA a bit further. 

The other concerns I shared in my other emails about the usefulness of
this work still remains.

Regards,
Vidya

> -----Original Message-----
> From: Stephen Hanna [mailto:shanna at juniper.net] 
> Sent: Friday, May 26, 2006 1:35 PM
> To: nea at ietf.org
> Subject: [Nea] Charter language on compromised endpoints
> 
> Since several people on the NEA list have asked to have the 
> charter address the matter of compromised endpoints but 
> nobody has suggested that this should be in scope for NEA 
> (except that it will be addressed in the overall security 
> analysis), I propose adding the following text to the current 
> draft charter just before the milestones:
> 
> -----
> 
> One commonly discussed issue with NEA systems is how to 
> handle compromised endpoints, whose reports of their own 
> posture may not be accurate. This issue is out of scope for 
> the NEA working group except in the security analysis section 
> of the Requirements document.
> 
> -----
> 
> I invite comments on this proposal.
> 
> Thanks,
> 
> Steve
> 
> _______________________________________________
> Nea mailing list
> Nea at ietf.org
> https://www1.ietf.org/mailman/listinfo/nea
> 

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




Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.