This Annex contains a self-contained set of ABNF rules, comprising the re-used rules from IETF RFCs, and the rules defined by the 3GPP custom headers defined in this specification (see clause 5.2.3). This grammar may be used as input to existing tools to help implementations to parse 3GPP custom headers. Given that this Annex is included in relation to ABNF tooling, the following aspects should be observed:

• The "list extension" rule definedin Section 5.6.1 of RFC 9110 is typically not supported by ABNF tooling, so rules included this syntax have been re-written with their equivalent syntax:
  is re-written as:
• The ABNF specification defined in RFC 5234 does not describe how to evaluate the "alternative" operator (i.e., "Rule1 / Rule2"), when both rules match, but one of them have a "longer" match than the other. Based on existing ABNF rules in different RFCs, it seems that the approach is to apply a "longest" match (see, for example, the "dec-octet" rule in RFC 3986); however, most existing ABNF tools apply a "left-most" match. When this occurs, the rules in this Annex have been re-written by placing the rule with a longest match on the left side, and the shortest match on the right side of the alternative operator.
  For example:
  is re-written as:
• The rules containing prose text ("<…>") are typically not supported by ABNF tooling, so the rule in RFC 3986:
  is re-written as:
• Some rules in RFC 9110 ("day", "month", "year") contain the same rule names as in RFC 5322, so these clashing rule names in RFC 9110 have been renamed as "day-rfc9110", "month-rfc9110" and "year-rfc9110" respectively.