Issues
------
* ietf-tapswg/api-drafts (+37/-2/💬19)
37 issues created:
- nits (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1355 [API]
- Wrong IP address in example (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1354 [API]
- Inclusive language (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1353 [API] [editorial]
- Clarify rcv backpressure (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1352 [API]
- What does worse performance mean? (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1351
- s/datagram/UDP payload (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1350 [API] [editorial]
- MSS and PMTUD (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1349 [API]
- Later control of sender checksum coverage, and corruption / reliability (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1348 [API]
- Bounds on send and receive rate (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1347 [API]
- How to express "Full Coverage" (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1346 [API]
- 0-RTT property name (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1345 [API]
- HTTPS = TCL/TLS ? (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1344 [API]
- Why didn't we overload WithIPAddress for multicast? (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1343 [API]
- Service names should refer to IANA names; and "getservbyname" (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1342 [API]
- Port integer type (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1341 [API]
- Programmer can't know that all endpoints are the same service (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1340 [API]
- Define "represent the same host" (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1339 [API]
- Property names (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1338 [API]
- String encoding shouldn't assume a defined string representation (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1337 [API] [review]
- Contradicting Connection / Message properties (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1336 [API] [review]
- Scheduler property (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1335 [API] [review]
- Complex interactions between properties (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1334 [API] [review]
- WithProtocol TCP/TLS in an example (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1333 [API] [review]
- Usage of protocol identifiers (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1332 [API]
- How does an application learn allowed/available interface names? (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1331 [API]
- Not just "IETF document in the RFC series" (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1330 [API] [review]
- Code location (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1329 [Implementation] [From a partial review]
- Example on QUIC? (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1328 [Implementation] [From a partial review]
- Format suggestion to avoid too long line (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1327 [Implementation] [From a partial review]
- HTTP/3 suggestions and reference missing (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1326 [Implementation] [From a partial review]
- How to implement security considerations? (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1325 [Implementation] [From a partial review]
- Change a few examples from IPv4/LTE to IPv6? (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1324 [Implementation]
- Example style (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1323 [Implementation]
- IPv6 address representation and port number (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1322 [Implementation]
- Why batch sends? (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1321 [Implementation]
- Why not QUIC? (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1320 [Implementation]
- Two nits in -impl (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1319 [Implementation]
15 issues received 19 new comments:
- #1354 Wrong IP address in example (1 by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/1354 [API]
- #1353 Inclusive language (2 by gorryfair, tfpauly)
https://github.com/ietf-tapswg/api-drafts/issues/1353 [API] [editorial]
- #1352 Clarify rcv backpressure (1 by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1352 [API]
- #1350 s/datagram/UDP payload (1 by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/1350 [API] [editorial]
- #1349 MSS and PMTUD (1 by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/1349 [API]
- #1348 Later control of sender checksum coverage, and corruption / reliability (1 by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/1348 [API]
- #1346 How to express "Full Coverage" (1 by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1346 [API]
- #1345 0-RTT property name (1 by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1345 [API]
- #1341 Port integer type (1 by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1341 [API]
- #1336 Contradicting Connection / Message properties (1 by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1336 [API] [review]
- #1334 Complex interactions between properties (1 by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1334 [API] [review]
- #1330 Not just "IETF document in the RFC series" (1 by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1330 [API] [review]
- #1319 Two nits in -impl (1 by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1319 [Implementation]
- #1275 How are IETF namespaces to be differentiated? (4 by gorryfair, mirjak, mwelzl, philsbln)
https://github.com/ietf-tapswg/api-drafts/issues/1275 [API] [discuss]
- #1267 s/TTL/hop limit ? (1 by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/1267 [API]
2 issues closed:
- Inclusive language https://github.com/ietf-tapswg/api-drafts/issues/1353 [API] [editorial]
- Protocol-specific properties or Generic properties https://github.com/ietf-tapswg/api-drafts/issues/1302 [API] [editorial]
Pull requests
-------------
* ietf-tapswg/api-drafts (+2/-2/💬4)
2 pull requests submitted:
- Remove the use of "native" (by tfpauly)
https://github.com/ietf-tapswg/api-drafts/pull/1356 [editorial]
- Create IANA registry for Tansport Property Namespace (by philsbln)
https://github.com/ietf-tapswg/api-drafts/pull/1318
1 pull requests received 4 new comments:
- #1306 A title change to The Transport Service System? (4 by abrunstrom,
gorryfair, tfpauly, zaheduzzaman)
https://github.com/ietf-tapswg/api-drafts/pull/1306 [Architecture] [discuss]
2 pull requests merged:
- Remove the use of "native"
https://github.com/ietf-tapswg/api-drafts/pull/1356 [editorial]
- Generic Properties
https://github.com/ietf-tapswg/api-drafts/pull/1317 [API]
Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-tapswg/api-drafts
_______________________________________________
Taps mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/taps
