EP4078931A1

EP4078931A1 - Method for resolving naming identifiers

Info

Publication number: EP4078931A1
Application number: EP20845197.1A
Authority: EP
Inventors: Emile Stephan; Gaël FROMENTOUX; Frédéric FIEAU
Original assignee: Orange SA
Current assignee: Orange SA
Priority date: 2019-12-20
Filing date: 2020-12-14
Publication date: 2022-10-26
Also published as: CN115211090A; WO2021123593A1; US20230044885A1; FR3105678A1

Abstract

Existing naming identifier resolution solutions give priority to one aspect, performance of the service or protection of privacy, over the other without it being possible to deviate therefrom. This lack of flexibility is detrimental to the user's quality of experience. This also impacts resource management for the various communication equipment involved in the resolution of naming identifiers. The proposed solution makes it possible to give priority to performance or respecting privacy on a case-by-case basis. On the basis of an authorization to share a location of the equipment, the resolver gives priority to transmitting either a network address of a server associated with the naming identifier to be resolved requiring location information of the equipment, giving priority to performance, or a network address of a server associated with the naming identifier to be resolved not requiring location information of the equipment, giving priority to respecting privacy.

Description

DESCRIPTION

TITLE: Method for resolving naming identifiers

Field of the invention

The field of the invention is that of the resolution of naming identifiers such as domain names. More specifically, the invention relates to the selection of servers associated with naming identifiers to be resolved as a function of constraints relating to the protection of privacy expressed by a user of a device requiring the resolution of a naming identifier.

Prior art and its drawbacks

In the domain of naming identifier resolution, three scenarios stand out. Such naming identifiers are, for example, domain names.

The [Fig. IA] represents a first scenario for resolving naming identifiers. A device 10 sends a request for resolution of FQDN naming identifiers (in English fully qualified domain name) to a resolver of naming identifiers 11 managed by an Internet service provider ISP (in English Internet Service Provider) to from which a user of the equipment 10 has subscribed to a service offer. The resolver 11 regularly exchanges messages with at least one authoritative server 12 associated with a naming identifier. The authoritative server 12 determines from a network address of the identifier of a sub-network in which the equipment 10 is located or from a network address of the resolver 11 the servers 13 most suitable to serve the resource in a zone of the network managed by the resolver 11. A network address is for example an IP (Internet Protocol) address of the IPv4 or IPv6 type. The resolver 11 thus obtains from the authoritative server 12 IP addresses associated with servers 13 associated with a naming identifier to be resolved, these servers 13 storing data relating to the implementation of a service required by the equipment 10 such as data relating to a web page or data relating to downloadable content, etc.

Once in possession of the IP (Internet Protocol) addresses associated with the servers 13, the resolver 11 transmits at least one of the IP addresses associated with the servers 13 to the device 10. The device 10 then establishes a connection with the device. corresponding server 13 and can access data relating to the implementation of the required service. In this first scenario, the servers 13 associated with a naming identifier to be resolved are either known to the authoritative server 12 as being topologically close to the equipment 10 as described for example on the Wikipedia page referenced https://en.wikipedia.org / wiki / Geolocation software), or known to the authoritative server 12 as being managed by the internet service provider ISP from which a user of the equipment 10 has subscribed to a service offer, thus favoring in particular the performance of the service.

The [Fig. IB] represents a second scenario for resolving naming identifiers, the elements common to FIG. IA are numbered identically. The equipment 10 sends, in an encrypted connection, a request for resolution of naming identifiers ERQDN intended for a resolver of public naming identifiers 14 managed by a third company. On receipt of the request for resolution of encrypted naming identifiers EFQDN (External FQDN), the public resolver 14 sends a message comprising an identifier of a sub-network in which the equipment 10 is located to the associated authoritative server 12 with a naming identifier. The public resolver 14 thus obtains from the authoritative server 12 IP (Internet Protocol) addresses 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 equipment 10 such as data relating to a web page or data relating to downloadable content, etc. Once in possession of the IP (Internet Protocol) addresses associated with the servers 13, the public resolver 14 transmits at least one of the IP addresses associated with the servers 13 to the equipment 10. The equipment 10 then establishes a connection with the corresponding server 13 and can access the data relating to the implementation of the required service. In this second scenario, the authoritative server 12 having knowledge of the location of the device 10, it provides the device 10 with IP addresses relating to servers 13 associated with a naming identifier to be resolved which are either topologically close or managed by the Internet service provider ISP from which a user of the equipment 10 has subscribed to a service offer, also favoring the performance of the service.

The [Fig. IC] represents a third scenario of resolution of naming identifiers, the elements common to figure IA and to figure IB are numbered identically. The device 10 sends an EFQDN encrypted naming identifier resolution request to a public naming identifier resolver 14 managed by a third-party company. On receipt of the request for resolution of EFQDN encrypted naming identifiers, the public resolver 14 sends a message to the authoritative server 12 associated with a naming identifier. The public resolver 14 then obtains from the authoritative server 12 IP (Internet Protocol) addresses associated with servers 15 associated with the naming identifier to be resolved, these servers 15 storing data relating to the implementation of a service. required by the equipment10 such as data relating to a web page or data relating to downloadable content, etc. Such servers 15 are located in a separate third-party network which is not managed by the Internet service provider ISP with which a user of the equipment 10 has subscribed to a service offer.

