### Table 3: Security Levels and Encrypted Data Security Encrypted Field

1994

"... In PAGE 4: ... Amount of data encrypted depends on the selected se- curity level. Table3 shows correspondence between the security levels and encrypted fields of a datagram. Boxes with 14 denotes encrypted data, and (auth) denotes that the field is encrypted into an appropriate authenticator format.... ..."

Cited by 2

### Table 3. Application to RSA: Encryption

1999

"... In PAGE 7: ... 6.2 Application to RSA Table3 shows our results from the tables above, applied to RSA. The encryption time is calculated for the F4 expo- nent, requiring 2 19(n + 4) clock cycles.... ..."

Cited by 26

### Table 3. Application to RSA: Encryption

1999

"... In PAGE 7: ... 6.2 Application to RSA Table3 shows our results from the tables above, applied to RSA. The encryption time is calculated for the F 4 expo- nent, requiring 2 #01 19#28n +4#29clock cycles.... ..."

Cited by 26

### Table 2 Uniform encryption table.

"... In PAGE 6: ...Trivial, with geometric series properties applied to the terms containing A, and Bj. the rows from 0 to n - 3 of the matrix such that for any given A,, B,, Table2 will produce the right encryption for the added bit positions. Theorem 3 The encryption can be transformed into the following equivalence: 2 [ (Aj .... ..."

### Table 3. Encryption Rates for AES

2005

"... In PAGE 11: ... The rates for values of n 300 varied by less than 2% and the rates across all val- ues of n varied by at most 8%. The results for AES-GL in Table3 are the averages over n 300 when a single pixel component and all of the RGBA pixel components are utilized. The corresponding decryption rates for the C and OpenGL implementations will be slightly lower than the encryption rates due to a small difference in the number of operations in the decryption function compared to that of the encryption function.... ..."

Cited by 9

### Table 3. Encryption Rates for AES

2005

"... In PAGE 11: ... The rates for values of a27 a0 a0 a1 a1 varied by less than 2% and the rates across all val- ues of a27 varied by at most 8%. The results for AES-GL in Table3 are the averages over a27 a0 a0 a1 a1 when a single pixel component and all of the RGBA pixel components are utilized. The corresponding decryption rates for the a0 and OpenGL implementations will be slightly lower than the encryption rates due to a small difference in the number of operations in the decryption function compared to that of the encryption function.... ..."

Cited by 9

### Table 3: Encryption current consumptions

2005

"... In PAGE 4: ... The Rx + Tx application contains twice as many wake + sleep operations per sec- ond as the Rx application. Table3 shows the Rx+Tx application with the introduc- tion of encryption, using values measured by P. Ganesan et al.... ..."

Cited by 3

### Table 2. Encryption speeds, ranked

"... In PAGE 8: ... A lesser amount of data has been accumulated for 64 bit architectures, but not much detailed information on 8 bit and/or hard- ware performance is available at this point (hopefully, Round 2 will shed more light on the latter platforms). Table 1 in the Appendix summarizes some information received from the public on speeds; Table2 reformulates Table 1 by giving relative ranks. NIST has also accumu- lated information on speeds by testing the ANSI C and Java supplied by the algorithm submitters [33] and [34].... In PAGE 22: ...Journal of Research of the National Institute of Standards and Technology Table2 provides the ranking of the encryption speeds of the candidates for encrypting one 128 bit block with a 128 bit key. Note that a ranking of 1 denotes the fastest encryption speed.... ..."

### Table 14: Default Symmetric Encryption

"... In PAGE 6: ... Of those that supported both, 5469 (29 percent of all servers) chose MD5. As shown in Table14 , none of the servers chose RC2 from the available symmetric encryption algorithms. However, 657 servers that support AES (namely about 6 percent of those that support AES) did not choose AES by default.... ..."

### Table 1. Encryption speeds of the candidates

"... In PAGE 8: ... A lesser amount of data has been accumulated for 64 bit architectures, but not much detailed information on 8 bit and/or hard- ware performance is available at this point (hopefully, Round 2 will shed more light on the latter platforms). Table1 in the Appendix summarizes some information received from the public on speeds; Table 2 reformulates Table 1 by giving relative ranks. NIST has also accumu- lated information on speeds by testing the ANSI C and Java supplied by the algorithm submitters [33] and [34].... In PAGE 8: ... A lesser amount of data has been accumulated for 64 bit architectures, but not much detailed information on 8 bit and/or hard- ware performance is available at this point (hopefully, Round 2 will shed more light on the latter platforms). Table 1 in the Appendix summarizes some information received from the public on speeds; Table 2 reformulates Table1 by giving relative ranks. NIST has also accumu- lated information on speeds by testing the ANSI C and Java supplied by the algorithm submitters [33] and [34].... In PAGE 9: ... This has some impact on the measurement of efficiency. For example, Table1 in the Appendix is based on encryption speed. However, some candidates have different speeds for encryption and decryption.... In PAGE 21: ... Tables In the following tables, some candidates will be ab- breviated, as follows: CAST = CAST-256 CRYP = CRYPTON LOKI = LOKI97 MAG = MAGENTA RIJN = Rijndael SAFR = SAFER+ SERP = Serpent TWOF = Twofish NIST does not vouch for the accuracy of data not obtained by NIST. Table1 provides the encryption speeds of the candi- dates, measured in clock cycles, for encrypting one 128 bit block with a 128 bit key. Table 1.... ..."