DELEGATION OF A FUNCTION FOR RESOLVING NAMES

Description

Field of invention

[0001] The field of the invention is that of resolving naming identifiers such as domain names. More specifically, the invention relates to the delegation of a naming identifier resolution function, normally performed by naming identifier resolvers, to servers whose function is not this, such as servers hosting resources that terminals can access via an Internet browser. Prior art and its drawbacks

[0002] There [ Fig. 1 ] represents an example of a naming identifier resolution scenario. A terminal 10 issues an encrypted EFQDN (in English) naming identifier resolution request external fully qualified domain name) to a public naming identifier resolver 11 managed by a third-party company. The public resolver 11 then obtains network addresses, such as IP addresses ( Internet Protocol ) of IPv4 or IPv6 type, associated with servers 13 associated with the naming identifier to be resolved, these servers 13 storing data relating to the implementation of a service required by the terminal 10 such as data relating to a web page or data relating to downloadable content, etc. Such servers 13 are located in a separate third-party network which is not managed by an internet service provider ISP (in English Internet Service Provider) with which a user of terminal 10 has subscribed to a service offer.

[0003] Once in possession of the IP addresses (Internet Protocol)associated with the servers 13, the public resolver 11 transmits at least one of the IP addresses associated with the servers 13 to the terminal 10. The terminal 10 then establishes a connection with the corresponding server 13 and can access the data relating to the implementation of the required service.

[0004] In this scenario, the servers 13 associated with a naming identifier to be resolved are selected by the third-party company which manages the authoritative servers 12 without consultation with the internet service provider ISP with which a user of the terminal 10 has subscribed to a service offer.

[0005] This impacts the management of resources of the various communication equipment, managed by the internet service provider ISP with which a user of terminal 10 has subscribed to a service offer and involved in the resolution of naming identifiers which may not be used optimally.

[0006] There is therefore a need for a technique for resolving naming identifiers that does not have all or some of the aforementioned drawbacks. US 2017 / 048186 A1 describes a system for delegating the provision of DNS records to additional providers in which the resolution of domain names for certain types of records is delegated from an authoritative DNS service provider to one or more additional DNS service providers. Statement of the invention

[0007] The invention meets this need by proposing a method for resolving at least one naming identifier as claimed in claim 1.

[0008] Such a solution allows a third-party company that wishes to do so to delegate the resolution of naming identifiers carried out by default by naming identifier resolvers, which the third-party company manages, to servers hosting resources, such as web servers, managed for example by an internet service provider.

[0009] Delegating the resolution of naming identifiers to servers hosting resources makes it possible to reduce the costs associated with the execution of this naming identifier resolution function. Indeed, by delegating the resolution of naming identifiers to a server hosting resources, it is possible to reduce the number of connections between communication devices in order to resolve a naming identifier, in particular by reusing existing connections between user devices and servers hosting resources. Such a reduction in the number of connections between communication devices leads to a reduction in the energy consumption of these communication devices.

[0010] In addition, such a solution for delegating the resolution of naming identifiers also offers increased performance. This is due to the fact that the number of connections established between communication devices in order to resolve a naming identifier is reduced.

[0011] Finally, the proposed solution for delegating naming identifier resolution is reliable. Indeed, in the context of the described naming resolution method, a server hosting resources implementing naming identifier resolution instead of a naming identifier resolver is provided with an authorization to execute this function of resolving at least one naming identifier, which can be verified if necessary.

[0012] According to a particular characteristic of the naming identifier resolution method, the delegation parameter is a digital fingerprint of the naming identifier associated with said server hosting resources signed by a cryptographic key associated with an authoritative server associated with at least one naming identifier.

[0013] The delegation parameter is generated by an authoritative server associated with a naming identifier and is specific to each resource server to which a naming identifier resolution function is delegated. Thus, only a resource server authorized by an authoritative server associated with a naming identifier is delegated naming identifier resolution.

[0014] According to a particular characteristic of the method for resolving naming identifiers, the latter comprises, prior to the step of transmitting the delegation parameter, a step of receiving a message comprising the delegation parameter.

[0015] In a particular implementation of the naming identifier resolution method, the received message is sent by said authoritative server associated with at least one naming identifier.

[0016] Thus the authoritative server associated with a naming identifier to be resolved directly transmits the delegation parameter to the server hosting the resources concerned.

[0017] In a particular implementation of the naming identifier resolution method, the received message is issued by a naming identifier resolver.

[0018] In this implementation, the naming identifier resolver that is supposed to resolve a particular naming identifier relays a message, transmitted by the authoritative server associated with the particular naming identifier and including the delegation parameter, to the server hosting resources concerned. In this implementation, the naming identifier resolver that is supposed to resolve a particular naming identifier is thus informed of the delegation of the resolution of the particular naming identifier.

[0019] The invention also relates to a method for requesting resolution of at least one naming identifier according to claim 6. The terminal receives, in response to a request for access to the resources hosted by the server hosting resources, the delegation parameter of the server hosting resources.

[0020] The terminal then verifies the authenticity of this delegation parameter prior to any resolution of naming identifiers in order to ensure the reliability of the server hosting resources with regard to the resolution of naming identifiers.

[0021] When the authenticity of said delegation parameter is not verified, a step of issuing a request for resolution of the naming identifier to a naming identifier resolver.

[0022] When the terminal determines that the server hosting data is not authorized to resolve a particular naming identifier, the terminal then transmits a request to resolve the naming identifier in question to a naming identifier resolver that is known to be authorized to resolve naming identifiers.

[0023] According to an implementation of the method for requesting resolution of at least one naming identifier, this comprises a step of receiving a message, sent by the server hosting resources, comprising at least one network address of a server associated with a naming identifier to be resolved.

[0024] In this implementation of the method for requesting resolution of a naming identifier, the server hosting resources provides a network address of a server associated with a naming identifier that it is authorized to resolve without waiting for the terminal to verify the authenticity of the delegation parameter.

[0025] Such an implementation allows to reduce the processing time of the resolution of a naming identifier, since as soon as the authenticity of the delegation parameter is verified, the terminal can access a server associated with a naming identifier because it is already in possession of the network addresses of servers associated with a naming identifier.

[0026] According to another implementation of the method for requesting resolution of at least one naming identifier, this comprises when the authenticity of said delegation parameter is verified and prior to receiving the message comprising the network address of a server associated with said naming identifier to be resolved: a step of sending a request to resolve the naming identifier to the server hosting resources.

[0027] In this implementation of the method for requesting resolution of a naming identifier, the server hosting resources provides a network address of a server associated with a naming identifier that it is authorized to resolve in response to a naming identifier resolution request issued by the terminal after verifying the authenticity of the delegation parameter.

[0028] According to a particularity of the process of requesting resolution of a naming identifier, the verification of the authenticity of the delegation parameter includes: issuing a request for information relating to said resource-hosting server to a naming identifier resolver, receiving a message comprising a cryptographic key associated with an authoritative server associated with a naming identifier and the delegation parameter, verifying the delegation parameter transmitted by the resource-hosting server using the cryptographic key and the delegation parameter transmitted by the naming identifier resolver.

[0029] To ensure the authenticity of the delegation parameter transmitted by the server hosting resources, the terminal queries a naming identifier resolver which is considered to be a reliable device.

[0030] According to a particularity of the method of requesting resolution of a naming identifier, the delegation parameter is a digital fingerprint of the naming identifier associated with said server hosting resources signed by the cryptographic key associated with an authoritative server associated with a naming identifier.

[0031] The invention further relates to a server according to claim 9.

[0032] One such server hosting resources is, for example, a server managed by an internet service provider such as Orange. In this case, an example of resources hosted by such a server is the orange.fr homepage, which contains numerous links to other websites.

[0033] Another object of the invention relates to a terminal according to claim 10.

