On Mon, 15 Jun 2009, Terry Manderson wrote:
This might then be used by the WG and authors of other drafts to ask
questions pertaining to the completeness, direction, and applicability of
the work from a clear use case basis.
...
The draft is attached for your review, and the authors and I would be most
appreciative if you could read this document and either before, or at, IETF
75 provide your comments.
This document is a useful contribution. My hope is that we will use
this document as a template to generate examples of how to satisfy
each use given a set of validation rules. From that, we can see if
the validation rules (and the artitecture generally) let us satisfy
the full set of cases we care about.
For the RPKI, sections 3 and 5 are useful. I have basically ignored
section 4.
On to the specifics:
Observation: Most of the Section 3 cases speak about which routes one
wishes to have accepted (or chosen) and make no explicit statement
about which routes one wants to have rejected. I think it would be
useful to include such statements, perhaps as "attack" case. This may
result in an effectively two-dimensional table of cases.
I believe the "partial deployment use cases" of section 5 are critical
to the success of the RPKI, and I think the set of cases here is too
limited. For instance, a variation on 5.1 ("parent does not do RPKI")
is "other upstream(s) don't do RPKI". Perhaps we could generate these
by going through the section 3 cases and, for each one, add the
permutations of which parties do and don't support the RPKI. Sadly,
when combined with the above, that could give us a three dimensional
space to work in, but most of the section 3 cases involve only one
party, so the problem should be tractable.
Perhaps some of this expansion could be rolled into the next revision.
-- Sam
_______________________________________________
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr
