Английская Википедия:Exposure Notification

Материал из Онлайн справочника
Перейти к навигацииПерейти к поиску

Шаблон:Short description Шаблон:Infobox protocol

The (Google/Apple) Exposure Notification System (GAEN)[1][2]Шаблон:Efn is a framework and protocol specification developed by Apple Inc. and Google to facilitate digital contact tracing during the COVID-19 pandemic. When used by health authorities, it augments more traditional contact tracing techniques by automatically logging close approaches among notification system users using Android or iOS smartphones. Exposure Notification is a decentralized reporting protocol built on a combination of Bluetooth Low Energy technology and privacy-preserving cryptography. It is an opt-in feature within COVID-19 apps developed and published by authorized health authorities.[3][4] Unveiled on April 10, 2020, it was made available on iOS on May 20, 2020 as part of the iOS 13.5 update[5] and on December 14, 2020 as part of the iOS 12.5 update for older iPhones.[6] On Android, it was added to devices via a Google Play Services update, supporting all versions since Android Marshmallow.

The Apple/Google protocol is similar to the Decentralized Privacy-Preserving Proximity Tracing (DP-3T) protocol created by the European DP-3T consortium and the Temporary Contact Number (TCN) protocol by Covid Watch, but is implemented at the operating system level, which allows for more efficient operation as a background process.[7][8][9] Since May 2020, a variant of the DP-3T protocol is supported by the Exposure Notification Interface.[10] Other protocols are constrained in operation because they are not privileged over normal apps. This leads to issues, particularly on iOS devices where digital contact tracing apps running in the background experience significantly degraded performance.[11][12][13] The joint approach is also designed to maintain interoperability between Android and iOS devices, which constitute nearly all of the market.

The ACLU stated the approach "appears to mitigate the worst privacy and centralization risks, but there is still room for improvement".[14] In late April, Google and Apple shifted the emphasis of the naming of the system, describing it as an "exposure notification service", rather than "contact tracing" system.[15]

Technical specification

Digital contact tracing protocols typically have two major responsibilities: encounter logging and infection reporting.[12] Exposure Notification only involves encounter logging which is a decentralized architecture. The majority of infection reporting is centralized in individual app implementations.[16]

To handle encounter logging, the system uses Bluetooth Low Energy to send tracking messages to nearby devices running the protocol to discover encounters with other people. The tracking messages contain unique identifiers that are encrypted with a secret daily key held by the sending device. These identifiers change every 15–20 minutes as well as Bluetooth MAC address in order to prevent tracking of clients by malicious third parties through observing static identifiers over time.Шаблон:Cn

The sender's daily encryption keys are generated using a random number generator.[17] Devices record received messages, retaining them locally for 14 days. If a user tests positive for infection, the last 14 days of their daily encryption keys can be uploaded to a central server, where it is then broadcast to all devices on the network. The method through which daily encryption keys are transmitted to the central server and broadcast is defined by individual app developers. The Google-developed reference implementation calls for a health official to request a one-time verification code (VC) from a verification server, which the user enters into the encounter logging app. This causes the app to obtain a cryptographically signed certificate, which is used to authorize the submission of keys to the central reporting server.[18]

The received keys are then provided to the protocol, where each client individually searches for matches in their local encounter history. If a match meeting certain risk parameters is found, the app notifies the user of potential exposure to the infection.[19] Google and Apple intend to use the received signal strength (RSSI) of the beacon messages as a source to infer proximity.[20] RSSI and other signal metadata will also be encrypted to resist deanonymization attacks.[17]

Version 1.0

To generate encounter identifiers, first a persistent 32-byte private Tracing Key (<math>tk</math>) is generated by a client. From this a 16 byte Daily Tracing Key is derived using the algorithm <math>dtk_i = HKDF(tk, NULL, \text{'CT-DTK'}||D_i, 16)</math>, where <math>HKDF(\text{Key, Salt, Data, OutputLength})</math> is a HKDF function using SHA-256, and <math>D_i</math> is the day number for the 24-hour window the broadcast is in starting from Unix Epoch Time. These generated keys are later sent to the central reporting server should a user become infected.[21]

From the daily tracing key a 16-byte temporary Rolling Proximity Identifier is generated every 10 minutes with the algorithm <math>RPI_{i,j} = \text{Truncate}(HMAC(dtk_i, \text{'CT-RPI'}||TIN_j),16)</math>, where <math>HMAC(\text{Key, Data})</math> is a HMAC function using SHA-256, and <math>TIN_j</math> is the time interval number, representing a unique index for every 10 minute period in a 24-hour day. The Truncate function returns the first 16 bytes of the HMAC value. When two clients come within proximity of each other they exchange and locally store the current <math>RPI_{i,j}</math> as the encounter identifier.[21]

Once a registered health authority has confirmed the infection of a user, the user's Daily Tracing Key for the past 14 days is uploaded to the central reporting server. Clients then download this report and individually recalculate every Rolling Proximity Identifier used in the report period, matching it against the user's local encounter log. If a matching entry is found, then contact has been established and the app presents a notification to the user warning them of potential infection.[21]

Version 1.1

Unlike version 1.0 of the protocol, version 1.1 does not use a persistent tracing key, rather every day a new random 16-byte Temporary Exposure Key (<math>tek_i</math>) is generated. This is analogous to the daily tracing key from version 1.0. Here <math>i</math> denotes the time is discretized in 10 minute intervals starting from Unix Epoch Time. From this two 128-bit keys are calculated, the Rolling Proximity Identifier Key (<math>RPIK_i</math>) and the Associated Encrypted Metadata Key (<math>AEMK_i</math>). <math>RPIK_i</math> is calculated with the algorithm <math>RPIK_i = HKDF(tek_i, NULL, \text{'EN-RPIK'},16)</math>, and <math>AEMK_i</math> using the algorithm<math>AEMK_i = HKDF(tek_i, NULL, \text{'EN-AEMK'},16)</math>.[22]

From these values a temporary Rolling Proximity Identifier (<math>RPI_{i,j}</math>) is generated every time the BLE MAC address changes, roughly every 15–20 minutes. The following algorithm is used: <math>RPI_{i,j} = AES128(RPIK_i, \text{'EN-RPI'} || \mathtt{0x000000000000} || ENIN_j)</math>, where <math>AES128(\text{Key, Data})</math> is an AES cryptography function with a 128-bit key, the data is one 16-byte block, <math>j</math> denotes the Unix Epoch Time at the moment the roll occurs, and <math>ENIN_j</math> is the corresponding 10-minute interval number. Next, additional Associated Encrypted Metadata is encrypted. What the metadata represents is not specified, likely to allow the later expansion of the protocol. The following algorithm is used: <math>\text{Associated Encrypted Metadata}_{i,j} = AES128\_CTR(AEMK_i, RPI_{i,j}, \text{Metadata})</math>, where <math>AES128\_CTR(\text{Key, IV, Data})</math> denotes AES encryption with a 128-bit key in CTR mode. The Rolling Proximity Identifier and the Associated Encrypted Metadata are then combined and broadcast using BLE. Clients exchange and log these payloads.[22]

Once a registered health authority has confirmed the infection of a user, the user's Temporary Exposure Keys <math>tek_i</math> and their respective interval numbers <math>i</math> for the past 14 days are uploaded to the central reporting server. Clients then download this report and individually recalculate every Rolling Proximity Identifier starting from interval number <math>i</math>, matching it against the user's local encounter log. If a matching entry is found, then contact has been established and the app presents a notification to the user warning them of potential infection.[22]

Version 1.2

Version 1.2 of the protocol is identical to version 1.1, only introducing minor terminology changes.[22]

Privacy

