Issues
------
* ietf-tapswg/api-drafts (+0/-16/💬29)
 18 issues received 29 new comments:
 - #1378 Priority order (2 by gorryfair, tfpauly)
https://github.com/ietf-tapswg/api-drafts/issues/1378 [API] [From a partial review] - #1363 Preconnection vs Listener (1 by mwelzl) https://github.com/ietf-tapswg/api-drafts/issues/1363 [API] [review - must reply] [From a partial review] - #1362 ALPN (2 by mwelzl, tfpauly) https://github.com/ietf-tapswg/api-drafts/issues/1362 [API] [review - must reply] [From a partial review] - #1361 WithPort and WithService, but not WithProtocol (2 by gorryfair, mwelzl) https://github.com/ietf-tapswg/api-drafts/issues/1361 [API] [review - must reply] [From a partial review] - #1360 Hostname vs FQDN (1 by mwelzl) https://github.com/ietf-tapswg/api-drafts/issues/1360 [API] [review - must reply] [From a partial review] - #1357 Netflows vs. IP flows (1 by gorryfair) https://github.com/ietf-tapswg/api-drafts/issues/1357 [API] [review - must reply] [From a partial review] - #1347 Bounds on send and receive rate (1 by gorryfair) https://github.com/ietf-tapswg/api-drafts/issues/1347 [API] - #1346 How to express "Full Coverage" (1 by gorryfair) https://github.com/ietf-tapswg/api-drafts/issues/1346 [API] - #1338 Property names (1 by gorryfair) https://github.com/ietf-tapswg/api-drafts/issues/1338 [API] - #1336 Contradicting Connection / Message properties (1 by mwelzl) https://github.com/ietf-tapswg/api-drafts/issues/1336 [API] [review - must reply] - #1334 Complex interactions between properties (1 by mwelzl) https://github.com/ietf-tapswg/api-drafts/issues/1334 [API] [review - must reply] - #1333 WithProtocol TCP/TLS in an example (6 by gorryfair, mwelzl, tfpauly) https://github.com/ietf-tapswg/api-drafts/issues/1333 [API] [review - must reply] - #1332 Usage of protocol identifiers (2 by mwelzl) https://github.com/ietf-tapswg/api-drafts/issues/1332 [API] [review - must reply] - #1331 How does an application learn allowed/available interface names? (2 by mwelzl) https://github.com/ietf-tapswg/api-drafts/issues/1331 [API] [review - must reply] - #1321 Why batch sends? (1 by gorryfair) https://github.com/ietf-tapswg/api-drafts/issues/1321 [Implementation] - #1299 MPTCP (1 by mwelzl) https://github.com/ietf-tapswg/api-drafts/issues/1299 [Architecture] - #1265 Normative language in section 5 (1 by gorryfair) https://github.com/ietf-tapswg/api-drafts/issues/1265 [API] [discuss] - #1255 Security by default? (2 by tfpauly) https://github.com/ietf-tapswg/api-drafts/issues/1255 [Architecture]
 16 issues closed:
- How are IETF namespaces to be differentiated? https://github.com/ietf-tapswg/api-drafts/issues/1275 [API] - Not just "IETF document in the RFC series" https://github.com/ietf-tapswg/api-drafts/issues/1330 [API] [review - must reply] - Normative language in section 5 https://github.com/ietf-tapswg/api-drafts/issues/1265 [API] - s/Collection/Set or Bag? https://github.com/ietf-tapswg/api-drafts/issues/1280 [API] - Add a (stronger?) statement about monitoring? https://github.com/ietf-tapswg/api-drafts/issues/1279 [Architecture] - Changing types of Selection Properties https://github.com/ietf-tapswg/api-drafts/issues/1281 [API] - Format suggestion to avoid too long line https://github.com/ietf-tapswg/api-drafts/issues/1327 [Implementation] [editorial] [From a partial review] - Example style https://github.com/ietf-tapswg/api-drafts/issues/1323 [Implementation] - Connections don't resolve stuff https://github.com/ietf-tapswg/api-drafts/issues/1308 [API] [editorial] - Leave the empty IANA section in there https://github.com/ietf-tapswg/api-drafts/issues/1295 [Architecture] [editorial] - Two nits in -impl https://github.com/ietf-tapswg/api-drafts/issues/1319 [Implementation] - nits https://github.com/ietf-tapswg/api-drafts/issues/1313 [API] [editorial] - Editorial nit: "myVariableName" https://github.com/ietf-tapswg/api-drafts/issues/1297 [API] [editorial] - nit about simultaneous open text https://github.com/ietf-tapswg/api-drafts/issues/1291 [Architecture] - A nit about MUXing text https://github.com/ietf-tapswg/api-drafts/issues/1293 [Architecture] [editorial] - Message can be spread across multiple packets https://github.com/ietf-tapswg/api-drafts/issues/1292 [Architecture]


