[regext] Does section 3.7 of RFC 8748 forbid standard fees for non-standard (aka premium) domains?

[Ryan Jaeb <[e-mail]>]

Hi,

The end of section 3.7 says:

"
Servers that make use of this element MUST use a <fee:class> element
with the value "standard" for all objects that are subject to the
standard or default fee.
"

Does that forbid a response to a "check' command where
fee:class=standard alongside a fee:fee that is equal to the standard
fee for the TLD?  For example, if the standard renewal fee for a
domain is $22 USD, is a "check" command allowed to respond with
something like:

<extension>
   <fee:chkData
      xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0">
      <fee:currency>USD</fee:currency>
      <fee:cd avail="0">
         <fee:objID>example.com</fee:objID>
         <fee:class>premium</fee:class>
         ...
         <fee:command name="renew">
            <fee:period unit="y">1</fee:period>
            <fee:fee
               description="Renewal Fee"
               refundable="1"
               grace-period="P5D">22.00</fee:fee>
         </fee:command>
      </fee:cd>
   </fee:chkData>
</extension>

I have a domain where the "fee:class" has been changed from "standard"
to "premium" and I'm trying to understand what impact that has on me
and if it violates any applicable standards.  Any input would be
greatly appreciated.

Ryan