[0034] Such a terminal is, for example, a computer or a smartphone, equipped with an internet browser.

[0035] The invention finally relates to computer program products comprising program code instructions for implementing the methods as described above, when executed by a processor.

[0036] The invention also relates to a computer-readable recording medium on which computer programs are recorded comprising program code instructions for executing the steps of the methods according to the invention as described above.

[0037] Such a recording medium may be any entity or device capable of storing the program(s). For example, the medium may include a storage medium, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or a magnetic recording medium, for example a USB key or a hard disk.

[0038] On the other hand, such a recording medium may be a transmissible medium such as an electrical or optical signal, which may be conveyed via an electrical or optical cable, by radio or by other means, so that the computer programs contained therein are remotely executable. The programs according to the invention may in particular be downloaded over a network, for example the Internet.

[0039] Alternatively, the recording medium may be an integrated circuit in which the programs are incorporated, the circuit being adapted to execute or to be used in the execution of the methods which are the subject of the invention mentioned above. List of figures

[0040] Other aims, characteristics and advantages of the invention will appear more clearly on reading the following description, given as a simple illustrative, and non-limiting, example, in relation to the figures, among which: [ Fig. 1 ] : this figure represents an example of a naming identifier resolution scenario known from the state of the art, [ Fig. 2 ] : this figure represents a system in which the methods which are the subject of the invention are implemented, [ Fig. 3 ] : this figure represents a diagram of exchanges between different communication equipment involved in the implementation of the processes for resolving at least one naming identifier and requesting resolution of at least one naming identifier, [ Fig. 4 ] : this figure represents a terminal 10 according to an embodiment of the invention. Such a terminal 10 is capable of implementing the different embodiments of the method for requesting resolution of a naming identifier, [ Fig. 5 ]: this figure represents a server hosting resources capable of implementing the different embodiments of the naming identifier resolution method. Detailed description of embodiments of the invention

[0041] The general principle of the invention is based on the delegation of the resolution of naming identifiers usually carried out by naming identifier resolvers to servers hosting resources, such as web servers, managed for example by an internet service provider.

[0042] There [ Fig. 2 ] represents a system in which the methods that are the subject of the invention are implemented.

[0043] The system comprises at least one terminal 10 requiring a naming identifier resolution, a server hosting resources 14 whose naming identifier is for example orange.fr, at least one naming identifier resolver 11, at least one authoritative server 12 associated with a naming identifier and at least one server 13 associated with a naming identifier to be resolved, this server 13 storing data relating to the implementation of a service required by the terminal 10 such as data relating to a web page or data relating to downloadable content, etc.

[0044] The terminal 10 can exchange messages with the resource hosting server 14 and with the naming identifier resolver 11. A terminal 10 is a device that can issue requests to obtain content such as a personal computer, a home gateway, a digital television decoder, a smartphone, etc.

[0045] The naming identifier resolver 11 receives messages from the authoritative server 12 and exchanges messages with the resource hosting server 14 and the server 13.

[0046] The server 13 exchanges messages with the resource hosting server 14 and with the terminal 10.

[0047] These various message exchanges between these different devices as well as their contents are explained in more detail in the rest of this document.

[0048] There [ Fig. 3 ] represents a diagram of exchanges between different communication equipment involved in the implementation of the methods of resolving at least one naming identifier and requesting resolution of at least one naming identifier.

[0049] In a step E1, the authoritative server 12 associated with the naming identifier journal.fr transmits a first Record 1 message such as, for example, a DNS record type message comprising an IP address associated with the server 13 associated with the naming identifier journal.fr, to the naming identifier resolver 11. An example of such a Record 1 message is given below: DNS record journal.fr IN A: 10.1.1.10 where 10.1.1.10 is the IP address associated with the server 13 associated with the naming identifier journal.fr.

[0050] The authoritative server 12 can transmit in one or more Record 1 messages the IP addresses of different servers 13 associated with naming identifiers themselves associated with the authoritative server 12.

