[Taps] Weekly github digest (TAPS Activity Summary)

[Repository Activity Summary Bot <[e-mail]>]

Issues
------
* ietf-tapswg/api-drafts (+0/-25/💬6)
  4 issues received 6 new comments:
  - #1428 What are implications of keepAlive and keepaliveTimeout on stacked protocols with keepalives? (3 by dhobsd, tfpauly)
    https://github.com/ietf-tapswg/api-drafts/issues/1428 [Implementation] 
  - #1371 About using [] in the addRemote call (1 by tfpauly)
    https://github.com/ietf-tapswg/api-drafts/issues/1371 [API] [From a partial review] 
  - #1260 Is "IP Address" scoped?  (section 1) (1 by tfpauly)
    https://github.com/ietf-tapswg/api-drafts/issues/1260 [API] 
  - #1256 How to signal equivalence of security properties (1 by britram)
    https://github.com/ietf-tapswg/api-drafts/issues/1256 [API] [Architecture] 

  25 issues closed:
  - AddAlias or array https://github.com/ietf-tapswg/api-drafts/issues/1309 [API] 
  - What are implications of keepAlive and keepaliveTimeout on stacked protocols with keepalives? https://github.com/ietf-tapswg/api-drafts/issues/1428 [Implementation] 
  - It's not only about "multiple interfaces" https://github.com/ietf-tapswg/api-drafts/issues/1258 [API] 
  - Section 6.1: per service, per IP address https://github.com/ietf-tapswg/api-drafts/issues/1296 [API] 
  - How to implement security considerations? https://github.com/ietf-tapswg/api-drafts/issues/1325 [API] [From a partial review] 
  - Zero values for some properties are invalid or unspecified https://github.com/ietf-tapswg/api-drafts/issues/1433 [API] 
  - Change a few examples from IPv4/LTE to IPv6? https://github.com/ietf-tapswg/api-drafts/issues/1324 [Implementation] 
  - IPv6 address representation and port number https://github.com/ietf-tapswg/api-drafts/issues/1322 [Implementation] 
  - Clone going sideways https://github.com/ietf-tapswg/api-drafts/issues/1301 [API] 
  - How does an application learn allowed/available interface names? https://github.com/ietf-tapswg/api-drafts/issues/1331 [API] [review - must reply] 
  - Define words related to Connection states https://github.com/ietf-tapswg/api-drafts/issues/1377 [API] [From a partial review] 
  - How to signal equivalence of security properties https://github.com/ietf-tapswg/api-drafts/issues/1256 [API] [Architecture] 
  - What is "credentials"? https://github.com/ietf-tapswg/api-drafts/issues/1370 [API] [From a partial review] 
  - Identity https://github.com/ietf-tapswg/api-drafts/issues/1367 [API] [From a partial review] 
  - How to set remote peer's identity or certificate https://github.com/ietf-tapswg/api-drafts/issues/1375 [API] [From a partial review] 
  - Single credentials for multiple protocols? https://github.com/ietf-tapswg/api-drafts/issues/1358 [API] [review - must reply] [From a partial review] 
  - Parameters take algorithms as a parameter https://github.com/ietf-tapswg/api-drafts/issues/1389 [API] 
  - Identity and server-certificate forces same use over different protocols? https://github.com/ietf-tapswg/api-drafts/issues/1359 [API] [review - must reply] [From a partial review] 
  - Single credentials for multiple protocols? https://github.com/ietf-tapswg/api-drafts/issues/1358 [API] [review - must reply] [From a partial review] 
  - Clarify ambiguity in security properties (section 6.3 DISCUSS from Roman Danyliw) https://github.com/ietf-tapswg/api-drafts/issues/1286 [API] [review - must reply] 
  - Why didn't we overload WithIPAddress for multicast? https://github.com/ietf-tapswg/api-drafts/issues/1343 [API] 
  - Define "represent the same host" https://github.com/ietf-tapswg/api-drafts/issues/1339 [API] 
  - Programmer can't know that all endpoints are the same service https://github.com/ietf-tapswg/api-drafts/issues/1340 [API] 
  - Code location https://github.com/ietf-tapswg/api-drafts/issues/1329 [Implementation] [From a partial review] 
  - Is "IP Address" scoped?  (section 1) https://github.com/ietf-tapswg/api-drafts/issues/1260 [API] 



