Pre-Grant Publication Number: 20080162919
Track the progress of public participation in the review of this pending patent application, and view
application details. The menu on the right will help you navigate this patent application. Subscribe to
the community enables you to receive updates on this application via email so that you can easly follow recent activity.
LATEST PRIOR ART
| Date | Title | Reviewer |
|---|---|---|
| 07/16/08 | Using alternative protocols for boot image delivery | Igor Naumov |
| 07/16/08 | Preboot Execution Environment (PXE) Specification Version 2.1 | Daniel Berlin |
DISCUSSION
Kid Stevens (2 months ago)
At KP Corporation in Denver I managed multiple odd systems from DOS to Macintosh. On the public server I set Boot images for the machines. Each machine that could receive an email would get a script that pointed to the latest boot image for that machine type. Opening the email would then execute the script in DOS and Windows which would write the boot info into the OS. On the Macintoshes the script would have to be manually executed by the user and this would point the machine to the right image for the next boot.
In reality this is not a new idea in any form as email is too slow to move large images. The system would still relies on some other network protocol to finish the job. In my case it was aliases pointing the OS folder to the network OS folder.Igor Naumov (2 months ago)
The essence of this application is the replacement of the TFTP protocol usually used in network boot process with another protocol, which the inventor refers to as "messaging".
Almost all of the other steps involved in the claims (like selecting a boot image server, verifying a local boot image, etc) are standard features of DHCP, PXE and BIOS.
Using alternative protocols in network boot process has been done before (e.g. see booting over HTTP at http://etherboot.org/wiki/httpboot ).
In my opinion, the only original claim of the application is changing TFTP protocol to another protocol like SMTP (which may not have been done before due to obvious performance reasons).
The main problem with the application is that it fails to define which specific "messaging" protocols are covered by the claims. In the absence of a definition of "messaging" protocols the application becomes too broad by covering any and all present and future transfer protocol that may be used in delivery of a boot image. Technically any network protocol can be considered as "messaging" since it is used for delivery of "messages" (which may be UDP or TCP packets).
PEER TO PATENT ACTIVITY
All
Annotate and Evaluate Prior Art
7 prior art ratings
2 citations
7 prior art ratings
2 citations
Discuss Patent Applications
4 comments posted
Size of Community: 7
4 comments posted
Size of Community: 7
Upload + Explain Prior Art
2 submitted
2 submitted
Research Prior Art
0 research notes
0 research notes
WHAT IS THIS APPLICATION ABOUT
17 days left
