IP Library Granted Patent US 8,245,032
Granted Patent B2
US 8,245,032 · App. 10/401,919 · Granted Aug 14, 2012

Method to authenticate packet payloads

Assignee: Avaya Inc.
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,245,032
App. No.
10/401,919
Granted
Aug 14, 2012
Kind
B2
Abstract

An architecture for authenticating packets is provided that includes: an input 322 operable to receive a packet, the packet comprising at least one of a transport, session and presentation header portion and a transport agent 312 operable to compute a first message authentication code based on at least some of the contents of the packet and compare the first message authentication code with a second message authentication code in the at least one of a transport, session, and presentation header portion to authenticate the packet.

Claims (93)

1. A method, comprising:

(a) receiving, by a destination node and from a source node, a packet comprising a header that includes a first message authentication code and source port and checksum fields, the header having been altered by a firewall;

(b) computing, by the destination node and over the packet, a second message authentication code; and

(c) applying the following rules:

(c1) when the first and second message authentication codes match, the packet is authenticated successfully; and

(c2) when the first and second message authentication codes do not match, the packet is not authenticated successfully;

wherein each of the first and second message authentication codes is computed by the source and destination nodes, respectively, based on values for the source port and checksum fields that are different from the values for the source port and checksum fields in the packet before and after alteration by the firewall.

2. The method of claim 1 , wherein the first message authentication code is contained in an Open Systems Interconnect transport layer portion of the header.

3. The method of claim 2 , wherein the first message authentication code is contained in an authentication option.

4. The method of claim 3 , wherein the authentication option comprises an option indicator having a value associated with the authentication option, a length having a value associated with the length of the first message authentication code, and the first message authentication code, and wherein the first message authentication code is truncated to a selected number of bits.

5. The method of claim 2 , wherein, in computing the first and second message authentication codes, the values for the source port, destination port, and checksum fields are independent of the corresponding values in the header.

6. The method of claim 1 , wherein the first and second message authentication codes are computed based on values for members of a set of fields, the values being the same as the values for the members of the set of fields contained in the header, both before and after firewall alteration, and wherein the set of fields comprise a plurality of an urgent pointer flag, PSH flag, finished flag, acknowledgment flag, synchronize flag, reset flag, sequence number, acknowledgment number, data offset, window, options, and padding.

7. The method of claim 3 , further comprising, after the receiving step:

(d) in a first mode, discarding the packet when the packet header does not include the authentication option; and

(e) in a second, different mode, discarding the packet when the packet header includes an authentication option, whether valid or invalid, wherein the computing and applying steps occur only in the first mode.

8. The method of claim 7 , further comprising:

(f) negotiating, by the source and destination nodes, protocol parameters over an insecure channel;

(g) receiving a start cipher and/or change cipher spec command;

(h) in response initiating receive authentication using a shared secret, wherein, in receive authentication, the first mode is performed; and

(i) thereafter resetting to a no authentication mode in which the second mode is performed.

9. A computer comprising, in memory, software, wherein, when the software is executed by the computer, the computer performs the steps of claim 1 .

10. A system, comprising:

(a) an input operable to receive, from a source node, a packet comprising a header that includes a first message authentication code and source port and checksum fields, the header having been altered by a firewall;

(b) a transport agent, at a destination node, operable to compute, for the packet, a second message authentication code and apply the following rules:

(b1) when the first and second message authentication codes match, the packet is authenticated successfully; and

(b2) when the first and second message authentication codes do not match, the packet is not authenticated successfully;

wherein each of the first and second message authentication codes is computed by the source and destination nodes, respectively, based on values for the source port and checksum fields that are different from the values for the source port and checksum fields in the packet before and after alteration by the firewall.

11. The system of claim 10 , wherein the first message authentication code is contained in an Open Systems Interconnect transport layer portion of the header.

12. The system of claim 10 , wherein the first message authentication code is contained in an authentication option.

13. The system of claim 12 , wherein the authentication option comprises an option indicator having a value associated with the authentication option, a length having a value associated with the length of the first message authentication code, and the first message authentication code, and wherein the first message authentication code is truncated to a selected number of bits.

14. The system of claim 10 , wherein, in computing the first and second message authentication codes, the values for the source port, destination port, and checksum fields are independent of the corresponding values in the header.

15. The system of claim 10 , wherein the first and second message authentication codes are computed based on values for members of a set of fields, the values being the same as the values for the members of the set of fields contained in the header, both before and after firewall alteration, and wherein the set of fields comprise a plurality of an urgent pointer flag, PSH flag, finished flag, acknowledgment flag, synchronize flag, reset flag, sequence number, acknowledgment number, data offset, window, options, and padding.

16. The system of claim 10 , wherein the transport agent:

in a first mode, discarding the packet when the packet header does not include the authentication option; and

in a second, different mode, discarding the packet when the packet header includes an authentication option, whether valid or invalid, wherein the computing and applying steps occur only in the first mode.

17. A method, comprising:

(a) generating, by a source node, a packet, the packet comprising a header that includes a first message authentication code and source port and checksum fields; and

(b) altering, by a firewall, the packet header;

wherein a destination node authenticates the packet by computing a second message authentication code; and

wherein each of the first and second message authentication codes is computed by the source and destination nodes, respectively, based on values for the source port and checksum fields that are different from the values for the source port and checksum fields in the packet before and after alteration by the firewall.

18. The method of claim 17 , wherein the first message authentication code is contained in an Open Systems Interconnect transport layer portion of the header.

19. The method of claim 17 , wherein the first message authentication code is contained in an authentication option.

20. The method of claim 19 , wherein the authentication option comprises an option indicator having a value associated with the authentication option, a length having a value associated with the length of the first message authentication code, and the first message authentication code, and wherein the first message authentication code is truncated to a selected number of bits.

21. The method of claim 17 , wherein, in computing the first and second message authentication codes, the values for the source port, destination port, and checksum fields are independent of the corresponding values in the header.

22. The method of claim 17 , wherein the first and second message authentication codes are computed based on values for members of a set of fields, the values being the same as the values for the members of the set of fields contained in the header, both before and after firewall alteration, and wherein the set of fields comprise a plurality of an urgent pointer flag, PSH flag, finished flag, acknowledgment flag, synchronize flag, reset flag, sequence number, acknowledgment number, data offset, window, options, and padding.

23. The method of claim 17 , further comprising, after the receiving step:

(c) in a first mode, generating the first message authentication code and locating the first message authentication code in an authentication option in a selected packet header; and

(d) in a second, different mode, not setting the authentication option in the selected packet header.

24. The method of claim 23 , further comprising:

(e) negotiating, by the source and destination nodes, protocol parameters over an insecure channel;

(f) initiating transmit authentication using a shared secret, wherein, in transmit authentication, the first mode is performed; and

(g) thereafter resetting to a no authentication mode in which the second mode is performed.

25. A computer comprising, in memory, software, wherein, when the computer executes the software, the computer performs the steps of claim 17 .

26. A method, comprising:

(a) receiving, by a destination node and from a source node, a packet comprising a header that includes first and second message authentication codes and source port and checksum fields, the header having been altered by a firewall;

(b) computing, by the destination node and over the packet, a third message authentication code; and

(c) applying the following rules:

(c1) when the first and third message authentication codes match, the packet is authenticated successfully; and

(c2) when the first and third message authentication codes do not match, the packet is not authenticated successfully;

wherein the first and third message authentication codes are computed by the source and destination nodes, respectively, and exclude values for the source port and checksum fields.

27. The method of claim 26 , wherein the first message authentication code is contained in an Open Systems Interconnect (“OSI”) transport layer portion of the header and the second message authentication code is contained in an authentication header used between OSI layers 3 and 4 .

28. The method of claim 26 , wherein the first message authentication code is contained in an authentication option.

29. The method of claim 28 , wherein the authentication option comprises an option indicator having a value associated with the authentication option, a length having a value associated with the length of the first message authentication code, and the first message authentication code, and wherein the first message authentication code is truncated to a selected number of bits.

30. The method of claim 26 , wherein, in computing the first and third message authentication codes, the value for the destination port is excluded.

31. The method of claim 26 , wherein the first and third message authentication codes are computed based on values for members of a set of fields, the values being the same as the values for the members of the set of fields contained in the header, both before and after firewall alteration, and wherein the set of fields comprise a plurality of an urgent pointer flag, PSH flag, finished flag, acknowledgment flag, synchronize flag, reset flag, sequence number, acknowledgment number, data offset, window, options, and padding.

32. The method of claim 26 , further comprising, after the receiving step:

(d) in a first mode, discarding the packet when the packet header does not include the authentication option; and

(e) in a second, different mode, discarding the packet when the packet header includes an authentication option, whether valid or invalid, wherein the computing and applying steps occur only in the first mode.

33. The method of claim 32 , further comprising:

(f) negotiating, by the source and destination nodes, protocol parameters over an insecure channel;

(g) receiving a start cipher and/or change cipher spec command;

(h) in response initiating receive authentication using a shared secret, wherein, in receive authentication, the first mode is performed; and

(i) thereafter resetting to a no authentication mode in which the second mode is performed.

34. A computer comprising software, wherein, when the computer executes the software, the computer performs the steps of claim 26 .

35. A system, comprising:

(a) an input to receive, from a source node, a packet comprising a header that includes first and second message authentication codes and source port and checksum fields, the header having been altered by a firewall;

(b) a transport agent, at a destination node, operable to compute, for the packet, a third message authentication code and apply the following rules:

(b1) when the first and third message authentication codes match, the packet is authenticated successfully; and

(b2) when the first and third message authentication codes do not match, the packet is not authenticated successfully;

wherein the first and third message authentication codes are computed by the source and destination nodes, respectively, and exclude values for the source port and checksum fields.

36. The system of claim 35 , wherein the first message authentication code is contained in an Open Systems Interconnect (“OSI”) transport layer portion of the header and the second message authentication code is contained in an authentication header used between OSI layers 3 and 4 .

37. The system of claim 35 , wherein the first message authentication code is contained in an authentication option.

