Issues
------
* ietf-tapswg/api-drafts (+0/-1/💬2)
2 issues received 2 new comments:
- #440 Why do we use functions to set security parameters... (1 by philsbln)
https://github.com/ietf-tapswg/api-drafts/issues/440 [API] [ready for text]
- #398 Slim down per-protocol behavior, move other mappings out (1 by mwelzl)
https://github.com/ietf-tapswg/api-drafts/issues/398 [Implementation] [mappings] [ready for text]
1 issues closed:
- Why do we use functions to set security parameters... https://github.com/ietf-tapswg/api-drafts/issues/440 [API] [ready for text]
Pull requests
-------------
* ietf-tapswg/api-drafts (+2/-1/💬0)
2 pull requests submitted:
- Unify establishment errors (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/pull/597
- Remove the "lower-case" requirement for transport property names (by mwelzl)
https://github.com/ietf-tapswg/api-drafts/pull/596
1 pull requests merged:
- Remove the "lower-case" requirement for transport property names
https://github.com/ietf-tapswg/api-drafts/pull/596
Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-tapswg/api-drafts
_______________________________________________
Taps mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/taps
