...
- Drummond Reed
- Daniel Hardman
- Wenjing Chu
- Samuel Smith
- Darrell O'Donnell
- Antti Kettunen
- Mathieu Glaude
- Neil Thomson
- Subhasis Ojha
- Willem de Kok
- Jo Spencer
- Mark Scott
- Vladimir Simjanoski
- Keerthi Thomas
- Dima Postnikov
Agenda Items and Notes (including all relevant links)
Time | Agenda Item | Lead | Notes |
5 min |
| Leads |
|
5 mins | Urgency vs. Completeness Poll Results | Sam Curren | See the poll and results here. If you have not voted yet, please do. |
15 mins | Considerations raised by the Two-Layer Design Model Proposal | See this Github discussion for more about the Two-Layer Design Model Proposal. The purpose of this proposal was to see if we could achieve alignment by compartmentalizing which problems were solved where. Daniel Hardman kicked off discussion with some thoughts about points he has made in the discussion by sharing screenshot screenshots #1 through #7 below. Among See those slides for his points: . Wenjing Chu understands Daniel's argument for a number of his proposed features but does not feel it needs to be in Layer 2. His test would be, "If a feature is not included in Layer 2, it would be hard to implement in a higher layer." Sometimes ambiguity is useful in language. Daniel Hardman felt very strongly that the properties he is talking about cannot be at any higher layers. Antti Kettunen is open to the possibility that there are n layers above the TSP layer, and believes that is where the abuse is likely to happen. He suggests we should focus on the features that are needed by those higher layer to achieve Daniel's properties. Samuel Smith raised questions in this context about different approaches to supporting composability. Darrell O'Donnell made some points about how TCP/IP required both TCP and IP to gain adoption. Jo Spencer spoke in favor of the "logical separation" of the proposal. Sam Curren suggested a specific set of five work items that could be a path forward. | |
90 mins | Open Discussion | All | |
5 mins |
| Leads |
...