…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…

…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…

…after 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…

…after 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…

… When base64 encoding and decoding are used, they MUST conform to Section 4 of [RFC4648] , which is the base64 method used in [ RFC5545 ]. Daboo, et al. Standards Track [Page 4] RFC 6321 xCal August 2011 One key difference in the formatting of values used in iCalendar and xCal is…

… base64 decoded. When base64 encoding is used, it MUST conform to Section 4 of [RFC4648] , which is the base64 method used in [ RFC5545 ]. One key difference in the formatting of values used in iCalendar and jCal is that in jCal, the specification uses date/time values aligned wi…

…ing the URL- and filename-safe character set defined in Section 5 of RFC 4648 [ RFC4648 ], with all trailing '=' characters omitted (as permitted by Section 3.2 ) and without the inclusion of any line breaks, whitespace, or other additional characters. Note that the base64url enc…

…d obtains the basic-credentials by encoding this octet sequence using Base64 ( [RFC4648], Section 4 ) into a sequence of US-ASCII characters ([ RFC0020 ]). The original definition of this authentication scheme failed to specify the character encoding scheme used to convert the us…

… When base64 encoding and decoding are used, they MUST conform to Section 4 of [RFC4648], which is the base64 method used in [RFC5545]. One key difference in the formatting of values used in iCalendar and xCal is that, in xCal, the specification uses date/time and UTC offset valu…

…ntent of the DNS request (as described in Section 6 ), encoded with base64url [ RFC4648 ]. Future specifications for new media types for DoH MUST define the variables used for URI Template processing with this protocol. DoH servers MUST implement both the POST and GET methods. Ho…

… file extension. PEM encoding is either the Base64 encoding, from Section 4 of [RFC4648] , of the DER-encoded EncryptedPrivateKeyInfo sandwiched between: -----BEGIN ENCRYPTED PRIVATE KEY----- -----END ENCRYPTED PRIVATE KEY----- or the Base64 encoding, see Section 4 of [RFC4648] ,…

…d obtains the basic-credentials by encoding this octet sequence using Base64 ( [RFC4648], Section 4 ) into a sequence of US-ASCII characters ([ RFC0020 ]). The original definition of this authentication scheme failed to specify the character encoding scheme used to convert the us…

… file extension. PEM encoding is either the Base64 encoding, from Section 4 of [RFC4648], of the DER-encoded EncryptedPrivateKeyInfo sandwiched between: -----BEGIN ENCRYPTED PRIVATE KEY----- -----END ENCRYPTED PRIVATE KEY----- or the Base64 encoding, see Section 4 of [RFC4648], o…

…d as an URN RFC8141 using the namespace identifier eris and the unpadded Base32 RFC4648 encoding of the read capability as namespace specific string, i.e: urn:eris:BASE32-READ-CAPABILITY For example the ERIS URN of the UTF-8 encoded string "Hello world!" (with block size 1KiB and…