Re: [web-nfc] Fix external type validation algorithm (#511)

By what I read from https://github.com/w3c/web-nfc/issues/511#issuecomment-570620933, and given that the latest spec is already checking 

> If input is not an ASCII string, is empty, or its length exceeds 255 bytes, return false.

I don't think we need to do the following checks

> Let asciiDomain be the result of running domain to ASCII given domain and true (as beStrict).
If asciiDomain is failure, return false.
If asciiDomain contains a forbidden host code point or U+005F LOW LINE (_), return false.

but just validating that `domain` is LDH-lable should be OK, because now our `domain` has nothing to do with DNS/IDN, it just serves as a namespace.


-- 
GitHub Notification of comment by leonhsl
Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/511#issuecomment-571945302 using your GitHub account

Received on Wednesday, 8 January 2020 08:36:53 UTC