Preservation of privacy was referred to as a major component of the protocol; it is designed so that no personally identifiable information can be obtained about the user or their device.[23][4][24][25] Apps implementing Exposure Notification are only allowed to collect personal information from users on a voluntary basis.[26] Consent must be obtained by the user to enable the system or publicize a positive result through the system, and apps using the system are prohibited from collecting location data.[27] As an additional measure, the companies stated that it would sunset the protocol by-region once they determine that it is "no longer needed".[28]

The Electronic Frontier Foundation showed concerns the protocol was vulnerable to "linkage attacks", where sufficiently capable third parties who had recorded beacon traffic may retroactively be able to turn this information into tracking information, for only areas in which they had already recorded beacons, for a limited time segment and for only users who have disclosed their COVID-19 status, once a device's set of daily encryption keys have been revealed.[29]

On April 16, the European Union started the process of assessing the proposed system for compatibility with privacy and data protection laws, including the General Data Protection Regulation (GDPR).[30] On April 17, 2020, the UK's Information Commissioner's Office, a supervisory authority for data protection, published an opinion analyzing both Exposure Notification and the Decentralized Privacy-Preserving Proximity Tracing protocol, stating that the systems are "aligned with the principles of data protection by design and by default" (as mandated by the GDPR).[31]

Deployment

Exposure Notification is compatible with Android devices supporting Bluetooth Low Energy and running Android 6.0 "Marshmallow" and newer with Google Mobile Services. It is serviced via updates to Google Play Services, ensuring compatibility with the majority of Android devices released outside of Mainland China, and not requiring it to be integrated into Android firmware updates (which would hinder deployment by relying on individual OEMs). It is not compatible with devices that do not have GMS, such as Huawei devices released since May 2019.[32][33] On iOS, EN is serviced via operating system updates.[5] It was first introduced as part of iOS 13.5 on May 20, 2020.[34][35] In December 2020, Apple released iOS 12.5, which backported EN support to iPhone models that cannot be upgraded to iOS 13, including iPhone 6 and older.[35]

Exposure Notification apps may only be released by public health authorities. To discourage fragmentation, each country will typically be restricted to one app, although Apple and Google stated that they would accommodate regionalized approaches if a country elects to do so.[27] Apple and Google released reference implementations for apps utilizing the system, which can be used as a base.[27]

On September 1, 2020, the consortium announced "Exposure Notifications Express" (EN Express), a system designed to ease adoption of the protocol by health authorities by removing the need to develop an app themselves. Under this system, a health authority provides parameters specific to their implementation (such as thresholds, branding, messaging, and key servers), which is then processed to generate the required functionality. On Android, this data is used to generate an app, and a configuration profile that can also be deployed to users via Google Play Services without a dedicated app.[36] On iOS, the functionality is integrated directly at the system level on iOS 13.7 and newer without a dedicated app.[37] On December 14, 2020, Apple released iOS 12.5, bringing support for Exposure Notifications to older iPhones.Шаблон:Cn

The last information update on the “Exposure Notification Systems” partnership was a year end review issued by Google in December 2020:[38] "we plan to keep you updated here with new information again next year". Nothing has however been issued on the one year anniversary of the launch of the “Exposure Notification Interface” API in spite of important changes on the pandemic front such as vaccination, variants, digital health passports, app adoption challenges as well as growing interest for tracking QR codes (and notifying from that basis) on a mostly airborne transmitted virus.Шаблон:Original research inline The Frequently Asked Questions (FAQ) published document has not been revised since May 2020.[39] Basic support remains provided through the apps store released by authorized public health agencies, including enforcement of the personal privacy protection framework as demonstrated on the UK NHS challenge in support of their contact tracers.[40]

In June 2021, Google faced allegations that it had automatically downloaded Massachusetts' "MassNotify" app to Android devices without user consent. Google clarified that it had not actually downloaded the app to user devices, and that Google Play Services was being used to deploy an EN Express configuration profile that would allow it to be enabled via the Google Settings app without needing to download a separate app.[36]

