Issues
------
* ietf-tapswg/api-drafts (+6/-11/💬14)
6 issues created:
- We fixed ARCH lets fix Imple (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/958
- Impl: Pooled Connection (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/956 [Implementation]
- We fixed Arch - let's fix API (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/955 [API]
- TAPS API sits above the Transport System (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/953 [API]
- Arch-Review MW: Connections introducing head-of-line blocking (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/945 [Architecture]
- Arch-Review MW: (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/944 [API] [editorial]
11 issues received 14 new comments:
- #901 ART-ART: Explicit context in the Send in example in 3.1.1 (2 by mwelzl,
tfpauly)
https://github.com/ietf-tapswg/api-drafts/issues/901 [API] [editorial]
- #919 ART-ART: Send events too limiting? (2 by mwelzl, gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/919 [API]
- #914 ART-ART: MUST NOT in section 8 paragraph 3 (2 by mwelzl, gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/914 [API]
- #865 Should Endpoint Object identifiers be discoverable? (1 by britram)
https://github.com/ietf-tapswg/api-drafts/issues/865 [API]
- #945 Arch-Review MW: Connections introducing head-of-line blocking (1 by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/945 [Architecture]
- #909 ART-ART: WithServiceName (1 by britram)
https://github.com/ietf-tapswg/api-drafts/issues/909 [API]
- #879 ART-ART: Separation of architecture and interface documents (1 by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/879 [Architecture]
- #915 ART-ART: be clearer with RFC 7556 reference (1 by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/915 [API]
- #918 ART-ART: scope vs. framer (1 by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/918 [API]
- #184 Replace long author lists with editors (1 by gorryfair)
https://github.com/ietf-tapswg/api-drafts/issues/184 [wontfix] [API] [admin stuff]
- #911 ART-ART: how does an application doing ICE learn about candidates? (1 by tfpauly)
https://github.com/ietf-tapswg/api-drafts/issues/911 [API]
11 issues closed:
- TAPS API sits above the Transport System https://github.com/ietf-tapswg/api-drafts/issues/953 [API]
- ART-ART: MUST NOT in section 8 paragraph 3 https://github.com/ietf-tapswg/api-drafts/issues/914 [API]
- ART-ART: Avoid "atop" and "underneath" https://github.com/ietf-tapswg/api-drafts/issues/895 [API] [editorial]
- ART-ART: Make sure that language can age well https://github.com/ietf-tapswg/api-drafts/issues/894 [API] [editorial]
- Add implementation text for multicast https://github.com/ietf-tapswg/api-drafts/issues/876 [Implementation]
- ART-ART: high vs. low priority values vs. semantics https://github.com/ietf-tapswg/api-drafts/issues/917 [API] [editorial]
- ART-ART: Introduce Caching https://github.com/ietf-tapswg/api-drafts/issues/883 [Architecture] [editorial]
- ART-ART: Tidy "cleaning up" in Arch https://github.com/ietf-tapswg/api-drafts/issues/892 [Architecture] [editorial]
- Are scoped IPv6 address (and zone indexes in particular) supported? https://github.com/ietf-tapswg/api-drafts/issues/864 [API]
- ART-ART: Explicit context in the Send in example in 3.1.1 https://github.com/ietf-tapswg/api-drafts/issues/901 [API] [editorial]
- what does connected mean? https://github.com/ietf-tapswg/api-drafts/issues/737 [Implementation]
Pull requests
-------------
* ietf-tapswg/api-drafts (+14/-12/💬7)
14 pull requests submitted:
- And then there were five authors.... (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/pull/960
- And then there were five authors.... (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/pull/959 [Architecture]
- Trying to align more with ARCH draft-ietf-taps-impl.md (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/pull/957
- Terms for Transport Services (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/pull/954
- Minset: Fixing wrong statement about missing soft error, name cleanup (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/pull/952
- ARCH components. (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/pull/951
- API: PVD and other queriable info (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/pull/950 [API]
- Remove a MUST NOT (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/pull/949
- PR to address Arch-Review MW (by gorryfair)
https://github.com/ietf-tapswg/api-drafts/pull/948
- Be careful with the results of Preconnection.Resolve() (by britram)
https://github.com/ietf-tapswg/api-drafts/pull/947
- Scoped IPv6 addresses (by britram)
https://github.com/ietf-tapswg/api-drafts/pull/946
- clean up cleaning up (by britram)
https://github.com/ietf-tapswg/api-drafts/pull/943
- Introduce caching as an implementation feature (by britram)
https://github.com/ietf-tapswg/api-drafts/pull/942
- flexibile? (by britram)
https://github.com/ietf-tapswg/api-drafts/pull/941
6 pull requests received 7 new comments:
- #931 Add a Connection to a group at any time, also on the passive side (2 by
mwelzl, gorryfair)
https://github.com/ietf-tapswg/api-drafts/pull/931 [discuss]
- #934 Explicit context in example (1 by mwelzl)
https://github.com/ietf-tapswg/api-drafts/pull/934 [API] [editorial]
- #935 s/MUST/SHOULD because else we don't even eat our own dog food :) (1 by mwelzl)
https://github.com/ietf-tapswg/api-drafts/pull/935 [Architecture]
- #952 Minset: Fixing wrong statement about missing soft error, name cleanup (1 by mwelzl)
https://github.com/ietf-tapswg/api-drafts/pull/952 [API]
- #949 Remove a MUST NOT (1 by gorryfair)
https://github.com/ietf-tapswg/api-drafts/pull/949 [API] [editorial]
- #951 ARCH components. (1 by gorryfair)
https://github.com/ietf-tapswg/api-drafts/pull/951
12 pull requests merged:
- ARCH components.
https://github.com/ietf-tapswg/api-drafts/pull/951 [API]
- Remove a MUST NOT
https://github.com/ietf-tapswg/api-drafts/pull/949 [API] [editorial]
- s/MUST/SHOULD because else we don't even eat our own dog food :)
https://github.com/ietf-tapswg/api-drafts/pull/935 [Architecture]
- Ensure language can age well, avoid atop and underneath
https://github.com/ietf-tapswg/api-drafts/pull/929 [API] [editorial]
- Multicast reuse draft-ietf-taps-impl.md
https://github.com/ietf-tapswg/api-drafts/pull/877 [Implementation]
- Priority values: higher = higher.
https://github.com/ietf-tapswg/api-drafts/pull/928 [API]
- Small fixes to Gorry's latest arch update.
https://github.com/ietf-tapswg/api-drafts/pull/940 [Architecture]
- Caching and racing in implementation intro
https://github.com/ietf-tapswg/api-drafts/pull/942 [Architecture]
- clean up cleaning up
https://github.com/ietf-tapswg/api-drafts/pull/943
- Scoped IPv6 addresses
https://github.com/ietf-tapswg/api-drafts/pull/946
- #737 "connected" doesn't mean send a packet to draft-ietf-taps-impl.md
https://github.com/ietf-tapswg/api-drafts/pull/878 [Implementation]
- flexibile?
https://github.com/ietf-tapswg/api-drafts/pull/941
Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-tapswg/api-drafts
_______________________________________________
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps
