This contest is closed.
Patexia is looking for descriptions of a media proxy router sitting outside a firewall-protected network to securely forward data packets from an unsecured network, such as the Internet, across the firewall, and to a destination inside the protected network.
Submitted documents describing this system must be:
- filed or published before 08/17/2002
not on the known references list
The entire submission must describe a media proxy router where:
- the router sits outside the firewall-protected network
- can request the firewall to create a forwarding port, or “pinhole”
- store the forwarding port or pinhole address on the router itself
replace the address header with the pinhole address for of any packet heading into the protected network from an unsecured network, such as the Internet
Pinhole: is a communication port, also referred to as an IP port, that the network entity designates for sending information packets out of the network and also receiving information packets (e.g. responses) into the network during a communication session. See the ‘323 patent, col. 3, ll. 14-18. Typically the address of the pinhole is stored in the media proxy router. The advantage of this arrangement is that it allows a firewall to open temporarily to permit only desired communications to pass through the firewall (since only those information packets will have the address of the pinhole) while maintaining the blockage of unwanted communications.
A media proxy router: is a network entity that performs IP address translation on signaling/media information packets. This is the definition provided in the specification of the ‘323 patent at column 1, lines 47-49.
An information packet: means a packet containing data.
A first destination address designation: means a label designating a first address to which data can be sent. The first destination address designation is not limited to the address of the Media Proxy Router, it is broader. The Soft Switch and the Media Proxy Router do not have to communicate over the internet (see, e.g., the ‘323 patent at col. 6, lines 61-64 and claim 15).
Correlate the first destination address designation with a second address designation using a data element stored in the media proxy router: means to establish relationships between addresses (viz. the first destination address and the second address) based on an element stored at the media proxy router.
An address of a pinhole in the firewall: means the location (i.e. address in the network) of a pinhole in the firewall.
|1||Is the reference either a US patent filed, a foreign patent published, or a non-patent document published before August 17th, 2002?||T/F|
|2||Does the reference show a media proxy router that (1) sits outside a firewall-protected network to (2) securely forward data packets from an unsecured network, such as the Internet, into the protected network?||50|
|3||Does the reference show the media proxy router has a network interface that is directly connected to the firewall to signal the creation of a pinhole address (or forwarding port) to allow for secure data transmissions across the firewall?||10|
|4||(3a) Does the reference further show the network interface receives a signal back from the firewall with the address for the pinhole communication port?||5|
|5||Does the reference show that when a data packet arrives at the media proxy router from an unsecured network, such as the Internet, the media proxy router (1) locally looks up the address for the pinhole port, (2) overwrites the packet address header with the pinhole port address, and (3) transmits the modified packet through the network interface across the firewall to its destination?||35|
This is a Prior Art Search contest aimed at determining if a patent idea was known and publicly available before a patent was filed.
+5 bonus points will be awarded for non-patent literature and for foreign language references.
This contest will close on Sunday, July 26th, 2015 at 11:59 PM PST.
Please review the Contest Rules. For more information on how to submit to this Contest type, please read the Intro to Prior Art Search page.
- All work must be original and prepared by a single author
- Maximum of one entry per person allowed
- Maximum length of 1,500 words
- Entries must be in English
- Ideas should be clearly expressed at a college-educated, non-expert level
- All submissions are subject to Patexia's contest legal terms
- Failure to follow these rules may lead to disqualification from the contest
- , Firewall Requirements for Securing VoIP-Real Time Mixed Media (RTMM) firewalls can secure both Jun. 13 2003; www.cConvergence.com
- , "Foster B ""RFC 3064: MGCP CAS Packages;"" (Feb. 2001); Internet Society."
- , "Greena Mark; ""Firewall and Proxy Server HOWTO;"" (Feb. 26 2000); ispbs.hostplus.net/linux/Firewall-HOWTO.html."
- , "Hockmuth et al; ""Firewall limits vex VoIP users;"" (Jul. 8 2002); Network World."
- , "Jacobs; S; ""Internet Draft: MGCP MEGACO and SIP VoIP Signalling Protocol Security Requirements;"" (Oct. 2002); Internet Society."
- , "Mercer et al; ""Internet Draft: H.323 Firewall Control Interface;"" (Nov. 1998)."
- , "Paul Drew and Chris Gallon; ""Next-Generation VoIP Network Architecture;"" (Mar. 2003); www.msforum.com."
- , "Rosenberg J. et al. ""RFC 3261: Session Initiation Protocol;"" (Jun. 2002); Internet Society."
- , Rosenberg J; Internet Draft: SIP Traversal through Residential and Enterprise NATs and Firewalls; (Mar. 2 2001); IEFT.
- , Jonathan Rosenberg Joel Weinberger Christian Huitema & Rohan Mahy Traversal Using Relay NAT (TURN) November 14 2001
- http://web.archive.org/web/20020124103457/ http://www.ietf.org
- http://web.archive.org/web/ 20010413091132/http://ietf.org/overview.html
- http://web.archive.org/web/ 20011205080424/http://www.ietf.org/ID.html
- http://web.archive.org/ web/20011205075037/http://www.ietf.org/1id-abstracts.html
- http://web.archive.org/web/20011223005932/http://www.ietf.org/ids.by.w g.none.html
- http://web.archive.org/web/20010413090316/ http://ietf.org/maillist.html
- , "Tyson; Jeff; ""How Firewalls Work;"" 2003; www.howstuffworks.com."
- http://web.archive.org/web/20011012035130/http://www.ietf.org/html.cha rters/wg-dir.html
- http://web.archive.org/web/20011004061031/http://www.ietf.org/html.cha rters/midcom-charter.html
- http://web.archive.org/ web/20011226223325/http://www.jdrosen.net/midcom_turn.html
- http://web.archive.org/ web/20020616064555/http://jdrosen.net/midcom_turn.html
- http://web.archive.org/ web/20020910200154/http://www.jdrosen.net/midcom_turn.html
- http://web.archive.org/ web/20011128155647/http://www.jdrosen.net/
- http://web.archive.org/ web/20011215064857/http://www.jdrosen.net/ietf.html
- http://www.ietf.org/mail-archive/web/midcom/ current/msg01629.html
- , Elizabeth D. Zwicky et al. Building Internet Firewalls 21-23 (2nd ed.2000)
- , Henning Schulzrinne et al. RTP: A Transport Protocol for Real-Time Applications January 1996 (“RFC1889”)
- , Newton’s Telecom Dictionary 253-254 (11th ed. 1996)
- , Andrew S. Tanenbaum Computer Networks 410-412 (3rd ed. 1996)