Pull requests
-------------
* ietf-tapswg/api-drafts (+8/-8/💬7)
 8 pull requests submitted:
 - Make UTO more clearly a TCP example (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/pull/1401 [API] - Change hi<->lo priority (by gorryfair) https://github.com/ietf-tapswg/api-drafts/pull/1400 - Add ALPN parameter (by tfpauly) https://github.com/ietf-tapswg/api-drafts/pull/1399 - Hostnames SHOULD be FQDNs (by tfpauly) https://github.com/ietf-tapswg/api-drafts/pull/1398 [API] - Explain errors for message properties (by tfpauly) https://github.com/ietf-tapswg/api-drafts/pull/1397 [API] - Could/Can/Might rather than may (by gorryfair) https://github.com/ietf-tapswg/api-drafts/pull/1396 - Review of "should" in API (by gorryfair) https://github.com/ietf-tapswg/api-drafts/pull/1395 - Make it clearer that Messages can be spread across multiple packets (by mwelzl) https://github.com/ietf-tapswg/api-drafts/pull/1394 [Architecture]
 6 pull requests received 7 new comments:
 - #1400 Change hi<->lo priority (1 by gorryfair)
https://github.com/ietf-tapswg/api-drafts/pull/1400 [API] - #1395 Review of "should" in API (1 by mwelzl) https://github.com/ietf-tapswg/api-drafts/pull/1395 - #1393 Mention the Connection priority in the scheduler property description (1 by mwelzl) https://github.com/ietf-tapswg/api-drafts/pull/1393 [API] - #1388 s/Collection/Set (1 by gorryfair) https://github.com/ietf-tapswg/api-drafts/pull/1388 - #1318 Create IANA registry for Tansport Property Namespace (2 by martinduke, mwelzl) https://github.com/ietf-tapswg/api-drafts/pull/1318 [API] [discuss] - #1306 A title change to The Transport Service System? (1 by tfpauly) https://github.com/ietf-tapswg/api-drafts/pull/1306 [Architecture]
 8 pull requests merged:
- Create IANA registry for Tansport Property Namespace https://github.com/ietf-tapswg/api-drafts/pull/1318 [API] [discuss] - Review of "should" in API https://github.com/ietf-tapswg/api-drafts/pull/1395 - s/Collection/Set https://github.com/ietf-tapswg/api-drafts/pull/1388 [API] - A statement about supporting monitoring https://github.com/ietf-tapswg/api-drafts/pull/1390 [Architecture] - 2nd attempt at a Title Change https://github.com/ietf-tapswg/api-drafts/pull/1381 [Architecture] - Non-Preference Selection Properties don't change their type https://github.com/ietf-tapswg/api-drafts/pull/1391 [API] - Nits https://github.com/ietf-tapswg/api-drafts/pull/1392 [API] [Architecture] [Implementation] - Make it clearer that Messages can be spread across multiple packets https://github.com/ietf-tapswg/api-drafts/pull/1394 [Architecture]

Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-tapswg/api-drafts
_______________________________________________
Taps mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/taps

Reply via email to