Adoption

As of May 21, at least 22 countries had received access to the protocol.[26] Switzerland and Austria were among the first to back the protocol.[41] On April 26, after initially backing PEPP-PT, Germany announced it would back Exposure Notification,[42] followed shortly after by Ireland [43] and Italy.[44] Despite already adopting the centralised BlueTrace protocol,[45] Australia's Department of Health and Digital Transformation Agency were investigating whether the protocol could be implemented to overcome limitations of its COVIDSafe app.[26] On May 25, Switzerland became the first country to launch an app leveraging the protocol, SwissCovid, beginning with a small pilot group.[46]

In England, the National Health Service (NHS) trialed both an in-house app on a centralized platform developed by its NHSX division, and a second app using Exposure Notification.[47] On June 18, the NHS announced that it would focus on using Exposure Notification to complement manual contact tracing, citing tests on the Isle of Wight showing that it had better cross-device compatibility (and would also be compatible with other European approaches), but that its distance calculations were not as reliable as the centralized version of the app,[48] an issue which was later rectified.[49][50] Later, it was stated that the app would be supplemented by QR codes at venues.[51] A study of the impact of Exposure Notification in England and Wales estimated that it averted 8,700 (95% confidence interval 4,700–13,500) deaths out of the 32,500 recorded from its introduction on 24 September 2020 to 31 December 2020.[52]

Canada launched its COVID Alert app, co-developed in partnership with BlackBerry Limited and Shopify,[53] on July 31 in Ontario.[54] As of February 2022, only around 57,000 positive cases had been reported via the app, leading some critics to dismiss it as a failure.[55][56][57]

In May 2020, Covid Watch launched the first calibration and beta testing pilot of the GAEN APIs in the United States at the University of Arizona.[58][59] In Aug 2020, the app launched publicly for a phased roll-out in the state of Arizona.[60][61][62]

The U.S. Association of Public Health Laboratories (APHL) stated in July 2020 that it was working with Apple, Google, and Microsoft on a national reporting server for use with the protocol, which it stated would ease adoption and interoperability between states.[63][37]

In August 2020, Google stated that at least 20 U.S. states had expressed interest in using the protocol. In Alabama, the Alabama Department of Public Health, University of Alabama at Birmingham, and the University of Alabama System deployed the "GuideSafe" app for university students returning to campus, which includes Exposure Notification features.[64][65] On August 5, the Virginia Department of Health released its "COVIDWise" app — making it the first U.S. state to release an Exposure Notification-based app for the general public.[66][67][68] North Dakota and Wyoming released an EN app known as "Care19 Alert", developed by ProudCrowd and using the APHL server (the app is a spin-off from an existing location logging application it had developed, based on one it had developed primarily for use by students travelling to attend college football away games).[69][70]

Maryland, Nevada, Virginia, and Washington, D.C. have announced plans to use EN Express.[37] In September, Delaware, New Jersey, New York, and Pennsylvania all adopted "COVID Alert" apps developed by NearForm, which are based on its COVID Tracker Ireland app.[71][72] Later that month, the Norwegian Institute of Public Health announced that it would lead development of an Exposure Notification-based app for the country, which replaces a centralized app that had ceased operations in June 2020 after the Norwegian Data Protection Authority ruled that it violated privacy laws.[73][74]

In Nov 2020, Bermuda launched the Wehealth Bermuda app developed by Wehealth, a Public Benefit Corporation, which was based on the Covid Watch app released in Arizona.[75][76][77]

Country Region/State Name Announced/Released Notes
Шаблон:Flagcountry Stopp Corona App June 26, 2020 [78]
Шаблон:Flagcountry Coronavírus-SUS July 31, 2020 [79]
Шаблон:Flagcountry Wehealth Bermuda Nov 24, 2020 [75][76][77]
Шаблон:Flagcountry Coronalert October 1, 2020 (public) September 2, 2020 (Pilot phase) [80]
Шаблон:Flagcountry COVID Alert July 31, 2020 Available in New Brunswick, Newfoundland and Labrador, Ontario, Manitoba, Saskatchewan, Quebec, Prince Edward Island, and Nova Scotia.[81][54][82] Alberta and British Columbia have declined its use.[82]
Шаблон:Flagcountry eRouška (eMask) September 17, 2020 Since version 2.1[83][84]
Шаблон:Flagcountry Smittestop June 18, 2020 [85]
Шаблон:Flagcountry Hoia August 20, 2020 [86]
Шаблон:Flagcountry Koronavilkku August 31, 2020 [87]
Шаблон:Flagcountry Corona-Warn-App June 16, 2020 [88]
Шаблон:Flagcountry BEAT Covid Gibraltar June 18, 2020 Based on COVID Tracker Ireland and will interoperate with it.[89][90]
Шаблон:ISL Rakning C-19 May 12, 2021 GEAN implementation activated in May 2021, replaced previous version of app which used GPS tracking stored on-device launched in April 2020.[91][92]
Шаблон:Flagcountry COVID Tracker Ireland July 7, 2020 [93][94]
Шаблон:Flagcountry Immuni June 1, 2020 [95]
Шаблон:Flagcountry COCOA June 19, 2020 [96]
Шаблон:Flagcountry Jersey COVID Alert September 21, 2020 [97]
Шаблон:Flagcountry Apturi Covid May 29, 2020 [98]
Шаблон:Flagcountry Ma3an July 16, 2020 [99]
Шаблон:Flagicon Netherlands CoronaMelder October 10, 2020 (full release) [100]
Шаблон:Flagicon New Zealand NZ COVID Tracer December 10, 2020 (full release) [101]
Шаблон:Flagcountry Smittestopp December 21, 2020 Replaced a version of the app that was suspended earlier in the year due to scrutiny from the local Norwegian Data Protection Authority.[73][74]
Шаблон:Flagcountry StaySafe.ph March 29, 2021 GAEN implementation activated in April 2021 [102]
Шаблон:Flagcountry ProteGO Safe June 9, 2020 Update to existing encounter logging app.[103]
Шаблон:Flagcountry STAYAWAY COVID August 28, 2020 [104]
Шаблон:Flag Gosuslugi. Covid Tracker November 23, 2020 https://play.google.com/store/apps/details?id=com.minsvyaz.gosuslugi.exposurenotificationdroid
Шаблон:Flagcountry COVID Alert SA September 1, 2020 [105]
Шаблон:Flagcountry Radar COVID June 30, 2020 (beta test) [106]
Шаблон:Flagcountry SwissCovid May 26, 2020 (pilot phase) [46]
Шаблон:Flagcountry 臺灣社交距離 May 3, 2021 [107]
Шаблон:Flagcountry Thai Covid Alert April 26, 2022 [108]
Шаблон:Flagcountry Шаблон:Flagcountry
Шаблон:Flagcountry 		NHS COVID-19 September 24, 2020 [109]
Шаблон:Flagcountry StopCOVID NI July 30, 2020 Interoperates with COVID Tracker Ireland.[94]
Scotland Scotland Protect Scotland September 11, 2020 Based on COVID Tracker Ireland and will interoperate with it.[89]
Шаблон:Flagicon United States Шаблон:Flagicon Alabama GuideSafe August 3, 2020 Targeting University of Alabama students as part of a larger program under the same name.[64]
Шаблон:Flagicon Alaska Alaska COVID ENX January 20, 2022 [110]
Шаблон:Flagicon Arizona Covid Watch May 28, 2020 (attenuation and dynamic risk testing)

August 19, 2020 (released)

