@NoCache should not set a "public" tag

When we use the @NoCache annotation on a @GET resource, we see in our clients:

Cache-control: public, no-cache

from the spec http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.1
we see:

• public Indicates that the response MAY be cached by any cache
• no-cache ... a cache MUST NOT use the response to satisfy a
  subsequent request without successful revalidation with the origin
  server.

So, what is the meaning of "public, no-cache"?

Thanks,

Matthew