IP
Click on the red underlined text to get to the source
... created by Firewalls. We decided
to develop a process by which TCP/IP itself is carried over HTTP.
...
...
With this innovation anyone can use any new TCP/IP application
immediately without having to go through the laborious process of
dealing with Firewall ...
... dealing with Firewall access for the particular application. An
unintended byproduct of this proposal is that existing TCP/IP
applications can also be supported to better serve the users. With
FEP, the users can decide what applications they can run.
...
... proposal for MIME encoding of IP packets. We use the ubiquitous HTTP
protocol format. The IP datagram ...
... IP packets. We use the ubiquitous HTTP
protocol format. The IP datagram is carried in the message body of
the HTTP message ...
... firewall). Using a tunnel interface the TCP/IP
datagram is routed to our FEP software (2), which encodes the
...
... HTTP message. Then this message is sent via a
HTTP/TCP/IP tunnel (3) to host B on the normal HTTP ...
... tunnel to the FEP
software (5), which decodes the packet and creates a TCP/IP datagram
to insert into host ...
... |----------| |----------|
| IP | | IP | (6)
|----------| |----------|
| FEP dvr | (2) | FEP dvr | (5)
...
...
FEP allows either side to look like a client or server. Each TCP/IP
packet is sent as either a HTTP GET request or a response to a GET
...
...
The TCP/IP packet is encoded into the HTTP command in two (or
optionally three) steps. First, the IP packet ...
... TCP/IP packet is encoded into the HTTP command in two (or
optionally three) steps. First, the IP packet is encoded as the
message body in MIME ...
... packet header is parsed and encoded into new HTTP headers. Finally,
as an option, the IP header can also be encoded into new optional
HTTP headers. Encoding ...
... HTTP headers. Encoding the TCP and optionally the IP header is
strictly for human readability, since the entire IP datagram is
...
... TCP and optionally the IP header is
strictly for human readability, since the entire IP datagram is
encoded in the body part of the HTTP command.
...
... enclosed in square brackets. Representative options and their
encoding follow, other IP options follow the same form:
End of Options option: ["End of Options"]
...
...
IP_Ver - The IP Version number, encoded as an UTF-8 string. The
legitimate values for the string are "four", "five", and "six."
...
... legitimate values for the string are "four", "five", and "six."
The encapsulation of the fields in the IP header are defined in
this section if the value is "four", and in section 3.3 if the
value is "six". Encapsulations ...
... value is "six". Encapsulations for headers with IP_Ver value of
"five" will be developed if the right orders are received.
Encapsulations ...
... Encapsulations for headers with the IP_Ver value of "eight" are
empty. Implementations MUST be able to support arbitrary native
languages ...
... languages for these strings.
IP4_Hlen - The IP Internet Header Length field, it is encoded in the
...
...
IP4_SSN - The IP Identification field, encoded as an ASCII string
representing the value of the field.
...
... representing the value of the field.
IP4_Flags - The IP Flags, encoded as the set of 3 comma separated
ASCII strings: [{"Must Be Zero"}, {"May Fragment ...
... representing the common name for the protocol whose header
follows the IP header.
IP4_Checkit - The 16-bit ...
... enclosed in square brackets. Representative options and their
encoding follow, other IP options follow the same form:
End of Options option: ["End of Options"]
...