Re: [Sat] WG Last Call for comments: draft-ietf-satp-architecture-02

[Martin Gfeller <[e-mail]>]

Dear Thomas and Wes

I have the following comments / questions, most likely based on my
incomplete understanding:

2. Terminology - Resource Domain:

 > The collection of resources and entities participating within an asset
network.  The domain denotes a boundary for permissible or authorized
actions on resources.

I find this a bit hard to understand - participating in what exactly?
Boundary means that actions cannot reach into another domain?

Resource Domain is not used thereafter (or I didn't find it).  The
following two definitions, interior and exterior resources are way easier
to grasp.


2. Terminology - Application Context-ID and 5.5 Stage 0

In 5.5 Stage 0, it is explained that the apps "may establish some shared
transfer context information (e.g.  Context-ID)", but I didn't find any
information on why this is required or beneficial.
Why not something like "Shared transfer context information (in particular,
IDs) may be established between applications if required for a particular
use case or application."


5.4 Event log-data ...:

> The log-data generated by a gateway should be considered as an interior
resource
> accessible to other authorized gateways within the same network.


> The mechanism used to provide gateway crash-recovery is dependent on
> the specific network.  For interoperability purposes the information
> contained in the log and the format of the log-data should be
> standardized.


The log-data is declared internal to a network, yet it asks for
standardization, without mentioning which standard should be followed.
Perhaps "should use standards established within the network"
would suffice, without mentioning interoperability at all.

14.1 Normative References

[ISO] Why not reference it as [ISO22739], although the reference isn't used
in the body? There is a new version ISO 22739:2024.


Best regards,
Martin

-----Original Message-----
From: sat <[e-mail]<mailto:[e-mail]>> On Behalf Of
Wes Hardaker
Sent: Saturday, March 9, 2024 9:08 AM
To: [e-mail]<mailto:[e-mail]>
Subject: [Sat] WG Last Call for comments: draft-ietf-satp-architecture-02


Greetings all,

The authors have requested that draft-ietf-satp-architecture-02 be placed
into WG last call and after a review by the chairs we agree it's ready to
progress forward.  I have some personal comments that I'll submit during
last call, but nothing substantive or process-problematic that should hold
up it progressing.  Thus, we have changed the document's status to being in
WG LC and have set a deadline of 4 weeks from now.  Thus, WG LC will end on
April 6th, AOE (anywhere on earth).

We encourage all participants of the WG to read the document,  suggest any
changes you feel are needed from simple editorial suggestions to calling
out major issues you find with the document.  WG participants should also
express their opinions about whether or not the document is ready to
progress and you support it's publication.

All comments should be sent to the mailing list.

--
Wes Hardaker
USC/ISI