Use kernel version number rather than package release
Use the kernel version number to indicate release rather than just package version. The RHEL kernel is already an amalgam of multiple upstream releases and the version should help reflect that. One way would be to ship RHEL7.0 on kernel 3.x and rebase 7.1 on 3.x.N patch release. It may be possible to even include all local RH patches in a 3.x.N stable release. It may also be palatable to clients to ship 3.y.N as a 7.x service pack release
Responses
I'm not sure what exactly you're asking for here; there seems to be two parts. First, you suggest what appears to be a 'kernel-rhel7-1.0' sort of naming - is that correct? What would be the use case for this?
Secondly, you suggest rebasing the kernel between releases; this would be a separate issue to the versioning, and brings with it other complications. Would you want this for hardware support? Bringing in additional bugfixes?
However, unless we start doing a full rebase of the kernel instead of selective backports as currently done, updating the version number doesn't really make it any more accurate. In your example, we may have backported the IPv6 tproxy support, but we didn't backport other things that were in 2.6.37, so that would be just as misleading.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
