Optimal engine for small lookup tables in MySQL
I answered a similar question in Aug 2011 : Which DBMS is good for super-fast reads and a simple data structure?
Since you are asking about MySQL and which storage engine. To be honest, it is hard to say because there are rare occasions when MyISAM can outperform InnoDB when it comes to SELECTs.
Here are some of my past posts on this controversy

Sep 20, 2011 : Best of MyISAM and InnoDB
May 03, 2012 : Which is faster, InnoDB or MyISAM?
Jul 05, 2012 : InnoDB vs MyISAM with many indexes
Sep 26, 2012 : Choosing MyISAM over InnoDB for these project requirements; and long term options

You might asking right now : Why would I ever favor MyISAM over InnoDB ?
Take a look at this diagram (created by Vadim Tkachenko, Percona CTO)

MyISAM will cache indexes and your table would have 2 indexes (PRIMARY KEY on id and an index of Name). On the other hand, InnoDB has too many moving parts to accommodate for, especially if the InnoDB Buffer Pool has to load and dismiss 16K pages periodically.
To be fair, you should do an experiment.

Go to my post What are the main differences between InnoDB and MyISAM?. Read it carefully.
Setup a server using MyISAM and all your tables using ROW_FORMAT=Fixed (See my post What is the performance impact of using CHAR vs VARCHAR on a fixed-size field?) and use a large key_buffer_size.
Setup another server using InnoDB and a large innodb_buffer_pool_size.
Add your data to both server and query them like crazy.

This will give you the best assessment for Storage Engine choice for your dataset.
GIVE IT A TRY !!!