Once in possession of the IP (Internet Protocol) addresses associated with the servers 15, the public resolver 14 transmits at least one of the IP addresses associated with the servers 15 to the equipment 10. The equipment 10 then establishes a connection with the corresponding server 15 and can access the data relating to the implementation of the required service. In this third scenario, respect for the privacy of the user of the equipment 10 is privileged since the location of the equipment is never shared.

Each of the three previous scenarios favors one aspect, performance of the service or protection of privacy, over the other without it being possible to derogate from it. Such lack of flexibility is detrimental to the quality of experience of the user of the equipment. This also impacts the management of the resources of the various communication equipment involved in the resolution of naming identifiers which may not be used optimally. In addition, this impacts the load of inter-domain links.

There is therefore a need for a naming identifier resolution technique that does not have all or some of the aforementioned drawbacks.

Disclosure of the invention

The invention meets this need by providing a method for resolving at least one naming identifier, said method being implemented by a naming identifier resolver and comprising the following steps:

reception of at least one network address of a first server associated with a naming identifier, the first server requesting a parameter relating to a device requiring resolution of the naming identifier,

transmission, to the equipment requiring the resolution of said naming identifier, the network address associated with the first server as a function of authorization information for sharing said parameter representative of said equipment.

In a variant of the method for resolving at least one naming identifier, the latter further comprises:

- a step of receiving at least one network address from a second server associated with said naming identifier, the second server not requiring any parameter relating to said equipment,

transmission, to the equipment requiring the resolution of said naming identifier, of the IP address associated with the second server as a function of authorization information for sharing said parameter representative of said equipment.

Such a solution makes it possible to favor the performance or the respect for the private life of a user of the equipment having requested the resolution of a naming identifier on a case-by-case basis.

Indeed, depending on a value of the authorization information for sharing the location parameter of the equipment, the resolver transmits either a network address of a server associated with the naming identifier to be resolved requiring information. location of the equipment, thus favoring performance, ie a network address of a server associated with the naming identifier to be resolved that does not require information on the location of the equipment, thus favoring respect for privacy. The resolver can also transmit the IP addresses of the two servers associated with the naming identifier to be resolved to the user equipment.

Thus, a user of a device can choose, when browsing the Internet, to favor respect for his private life or the performance of the service consulted.

According to one embodiment of the method for resolving at least one naming identifier, when the resolver has the authorization information for sharing said location parameter of said device, the resolver transmits said at least one network address of the device. one of the two servers at the equipment requesting the resolution of said naming identifier.

In a first case, the sharing authorization information of the location parameter of the equipment is a sharing authorization. In this first case, knowing that the user of the equipment gives his consent to share the location of the equipment, the resolver transmits the network address of a server associated with the naming identifier to be resolved requiring information from location of the equipment. Such a scenario favors performance. Indeed, the server thus selected is most often located in the same subnet as the equipment, which offers short response or transfer times. Such a configuration is particularly advantageous when the service consulted is for example a continuous or streaming content service in English.

In a second case, the sharing authorization information of the location parameter of the equipment is a sharing prohibition. In this second case, knowing that the user of the equipment does not agree to share the location of the equipment, the resolver transmits the network address of a server associated with the naming identifier to be resolved, requiring no no equipment location information. Such a scenario favors respect for private life. Indeed, the server thus selected is most often located in a remote network.

According to another embodiment of the method for resolving at least one naming identifier, when the resolver does not have the authorization information for sharing said location parameter of said device, the resolver transmits said at least one network address of the first server and said at least one network address of the second server to the equipment requiring the resolution of said naming identifier.

For example, in such an embodiment, the user of the equipment has not specified whether or not he wishes to share the location of the equipment. Thus, in the absence of information, the resolver transmits both the network address of a server associated with the naming identifier to be resolved requiring equipment location information and the network address of a server associated with the naming identifier to be resolved not requiring any item of equipment location information. The resolver thus delegates the selection of the server with which to establish communication to the equipment. According to another embodiment of the method for resolving at least one naming identifier, the latter comprises a step of receiving a message comprising the authorization information for sharing said device location parameter, said device. message being sent by the equipment.

The device thus transmits information for sharing the location parameter of the device explicitly to the resolver.

According to a particular implementation of the method for resolving at least one naming identifier, the message comprising the authorization information for sharing said device location parameter is the request for resolution of the naming identifier sent by the device. 'equipment.

In this implementation, the item of equipment location parameter sharing information being included in the naming identifier resolution request, it is only valid for this naming identifier resolution request.

According to another particular implementation of the method for resolving at least one naming identifier, the message comprising the authorization information for sharing said device location parameter is a request message for the establishment of a session. communication between the device and the naming identifier resolver sent by the device.

In this implementation, the information for sharing the location parameter of the device being included in the message for establishing a communication session between the device and the resolver, the information for sharing the location parameter of the device being included in the message for establishing a communication session between the device and the resolver. The equipment is applied to all the naming identifier resolution requests sent by the equipment during the communication session.

