Maybe this is a separate bug, but it's not clear what each "class-N" actually means. Instead of exposing the underlying protocol names, maybe these could use more dev friendly names and them mention their "class-n" equivalent in the spec? WDYT?