# US 2016/0366123 A1 · Device naming in an internet of things > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2016/0366123 A1 - Document ID: US20160366123A1 - Status: Published application - Kind: A1 - Application number: 14/865,987 - Filed: 2015-09-25 - Published: 2016-12-15 - Earliest claimed: 2015-06-10 - Assignees: McAfee, Inc. - Applicants: Mcafee, Inc. - Inventors: Ned M. Smith; Nathan Heldt-Sheller; Sven Schrecker - Web page: https://patentgrep.com/patent/US20160366123A1 ## CPC - H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)} - H04L 9/3268: {using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]} - H04L 61/4511: using domain name system [DNS] - H04L 63/062: {for key distribution, e.g. centrally by trusted party (cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819)} - H04L 63/1466: {Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks} - H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC] - H04W 12/082: using revocation of authorisation - H04W 12/12: Detection or prevention of fraud - H04W 12/122: Counter-measures against attacks; Protection against rogue devices - H04L 61/3025: {Domain name generation or assignment} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract In an example, there is disclosed a computing apparatus, having: a network interface; and one or more logic elements providing a name management engine, operable to: receive a self-assigned name registration request for a name N1 from an endpoint device via the network interface; compare N1 to a database of registered names; determine that the name has not been registered; and sign a certificate for N1. The engine is further operable to determine that the name has been registered, and send a notification that the name is not available. There is also disclosed a computer-readable medium having executable instructions for providing a name management engine, and a method of providing a name management engine. ## Claims ### Claim 1 A computing apparatus, comprising: a network interface; and one or more logic elements comprising a name management engine, operable to: receive a self-assigned name registration request for a name N1 from an endpoint device via the network interface; compare N1 to a database of registered names; determine that the name has not been registered; and sign a certificate for N1. ### Claim 2 (depends on 1) The computing apparatus of claim 1, wherein the name management engine is further operable to determine that the name has been registered, and send a notification that the name is not available. ### Claim 3 (depends on 1) The computing apparatus of claim 1, wherein the name management engine is further operable to determine that the endpoint device has a trusted execution environment (TEE) meeting a minimum security requirement, and wherein the certificate is a high veracity certificate. ### Claim 4 (depends on 1) The computing apparatus of claim 1, wherein the name management engine is further operable to determine that the endpoint device does not have a trusted execution environment (TEE) meeting a minimum security requirement, and wherein the certificate is a low veracity certificate. ### Claim 5 (depends on 1) The computing apparatus of claim 1, wherein the name management engine is further operable to determine that the name registration request is signed by a valid signature, and wherein the certificate is a high veracity certificate. ### Claim 6 (depends on 5) The computing apparatus of claim 5, wherein the valid signature is a proof of possession valid signature. ### Claim 7 (depends on 1) The computing apparatus of claim 1, wherein the name management engine is further operable to determine that the name registration request is not signed by a valid signature, and wherein the certificate is a low veracity certificate. ### Claim 8 (depends on 1) The computing apparatus of claim 1, wherein the name management engine is operable to receive a certificate revocation list (CRL). ### Claim 9 (depends on 8) The computing apparatus of claim 8, wherein receiving the CRL comprises receiving a name revocation request via the network interface. ### Claim 10 (depends on 9) The computing apparatus of claim 9, wherein the name revocation request is post-dated. ### Claim 11 (depends on 8) The computing apparatus of claim 8, wherein receiving the CRL comprises receiving a batch CRL via the network interface. ### Claim 12 (depends on 8) The computing apparatus of claim 8, wherein the name management engine is further operable to mark a plurality of names in the registered name database as revoked, wherein the plurality of names appear on the CRL. ### Claim 13 (depends on 8) The computing apparatus of claim 8, wherein the CRL is anonymized. ### Claim 14 One or more tangible, non-transitory computer readable storage mediums having stored thereon executable instructions for providing a name management engine, wherein the name management engine is configured to: receive a self-assigned name registration request for a name N1 from an endpoint device via a network interface; compare N1 to a database of registered names; determine that the name has not been registered; and sign a certificate for N1. ### Claim 15 (depends on 14) The one or more tangible, computer-readable storage mediums of claim 14, wherein the name management engine is further operable to determine that the name has been registered, and send a notification that the name is not available. ### Claim 16 (depends on 14) The one or more tangible, computer-readable storage mediums of claim 14, wherein the name management engine is further operable to determine that the endpoint device has a trusted execution environment (TEE) meeting a minimum security requirement, and wherein the certificate is a high veracity certificate. ### Claim 17 (depends on 14) The one or more tangible, computer-readable storage mediums of claim 14, wherein the name management engine is further operable to determine that the endpoint device does not have a trusted execution environment (TEE) meeting a minimum security requirement, and wherein the certificate is a low veracity certificate. ### Claim 18 (depends on 14) The one or more tangible, computer-readable storage mediums of claim 14, wherein the name management engine is further operable to determine that the name registration request is signed by a valid proof of possession signature, and wherein the certificate is a high veracity certificate. ### Claim 19 (depends on 14) The one or more tangible, computer-readable storage mediums of claim 14, wherein the name management engine is further operable to determine that the name registration request is not signed by a valid signature, and wherein the certificate is a low veracity certificate. ### Claim 20 (depends on 14) The one or more tangible, computer-readable storage mediums of claim 14, wherein the name management engine is operable to receive an anonymized certificate revocation list (CRL). ### Claim 21 (depends on 20) The one or more tangible, computer-readable storage mediums of claim 20, wherein receiving the CRL comprises receiving a name revocation request via the network interface. ### Claim 22 (depends on 21) The one or more tangible, computer-readable storage mediums of claim 21, wherein the name revocation request is post-dated. ### Claim 23 (depends on 20) The one or more tangible, computer-readable storage mediums of claim 20, wherein receiving the CRL comprises receiving a batch CRL via the network interface. ### Claim 24 A computing apparatus, comprising: a network interface; and a key management engine operable to: determine that a first device D1 in a first realm R1 with the computing apparatus needs to establish a connection with a second device D2 in a second realm R2; establish a secure channel with a secure management service of the second realm R2; and issue a key management ticket for D1 to securely communicate with D2. ### Claim 25 (depends on 24) The computing apparatus of claim 24, wherein the key management engine is further operable to perform a domain name system (DNS) lookup of a name for R1 or R2 on a DNS-based authentication of named entities (DANE) service.