Issues
------
* ietf-wg-dnsop/draft-ietf-dnsop-domain-verification-techniques (+1/-1/💬1)
 1 issues created:
 - Add security consideration for old domain owner retaining access (by enygren)
https://github.com/ietf-wg-dnsop/draft-ietf-dnsop-domain-verification-techniques/issues/209 [WGLC]
 1 issues received 1 new comments:
 - #167 Re-org discussion (Jan 29) (1 by enygren)
https://github.com/ietf-wg-dnsop/draft-ietf-dnsop-domain-verification-techniques/issues/167 [WGLC]
 1 issues closed:
- Threat model and random token lengths https://github.com/ietf-wg-dnsop/draft-ietf-dnsop-domain-verification-techniques/issues/199 [WGLC]


Pull requests
-------------
* ietf-wg-dnsop/draft-ietf-dnsop-domain-verification-techniques (+3/-0/💬0)
 3 pull requests submitted:
 -  (by enygren)
- (by enygren) - (by enygren)
* ietf-wg-dnsop/draft-ietf-dnsop-structured-dns-error (+2/-0/💬2)
 2 pull requests submitted:
 -  (by tireddy2)
- (by tireddy2)
 1 pull requests received 2 new comments:
 - #71 Address comments received during LC (2 by danwing, neilcook)
https://github.com/ietf-wg-dnsop/draft-ietf-dnsop-structured-dns-error/pull/71

Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-wg-dnsop/draft-ietf-dnsop-dnssec-automation
* 
https://github.com/ietf-wg-dnsop/draft-ietf-dnsop-domain-verification-techniques
* https://github.com/ietf-wg-dnsop/draft-ietf-dnsop-structured-dns-error
* https://github.com/ietf-wg-dnsop/draft-ietf-dnsop-qdcount-is-one
* https://github.com/ietf-wg-dnsop/draft-ietf-dnsop-algorithm-update
* https://github.com/ietf-wg-dnsop/draft-ietf-dnsop-must-not-sha1
* https://github.com/ietf-wg-dnsop/draft-ietf-dnsop-must-not-gost
* https://github.com/ietf-wg-dnsop/draft-ietf-dnsop-grease
* https://github.com/ietf-wg-dnsop/DNSOP_Doc_Tracker


--
To have a summary like this sent to your list, see: 
https://github.com/ietf-github-services/activity-summary
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to