In one embodiment of the method for resolving at least one naming identifier, the latter comprises, prior to the reception step, a step of transmitting at least one message requiring the transmission of at least one network address a first server and at least one network address of a second server both associated with the same naming identifier, the first server requesting a location parameter of a device requiring resolution of the naming identifier, and the second server requiring no location parameter of said equipment.

When the IP addresses of the two servers associated with the naming identifier to be resolved are not stored in a cash memory of the resolver, the latter transmits a request to obtain this information. This request can be, for example, transmitted to an authoritative server associated with the naming identifier to be resolved.

The invention also relates to a method for requesting the resolution of at least one naming identifier, said method being implemented by an item of equipment and comprising at least:

a step of transmitting a message comprising authorization information for sharing a location parameter of the equipment to a naming identifier resolver.

According to an alternative embodiment of the method for requesting resolution of at least one naming identifier, the message comprising the authorization information for sharing said device location parameter is a request for resolution of the naming identifier.

According to another variant embodiment of the method for requesting resolution of at least one naming identifier, the message comprising the sharing authorization information of said device location parameter is a request message for establishment of a communication session between the device and the naming identifier resolver. Another object of the invention is a method of communication between an authoritative server and a naming identifier resolver, said method being implemented by the authoritative server and comprising at least:

a step of transmitting at least one network address of a first server and at least one network address of a second server both associated with the same naming identifier, the first server requiring a location parameter of a device requiring resolution of the naming identifier, and the second server requiring no location parameter of said device.

The invention also relates to a naming identifier resolver comprising means for:

- receive at least one network address of a first server associated with a naming identifier to be resolved, the first server requesting a parameter relating to a device requiring resolution of the naming identifier,

transmitting, to the equipment requiring the resolution of said naming identifier, the network address associated with the first server as a function of authorization information for sharing said parameter relating to said equipment.

Another object of the invention is a device requiring a resolution of at least one naming identifier, said device comprising means for:

- transmit a message comprising authorization information for sharing a device location parameter to a naming identifier resolver.

The subject of the invention is also an authoritative server capable of communicating with at least one naming identifier resolver, said authoritative server comprising means for:

- transmit at least one network address of a first server and at least one network address of a second server both associated with the same naming identifier to be resolved, the first server requesting a location parameter of a device requiring resolution of the naming identifier, and the second server requiring no location parameter of said equipment.

Finally, the invention finally relates to computer program products comprising program code instructions for implementing the methods as described above, when they are executed by a processor.

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

Such a recording medium can be any entity or device capable of storing the programs. For example, the medium may comprise a storage means, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or else a magnetic recording means, for example a USB key or a hard disk.

On the other hand, such a recording medium can be a transmissible medium such as an electrical or optical signal, which can be conveyed via an electrical or optical cable, by radio or by other means, so that the programs computer it contains can be executed remotely. The programs according to the invention can in particular be downloaded over a network, for example the Internet.

Alternatively, the recording medium can 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 aforementioned methods of the invention.

List of Figures Other aims, characteristics and advantages of the invention will emerge more clearly on reading the following description, given by way of simple illustrative example, and not limiting, in relation to the figures, among which:

[fig. IA]: this figure represents a first scenario for resolving naming identifiers,

[fig. IB]: this figure represents a second scenario for resolving naming identifiers,

[fig. IC]: this figure represents a third scenario for resolving naming identifiers,

[fig. 2]: this figure represents a diagram of exchanges between different communication equipments involved in a first mode of implementation of the methods of resolution of at least one naming identifier, of request for resolution of at least one naming identifier and communication between an authoritative server and a naming identifier resolver,

[fig. 3]: this figure represents a diagram of exchanges between different communication equipments involved in a second mode of implementation of the methods of resolution of at least one naming identifier, of request for resolution of at least one naming identifier and communication between an authoritative server and a naming identifier resolver,

[fig. 4]: this figure represents a diagram of exchanges between different communication equipments involved in a third mode of implementation of the methods of resolution of at least one naming identifier, of request for resolution of at least one naming identifier and communication between an authoritative server and a naming identifier resolver,

[fig. 5]: this figure shows equipment 10 according to one embodiment of the invention. Such a device 10 is able to implement the various embodiments of the method for requesting the resolution of a naming identifier, s

[fig. 6]: this figure represents a resolver 11 capable of implementing the various embodiments of the method for resolving naming identifiers,

[fig. 7]: this figure represents an authoritative server 12 able to implement the various embodiments of the communication method.

Detailed description of embodiments of the invention

The general principle of the invention is based on the one hand on the provision, to a naming identifier resolver, of authorization information for sharing a parameter relating to a device requiring a resolution of '' a naming identifier and on the other hand on the transmission, to the resolver of naming identifiers by authoritative servers, of IP addresses associated with servers associated with the naming identifier to be resolved, some servers requiring a device location parameter requiring a naming identifier resolution, and other servers not requiring any device location parameter.

We present, in relation with [fig. 2] a diagram of exchanges between different communication equipments involved in a first mode of implementation of the methods of resolution of at least one naming identifier, of request for resolution of at least one naming identifier and of communication between a authoritative server and a naming identifier resolver. During a step E1, an item of equipment 10 sends a request message for the establishment of a communication session HS to a naming identifier resolver 11. Such a message for establishment of a communication session. communication is for example a message of the DoH HTTPS handshake type (DoH meaning DNS over HTTPS) specified in the document RFC8484 (Request for Comment) published by the IETF (Internet Engineering Task Force).

