- From: François Beaufort via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 Jan 2020 07:22:12 +0000
- To: public-web-nfc@w3.org
From what I can read, "NFC Data Exchange Format" spec says
> - The use of IP addresses in URIs SHOULD be avoided whenever possible (see [RFC 1900]). However, when used, the literal format for IPv6 addresses in URIs described by [RFC 2732] SHOULD be supported.
> - Generators of NDEF messages SHOULD rely only on the most rudimentary equivalence rules defined by [RFC 3986]
And "Signature Record Type Definition" spec only mentions `dns-name` in M2M Certificate Profile.
```
GeneralName ::= CHOICE {
rfc822Name IA5String (SIZE (1..128)),
dNSName IA5String (SIZE (1..128)),
directoryName Name,
uniformResourceIdentifier IA5String (SIZE (1..128)),
iPAddress OCTET STRING (SIZE (1..16)),
--4 octets for IPV4 16 octets for IPV6
registeredID OBJECT IDENTIFIER
}
```
--
GitHub Notification of comment by beaufortfrancois
Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/511#issuecomment-571033201 using your GitHub account
Received on Monday, 6 January 2020 07:22:14 UTC