1 C
`
`-HTTP
`The development of
`a secure, closed HTTP-based network
`on the Internet
`
`Takahiro Kiuchi, M.D.
`
`Dep. of Epidemiology and Biostatistics,
`Faculty of Medicine, University of Tokyo, Japan
`
`Shigekoto Kaihara, M.D.
`
`Hospital Computer Center,
`University of Tokyo Hospital, Japan
`
`VIRNETX EXHIBIT 2063
`Mangrove v. VirnetX
`Trial IPR2015-01047
`
`Page 1 of 42
`
`
`
`-HTTP
`The development of
`a secure, closed HTTP-based network
`on the Internet
`
`Takahiro Kiuchi, M.D.
`
`Dep. of Epidemiology and Biostatistics,
`Faculty of Medicine, University of Tokyo, Japan
`
`Shigekoto Kaihara, M.D.
`
`Hospital Computer Center,
`University of Tokyo Hospital, Japan
`
`VIRNETX EXHIBIT 2063
`Mangrove v. VirnetX
`Trial IPR2015-01047
`
`Page 1 of 42
`
`
`
`2 I
`
`ntroduction (1)
`
`Medical Community
`
`1. Needs for secure data communications
`
`Multi-institutional clinical research
`Case reports
`Patient referral
`
`2. Unskilled computer users
`
`Keys? Certificates? Encryption?
`
`3. Security insensitive users
`
`Security of their patient’s information, not their own
`
`Page 2 of 42
`
`
`
`3 I
`
`ntroduction (2)
`
`Current Medical Information Networks in Japan
`
`1. UMIN (University Medical Information Network)
`
`Participants University Hospitals
`Protocol
`N1 Protocol
`Internet
`Not accessible
`
`2. Cancer Center Network
`
`Participants Central and regional
`national cancer centers
`TCP/IP
`Accessible via a gateway
`
`Protocol
`Internet
`
`Page 3 of 42
`
`
`
`4 I
`
`ntroduction (3)
`
`“Physical” closed network
`
`1. Expensive
`
`2. Not flexible
`
` Virtual closed network
`
`Page 4 of 42
`
`
`
`5 I
`
`ntroduction (4)
`
`Why HTTP? Why not our own?
`
`1) Flexibility of HTTP
`Most services can be provided
`using HTTP.
`
`2) User friendly interface
`
`3) User agents and servers available
`on almost all platforms
`
`Page 5 of 42
`
`
`
`6 C
`
`-HTTP Overview (1)
`
`Overview
`
`1. C-HTTP
` *Proxy on a firewall of each site
` *Secure data communication
`between proxies
` *Proxy-proxy authentication
` (Institutional authentication)
`
`2. C-HTTP name service
`*Centralized name, certificate and
`public key administration
`*Secure
`name
`service,
`encryption (DNS not used)
`
`using
`
`3. Scalability
`*A
`few hundreds of hospitals
`(proxies)
`
`Page 6 of 42
`
`
`
`7 C
`
`-HTTP overview (2)
`
` Hospital A
`
`User agent (UA)
` HTTP 1.0
` 12 1
`
`Client-side proxy (CP)
`
` 3 2 C-HTTP name service
`
`The Internet
`
`C-HTTP
`
`C-HTTP name server
`
`( N S )
` 7, 11 4, 8 5 6 C-HTTP name service
`
`
`Server-side proxy (SP)
` HTTP 1.0
` 10 9
`
`Origin server (OS)
` Hospital B
`
`Page 7 of 42
`
`
`
`8 C
`
`-HTTP overview (3)
`
`Security technology
`
`SSL (SSLeay 0.5.1a)
`Asymmetric key encryption
`Symmetric key encryption
`Electronic signature
`One-way hush function
`Random key generation
`
`Protocol layer
`
`1. HTTP/1.0
`
`1. C-HTTP name service
`
`2. C-HTTP
`
`3. SSL
`
`4. TCP/IP
`
`2. SSL
`
`3. TCP/IP
`
`Page 8 of 42
`
`
`
`9 C
`
`-HTTP overview (4)
`
`Information each component keeps
`
`1. C-HTTP name server (NS)
`Own IP address and port number
`Own private key
`Own public key
`Public keys of all proxies
`Resource names, IP address, port numbers of
`all proxies
`Connection table for all the combinations of proxies
`
`2. Client-side proxy (CP)
`Own private key
`Own public key
`Own resource name and IP address
`
`3. Server-side proxy (SP)
`Own private key
`Own public key
`Own resource name, IP address and port number
`
`Page 9 of 42
`
`
`
`10
`
`C-HTTP overview (5)
`
`Example of Connection Table stored in
`C-HTTP name server
`SCP
` CP
`(IP:Port)
`
`medical.server
`(222.222.222.222:2222)
`CAG.project
`(222.222.222.222:1234)
`Lung.cancer.trial
`(130.69.109.61:9876)
`AMI.trial
`(130.69.109.61:8765)
`AntibiotiCProject
`(130.69.109.57:2345)
`
`u-tokyo.hospital
` X
`
`nagano.hospital
` X
`
`osaka-u.hospital
` X
`
` X
`
` X
`
` X
`
` X
`
` X
`
` X
`
` X
`
`Page 10 of 42
`
`
`
`11
`
`C-HTTP overview (6)
`
`How to participate in a closed network
`
`1. Determine resource name, IP address and port number (in
`case of server-side proxy) of own proxy.
`
`2. Generate own private key and public key (certificate
`request).
`
`3. Send own resource name, IP address port number and public
`key (certificate request) to an administrator of C-HTTP name
`server (or C-HTTP-based network) in a secure manner.
`
`4. Obtain a public key (certificate), IP address and port number
`of the C-HTTP name server in a secure manner.
`
`Page 11 of 42
`
`
`
`12
`C-HTTP-based communication (1)
`
`Overview
`
`NS: C-HTTP name server, CP: Client-side proxy,
`SP: Server-side proxy, OS: Origin server, UA: User agent
`
`Type
`HTTP request
`
` 1.
`
`From To
`UA
`CP
`
` 2.
` 3.
`
` 4.
` 5.
` 6.
`
`C-HTTP name request CP
`C-HTTP
`name
`N S
`response
`C-HTTP request
`C-HTTP name request
`C-HTTP
`name
`response
`C-HTTP response
` 7.
`C-HTTP request
` 8.
`HTTP request
` 9.
`10. HTTP response
`11. C-HTTP response
`12. HTTP response
`
`CP
`SP
`N S
`
`SP
`CP
`SP
`O S
`SP
`CP
`
`19. HTTP request
`20. C-HTTP request
`21. HTTP request
`22. HTTP response
`23. C-HTTP response
`24. HTTP response
`
`31. HTTP request
`
`UA
`CP
`SP
`O S
`SP
`CP
`
`UA
`
`in
`
`the
`
`Explanation
`Resource
`requested
`Request for SP information
`SP information returned if available
`
`closed
`
`network
`
`Request for connection
`Request for CP information
`CP information
`
`Connection acknowledged
`Object requested
`Object requested
`Object sent
`Object sent
`Object sent
`
`Object requested
`Object requested
`Object requested
`Object sent
`Object sent
`Object sent
`
`Object not in closed network requested
`
`N S
`CP
`
`SP
`N S
`SP
`
`CP
`SP
`O S
`SP
`CP
`UA
`
`CP
`SP
`O S
`SP
`CP
`UA
`
`CP
`
`Page 12 of 42
`
`
`
`13
`
`32. C-HTTP request
`33. C-HTTP response
`34. HTTP request
`
`CP
`SP
`CP
`
`SP
`CP
`O S
`
`Request for disconnection
`Disconnection acknowledged
`Ordinary HTTP/1.0 request
`
`Page 13 of 42
`
`
`
`14
`C-HTTP overview (2)
`
` Hospital A
`
`User agent (UA)
` HTTP 1.0
` 12 1
`
`Client-side proxy (CP)
`
` 3 2 C-HTTP name service
`
`The Internet
`
`C-HTTP
`
`C-HTTP name server
`
`( N S )
` 7, 11 4, 8 5 6 C-HTTP name service
`
`
`Server-side proxy (SP)
` HTTP 1.0
` 10 9
`
`Origin server (OS)
` Hospital B
`
`Page 14 of 42
`
`
`
`15
`
`C-HTTP-based communication(2)
`
`Example
`
`Resource name
`
`u-tokyo.hospital
`medical.server
`
`
` IP
`192.168.111.111
`111.111.111.111
`222.222.222.222
`192.168.222.222
`123.123.123.123
`
`Port
`
`2222
`
`UA
`CP
`SP
`OS
`NS
`
`Page 15 of 42
`
`
`
`16
`
`C-HTTP-based communication (3)
`
` 1.
`
` 2.
` 3.
`
`Type
`HTTP request
`
`From To
`UA
`CP
`
`C-HTTP name request CP
`C-HTTP
`name
`N S
`response
`
`N S
`CP
`
`Example:
`
`in
`
`the
`
`Explanation
`Resource
`requested
`Request for SP information
`SP information returned if available
`
`closed
`
`network
`
`GET http://medical.server/index.html HTTP/1.0<CR><LF>
`
`Page 16 of 42
`
`
`
`17
`
`C-HTTP-based communication (4)
`
` 1.
`
` 2.
` 3.
`
`Type
`HTTP request
`
`From To
`UA
`CP
`
`C-HTTP name request CP
`C-HTTP
`name
`N S
`response
`
`N S
`CP
`
`in
`
`the
`
`Explanation
`Resource
`requested
`Request for SP information
`SP information returned if available
`
`closed
`
`network
`
`Protocol
`
`C-HTTP-NAME-SERVICE-VERSION<CR><LF>
`SERVICE-TYPE<CR><LF>
`RESOURCE-NAME<CR><LF>
`
`Example
`
`C-HTTP-NS/0.2<CR><LF>
`ServerInfo<CR><LF>
`medical.server<CR><LF>
`
`Page 17 of 42
`
`
`
`18
`
`C-HTTP-based communication (5)
`
`Stateless HTTP to stateful C-HTTP
`
`a. The HTML document sent from a origin server to a client-side proxy
`<TITLE>SAMPLE</TITLE>
`<BODY>
`<A HREF ="http://medical.server/sample.html">
`
`Please click here.</A>
`<A HREF ="http://another.server/">Another server.</A>
`
`</BODY>
`
`b. The HTML document rewritten and forwarded to a use agent by the client-side
`proxy. The string, "6zdDfldfcZLj8V!i", attached to the end of the URLs is a
`connection ID
`<TITLE>SAMPLE</TITLE>
`<BODY>
`<A HREF ="http://medical.server/sample.html=@=6zdDfldfcZLj8V!i">
`
`Please click here.</A>
`<A HREF = "http://another.server/=@=6zdDfldfcZLj8V!i">
`
`Another server.</A>
`</BODY>
`
`c. HTTP/1.0 request from the user agent (1) and HTTP/1.0 request encrypted and
`wrapped in C-HTTP request dispatched by the client-side proxy (2)
`
`(1) GET "http://medical.server/sample.html=@=6zdDfldfcZLj8V!i" HTTP/1.0<CR><LF>
`(2) GET "http://medical.server/sample.html" HTTP/1.0<CR><LF>
`
`Page 18 of 42
`
`
`
`19
`
`C-HTTP-based communication (6)
`
`C-HTTP session table
`
`ConnectionID SP
`azd3wzece3Zj5hJKP
`CAG.project
`2z4RTswWsdfuiOsa
`Lung.cancer.trial
`bcui2s9deklwWjP
`AMI.trial
`
`IP
`222.222.222.222
`130.69.109.61
`130.69.109.61
`
`Port UA
`1234
`192.168.109.2
`9876
`192.168.108.3
`8765
`192.168.111.4
`
`Page 19 of 42
`
`
`
`20
`
`C-HTTP-based communication (7)
`
` 2.
` 3.
`
` 4.
`
`C-HTTP name request CP
`C-HTTP
`name
`N S
`response
`C-HTTP request
`
`CP
`
`N S
`CP
`
`SP
`
`Request for SP information
`SP information returned if available
`
`Request for connection
`
`Protocol
`
`C-HTTP-NAME-SERVICE-STATUS<CR><LF>
`SERVER-SIDE-PROXY-IP<CR><LF>
`SERVER-SIDE-PROXY-PORT<CR><LF>
`SERVER-SIDE-PROXY-CERTIFICATE<CR><LF>
`REQUEST-NONCE<CR><LF>
`
`Example
`
`OK<CR><LF>
`222.222.222.222<CR><LF>
`222<CR><LF>
`-----BEGIN X509 CERTIFICATE-----
`MIICkjCCAjwCAQAwDQYJKoZIhvcNAQEEBQAwgdMxCzAJBgNVBAYTAkpQMQ4wDAYD
`VQQIEwVUb2t5bzESMBAGA1UEBxMJQnVua3lvLWt1MSwwKgYDVQQKEyNGYWN1bHR5
`IG9mIE1lZGljaW5lLCBVbml2LiBvZiBUb2t5bzEvMC0GA1UECxMmRGVwLiBvZiBF
`cGlkZW1pb2xvZ3kgYW5kIEJpb3N0YXRpc3RpY3MxEjAQBgNVBAMTCUtpdWNoaSBD
`QTEtMCsGCSqGSIb3DQEJARYea2l1Y2hpQGVwaXN0YXQubS51LXRva3lvLmFjLmpw
`MB4XDTk2MDIxNDExMzcyMVoXDTk2MDMxNTExMzcyMVowgdMxCzAJBgNVBAYTAkpQ
`MQ4wDAYDVQQIEwVUb2t5bzESMBAGA1UEBxMJQnVua3lvLWt1MSwwKgYDVQQKEyNG
`YWN1bHR5IG9mIE1lZGljaW5lLCBVbml2LiBvZiBUb2t5bzEvMC0GA1UECxMmRGVw
`LiBvZiBFcGlkZW1pb2xvZ3kgYW5kIEJpb3N0YXRpc3RpY3MxEjAQBgNVBAMTCUtp
`dWNoaSBDQTEtMCsGCSqGSIb3DQEJARYea2l1Y2hpQGVwaXN0YXQubS51LXRva3lv
`LmFjLmpwMFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBAKHWVLOml02szEb7WHOILMAy
`1bTh9KpbFMb+/Ib8hEAEKBUlkRVxjdWeEtD4JTw2U1dDRZc6SVq7Vo4/65IbnZ0C
`AwEAATANBgkqhkiG9w0BAQQFAANBAJK1kVbk35i7gaBGR0+CmN2XUDgY7TlcpmNY
`AwXqcbHJN1C6rfoyBrn6dW08pi4Vnd1VUFYILKtJf39+tFvBupE=
`-----END X509 CERTIFICATE-----<CR><LF>
`8abd853f<CR><LF>
`C-HTTP overview (8)
`
`Page 20 of 42
`
`
`
`21
`
` 3.
`
` 4.
` 5.
`
`name
`
`C-HTTP
`response
`C-HTTP request
`C-HTTP name request
`
`N S
`
`CP
`SP
`
`CP
`
`SP
`N S
`
`SP information returned if available
`
`Request for connection
`Request for CP information
`
`Example
`
`CONNECT C-HTTP/0.7<CR><LF>
`Client-Side-Proxy-Name: u-tokyo.hospital<CR><LF>
`Request-Nonce: 8abd8540<CR><LF>
`
`Page 21 of 42
`
`
`
`22
`
`C-HTTP overview (9)
`
` 4.
` 5.
` 6.
`
`C-HTTP request
`C-HTTP name request
`C-HTTP
`name
`response
`
`CP
`SP
`N S
`
`SP
`N S
`SP
`
`Request for connection
`Request for CP information
`CP information
`
`Protocol
`
`C-HTTP-NAME-SERVICE-VERSION<CR><LF>
`SERVICE-TYPE<CR><LF>
`RESOURCE-NAME<CR><LF>
`
`Example
`
`C-HTTP-NS/0.2<CR><LF>
`ClientInfo<CR><LF>
`u-tokyo.hospital<CR><LF>
`
`Page 22 of 42
`
`
`
`23
`C-HTTP-based communications (10)
`
` 5.
` 6.
`
` 7.
`
`C-HTTP name request
`C-HTTP
`name
`response
`C-HTTP response
`
`SP
`N S
`
`SP
`
`N S
`SP
`
`CP
`
`Request for CP information
`CP information
`
`Connection acknowledged
`
`Protocol
`
`C-HTTP-NAME-SERVICE-STATUS<CR><LF>
`Client-SIDE-PROX-IP<CR><LF>
`CLIENT-SIDE-PROXY-CERTIFICATE<CR><LF>
`RESPONSE-NONCE<CR><LF>
`
`Example
`
`OK<CR><LF>
`111.111.111.111<CR><LF>
`-----BEGIN X509 CERTIFICATE-----
`MIIChDCCAi4CAQIwDQYJKoZIhvcNAQEEBQAwgdMxCzAJBgNVBAYTAkpQMQ4wDAYD
`VQQIEwVUb2t5bzESMBAGA1UEBxMJQnVua3lvLWt1MSwwKgYDVQQKEyNGYWN1bHR5
`IG9mIE1lZGljaW5lLCBVbml2LiBvZiBUb2t5bzEvMC0GA1UECxMmRGVwLiBvZiBF
`cGlkZW1pb2xvZ3kgYW5kIEJpb3N0YXRpc3RpY3MxEjAQBgNVBAMTCUtpdWNoaSBD
`QTEtMCsGCSqGSIb3DQEJARYea2l1Y2hpQGVwaXN0YXQubS51LXRva3lvLmFjLmpw
`MB4XDTk2MDIxNDExNDc0MVoXDTk3MDIxMzExNDc0MVowgcUxCzAJBgNVBAYTAkpQ
`MQ4wDAYDVQQIEwVUb2t5bzEsMCoGA1UEChMjRmFjdWx0eSBvZiBNZWRpY2luZSwg
`VW5pdi4gb2YgVG9reW8xLzAtBgNVBAsTJkRlcC4gb2YgRXBpZGVtaW9sb2d5IGFu
`ZCBCaW9zdGF0aXN0aWNzMRgwFgYDVQQDEw9UYWthaGlybyBLaXVjaGkxLTArBgkq
`hkiG9w0BCQEWHmtpdWNoaUBlcGlzdGF0Lm0udS10b2t5by5hYy5qcDBcMA0GCSqG
`SIb3DQEBAQUAA0sAMEgCQQDPZy4ABrzjxLOjdfrZ8OQyVQnwIRbP0fyhAVT8D9qO
`3oSPeXnpNi1zjnn0B8tg2E4uf/HGIe6YhxsEIxqfOjsNAgMBAAEwDQYJKoZIhvcN
`AQEEBQADQQBcw17ia0W5Jyh+Sy2DJNoAl3OP0E9IM7CV1EiCuGOYgB+Swg9EicDK
`MrrLezvA4INeh1iGyTw0kOGEoSZpc0a9
`-----END X509 CERTIFICATE-----<CR><LF>
`ef23cd99<CR><LF>
`
`Page 23 of 42
`
`
`
`24
`
`C-HTTP-based communications (11)
`
` 6.
`
` 7.
` 8.
`
`C-HTTP
`response
`C-HTTP response
`C-HTTP request
`
`name
`
`N S
`
`SP
`CP
`
`SP
`
`CP
`SP
`
`CP information
`
`Connection acknowledged
`Object requested
`
`Example
`
`C-HTTP/0.7 OK<CR><LF>
`Response-Nonce: 8abd853f <CR><LF>
`Connection-ID: 6zdDfldfcZLj8Vli<CR><LF>
`
`Page 24 of 42
`
`
`
`25
`
`C-HTTP-based communications (12)
`
` 7.
` 8.
` 9.
`
`C-HTTP response
`C-HTTP request
`HTTP request
`
`SP
`CP
`SP
`
`CP
`SP
`O S
`
`Connection acknowledged
`Object requested
`Object requested
`
`Example
`
`Request C-HTTP/0.7<CR><LF>
`Request-Nonce: 8abd8541<CR><LF>
`Connection-ID: 6zdDfldfcZLj8Vli <CR><LF>
`<CR><LF>
`GET /index.html HTTP/1.0<CR><LF>
`
`Page 25 of 42
`
`
`
`26
`
`C-HTTP-based communications (13)
`
`C-HTTP request
` 8.
`HTTP request
` 9.
`10. HTTP response
`
`CP
`SP
`O S
`
`SP
`O S
`SP
`
`Object requested
`Object requested
`Object sent
`
`Example
`
`GET /index.html HTTP/1.0<CR><LF>
`
`Page 26 of 42
`
`
`
`27
`
`C-HTTP-based communications (14)
`
`HTTP request
` 9.
`10. HTTP response
`11. C-HTTP response
`
`SP
`O S
`SP
`
`O S
`SP
`CP
`
`Object requested
`Object sent
`Object sent
`
`Example
`
`HTTP/1.0 OK 200<CR><LF>
`Content-Type: text/html<CR><LF>
`Content-Length: 345<CR><LF>
`<CR><LF>
`<TITLE>Example</TITLE>
`<H1>This
`is
`an
`example HTML
`
`text.</H1>
`
`Page 27 of 42
`
`
`
`28
`
`C-HTTP-based communications (15)
`
`10. HTTP response
`11. C-HTTP response
`12. HTTP response
`
`O S
`SP
`CP
`
`SP
`CP
`UA
`
`Object sent
`Object sent
`Object sent
`
`Example
`
`Response C-HTTP/0.7 OK<CR><LF>
`Response-Nonce: 8abd8541<CR><LF>
`Connection-ID: 6zdDfldfcZLj8Vli <CR><LF>
`<CR><LF>
`HTTP/1.0 OK 200<CR><LF>
`Content-Type: text/html<CR><LF>
`Content-Length: 345<CR><LF>
`<CR><LF>
`<TITLE>Example</TITLE>
`<H1>This
`is
`an
`example HTML
`
`text.</H1>
`
`Page 28 of 42
`
`
`
`29
`
`C-HTTP-based communications (16)
`
`11. C-HTTP response
`12. HTTP response
`
`SP
`CP
`
`CP
`UA
`
`Object sent
`Object sent
`
`Example
`
`HTTP/1.0 OK 200<CR><LF>
`Content-Type: text/html<CR><LF>
`Content-Length: 345<CR><LF>
`<CR><LF>
`<TITLE>Example</TITLE>
`<H1>This
`is
`an
`example HTML
`
`text.</H1>
`
`Page 29 of 42
`
`
`
`30
`
`C-HTTP-based communications (17)
`
`31. HTTP request
`32. C-HTTP request
`33. C-HTTP response
`34. HTTP request
`
`UA
`CP
`SP
`CP
`
`CP
`SP
`CP
`O S
`
`Object not in closed network requested
`Request for disconnection
`Disconnection acknowledged
`Ordinary HTTP/1.0 request
`
`Example
`
`DISCONNECT C-HTTP/0.7<CR><LF>
`Request-Nonce: 8abd8554 <CR><LF>
`Connection-ID: 6zdDfldfcZLj8Vli <CR><LF>
`
`Page 30 of 42
`
`
`
`31
`
`C-HTTP-based communications (18)
`
`31. HTTP request
`32. C-HTTP request
`33. C-HTTP response
`34. HTTP request
`
`UA
`CP
`SP
`CP
`
`CP
`SP
`CP
`O S
`
`Object not in closed network requested
`Request for disconnection
`Disconnection acknowledged
`Ordinary HTTP/1.0 request
`
`Example
`
`C-HTTP/0.7 OK<CR><LF>
`Response-Nonce: 8abd8549 <CR><LF>
`Connection-ID: 6zdDfldfcZLj8Vli <CR><LF>
`
`Page 31 of 42
`
`
`
`32
`Discussion (1)
`
`Secure HTTP for medical use
`
`“Proxy-proxy” v.s. “End-to-end”
`
`1. All hospitals are protected using
`
`firewalls.
`
`Page 32 of 42
`
`
`
`33
`Discussion (2)
`
`Secure HTTP for medical use
`
`“Proxy-proxy” v.s. “End-to-end”
`
`2. Key management
`
`Personal risk
`
`Commercial service
`
`v.s.
`
`Institutional or patients’ risk
`
`Medical information exchange
`
`Page 33 of 42
`
`
`
`34
`Discussion (3)
`
`Secure HTTP for medical use
`
`“Proxy-proxy” v.s. “End-to-end”
`
`3. Unskilled and users
`
`Easy installation essential
`
`Page 34 of 42
`
`
`
`35
`Discussion (4)
`
`C-HTTP Name Service
`
`1. Efficient
`
`Provide name service and certificate (public
`
`key) simultaneously
`
`2. Secure as compared with DNS
`
`a. Client and server authentication
`
`C-HTTP name server not available to public
`
`b. Communication encrypted
`
`Server IP and port number not detected even if its
`
`resource name (“http://medical.server/index.html”) is
`
`made public.
`
`Page 35 of 42
`
`
`
`36
`Discussion (5)
`
`Disadvantage and limitations
`
`1. Current C-HTTP can accommodate up to only a
`
`few hundreds of proxies
`
`2. Addition of a new proxy cannot be automated.
`
`Page 36 of 42
`
`
`
`37
`
`Discussion (6)
`
`Relation to other secure HTTPs
`
`C-HTTP is NOT ALTERNATIVE, but can CO-EXIST
`
`with them
`
`C-HTTP
`
` Institutional level security
`
`Other end-to-end secure HTTPs
`
` Personal level security
`
`Page 37 of 42
`
`
`
`38
`
`Discussions (7)
`
`C-HTTP v.s. Secure HTTP compatible proxy servers
`
`1. Centralized network management
`
`2. C-HTTP name service
`
`Page 38 of 42
`
`
`
`39
`Discussion (8)
`
`Use in areas other than in medicine
`
`For example,
`
`Virtual closed network between
`
`headquarters and branches of
`
`a small or middle size private company
`
`Page 39 of 42
`
`
`
`40
`Concluding remarks (1)
`
`Closed network on the Internet ?
`
`Internet
`
`C-HTTP
`
`Participation
`
`Open
`
`No.
`
`of
`
`Huge
`
`Closed
`
`Limited
`
`computers
`
`Flexibility
`
`Yes
`
`No
`
`Standardization Necessary
`
`Not necessary
`
`Administration
`
`Distributed
`
`Centralized
`
`Page 40 of 42
`
`
`
`41
`Concluding remarks (2)
`
`More investments to the Internet, rather
`than the development of physical closed
`network.
`
`Page 41 of 42
`
`
`
`42
`
`How to introduce “status” to stateless HTTP
`
`Page 42 of 42
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
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.
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.
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