38. The system of claim 37 , wherein the authentication option comprises an option indicator having a value associated with the authentication option, a length having a value associated with the length of the first message authentication code, and the first message authentication code, and wherein the first message authentication code is truncated to a selected number of bits.

39. The system of claim 35 , wherein, in computing the first and third message authentication codes, the value for the destination port is excluded.

40. The system of claim 35 , wherein the first and third message authentication codes are computed based on values for members of a set of fields, the values being the same as the values for the members of the set of fields contained in the header, both before and after firewall alteration, and wherein the set of fields comprise a plurality of an urgent pointer flag, PSH flag, finished flag, acknowledgment flag, synchronize flag, reset flag, sequence number, acknowledgment number, data offset, window, options, and padding.

41. The system of claim 35 , further comprising, after the receiving step:

(c) in a first mode, discarding the packet when the packet header does not include the authentication option; and

(d) in a second, different mode, discarding the packet when the packet header includes an authentication option, whether valid or invalid, wherein the computing and applying steps occur only in the first mode.

42. The system of claim 41 , further comprising:

(e) negotiating, by the source and destination nodes, protocol parameters over an insecure channel;

(f) receiving a start cipher and/or change cipher spec command;

(g) in response initiating receive authentication using a shared secret, wherein, in receive authentication, the first mode is performed; and

(h) thereafter resetting to a no authentication mode in which the second mode is performed.

Assignments (24)
(SECURITY INTEREST) GRANTOR'S NAME CHANGE Recorded Sep 21, 2023
From: AVAYA INC.
To: AVAYA LLC
Reel/Frame 065019/0231 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 61087/0386) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063690/0359 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 53955/0436) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063705/0023 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001) Recorded May 18, 2023
From: GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT
To: AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.); HYPERQUALITY, INC.; HYPERQUALITY II, LLC; CAAS TECHNOLOGIES, LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 063779/0622 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 4, 2023
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 063542/0662 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 3, 2023
From: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; KNOAHSOFT INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB [COLLATERAL AGENT]
Reel/Frame 063742/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026 Recorded Apr 26, 2023
From: CITIBANK, N.A., AS COLLATERAL AGENT
To: AVAYA HOLDINGS CORP.; AVAYA INC.; AVAYA MANAGEMENT L.P.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063457/0001 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Aug 5, 2022
From: AVAYA INC.; INTELLISIST, INC.; AVAYA MANAGEMENT L.P.; AVAYA CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 061087/0386 →
BANKRUPTCY COURT ORDER RELEASING THE SECURITY INTEREST RECORDED AT REEL/FRAME 020156/0149 Recorded Jul 25, 2022
From: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
To: AVAYA, INC.; AVAYA TECHNOLOGY LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES
Reel/Frame 060953/0412 →
SECURITY INTEREST Recorded Sep 25, 2020
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 053955/0436 →
SECURITY INTEREST Recorded Jan 23, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 045124/0026 →
SECURITY INTEREST Recorded Jan 10, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 045034/0001 →
RELEASE OF SECURITY INTEREST Recorded Jan 9, 2018
From: CITICORP USA, INC.
To: AVAYA, INC.; SIERRA HOLDINGS CORP.; AVAYA TECHNOLOGY, LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.
Reel/Frame 045032/0213 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 025863/0535 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST, NA
To: AVAYA INC.
Reel/Frame 044892/0001 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001 Recorded Dec 15, 2017
From: CITIBANK, N.A.
To: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION); VPNET TECHNOLOGIES, INC.
Reel/Frame 044893/0531 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 030083/0639 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 045012/0666 →
SECURITY INTEREST Recorded Jan 27, 2017
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS CORPORATION; VPNET TECHNOLOGIES, INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 041576/0001 →
SECURITY AGREEMENT Recorded Mar 13, 2013
From: AVAYA, INC.
To: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE
Reel/Frame 030083/0639 →
SECURITY AGREEMENT Recorded Feb 22, 2011
From: AVAYA INC., A DELAWARE CORPORATION
To: BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLATERAL AGENT, THE
Reel/Frame 025863/0535 →
CONVERSION FROM CORP TO LLC Recorded May 12, 2009
From: AVAYA TECHNOLOGY CORP.
To: AVAYA TECHNOLOGY LLC
Reel/Frame 022677/0550 →
REASSIGNMENT Recorded Jun 26, 2008
From: AVAYA TECHNOLOGY LLC; AVAYA LICENSING LLC
To: AVAYA INC
Reel/Frame 021156/0082 →
SECURITY AGREEMENT Recorded Nov 28, 2007
From: AVAYA, INC.; AVAYA TECHNOLOGY LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.
To: CITICORP USA, INC., AS ADMINISTRATIVE AGENT
Reel/Frame 020166/0705 →
SECURITY AGREEMENT Recorded Nov 27, 2007
From: AVAYA, INC.; AVAYA TECHNOLOGY LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 020156/0149 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 27, 2003
From: DONLEY, CHRISTOPHER J.; GILMAN, ROBERT R.; HASERODT, KURT H.; WALTON, JOHN M.
To: AVAYA TECHNOLOGY CORP.
Reel/Frame 013932/0257 →
Continuity (1)
Related Publication 20040193876A1 · Sep 30, 2004