Recording

Attendees

To launch community participation in the drafting of the Design Principles for the ToIP Stack document

Time	Agenda Item	Lead	Notes
5 min	Start recording Welcome & antitrust notice Introduction of new members Agenda review	Chairs	Antitrust Policy Notice: Attendees are reminded to adhere to the meeting agenda and not participate in activities prohibited under antitrust and competition laws. Only members of ToIP who have signed the necessary agreements are permitted to participate in this activity beyond an observer role. New Members: Please, add your company if you are contributing to this document.
5 mins	Background on Design Principles for the ToIP Stack document	Drummond Reed	Current Google doc: Design Principles for the ToIP Stack
40 mins	Discussion of the End-to-End Principle	Drummond Reed
10 mins	Discuss volunteers for writing assignments for the next week		See Action Items
5 mins	Review decisions/action items Planning for next meeting	Chairs

Number of principles and their order won't be set until at least end of August
Drummond Reed DP document is not the first document for newcomers to the ToIP stack and Foundation.
Judith Fleenor , Wenjing Chu and others discussed how fundamental these principles are and how 'encyclopedic' or 'easy' their content might be.
Drummond Reed shared that all the principles need ToIP context into each of them. Each principle should probably answer these questions:
- What does principle mean
- Why ToIP finds important
- What are current examples of these principles in the ToIP stack
We reviewed the End-to-End Principle as an example of what the contents of a principle section should cover.
Victor Golubkov different principles are addressing different elements of the ToIP stack as a result public might be interested in only some of them. sankarshan insisted that DP document goal will be then to influence the reader to read the whole document.
Judith Fleenor in the beginning of each section provide a little executive summary why ToIP chooses this principle as important. 2-3 lines.

Wenjing Chu shared that we can not define 'ends' in the DP document, because only after stating a specific problem we can define 'ends' in this specific problem.
P Subrahmanyamsays it would help to give examples of what is NOT end-to-end.

Vikas Malhotra , Wenjing Chu , Victor Golubkov discussed various examples of the dualism of trust in current state of internet.

Each section in the document describing a design principle should ideally be between one and two pages in length (including illustrations).
Each principle should start with a 2-3 line of executive summary about why ToIP chooses this principle as important.
The writeup of each principle should follow this general structure:
1. What is the principle? (Explain it in layman's terms.)
2. What is the relevance of this principle to ToIP architecture and the ToIP stack?
3. What is a specific example of how it will be applied? (Plus, if possible, one or more counterexamples, i.e., design decisions that would contravene the principle).

sankarshanand Paul Grehanwill start working on the 'Introduction' and 'What are Design principles' sections. Continue working on these sections.
Drummond Reed will work on the 'End-to-End Principles' section.
Wenjing Chu volunteered to work on "Interoperability First" principle.
Vikas Malhotra volunteered to work on "Transitivity of Trust" and "Dualsim of Trust" principles.
Victor Golubkov will continue to work on other sections.