[Taps] Weekly github digest (TAPS GitHub Activity Digest)

[TAPS WG status robot <[e-mail]>]

Issues
------
* ietf-tapswg/api-drafts (+0/-25/💬20)
  13 issues received 20 new comments:
  - #852 Using Multicast Endpoints (7 by mwelzl, gorryfair, GrumpyOldTroll)
    https://github.com/ietf-tapswg/api-drafts/issues/852 [API] 
  - #865 Should Endpoint Object identifiers be discoverable? (2 by mwelzl, dhobsd)
    https://github.com/ietf-tapswg/api-drafts/issues/865 [API] 
  - #864 Are scoped IPv6 address (and zone indexes in particular) supported? (1 by britram)
    https://github.com/ietf-tapswg/api-drafts/issues/864 [API] 
  - #800 Remove use of the word TAPS? (1 by britram)
    https://github.com/ietf-tapswg/api-drafts/issues/800 [API] [editorial] 
  - #802 S3.2: Reference to single namespace is unclear (1 by britram)
    https://github.com/ietf-tapswg/api-drafts/issues/802 [API] [editorial] 
  - #811 S4.2.11. Interface Instance or Type - text clarification needed (1 by britram)
    https://github.com/ietf-tapswg/api-drafts/issues/811 [API] [editorial] 
  - #843 Where are events sent? (1 by britram)
    https://github.com/ietf-tapswg/api-drafts/issues/843 [API] [editorial] 
  - #815 S7.3.2.1. - send replies and map responses to their requests (1 by britram)
    https://github.com/ietf-tapswg/api-drafts/issues/815 [API] 
  - #753 Nit: Section 3.1: No such protocol… (1 by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/753 [Implementation] [editorial] 
  - #819 EstablishementError or InitiateError? Both names are used. (1 by britram)
    https://github.com/ietf-tapswg/api-drafts/issues/819 [API] [editorial] 
  - #791 be more concrete about receiving (1 by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/791 [API] 
  - #672 Perform a final edit pass on all three docs: normalize capitalization/spelling of keywords, formatting, pseudocode syntax, etc. (1 by britram)
    https://github.com/ietf-tapswg/api-drafts/issues/672 [API] [Architecture] [Implementation] [editorial] [ready for text] 
  - #798 S1.1: Definition of Tuple refers to property before it is defined (1 by britram)
    https://github.com/ietf-tapswg/api-drafts/issues/798 [API] [editorial] 

  25 issues closed:
  - S3.1.3 Wrong event handler in code exampe https://github.com/ietf-tapswg/api-drafts/issues/801 [API] [editorial] 
  - unified interface to datagram and connection-oriented transports https://github.com/ietf-tapswg/api-drafts/issues/846 [API] [editorial] 
  - Nit: Section 3.1: No such protocol… https://github.com/ietf-tapswg/api-drafts/issues/753 [Implementation] [editorial] 
  - argh unbreak circleci again https://github.com/ietf-tapswg/api-drafts/issues/738 
  - API summary does more than summarise https://github.com/ietf-tapswg/api-drafts/issues/849 [API] [editorial] 
  - Scope of the Interface Definition https://github.com/ietf-tapswg/api-drafts/issues/851 [API] [editorial] 
  - Endpoint aliases and protocols https://github.com/ietf-tapswg/api-drafts/issues/854 [API] [editorial] 
  - Where are events sent? https://github.com/ietf-tapswg/api-drafts/issues/843 [API] [editorial] 
  - Can we give the tables names in Appendix B? https://github.com/ietf-tapswg/api-drafts/issues/850 [API] [editorial] 
  - EstablishementError or InitiateError? Both names are used. https://github.com/ietf-tapswg/api-drafts/issues/819 [API] [editorial] 
  - Convenience Functions - options rather than requirements https://github.com/ietf-tapswg/api-drafts/issues/820 [API] [editorial] 
  - S7.1.3.3. Ordered - Default seems to point to wrong Selection Property https://github.com/ietf-tapswg/api-drafts/issues/814 [API] [editorial] 
  - S7.3.3.1. UDP(-Lite)-specific Property: ECN - Motivation https://github.com/ietf-tapswg/api-drafts/issues/817 [API] [editorial] 
  - S4.2.3. What makes Configure Per-Message Reliability special? https://github.com/ietf-tapswg/api-drafts/issues/807 [API] [editorial] 
  - S7.3.2.2. ReceivedPartial Example https://github.com/ietf-tapswg/api-drafts/issues/816 [API] [editorial] 
  -  6. Managing Connections - overlapping bullets https://github.com/ietf-tapswg/api-drafts/issues/813 [API] [editorial] 
  - S4.2.11. Interface Instance or Type - text clarification needed https://github.com/ietf-tapswg/api-drafts/issues/811 [API] [editorial] 
  - S4.2 Use of recommended  https://github.com/ietf-tapswg/api-drafts/issues/805 [API] [editorial] 
  - S3.2.2: Enumeration is a basic type so the two bullets do not read correctly https://github.com/ietf-tapswg/api-drafts/issues/803 [API] [editorial] 
  - S3.2: Reference to single namespace is unclear https://github.com/ietf-tapswg/api-drafts/issues/802 [API] [editorial] 
  - S2. Very long bullets are hard to read https://github.com/ietf-tapswg/api-drafts/issues/799 [API] [editorial] 
  - S1.1: Definition of Tuple refers to property before it is defined https://github.com/ietf-tapswg/api-drafts/issues/798 [API] [editorial] 
  - When are objects frozen? https://github.com/ietf-tapswg/api-drafts/issues/859 [API] [Implementation] 
  - S4.2.14. Multipath Transport - why different? https://github.com/ietf-tapswg/api-drafts/issues/812 [API] 
  - Remove use of the word TAPS? https://github.com/ietf-tapswg/api-drafts/issues/800 [API] [editorial] 



