Re: Issue 3: replacement boilerplate for management objectsensitivity

Hi -

> From: "David Harrington" <[email protected]>
> To: "'ops-area (IETF)'" <[email protected]>
> Sent: Wednesday, February 04, 2009 7:47 AM
> Subject: [OPS-AREA] Issue 3: replacement boilerplate for management objectsensitivity
...
> NEW:
...
> Following is a list of the potentially sensitive information, and why
> this information is sensitive:
> 
>     <list the sensitive information elements and state why they are
> sensitive to modification and exposure>
...

I prefer the approach of the old text, which split the information elements
according to concern (modification or mere exposure), rather than
lumping everything together like this, since separating them may help
in security policy formulation and sanity checking.

Randy