| Re: Re: Clarifications on "Domino Effect" | <– Date –> <– Thread –> |
|
From: Bernard Aboba (aboba |
|
| Date: Mon, 1 Aug 2005 12:05:23 -0400 (EDT) | |
> I'm not necessarily saying that we need to have a long > list of requirements imported from Russ'es document. > Or a requirements section for that matter. > > But it would be useful to have a discussion of the compromise > issue and other aspects of the system level security model in > the doc. Of course, we should not cover the extensions or > anything really beyond existing usage. I agree that this makes sense. Perhaps what we need to do is develop the "threat model" section and then analyze existing lower layers against those threats, providing concrete examples of how violation of draft-housley principles can lead to issues (if in fact that is the case). This might prove more helpful than just reciting a requirements list. Usually the first question we get from a lower layer designer is "why does this requirement matter to my lower layer?"
- Re: Clarifications on "Domino Effect", (continued)
-
Re: Clarifications on "Domino Effect" Bernard Aboba, July 31 2005
-
Re: Re: Clarifications on "Domino Effect" Jari Arkko, July 31 2005
- Re: Re: Clarifications on "Domino Effect" Bernard Aboba, July 31 2005
- Re: Re: Clarifications on "Domino Effect" Jari Arkko, August 1 2005
- Re: Re: Clarifications on "Domino Effect" Bernard Aboba, August 1 2005
-
Re: Re: Clarifications on "Domino Effect" Jari Arkko, July 31 2005
-
Re: Clarifications on "Domino Effect" Bernard Aboba, July 31 2005
Results generated by Tiger Technologies using MHonArc.