Once the communication session has been established between the device 10 and the resolver 11, the device 10 sends, in a step E2, a request for resolution of the FQDN naming identifier to the resolver 11 for the log naming identifier .Fr. This FQDN naming identifier resolution request is for example a message of the DoH query type also specified in the IETF document RFC8484.

In a first embodiment, a field, HTTP DNS_RELAY_CONSENT, of the message for establishing a DoH HTTPS handshake communication session is used to transport authorization information for sharing a parameter relating to the equipment 10. A such a parameter relating to the equipment is for example a location parameter of the equipment 10. In another embodiment, such a parameter relating to the equipment 10 is for example information relating to the nature of the equipment 10 , such as user terminal, resolver, etc. The parameter relating to the equipment 10 can also be information on the computing power of the equipment 10. In the remainder of the document, the parameter relating to the equipment 10 is a location parameter.

Such information is either a sharing authorization in which case the HTTP DNS_RELAY_CONSENT field includes TRUE information, or a sharing refusal in which case the HTTP DNS_RELAY_CONSENT field includes FALSE information.

In this first embodiment, the sharing information of the location parameter of the device 10 being included in the message for establishing a communication session between the device 10 and the resolver 11, the sharing information of the device location parameter is applied to all the naming identifier resolution requests sent by the device 10 during the communication session.

In a second embodiment, the field, HTTP DNS_RELAY_CONSENT, of RQDN naming identifier resolution request is used to transport the authorization information for sharing a location parameter of the device 10. Such information is either a sharing authorization in which case the HTTP DNS_RELAY_CONSENT field includes TRUE information, or a sharing refusal in which case the HTTP DNS_RELAY_CONSENT field includes FALSE information.

In this second embodiment, the information for sharing the location parameter of the device 10 being included in the request for resolution of the RQDN naming identifier, the information for sharing the location parameter of the device is not valid. that for this request for resolution of journal.fr naming identifier.

On receipt of the RQDN naming identifier resolution request for the journal.fr naming identifier, the resolver 11 issues, in a step E3, a first RQ1 request for resolution of a naming identifier associated with the identifier journal.fr naming. The request RQ1 is sent to one or more servers 20 constituting a network of DNS nodes. The servers 20 store, in the cache, the IP addresses of servers associated with the same naming identifier, some of these servers requiring a location parameter for the equipment 10, and other servers not requiring any location parameter for the device. equipment 10.

The servers 20 receive, during a step E0, the IP addresses of servers associated with the same naming identifier, some of these servers requiring a location parameter of the equipment 10, and other servers not requiring any parameters. location of the equipment 10. This information is transmitted by authoritative servers 12 associated with naming identifiers. Thus, during step E0, the authoritative server 12 associated with the journal.fr naming identifier transmits a first Record 1 message such as, for example, a DNS record ESNI type message comprising an extension called "geo" comprising a parameter relating to a location of an item of equipment 10, intended for a server 20. An example of such a Record 1 message is given below:

