Arghh... thats what an author like me deserves to get for not reading every bloody formal language RFC line by line *sigh*.
Meaning i will remove the definition HEXLC and just use RFC5234 HEXDIG even though i will keep lower case. Add a comment about preference to encode lower case but need to absorb any case mix. Thanks, Barry! Toerless On Thu, Aug 13, 2020 at 08:33:28AM -0400, Barry Leiba wrote: > > [ section 6.1.2 ] > > > > * The example "fd89b714F3db00000200000064000000" contains an uppercase "F" > > and therefore doesn't conform to 32HEXLC, I believe. > > HEXLC = DIGIT / "a" / "b" / "c" / "d" / "e" / "f" > > ABNF [RFC5234] is case-insensitive, so "f" in the grammar allows both > "f" and "F" in practice. So the example does conform to the grammar. > That said, it's probably best to make the example internally > consistent and use all lower case letters, even though mixing them is > legit. > > Barry -- --- [email protected] _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
