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

Hi Eric,

* This traffic was sent over an encrypted link
* All traffic to address X will be sent over an encrypted link
[Meiling] What does an encrypted link refer to, who established the link, and who negotiated encryption with whom?

* This traffic is not being sent to a spanning port or otherwise available for monitoring
[Meiling] Traffic is forwarded according to expected nodes and ports, and will not sent to a spanning port.  As for monitoring, it depends on the customer's choice, NASR just to ensure that there will be no monitoring without the user's consent.

Best,
Meiling
 
From: Eric Rescorla
Date: 2025-05-24 00:32
To: Luigi IANNONE
CC: Watson Ladd; Meiling Chen; Henk Birkholz; Liuchunchi; Toerless Eckert; [email protected]; IETF SAAG; Luigi Iannone
Subject: [nasr] Re: [saag] Re: Re: Re: NASR BOF Follow-Up


On Thu, May 22, 2025 at 12:52 AM Luigi IANNONE <[email protected]> wrote:
Hi Watson,

> 
> Correct. Some claims are easy to verify. Most aren't. Statements that "the
> router supports X" aren't really interesting. Statements that "this
> configuration will never pass your traffic over a bad link" are, but are a lot
> harder to show.
> 
> >

[LI] Agreed. This is a very claim hard show/attest. 
Note however that this is not what NASR is trying to do. 
NASR is more about router has feature X, Y, and Z which is what I want, and that traffic goes through the selected routers that support X, Y and Z.
NASR is not about proving that traffic does not go somewhere else (proof of non-transit is out of scope). 

As I understood the presentations, you wanted to make claims like:

* This traffic was sent over an encrypted link
* All traffic to address X will be sent over an encrypted link
* This traffic is not being sent to a spanning port or otherwise available for monitoring

Correct?

-Ekr



-Ekr


Ciao

L.

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