…s to take the value (as present in the header field, e.g., the base64-encoded [ RFC4648 ] version minus any leading and trailing whitespace) and concatenate this with the Globally Unique Identifier (GUID, [ RFC4122 ]) "258EAFA5-E914-47DA- 95CA-C5AB0DC85B11" in string form, which …

…as to take the value (as present in the header field, e.g., the base64-encoded [RFC4648] version minus any leading and trailing whitespace) and concatenate this with the Globally Unique Identifier (GUID, [RFC4122]) "258EAFA5-E914-47DA- 95CA-C5AB0DC85B11" in string form, which is …

…s to take the value (as present in the header field, e.g., the base64-encoded [ RFC4648 ] version minus any leading and trailing whitespace) and concatenate this with the Globally Unique Identifier (GUID, [ RFC4122 ]) "258EAFA5-E914-47DA- 95CA-C5AB0DC85B11" in string form, which …

…ng base32-string->bytevector nix-base32-string->bytevector %nix-base32-charset %rfc4648-base32-charset &invalid-base32-character invalid-base32-character? invalid-base32-character-value invalid-base32-character-string)) ;;; Commentary: ;;; ;;; A generic, customizable to convert b…

… is interpreted as a sequence of pairs of hex digits (base16; see Section 8 of [RFC4648] ) or a base64(url) string ( Section 4 or Section 5 of [RFC4648] ), respectively (as with the diagnostic notation in Section 6 of [RFC7049] ; cf. Appendix G.2 ); any whitespace present within …

…ter first encoding it into text using the "BASE64" encoding method defined in [ RFC4648 ]. Inline binary content SHOULD only be used in applications whose special circumstances demand that an iCalendar object be expressed as a single entity. A property containing inline binary co…

… mechanism name is concatenation of the string "GS2-" and the Base32 encoding [ RFC4648 ] (with an uppercase alphabet) of the first 55 bits of the binary SHA-1 Josefsson & Williams Standards Track [Page 5] RFC 5801 SASL GS2-* July 2010 hash [ FIPS.180-1.1995 ] string computed ove…

… is interpreted as a sequence of pairs of hex digits (base16; see Section 8 of [RFC4648]) or a base64(url) string (Section 4 or Section 5 of [RFC4648]), respectively (as with the diagnostic notation in Section 6 of [RFC7049]; cf. Appendix G.2); any whitespace present within the s…

…e identity assertion value is encoded as Base-64, as described in Section 4 of [RFC4648] . The procedures in this section are based on the assumption that the identity assertion of an endpoint is bound to the fingerprints of the endpoint. This does not preclude the definition of …

… is interpreted as a sequence of pairs of hex digits (base16; see Section 8 of [RFC4648]) or a base64(url) string (Section 4 or Section 5 of [RFC4648]), respectively (as with the diagnostic notation in Section 6 of [RFC7049]; cf. Appendix G.2); any whitespace present within the s…

… is interpreted as a sequence of pairs of hex digits (base16; see Section 8 of [RFC4648] ) or a base64(url) string ( Section 4 or Section 5 of [RFC4648] ), respectively (as with the diagnostic notation in Section 6 of [RFC7049] ; cf. Appendix G.2 ); any whitespace present within …

… is interpreted as a sequence of pairs of hex digits (base16; see Section 8 of [RFC4648] ) or a base64(url) string ( Section 4 or Section 5 of [RFC4648] ), respectively (as with the diagnostic notation in Section 6 of [RFC7049] ; cf. Appendix G.2 ); any whitespace present within …

…fter first encoding it into text using the "BASE64" encoding method defined in [RFC4648]. Inline binary content SHOULD only be used in applications whose special circumstances demand that an iCalendar object be expressed as a single entity. A property containing inline binary con…

…lue of the "version" key is 1, the UA MUST set this value to the base64-encoded RFC4648 serialized SignedCertificateTimestamp structure from Section 3.2 of [ RFC6962 . The base64 encoding is defined in Section 4 of [ RFC4648 . If the value of the "version" key is 2, the UA MUST s…

…lue of the "version" key is 1, the UA MUST set this value to the base64-encoded RFC4648 serialized SignedCertificateTimestamp structure from Section 3.2 of [ RFC6962 . The base64 encoding is defined in Section 4 of [ RFC4648 . If the value of the "version" key is 2, the UA MUST s…