Thanks, Dean. This matches the output I see from my implementation of the algorithm (https://bifurcation.github.io/nomcom/).
--Richard
On Sat, Jul 6, 2024 at 8:53 PM NomCom Chair 2024 <nomcom-chair-2024@xxxxxxxx> wrote:
Hello,
The lottery results are in and these are the results:
# The seven numbers from Croatian Lottery Loto 7 on July 6th, 2024
12 13 15 18 24 27 32
# The seven numbers from Euro-Millions on July 5th, 2024
11 13 29 31 47 1 11
# Six numbers from the US Mega Millions on July 5th, 2024
6 15 32 54 67 4
# The nine numbers from the Japanese Lotto 7 on July 5th, 2024
5 7 22 29 30 32 36 3 33
Unfortunately, there was an operator error. In the 2024.seeds, I had a leading new line, which created a wrong string
./12.13.15.18.24.27.32./1.11.11.13.29.31.47./4.6.15.32.54.67./3.5.7.22.29.30.32.33.36./
(see the leading ./)
The correct string is
12.13.15.18.24.27.32./1.11.11.13.29.31.47./4.6.15.32.54.67./3.5.7.22.29.30.32.33.36./
I've corrected the 2024.seeds file. Rich Salz, who is the implementor and maintainer of the code, will be informed about this issue.
The original list sent out had 163 names, but the 2024.names was 1 name shorter, and that was corrected as well.
With using corrected seeds, the RFC 3797 algorithm produces the following list:
./pick -s 2024.seeds -n 2024.names -c 15 -d
Read 163 names
Need approximately 69.5 bits of entropy
Key string is 12.13.15.18.24.27.32./1.11.11.13.29.31.47./4.6.15.32.54.67./3.5.7.22.29.30.32.33.36./
index hex value of MD5 div selected
1 BC81F2624CA65F4E4D06FBBE391A2C07 163 -> 33 <- Nick Doty Center for Democracy & Technology
2 EA58F62A08DD75055BC556603E1746FA 162 -> 122 <- Hang Shi Huawei
3 904BECF7222521E31E1DA5E15CB52580 161 -> 43 <- Giuseppe Fioccola Huawei Technologies
4 DC9D1194C9E0FBF11DF5DAB23758505B 160 -> 127 <- A.J. Stein NIST
5 7AEBBBDBA66D6982D474E19473F56250 159 -> 115 <- Michael Richardson Sandelman Software Works Inc
6 A23A244DD0B5967CF666CC8C887D0929 158 -> 100 <- Benno Overeinder NLnet Labs
7 EC40AF8FC79BBD91EBB01EF92BEFCCA4 157 -> 132 <- Dirk Trossen Huawei Technologies
8 B64F1852DA7C978A99F262FBC6C09285 156 -> 145 <- Quan Xiong ZTE Corporation
9 0E59DEA81DF59D21B2BCF0CC5482E206 155 -> 76 <- Eliot Lear "Cisco Systems, Inc."
10 9914609D233ADE76B74F6D5851CABD1C 154 -> 45 <- Thomas Fossati Linaro
11 8BC011E2B310CB06D8CEAA62EE54A769 153 -> 129 <- Haiyang Su Huawei Technologies Co.,Ltd.
12 98C4F73860C4AC430EBBB2A517A51674 152 -> 89 <- Kiran Makhijani independent
13 660764B9ADC6FD93DDD494CC8B780FC7 151 -> 97 <- Greg Mirsky Ericsson
14 0129973C4B790D9CEB852C3A96048BEF 150 -> 16 <- Luc Andre Burdet Cisco
15 B99E02C2E5CA109CCE7339DC6089C336 149 -> 57 <- Tom Harrison APNIC
Per rfc9389 section 4.1.2. The Two-per-organization limit, Dirk Trossen and Haiyang Su are ineligible, so the first 10 members are:
1 BC81F2624CA65F4E4D06FBBE391A2C07 163 -> 33 <- Nick Doty Center for Democracy & Technology
2 EA58F62A08DD75055BC556603E1746FA 162 -> 122 <- Hang Shi Huawei
3 904BECF7222521E31E1DA5E15CB52580 161 -> 43 <- Giuseppe Fioccola Huawei Technologies
4 DC9D1194C9E0FBF11DF5DAB23758505B 160 -> 127 <- A.J. Stein NIST
5 7AEBBBDBA66D6982D474E19473F56250 159 -> 115 <- Michael Richardson Sandelman Software Works Inc
6 A23A244DD0B5967CF666CC8C887D0929 158 -> 100 <- Benno Overeinder NLnet Labs
7 B64F1852DA7C978A99F262FBC6C09285 156 -> 145 <- Quan Xiong ZTE Corporation
8 0E59DEA81DF59D21B2BCF0CC5482E206 155 -> 76 <- Eliot Lear "Cisco Systems, Inc."
9 9914609D233ADE76B74F6D5851CABD1C 154 -> 45 <- Thomas Fossati Linaro
10 98C4F73860C4AC430EBBB2A517A51674 152 -> 89 <- Kiran Makhijani independent
I apologize for the operator error and thanks to Martin Thomson, who informed me quickly about the discrepancy in the results. I will inform the selected members via email.
This mail starts a challenge period. The challenge period will end on July 17th, 2024. If you wish to challenge this selection, see Section 4.17 of RFC 8713 for the process to follow (in short: email me).
Dean Bogdanovic
nomcom-chair-2024@xxxxxxxx
_______________________________________________
IETF-Announce mailing list -- ietf-announce@xxxxxxxx
To unsubscribe send an email to ietf-announce-leave@xxxxxxxx
