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

Missing Appendix C: Mapping of Existing Technologies into the ToIP Stack #57

Closed
talltree opened this issue Nov 3, 2022 · 3 comments
Closed
Assignees
Labels
priority: high It is important for the group to resolve this issue soon. status: needs-review type: content The issue involves normative content; resolution requires group consensus.
Milestone

Comments

@talltree
Copy link
Collaborator

talltree commented Nov 3, 2022

In the current draft this is Appendix B, however in issue #31, I propose to add a new Appendix B, so this would become Appendix C.

@talltree talltree added priority: high It is important for the group to resolve this issue soon. status: pr-in-progress The issue has been assigned and work is in progress. type: content The issue involves normative content; resolution requires group consensus. labels Nov 3, 2022
@andorsk andorsk added this to the PR-1 milestone Nov 3, 2022
@talltree
Copy link
Collaborator Author

talltree commented Nov 7, 2022

The primary purpose of Appendix C is to point readers to a separate document entitled Evolution of the ToIP Stack. This is a living document — the first version of which is to be published (as a PDF) at the same time as the first public review draft of the ToIP Technology Architecture Specification — that is intended to constantly evolve as progress is made in the development of component specifications.

Although I have not drafted Appendix C yet, I have finished a complete draft of Evolution of the ToIP Stack
(modulo a few TODOs near the end). Please review and add comments directly to the Google doc (which should be accessible to any ToIP member).

@talltree
Copy link
Collaborator Author

In addition to the new Evolution of the ToIP Stack document (see above), the proposed text for Appendix B has now been drafted in a Google doc. Please review; then it will be turned into a PR.,

@talltree talltree removed the status: pr-in-progress The issue has been assigned and work is in progress. label Nov 10, 2022
@talltree
Copy link
Collaborator Author

Closed by PR #68

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority: high It is important for the group to resolve this issue soon. status: needs-review type: content The issue involves normative content; resolution requires group consensus.
Projects
None yet
Development

No branches or pull requests

3 participants