Tweet
Hey All!
I want to welcome you to this year’s TCP/IP Enabled Device Contest. Below you’ll find our newest revision on the contest rules. Last year many participants felt that the required documentation on the device was a bit much, so this year we’ve chosen to give those that do decide to do a write up, and even those that take it a step further and document their efforts on film, extra points in the final judging process. It is still required, however, to send a description of the device to us for pre-evaluation. As the rules state, there are certain projects that just wouldn’t be appropriate at the con. Those submissions can be sent to:
jerleung@uat.edu
Any questions about the contest or the rules below can be sent to the same address, or just throw up a post in this here thread. I encourage all those participating in the contest to talk with each other on the forums. You'll learn alot from your peers.
The contest will be hosted by DC480 this year. To find out more about our group check out:
www.dc480.org
Submissions can be sent by a link on that site and there is a page that has the same rules as below.
Each year our group has worked on a unique TCP/IP Enabled Device of our own, as an example device to display at our booth(not an eligible entry to the contest, but something to help us get excited about the contest as well). This has allowed us to go through the same brainstorming, concept drawing, parts ordering, and design steps that each of the contestants would have to go through. We’ve already begun work on this years device and in the coming weeks we should have a blog up for those interested to be able to follow our progress.
From here, I just want to say good luck, start brainstorming, and get those submissions in!
Now on to the rules…
------------------------------------------------------------------------------------------------------------
Proposed Simplified Rules for Homebrew TCP/IP appliance contest for Defcon 14
Version 0.5 - Last updated 12/28/05 7:41 AM MST
What the contest is:
Net-enabled devices have become more of a reality than fiction as computing power has increased and costs have decreased. Right now the industry is working on net enabling your home whether it’s your television or your refrigerator. The purpose of this contest is to think outside of the box that the industry is thinking and create TCP/IP enabled devices that are fresh, new, cool, and literally way outside of the box.
There are two categories of devices in this contest.
The first category is TCP/IP embedded devices. These are stand alone devices which simply need to be plugged into a hub or switch. The device must host a TCP/IP aware service which someone can control and/or query a status from over a LAN or the internet and have it report back to the remote client that is controlling/querying it.
The second category is TCP/IP enabled peripherals. These are devices which must be connected to a host system such as a laptop or desktop computer which hosts the TCP/IP enabled service for the device. The host system must be able to communicate with the attached device in order to control it and/or query its status over a LAN or the internet and report back to the remote client which is controlling/querying it.
Devices in each category will be judged on originality, functionality, best value for actual cost and the coolness factor.
Three main awards will be available. One for Best TCP/IP embedded device, Best TCP/IP enabled peripheral, and the Hax0r’s Choice Award where your peers vote for what they think is the most uber elite device in the entire contest . Be sure to expect some extra goodies for participating.
Contest Rules:
1. All entries (which these rules shall refer to as "TCP/IP enabled device", “TCP/IP embedded device” or just "device") must be a homebrewed creation in regards to TCP/IP enabling the device. Slapping a HP Jet Direct card on a printer to TCP/IP enable it is not considered to be a homebrewed creation.
2. Entries must not be something which is commercially available. Hybrids of a commercially available item may be considered if you hacked on lots of additional functionality, but its best to create your own device rather than to improve on an existing one.
3. Entries must not be in the service of a commercial, educational, or governmental entity at any time prior to the contest. Bringing your work or school's existing TCP/IP enabled soda vending machine is not allowed. The idea is to create something specifically for this contest. However, if your entry is a TCP/IP enabled robot which is also entering in the Robot Warez Contest, it will be allowed as long as it’s still functioning when we do our judging for this contest.
Team Rules and Responsibilities:
1. Teams must submit an email detailing their intended entry as well as a list of team members. Once you are approved you may begin construction of your entry. We're trying to avoid too many last minute/surprise entries. We also want to make sure your entry fits within the intended scope of this contest which is why we ask to pre-approve your project. We wouldn’t want you to build something that would end up being disqualified for one reason or another.
2. Teams should keep some sort of development log detailing design, construction and cost of their device. Development logs are to be submitted at the same time that your final product is submitted for judging and peer review and will help in the judging process. Documentation can be submitted by email or in print out form to ensure that your word document doesn't get lost or mangled in some fashion. Additional documentation in the form of a video log or presentation material will be given extra “cool” credits if it's well made and presentable to the audience. So making a brief behind the scenes video could earn you some extra points.
3. Each team will have their device on display to demonstrate their device and garner votes from your fellow Defcon attendees for the Hax0r’s Choice Award. A team member will need to be on present to demonstrate the device during the allotted demonstration time. Those teams that demonstrate their devices will earn extra points.
Device Construction Rules:
1. Teams may use commercial components and kits to create their devices but be aware that the less home brew your device is, the lower it will score.
2. Devices which may cause harm to an individual or is of a sexual nature are prohibited. Sorry. No battle bots, TCP/IP enabled flame throwers, EM Pulse machines, or TCP/IP enabled sex toys of any kind (because we could get into trouble if you “demonstrate” them for your peers.)
Judging:
1. TCP/IP embedded devices must demonstrate in real time that it hosts a TCP/IP service which can be accessed remotely by a client to control the device and/or query its status.
2. TCP/IP enabled peripherals must demonstrate in real time that it can be controlled by a host device upon which a TCP/IP service is activated to solely control and/or query the status of the device.
3. Each function of the device will be tested to ensure accuracy in performing its intended purpose as documented in the original contest submission.
4. Points will be deducted if an intended function of the device fails to function or functions inaccurately.
Example: If your device has 4 functions plus a status query function (5 functions in total) and 1 of the functions fail and it returns an inaccurate status report, you will only receive credit for the remaining 3 working functions.
5. Entries whose TCP/IP components are assembled from a pre-packaged kit will generally score lower than someone who homebrewed their components. However if you take an existing kit and hack extra features onto it, you will definitely earn extra “cool” points which might help you during the judging.
6. Finally, If your device has been pre-approved and your team has been working on the project for some time but just couldn’t get it finished in time, bring what you have in anyways. You will still have a chance to grab some points, and the judges as well as your fellow contestants will be interested in seeing what you were going for and how far you got.
Submissions and Questions:
1. The contact for this contest is UberSchnitzel (jerleung@uat.edu). Please direct questions, comments, concerns, or submissions to this email address.
2. This contest is sponsored by DC480 in Tempe, AZ. Check out their website at www.dc480.org
I want to welcome you to this year’s TCP/IP Enabled Device Contest. Below you’ll find our newest revision on the contest rules. Last year many participants felt that the required documentation on the device was a bit much, so this year we’ve chosen to give those that do decide to do a write up, and even those that take it a step further and document their efforts on film, extra points in the final judging process. It is still required, however, to send a description of the device to us for pre-evaluation. As the rules state, there are certain projects that just wouldn’t be appropriate at the con. Those submissions can be sent to:
jerleung@uat.edu
Any questions about the contest or the rules below can be sent to the same address, or just throw up a post in this here thread. I encourage all those participating in the contest to talk with each other on the forums. You'll learn alot from your peers.
The contest will be hosted by DC480 this year. To find out more about our group check out:
www.dc480.org
Submissions can be sent by a link on that site and there is a page that has the same rules as below.
Each year our group has worked on a unique TCP/IP Enabled Device of our own, as an example device to display at our booth(not an eligible entry to the contest, but something to help us get excited about the contest as well). This has allowed us to go through the same brainstorming, concept drawing, parts ordering, and design steps that each of the contestants would have to go through. We’ve already begun work on this years device and in the coming weeks we should have a blog up for those interested to be able to follow our progress.
From here, I just want to say good luck, start brainstorming, and get those submissions in!
Now on to the rules…
------------------------------------------------------------------------------------------------------------
Proposed Simplified Rules for Homebrew TCP/IP appliance contest for Defcon 14
Version 0.5 - Last updated 12/28/05 7:41 AM MST
What the contest is:
Net-enabled devices have become more of a reality than fiction as computing power has increased and costs have decreased. Right now the industry is working on net enabling your home whether it’s your television or your refrigerator. The purpose of this contest is to think outside of the box that the industry is thinking and create TCP/IP enabled devices that are fresh, new, cool, and literally way outside of the box.
There are two categories of devices in this contest.
The first category is TCP/IP embedded devices. These are stand alone devices which simply need to be plugged into a hub or switch. The device must host a TCP/IP aware service which someone can control and/or query a status from over a LAN or the internet and have it report back to the remote client that is controlling/querying it.
The second category is TCP/IP enabled peripherals. These are devices which must be connected to a host system such as a laptop or desktop computer which hosts the TCP/IP enabled service for the device. The host system must be able to communicate with the attached device in order to control it and/or query its status over a LAN or the internet and report back to the remote client which is controlling/querying it.
Devices in each category will be judged on originality, functionality, best value for actual cost and the coolness factor.
Three main awards will be available. One for Best TCP/IP embedded device, Best TCP/IP enabled peripheral, and the Hax0r’s Choice Award where your peers vote for what they think is the most uber elite device in the entire contest . Be sure to expect some extra goodies for participating.
Contest Rules:
1. All entries (which these rules shall refer to as "TCP/IP enabled device", “TCP/IP embedded device” or just "device") must be a homebrewed creation in regards to TCP/IP enabling the device. Slapping a HP Jet Direct card on a printer to TCP/IP enable it is not considered to be a homebrewed creation.
2. Entries must not be something which is commercially available. Hybrids of a commercially available item may be considered if you hacked on lots of additional functionality, but its best to create your own device rather than to improve on an existing one.
3. Entries must not be in the service of a commercial, educational, or governmental entity at any time prior to the contest. Bringing your work or school's existing TCP/IP enabled soda vending machine is not allowed. The idea is to create something specifically for this contest. However, if your entry is a TCP/IP enabled robot which is also entering in the Robot Warez Contest, it will be allowed as long as it’s still functioning when we do our judging for this contest.
Team Rules and Responsibilities:
1. Teams must submit an email detailing their intended entry as well as a list of team members. Once you are approved you may begin construction of your entry. We're trying to avoid too many last minute/surprise entries. We also want to make sure your entry fits within the intended scope of this contest which is why we ask to pre-approve your project. We wouldn’t want you to build something that would end up being disqualified for one reason or another.
2. Teams should keep some sort of development log detailing design, construction and cost of their device. Development logs are to be submitted at the same time that your final product is submitted for judging and peer review and will help in the judging process. Documentation can be submitted by email or in print out form to ensure that your word document doesn't get lost or mangled in some fashion. Additional documentation in the form of a video log or presentation material will be given extra “cool” credits if it's well made and presentable to the audience. So making a brief behind the scenes video could earn you some extra points.
3. Each team will have their device on display to demonstrate their device and garner votes from your fellow Defcon attendees for the Hax0r’s Choice Award. A team member will need to be on present to demonstrate the device during the allotted demonstration time. Those teams that demonstrate their devices will earn extra points.
Device Construction Rules:
1. Teams may use commercial components and kits to create their devices but be aware that the less home brew your device is, the lower it will score.
2. Devices which may cause harm to an individual or is of a sexual nature are prohibited. Sorry. No battle bots, TCP/IP enabled flame throwers, EM Pulse machines, or TCP/IP enabled sex toys of any kind (because we could get into trouble if you “demonstrate” them for your peers.)
Judging:
1. TCP/IP embedded devices must demonstrate in real time that it hosts a TCP/IP service which can be accessed remotely by a client to control the device and/or query its status.
2. TCP/IP enabled peripherals must demonstrate in real time that it can be controlled by a host device upon which a TCP/IP service is activated to solely control and/or query the status of the device.
3. Each function of the device will be tested to ensure accuracy in performing its intended purpose as documented in the original contest submission.
4. Points will be deducted if an intended function of the device fails to function or functions inaccurately.
Example: If your device has 4 functions plus a status query function (5 functions in total) and 1 of the functions fail and it returns an inaccurate status report, you will only receive credit for the remaining 3 working functions.
5. Entries whose TCP/IP components are assembled from a pre-packaged kit will generally score lower than someone who homebrewed their components. However if you take an existing kit and hack extra features onto it, you will definitely earn extra “cool” points which might help you during the judging.
6. Finally, If your device has been pre-approved and your team has been working on the project for some time but just couldn’t get it finished in time, bring what you have in anyways. You will still have a chance to grab some points, and the judges as well as your fellow contestants will be interested in seeing what you were going for and how far you got.
Submissions and Questions:
1. The contact for this contest is UberSchnitzel (jerleung@uat.edu). Please direct questions, comments, concerns, or submissions to this email address.
2. This contest is sponsored by DC480 in Tempe, AZ. Check out their website at www.dc480.org