Targeting University of Arizona in a phased roll-out for the state of Arizona.[60][61][62]
Шаблон:Flagicon California CA Notify December 10, 2020 [111][112]
Шаблон:Flagicon Colorado CO Exposure Notifications October 25, 2020 [113]
Шаблон:Flagicon Connecticut COVID Alert CT November 12, 2020 [114]
Шаблон:Flagicon Delaware COVID Alert DE September 15, 2020 Based on COVID Tracker Ireland.[72]
Шаблон:Flagicon Guam Guam Covid Alert September 10, 2020 Based on the PathCheck Foundation's GAEN Mobile project
Шаблон:Flagicon Hawaii Aloha Safe Alert November 11, 2020 Based on the PathCheck Foundation's GAEN Mobile project
Шаблон:Flagicon Louisiana COVID Defense January 22, 2021 Based on the PathCheck Foundation's GAEN Mobile project [115][116]
Шаблон:Flagicon Maryland MD COVID Alert October 10, 2020 [117]
Шаблон:FlagiconMassachusetts MassNotify Uses EN Express.[118]
Шаблон:Flagicon Michigan MI COVID Alert October 15, 2020 (Michigan State University pilot)

November 9, 2020 (statewide)

[119][120][121]
Шаблон:Flagicon Minnesota COVIDaware MN November 23, 2020 [122][123]
Шаблон:Flagicon Missouri MO/Notify July 29, 2021 Targeting Washington University in St. Louis in a phased roll-out for the state of Missouri.[124][125]
Шаблон:Flagicon New Jersey COVID Alert NJ September 30, 2020 Based on COVID Tracker Ireland.[72]
Шаблон:Flagicon New York COVID Alert NY September 30, 2020 Based on COVID Tracker Ireland.[72]
Шаблон:Flagicon North Carolina SlowCOVIDNC September 22, 2020 The app was shut down on or before August 19, 2022.[126]
Шаблон:Flagicon North Dakota Care19 Alert August 13, 2020 [127]
Шаблон:Flagicon Pennsylvania COVID Alert PA September 24, 2020 Based on COVID Tracker Ireland.[72]
Шаблон:Flagicon Utah UT Exposure Notifications February 16, 2021 [128]
Шаблон:Flagicon Virginia COVIDWise August 5, 2020 [68]
Шаблон:Flagicon Washington WA Notify November 30, 2020 [129][130]
Шаблон:Flagicon Wisconsin WI Exposure Notification December 23, 2020 [131]
Шаблон:Flagicon Wyoming Care19 Alert August 14, 2020 [132]
Шаблон:Flagcountry Coronavirus UY June 15, 2020 [133]

Alternatives

Some countries, such as France, have pursued centralized approaches to digital contact tracing, in order to maintain records of personal information that can be used to assist in investigating cases.[24][134] The French government asked Apple in April 2020 to allow apps to perform Bluetooth operations in the background, which would allow the government to create its own system independent of Exposure Notification.[135]

On August 9, the Canadian province of Alberta announced plans to migrate to the EN-based COVID Alert from its BlueTrace-based ABTraceTogether app.[136][137] This did not occur, and on November 6 Premier of Alberta Jason Kenney announced that the province would not do so, arguing that ABTraceTogether was "from our view, simply a better and more effective public health tool", and that they would be required to phase out ABTraceTogether if they did switch.[138] British Columbia has also declined to adopt COVID Alert, with provincial health officer Bonnie Henry stating that COVID Alert was too "non-specific".[138]

Australia's officials have stated its COVIDSafe, which is based on Singapore's BlueTrace, will not be shifting from manual intervention.[139][140]

In the United States, states such as California and Massachusetts declined to use the technology, opting for manual contact tracing.[141] California later reversed course and adopted the system in December 2020.[111][112]

