A Transport Services System, architecture, and Transport Services Implementation #1288
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This document has been edited many ways, and this PR proposes a change in title and refinement in the use of the word 'architecture' to focus on the system specification, rather than the architectural principles. It does not intend to change the system in any way, this is intended as a language revision, to make it slightly less philosophical.
Closed
|
Happy also to muse with this change /Transport Services system/Transport Services System/ is people wish this... |
mwelzl
reviewed
Sep 8, 2023
Co-authored-by: mwelzl <michawe@ifi.uio.no>
Co-authored-by: mwelzl <michawe@ifi.uio.no>
Co-authored-by: mwelzl <michawe@ifi.uio.no>
Co-authored-by: mwelzl <michawe@ifi.uio.no>
Co-authored-by: mwelzl <michawe@ifi.uio.no>
Co-authored-by: mwelzl <michawe@ifi.uio.no>
Co-authored-by: mwelzl <michawe@ifi.uio.no>
Co-authored-by: mwelzl <michawe@ifi.uio.no>
Co-authored-by: mwelzl <michawe@ifi.uio.no>
Co-authored-by: mwelzl <michawe@ifi.uio.no>
This capitalises "Transport Services System". Removes most confusion between system and implementation. Removes two definitions of these, the second one simply becoming text rather than definition. Hopefully now in a fit state for reading!
|
Please also add the "Transport Services Implementation" to the glossary. |
mwelzl
reviewed
Sep 8, 2023
Co-authored-by: mwelzl <michawe@ifi.uio.no>
Co-authored-by: mwelzl <michawe@ifi.uio.no>
Co-authored-by: mwelzl <michawe@ifi.uio.no>
mwelzl
approved these changes
Sep 8, 2023
gorryfair
changed the title
Some phrases are about the architecture of the system, but others are about the system itself, and some others about the implementation below the API. These are separate concepts, and this revision seeks to ensure we use them consistently where possible
theri
reviewed
Oct 2, 2023
Co-authored-by: Reese Enghardt <ietf@tenghardt.net>
Co-authored-by: Reese Enghardt <ietf@tenghardt.net>
tfpauly
reviewed
Oct 2, 2023
csperkins
reviewed
Oct 2, 2023
csperkins
reviewed
Oct 2, 2023
csperkins
approved these changes
Oct 2, 2023
Co-authored-by: Tommy Pauly <tpauly@apple.com>
Co-authored-by: Colin Perkins <csp@csperkins.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This document has been edited many ways, and this PR proposes a change in title and refinement in the use of the word 'architecture' to focus on the system specification, rather than the architectural principles. It does not intend to change the system in any way, this is intended as a language revision, to make it slightly less philosophical.
This is part 1 of addressing Eric's DISCUSS - the other part could be a title change, but this PR needs to land first because it will conflict with other development of text