RFC 2065:Domain Name System Security Extensions
RFC-Ref

encoding


Click on the red underlined text to get to the source

... An Appendix is provided that gives details of base 64 encoding which is used in the file representation of some RR's defined in this ...


... Appendix: Base 64 Encoding ...
... The following encoding technique is taken from RFC 1521(-> 2049draft | 2048(-> 4289 | 4288) | 2047draft | 2046draft | 2045draft) by N. Borenstein and N. Freed. It is reproduced here in an edited form for ...
... The encoding process represents 24-bit groups of input bits ...
... Table 1: The Base 64 Alphabet Value Encoding Value Encoding Value Encoding Value Encoding ...
... Value Encoding Value Encoding Value Encoding Value Encoding ...
... Value Encoding Value Encoding Value Encoding Value Encoding 0 A 17 R 34 i 51 z ...
... Encoding Value Encoding Value Encoding Value Encoding 0 A 17 R 34 i 51 z 1 B 18 S 35 j 52 0 ...
... Special processing is performed if fewer than 24 bits are available at the end of the data being encoded. A full encoding quantum is always completed at the end of a quantity. When fewer than 24 input bits ...
... end of the data is performed using the '=' character. Since all base 64 input is an integral number of octets, only the following cases can arise: (1) the final quantum of encoding input is an integral multiple of 24 bits; here, the final unit of encoded output will be ...
... 24 bits; here, the final unit of encoded output will be an integral multiple of 4 characters with no "=" padding, (2) the final quantum of encoding input is exactly 8 bits; here, the final unit of encoded output will be two characters followed by two "=" ...
... 8 bits; here, the final unit of encoded output will be two characters followed by two "=" padding characters, or (3) the final quantum of encoding input is exactly 16 bits; here, the final unit of encoded output will be three ...



Google
Web
RFC-Ref