Methods for handling requests between different resource record types and systems thereof

• US 9,106,699 B2
• Filed: 11/04/2010
• Issued: 08/11/2015
• Est. Priority Date: 11/04/2010
• Status: Expired due to Fees

• Current Assignee: F5 Networks, Inc. (F5 Incorporated)
• Original Assignee: F5 Networks, Inc. (F5 Incorporated)
• Inventors: Thornewell, Peter M., Baker, Christopher R.
• Primary Examiner(s): Williams, Jeffery
• Assistant Examiner(s): Harris, Christopher C
• Application Number:
  US12/939,377
• Publication Number:
  US 20120117379A1
• Time in Patent Office: 1,741 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 61/2514 between local and global IP addresses
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 69/167 Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6 translation of Internet protocol [IP] addresses H04L61/2503

Abstract

A method, computer readable medium, and device for handling requests between different resource record types includes receiving at a traffic management device a first resource record type from one or more server devices in response to a request from a client device. The traffic management device validates the first resource record type, and creates a second resource record type corresponding to the first resource record type after the validating. Signing the second resource record type at the traffic management device is carried out for servicing the request from the client device.

Claims

1. A method for handling requests between different resource record types, comprising:

receiving by a traffic management device interposed between a client device and one or more server devices, a first resource record type from the one or more server devices in response to a request from the client device, wherein the first resource record type includes a resource record signature provided by the one or more server devices;

validating by the traffic management device the first resource record type;

creating by the traffic management device a second resource record type corresponding to the first resource record type after the validating; and

creating by the traffic management device a new resource record signature at the traffic management device and attaching the new resource record signature to the second resource record type for servicing the request from the client device.

2. The method as set forth in claim 1, wherein the receiving comprises receiving a signature associated with the first resource record type, and wherein the signature is used for the validating.

4. The method as set forth in claim 1, wherein the first resource record type is a 32 bit Internet Protocol version 4 (IPv4) A resource record type and the second resource record type is a 128 bit Internet Protocol version 6 (IPv6) AAAA resource record type.

5. The method as set forth in claim 4, wherein the request from the client device is an IPv6 request.

6. The method as set forth in claim 5 further comprising:

determining by the traffic management device whether when the one or more server devices can directly provide a signed IPv6 resource record type in response to the IPv6 request, wherein the receiving, the validating, the creating, and the signing are performed only when the one or more server device cannot provide an IPv6 resource record type in response to the IPv6 request from the client device.

7. The method as set forth in claim 1, wherein a signature used for validating the first resource record type is discarded after the validating, and wherein the signing comprises attaching a new signature to the second resource record type prior to forwarding the signed second resource record type to the client device.

3. The method as set forth in 1, wherein the validating is performed using public key cryptography.

8. A non-transitory computer readable medium, having stored thereon instructions for handling requests between different resource record types comprising machine executable code which when executed by at least one processor, causes the processor to perform steps comprising:

receiving, by a traffic management device, a first resource record type from the one or more server devices in response to a request from the client device, wherein the first resource record type includes a resource record signature provided by the one or more server devices;

validating, by the traffic management device, the first resource record type;

creating, by the traffic management device, a second resource record type corresponding to the first resource record type after the validating; and

creating, by the traffic management device, a new resource record signature and attaching the new resource record signature to the second resource record type for servicing the request from the client device.

9. The medium as set forth in claim 8, wherein the receiving comprises receiving a signature associated with the first resource record type, and wherein the signature is used for the validating.

11. The medium as set forth in claim 8, wherein the first resource record type is a 32 bit Internet Protocol version 4 (IPv4) A resource record type and the second resource record type is a 128 bit Internet Protocol version 6 (IPv6) AAAA resource record type.

12. The medium as set forth in claim 11, wherein the request from the client device is an IPv6 request.

13. The medium as set forth in claim 12, wherein the machine executable code which when executed by the at least one processor, causes the processor to perform steps further comprising:

determining whether when the one or more server devices can directly provide a signed IPv6 resource record type in response to the IPv6 request, wherein the receiving, the validating, the creating, and the signing are performed only when the one or more server device cannot provide an IPv6 resource record type in response to the IPv6 request from the client device.

14. The medium as set forth in claim 8, wherein a signature used for validating the first resource record type is discarded after the validating, and wherein the signing comprises attaching a new signature to the second resource record type prior to forwarding the signed second resource record type to the client device.

10. The medium as set forth in 8, wherein the validating is performed using public key cryptography.

15. A traffic management device interposed between one or more server devices and a client device, the traffic management device comprising:

one or more processors;

a memory coupled to the one or more processors by a bus; and

a network interface controller coupled to the one or more processors and the memory and configured to be capable of receiving and forwarding data packets from a network that relate to a plurality of applications, at least one of the one or more processors configured to be capable of executing execute programmed instructions stored in the memory or the network interface controller with logic configured to implement, comprising;

receiving a first resource record type from one or more server devices in response to a request from a client device, wherein the first resource record type includes a resource record signature provided by the one or more server devices;

validating the first resource record type;

creating a second resource record type corresponding to the first resource record type after the validating; and

creating a new resource record signature and attaching the new resource record signature to the second resource record type for servicing the request from the client device.

16. The device as set forth in claim 15, wherein the receiving comprises receiving a signature associated with the first resource record type, and wherein the signature is used for the validating.

18. The device as set forth in claim 15, wherein the first resource record type is a 32 bit Internet Protocol version 4 (IPv4) A resource record type and the second resource record type is a 128 bit Internet Protocol version 6 (IPv6) AAAA resource record type.

19. The device as set forth in claim 18, wherein the request from the client device is an IPv6 request.

20. The device as set forth in claim 19, wherein the at least one of the one or more processors is configured to be capable of executing execute programmed instructions stored in the memory or the network interface controller with logic configured to implement further comprising:

determining whether when the one or more server devices can directly provide a signed IPv6 resource record type in response to the IPv6 request, wherein the receiving, the validating, the creating, and the signing are performed only when the one or more server device cannot provide an IPv6 resource record type in response to the IPv6 request from the client device.

21. The device as set forth in claim 15, wherein a signature used for validating the first resource record type is discarded after the validating, and wherein the signing comprises attaching a new signature to the second resource record type prior to forwarding the signed second resource record type to the client device.

17. The device as set forth in 15, wherein the validating is performed using public key cryptography.