throbber
Presentation of Petitioner Apple Inc.
`
`IPR2015-00810
`IPR2015-00811
`IPR2015-00812
`
`
`U.S. Patent No. 8,868,705, ,
`
`U.S. Patent No. 8,850,009
`
`Petitioner Apple Inc. – Ex. 1070
`
`1
`
`

`
`IPR2015-00810 & -00812
`Beser and RFC 2401
`Grounds
`
`1.
`
`2.
`
`IPR2015-00810
`A. Ground 1: Whether Claims 1-4, 6-10, 12-26, and
`
`28 3428-34 are obvious under 35 U.S.C. § 103 over b i d 35 U S C § 103
`
`
`
`Beser (Beser (Ex. 1007)) and RFC 2401 (Ex.
`1008)
`B. Ground 2: Whether Claims 5, 11, and 27 are
`obvious under 35 U.S.C. § 103 over Beser, RFC
`2401 and Brand (Ex. 1012)
`IPR2015-00812
`A. Ground 1: Whether Claims 1-8,10-20, and 22-25
`b iare obvious under 35 U.S.C. § 103 over Beser d 35 U S C § 103 B
`
`
`
`
`(Beser (Ex. 1007)) and RFC 2401 (Ex. 1008)
`
`Petitioner Apple Inc. – Ex. 1070
`
`2
`
`

`
`IPR2015-00810, -812
`
`1. Beser and RFC 2401 Issues (810 & 812)
`A. Combining Beser and RFC 2401 would have been obvious
`to one of ordinary skill in the art (810 claims 1, 21) (812
`claims 1, 14))
`B. Beser and RFC 2401 teach “a request to look up an
`Internet Protocol (IP) address corresponding to a domain
`
`name associated with the target device” (810 claims 1, 21)name associated with the target device (810 claims 1, 21)
`(812 claims 1, 14)
`C. Beser and RFC 2401 teach “intercepting from the client
`
`device [the] request to look up an Internet Protocol (IP)device [the] request to look up an Internet Protocol (IP)
`address” (810 claims 1, 21) (812 claims 1, 14)
`2. Beser and RFC 2401 Issues (812 only)
`A. Beser and RFC 2401 teach “Receiv[ing]. . . An Indication, a
`Network Address, and Provisioning Information” (claims 1,
`14)
`
`Petitioner Apple Inc. – Ex. 1070
`
`3
`
`

`
`Beser and RFC 2401 Grounds
`
`RFC 2401 at 25; Pet. at 24
`
`Petitioner Apple Inc. – Ex. 1070
`
`4
`
`

`
`IPR2015-00810, -812
`Ground 1: Beser and RFC 2401
`
`1. Beser and RFC 2401 Issues (810 & 812)
`A. Combining Beser and RFC 2401 would have been
`obvious to one of ordinary skill in the art (810 claims 1,
`
`21) (812 claims 1, 14)) ( )
`
`B. Beser and RFC 2401 teach “a request to look up an
`Internet Protocol (IP) address corresponding to a domain
`
`name associated with the target device” (810 claims 1, 21)name associated with the target device (810 claims 1, 21)
`(812 claims 1, 14)
`C. Beser and RFC 2401 teach ““intercepting from the client
`
`device [the] request to look up an Internet Protocol (IP)device [the] request to look up an Internet Protocol (IP)
`address” (810 claims 1, 21) (812 claims 1, 14)
`2. Beser and RFC 2401 Issues (812 only)
`A. Beser and RFC 2401 teach “Receiv[ing]. . . An Indication, a
`Network Address, and Provisioning Information” (claims 1,
`14)
`
`Petitioner Apple Inc. – Ex. 1070
`
`5
`
`

`
`Grounds Based on Beser and RFC 2401
`Combining Beser and RFC 2401
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01 Admin
`AventaGuide Page 010 pngil Connect v3 01 Admin
`
`Beser (Ex. 1007) at 1:54-58; Pet. (810) at 22, 24
`
`US8868705_Page_001.png
`
`1009 - IPR2015-00811 1 -
`
`AventaGuide Page 010 pngil Connect v3 01 AdminAventaGuide_Page_010.pngil Connect v3.01 Admin
`
`Beser (Ex. 1007) at 2:1-5; Reply (810) at 4
`
`Petitioner Apple Inc. – Ex. 1070
`
`6
`
`

`
`Grounds Based on Beser and RFC 2401
`Combining Beser and RFC 2401
`
`_
`g _
`p g
`1009 - IPR2015-00811 1 - AventaGuide_Page_010.pngil
`Connect v3.01 Admin
`
`Beser (Ex. 1007) at 2:36-40; Reply (810) at 5
`
`US8868705_Page_001.png
`
`Petitioner Apple Inc. – Ex. 1070
`
`7
`
`

`
`Combining Beser and RFC 2401
`
`1009 - IPR2015-00811 1 -
`US8868705_Page_001.png
`AventaGuide Page 010.pngil Connect v3.01 Admin
`_
`g _
`p g
`
`Pet. (810) at 28
`
`Petitioner Apple Inc. – Ex. 1070
`
`8
`
`

`
`Institution Decision
`Combining Beser and RFC 2401
`
`US8868705_Page_001.png
`
`Decision (810) at 13
`
`Petitioner Apple Inc. – Ex. 1070
`
`9
`
`

`
`Patent Owner Assertion
`Combining Beser and RFC 2401
`
`Opposition (810) at 32
`
`Petitioner Apple Inc. – Ex. 1070
`
`10
`
`

`
`Final Written Decision in IPR2014-00237
`Combining Beser and RFC 2401
`
`Final Written Decision, IPR2014-00237 at 41; Reply (810) at 2-3
`
`Petitioner Apple Inc. – Ex. 1070
`
`11
`
`

`
`Grounds Based on Beser and RFC 2401
`Combining Beser and RFC 2401
`
`1009 IPR2015 00811 11009 - IPR2015-00811 1 -
`
`AventaGuide_Page_010.pngil Connect v3.01 Admin
`
`US8868705_Page_001.png
`
`Beser (Ex. 1007) at 1:60-67; Pet. (810) at 24; Reply (810) at 6
`
`Petitioner Apple Inc. – Ex. 1070
`
`12
`
`

`
`Grounds Based on Beser and RFC 2401
`Combining Beser and RFC 2401
`
`1009 IPR2015 00811 11009 - IPR2015-00811 1 -
`
`AventaGuide_Page_010.pngil Connect v3.01 Admin
`US8868705_Page_001.png
`
`Beser (Ex. 1007) at 2:18-35; Pet. (810) at 29; Reply (810) at 4
`
`Petitioner Apple Inc. – Ex. 1070
`
`13
`
`

`
`IPR2015-00810, -812
`Ground 1: Beser and RFC 2401
`
`1. Beser and RFC 2401 Issues (810 & 812)
`A. Combining Beser and RFC 2401 would have been obvious
`to one of ordinary skill in the art (810 claims 1, 21) (812
`claims 1, 14))
`B. Beser and RFC 2401 teach “a request to look up an
`Internet Protocol (IP) address corresponding to a
`
`domain name associated with the target device” (810domain name associated with the target device (810
`claims 1, 21) (812 claims 1, 14)
`C. Beser and RFC 2401 teach “intercepting from the client
`
`device [the] request to look up an Internet Protocol (IP)device [the] request to look up an Internet Protocol (IP)
`address” (810 claims 1, 21) (812 claims 1, 14)
`2. Beser and RFC 2401 Issues (812 only)
`A. Beser and RFC 2401 teach “Receiv[ing]. . . An Indication, a
`Network Address, and Provisioning Information” (claims 1,
`14)
`
`Petitioner Apple Inc. – Ex. 1070
`
`14
`
`

`
`’705 Patent, Claim 1
`
`US8868705_Page_001.png
`
`’705 Patent (Ex. 1001) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1070
`
`15
`
`

`
`Grounds Based on Beser and RFC 2401
`Combining Beser and RFC 2401
`
`US8868705_Page_001.png
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect
`v3.01 Admin
`
`Beser (Ex. 1007) at Fig. 4; Pet. (810) at 43
`
`Petitioner Apple Inc. – Ex. 1070
`
`16
`
`

`
`Beser and RFC 2401
`“a request to look up an Internet Protocol (IP) address”
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01 Admin
`AventaGuide Page 010 pngil Connect v3 01 Admin
`
`US8868705_Page_001.png
`
`Pet. at 34
`
`1009 - IPR2015-00811 1 -1009 IPR2015 00811 1
`
`
`AventaGuide_Page_010.pngil Connect v3.01 Admin
`
`Ex. 1005 at ¶ 310; Pet. (810) at 33
`
`Petitioner Apple Inc. – Ex. 1070
`
`17
`
`

`
`Patent Owner Assertion
`“a request to look up an Internet Protocol (IP) address”
`
`Opposition (810) at 23
`
`Petitioner Apple Inc. – Ex. 1070
`
`18
`
`

`
`Patent Owner Assertion
`“a request to look up an Internet Protocol (IP) address”
`
`Opposition (810) at 23
`
`Petitioner Apple Inc. – Ex. 1070
`
`19
`
`

`
`Grounds Based on Beser and RFC 2401
`“a request to look up an Internet Protocol (IP) address”
`
`US8868705_Page_001.png
`
`
`1009 IPR2015 00811 11009 - IPR2015-00811 1 -
`
`* * ** * *
`AventaGuide_Page_010.pngil
`Connect v3.01 Admin
`
`
`
`Beser (Ex 1007) at 11:23 58; Pet (810) at 33Beser (Ex. 1007) at 11:23-58; Pet. (810) at 33
`
`Petitioner Apple Inc. – Ex. 1070
`
`20
`
`

`
`Grounds Based on Beser and RFC 2401
`“a request to look up an Internet Protocol (IP) address”
`
`Beser (Ex. 1007) at Fig. 5; Reply (810) at 10
`
`1009 - IPR2015-00811 1 -
`US8868705_Page_001.png
`AventaGuide_Page_010.pngil Connect
`v3.01 Admin
`
`
`
`* * ** * *
`
`
`
`Beser (Ex 1007) at 11:23 58; Pet (810) at 33Beser (Ex. 1007) at 11:23-58; Pet. (810) at 33
`
`Beser (Ex. 1007) at Fig. 6; Pet. (810) at 17-19, 34
`
`Petitioner Apple Inc. – Ex. 1070
`
`21
`
`

`
`Beser and RFC 2401
`“a request to look up an Internet Protocol (IP) address”
`
`1009 - IPR2015-00811 1 -
`
`AventaGuide Page 010.pngil Connect v3.01 AdminAventaGuide_Page_010.pngil Connect v3.01 Admin
`
`US8868705_Page_001.png
`
`Ex. 1005 at ¶ 310; Pet. (810) at 34
`
`Petitioner Apple Inc. – Ex. 1070
`
`22
`
`

`
`’705 Patent, Claim 1
`
`’705 Patent (Ex. 1001) at Claim 1
`
`US8868705_Page_001.png
`
`’705 Patent (Ex. 1001) at 40:18-19
`
`Petitioner Apple Inc. – Ex. 1070
`
`23
`
`

`
`Patent Owner Assertion
`“a request to look up an Internet Protocol (IP) address”
`
`Opposition at 22
`
`Petitioner Apple Inc. – Ex. 1070
`
`24
`
`

`
`Grounds Based on Beser and RFC 2401
`“a request to look up an Internet Protocol (IP) address”
`
`1009 - IPR2015-00811 1 -
`
`AventaGuide Page 010 pngil Connect v3 01AventaGuide_Page_010.pngil Connect v3.01
`AdminBeser (Ex. 1007) at 9:29-30; Pet. 20, 35-36
`
`US8868705_Page_001.png
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil
`Connect v3.01 Admin
`
`Beser (Ex. 1007) at Fig. 6; Pet. (810) at 17-18
`
`Petitioner Apple Inc. – Ex. 1070
`
`25
`
`

`
`Final Written Decision in IPR2014-00237
`“a request to look up an Internet Protocol (IP) address”
`
`Final Written Decision, IPR2014-00237 at 24; Reply (810) at 8
`
`Petitioner Apple Inc. – Ex. 1070
`
`26
`
`

`
`IPR2015-00810, -812
`Ground 1: Beser and RFC 2401
`
`1. Beser and RFC 2401 Issues (810 & 812)
`A. Combining Beser and RFC 2401 would have been obvious
`to one of ordinary skill in the art (810 claims 1, 21) (812
`claims 1, 14))
`B. Beser and RFC 2401 teach “a request to look up an
`Internet Protocol (IP) address corresponding to a domain
`
`name associated with the target device” (810 claims 1, 21)name associated with the target device (810 claims 1, 21)
`(812 claims 1, 14)
`C. Beser and RFC 2401 teach “intercepting from the client
`
`device [the] request to look up an Internet Protocol (IP)device [the] request to look up an Internet Protocol (IP)
`address” (810 claims 1, 21) (812 claims 1, 14)
`2. Beser and RFC 2401 Issues (812 only)
`A. Beser and RFC 2401 teach “Receiv[ing]. . . An Indication, a
`Network Address, and Provisioning Information” (claims 1,
`14)
`
`Petitioner Apple Inc. – Ex. 1070
`
`27
`
`

`
`’705 Patent, Claim 1
`“intercepting … [the] request to look up an Internet Protocol (IP) address”
`
`US8868705_Page_001.png
`
`’705 Patent (Ex. 1001) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1070
`
`28
`
`

`
`Grounds Based on Beser and RFC 2401
`“intercepting … [the] request to look up an Internet Protocol (IP) address”
`
`US8868705_Page_001.png
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01
`Admin
`
`Pet. at 32-33
`
`Petitioner Apple Inc. – Ex. 1070
`
`29
`
`

`
`Grounds Based on Beser and RFC 2401
`“intercepting … [the] request to look up an Internet Protocol (IP) address”
`
`1009 IPR2015 00811 1 A1009 - IPR2015-00811 1 - AventaGuide_Page_010.pngil G id P 010 il
`
`
`Connect v3.01 Admin
`
`
`
`
`
`US8868705_Page_001.png
`
`Beser (Ex. 1007) at 8:38-43; Pet. (810) at 18
`
`Petitioner Apple Inc. – Ex. 1070
`
`30
`
`

`
`Patent Owner Assertion
`“a request to look up an Internet Protocol (IP) address”
`
`Opposition (810) at 25
`
`Opposition (810) at 22
`
`Petitioner Apple Inc. – Ex. 1070
`
`31
`
`

`
`Patent Owner Admission
`Dr. Monrose: tunneling requests are not addressed to the trusted device
`
`Ex. 2016 at ¶ 38; Opposition (810) at 26
`
`Ex. 1066 at 101:11-14
`
`Petitioner Apple Inc. – Ex. 1070
`
`32
`
`

`
`’705 Patent
`“intercepting … [the] request to look up an Internet Protocol (IP) address”
`
`US8868705_Page_001.png
`
`’705 Patent (Ex. 1001) at 40:1-3
`
`Ex. 1005 at ¶ 68; Pet. (810) at 10
`
`Petitioner Apple Inc. – Ex. 1070
`
`33
`
`

`
`Patent Owner Admission
`Dr. Monrose: has no opinion about what “intercepting” requires
`
`Ex. 1066 at 132:7-13; Reply (810) at 14
`
`Petitioner Apple Inc. – Ex. 1070
`
`34
`
`

`
`Final Written Decision in IPR2014-00237
`“intercepting … [the] request to look up an Internet Protocol (IP) address”
`
`Final Written Decision, IPR2014-00237 at 24; Reply (810) at 8
`
`Petitioner Apple Inc. – Ex. 1070
`
`35
`
`

`
`IPR2015-00810, -812
`
`1. Beser and RFC 2401 Issues (810 & 812)
`A. Combining Beser and RFC 2401 would have been obvious
`to one of ordinary skill in the art (810 claims 1, 21) (812
`claims 1, 14))
`B. Beser and RFC 2401 teach “a request to look up an
`Internet Protocol (IP) address corresponding to a domain
`
`name associated with the target device” (810 claims 1, 21)name associated with the target device (810 claims 1, 21)
`(812 claims 1, 14)
`C. Beser and RFC 2401 teach “intercepting from the client
`
`device [the] request to look up an Internet Protocol (IP)device [the] request to look up an Internet Protocol (IP)
`address” (810 claims 1, 21) (812 claims 1, 14)
`2. Beser and RFC 2401 Issues (812 only)
`A. Beser and RFC 2401 teach “Receiv[ing]. . . An
`Indication, a Network Address, and Provisioning
`Information” (claims 1, 14)
`
`Petitioner Apple Inc. – Ex. 1070
`
`36
`
`

`
`’009 Patent, Claim 1
`
`“receive” an “indication” and the “network address”ece e a d cat o a d t e et o add ess
`
`
`
`
`US8868705_Page_001.png
`
`’009 Patent (Ex. 1001) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1070
`
`37
`
`

`
`Patent Owner Assertion
`Beser does not show both “an indication” and a “network address”
`
`Response (812) at 40-41
`
`Petitioner Apple Inc. – Ex. 1070
`
`38
`
`

`
`Grounds Based on Beser and RFC 2401
`Beser teaches “an indication” and a “network address”
`
`US8868705_Page_001.png
`
`Pet. (812) at 41
`
`Beser (Ex. 1007) at 21:48-54; Pet. (812) at 41; Reply (812) at 17
`
`Petitioner Apple Inc. – Ex. 1070
`
`39
`
`

`
`IPR2015-00811
`Grounds
`1. Whether Claims 1-3, 6, 14, 16-25, 28, 31, and 34 are
`obvious under 35 U.S.C. § 103 over Aventail (Ex. 1009)
`
`and RFC 2401 (Ex. 1008)and RFC 2401 (Ex. 1008)
`
`2. Whether Claims 8-10, 12, 15, 30 and 32 are obvious under
`
`35 U.S.C. § 103 over Aventail, RFC 2401 and RFC 254335 U.S.C. § 103 over Aventail, RFC 2401 and RFC 2543
`(Ex. 1013)
`
`
`
`
`
`3. Whether Claims 4, 5, 7, 26, 27, and 29 are obvious under 3 e e C a s , 5, , 6, , a d 9 a e ob ous u de
`35 U.S.C. § 103 over Aventail, RFC 2401 and Brand (Ex.
`1012)
`
`4. Whether Claims 11 and 13 are obvious under 35 U.S.C. §
`103 over Aventail, RFC 2401, RFC 2543 and Brand
`
`Petitioner Apple Inc. – Ex. 1070
`
`40
`
`

`
`Grounds Based on Aventail and RFC 2401
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01
`
`Admin Guide Page 010 pngAdmin Guide_Page_010.png
`Aventail (Ex. 1009) at 10; Pet. at 19, 33
`
`Aventail (Ex. 1009) at 72
`Pet. at 17
`
`Petitioner Apple Inc. – Ex. 1070
`
`41
`
`

`
`Grounds Based on Aventail and RFC 2401
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`Guide_Page_010.png
`
`Aventail (Ex. 1009) at 11-12
`Pet. at 31-32, passim
`
`Petitioner Apple Inc. – Ex. 1070
`
`42
`
`

`
`Grounds Based on Aventail and RFC 2401
`
`1009 IPR2015 00811 1
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01
`Admin
`
`Aventail (Ex. 1009) at 11-12
`Pet. at 31-32, passim
`
`Petitioner Apple Inc. – Ex. 1070
`
`43
`
`

`
`IPR2015-00811
`
`1. Aventail and RFC 2401 Issues
`A. Aventail and RFC 2401 teach “Determining
`Whether the Request to Look Up the IP Address q p
`
`
`[Intercepted] in Step (1) . . . Corresponds to a
`Device that Accepts an Encrypted Channel
`
`CConnection” (claims 1, 21)ti ” ( l i 1 21)
`
`
`
`
`B. Aventail and RFC 2401 teach “Encrypted
`
`CCommunications Channel Between the Client Device i ti Ch l B t th Cli t D i
`
`
`
`
`
`and the Target Device” (claims 1, 21)
`
`C AC. Aventail and RFC 2401 teach “In Response to t il d RFC 2401 t h “I R t
`
`
`
`
`
`Determining . . . Providing Provisioning Information”
`
`i( l(claims 1, 21)1 21)
`
`
`
`
`
`Petitioner Apple Inc. – Ex. 1070
`
`44
`
`

`
`’705 Patent, Claim 1
`
`US8868705_Page_001.png
`
`’705 Patent (Ex. 1001) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1070
`
`45
`
`

`
`Grounds Based on Aventail and RFC 2401
`“a request to look up an Internet Protocol (IP) address”
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01
`Pet. at 31
`
`Ad iAdmin
`Reply at 7
`
`1009 - IPR2015-00811 1 -
`AventaGuide_Page_010.pngil Connect v3.01
`Admin
`US8868705_Page_001.png
`
`Pet. at 31
`
`1009 IPR2015 00811 11009 - IPR2015-00811 1 -
`
`AventaGuide_Page_010.pngil Connect v3.01
`Admin
`
`Reply at 7
`
`Petitioner Apple Inc. – Ex. 1070
`
`46
`
`

`
`Grounds Based on Aventail and RFC 2401
`“a request to look up an Internet Protocol (IP) address”
`
`1009
`IPR2015 00811 1 Aventail Connect v3.01 Admin
`1009 - IPR2015-00811 1 - Aventail Connect v3 01 Admin
`Guide_Page_010.png
`
`Aventail (Ex. 1009) at 10
`Pet. at 19, 33
`
`1009 IPR2015 00811 1 Aventail Connect v3 01 Admin1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`
`Guide_Page_010.png
`
`Aventail (Ex. 1009) at 11-12
`A
`t il (E 1009)
`t 11 12
`
`Petitioner Apple Inc. – Ex. 1070
`
`47
`
`

`
`Grounds Based on Aventail and RFC 2401
`“a request to look up an Internet Protocol (IP) address”
`
`1009 IPR2015 00811 11009 - IPR2015-00811 1 -
`
`AventaGuide_Page_010.pngil Connect v3.01
`Admin
`
`US8868705_Page_001.png
`
`Pet. at 32
`
`1009 - IPR2015-00811 1 -
`
`AAventaGuide_Page_010.pngil Connect v3.01 Admint G id P 010 il C t 3 01 Ad i
`
`
`
`
`
`
`Reply at 7
`
`Petitioner Apple Inc. – Ex. 1070
`
`48
`
`

`
`Grounds Based on Aventail and RFC 2401
`“a request to look up an Internet Protocol (IP) address”
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`Guide_Page_010.png
`
`Aventail (Ex. 1009) at 11-12
`
`Pet. at 31-32, passimPet. at 31 32, passim
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`
`G id PGuide_Page_010.png010
`
`
`Aventail (Ex. 1009) at 11-12
`Pet. at 31-32, passim
`
`Petitioner Apple Inc. – Ex. 1070
`
`49
`
`

`
`Grounds Based on Aventail and RFC 2401
`“a request to look up an Internet Protocol (IP) address”
`
`1009 - IPR2015-00811 1 - AventaGuide_Page_010.pngil Connect v3.01
`Admin
`US8868705_Page_001.png
`
`Pet. at 33
`
`Petitioner Apple Inc. – Ex. 1070
`
`50
`
`

`
`Institution Decision
`“a request to look up an Internet Protocol (IP) address”
`
`Decision (811) at 15
`
`Petitioner Apple Inc. – Ex. 1070
`
`51
`
`

`
`Institution Decision
`“a request to look up an Internet Protocol (IP) address”
`
`
`
`Decision (811) at 15 16Decision (811) at 15-16
`
`Petitioner Apple Inc. – Ex. 1070
`
`52
`
`

`
`’705 Patent, Claim 1
`
`US8868705_Page_001.png
`
`’705 Patent (Ex. 1001) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1070
`
`53
`
`

`
`Grounds Based on Aventail
`“determining whether the request to look up
`
`the IP address [intercepted] in Step (1)…”the IP address [intercepted] in Step (1)…
`
`1009
`IPR2015 00811 1 Aventail Connect v3.01 Admin
`1009 - IPR2015-00811 1 - Aventail Connect v3 01 Admin
`Guide_Page_010.png
`
`Aventail (Ex. 1009) at 10
`Pet. at 33-34
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`Guide_Page_010.png
`
`Aventail (Ex 1009) at 73Aventail (Ex. 1009) at 73
`
`Pet. at 34
`
`Petitioner Apple Inc. – Ex. 1070
`
`54
`
`

`
`Grounds Based on Aventail and RFC 2401
`“determining whether the request to look up
`
`the IP address [intercepted] in Step (1)…”the IP address [intercepted] in Step (1)…
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`Guide_Page_010.png
`
`Aventail (Ex. 1009) at 11-12
`
`Petitioner Apple Inc. – Ex. 1070
`
`55
`
`

`
`Institution Decision
`“determining whether the request to look up
`the IP address [Intercepted] in Step (1)…
`the IP address [Intercepted] in Step (1)…”
`
`
`
`Decision (811) at 16( )
`
`
`
`Petitioner Apple Inc. – Ex. 1070
`
`56
`
`

`
`Patent Owner Assertion
`“determining whether the request to look up
`
`the IP address [intercepted] in Step (1)…”the IP address [intercepted] in Step (1)…
`
`Opposition at 18
`
`Petitioner Apple Inc. – Ex. 1070
`
`57
`
`

`
`Grounds Based on Aventail
`“determining whether the request to look up
`
`the IP address [intercepted] in Step (1)…”the IP address [intercepted] in Step (1)…
`
`10091009 - IPR2015-00811 1 -201 00811 1
`
`
`AventaGuide_Page_010.pngil Connect v3.01
`Admin
`
`Aventail (Ex. 1009) at 11-12
`
`Petitioner Apple Inc. – Ex. 1070
`
`58
`
`

`
`Patent Owner Assertion
`“determining whether the request to look up
`
`the IP address [intercepted] in Step (1)…”the IP address [intercepted] in Step (1)…
`
`Opposition at 20
`
`Petitioner Apple Inc. – Ex. 1070
`
`59
`
`

`
`’705 Patent, Claim 1
`
`US8868705_Page_001.png
`
`’705 Patent (Ex. 1001) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1070
`
`60
`
`

`
`Institution Decision
`“determining whether the request to look up
`the IP address [Intercepted] in Step (1)…
`the IP address [Intercepted] in Step (1)…”
`
`Decision (811) at 19
`
`Petitioner Apple Inc. – Ex. 1070
`
`61
`
`

`
`Grounds Based on Aventail and RFC 2401
`“determining whether the request to look up
`
`the IP address [intercepted] in Step (1)…”the IP address [intercepted] in Step (1)…
`
`1009 - IPR2015-00811 1 - AsdfdfsventaGuide_Page_010.pngil
`Connect v3.01 Admin
`C
`t 3 01 Ad i
`
`Pet. at 28
`
`1009 IPR2015 00811 1 A dfdf1009 - IPR2015-00811 1 - AsdfdfsventaGuide_Page_010.pngil Connect t G id P 010 il C t
`
`
`v3.01 Admin
`
`
`
`
`
`
`
`Pet. at 41
`
`Petitioner Apple Inc. – Ex. 1070
`
`62
`
`

`
`Institution Decision
`“determining whether the request to look up
`the IP address [Intercepted] in Step (1)…
`the IP address [Intercepted] in Step (1)…”
`
`Decision (811) at 17
`
`Petitioner Apple Inc. – Ex. 1070
`
`63
`
`

`
`Institution Decision
`“determining whether the request to look up
`the IP address [Intercepted] in Step (1)…
`the IP address [Intercepted] in Step (1)…”
`
`Decision (811) at 18
`
`Petitioner Apple Inc. – Ex. 1070
`
`64
`
`

`
`Patent Owner Assertion
`“determining whether the request to look up
`
`the IP address [intercepted] in Step (1)…”the IP address [intercepted] in Step (1)…
`
`Opposition at 21
`
`Petitioner Apple Inc. – Ex. 1070
`
`65
`
`

`
`Grounds Based on Aventail and RFC 2401
`“determining whether the request to look up
`
`the IP address [intercepted] in Step (1)…”the IP address [intercepted] in Step (1)…
`
`1009
`IPR2015 00811 1 Aventail Connect v3.01 Admin
`1009 - IPR2015-00811 1 - Aventail Connect v3 01 Admin
`Guide_Page_010.png
`
`Aventail (Ex. 1009) at 10
`Pet. at 33-34
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`Guide_Page_010.png
`
`Aventail (Ex 1009) at 73Aventail (Ex. 1009) at 73
`
`Pet. at 34
`
`Petitioner Apple Inc. – Ex. 1070
`
`66
`
`

`
`Institution Decision
`“determining whether the request to look up
`the IP address [Intercepted] in Step (1)…
`the IP address [Intercepted] in Step (1)…”
`
`
`
`Decision (811) at 16( )
`
`
`
`Petitioner Apple Inc. – Ex. 1070
`
`67
`
`

`
`IPR2015-00811
`
`1. Aventail and RFC 2401 Issues
`A. Aventail and RFC 2401 teach “Determining Whether
`the Request to Look Up the IP Address [Intercepted] in q p [ p ]
`
`
`
`
`
`Step (1) . . . Corresponds to a Device that Accepts an
`Encrypted Channel Connection” (claims 1, 21)
`B. Aventail and RFC 2401 teach “Encrypted
`Communications Channel Between the Client
`
`D iDevice and the Target Device” (claims 1, 21)d th T t D i ” ( l i 1 21)
`
`
`
`
`
`C. Aventail and RFC 2401 teach “In Response to
`Determining . . . Providing Provisioning Information”
`
`Petitioner Apple Inc. – Ex. 1070
`
`68
`
`

`
`Patent Owner Assertion
`“encrypted communications channel”
`
`Opposition at 23
`
`Petitioner Apple Inc. – Ex. 1070
`
`69
`
`

`
`Grounds Based on Aventail and RFC 2401
`“encrypted communications channel”
`
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`
`Guide Page 010 pngGuide_Page_010.png
`
`Reply at 3
`
`Petitioner Apple Inc. – Ex. 1070
`
`70
`
`

`
`Grounds Based on Aventail and RFC 2401
`“[Direct] encrypted communications channel”
`
`1009 - IPR2015-00811 1 - Aventail Connect
`v3.01 Admin Guide_Page_010.png
`1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`Guide_Page_010.png
`
`Aventail (Ex. 1009) at 11-12
`
`Petitioner Apple Inc. – Ex. 1070
`
`71
`
`

`
`Grounds Based on Aventail and RFC 2401
`“[Direct] encrypted communications channel”
`
`1009 - IPR2015-00811 1 - Aventail Connect v3 01 Admin1009 - IPR2015-00811 1 - Aventail Connect v3.01 Admin
`
`Guide_Page_010.png
`
`Pet. at 23-24
`Aventail (Ex. 1009) at 90-101
`
`Petitioner Apple Inc. – Ex. 1070
`
`72
`
`

`
`IPR2015-00811
`
`1. Aventail and RFC 2401 Issues
`A. Aventail and RFC 2401 teach “Determining Whether
`the Request to Look Up the IP Address [Intercepted] in q p [ p ]
`
`
`
`
`
`Step (1) . . . Corresponds to a Device that Accepts an
`Encrypted Channel Connection” (claims 1, 21)
`B. Aventail and RFC 2401 teach “Encrypted
`Communications Channel Between the Client Device
`1 21)i” ( lt D id th Tand the Target Device” (claims 1, 21)
`
`
`
`
`
`C. Aventail and RFC 2401 teach “In Response to
`Determining . . . Providing Provisioning
`Information” (claims 1, 21)
`
`Petitioner Apple Inc. – Ex. 1070
`
`73
`
`

`
`’705 Patent, Claim 1
`
`US8868705_Page_001.png
`
`’705 Patent (Ex. 1001) at Claim 1
`
`Petitioner Apple Inc. – Ex. 1070
`
`74
`
`

`
`Institution
`Construction of “provisioning information”
`
`Decision (811) at 9
`
`Petitioner Apple Inc. – Ex. 1070
`
`75
`
`

`
`Institution Decision
`“provisioning information”
`
`
`
`D iDecision (811) at 19i (811) t 19
`
`
`
`
`
`
`
`Petitioner Apple Inc. – Ex. 1070
`
`76
`
`

`
`Patent Owner Assertion
`“provisioning information”
`
`Opposition at 10-11
`
`Opposition at 29
`
`Opposition at 29
`
`Petitioner Apple Inc. – Ex. 1070
`
`77
`
`

`
`IPR2015-00810-812
`
`Aventail and the RFC References are Prior Art
`
`Petitioner Apple Inc. – Ex. 1070
`
`78
`
`

`
`Declaration of Christopher A. Hopen
`
`Petition at 15-16
`Reply at 21-22
`Ex. 1023
`Petitioner Apple Inc. – Ex. 1070
`
`79
`
`

`
`Declaration of James Chester
`
`Petition at 15-17
`Reply at 21-23
`Ex. 1022
`Petitioner Apple Inc. – Ex. 1070
`
`80
`
`

`
`Declaration of Michael Allyn Fratto
`
`Petition at 15-17
`Reply at 21-23
`Ex. 1043
`Petitioner Apple Inc. – Ex. 1070
`
`81
`
`

`
`Exhibit I to
`y
`Declaration of Michael Allyn Fratto
`
`Reply at 21-23
`Ex. 1043 at 275
`
`Petitioner Apple Inc. – Ex. 1070
`
`82
`
`

`
`RFCs
`
`Petitioner’s Expert, Dr. Tamassia
`
`Petitioner’s Expert, Dr. Tamassia
`
`Ex. 1005 at ¶149; Ex. 1036 at 6; 811 Pet. at 24
`
`
`
`Ex. 2015 at 103:1-13; Reply at 21Ex. 2015 at 103:1 13; Reply at 21
`
`Petitioner Apple Inc. – Ex. 1070
`
`83
`
`

`
`RFCs
`
`NetworkWorld, Mar. 15, 1999
`
`InfoWorld, Aug. 16, 1999
`
`
`
`E 1065 t 3 810 R lEx. 1065 at 3; 810 Reply at 21t 21
`
`
`
`
`
`E 1064 t 9 810 R lEx. 1064 at 9; 810 Reply at 21t 21
`
`
`
`Petitioner Apple Inc. – Ex. 1070
`
`84
`
`

`
`Beser and RFC 2401
`
`1009 - IPR2015-00811 1 - AventaGuide_Page_010.pngil Connect v3.01
`Admin
`
`US8868705_Page_001.png
`
`Reply at 2-3
`
`Petitioner Apple Inc. – Ex. 1070
`
`85
`
`

`
`Beser and RFC 2401
`
`1009 - IPR2015-00811 1 - AventaGuide_Page_010.pngil Connect v3.01
`Admin
`
`US8868705_Page_001.png
`
`
`
`Reply at 8Reply at 8
`
`Petitioner Apple Inc. – Ex. 1070
`
`86

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket