Thanks, this is where I've been looking and confusing myself over the nature of rules that are themselves defined by strings. Got it now. Luckily it's the simplest bug in the world to fix. Cheers Steve
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Iñaki Baz Castillo Sent: 02 February 2010 12:15 To: [email protected] Subject: Re: [Sip-implementors] Lower case hex in escaped chars El Martes, 2 de Febrero de 2010, Stephen Paterson escribió: > Thanks Inaki, > Any reference for this? Read the RFC about ABNF grammar: RFC 2234. Look for the word "case": ---------------------------- 2. RULE DEFINITION 2.1 Rule Naming The name of a rule is simply the name itself; that is, a sequence of characters, beginning with an alphabetic character, and followed by a combination of alphabetics, digits and hyphens (dashes). NOTE: Rule names are case-insensitive [...] page 4: Literal text strings are interpreted as a concatenated set of printable characters. NOTE: ABNF strings are case-insensitive and the character set for these strings is us-ascii. Hence: rulename = "abc" and: rulename = "aBc" will match "abc", "Abc", "aBc", "abC", "ABc", "aBC", "AbC" and "ABC". To specify a rule which IS case SENSITIVE, specify the characters individually. For example: rulename = %d97 %d98 %d99 or rulename = %d97.98.99 will match only the string which comprises only lowercased characters, abc. -------------------------------------- For example, SIP METHOD's are defined as case *sensitive* in this way (RFC 3261): INVITEm = %x49.4E.56.49.54.45 ; INVITE in caps -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