Chinese vendor Huawei (which cannot include Google software on its current Android products due to U.S. sanctions) added a OS-level DP-3T API known as "Contact Shield" to its Huawei Mobile Services stack in June 2020, which the company states is intended to be interoperable with Exposure Notification.[142]

Notes

Шаблон:Notelist

References

Шаблон:Reflist

External links

Шаблон:Apple Шаблон:Google LLC

Партнерские ресурсы
Криптовалюты
Магазины
Хостинг
Разное

  1. ↑ Шаблон:Cite web
  2. ↑ Шаблон:Cite journal
  3. ↑ Шаблон:Cite web
  4. ↑ 4,0 4,1 Шаблон:Cite web
  5. ↑ 5,0 5,1 Шаблон:Cite news
  6. ↑ Шаблон:Cite web
  7. ↑ Шаблон:Cite web
  8. ↑ Шаблон:Cite web
  9. ↑ Шаблон:Cite web
  10. ↑ Шаблон:Cite web
  11. ↑ Шаблон:Cite web
  12. ↑ 12,0 12,1 Шаблон:Cite web
  13. ↑ Шаблон:Cite web
  14. ↑ Шаблон:Cite news
  15. ↑ Шаблон:Cite web
  16. ↑ Шаблон:Cite web
  17. ↑ 17,0 17,1 Шаблон:Cite web
  18. ↑ Шаблон:Cite web
  19. ↑ Шаблон:Cite web
  20. ↑ Шаблон:Cite magazine
  21. ↑ 21,0 21,1 21,2 Шаблон:Cite web
  22. ↑ 22,0 22,1 22,2 22,3 Шаблон:Cite web
  23. ↑ Шаблон:Cite web
  24. ↑ 24,0 24,1 Шаблон:Cite web
  25. ↑ Шаблон:Cite web
  26. ↑ 26,0 26,1 26,2 Шаблон:Cite web
  27. ↑ 27,0 27,1 27,2 Шаблон:Cite news
  28. ↑ Шаблон:Cite web
  29. ↑ Шаблон:Cite web
  30. ↑ Шаблон:Cite news
  31. ↑ Шаблон:Cite web
  32. ↑ Шаблон:Cite web
  33. ↑ Шаблон:Cite web
  34. ↑ Шаблон:Cite web
  35. ↑ 35,0 35,1 Шаблон:Cite web
  36. ↑ 36,0 36,1 Шаблон:Cite web
  37. ↑ 37,0 37,1 37,2 Шаблон:Cite web
  38. ↑ Шаблон:Cite web
  39. ↑ Шаблон:Cite web
  40. ↑ Шаблон:Cite news
  41. ↑ Шаблон:Cite web
  42. ↑ Шаблон:Cite news
  43. ↑ Шаблон:Cite news
  44. ↑ Шаблон:Cite web
  45. ↑ Шаблон:Cite web
  46. ↑ 46,0 46,1 Шаблон:Cite web
  47. ↑ Шаблон:Cite news
  48. ↑ Шаблон:Cite news
  49. ↑ Шаблон:Cite arXiv
  50. ↑ Шаблон:Cite web
  51. ↑ Шаблон:Cite web
  52. ↑ Шаблон:Cite journal
  53. ↑ Шаблон:Cite web
  54. ↑ 54,0 54,1 Шаблон:Cite web
  55. ↑ Шаблон:Cite web
  56. ↑ Шаблон:Cite web
  57. ↑ Шаблон:Cite web
  58. ↑ Шаблон:Cite web
  59. ↑ Шаблон:Cite web
  60. ↑ 60,0 60,1 Шаблон:Cite web
  61. ↑ 61,0 61,1 Шаблон:Cite web
  62. ↑ 62,0 62,1 Шаблон:Cite web
  63. ↑ Шаблон:Cite web
  64. ↑ 64,0 64,1 Шаблон:Cite web
  65. ↑ Шаблон:Cite web
  66. ↑ Шаблон:Cite web
  67. ↑ Шаблон:Cite web
  68. ↑ 68,0 68,1 Шаблон:Cite news
  69. ↑ Шаблон:Cite web
  70. ↑ Шаблон:Cite news
  71. ↑ Шаблон:Cite web
  72. ↑ 72,0 72,1 72,2 72,3 72,4 Шаблон:Cite web
  73. ↑ 73,0 73,1 Шаблон:Cite web
  74. ↑ 74,0 74,1 Шаблон:Cite news
  75. ↑ 75,0 75,1 Шаблон:Cite web
  76. ↑ 76,0 76,1 Шаблон:Cite web
  77. ↑ 77,0 77,1 Шаблон:Cite web
  78. ↑ Шаблон:Cite web
  79. ↑ Шаблон:Cite news
  80. ↑ Шаблон:Cite news
  81. ↑ Шаблон:Cite web
  82. ↑ 82,0 82,1 Шаблон:Cite web
  83. ↑ Шаблон:Cite web
  84. ↑ Шаблон:Cite news
  85. ↑ Шаблон:Cite web
  86. ↑ Шаблон:Cite news
  87. ↑ Шаблон:Cite news
  88. ↑ Шаблон:Cite web
  89. ↑ 89,0 89,1 Шаблон:Cite news
  90. ↑ Шаблон:Cite web
  91. ↑ Шаблон:Cite web
  92. ↑ Шаблон:Cite web
  93. ↑ Шаблон:Cite news
  94. ↑ 94,0 94,1 Шаблон:Cite news
  95. ↑ Шаблон:Cite news
  96. ↑ Шаблон:Cite web
  97. ↑ Шаблон:Cite web
  98. ↑ Шаблон:Cite web
  99. ↑ Шаблон:Cite web
  100. ↑ Шаблон:Cite web
  101. ↑ Шаблон:Cite web
  102. ↑ Шаблон:Cite news
  103. ↑ Шаблон:Cite news
  104. ↑ Шаблон:Cite news
  105. ↑ Шаблон:Cite web
  106. ↑ Шаблон:Cite web
  107. ↑ Шаблон:Cite web
  108. ↑ Шаблон:Cite web
  109. ↑ Шаблон:Cite news
  110. ↑ Шаблон:Cite web
  111. ↑ 111,0 111,1 Шаблон:Cite web
  112. ↑ 112,0 112,1 Шаблон:Cite web
  113. ↑ Шаблон:Cite web
  114. ↑ Шаблон:Cite web
  115. ↑ Шаблон:Cite web
  116. ↑ Шаблон:Cite web
  117. ↑ Шаблон:Cite web
  118. ↑ Шаблон:Cite web
  119. ↑ Шаблон:Cite web
  120. ↑ Шаблон:Cite press release
  121. ↑ Шаблон:Cite web
  122. ↑ Шаблон:Cite web
  123. ↑ Шаблон:Cite web
  124. ↑ Шаблон:Cite web
  125. ↑ Шаблон:Cite web
  126. ↑ Шаблон:Cite web
  127. ↑ Шаблон:Cite web
  128. ↑ Шаблон:Cite web
  129. ↑ Шаблон:Cite web
  130. ↑ Шаблон:Cite web
  131. ↑ Шаблон:Cite press release
  132. ↑ Шаблон:Cite web
  133. ↑ Шаблон:Cite news
  134. ↑ Шаблон:Cite news
  135. ↑ Шаблон:Cite news
  136. ↑ Шаблон:Cite web
  137. ↑ Шаблон:Cite web
  138. ↑ 138,0 138,1 Шаблон:Cite web
  139. ↑ Шаблон:Cite web
  140. ↑ Шаблон:Cite web
  141. ↑ Шаблон:Cite magazine
  142. ↑ Шаблон:Cite web
Источник — http://wikihandbk.com/ruwiki/index.php?title=Английская_Википедия:Exposure_Notification&oldid=14631071