Re: [Roll] draft-ietf-roll-security-framework returned to working group.

[Abdussalam Baryun <[e-mail]>]

>
>
> The right thing to do is to publish documents with the right content. As
> Michael
> said, the problem with the Security Framework document is that it does not
> answer the *how* and *why* of what security to apply in what places. While
> it
> does an *AWESOME* job of identify threats it doesn't tell us which protocol
> mechanisms deal with what threats.


 I think the document did n't have to explain *how* and *why*, because this
document is an informational framework not a standard/Best-Practice
framework. The job of the document was intended to give information of
identifying threats. I don't like a documet that has pages more than 50, so
I think this document can change its title and scope to clarify its use
(threats identification informational I-D), and a future standard I-D of
security framwork can have the *how* and *why* related to
protocol/mechanism.

AB