Pull requests
-------------
* ietf-tapswg/api-drafts (+5/-17/💬3)
  5 pull requests submitted:
  - Explain stacked layers of keep alive protocols (by tfpauly)
    https://github.com/ietf-tapswg/api-drafts/pull/1452 [Implementation] 
  - Rework aliases (by tfpauly)
    https://github.com/ietf-tapswg/api-drafts/pull/1451 [API] 
  - Interfaces -> network paths (by tfpauly)
    https://github.com/ietf-tapswg/api-drafts/pull/1450 [API] 
  - Security equivalence is in system policy. (by britram)
    https://github.com/ietf-tapswg/api-drafts/pull/1449 
  - Make IPv4 and IPv6 port numbers consistent (by philsbln)
    https://github.com/ietf-tapswg/api-drafts/pull/1448 [Implementation] [From a partial review] 

  3 pull requests received 3 new comments:
  - #1444 keepAliveTimeout: introduce `System default` (1 by tfpauly)
    https://github.com/ietf-tapswg/api-drafts/pull/1444 [API] 
  - #1434 Where do interface names come from? (1 by mwelzl)
    https://github.com/ietf-tapswg/api-drafts/pull/1434 [API] 
  - #1430 Disambiguate security properties per rdd review (1 by britram)
    https://github.com/ietf-tapswg/api-drafts/pull/1430 

  17 pull requests merged:
  - Rework aliases
    https://github.com/ietf-tapswg/api-drafts/pull/1451 [API] 
  - Explain stacked layers of keep alive protocols
    https://github.com/ietf-tapswg/api-drafts/pull/1452 [Implementation] 
  - Interfaces -> network paths
    https://github.com/ietf-tapswg/api-drafts/pull/1450 [API] 
  - Not "values" for "Connectedness"
    https://github.com/ietf-tapswg/api-drafts/pull/1440 [Implementation] [editorial] 
  - Well-known service names come from the IANA list
    https://github.com/ietf-tapswg/api-drafts/pull/1441 [API] 
  - How to choose security protocols is out of scope, but cite RFC 8922
    https://github.com/ietf-tapswg/api-drafts/pull/1442 [API] 
  - What about zero Integer or Numeric values?
    https://github.com/ietf-tapswg/api-drafts/pull/1443 [API] 
  - Make IPv4 and IPv6 port numbers consistent
    https://github.com/ietf-tapswg/api-drafts/pull/1448 [Implementation] [From a partial review] 
  - Clone going sideways (later)
    https://github.com/ietf-tapswg/api-drafts/pull/1438 [API] 
  - Where do interface names come from?
    https://github.com/ietf-tapswg/api-drafts/pull/1434 [API] 
  - Three new read-only Connection properties
    https://github.com/ietf-tapswg/api-drafts/pull/1437 [API] 
  - Security equivalence is in system policy.
    https://github.com/ietf-tapswg/api-drafts/pull/1449 
  - Disambiguate security properties per rdd review
    https://github.com/ietf-tapswg/api-drafts/pull/1430 
  - Explain reason for separate multicast specifiers
    https://github.com/ietf-tapswg/api-drafts/pull/1436 [API] [From a partial review] 
  - Clarify multiple Local/remote endpoints
    https://github.com/ietf-tapswg/api-drafts/pull/1447 [API] [From a partial review] 
  - Section 11: not all state transitions have events
    https://github.com/ietf-tapswg/api-drafts/pull/1445 [API] 
  - Point at Software Heritage Archive
    https://github.com/ietf-tapswg/api-drafts/pull/1446 [Implementation] 


Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-tapswg/api-drafts