DNS record ESNI: {journal.fr, ESNIKeys: {...}, extension: {geo: 10.1.1.0/24} The 'geo' extension gives the list of content servers which are regionalised: in the example it This is the IP address mask: 10.1.1.0/24.

The authoritative server 12 associated with the journal.fr naming identifier also transmits a second Record 2 message such as, for example, a DNS record type message comprising a list of IP addresses associated with servers 13, 15 associated with the 'journal.fr naming identifier, intended for a server 20. An example of such a Record 2 message is given below:

DNS record journal.fr IN A: 10.10.1.1, 10.1.1.10, 10.1.1.11

The server 20 applies the 'geo' extension to the content of the Record 2 message in order to identify on the one hand regionalized servers {10.10.1.1, 10.1.1.10} and on the other hand a global server {10.1.1.11}.

Step E0 is implemented on receipt of a request sent by a server 20 when the latter does not have in its cache memory the information necessary for the resolution of a naming identifier. In the context of the invention, step EO can be implemented throughout the execution of the methods described.

The query RQ1 sent by the resolver 11 is for example a message of the DNS query ESNI (Domain Name System query Encrypted Server Name Indication) type. On receipt of this request RQ1, the server 20 sends an IN ESNI message to the resolver 11 in a step E4.

An example of such an IN ESNI message is: IN ESNI {... {geo: 10.1.1.0/24}}. Thus, at the end of step E4, the resolver 11 has an IP address mask: 10.1.1.0/24.

In a step E5, a second request RQ2 for the resolution of a naming identifier associated with the journal.fr naming identifier is sent to one or more servers 20 constituting a network of DNS nodes by the resolver 11.

The request RQ2 sent by the resolver 11 is for example a message of the DNS query journal.fr type. On receipt of this request RQ2, the server 20 sends a message IN A to the resolver 11 in a step E6.

An example of such an IN A message is as follows: IN A 10.10.1.1, 10.1.1.10, 10.1.1.11. Thus, at the end of step E6, the resolver 11 has a list of IP addresses associated with servers associated with the journal.fr naming identifier.

In a step E7, the resolver 11 determines, as a function of the authorization information for sharing a location parameter of the equipment 10 received during step E1 or during step E2 which address network it must transmit to the device 10 in response to the journal.fr naming identifier resolution request.

If the sharing authorization information of a location parameter of the equipment10 is a refusal to share, the resolver 11 applies the mask 10.1.1.0/24 received during step E4 and identifies the server whose network address 10.10.1.1 does not belong to the mask. This means that this server is located in a remote network and that it is not necessary to have information on the location of the equipment 10 in order to communicate with this server.

In a step E8, the equipment 10 establishes a communication with the server whose network address is 10.10.1.1.

If the sharing authorization information of a location parameter of the equipment 10 is a sharing authorization, the resolver 11 applies the mask 10.1.1.0/24 received during of step E4 and identifies the servers whose IP addresses 10.1.1.10, and 10.1.1.11 belong to the mask. This means that these servers are close to the equipment 10 since each IP address mask transmitted by an authoritative server corresponds to a particular subnet.

In a step E9, the equipment 10 establishes a communication session with one of the servers whose IP addresses are 10.1.1.10, 10.1.1.11.

We present, in relation with [fig. 3] a diagram of exchanges between different communication equipments involved in a second mode of implementation of the methods of resolution of at least one naming identifier, of request for resolution of at least one naming identifier and of communication between a authoritative server and a naming identifier resolver.

In a step F1, the equipment 10 sends a first request RQ3 to the resolver 11 for the journal.fr naming identifier. The request RQ3 sent by the equipment 10 is for example a message of the DNS type queryjournal.fr.

In a first embodiment, on receipt of the request RQ3, the resolver 11 sends, in a step F2, a second request RQ4 for the resolution of a naming identifier associated with the journal.fr naming identifier. The request RQ41 is sent to one or more servers 20 constituting a network of DNS nodes. The servers 20 store, in the cache, the IP addresses of servers associated with the same naming identifier, some of these servers requiring a location parameter for the equipment 10, and other servers not requiring any location parameter for the device. equipment 10.

The servers 20 receive, during a step E0, the IP addresses of servers associated with the same naming identifier, some of these servers requiring a location parameter of the equipment 10, and other servers not requiring any parameters. location of the equipment 10. This information is transmitted by authoritative servers 12 associated with naming identifiers.

Thus, during step EO, the authoritative server 12 associated with the journal.fr naming identifier transmits a first Record 1 message such as, for example, a DNS record ESNI type message comprising an extension called “anycast”. comprising a parameter relating to a location of the equipment whose network addresses are 10.1.1.10 and 10.1.1.11, intended for a server 20. An example of such a Record 1 message is given below:

DNS record ESNI: {journal.fr, ESNIKeys: {...}, extension: {anycast: 10.1.1.0/24}

Here, the parameter relating to a location of a device 10 is an IP address mask: 10.1.1.0/24.

"Anycast" is an addressing and routing technique for redirecting data to the "closest" or "most efficient" server among a set of servers using a single address, depending on the routing policy chosen.

The "anycast" routing technique is usually implemented using the BGP (Boarder Gateway Protocol) protocol which simultaneously announces the same range of IP addresses accessible from several places on a communication network. In this way, the data packets are routed to the "nearest" network node announcing the destination route.

The “anycast” routing technique is described in RFC 4786 published by the IETF.

For this reason, the “anycast” routing technique is typically used to provide high availability and load balancing for offline mode services. RFC 3258 describes how the “anycast” routing technique is used to provide a naming identifier resolution service. The authoritative server 12 associated with the journal.fr naming identifier also transmits a second Record 2 message such as, for example, a DNS record type message comprising a list of IP addresses associated with servers 13, 15 associated with the 'journal.fr naming identifier, intended for a server 20. An example of such a Record 2 message is given below:

DNS record journal.fr IN A: 10.10.1.1, 10.1.1.10, 10.1.1.11

The request RQ3 sent by the resolver 11 is for example a message of the DNS query journal.fr type.

On receipt of this request RQ3, the server 20 sends, in a step F3, a message IN A to the resolver 11.

An example of such an IN A message is as follows: IN A 10.10.1.1, 10.1.1.10, 10.1.1.11.

In a step F4, a third request RQ5 for the resolution of a naming identifier associated with the journal.fr naming identifier is sent to one or more servers 20 constituting a network of DNS nodes by the resolver 11.

Thus, at the end of step F4, the resolver 11 has an IP address mask: 10.1.1.0/24

The RQ5 query sent by the resolver 11 is for example a message of the DNS query ESNI (Domain Name System query Encrypted Server Name Indication) type. On receipt of this RQ5 request, the server 20 sends an IN ESNI message to the resolver 11 in a step F5.

An example of such an IN ESNI message is: IN ESNI {... {anycast: 10.1.1.0/24}}. Thus, at the end of step F5, the resolver 11 has an IP address mask: 10.1.1.0/24.

In a second particular embodiment, steps F4 and F5 are not implemented. Following step F3, the device 10 sends a fourth request RQ6 to the resolver 11 in a step F6. The RQ6 request sent by the equipment 10 is for example a message of the DNS query ESNI (Domain Name System query Encrypted Server Name Indication) type associated with the journal.fr naming identifier.

In a step F7, the request RQ5 for resolving a naming identifier associated with the journal.fr naming identifier is sent by the resolver 11 to one or more servers 20 constituting a network of DNS nodes.

The RQ5 query sent by the resolver 11 is for example a message of the DNS query ESNI (Domain Name System query Encrypted Server Name Indication) type. On receipt of this RQ5 request, the server 20 sends an IN ESNI message to the resolver 11 in a step F8.

An example of such an IN ESNI message is: IN ESNI {... {anycast: 10.1.1.0/24}}. Thus, at the end of step F8, the resolver 11 has an IP address mask: 10.1.1.0/24.

In the first embodiment relating to FIG. 3, during a step F9, the resolver 11 determines, as a function of authorization information for sharing a location parameter of the equipment 10 which address network it must transmit to the device 10 in response to the journal.fr naming identifier resolution request. The resolver 11 is for example configured to select IP addresses of the “anycast” type. Thus, the resolver 11 applies the mask 10.1.1.0/24 received during step F5 and identifies the servers whose network addresses are 10.1.1.10, and 10.1.1.11 belong to the mask. This means that these servers are close in the sense of the authoritative server of the equipment 10 since each IP address mask transmitted by an authoritative server corresponds to a particular subnet.

Then, in a step F10, the resolver 11 transmits a message IN A to the equipment 10. An example of such a message IN A is as follows: IN A 10.1.1.10, 10.1.1.11. In the second embodiment relating to FIG. 3, during a step Fil, the resolver 11 transmits a message IN A to the equipment 10. An example of such a message IN A is as follows: IN A 10.10.1.1, 10.1.1.10, 10.1.1.11 and the following IN ESNI message: IN ESNI {... {anycast: 10.1.1.0/24}}.

The equipment 10 determines, in a step F12, as a function of authorization information for sharing a location parameter of the equipment 10, the server with which to establish a communication session.

We present, in relation with [fig. 4] a diagram of exchanges between different communication equipments involved in a third mode of implementation of the methods of resolution of at least one naming identifier, of request for resolution of at least one naming identifier and of communication between a authoritative server and a naming identifier resolver.

The servers whose IP addresses are 10.1.1.10, 10.1.1.11, and which are regional servers, store, in cache, the IP addresses of servers associated with the same naming identifier, some of these servers requiring a location parameter of equipment 10, and other servers that do not require any location parameters for equipment 10.

The servers whose IP addresses are 10.1.1.10, 10.1.1.11 receive, during a step G0, the IP addresses of servers associated with the same naming identifier, some of these servers requiring a device location parameter 10, and other servers not requiring any location parameters for the equipment 10. This information is transmitted by authoritative servers 12 associated with naming identifiers.

Thus, during step G0, the authoritative server 12 associated with the journal.fr naming identifier transmits a first Record 1 message such as, for example, a DNS record ESNI type message comprising an extension called "geo" comprising a parameter relating to a location of an item of equipment 10, intended for a server 20. An example of such a Record 1 message is given below:

DNS record ESNI: {journal.fr, ESNIKeys: {...}, extension: {geo: 10.1.1.0/24}

The authoritative server 12 associated with the journal.fr naming identifier also transmits a second Record 2 message such as, for example, a DNS record type message comprising a list of IP addresses associated with servers 13, 15 associated with the 'journal.fr naming identifier, intended for a server whose IP address is 10.1.1.10, or 10.1.1.11. An example of such a Record 2 message is given below:

DNS record journal.fr IN A: 10.10.1.1, 10.1.1.10, 10.1.1.11

Step G0 is implemented on receipt of a request sent by a server whose IP address is 10.1.1.10, or 10.1.1.11 when the latter does not have in its cache memory the information necessary for the resolution of d 'a naming identifier. In the context of the invention, step G0 can be implemented throughout the execution of the methods described.

During a step Gl, a device 10 receives an MSG message of DHCP (Dynamic Host Configuration Protocol) RA (Router Advertisement) type sent by a communication device 30 of the Internet service provider IPS to which the user of equipment 10 has subscribed to an offer. Such an MSG message comprises information making it possible to select a server associated with a naming identifier with which the equipment 10 can establish a communication session. An example of an MSG message is as follows:

Hints = {

// domain, scope, resolver

['Orange.com,' local ',' intranet '], ['Orange.fr,' host ',' isp '],

["Journal.fr," subnet ', "any'j,

[".Fr, null," any'j,

}

During a step G2, the equipment 10 sends a request message for the establishment of a communication session HS to the naming identifier resolver 11. Such a message for establishing a communication session is for example a DoH HTTPS handshake type message (DoH meaning DNS over HTTPS) specified in the RFC8484 document published by the IETF.

A field, DoH Hints, of the message for establishing a DoH HTTPS handshake communication session is used to transport selection information from a server associated with a naming identifier to be resolved. Such information is one of the information contained in the MSG message.

An example of an HS message is: DoH Hints = {// domain ... "any'j

Once the communication session has been established between the equipment 10 and the resolver 11, the equipment 10 sends, in a step G3, a request for resolution of the naming identifier FQDN to a public resolver 14 for the identifier. journal.fr naming. This FQDN naming identifier resolution request is for example a message of the DoH query type.

A field, HTTP DNS_RELAY_VIEW, of the RQDN naming identifier resolution request is used to carry the server selection information associated with the naming identifier to be resolved.

An example of such a field is: HTTP DNS_RELAY_VIEW = 'subnet'.

In this second embodiment, the information for sharing the location parameter of the device 10 being included in the request for resolution of the RQDN naming identifier, the information for sharing the location parameter of the device is not valid. only for this request for resolution of the journal.fr naming identifier.

In a step G4, the public resolver 14 transmits a message IN A comprising the IP addresses of servers associated with the naming identifier to be resolved and being located in the same sub-network as the device 10, to the device 10. An example of such an IN A message is as follows: IN A 10.1.1.10, 10.1.1.11.

In a step G5, the equipment 10 establishes a communication session with one of the servers whose IP addresses are 10.1.1.10, or 10.1.1.11.

During a step G6, the equipment 10 sends in a step E2, a second request for resolution of the naming identifier FQDN2 intended for the resolver 11 for the orange.fr naming identifier. This FQDN2 naming identifier resolution request is for example a message of the DoH query type.

A field, HTTP DNS_RELAY_VIEW, of the FQDN2 naming identifier resolution request is used to carry the server selection information associated with the naming identifier to be resolved.

An example of such a field is: HTTP DNS_RELAY_VIEW = "host".

In a step G7, the resolver 11 sends an RQ6 query of the DNS query orange.fr type to a server whose network address is 10.1.1.10, or 10.1.1.11. The server whose network address is 10.1.1.10, or 10.1.1.11 received during step GO a DNS record orange.fr IN A 192.169.1.1 message sent by a server associated with the orange naming identifier. fr whose network address is 192.169.1.1.

On receipt of this RQ6 request, the server whose IP address is 10.1.1.10, or 10.1.1.11 sends, in a step G8, a message IN A to the resolver 11.

An example of such an IN A message is as follows: IN A 192.169.1.1.

In a step G9, the resolver 11 transmits a message IN A to the equipment 10. An example of such a message IN A is as follows: IN A 192.169.1.1.

The device 10 establishes, in a step G10, a communication session with the server associated with the orange.fr naming identifier whose network address is 192.169.1.1.

The [fig. 5] shows equipment 10 according to one embodiment of the invention. Such a device 10 is able to implement the different embodiments of the method for requesting resolution of a naming identifier according to FIGS. 2-4.

An item of equipment 10 may include at least one hardware processor 501, a storage unit 502, an input device 503, a display device 504, an interface 505, and at least one network interface 506 which are connected to each other across. of a bus 507. Of course, the constituent elements of the equipment 10 can be connected by means of a connection other than a bus.

The processor 501 controls the operations of the equipment 10. The storage unit 502 stores at least one program for implementing the method according to an embodiment of the invention to be executed by the processor 501, and various data, such as parameters used for calculations performed by processor 501, intermediate data from calculations performed by processor 501, and the like. The processor 501 can be formed by any known and suitable hardware or software, or by a combination of hardware and software. For example, the processor 501 can be formed by dedicated hardware such as a processing circuit, or by a programmable processing unit such as a Central Processing Unit which executes a program stored in a memory of this one.

The storage unit 502 may be formed by any suitable means capable of storing the program or programs and data in a computer readable manner. Examples of storage unit 502 include computer readable non-transient storage media such as solid-state memory devices, and magnetic, optical, or magneto-optical recording media loaded in a read and write unit. 'writing.

Input device 503 may be formed by a keyboard, a pointing device such as a mouse for use by a user to enter commands. The display device 504 can also be formed by a display module, such as for example a graphical user interface or GUI (for Graphical User Interface).

Interface 505 provides an interface between equipment 10 and other equipment.

At least one network interface 506 provides a connection between the equipment 10 and the resolver 11.

The [fig. 6] represents a resolver 11 capable of implementing the various embodiments of the method for resolving naming identifiers according to FIGS. 2-4. A resolver 11 can comprise at least one hardware processor 601, a storage unit 602, an interface 603, and at least one network interface 604 which are connected to each other through a bus 605. Of course, the constituent elements of the resolver 11 can be connected by means of a connection other than a bus.

The processor 601 controls the operations of the resolver 11. The storage unit 602 stores at least one program for the implementation of the method according to an embodiment to be executed by the processor 601, and various data, such as parameters used. for calculations performed by the processor 601, intermediate data of calculations performed by the processor 601, etc. The processor 601 can be formed by any known and suitable hardware or software, or by a combination of hardware and software. For example, the processor 601 can be formed by dedicated hardware such as a processing circuit, or by a programmable processing unit such as a Central Processing Unit which executes a program stored in a memory of this one.

The storage unit 602 may be formed by any suitable means capable of storing the program or programs and data in a computer readable manner. Examples of storage unit 602 include computer readable non-transient storage media such as solid-state memory devices, and magnetic, optical, or magneto-optical recording media loaded in a read and write unit. 'writing.

Interface 603 provides an interface between resolver 11 and at least the authoritative server

12.

At least one network interface 604 provides a connection between the resolver 11 and the equipment 10.

The [fig. 7] represents an authoritative server 12 able to implement the various embodiments of the communication method according to FIGS. 2-4.

An authoritative server 12 can comprise at least one hardware processor 701, a storage unit 702, an interface 703, and at least one network interface 704 which are connected to each other through a bus 705. Of course, the constituent elements of the authoritative server 12 can be connected by means of a connection other than a bus.

The processor 601 controls the operations of the authoritative server 12. The storage unit 702 stores at least one program for the implementation of the method according to an embodiment to be executed by the processor 701, and various data, such as parameters. used for calculations performed by processor 701, intermediate data of calculations performed by processor 701, etc. Processor 701 may be formed by any known and suitable hardware or software, or by a combination of hardware and software. For example, the processor 701 can be formed by dedicated hardware such as a processing circuit, or by a programmable processing unit such as a Central Processing Unit which executes a program stored in a memory of this one.

Storage unit 702 may be formed by any suitable means capable of storing program or programs and data in a computer readable manner. Examples of storage unit 702 include computer readable non-transient storage media such as solid-state memory devices, and magnetic, optical, or magneto-optical recording media loaded in a read and write unit. 'writing.

Interface 703 provides an interface between authoritative server 12 and resolver 11.

At least one network interface 704 provides a connection between authoritative server 12 and other servers associated with naming identifiers.

Claims

1. A method of resolving at least one naming identifier, said method being implemented by a naming identifier resolver and comprising the following steps:

reception of at least one network address of a first server associated with a naming identifier, the first server requesting a parameter relating to a device requiring a resolution of G naming identifier,

transmission, to the equipment requiring the resolution of said naming identifier, said at least one network address associated with the first server as a function of a value of authorization information for sharing said parameter representative of said equipment.

2. A method of resolving at least one naming identifier according to claim 1 further comprising:

a step of receiving at least one network address of a second server associated with said naming identifier, the second server not requiring any parameter relating to said equipment,

transmission, to the equipment requiring the resolution of said naming identifier, of said at least one address associated with the second server as a function of the value of the sharing authorization information of said parameter representative of said equipment.

3. A method of resolving at least one naming identifier, according to claim 1, in which the parameter relating to the equipment is a parameter for locating the equipment.

4. A method of resolving at least one naming identifier according to claim 2 wherein, when the value of the sharing authorization information of said parameter relating to said equipment is non-zero, the resolver transmits said at least one address. network from one of the two servers to the equipment requiring the resolution of said naming identifier.

5. A method of resolving at least one naming identifier according to claim 1 wherein, when the value of the sharing authorization information of said parameter relating to said equipment is zero, the resolver transmits said at least one network address of the device. first server and said at least one network address from the second server to the equipment requiring the resolution of said naming identifier.

6. A method of resolving at least one naming identifier according to claim 4, comprising a step of receiving a message comprising the authorization information for sharing said parameter relating to the equipment, said message being sent by the device. 'equipment.

7. A method of resolving at least one naming identifier according to claim 6, in which the message comprising the authorization information for sharing said parameter relating to the equipment is a request for the resolution of the naming identifier sent by. the equipment.

8. A method of resolving at least one naming identifier according to claim 6, in which the message comprising the authorization information for sharing said parameter relating to the equipment is a request message for establishing a session communication between the device and the naming identifier resolver sent by the device.

9. A method of resolving at least one naming identifier according to claim 1 comprising, prior to the receiving step, a step of transmitting at least one message requiring the transmission of at least one network address of a. first server and at least one network address of a second server both associated with the same naming identifier, the first server requiring a parameter relating to a device requiring resolution of the naming identifier, and the second server does not requiring no equipment parameter.

10. Method for requesting resolution of at least one naming identifier, said method being implemented by a device and comprising at least: - a step of transmitting a message comprising authorization information for sharing a parameter relating to the equipment to a naming identifier resolver

a step of receiving at least one network address associated with the first server, said at least one network address being transmitted as a function of a value of the sharing authorization information and taken into account in the resolution of said at least a login.

11. A method of requesting resolution of at least one naming identifier according to claim 7, in which the message comprising the authorization information for sharing said parameter relating to the equipment is a request for resolution of the identifier of the device. naming.

12. A method of requesting resolution of at least one naming identifier according to claim 7, in which the message comprising the sharing authorization information of said parameter relating to the equipment is a request message for establishment of. a communication session between the device and the naming identifier resolver.

13. Naming identifier resolver comprising means for:

transmitting, to the equipment requiring the resolution of said naming identifier, said at least one network address associated with the first server as a function of a value of an authorization information item for sharing said parameter relating to said equipment.

14. Equipment requiring a resolution of at least one naming identifier, said equipment comprising means for:

- transmit a message comprising authorization information for sharing a parameter relating to the equipment to a naming identifier resolver

receiving at least one network address associated with the first server, said at least one network address being transmitted as a function of a value of the sharing authorization information and taken into account in the resolution of said at least one identifier.

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

16. A computer program product comprising program code instructions for implementing a method according to claim 10, when it is executed by a processor.