[saag] Re: [nasr] Re: Re: Re: Re: NASR BOF Follo w-Up

HI,

I think there is a bit of a  misunderstanding …


The BOF presented a number of problems that allegedly NASR was trying
to solve, including that:

1. The router in question would forward/has forwarded specific
traffic classes on specific links and not others.
[LI] Nope. NASR is not about forwarding on specific links. It is about being able to proof that traffic went through a certain set of devices that fulfil a set of claims (or requirements if you wish…).
Attesting that the set of devices fulfils the requirements is done by extending the RATS technology.
Proving that the traffic did go through those devices is done a proof of transit technology for which there are a couple of early ideas documented.

2. That specific traffic classes would be/had been encrypted
using MACSEC.
[LI] Nope. (as I state in a previous mail) this is orthogonal to NASR. Whether you want to use it is not part of the NASR problem statement.

NASR represents one specific proposal for addressing these problems,
which is to attest to the code and configuration running on specific
network elements. So, yes, a system like NASR needs to establish
that the code and configuration guarantees these properties in
order to address the stated problem.
[LI] You do not need that level of granularity.
It's certainly not sufficient
to demonstrate that the device simply supports MACSEC, because
it might be disabled.

If you think there is some other set of problems that need to be
solved, and that these don't need to be then I think you need to state
that more clearly.
[LI] Agreed. We certainly need to do more work in clarifying the problem and possible solution space.
The ongoing exchange in very helpful in this sense.
Thanks
Ciao
L.



-Ekr

_______________________________________________
saag mailing list -- [email protected]
To unsubscribe send an email to [email protected]