Pull requests
-------------
* ietf-tapswg/api-drafts (+6/-9/💬4)
  6 pull requests submitted:
  - Resolve #872: text disclaiming multicast rendezvous (by GrumpyOldTroll)
    https://github.com/ietf-tapswg/api-drafts/pull/871 
  - editorial rollup number three (by britram)
    https://github.com/ietf-tapswg/api-drafts/pull/870 
  - section refactor (by britram)
    https://github.com/ietf-tapswg/api-drafts/pull/869 
  - More editorial fixes. (by britram)
    https://github.com/ietf-tapswg/api-drafts/pull/868 
  - Many editorial fixes (rollup 1) (by britram)
    https://github.com/ietf-tapswg/api-drafts/pull/867 
  - Preconnections are just structs (by mwelzl)
    https://github.com/ietf-tapswg/api-drafts/pull/866 [API] 

  3 pull requests received 4 new comments:
  - #862 Help UDP fit wrt connection (2 by gorryfair, csperkins)
    https://github.com/ietf-tapswg/api-drafts/pull/862 [Architecture] 
  - #869 section refactor (1 by britram)
    https://github.com/ietf-tapswg/api-drafts/pull/869 
  - #863 Re-group managing  properties & protocol instances (1 by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/pull/863 [API] [editorial] 

  9 pull requests merged:
  - editorial rollup number three
    https://github.com/ietf-tapswg/api-drafts/pull/870 
  - section refactor
    https://github.com/ietf-tapswg/api-drafts/pull/869 
  - Editorial nits
    https://github.com/ietf-tapswg/api-drafts/pull/856 [API] [editorial] 
  - More editorial fixes.
    https://github.com/ietf-tapswg/api-drafts/pull/868 
  - Many editorial fixes (rollup 1)
    https://github.com/ietf-tapswg/api-drafts/pull/867 
  - Preconnections are just structs
    https://github.com/ietf-tapswg/api-drafts/pull/866 [API] 
  - Fixes #812
    https://github.com/ietf-tapswg/api-drafts/pull/857 [API] 
  - Help UDP fit wrt connection
    https://github.com/ietf-tapswg/api-drafts/pull/862 [Architecture] 
  - Re-group managing  properties & protocol instances
    https://github.com/ietf-tapswg/api-drafts/pull/863 [API] [editorial] 


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