Skip to content
This repository has been archived by the owner on Sep 19, 2024. It is now read-only.

producing/consuming... do we need a new term of accepting, passing? #421

Open
mcr opened this issue Jul 23, 2022 · 0 comments
Open

producing/consuming... do we need a new term of accepting, passing? #421

mcr opened this issue Jul 23, 2022 · 0 comments
Assignees

Comments

@mcr
Copy link
Collaborator

mcr commented Jul 23, 2022

We think that this could sometimes be the case, but we felt that that the
diagram would best be adjusted anyway.
(Yes, we came up with different answers two what are apparently the same
problem with the diagram)

https://github.com/ietf-rats-wg/architecture/pull/414/files

Thanks for clarifying.

What I'm getting from this text is that there is "producing" and "consuming" per Section 4.

I took those terms to be describing/constraining information flow -- what information can comes and go among the various architectural elements.

It appears that Section 5 is introducing a new behavior which is "accepting" (receiving but not processing) and "passing" (sending but not processing). There also appear to be element specific behavior of "caching".

I see no conflict with these four behaviors. My concern is that these nuances in behavior were not explicitly stated. They should be. Furthermore, just as certain architectural elements are defined by what they can produce or consume, I'm wondering if the same is true for the "accepting"/"passing" behavior?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants