[Taps] Weekly github digest (TAPS Activity Summary)

Repository Activity Summary Bot Sun, 11 Jun 2023 00:41:06 -0700



Issues
------
* ietf-tapswg/api-drafts (+18/-10/💬33)
 18 issues created:
 - Fewer normative references? (by mwelzl)

https://github.com/ietf-tapswg/api-drafts/issues/1197 [API]- Security considerations (by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1196 [API]- Section 8.1.10 make reference to -arch more precise (by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1195 [API]- Section 8.1.5 connection group transmission scheduler (by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1194 [API]- 6.3 Security parameters and callbacks (by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1193 [API]- Section 6.2.18 vague reference to -impl draft (by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1192 [API]- Alias statement consistency, section 6.1.3 (by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1191 [API]- Multicast confusion in 1st paragraph of section 6.1.1 (by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1190 [API]- Section 6.1 "withport" example (by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1189 [API]- s/SHOULD/MUST regarding multiple remote endpoints (by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1188 [API]- Peer example, section 3.1.3 (by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1186 [API]- Example in section 3.1.2 (by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1185 [API]- HTTPS + raw PK (by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1184 [API]- Basic types (by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1183 [API]- Some examples have too long lines (by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1182 [API]- Add a sentence about implementation freedom (by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1181- API presentation language (by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1180- gen-art review of -interface (by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1179 [API]

 14 issues received 33 new comments:
 - #1197 Fewer normative references? (3 by britram, gorryfair, mwelzl)

https://github.com/ietf-tapswg/api-drafts/issues/1197 [API]- #1194 Section 8.1.5 connection group transmission scheduler (10 by abrunstrom, gorryfair, mirjak, mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1194 [API]- #1192 Section 6.2.18 vague reference to -impl draft (1 by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1192 [API]- #1191 Alias statement consistency, section 6.1.3 (1 by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1191 [API] [editorial]- #1189 Section 6.1 "withport" example (2 by britram, mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1189 [API]- #1188 s/SHOULD/MUST regarding multiple remote endpoints (2 by mwelzl, tfpauly)https://github.com/ietf-tapswg/api-drafts/issues/1188 [API]- #1186 Peer example, section 3.1.3 (1 by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1186 [API]- #1185 Example in section 3.1.2 (4 by mwelzl, tfpauly)https://github.com/ietf-tapswg/api-drafts/issues/1185 [API]- #1184 HTTPS + raw PK (2 by britram, mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1184 [API]- #1182 Some examples have too long lines (1 by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1182 [API]- #1181 Be clearer about implementation freedom (2 by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1181 [API]- #1180 API presentation language (2 by britram, mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1180 [API]- #1179 gen-art review of -interface (1 by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1179 [API]- #1176 Comment from Ops area review (1 by mwelzl)https://github.com/ietf-tapswg/api-drafts/issues/1176 [Implementation]

 10 issues closed:

- Security considerations https://github.com/ietf-tapswg/api-drafts/issues/1196 [API]- Editorial things - in section 4 (and its subsections) https://github.com/ietf-tapswg/api-drafts/issues/1187 [API] [editorial]- s/SHOULD/MUST regarding multiple remote endpoints https://github.com/ietf-tapswg/api-drafts/issues/1188 [API]- Be clearer about implementation freedom https://github.com/ietf-tapswg/api-drafts/issues/1181 [API]- Fewer normative references? https://github.com/ietf-tapswg/api-drafts/issues/1197 [API]- Multicast confusion in 1st paragraph of section 6.1.1 https://github.com/ietf-tapswg/api-drafts/issues/1190 [API]- Peer example, section 3.1.3 https://github.com/ietf-tapswg/api-drafts/issues/1186 [API]- Section 6.1 "withport" example https://github.com/ietf-tapswg/api-drafts/issues/1189 [API]- API presentation language https://github.com/ietf-tapswg/api-drafts/issues/1180 [API]- DNS nits https://github.com/ietf-tapswg/api-drafts/issues/1177 [Implementation]



Pull requests
-------------
* ietf-tapswg/api-drafts (+11/-8/💬2)
 11 pull requests submitted:
 - Minor wording change in example in section 3.1.2. (by mwelzl)

https://github.com/ietf-tapswg/api-drafts/pull/1208 [API]- Added basic types: string, IPv4 address, IPv6 address. (by mwelzl)https://github.com/ietf-tapswg/api-drafts/pull/1207 [API]- Various editorial fixes from Genart review. (by mwelzl)https://github.com/ietf-tapswg/api-drafts/pull/1206 [API] [editorial]- GENART Section 4 editorial rollup (by britram)https://github.com/ietf-tapswg/api-drafts/pull/1205- Security considerations fixes from GENART review (by britram)https://github.com/ietf-tapswg/api-drafts/pull/1204- Add server-certificate and client-certificate (as opposed to just key… (by britram)https://github.com/ietf-tapswg/api-drafts/pull/1203- Make implementation freedom clearer (by britram)https://github.com/ietf-tapswg/api-drafts/pull/1202- Downgrade (most) normative references (by britram)https://github.com/ietf-tapswg/api-drafts/pull/1201- Fix peer example (by csperkins)https://github.com/ietf-tapswg/api-drafts/pull/1200- Clarify behaviour of multicast (by csperkins)https://github.com/ietf-tapswg/api-drafts/pull/1199- Clarify multiple remote endpoints (by tfpauly)https://github.com/ietf-tapswg/api-drafts/pull/1198 [API]

 2 pull requests received 2 new comments:
 - #1206 Various editorial fixes from Genart review. (1 by mwelzl)

https://github.com/ietf-tapswg/api-drafts/pull/1206 [API] [editorial]- #1198 Clarify multiple remote endpoints (1 by tfpauly)https://github.com/ietf-tapswg/api-drafts/pull/1198 [API]

 8 pull requests merged:
 - Security considerations fixes from GENART review

https://github.com/ietf-tapswg/api-drafts/pull/1204- GENART Section 4 editorial rolluphttps://github.com/ietf-tapswg/api-drafts/pull/1205- Clarify multiple remote endpointshttps://github.com/ietf-tapswg/api-drafts/pull/1198 [API]- Make implementation freedom clearerhttps://github.com/ietf-tapswg/api-drafts/pull/1202- Downgrade (most) normative referenceshttps://github.com/ietf-tapswg/api-drafts/pull/1201- Clarify behaviour of multicasthttps://github.com/ietf-tapswg/api-drafts/pull/1199- Fix peer examplehttps://github.com/ietf-tapswg/api-drafts/pull/1200- Fix DNS nitshttps://github.com/ietf-tapswg/api-drafts/pull/1178 [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

[Taps] Weekly github digest (TAPS Activity Summary)

Reply via email to