Issues
------
* ietf-tapswg/api-drafts (+1/-0/💬1)
1 issues created:
- Clarify that more flexible resolution is an architectural feature (by
britram)
https://github.com/ietf-tapswg/api-drafts/issues/385 [Architecture]
1 issues received 1 new comments:
- #371 Do we need an example for an HTTP/1, HTTP/2, HTTP/3 agnostic
connection? (1 by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/371 [API]
Pull requests
-------------
* ietf-tapswg/api-drafts (+2/-1/💬8)
2 pull requests submitted:
- Fix #385: Resolution is key to path and stack agility. Say so. (by britram)
https://github.com/ietf-tapswg/api-drafts/pull/387
- Minor editorial tweaks to Architecture (by britram)
https://github.com/ietf-tapswg/api-drafts/pull/386
2 pull requests received 8 new comments:
- #381 Move Transport Properties text and close #373 (7 by philsbln,
abrunstrom, britram, tfpauly)
https://github.com/ietf-tapswg/api-drafts/pull/381
- #387 Fix #385: Resolution is key to path and stack agility. Say so. (1 by britram)
https://github.com/ietf-tapswg/api-drafts/pull/387
1 pull requests merged:
- Minor editorial tweaks to Architecture
https://github.com/ietf-tapswg/api-drafts/pull/386
Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-tapswg/api-drafts
_______________________________________________
Taps mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/taps
