…btags are distinguished and separated from one another by a hyphen ("-", ABNF [ RFC4234 ] %x2D). A language tag consists of a "primary language" subtag and a (possibly empty) series of subsequent subtags, each of which refines or narrows the range of languages identified by the o…

…isible (printing) characters where WSP, ALPHA, DIGIT, and VCHAR are defined in [RFC4234]. 9.2. SRTP "Crypto" Attribute Grammar This section provides an Augmented BNF [RFC4234] grammar for the SRTP-specific use of the SDP crypto attribute: crypto-suite = srtp-crypto-suite key-meth…

…phens, and/or underscores. In the following Augmented Backus-Naur Form (ABNF) [ RFC4234 ] grammar, the <sasl-mech> production defines the syntax of a SASL mechanism name. sasl-mech = 1*20mech-char mech-char = UPPER-ALPHA / DIGIT / HYPHEN / UNDERSCORE ; mech-char is restricted to …

…TP/1.1 [ RFC2616 ] and later [ RFC3066 ]. It is defined by the following ABNF [ RFC4234 ]: language-range = (1*8ALPHA *("-" 1*8alphanum)) / "*" alphanum = ALPHA / DIGIT A basic language range differs from the language tags defined in [ RFC4646 ] only in that there is no requireme…

…TP/1.1 [ RFC2616 ] and later [ RFC3066 ]. It is defined by the following ABNF [ RFC4234 ]: language-range = (1*8ALPHA *("-" 1*8alphanum)) / "*" alphanum = ALPHA / DIGIT A basic language range differs from the language tags defined in RFC4646 ] only in that there is no requirement…

…by HTTP/1.1 [RFC2616] and later [RFC3066]. It is defined by the following ABNF [RFC4234]: language-range = (1*8ALPHA *("-" 1*8alphanum)) / "*" alphanum = ALPHA / DIGIT A basic language range differs from the language tags defined in [RFC4646] only in that there is no requirement …

…TP/1.1 [ RFC2616 ] and later [ RFC3066 ]. It is defined by the following ABNF [ RFC4234 ]: language-range = (1*8ALPHA *("-" 1*8alphanum)) / "*" alphanum = ALPHA / DIGIT A basic language range differs from the language tags defined in RFC4646 ] only in that there is no requirement…

…by HTTP/1.1 [RFC2616] and later [RFC3066]. It is defined by the following ABNF [RFC4234]: language-range = (1*8ALPHA *("-" 1*8alphanum)) / "*" alphanum = ALPHA / DIGIT A basic language range differs from the language tags defined in [RFC4646] only in that there is no requirement …

…TP/1.1 [ RFC2616 ] and later [ RFC3066 ]. It is defined by the following ABNF [ RFC4234 ]: language-range = (1*8ALPHA *("-" 1*8alphanum)) / "*" alphanum = ALPHA / DIGIT A basic language range differs from the language tags defined in RFC4646 ] only in that there is no requirement…

… The grammatical rules in this document are to be interpreted as described in [ RFC4234 ]. 2 . JSON Grammar A JSON text is a sequence of tokens. The set of tokens includes six structural characters, strings, numbers, and three literal names. A JSON text is a serialized object or …

…FC2119 ]. This specification makes use of the Augmented Backus-Naur Form (ABNF) RFC4234 ] notation, including the core rules defined in Appendix A of that document. Freed & Klensin Best Current Practice [Page 3] RFC 4288 Media Type Registration December 2005 . Media Type Registra…

…cument title. September 25, 2005 Update BIND reference. October 05, 2005 Update RFC4234 reference. October 22, 2005 Author's address update. February 12, 2006 Update BIND reference. March 16, 2006 Add typed literals to QSD. August 20, 2006 Update XML reference. August 28, 2006 Ad…

… The grammatical rules in this document are to be interpreted as described in [ RFC4234 ]. . JSON Grammar A JSON text is a sequence of tokens. The set of tokens includes six structural characters, strings, numbers, and three literal names. A JSON text is a serialized object or ar…

… The grammatical rules in this document are to be interpreted as described in [ RFC4234 ]. . JSON Grammar A JSON text is a sequence of tokens. The set of tokens includes six structural characters, strings, numbers, and three literal names. A JSON text is a serialized object or ar…

…0-02 Verifier Name: Russ Housley Date Verified: 2010-04-12 Section 5.5 says: | [RFC4234] progressed from Proposed Standard through Draft Standard | to Standard and is obsoleted by [RFC5234]. It should say: | [RFC4234] progressed from Proposed Standard to Draft Standard and | then…