Re: [webauthn] Allow caller to pick between strict and eTLD+1 matching

For either of these solutions, please note that RFC 7719 basically 
says that "eTLD+1" is not well defined. Quoting: "Note that the term 
"public suffix" is controversial in the DNS community for many 
reasons, and may be significantly changed in the future." Can we 
clarify that the Mozilla-maintained list of public suffixes is 
authoritative on this term?

-- 
GitHub Notification of comment by yaronf
Please view or discuss this issue at 
https://github.com/w3c/webauthn/pull/162#issuecomment-245349131 using 
your GitHub account

Received on Wednesday, 7 September 2016 17:03:53 UTC