Issues
------
* ietf-tapswg/api-drafts (+8/-4/💬14)
8 issues created:
- Review by CA - Which ICMP to forward for Multicast? (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/1032
- Review by CA - ConnectionError additional info (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/1031 [Implementation]
- Review by CA - Is the content of messages always bytes? (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/1030 [Implementation]
- Review by CA - Is there formal language or pseudocode? (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/1029 [Implementation]
- Review by CA - Final message property IsEndOfMessage event? (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/1028 [Implementation]
- Review by CA - privacy implications of using the same token on different paths? (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/1027 [Implementation]
- Review by CA - Datgram v Coinnectionless (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/1026
- Implementation Draft Review: Section 4.1 - Define Racing earlier to include Staggered/Failover scenarios (by benthor)
https://github.com/ietf-tapswg/api-drafts/issues/1020
9 issues received 14 new comments:
- #1031 Review by CA - ConnectionError additional info (2 by chrysn, gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/1031 [Implementation]
- #1030 Review by CA - Is the content of messages always bytes? (1 by chrysn)
https://github.com/ietf-tapswg/api-drafts/issues/1030 [Implementation]
- #1028 Review by CA - Final message property IsEndOfMessage event? (2 by gorryfair, mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1028 [Implementation]
- #1026 Review by CA - Datagram v Connectionless (3 by gorryfair, mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1026 [API] [Implementation]
- #1020 Implementation Draft Review: Section 4.1 - Define Racing earlier to include Staggered/Failover scenarios (1 by tfpauly)
https://github.com/ietf-tapswg/api-drafts/issues/1020 [Implementation]
- #1012 Interface draft: Different Property Types and States still confusing (2 by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1012 [API]
- #715 Use of protocol, protocol stack (1 by britram)
https://github.com/ietf-tapswg/api-drafts/issues/715 [Implementation] [editorial]
- #713 Privacy considerations section (1 by britram)
https://github.com/ietf-tapswg/api-drafts/issues/713 [Implementation] [editorial]
- #631 Peer user timeout (1 by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/631 [mappings]
4 issues closed:
- Use of protocol, protocol stack https://github.com/ietf-tapswg/api-drafts/issues/715 [Implementation] [editorial]
- Privacy considerations section https://github.com/ietf-tapswg/api-drafts/issues/713 [Implementation] [editorial]
- Peer user timeout https://github.com/ietf-tapswg/api-drafts/issues/631 [mappings]
- Implementation Draft Review: Section 4.1 - Choice of terms leads to confusing language https://github.com/ietf-tapswg/api-drafts/issues/1016 [Implementation]
Pull requests
-------------
* ietf-tapswg/api-drafts (+9/-4/💬13)
9 pull requests submitted:
- Update to resolve Datagram v Connectionless (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/pull/1034
- Reading Selection Properties, etc. Resolves #1012 (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/pull/1033
- Editorial changes: Protocol Stack and Protocol Instance (by britram)
https://github.com/ietf-tapswg/api-drafts/pull/1025
- Update draft-ietf-taps-impl.md (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/pull/1024
- Explain use of framers for connectionless protocols (by tfpauly)
https://github.com/ietf-tapswg/api-drafts/pull/1023 [Implementation]
- Soften order of operations text (by tfpauly)
https://github.com/ietf-tapswg/api-drafts/pull/1022 [Implementation]
- Sketch alternative multicast model (by csperkins)
https://github.com/ietf-tapswg/api-drafts/pull/1021
- A few nits; primarily adding "non-negative" in some places (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/pull/1019
- add a stream-id: assignable and readable. Closes #1010 (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/pull/1018
7 pull requests received 13 new comments:
- #1033 Reading Selection Properties, etc. Resolves #1012 (1 by mwelzl)
https://github.com/ietf-tapswg/api-drafts/pull/1033 [API]
- #1023 Explain use of framers for connectionless protocols (1 by chrysn)
https://github.com/ietf-tapswg/api-drafts/pull/1023 [Implementation]
- #1022 Soften order of operations text (1 by gorryfair)
https://github.com/ietf-tapswg/api-drafts/pull/1022 [Implementation]
- #1021 Sketch alternative multicast model (1 by tfpauly)
https://github.com/ietf-tapswg/api-drafts/pull/1021 [API]
- #1019 A few nits; primarily adding "non-negative" in some places (1 by philsbln)
https://github.com/ietf-tapswg/api-drafts/pull/1019 [API]
- #1018 add a stream-id: assignable and readable. Closes #1010 (7 by britram, mwelzl, philsbln, tfpauly)
https://github.com/ietf-tapswg/api-drafts/pull/1018 [API]
- #1014 readability edit of section 4.0, complementing my ongoing draft review (1 by abrunstrom)
https://github.com/ietf-tapswg/api-drafts/pull/1014
4 pull requests merged:
- Update to resolve Datagram v Connectionless
https://github.com/ietf-tapswg/api-drafts/pull/1034 [Implementation]
- Editorial changes: Protocol Stack and Protocol Instance
https://github.com/ietf-tapswg/api-drafts/pull/1025 [Implementation]
- A few nits; primarily adding "non-negative" in some places
https://github.com/ietf-tapswg/api-drafts/pull/1019 [API]
- Clarify leaf node establishment
https://github.com/ietf-tapswg/api-drafts/pull/1017 [Implementation]
Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-tapswg/api-drafts
_______________________________________________
Taps mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/taps