[0051] The naming identifier resolver 11 stores these IP addresses and the associated naming identifier in a lookup table used when resolving naming identifiers.

[0052] In a step E2, the authoritative server 12 associated with the naming identifier journal.fr transmits a second Record 2 message such as, for example, a DNS record ESNI type message comprising a cryptographic key associated with the authoritative server 12 and a delegation parameter associated with the server hosting resources 14 for the naming identifier journal.fr to the naming identifier resolver 11. An example of such a Record 2 message is given below: ESNI record journal.fr { SNI encryption key: C5E74D Trusted_entities : { orange.fr_encrypted: 9B5D248 #}

[0053] The authoritative server 12 transmits for each of the naming identifiers associated with it a Record 2 message comprising the cryptographic key associated with the authoritative server 12 and a delegation parameter associated with the server hosting resources 14 for a given naming identifier such as for example sport.com to the naming identifier resolver 11.

[0054] An example of such a Record 2 message is given below: ESNI record sport.com { SNI encryption key: C5E74D Trusted_entities : { orange.fr_encrypted: A359DA8}

[0055] In a known manner, in order to allow the encryption of an ESNI field of a TLS message (Transport Rent Security ) "ClientHello"issued by a terminal 10, the authoritative server associated with the naming identifier FQDN_i calculates a private and public cryptographic key pair. The authoritative server 12 associated with the naming identifier FQDN_i announces the public key in a DNS ESNI record type message to a naming identifier resolver 11. The terminal obtains this public key from the naming identifier resolver 11.

[0056] Once in possession of the public key, the terminal 11 encrypts the eSNI field of the TLS ClientHello message with this public key. The TLS ClientHello message is then transmitted to a server associated with the naming identifier FQDN_i. The server associated with the naming identifier FQDN_i decrypts the message. TLS ClientHello » using the private key and transmits a message “ServerHello TLS” to terminal 10 in order to establish an HTTPS connection between the server associated with the naming identifier FQDN_i and terminal 10.

[0057] In the present methods for resolving at least one naming identifier and requesting resolution of at least one naming identifier, the authoritative server 12 encrypts with the private key associated with the public key each naming identifier associated with a server hosting resources 14 to which it gives authorization to execute a function for resolving at least one naming identifier. In the example described, the public key of the authoritative server 12 is C5E74D. The authoritative server 12 then calculates a digital fingerprint of the naming identifier associated with the server hosting resources 14 signed by the cryptographic key associated with the authoritative server (12). Such a digital fingerprint is for example a hash of the public key and the naming identifier, orange.fr, associated with the server hosting resources 14.The authoritative server 12 thus determines the delegation parameter of the server hosting resources 14 for the naming identifier journal.fr: 9B5D248 #. The delegation parameter of the server hosting resources 14 is transmitted in the field. "Trusted-entities » and the public key of the authoritative server 12 is transmitted in the field « SNI encryption » key of the Record 2 message when it is a DNS record ESNI type.

[0058] In a particular embodiment of the methods for resolving at least one naming identifier and requesting resolution of at least one naming identifier, the different Record 1 and Record 2 messages are sent by the authoritative server 12 directly to the server hosting resources 14.

[0059] These steps E1 and E2 do not directly trigger steps E3 and following, but must be prior to them in order to ensure the correct execution of the processes for resolving at least one naming identifier and requesting resolution of at least one naming identifier.

[0060] In a step E3, the server hosting resources 14 stores, in cache, IP addresses of the servers 13 associated with naming identifiers. This information can be transmitted by authoritative servers 12 associated with naming identifiers.

[0061] During a step E4, the server hosting resources 14 sends a request RQ1 to the naming identifier resolver 11 in order to obtain a delegation parameter relating to a particular naming identifier in order to be able to resolve it. Such a request RQ1 is for example a message of the type DNS query ESNI ( Domain Name System query Encrypted Server Name Indication) including the naming identifier for which the delegation parameter is required, here journal.fr. Upon receipt of this request RQ1, the naming identifier resolver 11 sends, for example, an ESNI response message to the server hosting resources 14 in a step E5 and including the required delegation parameter, here 9B5D248 #.

[0062] The resource hosting server 14 issues such a request RQ1 for each of the naming identifiers for which a delegation parameter associated with the resource hosting server 14 has been generated by the authoritative server.

[0063] Such an ESNI response message includes, among other things, the delegation parameter associated with the server hosting resources 14 and corresponding to a particular naming identifier, for example journal.fr.

[0064] Similarly, the resolver 11 issues an ESNI response message for each of the naming identifiers for which a delegation parameter has been requested by the resource hosting server 14.

[0065] These steps E4 and E5 do not directly trigger steps E6 and following, but must be prior to them in order to ensure the correct execution of the processes for resolving at least one naming identifier and requesting resolution of at least one naming identifier.

[0066] The terminal 10 having established a communication session with the server hosting resources 14, it sends, in a step E6, a request for resources DR to the server hosting resources 14. Such a request for resources is for example a message of the type HTTPS GET resource orange.fr.

[0067] In response to this resource request DR, the resource hosting server 14 transmits, in a step E7, the requested resources as well as a list comprising the different delegation parameters associated with the resource hosting server 14 and corresponding to the different naming identifiers that the resource hosting server 14 is authorized to resolve. Thus, for the naming identifier journal.fr, the resource hosting server 14 transmits the delegation parameter 9B5D248#, and for the naming identifier sport.com, the resource hosting server 14 transmits the delegation parameter A359DA8.

[0068] In a particular embodiment, step E3 can be implemented by the server hosting resources 14 following the implementation of step E7, for example if it is the first time that the server hosting resources 14 receives a request for resources of the HTTPS GET resource orange.fr type from a terminal 10, following a cleaning of the cache of the server hosting resources 14 for example.

[0069] Steps E8 to E10 described below constitute a phase of verification of the authenticity of the delegation parameters transmitted by the server hosting resources 14.

[0070] Thus, in a step E8, the terminal 10 sends a request for information DI relating to the server hosting resources 14 to the naming identifier resolver 11. Such an information request comprises at least one naming identifier, for example journal.fr, for which the terminal wishes to verify the delegation parameter associated with the server hosting data 14. The information request DI is for example a message of the DNS query ESNI type.

[0071] In a step E9, the naming identifier resolver 11 transmits a message MSG1, such as for example a DNS record ESNI type message, comprising the public key C5E74D associated with the authoritative server 12 and the delegation parameter 9B5D248 # associated with the server hosting resources 14 for the naming identifier journal.fr.

[0072] In this implementation example, at the end of step E9, the terminal 10 has a first version V1 of the delegation parameter associated with the server hosting resources 14 for the naming identifier journal.fr that it received from the server hosting resources 14 during step E7, and a second version V2 of the delegation parameter associated with the server hosting resources 14 for the naming identifier journal.fr that it received from the naming identifier resolver 11 during step E9. This second version V2 of the delegation parameter associated with the server hosting resources 14 for the naming identifier journal.fr is considered reliable because it is issued by a reliable device, namely the naming identifier resolver 11.

[0073] During a step E10, the terminal 10 verifies the authenticity of the first version V1 of the delegation parameter. For this, the terminal 10 uses the ESNI encryption parameters, such as for example the public key C5E74D, associated with the authoritative server 12 in order to verify the authenticity of the digital fingerprint of the first version V1 of the delegation parameter, it thus obtains a first decrypted version DcV1 of the naming identifier of the server hosting resources 14. The first decrypted version DcV1 of the naming identifier gives “orange.fr”.

[0074] The terminal 10 also decrypts the second version V2 of the delegation parameter associated with the server hosting resources 14 using the public key, thus obtaining a second decrypted version DcV2 of the naming identifier of the server hosting resources 14. Here, the second decrypted version DcV2 of the naming identifier thus decrypted gives “orange.fr”. The terminal 10 then compares the first decrypted version DcV1 of the naming identifier of the server hosting resources 14 with the second decrypted version DcV2 of the naming identifier of the server hosting resources 14. When the two decrypted versions DcV1 and decrypted DcV2 of the naming identifier associated with the server hosting resources 14 match, the authenticity of the delegation parameter associated with the server hosting resources 14 for a given naming identifier is verified.

[0075] When the authenticity of the delegation parameter associated with the server hosting resources 14 for a given naming identifier is verified, the terminal 10 then sends, in a step E11, a request for resolution of FQDN naming identifiers to the server hosting resources 14. Such a request for resolution of FQDN naming identifiers may comprise a single naming identifier to be resolved or all of the naming identifiers for which the server hosting resources 14 is authorized to execute a naming identifier resolution function. Such a request for resolution of FQDN naming identifiers is for example a message of the DOH query ip type comprising at least one naming identifier.

[0076] In a step E12, the server hosting resources 14 sends an MSG2 message to the terminal 10. The MSG2 message comprises at least one network address of a server 13 associated with a naming identifier to be resolved, this server 13 storing data relating to the implementation of a service required by the terminal 10.

[0077] In a particular embodiment, called "push" mode, of the methods for resolving at least one naming identifier and requesting resolution of at least one naming identifier, step E11 is not implemented by the terminal 10 and step E12 is placed between steps E7 and E8. This embodiment makes it possible to reduce the processing time for resolving a naming identifier, since as soon as the authenticity of the delegation parameter is verified, the terminal 10 can access a server 13 associated with a naming identifier because it is already in possession of the network addresses of servers 13 associated with a naming identifier.

[0078] When the two decrypted DcV1 and decrypted DcV2 versions of the naming identifier associated with the server hosting resources 14 do not match, the authenticity of the delegation parameter associated with the server hosting resources 14 for a given naming identifier is not verified.

[0079] In such a situation, the terminal 10 behaves as if it had not received delegation parameters from the server hosting resources 14 and sends, during a step E13, a request for resolution of FQDN2 naming identifiers to the naming identifier resolver 11 requesting the resolution of at least one naming identifier for which the server hosting resources 14 is not authorized to perform a naming identifier resolution. Such a request for resolution of FQDN2 naming identifiers comprises the naming identifier to be resolved, for example sport.com. Such a request for resolution of FQDN2 naming identifiers is for example a message of the DOH query ip type.

[0080] During a step E14, the naming identifier resolver 11 sends a message MSG3 to the terminal 10. The message MSG2 includes at least one network address of a server 13 associated with the naming identifier to be resolved, here sport.com.

[0081] In a particular embodiment, the naming identifier resolution function may be limited only to the naming identifiers of contents referenced in the resources hosted by the resource hosting server 14. Thus, the terminal 10 may reject resolutions of certain naming identifiers for which the resource hosting server 14 has a resolution delegation but whose contents are not hosted by the resource hosting server 14. For example, the resource hosting server 14 has a delegation to resolve the naming identifier replay.fr but the content associated with this naming identifier replay.fr is not referenced among the resources hosted by the resource hosting server 14; in this case, the terminal 10 does not transmit a naming identifier resolution request to the resource hosting server 14 for the naming identifier replay.fr.

[0082] In a step E15, the terminal 10 sends a request for DS resources to a server 13 in order to obtain data relating to the implementation of a service required by the terminal 10. Such a request to establish a DS communication session is for example a message of the type GET journal.fr content from @ip_journal.fr.

[0083] In response to this request for DS resources, the server 13 provides the required resource during a step E16.

[0084] There [ Fig. 4 ] represents a terminal 10 according to one embodiment of the invention. Such a terminal 10 is capable of implementing the different embodiments of the method for requesting resolution of a naming identifier according to the figure 3 .

[0085] A terminal 10 may comprise at least one hardware processor 41, a storage unit 42, an input device 43, a display device 44, an interface 45, and at least one network interface 46 which are connected to each other through a bus 47. Of course, the constituent elements of the terminal 10 may be connected by means of a connection other than a bus.

[0086] The processor 41 controls the operations of the terminal 10. The storage unit 42 stores at least one program for implementing the method according to an embodiment of the invention to be executed by the processor 41, and various data, such as parameters used for calculations performed by the processor 41, intermediate data of calculations performed by the processor 41, etc. The processor 41 may be formed by any known and suitable hardware or software, or by a combination of hardware and software. For example, the processor 41 may be formed by dedicated hardware such as a processing circuit, or by a programmable processing unit such as a central processing unit ( Central Processing Unit ) which executes a program stored in a memory of it.

[0087] The storage unit 42 may be formed by any suitable means capable of storing the program(s) and data in a computer-readable manner. Examples of the storage unit 42 include non-transitory computer-readable storage media such as semiconductor memory devices, and magnetic, optical, or magneto-optical recording media loaded into a read-write unit.

[0088] The input device 43 may be formed by a keyboard, a pointing device such as a mouse to be used by a user to enter commands. The display device 504 may also be formed by a display module, such as for example a graphical user interface or GUI (for Graphical User Interface ).

[0089] Interface 45 provides an interface between terminal 10 and other equipment.

[0090] At least one network interface 46 provides a connection between the terminal 10 and the resource hosting server 14, the resolver 11 and the servers 13.

[0091] There [ Fig. 5 ] represents a server hosting resources 14 capable of implementing the different embodiments of the method for resolving naming identifiers according to the figure 3 .

[0092] A resource hosting server 14 may comprise at least one hardware processor 51, a storage unit 52, and at least one network interface 53 which are connected to each other through a bus 54. Of course, the constituent elements of the resource hosting server 14 may be connected by means of a connection other than a bus.

[0093] The processor 51 controls the operations of the resource-hosting server 14. The storage unit 52 stores at least one program for implementing the method according to an embodiment to be executed by the processor 51, and various data, such as parameters used for calculations performed by the processor 51, intermediate data of calculations performed by the processor 51, etc. The processor 51 may be formed by any known and suitable hardware or software, or by a combination of hardware and software. For example, the processor 51 may be formed by dedicated hardware such as a processing circuit, or by a programmable processing unit such as a central processing unit ( Central Processing Unit ) which executes a program stored in a memory of it.

[0094] The storage unit 52 may be formed by any suitable means capable of storing the program(s) and data in a computer-readable manner. Examples of the storage unit 52 include non-transitory computer-readable storage media such as semiconductor memory devices, and magnetic, optical, or magneto-optical recording media loaded into a read-write unit.

[0095] At least one network interface 53 provides a connection between the resource hosting server 14, the resolver 11, the terminal 10 and the authoritative server 12.

Claims

1. Method for resolving at least one naming identifier, said method being implemented by a server hosting resources (14) able to be accessed by at least one terminal (10), and comprising the following steps: - receiving (E6) a resources request (DR) sent by the terminal (10), - in response to the resources request (DR), transmitting (E7), to the terminal, the requested resources and a message comprising at least one parameter, referred to as delegation parameter, relating to authorization for said server hosting resources (14) to execute a function for resolving at least one naming identifier, said delegation parameter having been generated by an authoritative server associated with a naming identifier and being specific to each server hosting resources to which a function for resolving a naming identifier is delegated, - receiving (E11) a request to resolve at least one naming identifier, transmitted by said terminal (10), when the authenticity of said delegation parameter is verified by the terminal; - transmitting (E12), to the terminal (10), at least one network address of a server (13, 14) associated with the naming identifier to be resolved.

2. Method for resolving at least one naming identifier according to Claim 1, wherein the delegation parameter is a digital fingerprint of the naming identifier associated with said server hosting resources (14), signed by a cryptographic key associated with an authoritative server (12) associated with at least one naming identifier.

3. Method for resolving at least one naming identifier according to Claim 1, comprising, prior to the step (E7) of transmitting the delegation parameter, a step (E5, E2) of receiving a message comprising the delegation parameter.

4. Method for resolving at least one naming identifier according to Claim 3, wherein the received message is sent by said authoritative server (12) associated with at least one naming identifier.

5. Method for resolving at least one naming identifier according to Claim 3, wherein the received message is sent by a naming identifier resolver (11).

6. Method for requesting resolution of at least one naming identifier, said method being implemented by a terminal (10) and comprising the following steps: - sending (E6) a resources request (DR) to a server hosting resources (14) able to be accessed by the terminal (10), - receiving (E7) the requested resources and a message, sent by the server hosting resources (14), comprising at least one parameter, referred to as delegation parameter, relating to authorization for said server hosting resources (14) to execute a function for resolving at least one naming identifier, said delegation parameter having been generated by an authoritative server associated with a naming identifier and being specific to each server hosting resources to which a function for resolving a naming identifier is delegated, - verifying (E8, E9, E10) the authenticity of said delegation parameter, - when the authenticity of said delegation parameter is verified, transmitting (E11) a request to resolve at least one naming identifier to the server hosting resources (14), - transmitting (E15) a resource request (DS) to a server (13) associated with the naming identifier to be resolved and for which a network address is provided by the server hosting resources (14) in response to the request to resolve at least one naming identifier.

7. Method for requesting resolution of at least one naming identifier according to Claim 6, wherein verifying the authenticity of the delegation parameter comprises: - sending (E8) a request for information relating to said server hosting resources (14) to a naming identifier resolver (11), - receiving (E9) a message comprising a cryptographic key associated with an authoritative server (12) associated with a naming identifier and the delegation parameter, - verifying (E10) the delegation parameter transmitted by the server hosting resources (14) by way of the cryptographic key and the delegation parameter transmitted by the naming identifier resolver (11).

8. Method for requesting resolution of at least one naming identifier according to Claim 7, wherein the delegation parameter is a digital fingerprint of the naming identifier associated with said server hosting resources (14), signed by the cryptographic key associated with an authoritative server (12) associated with a naming identifier.

9. Server hosting resources (14) able to be accessed by at least one terminal (10), said server hosting data (10) being authorized to resolve at least one naming identifier, and comprising means for: - receiving a resources request (DR) sent by the terminal (10), - in response to the resources request (DR), transmitting, to the terminal (10), the requested resources and a message comprising at least one parameter, referred to as delegation parameter, relating to authorization for said server hosting resources (14) to execute a function for resolving at least one naming identifier, said delegation parameter having been generated by an authoritative server associated with a naming identifier and being specific to each server hosting resources to which a function for resolving a naming identifier is delegated, - receiving (E11) a request to resolve at least one naming identifier, transmitted by said terminal (10), when the authenticity of said delegation parameter is verified by the terminal; - transmitting, to the terminal (10), at least one network address of a server (13, 14) associated with the naming identifier to be resolved.

10. Terminal (10) requesting resolution of at least one naming identifier, comprising means for: - sending a resource request (DR) to a server hosting resources (14) able to be accessed by the terminal (10), - receiving the requested resources and a message, sent by the server hosting resources (14), comprising at least one parameter, referred to as delegation parameter, relating to authorization for said server hosting resources (14) to execute a function for resolving at least one naming identifier, said delegation parameter having been generated by an authoritative server associated with a naming identifier and being specific to each server hosting resources to which a function for resolving a naming identifier is delegated, - verifying the authenticity of said delegation parameter, - when the authenticity of said delegation parameter is verified, transmitting a request to resolve at least one naming identifier to the server hosting resources (14), - transmitting a resource request (DS) to a server (13) associated with the naming identifier to be resolved and for which a network address is provided by the server hosting resources (14) in response to the request to resolve at least one naming identifier.

11. Computer program product comprising program code instructions for implementing a method according to Claim 1 when it is executed by a processor.

12. Computer program product comprising program code instructions for implementing a method according to Claim 6 when it is executed by a processor.